To begin, my phone is functioning and I am trying to install a custom recovery application CWM/TWRP. I just replaced the LCD and screen on my phone after not using it for a year. I THOUGHT I had TWRP installed, but after I factory reset (to start fresh) I tried to root my phone and noticed the recovery is stuck in manual mode.
I followed many online guides for assistance with using Odin3 to install the custom recovery, but every forum or instruction set tells you to go into "download mode" which isn't accessible from the manual version of recovery. Here are all the options I have:
Android system recover <3e>
KTU84P.M919UVUFOH3
Reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipre cache partition
apply update from cache
(Picture of droid with red triangle!)
# Manual Mode #
-- Applying Multi-CSC....
Applied the CSC-code : TMB
Successfully applied multi-CSC.
I am familiar with command line and if anyone has a suggestion for using CMD in windows to load a custom recovery, I'd REALLY appreciate it. So tired of KitKat!
That's just the stock recovery. You reach Download Mode via Power + Volume Down + Home and then Volume Up to continue.
es0tericcha0s said:
That's just the stock recovery. You reach Download Mode via Power + Volume Down + Home and then Volume Up to continue.
Click to expand...
Click to collapse
Thank you for the help! All the guides I saw said to use Vol Up to access download mode. I was able to successfully upgrade my S4 to use S6 software with 5.1.1! I'm very excited to have trusted devices and not have to enter my unlock code every 5 minutes!
I don't understand the idea of writing a guide and getting the most basic things wrong..? Glad all is well. ☺
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
Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J
Hey guys. I have the Huawei Ascend XT and I thought I was hard bricked and I started to mess around with some of the commands with Fastboot. I was able to get my phone back up and running. I am currently on the B180 but I am assuming it will work for any version between B140 and B180. What happened with me was I wiped my system partition but I had an unlocked bootloader. I could not get TWRP to boot up or I wasn't able to flash it because of the "FRP Lock", which is also known as Factory Reset Protection so a lot of commands were disabled such as "fastboot -w" to do a factory reset so I thought the worst case scenario.
1. Make sure you can access the "Rescue & Fastboot Mode" by holding down the Volume Down button and Power Button. Mine boot looped for a few screen flashes but it eventually booted into it.
2. Download the stock B140 recovery from here, post #7. (Special Thanks to clsA) https://forum.xda-developers.com/huawei-ascend-xt/help/stock-ascend-xt-recovery-t3572924
3. Assuming you have already downloaded the Minimal ADB and Fastboot files, open up a command prompt navigating to the fastboot folder and type in the following commands: "fastboot boot recovery.img"
4. After it boots, you can go ahead a do a factory reset via the recovery. It will be stuck on 99% and it wont go to 100%. Give the phone 5 minutes on 99% before doing anything. It gives it a chance to wipe everything completely.
5. Reboot your phone by holding the Volume Down and Power button until it boots into "Recovery & Fastboot Mode" and then flash TWRP as you like. As you can now see that "FRP Lock" disappeared thus allowing you to flash recoveries and use commands again.
It helped me so I hope it helps you out, saved me a lot of stress. Press thanks if this helped and feedback is always welcome.
Always been a great feature - can use fastboot to boot into any recovery, especially useful for testing if a new one works before flashing it. Fairly certain it's fully functional too, so you can do whatever changes you like or make backups without changing your stock recovery.
TheShwksFan86 said:
Hey guys. I have the Huawei Ascend XT and I thought I was hard bricked and I started to mess around with some of the commands with Fastboot. I was able to get my phone back up and running. I am currently on the B180 but I am assuming it will work for any version between B140 and B180. What happened with me was I wiped my system partition but I had an unlocked bootloader. I could not get TWRP to boot up or I wasn't able to flash it because of the "FRP Lock", which is also known as Factory Reset Protection so a lot of commands were disabled such as "fastboot -w" to do a factory reset so I thought the worst case scenario.
1. Make sure you can access the "Rescue & Fastboot Mode" by holding down the Volume Down button and Power Button. Mine boot looped for a few screen flashes but it eventually booted into it.
2. Download the stock B140 recovery from here, post #7. (Special Thanks to clsA) https://forum.xda-developers.com/huawei-ascend-xt/help/stock-ascend-xt-recovery-t3572924
3. Assuming you have already downloaded the Minimal ADB and Fastboot files, open up a command prompt navigating to the fastboot folder and type in the following commands: "fastboot boot recovery.img"
4. After it boots, you can go ahead a do a factory reset via the recovery. It will be stuck on 99% and it wont go to 100%. Give the phone 5 minutes on 99% before doing anything. It gives it a chance to wipe everything completely.
5. Reboot your phone by holding the Volume Down and Power button until it boots into "Recovery & Fastboot Mode" and then flash TWRP as you like. As you can now see that "FRP Lock" disappeared thus allowing you to flash recoveries and use commands again.
It helped me so I hope it helps you out, saved me a lot of stress. Press thanks if this helped and feedback is always welcome.
Click to expand...
Click to collapse
How were you able to flash the recovery in FRP Lock???
I've tested to flash on that mode and got the same error "Command Not Allowed"
How have you flashed the recovery??
What am i missing??
Thanks
RSGI said:
How were you able to flash the recovery in FRP Lock???
I've tested to flash on that mode and got the same error "Command Not Allowed"
How have you flashed the recovery??
What am i missing??
Thanks
Click to expand...
Click to collapse
Same
TheShwksFan86 said:
Hey guys. I have the Huawei Ascend XT and I thought I was hard bricked and I started to mess around with some of the commands with Fastboot. I was able to get my phone back up and running. I am currently on the B180 but I am assuming it will work for any version between B140 and B180. What happened with me was I wiped my system partition but I had an unlocked bootloader. I could not get TWRP to boot up or I wasn't able to flash it because of the "FRP Lock", which is also known as Factory Reset Protection so a lot of commands were disabled such as "fastboot -w" to do a factory reset so I thought the worst case scenario.
1. Make sure you can access the "Rescue & Fastboot Mode" by holding down the Volume Down button and Power Button. Mine boot looped for a few screen flashes but it eventually booted into it.
2. Download the stock B140 recovery from here, post #7. (Special Thanks to clsA) https://forum.xda-developers.com/huawei-ascend-xt/help/stock-ascend-xt-recovery-t3572924
3. Assuming you have already downloaded the Minimal ADB and Fastboot files, open up a command prompt navigating to the fastboot folder and type in the following commands: "fastboot boot recovery.img"
4. After it boots, you can go ahead a do a factory reset via the recovery. It will be stuck on 99% and it wont go to 100%. Give the phone 5 minutes on 99% before doing anything. It gives it a chance to wipe everything completely.
5. Reboot your phone by holding the Volume Down and Power button until it boots into "Recovery & Fastboot Mode" and then flash TWRP as you like. As you can now see that "FRP Lock" disappeared thus allowing you to flash recoveries and use commands again.
It helped me so I hope it helps you out, saved me a lot of stress. Press thanks if this helped and feedback is always welcome.
Click to expand...
Click to collapse
Yeah, it seemed like it was gonna work, got boot.img downloaded, but it sat there trying to boot for a half an hour with nada happening. Bummer.