Nokia 1 TA-1047 in Red State

Pages (4): 1 2 3 4 Next

hartmut
Junior Member

14-02-2019, 06:04 PM

I my attempt to root the Nokia TA-1047 I probably made several mistakes and ended up in a Red State. On power up it indicates "Red State" and "will reboot in 5 Seconds" and this is going on in an endless loop. So I cannot even connect with adb or fastboot.
I installed the SPFlashTool. I downloaded Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip mentioned in https://www.hovatek.com/forum/thread-24190.html. Unfortunately, already mentioned there, it contains only NVRAM and NVDATA and not the essential parts for booting (is this true?). Nevertheless I tried to download it to the phone.
Then I got the error message "CHIP TYPE NOT match!! target efuse value: 0x94010000". As suggested here https://www.hovatek.com/forum/thread-439.html I should untick the preloader when flashing, but the preloader doesn't show up in this rom package.

I conclude that SPFlashTool can communicate with the phone, but I am just missing the right firmware package, right? I googeled a lot but I always ended up at the same package.

I there any way to put the phone back to life?

xerxes
Senior Member

8,357

15-02-2019, 08:22 AM

(14-02-2019, 06:04 PM)hartmut I my attempt to root the Nokia TA-1047 I probably made several mistakes and ended up in a Red State. On power up it indicates "Red State" and "will reboot in 5 Seconds" and this is going on in an endless loop. So I cannot even connect with adb or fastboot.
I installed the SPFlashTool. I downloaded Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip mentioned in https://www.hovatek.com/forum/thread-24190.html. Unfortunately, already mentioned there, it contains only NVRAM and NVDATA and not the essential parts for booting (is this true?). Nevertheless I tried to download it to the phone.
Then I got the error message "CHIP TYPE NOT match!! target efuse value: 0x94010000". As suggested here https://www.hovatek.com/forum/thread-439.html I should untick the preloader when flashing, but the preloader doesn't show up in this rom package.

I conclude that SPFlashTool can communicate with the phone, but I am just missing the right firmware package, right? I googeled a lot but I always ended up at the same package.

I there any way to put the phone back to life?

Can the phone still boot to fastboot mode?

Sent from my M5 mini using Hovatek Mobile

hartmut
Junior Member

15-02-2019, 08:54 AM

Probably not. I usually entered fastboot mode with "adb reboot bootloader" but I cannot connect to it by adb any more. I tried pressing some buttons during booting but this didn't change anything. It is still stuck in its endless loop of boot trials.

hovatek
Administrator

49,753

15-02-2019, 10:22 AM

(15-02-2019, 08:54 AM)hartmut Probably not. I usually entered fastboot mode with "adb reboot bootloader" but I cannot connect to it by adb any more. I tried pressing some buttons during booting but this didn't change anything. It is still stuck in its endless loop of boot trials.

when you tried rooting, what exactly did you do? unlock bootloader, flash any file? if yes, then which?

to get to fastboot mode, try either of the two methods below
1
power off the phone (either disconnect / reconnect the battery OR wait for the battery to drain completely then charge a little) >
with the phone powered down, connect the phone to a charger and wait till the charging logo shows up >
press vol down + power button >
this should get you to fastboot mode

2
power off the phone (either disconnect / reconnect the battery OR wait for the battery to drain completely then charge a little) >
boot into recovery mode; connect the phone to a charger and wait till the charging logo shows up >
press vol up + power button >
if you get stuck at android lying on its back, press power + vol up
in recovery mode, select the option 'reboot to bootloader'
this should get you to fastboot mode

in fastboot mode, depending on what you did to try rooting
you may need to flash back stock image of any partition you flashed then relock bootloader

hartmut
Junior Member

15-02-2019, 11:41 AM

What I originally did:
- I unlocked the bootloader with "adb get-serialno" etc. see https://forum.xda-developers.com/nokia-1...1-t3784942[url=https://forum.xda-developers.com/nokia-1/help/how-to-unlock-bootloader-root-nokia-1-t3784942][/url]
- I installed TWRP, following this guide https://www.xda-developers.com/how-to-install-twrp/
- I entered "fastboot reboot". The phone rebooted. Android demanded again some basic configurations, as if it was brand new, and automatically downloaded and installed some updates. Then I could finally reboot into recovery mode and had TWRP on the screen.
- TWRP could not read the internal storage because of encryption. I did Wipe->Format Data and Wipe->Factory Reset.
- Now I could access the internal storage, but I could not do a System reboot any more. Always TWRP came up. I googeled this problem and tried several things but it didn't help.
- At this stage (I don't know since when exactly) the phone said being in "Orange State" when rebooting.
- Then I tried (probably my crucial mistake): "fastboot -i 0x2e04 oem lock"
- Now not even TWRP came up and the phone said "Red State".

With your methode 1 I could turn the phone into fastboot mode again. :-)
I could unlock it again. Now I am back in "Orange State" and TWRP comes up.

