Related
Hello,
I am not sure what happened, but here is the story.
First, I tried to root the phone using the 1-click method, only to later realize that it does not work as the phone I had was running the latest OTA update. I wanted to reset my phone to factory default and I proceeded to do that.
Now, when my phone starts I see the small recovery menu and a lot of red letters stating that the system could not mount, find or open recovery directories, files or logs. (On the screen is this info Enter ok key,Select vol up/down Rebot system now, apply update from scard,wipe data/factory reset,wipe cache partition But nothing will move courser,then blow that in red is E:failed to open/res/recovery.fstab(no such file or directory) E:unknown volume for path[/cache/recovery/command with a lot more then in yellow letters #manual mode# and the same messages)
When I enter the download mode, and tried to use Odin or ADB, neither one can detect my device. I tried installing different samsung drivers on my system to no solution to being able to detect the device. Is this due to Windows not being able to initiate the drivers correctly, because when I connect the phone in Download mode, Windows has a pop-up show up that says "Drivers not recognized, your device might not work properly".
Does this mean the phone is bricked or is there something I can do to restore the phone?
Informatic_dev said:
Hello,
I am not sure what happened, but here is the story.
First, I tried to root the phone using the 1-click method, only to later realize that it does not work as the phone I had was running the latest OTA update. I wanted to reset my phone to factory default and I proceeded to do that.
Now, when my phone starts I see the small recovery menu and a lot of red letters stating that the system could not mount, find or open recovery directories, files or logs. (On the screen is this info Enter ok key,Select vol up/down Rebot system now, apply update from scard,wipe data/factory reset,wipe cache partition But nothing will move courser,then blow that in red is E:failed to open/res/recovery.fstab(no such file or directory) E:unknown volume for path[/cache/recovery/command with a lot more then in yellow letters #manual mode# and the same messages)
When I enter the download mode, and tried to use Odin or ADB, neither one can detect my device. I tried installing different samsung drivers on my system to no solution to being able to detect the device. Is this due to Windows not being able to initiate the drivers correctly, because when I connect the phone in Download mode, Windows has a pop-up show up that says "Drivers not recognized, your device might not work properly".
Does this mean the phone is bricked or is there something I can do to restore the phone?
Click to expand...
Click to collapse
did you try a different usb port? also I'd try heimdall and see if that works and sees your phone. which stock odin package are yup trying to flash?
I did manage to recover to the stock EH03 rom, by doing the first couple of steps in section 4 of the Guide for installing Rom (http://forum.xda-developers.com/showthread.php?t=1238070).
At this point, I cannot get root on my phone. I tried using 1 click root methods and those fail to install SU. I tried using the manual method of pushing rage.bin file using ADB, but that also failed.
I tried flashing some of the ROMs from section 4 of the above guide, but they cant seem to install on my phone. When I try to install through recovery, I get the picture of the android on the side and a failed install and either get stuck with the Samsung logo or a recovery boot loop.
Am I missing a step or something in order to root the phone or load a custom ROM? Is it possible that my phone cannot be rooted due to a lock somewhere?
Thanks.
Informatic_dev said:
I did manage to recover to the stock EH03 rom, by doing the first couple of steps in section 4 of the Guide for installing Rom (http://forum.xda-developers.com/showthread.php?t=1238070).
At this point, I cannot get root on my phone. I tried using 1 click root methods and those fail to install SU. I tried using the manual method of pushing rage.bin file using ADB, but that also failed.
I tried flashing some of the ROMs from section 4 of the above guide, but they cant seem to install on my phone. When I try to install through recovery, I get the picture of the android on the side and a failed install and either get stuck with the Samsung logo or a recovery boot loop.
Am I missing a step or something in order to root the phone or load a custom ROM? Is it possible that my phone cannot be rooted due to a lock somewhere?
Thanks.
Click to expand...
Click to collapse
You should have read a little but noe I'm going to tell you what to do head over to droid styles guide here http://forum.xda-developers.com/showthread.php?t=1238070 now download cwmfixedforcm7.zip and atlas 2.2.zip and put it on your computer now download this. http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip put it on the root of your SD card now power on your computer run Odin as AMINISTRATOR put the atlas.zip in the pit space in Odin check mark beside the place that said PDA and put the cwm.zip there now put your phone in download mode hook it to the computer and when Odin recognizes it press start wait for it to say PASS it may take up to 20min when its done reboot the while while holding the volume buttons, Home key button, power button when you see the Samsung logo flash twice let go of the volume up button and the home key button continue holding volume down button and the power button you should now boot into a menu with blue text now release the buttons navigate with the VOLUME BUTTONS AND THE POWER BUTTON TO SELECT go to install zip from SD now choose zip from SD navigate to the .zip I told you to put on your SD card select it then you will see a bunch of no's and a yes select yes AFTER its finished press go back then press reboot system now ONCE IT REBOOTS CONGRATS YOUR ROOTED AND SHOULD HAVE SUPERUSER!!!
Sent from my SCH-I500 using Tapatalk 2
I managed to get it working, maybe the SU.tar was corrupted as it worked this time. Thanks.
Hopefully someone can help me, my child has a Pendo Pad 7 Model no.PNDPP44QC7 with Kitkat 4.4 and it ended up with lots of malware/viruses and barely usable. This tablet only has a power button and no other buttons so I did not know how to boot into recovery mode to do factory reset and after trying reset through settings which made no difference so I gave the device ROOT access so I could try and delete the malware etc but of course i did not do any sort of backup and did not add CWM or TWRP recovery. I ended up deleting something wrong and now the device just hangs on the Pendo logo screen. I have since worked out how to boot into Recovery Mode and also Fastboot mode now but a bit too late I tried to do a wipe data/factory reset and this made no difference still hangs on Pendo logo.
I can't seem to find a CWM or TWRP image file to suit the tablet and possibly try putting tablet into fastboot mode and using ADB on computer and flash the recovery to tablet. ???
in recovery mode options i get are
apply update from ADB
apply update from sdcard
apply update from cache
wipe data/factory reset
wipe cache partition
backup user data
restore user data
but i can not seem to find any correct files to work with this tablet any help to get this tablet working again would be much appreciated Thanks
Good day! how did you manage to boot into Recovery Mode or Fast Mode?
After pressing the power button and seeing the display turn on. Keep spamming the power button and a menu will pop-up on screen with boot options. Short press of the power button cycles through the options, long press selects the option.
Mine was also stuck on a boot loop, even though I had not played around with any settings or tried to root etc. I was able to revive it by going into recovery mode and doing a factory reset.
Hey OP I've got hold of the same tablet I'm working on getting a rom dump atm. Bare with me I'll try and send a link for the img. If u can get into recovery mode where u can update zip. That's good if not try and via pc. Once u have a link to the tablets boatloader, rest is history.
Hi,
Wondering if I can follow up on this.
Mine is stuck on the PENDO boot screen, and I have tried the reset button, as well as the se commands PENDO suggested....
1. Press On/Off Switch (Power), wait for the Pendo Logo start up screen, and then press On/Off Switch (Power) twice right away.
2. Factory mode menu comes out after 10 seconds, two fingers touches panel together to move to select the one like the following picture shows (no need to understand the Chinese words, just follow through as what the picture shows)
3. Press On/Off Switch (Power) and the following picture below will show, press On/Off Switch (Power) again to proceed on Recovery Mode, and wait for system to restart.
Unfortunately, nothing still happens.
ADB will not reveal what device it is, nor will Win 10 recognise the device for it to show in Device Manager or connected devices.
Windows responds with a ding ding, but nothing shows up.
I am stuck, and any info gladly accepted.
Thanks
bump please
ozviewer said:
Hi,
Wondering if I can follow up on this.
Mine is stuck on the PENDO boot screen, and I have tried the reset button, as well as the se commands PENDO suggested....
1. Press On/Off Switch (Power), wait for the Pendo Logo start up screen, and then press On/Off Switch (Power) twice right away.
2. Factory mode menu comes out after 10 seconds, two fingers touches panel together to move to select the one like the following picture shows (no need to understand the Chinese words, just follow through as what the picture shows)
3. Press On/Off Switch (Power) and the following picture below will show, press On/Off Switch (Power) again to proceed on Recovery Mode, and wait for system to restart.
Unfortunately, nothing still happens.
ADB will not reveal what device it is, nor will Win 10 recognise the device for it to show in Device Manager or connected devices.
Windows responds with a ding ding, but nothing shows up.
I am stuck, and any info gladly accepted.
Thanks
Click to expand...
Click to collapse
not working in my pendotab window 8
Hi,
I could get no further with mine, the same as you.
I contacted Pendo Support, and explained it would work but not boot, I even asked for the image file so I could reload it in recovery mode, however, they did not have access to it, the Chinese manufacturer had not made it available to them.
As I described it was not damaged, but simply not working, they agreed to send me a replacement, even though it was out of warranty, as really, as I said to them, it was not fit for purpose.
I had to send the old one back, but they sent me a satchel in which to do so, at no cost to me.
They sent me the new one very promptly.
Hope is not lost,
Someone has finally manage to extract the factory ROM for the pendo PNDPP44QC7. Just search the model number on needrom.
phoenixemer.blogspot.com.au/2017/04/pendo-pad7-pndpp44qc7.html
password : emerlitspendotab7
TWRP custom recovery
drive.google.com/open?id=0B3k_2dFOmDBGRmljV3JuSUZiUkU
I tried to upgrade a similar device to 5.x, some changes, but some options now not working I have a clone Q88H device, A33 quadcore processor 7" clone. Kernel 3.4.39, firm ware 2.1 Need to go back to 4.4.2 w latest update. Hopefully Play store will work again, as I need it. That, or change to windows version. advice pls?
drusid said:
Hope is not lost,
Someone has finally manage to extract the factory ROM for the pendo PNDPP44QC7. Just search the model number on needrom.
phoenixemer.blogspot.com.au/2017/04/pendo-pad7-pndpp44qc7.html
password : emerlitspendotab7
TWRP custom recovery
drive.google.com/open?id=0B3k_2dFOmDBGRmljV3JuSUZiUkU
Click to expand...
Click to collapse
Please i dont have a needrom account i cant download plz who Can send me the direct link to m'y account
Hello everybody,
since saturday I have a really big problem. Until now I tried to find a similar problem from an other person in the internet in order to fix mine but that was not possible.
So in my last hope I am now writing it down here. Hopefully someone can help me:
The phone was/is rooted and has TWRP as recovery installed (v3.21). The software is still the original EMUI.
On saturday my Huawei Honor 5x (Model KIW-L21) gave me the notification that there is an software update avaible. So I backuped everything with TWRP to my sd-card and copied it to the computer. After this I ran th eupdate. The update downloaded the new software, then rebootet to the recovery, installed the update.zip automaticly and rebootet again. Then there was written on the screen "Huawei software installing ... DO NOT unplug usb or press any key!". Also there was "0%" all the time. It did nothing. also the phone was not connected with usb.
After an hour I long pressed the power button. after two seconds there was the text "Warning: The powerkey is long pressed, please release powerkey to avoid system crash" displayed. I pressed it longer and the phone turned off.
Now I have the following problem. When the phone is turned off, I can:
press the power button: the phone starts, the "honor ... android" logo is shown but nothing more happens. ("fastboot devices" -> no devices found, "adb devices" -> device found but no permission to enter commands)
press the power button and the volume up button and the volume down button at the same time: normally this should take me in the recovery mode, mut it doesn't anymore. Instead the "EMUI" update screen is shown (see above "huawei software installing ..." with "0%") ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
press the power button and the volume up button at the same time: I get a huawei menu with three buttons: "reboot", "wipe user cache" and "factory reset". I tried both (wipe and reset) wich both finished without an error. But nothing changes ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
press the power button and the volume down button at the same time: I get an "eRecovery" menu from huawei with three buttons: "Reboot", "power off" and "Recover with latest software". The last button lets me connect to my wifi and then "searching for packages", with failes all the time. ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
This problem occures with and also without the sd-card. Also there is no "update.zip" or "update.app" on the sd-card.
I really hope somebody can help me. I only need to get into the recovery. If I am there I can recover the backup or install a new ROM. That would be no problem for me. But at the moment I get nothing :crying:
Or maybe a tool to reset the phone completly? to start over from the beginning?
greetings,
Christopher
PS.: Thanks for your efford.
PSS.: Sorry for my bad english, I really try my best and hope that you understand what I am trying to say.
Same problem here... Please help us :'(
christopher2007 said:
Hello everybody,
since saturday I have a really big problem. Until now I tried to find a similar problem from an other person in the internet in order to fix mine but that was not possible.
So in my last hope I am now writing it down here. Hopefully someone can help me:
The phone was/is rooted and has TWRP as recovery installed (v3.21). The software is still the original EMUI.
On saturday my Huawei Honor 5x (Model KIW-L21) gave me the notification that there is an software update avaible. So I backuped everything with TWRP to my sd-card and copied it to the computer. After this I ran th eupdate. The update downloaded the new software, then rebootet to the recovery, installed the update.zip automaticly and rebootet again. Then there was written on the screen "Huawei software installing ... DO NOT unplug usb or press any key!". Also there was "0%" all the time. It did nothing. also the phone was not connected with usb.
After an hour I long pressed the power button. after two seconds there was the text "Warning: The powerkey is long pressed, please release powerkey to avoid system crash" displayed. I pressed it longer and the phone turned off.
Now I have the following problem. When the phone is turned off, I can:
press the power button: the phone starts, the "honor ... android" logo is shown but nothing more happens. ("fastboot devices" -> no devices found, "adb devices" -> device found but no permission to enter commands)
press the power button and the volume up button and the volume down button at the same time: normally this should take me in the recovery mode, mut it doesn't anymore. Instead the "EMUI" update screen is shown (see above "huawei software installing ..." with "0%") ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
press the power button and the volume up button at the same time: I get a huawei menu with three buttons: "reboot", "wipe user cache" and "factory reset". I tried both (wipe and reset) wich both finished without an error. But nothing changes ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
press the power button and the volume down button at the same time: I get an "eRecovery" menu from huawei with three buttons: "Reboot", "power off" and "Recover with latest software". The last button lets me connect to my wifi and then "searching for packages", with failes all the time. ("fastboot devices" -> no devices found, "adb devices" -> no devices found)
This problem occures with and also without the sd-card. Also there is no "update.zip" or "update.app" on the sd-card.
I really hope somebody can help me. I only need to get into the recovery. If I am there I can recover the backup or install a new ROM. That would be no problem for me. But at the moment I get nothing :crying:
Or maybe a tool to reset the phone completly? to start over from the beginning?
greetings,
Christopher
PS.: Thanks for your efford.
PSS.: Sorry for my bad english, I really try my best and hope that you understand what I am trying to say.
Click to expand...
Click to collapse
suzushima said:
Same problem here... Please help us :'(
Click to expand...
Click to collapse
to enter fastboot mode
1. Place the device in fastboot mode:
Turn off the device. (then wait for at least 2 seconds) For a mobile phone, press and hold the volume down and power keys simultaneously for at least 10 seconds (for a tablet, press and hold the volume up and power keys).
2. If the above operations do not switch the device to fastboot mode, please try the following steps:
Turn off the device. (then wait for at least 2 seconds) Then insert the USB cable and press and hold the volume down and power keys simultaneously for at least 10 seconds.
Step 2 worked for me every time
Arobase40 said:
AGAIN AND AGAIN, when you receive an update notification you MUST first flash back to stock recovery or it won't update with TWRP !!!
- To recover a stock recovery you need to boot onto download mode/your bootloader mode (Power+Volume Down) : plug your phone to your computer and type "fastboot flash recovery recovery.img".
From there you will loose your connexion with your computer. So unplug your phone and reboot manually holding down the Power button for some seconds.
If the system ever update your phone, BE VERY PATIENT !
The above note should probably part of a sticky !!!
If you don't get back to your Home screen and if you need TWRP back, reboot again onto download mode/your bootloader mode (Power+Volume Down) : plug your phone to your computer and type "fastboot flash recovery twrp.img" (or whatever the custom recovery name).
Click to expand...
Click to collapse
The problem a lot of people were having is TWRP flashed enough of the update that they lost custom recovery and had no way to get to the bootloader / fastboot ... that's why I posted the instructions above and in about 4 other threads.
Did you ever get your phone updated ?
Arobase40 said:
AGAIN AND AGAIN, when you receive an update notification you MUST first flash back to stock recovery or it won't update with TWRP !!!
Click to expand...
Click to collapse
I did not knew this one. Thanks a lot.
Thanks to @clsA I found the stock recovery here and I will try it:
https://www.androidfilehost.com/?w=files&flid=49383
clsA said:
1.Turn off the device. (then wait for at least 2 seconds) For a mobile phone, press and hold the volume down and power keys simultaneously for at least 10 seconds (for a tablet, press and hold the volume up and power keys).
2. If the above operations do not switch the device to fastboot mode, please try the following steps:
Turn off the device. (then wait for at least 2 seconds) Then insert the USB cable and press and hold the volume down and power keys simultaneously for at least 10 seconds.
Click to expand...
Click to collapse
Working great thanks a lot!
"fastboot & rescue mode" with a working usb connection.
What is the next step? If I now flash the stock recovery, does the phone manages to finish the system update?
Or should I flash the twrp recovery and not the stock revocery?
greetings,
Christopher
EDIT:
I flashed the stock recovery and also the twrp recovery. both times i startet the phone and hoped the installation of the new software will go on. But it didn't.
So my problem is still resistant. so what can I do? How do I stop the update from blocking my recovery? I do not need the update. maybe I can reset my device with the fastboot access somehow?
christopher2007 said:
I did not knew this one. Thanks a lot.
Thanks to @clsA I found the stock recovery here and I will try it:
https://www.androidfilehost.com/?w=files&flid=49383
Working great thanks a lot!
"fastboot & rescue mode" with a working usb connection.
What is the next step? If I now flash the stock recovery, does the phone manages to finish the system update?
Or should I flash the twrp recovery and not the stock revocery?
greetings,
Christopher
EDIT:
I flashed the stock recovery and also the twrp recovery. both times i startet the phone and hoped the installation of the new software will go on. But it didn't.
So my problem is still resistant. so what can I do? How do I stop the update from blocking my recovery? I do not need the update. maybe I can reset my device with the fastboot access somehow?
Click to expand...
Click to collapse
All the full updates are in the file depot
Use stock recovery plus the full update for your version.
You have to hold volup + voldown + power to start the update
Refresh TWRP / Root and your good to go
Sent from my KIW-L24 using Tapatalk
clsA said:
All the full updates are in the file depot
Use stock recovery plus the full update for your version.
You have to hold volup + voldown + power to start the update
Refresh TWRP / Root and your good to go
Click to expand...
Click to collapse
I found the stock recovery at https://www.androidfilehost.com/?w=files&flid=51004 but I have no idea what update I must use and how to use it.
Could you please give me a concrete link with a little introduction? Do I have to copy the update file to my sd-card? or do I have to use the "fastboot update *" command?
(Most of the files are for "KIW-L24" but I have a "KIW-L21" ... is there a significant difference? Od do I can use also the other files?)
Also, don't I have to stop the wrong update first?
greetings,
Christopher
EDIT:
I tried these "UPDATE.APP":
http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684
http://www.androidvillaz.com/2016/0...honor-5x-to-stock-lollipop-firmware-b130.html
both did not work. I copied them into the "dload" folder in the root of the sd-card and started the phone with volup+coldown+power.
The only thing the phone said was "Software install failed! ... Press powerkey to conrifm ... Shutdown system now".
christopher2007 said:
I found the stock recovery at https://www.androidfilehost.com/?w=files&flid=51004 but I have no idea what update I must use and how to use it.
Could you please give me a concrete link with a little introduction? Do I have to copy the update file to my sd-card? or do I have to use the "fastboot update *" command?
(Most of the files are for "KIW-L24" but I have a "KIW-L21" ... is there a significant difference? Od do I can use also the other files?)
Also, don't I have to stop the wrong update first?
greetings,
Christopher
EDIT:
I tried these "UPDATE.APP":
http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684
http://www.androidvillaz.com/2016/0...honor-5x-to-stock-lollipop-firmware-b130.html
both did not work. I copied them into the "dload" folder in the root of the sd-card and started the phone with volup+coldown+power.
The only thing the phone said was "Software install failed! ... Press powerkey to conrifm ... Shutdown system now".
Click to expand...
Click to collapse
if the update.app doesn't work you'll have to flash TWRP and the Stock Rom and wait like everyone else that's stuck trying to update the L21
clsA said:
if the update.app doesn't work you'll have to flash TWRP and the Stock Rom and wait like everyone else that's stuck trying to update the L21
Click to expand...
Click to collapse
The only way I know to flash a ROM, is to go over TWRP.
So I now did the following:
Phone power off
connect to pc
voldown+power
in the fastboot flash the recovery from twrp
shutdown
copy the "customromtemplate-5x-plk21-b130-r3.zip" to the sd-card
volup+coldown+power what normally starts twrp, but only the huawei update manager is shown
I only need twrp, no update and nothing else.
What options do I have left, because "flash a ROM" is not working ...
How can I stop this terrible update that is blocking my twrp?
greetings,
Christopher
christopher2007 said:
The only way I know to flash a ROM, is to go over TWRP.
So I now did the following:
Phone power off
connect to pc
voldown+power
in the fastboot flash the recovery from twrp
shutdown
copy the "customromtemplate-5x-plk21-b130-r3.zip" to the sd-card
volup+coldown+power what normally starts twrp, but only the huawei update manager is shown
I only need twrp, no update and nothing else.
What options do I have left, because "flash a ROM" is not working ...
greetings,
Christopher
Click to expand...
Click to collapse
are you flashing TWRP ?
you enter recovery with Volume up and Power
in TWRP you choose Install then choose customromtemplate-5x-plk21-b130-r3.zip
swipe to flash when it's done reboot
and your rom should load
clsA said:
are you flashing TWRP ?
you enter recovery with Volume up and Power
in TWRP you choose Install then choose customromtemplate-5x-plk21-b130-r3.zip
swipe to flash when it's done reboot
and your rom should load
Click to expand...
Click to collapse
I flashed TWRP using "kiwi_twrp_3-21_recovery.img". I also used this one last time (one month ago) and it worked then and also now.
Flashing was successful, but when I press volup+power I get a huawei menu.
At the top there is the "EMUI" circle and below there are three buttons:
Reboot system now
Wipe data/factory reset
Wipe cache partition
I can move around in this little menu by using the volume keys.
But this is not TWRP.
And normally I enter the recovery by using volup+voldown+power. But this is currently blocked by the update progress from huawei.
greetings,
Christopher
christopher2007 said:
I flashed TWRP using "kiwi_twrp_3-21_recovery.img". I also used this one last time (one month ago) and it worked then and also now.
Flashing was successful, but when I press volup+power I get a huawei menu.
At the top there is the "EMUI" circle and below there are three buttons:
Reboot system now
Wipe data/factory reset
Wipe cache partition
I can move around in this little menu by using the volume keys.
But this is not TWRP.
And normally I enter the recovery by using volup+voldown+power. But this is currently blocked by the update progress from huawei.
greetings,
Christopher
Click to expand...
Click to collapse
You still have stock recovery
Flash TWRP -
fastboot flash recovery kiwi_twrp_3-21_recovery.img
Do not reboot the phone
Hold power plus volup and TWRP should load.
Now flash your rom
Sent from my KIW-L24 using Tapatalk
clsA said:
You still have stock recovery
Flash TWRP -
fastboot flash recovery kiwi_twrp_3-21_recovery.img
Do not reboot the phone
Hold power plus volup and TWRP should load.
Now flash your rom
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
C:\adb>fastboot flash recovery kiwi_twrp_3-21_recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (45196 KB)...
OKAY [ 1.442s]
writing 'recovery'...
OKAY [ 0.703s]
finished. total time: 2.148s
I now flashed this more then ten times ... but with power+volup I still get the EMUI menu.
christopher2007 said:
C:\adb>fastboot flash recovery kiwi_twrp_3-21_recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (45196 KB)...
OKAY [ 1.442s]
writing 'recovery'...
OKAY [ 0.703s]
finished. total time: 2.148s
I now flashed this more then ten times ... but with power+volup I still get the EMUI menu.
Click to expand...
Click to collapse
Are you rebooting from the fastboot screen?
From the white boot loader screen hold volume up and power for 15 seconds
Sent from my KIW-L24 using Tapatalk
clsA said:
Are you rebooting from the fastboot screen?
From the white boot loader screen hold volume up and power for 15 seconds
Click to expand...
Click to collapse
The last six hours I tried to fix my phone ... again. One thing I did really helped a little:
Target1920 said:
http://forum.android.com.pl/topic/205126-instalacjaodzyskiwanie-systemu-rom-za-pomoca-fastboot/
This is the polish version of manual, I will write you how to do it:
1. Download ADB and Fastboot
2. Extract to c:/adb
3. Download from this thread firmware for you (extracted version!) http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684 If you have problem what firmware you have to install, take look at the back side of phone, at the down you will se KIW-L21 or 24 (or another). Copy all files to adb folder
4. Rund adb program
5. Write in the command line: cd c:/adb
6. Connect phone to usb to download mode (power and vol- combination)
7. Write in fastboot command: fastboot flash recovery recover.img (or recovrey .img, see the file and type it name) - wait for install
8. And now: If the flash is succesfull, reboot the phone to recovery (power and volume+) and wipe all data. Phone have to work.
But if flash is not succesfull, plug again usb with download mode
9. Write this commands: fastboot flash cust cust.img -wait for install
and: fastboot flash system system.img -also wait, system.img can took a while
10. Now you will enter recovery and wipe all data
11. Again plug usb cable and install firmware with those commands:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
With this I am not able to start my phone again. It will boot normally and I have a clean android. No userdata and no root.
So I now did the same like last month:
Unlock OEM -> not necessary, because it is already unlocked
install twrp with fastboot
reboot to twrp and there it is again
I did exactly what you said and also I did exactly the same thing I did last month but both times there is the same result: TWRP will not show up.
The "stock recovery" is blocking twrp in some sort of way. I can do whatever I whant ... volup+power out of the fastbook mode, or with "adb reboot recovery", or other ways ... twrp will not show up.
How is this possible? I also tried different twrp images. (The "kiwi_twrp_2-27_recovery.img" and "kiwi_twrp_3-21_recovery.img" out of your repository, and also the "twrp-3.0.0-0-kiwi.img" and "twrp-3.0.2-0-kiwi.img" from the twrp website itself ... always the same result: no twrp)
I am really at the end of my knollage
greetings,
Christopher
christopher2007 said:
The last six hours I tried to fix my phone ... again. One thing I did really helped a little:
With this I am not able to start my phone again. It will boot normally and I have a clean android. No userdata and no root.
So I now did the same like last month:
Unlock OEM -> not necessary, because it is already unlocked
install twrp with fastboot
reboot to twrp and there it is again
I did exactly what you said and also I did exactly the same thing I did last month but both times there is the same result: TWRP will not show up.
The "stock recovery" is blocking twrp in some sort of way. I can do whatever I whant ... volup+power out of the fastbook mode, or with "adb reboot recovery", or other ways ... twrp will not show up.
How is this possible? I also tried different twrp images. (The "kiwi_twrp_2-27_recovery.img" and "kiwi_twrp_3-21_recovery.img" out of your repository, and also the "twrp-3.0.0-0-kiwi.img" and "twrp-3.0.2-0-kiwi.img" from the twrp website itself ... always the same result: no twrp)
I am really at the end of my knollage
greetings,
Christopher
Click to expand...
Click to collapse
First off thanks for the very informative post.
Without actually having the phone in my hands I'm also stumped at what to try next.
After flashing TWRP and still in the boot loader unplug the USB before you reboot with power and volume up.
That's all I can think of right now
Sent from my KIW-L24 using Tapatalk
--
clsA said:
First off thanks for the very informative post.
Without actually having the phone in my hands I'm also stumped at what to try next.
After flashing TWRP and still in the boot loader unplug the USB before you reboot with power and volume up.
That's all I can think of right now
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
I must thank you for all your help
So I now read some more articles and tried some things. So there are old problems solved, but also new problems came up:
For me it is no longer possible to flash a recovery that is permanent. I have no idea why but I am ignoring it, because I can start the phone with voldown+power into bootloader and then use a usb-connection to enter the following command:
fastboot boot twrp-3.0.2-0-kiwi.img
Click to expand...
Click to collapse
So i can enter twrp temporary and because I do not need TWRP this often, that is ok for me.
BUT:
with the extracted "UPDATE.APP" and flashing some "*.img" files manually (see my last post), I have a more or less working "L21C432B130" version of android.
So now there is everything original (recovery, system, ...).
The update to "L21C432B140" is still not working. But that is also something I can live with.
So now I whant to restore my old system in order to have my old data/apps/... .
So I enter my temporary TWRP, go to Restore and select my old backup. Then the restore starts. Restoring EFS, Restoring efs2, Restoring Recovery, Wiping System and Formatting System using make_ext4fs. All of this in this order are successful. But the last operation "Restoring Data" failes with the following error message:
extractTarFork() process ended with error 255
Click to expand...
Click to collapse
So I searched on xda and found out, that this could be ANYTHING. I tried five or six different methods in order to fix it. In the end I am not sure what really fixxed it, but now I can restore my old update without any error. The phone now runs and I have all my old data.
There are four main differences on my phone to the time before I tried that damn update:
1. I have less internal storage
2. I have no TWRP permanently avaible
3. I can not Factory-Reset
4. I can not use a "UPDATE.APP" inside a "dload" folder on the sdcard
(the last two things always failes)
But as long as the android system now runs smooth again I can live with these things.
Is there maybe anything else I should be careful? maybe a known bug/problem that I have not seen yet?
The reason why I wanted to update in the first place was, that I have problems with my sd-card.
Some Apps do not allow to use the external storage. Easy Voice Recorder is the main problem. But also the Call Recorder has problems with it.
Is this a well known bug? Does a update helps? And if so, how do I update? (Now I know how to rescue my phone, so I could try it again xD )
Or does this problem gets solved with an custom ROM? If so, what good custom ROMs are out there for the honor 5x?
Or is this a problem that is not possible to fix on the honor 5x? Because these apps does not have this problem on my HTC One M9 ...
And thanks again so much for all your help
greetings,
Christopher
christopher2007 said:
I must thank you for all your help
So I now read some more articles and tried some things. So there are old problems solved, but also new problems came up:
For me it is no longer possible to flash a recovery that is permanent. I have no idea why but I am ignoring it, because I can start the phone with voldown+power into bootloader and then use a usb-connection to enter the following command:
So i can enter twrp temporary and because I do not need TWRP this often, that is ok for me.
BUT:
with the extracted "UPDATE.APP" and flashing some "*.img" files manually (see my last post), I have a more or less working "L21C432B130" version of android.
So now there is everything original (recovery, system, ...).
The update to "L21C432B140" is still not working. But that is also something I can live with.
So now I whant to restore my old system in order to have my old data/apps/... .
So I enter my temporary TWRP, go to Restore and select my old backup. Then the restore starts. Restoring EFS, Restoring efs2, Restoring Recovery, Wiping System and Formatting System using make_ext4fs. All of this in this order are successful. But the last operation "Restoring Data" failes with the following error message:
So I searched on xda and found out, that this could be ANYTHING. I tried five or six different methods in order to fix it. In the end I am not sure what really fixxed it, but now I can restore my old update without any error. The phone now runs and I have all my old data.
There are four main differences on my phone to the time before I tried that damn update:
1. I have less internal storage
2. I have no TWRP permanently avaible
3. I can not Factory-Reset
4. I can not use a "UPDATE.APP" inside a "dload" folder on the sdcard
(the last two things always failes)
But as long as the android system now runs smooth again I can live with these things.
Is there maybe anything else I should be careful? maybe a known bug/problem that I have not seen yet?
The reason why I wanted to update in the first place was, that I have problems with my sd-card.
Some Apps do not allow to use the external storage. Easy Voice Recorder is the main problem. But also the Call Recorder has problems with it.
Is this a well known bug? Does a update helps? And if so, how do I update? (Now I know how to rescue my phone, so I could try it again xD )
Or does this problem gets solved with an custom ROM? If so, what good custom ROMs are out there for the honor 5x?
Or is this a problem that is not possible to fix on the honor 5x? Because these apps does not have this problem on my HTC One M9 ...
And thanks again so much for all your help
greetings,
Christopher
Click to expand...
Click to collapse
from your current state you can try flash recovery with TWRP by choosing install / image / your version of TWRP / choose recovery / swipe to flash
Now choose reboot / recovery
As for the sdcard try the sdcard fix for kit Kat in the play store. It works for some older apps.
Sent from my KIW-L24 using Tapatalk
Arobase40 said:
If you mean getting my phone updated to KIW-L21 B140, no I still don't get it !
But I did try with KIW-L24 B151 with the result I already mentioned previously : almost bricked... ^^
But I always managed to get into Bootloader/Fastboot to flash back any kind of recovery...
Click to expand...
Click to collapse
clsA said:
All the full updates are in the file depot
Use stock recovery plus the full update for your version.
You have to hold volup + voldown + power to start the update
Refresh TWRP / Root and your good to go
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
So i have this issue too. im so stupid for doing this. I can go into fastboot mode and i flashed stock recovery and when i rebooted into recovery it still said that it was updating the firmware. I flashed twrp after that and it had the same message. am i doing something wrong or is it my phone? I tried rebooting into bootloader using adb but only fastboot will reconize my phone so adb also wont work. could you guys maybe help me?
Edit: Yessss. i got it using the temporary command. Thank you guys all for your help. it was so stupid of me to flash it with twrp still on it. Thank you all very much
So my tablet's model is Bluewave 8 HD + (Rockchip 33GT or something like that) and I decided to update my system through wireless update. So I downloaded it, and clicked update now. By that time I had 35% of battery left.
However, it says that it was an error. I think there were "Installation aborted" and "Error 7" and that stuff. It was on fastboot/recovery mode.
Now, I obviously couldn't select other options apart from reboot system now since my tablet doesn't have volume buttons. The buttons are on the screen. So my option is to reboot and go to the same process again— system update (Android is loading something like an object or stuff), error, and reboot.
I watched a video where clicking the reset button with the power button will move the selection down, so that it won't be reboot system now but it doesn't work for me. Whenever I do that (and as well as holding power and reset button {it is the little hole on the back where I need to poke it inside with a bent paperclip}, it just turns the screen off like a hard reset.
I can't also connect to a computer. Although my computer detects it as an "Android Phone and the Android Boot blah blah", software's doesn't detect the device.
I can't remove battery either because the back is inseparable.
Any fix? I really need to get it running well ASAP.
Thanks!
Ps: My tablet is Rooted.
halseynth said:
So my tablet's model is Bluewave 8 HD + (Rockchip 33GT or something like that) and I decided to update my system through wireless update. So I downloaded it, and clicked update now. By that time I had 35% of battery left.
However, it says that it was an error. I think there were "Installation aborted" and "Error 7" and that stuff. It was on fastboot/recovery mode.
Now, I obviously couldn't select other options apart from reboot system now since my tablet doesn't have volume buttons. The buttons are on the screen. So my option is to reboot and go to the same process againâ?? system update (Android is loading something like an object or stuff), error, and reboot.
I watched a video where clicking the reset button with the power button will move the selection down, so that it won't be reboot system now but it doesn't work for me. Whenever I do that (and as well as holding power and reset button {it is the little hole on the back where I need to poke it inside with a bent paperclip}, it just turns the screen off like a hard reset.
I can't also connect to a computer. Although my computer detects it as an "Android Phone and the Android Boot blah blah", software's doesn't detect the device.
I can't remove battery either because the back is inseparable.
Any fix? I really need to get it running well ASAP.
Thanks!
Ps: My tablet is Rooted.
Click to expand...
Click to collapse
Hey how did you enter recovery mode can you please tell me and are there custom recoveries available?
PS: you can scroll through the recovery mode by pressing the little button in the tiniest hole in your tablet so use a paper clip or something.
How to solve it problem, anyone have same?
homedist said:
How to solve it problem, anyone have same?
Click to expand...
Click to collapse
this guy can help you ...
homedist said:
How to solve it problem, anyone have same?
Click to expand...
Click to collapse
I think I had the same issue. After OTA update, device requested a reboot. But it never rebooted completely and I got a message like this:
Code:
Android Recovery
Nokia/Crystal_00ww/CTL_sprout
9/PPR1.180610.....
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Supported API:3
Boot Reason: enablefilecrypto_failed
I took the SIM card off, connected a USB cable and launched the command:
Code:
fastboot getvar current-slot
I got the result:
Code:
current-slot: b
So i set the current slot to a and rebooted the device:
Code:
fastboot set_active a
fastboot reboot bootloader
Then, in Download Mode I pressed and held Volume Up and Power Key together until I saw No Command screen. At this moment I pressed and held Power Key and pressed Volume Up key until I saw the recovery options:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_srpout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Supported API:3
Boot Reason: (null)
Take into account that you should be seeing version 10 and not 9 in this Android Recovery screen. Version 10 has the name: 10/QKQ1.190828.002/00WW_4_08B. If you are seeing version 9 you have to set the other slot as active with fastboot command.
Once in the recovery menu, I selected Apply update from ADB and uploaded the Android 10 update with adb command:
Code:
adb sideload 29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
After applying the update, the next reboot took a while but finally the device started and I had not to wipe the data.
Thanks to xda-developers.com and techmesto for instructions about Nokia 7.1 recovery mode
Thank you so much
After wasting a few days trying to sort it out, these instructions helped me finally. Thank you so much
ubywan said:
I think I had the same issue. After OTA update, device requested a reboot. But it never rebooted completely and I got a message like this:
Code:
Android Recovery
Nokia/Crystal_00ww/CTL_sprout
9/PPR1.180610.....
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Supported API:3
Boot Reason: enablefilecrypto_failed
I took the SIM card off, connected a USB cable and launched the command:
Code:
fastboot getvar current-slot
I got the result:
Code:
current-slot: b
So i set the current slot to a and rebooted the device:
Code:
fastboot set_active a
fastboot reboot bootloader
Then, in Download Mode I pressed and held Volume Up and Power Key together until I saw No Command screen. At this moment I pressed and held Power Key and pressed Volume Up key until I saw the recovery options:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_srpout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Supported API:3
Boot Reason: (null)
Take into account that you should be seeing version 10 and not 9 in this Android Recovery screen. Version 10 has the name: 10/QKQ1.190828.002/00WW_4_08B. If you are seeing version 9 you have to set the other slot as active with fastboot command.
Once in the recovery menu, I selected Apply update from ADB and uploaded the Android 10 update with adb command:
Code:
adb sideload 29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
After applying the update, the next reboot took a while but finally the device started and I had not to wipe the data.
Thanks to xda-developers.com and techmesto for instructions about Nokia 7.1 recovery mode
Click to expand...
Click to collapse
ubywan said:
I think I had the same issue. After OTA update, device requested a reboot. But it never rebooted completely and I got a message like this:
[...]
Then, in Download Mode I pressed and held Volume Up and Power Key together until I saw No Command screen. At this moment I pressed and held Power Key and pressed Volume Up key until I saw the recovery options:
Click to expand...
Click to collapse
I managed to get to the Download mode successfully but then I am stuck at the highlighted step - cannot enter to recover menu to do sideload. Can you explain exactly how you did that ? Pressed power, released , and then pressed volume up? Or pressed sequentially and then released together ? Or pressed sequentially and released sequentially?
I did perform factory data reset earlier, not sure if this is causing my issues. Or maybe I am doing the key combination wrongly from your instructions...
ubywan said:
I think I had the same issue. After OTA update, device requested a reboot. But it never rebooted completely and I got a message like this:
Code:
Android Recovery
Nokia/Crystal_00ww/CTL_sprout
9/PPR1.180610.....
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Supported API:3
Boot Reason: enablefilecrypto_failed
I took the SIM card off, connected a USB cable and launched the command:
Code:
fastboot getvar current-slot
I got the result:
Code:
current-slot: b
So i set the current slot to a and rebooted the device:
Code:
fastboot set_active a
fastboot reboot bootloader
Then, in Download Mode I pressed and held Volume Up and Power Key together until I saw No Command screen. At this moment I pressed and held Power Key and pressed Volume Up key until I saw the recovery options:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_srpout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Supported API:3
Boot Reason: (null)
Take into account that you should be seeing version 10 and not 9 in this Android Recovery screen. Version 10 has the name: 10/QKQ1.190828.002/00WW_4_08B. If you are seeing version 9 you have to set the other slot as active with fastboot command.
Once in the recovery menu, I selected Apply update from ADB and uploaded the Android 10 update with adb command:
Code:
adb sideload 29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
After applying the update, the next reboot took a while but finally the device started and I had not to wipe the data.
Thanks to xda-developers.com and techmesto for instructions about Nokia 7.1 recovery mode
Click to expand...
Click to collapse
To do the fastboot commands the phone should be turned off or on? And one question, I can't install the drivers which are in my phone https://imgur.com/a/5LOskR5 the setup doesn't open..
Piotr_M said:
I managed to get to the Download mode successfully but then I am stuck at the highlighted step - cannot enter to recover menu to do sideload. Can you explain exactly how you did that ? Pressed power, released , and then pressed volume up? Or pressed sequentially and then released together ? Or pressed sequentially and released sequentially?
Click to expand...
Click to collapse
Press both at the same time and don't release them until the "No command" screen appears. There will be a restart in-between screens.
JaggerJam said:
To do the fastboot commands the phone should be turned off or on? And one question, I can't install the drivers which are in my phone the setup doesn't open..
Click to expand...
Click to collapse
If the phone is turned off, run the command and turn the phone on. The command will wait until the device is available.
Regarding the drivers, I have tested these commands from a linux machine where it is not necessary to install drivers.
---------- Post added at 01:51 PM ---------- Previous post was at 01:17 PM ----------
After runinng a few days with Android 10 the 2019-12 patch update popped up. I installed and reboot the phone but I got a similar error when the phone upgraded from Android 9 to Android 10:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_sprout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If
you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this
device.
-----
Try again
Factory data reset
I tried the same instructions than I posted before without success, this time with the patch: 04dbc995492eb40f43593f984e723ec6a9b90f0f.zip from android.googleapis.com/packages/ota-api/nokia_ctlsprout_crystal00ww/. Anyway, a factory data reset works and the phone is running again. But if you don't disable "System Settings -> System -> Developer Options -> Automatic system updates" the patch keeps trying to install and then you have to reset your device.
I will wait until another patch will be released.
After applying the update and installing it with adb success state 0. I have rebooted the system now.
Still it is prompting me the same "Cannot load Android System"
Do i need to wipe the user data as well?
I have the same problem today after I tried to reboot.
So I went through this page
1) Downloaded the tools and adb file.
2) Connected the phone to computer and my PC detects it for a brief moment of about 1 to 2 seconds.
3) When I run the .\fastboot.exe getvar current-slot command, it waits for detecting the device but nothing happens. I select the "try again"option while the phone is connected to PC and the fastboot command still waiting for device but nothing happens.
Any idea of how to proceed further or did I miss anything?
Note: I didn't try factory reset yet. I'm hoping to recover my data. I have a lot of photos and videos that I don't want to loose.
Hello, thanks a lot!
I tried both slots a & b but I still see version 9 on top of the android recovery screen. So I ddon't dare going further an apply update from adb...
How can I update to Android Recovery
Nokia/Crystal_00WW/CTL_sprout
10/QKQ1.190828.002/00WW_4_08B ?
It keeps getting worse and worse : on slot B i'm always stuck in "Download mode" and slot A still android recovery version 9...
Anyone an idea?
Gagandeepskohli said:
After applying the update and installing it with adb success state 0. I have rebooted the system now.
Still it is prompting me the same "Cannot load Android System"
Do i need to wipe the user data as well?
Click to expand...
Click to collapse
I too have the same issue. adb ends with status 0 and am back to the bootloop as after restart.
ubywan said:
Press both at the same time and don't release them until the "No command" screen appears. There will be a restart in-between screens.
If the phone is turned off, run the command and turn the phone on. The command will wait until the device is available.
Regarding the drivers, I have tested these commands from a linux machine where it is not necessary to install drivers.
---------- Post added at 01:51 PM ---------- Previous post was at 01:17 PM ----------
After runinng a few days with Android 10 the 2019-12 patch update popped up. I installed and reboot the phone but I got a similar error when the phone upgraded from Android 9 to Android 10:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_sprout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If
you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this
device.
-----
Try again
Factory data reset
I tried the same instructions than I posted before without success, this time with the patch: 04dbc995492eb40f43593f984e723ec6a9b90f0f.zip from android.googleapis.com/packages/ota-api/nokia_ctlsprout_crystal00ww/. Anyway, a factory data reset works and the phone is running again. But if you don't disable "System Settings -> System -> Developer Options -> Automatic system updates" the patch keeps trying to install and then you have to reset your device.
I will wait until another patch will be released.
Click to expand...
Click to collapse
Same problem, I did the adb install for Android 10 and and as soon as the security patch gets updated, we are back to square 1 into the reset loop with each restart
still no google security january 2020 for nokia7.1 ?
Same here for my mother's phone, as soon as 01/2020 security update gets installed, phone gets stuck and need to reset. Had this three times now.
Disabled automatic updates now in developer options.
Please confirm if a fix was published or found.
ubywan said:
Press both at the same time and don't release them until the "No command" screen appears. There will be a restart in-between screens.
If the phone is turned off, run the command and turn the phone on. The command will wait until the device is available.
Regarding the drivers, I have tested these commands from a linux machine where it is not necessary to install drivers.
---------- Post added at 01:51 PM ---------- Previous post was at 01:17 PM ----------
After runinng a few days with Android 10 the 2019-12 patch update popped up. I installed and reboot the phone but I got a similar error when the phone upgraded from Android 9 to Android 10:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_sprout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If
you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this
device.
-----
Try again
Factory data reset
I tried the same instructions than I posted before without success, this time with the patch: 04dbc995492eb40f43593f984e723ec6a9b90f0f.zip from android.googleapis.com/packages/ota-api/nokia_ctlsprout_crystal00ww/. Anyway, a factory data reset works and the phone is running again. But if you don't disable "System Settings -> System -> Developer Options -> Automatic system updates" the patch keeps trying to install and then you have to reset your device.
I will wait until another patch will be released.
Click to expand...
Click to collapse
January security patch released.
i am getting an 'update package is older than the current build, expected a build newer than timestamp 1581332319 but package has timestamp 1573729404 and downgrade not allowed.'
i then tried the different zip file above and got 'package is for source build 00WW_4_08B but expected 00WW_4_08E.'
any ideas? i feel like i am so close to fixing this but just need the right update file!
knudsenda said:
i feel like i am so close to fixing this but just need the right update file!
Click to expand...
Click to collapse
No you are not! (Sorry to disappoint you, but I am in the same boat)
The instructions above are a bit outdated, the 04dbc995 file is 00WW_4_08B. There are other versions in https://forum.xda-developers.com/nokia-7-1/help/nokia-7-1-ota-update-ddls-t3866999/page9 for example d5c7c8ca7305ed19067b7e66b9b6525216161a90 is for version 00WW_4_08D, which was installed on my slot b.
But I could NOT find a file for 00WW_4_08E so I think we are stuck at the moment.
Greetings
I tried the file below and it says its for 00WW_4_08D! Anyone have the file for the 'E' version?
d5c7c8ca7305ed19067b7e66b9b6525216161a90.zip
same story here
I've got the same problem. Something in the Jan update screwed up my wife's phone. It will do the update fine, but on the next boot, it is stuck and you have to wipe the phone. I've tried doing the update with adb. It appears to load fine, but on the next boot, same story. Nokia only suggests sending it in, and of course we're of warranty. Doesn't look like anybody has a feb update that will work with my phone either(wrong version). Does anybody know if you can skip updates? Like apply the feb, but not the jan one? Thanks.
Somehow I got the January update to take hold. Here's what I think I did, although I rebooted so many times, I am not entirely certain if this is the exact sequence of events.
1. Applied update as you normally would. Phone gets in boot-loop and eventually ends with the "enablefilecrypto" error.
2. Proceeded with wiping phone, got to boot. Enabled developer options rebooted with adb to fastboot.
3. Phone was on slot a, changed to slot b.
4. Rebooted to recovery by holding power and up volume. Then power + up volume to start recovery.
5. Sideloaded feb update from the url provided in the updated download thread on this forum. I verified that this url is the same that my phone provides. Note that on previous attempts I had tried installing the jan update, but that never worked and it always reverted back to dec update after the mandatory wipe. Feb update appeared to work, although it threw an error about logs not existing.
6. Now I rebooted phone. Not totally sure, but i think it went into a boot-loop (flashing "android one" screen every 10 seconds or so for a while) but finally came up with the ecrypto message, with option to wipe or retry. I wiped and phone finally booted. Once it booted and I got through the initial setup, I found that Jan update has been applied but not Feb. This is weird, as I don't think I ever got Jan update successfully installed on either a or b. At this point if I try and install the updates through the normal method, it will not work and the final result will be the ecrypto error message or worse! So I have turned off updates for now.
I did get into a bootloop once where it would only boot to the bootloader screen and most normal methods would not get me out of it. I found that if changed the active slot with fastboot, it would then start flashing the "android one" screen a few times. While it's doing that if I held down volume up and power it would eventually get to the recovery screen. From here rebooting seemed to eventually work.
Anyhow what a cluster of a situation. Nokia doesn't offer much help but to send it in for $58. Not sure I want to waste any more time on this thing.