Nokia 1 TA-1047 in Red State

Jemoh
Techie Member

50

23-02-2019, 04:33 PM

#11

Hello brother, did you manage?

raihanrana91
Junior Member

17

23-02-2019, 04:43 PM

#12

Pliz sir help ...I need TWRP SPD sc9832e Android 8.1 ...pliz sir give this recovery

Sent from my i95 using Hovatek Mobile

raihanrana91
Junior Member

17

23-02-2019, 04:46 PM

#13

Pliz sir help ...I need TWRP SPD sc9832e Android 8.1 ...pliz sir give this recovery

Sent from my i95 using Hovatek Mobile

X3non
Recognized Contributor

22,062

25-02-2019, 09:09 AM

#14

(23-02-2019, 04:43 PM)raihanrana91 Pliz sir help ...I need TWRP SPD sc9832e Android 8.1 ...pliz sir give this recovery

Sent from my i95 using Hovatek Mobile

stick to your thread @ https://www.hovatek.com/forum/thread-26802.html

hartmut
Junior Member

19

26-02-2019, 06:14 PM

#15

I tried several things.
- TWRP backup to SD card worked and created the files below:
16777216 boot.emmc.win
16935424 cache.ext4.win
4729856 data.ext4.win
1048576 frp.emmc.win
1048576 lk.emmc.win
2097152 logo.emmc.win
1678336 nvdata.ext4.win
5242880 nvram.emmc.win
524288 para.emmc.win
3145728 proinfo.emmc.win
11264 protect_f.ext4.win
9216 protect_s.ext4.win
16777216 recovery.emmc.win
1254513152 system.ext4.win
2097152 tee1.emmc.win
2097152 tee2.emmc.win
289496064 vendor.ext4.win

wwr tool is working when the PC is offline.

SPft still says "CHIP TYPE NOT match!". If I edit the scatter file and set "platform: MT6737" then SPft complains: "Platform MT67 not supported on this version. Please update to latest flashtool." Using SPft 5.1904. But MiracleBox confirms that the phone is a MT6735, so changing to MT6737 is probably not the right way.

MiracleBox: v2.58 keeps crashing, so I tried v2.82.
With MTK->Service->Read, "8th Boot(MT65xx & MT67xx/8127)" I get the following in the output panel:
Waiting for USB Port...
Set COM28
Connecting to Phone,Wait..
Connected to Phone.
CPU: MT6735 SW:0000 Ver: CA00
>>Downloading Boot8 ...
The progress bar goes immediately to 100% and the phone boots (into TWRP). No file dialog appears, no download is saved anywhere.
With MTK->Service->Read, "Boot(MT6735/7 & MT6582 & MT6571/2)" I get the same output (with Boot11 instead of Boot8).

So I have a TWRP backup now. All other backup attempts are not working yet. I didn't flash anything yet. I'll try to install magisk.
What else should I do?

hartmut
Junior Member

19

26-02-2019, 09:57 PM

#16

I have installed magisk via TWRP but as long as I cannot make a system boot this doesn't help me, right?

hartmut
Junior Member

19

27-02-2019, 07:37 AM

#17

Some of the files from the TWRP backup have the same filenames and the sizes as the files from the ROM "Nokia_1_TA-1047_MT6735_V8.1.0_180401". These are: nvram,lk,boot,recovery,logo,tee1,tee2. Some have different sizes: nvdata, system, cache. Some files are missing in the ROM: proinfo, protect_f, protect_s, para, frp, vendor, data. Some files are missing in the TWRP backup: secro, systeminfo

Is this due to different methods of backup, or does it mean that the ROM is not compatible? Anyway, the TWRP backup gives me no confirmation that the ROM scatter file is correct as concerns the block positions. I could not create a scatter file as described here https://www.hovatek.com/forum/thread-21970.html because SPft doesn't backup anything (CHIP TYPE NOT MATCH error). And I haven't got a preloader backup, because TWRP doesn't create one.