If I try to make a System Reboot this message comes: "Orange State. Your device has been unlocked and can't be trusted. Rebooting in 5 seconds." And then always TWRP comes up.

As concernes the ROM image Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip:
In fact the zip contains all parts, not only NVRAM and NVDATA, but the included MT6735_Android_scatter.txt refers only to these two items. Here https://www.hovatek.com/forum/thread-24190.html I found the file MT6735_Android_scatter_1.txt, which refers to all other parts but SPFlashTool tool says "Boundary Check Failed", the blocks PRELOADER and PGPT overlap. Since these two blocks go into different regions anyway (EMMC_BOOT and EMMC_USER) this is not a real problem (I assume) and one can fix it by setting "boundary_check: false" in the PRELOADER section. I upload the corrected MT6735_Android_scatter_1.txt here.

So I am ready to flash anything onto the phone now.
What do you recommend I should do?

Attached Files

MT6735_Android_scatter_1.txt
Size: 11.83 KB / Downloads: 39

hartmut
Junior Member

15-02-2019, 01:50 PM

Still I cannot make a System Boot. I just tried to flash the stock rom onto the phone. I get the error "CHIP TYPE NOT match!! target efuse value: 0x94010000". Deselecting the PRELOADER doesn't help.

hovatek
Administrator

49,753

15-02-2019, 05:28 PM

(15-02-2019, 11:41 AM)hartmut What I originally did:
...
So I am ready to flash anything onto the phone now.
What do you recommend I should do?

not sure how you got this rom or if its meant for your exact build, after checking the scatter file, you should be able to flash using miracle box @ https://www.hovatek.com/forum/thread-14106.html without modified boundary check

but don't flash the entire rom yet (unless you can somehow verify that this rom works for your device build)
try to backup firmware from your phone using the guide @ https://www.hovatek.com/forum/thread-21970.html
boot to fastboot then flash stock recovery.img >
use the values from the scatter file in your backup to format ONLY seccfg partition using the guide @ https://www.hovatek.com/forum/thread-21638.html
then reboot the phone and check if its still red or orange state

This post was last modified: 15-02-2019, 05:36 PM by X3non.

hartmut
Junior Member

15-02-2019, 10:27 PM

ok, I tried to create a backup. The tool Wwr_MTK didn't run. I tried versions 2.3 and 2.4 and both crashed a few seconds after the program window appeared.
I tried SPFlashTool with the Readback feature, and again got the error "CHIP TYPE NOT match!! target efuse value: 0x94010000". What does this error mean for a Readback?
I tried Miracle Box 2.58, MTK->Service->Read, "8th Boot(MT65xx & MT67xx/8127)". The output panel shows:
Connected to Phone.
CPU: MT6735 SW:000 Ver: CA00
Downloading Boot8...
100%
Then Miracle Box crashes.

I give up for the moment. Next week I am pretty much offline. I'll continue afterwards, hoping that the battery holds...

hovatek
Administrator

49,753

16-02-2019, 10:07 AM

(15-02-2019, 10:27 PM)hartmut ok, I tried to create a backup. The tool Wwr_MTK didn't run. I tried versions 2.3 and 2.4 and both crashed a few seconds after the program window appeared.
I tried SPFlashTool with the Readback feature, and again got the error "CHIP TYPE NOT match!! target efuse value: 0x94010000". What does this error mean for a Readback?
I tried Miracle Box 2.58, MTK->Service->Read, "8th Boot(MT65xx & MT67xx/8127)". The output panel shows:
Connected to Phone.
CPU: MT6735 SW:000 Ver: CA00
Downloading Boot8...
100%
Then Miracle Box crashes.

I give up for the moment. Next week I am pretty much offline. I'll continue afterwards, hoping that the battery holds...

disconnect internet before launching wwr tool or block the tool using a firewall program and it should launch without crashing
for SPft, try using an MT6737 scatter file
for miracle box, try v2.82 or try a different PC

hovatek
Administrator

49,753

18-02-2019, 08:52 PM

#10

(15-02-2019, 10:27 PM)hartmut ok, I tried to create a backup. The tool Wwr_MTK didn't run. I tried versions 2.3 and 2.4 and both crashed a few seconds after the program window appeared.
I tried SPFlashTool with the Readback feature, and again got the error "CHIP TYPE NOT match!! target efuse value: 0x94010000". What does this error mean for a Readback?
I tried Miracle Box 2.58, MTK->Service->Read, "8th Boot(MT65xx & MT67xx/8127)". The output panel shows:
Connected to Phone.
CPU: MT6735 SW:000 Ver: CA00
Downloading Boot8...
100%
Then Miracle Box crashes.

I give up for the moment. Next week I am pretty much offline. I'll continue afterwards, hoping that the battery holds...

Boot into TWRP and Backup .
Next flash magisk or supersu (systemless) then reboot.
Let me know how that goes

This post was last modified: 02-03-2019, 10:00 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

Pages (4): 1 2 3 4 Next

View a Printable Version

Users browsing this thread:
1 Guest(s)

Find us

Call us

Mail us

Useful Links

Actions