Still my problem is, that the phone is on orange state and that it doesn't boot into system, only recovery.

X3non
Recognized Contributor

22,062

27-02-2019, 11:17 AM

#18

(27-02-2019, 07:37 AM)hartmut Some of the files from the TWRP backup have the same filenames and the sizes as the files from the ROM "Nokia_1_TA-1047_MT6735_V8.1.0_180401". These are: nvram,lk,boot,recovery,logo,tee1,tee2. Some have different sizes: nvdata, system, cache. Some files are missing in the ROM: proinfo, protect_f, protect_s, para, frp, vendor, data. Some files are missing in the TWRP backup: secro, systeminfo
Is this due to different methods of backup, or does it mean that the ROM is not compatible?
...

different backup methods, keep the twrp backup handy

(27-02-2019, 07:37 AM)hartmut Anyway, the TWRP backup gives me no confirmation that the ROM scatter file is correct as concerns the block positions. I could not create a scatter file as described here https://www.hovatek.com/forum/thread-21970.html because SPft doesn't backup anything (CHIP TYPE NOT MATCH error). And I haven't got a preloader backup, because TWRP doesn't create one.

Still my problem is, that the phone is on orange state and that it doesn't boot into system, only recovery.

now try flashing ONLY boot and system.img from the firmware you downloaded
you can try flashing using SPflash tool, you'll probably require a DA file which you can get @ https://www.hovatek.com/forum/thread-23528.html
OR you can flash boot and system using fastboot

after flashing, relock bootloader and perform a factory reset then check if the phone can now boot to homescreen

hartmut
Junior Member

19

27-02-2019, 06:33 PM

#19

I downloaded MTK_AllInOne_DA.bin from https://www.hovatek.com/forum/thread-23528.html (Nokia 1). If I select it in SPft I get the error "LIB DA not match, please re-select DA or ask for help".

So I tried fastboot. The command "fastboot flash boot boot.bin" worked fine. The command "fastboot flash system system.bin" created the error "Invalid sparse file format at header magi". I tried the same with the system.bin which I had backedup before with TWRP and got the same error. So I guess that it is not the downloaded system.bin which creates the error. Then I tried again with boot.bin and it worked fine as before.

The backed-up system.bin has the file size 1 254 513 152.
The downloaded system.bin has thefile size 1 459 617 792.
When flashing with fastboot I get the message "target reported max download size of 134 217 728 bytes". Are the files too big for fastboot flash? Or do I have to delete something to get more space?

Btw, flashing boot.bin alone didn't solve the problem.

X3non
Recognized Contributor

22,062

28-02-2019, 09:40 AM

#20

(27-02-2019, 06:33 PM)hartmut I downloaded MTK_AllInOne_DA.bin from https://www.hovatek.com/forum/thread-23528.html (Nokia 1). If I select it in SPft I get the error "LIB DA not match, please re-select DA or ask for help".

So I tried fastboot. The command "fastboot flash boot boot.bin" worked fine. The command "fastboot flash system system.bin" created the error "Invalid sparse file format at header magi". I tried the same with the system.bin which I had backedup before with TWRP and got the same error. So I guess that it is not the downloaded system.bin which creates the error. Then I tried again with boot.bin and it worked fine as before.

The backed-up system.bin has the file size 1 254 513 152.
The downloaded system.bin has thefile size 1 459 617 792.
When flashing with fastboot I get the message "target reported max download size of 134 217 728 bytes". Are the files too big for fastboot flash? Or do I have to delete something to get more space?

Btw, flashing boot.bin alone didn't solve the problem.

for SPft lib error, try a different SPft version e.g v5.1828

for fastboot magic header error, use the adb & fastboot @ https://www.hovatek.com/forum/thread-17105.html

View a Printable Version

Users browsing this thread:
1 Guest(s)

Find us

Call us

Mail us

Useful Links

Actions