Related
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
I've found a way to boot directly into bootloader/fastboot mode.
Press simultaniously the Vol+ and the power button until the red light lit up. Then instantly leave the two buttons and press the Vol- button until you see the fastboot menu. You're done!!
This trick to boot into Stock Bootloader/recovery has been known for years and is used on many different Android device
Still, it's great that you participate in this forum !
Boutchoo said:
This trick to boot into Stock Bootloader/recovery has been known for years and is used on many different Android device
Still, it's great that you participate in this forum !
Click to expand...
Click to collapse
I see you don't get it. Up to now the only way to get into fastboot was via "adb reboot bootloader". Or from a successfully installed TWRP.
The "for years" known combinations will get you only into Recovery (Power + Vol up), FTM (Power + Vol down), or into EDL respective the useless DFU mode (Power + Vol up + Vol down). In case you've killed your recovery and your bootimg you now have a additional option to come back to a functional system. Especially for the A2017g with the useless DFU mode.
Can anyone with bricked A2017G confirm?
Controllerboy said:
Can anyone with bricked A2017G confirm?
Click to expand...
Click to collapse
Confirmed NOT WORKING .
It doesn't matter if it's working or not. Thanks for the info anyway.
Neither stock recovery nor fastboot will help if you're stuck in DFU mode for G model. You can't do anything to recover the device in neither mode. All what helps is previously had enabled "allow BL unlock" in developer options. This gives you the possibilty to flash a stock ROM from external SD card. It still needs to be aproved from a bricked "DFU" user!
Stoicho87 said:
Confirmed NOT WORKING .
Click to expand...
Click to collapse
Would you kindly tell us what is not working? Don't you see the menu? Or don't you know what to do with fastboot?
In case you managed it to get into fastboot the next step would be to get into edl by using this trick. -->
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
@tron1, all this does not work. I tried cause I had a bricked (DFU) device. I needed to send it in for repair. And gues: they changed the motherboard.
Even the fastboot_edl results in "remote unknown command". Nearly all commands in fastboot for Axon 7 are disabled bei ZTE.
I will try if it's possible to reboot to edl with the fastboot from the unlock procedure from drakenfx.
forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
ZTE crippled the loader in a bad ass way. But they left the flash command inside. So it should be possible to flash at least a working recovery to the system if you manage it to get into bootloader. As long as my phone is working I won't try it on it. So volunteers!!
Hint -->
fastboot flash <partition> [ <filename> ] write a file to a flash partition
fastboot erase <partition> erase a flash partition
I there a way recover such a bricked device?
I could only boot into bootloader. If i choose boot recovery the phone only shows a red light.
If i choose start its the same red light.
Or should i contact ZTE for a new phone?
Stoicho87 said:
Confirmed NOT WORKING .
Click to expand...
Click to collapse
I have bricked my Axon 7 several times this weekend, but new Qualcomm chipsets are unbrickable!!!!
1. There is a way to enter directly to EDL on most Qualcomm devices and works also in the Axon 7. Just ensure your phone is off, then press the three buttons at the same time. The red light will blink once, after that blink release the three buttons (you must be very quick releasing the buttons, otherwise the phone will turn on.
2. Plug your phone to your computer. Windows 10 should detect a new USB device QUSB_BULK without any warning message. Then you can use axon7tool to flash the original boot and recovery (stock or tenfar's signed TWRP).
After that, you will be able to enter into recovery, do a factory reset and then you will be able to restore de initial image from an SD formatted as FAT32 (no, exFAT is not supported by stock recovery) in case of stock recovery. Sideload will not work, always stop before finishing the transmission.
Oki, this is fine for you because you have the US version of the Axon the rest of the axon World is f..ed up with an useless so called DFU mode. Happy Birthday for your Axon.
Sent from my ZTE A2017G using XDA Free mobile app
Oki said:
... unbrickable!!!! ...
... ress the three buttons at the same time. The red light will blink once, after that blink release the three buttons (you must be very quick releasing the buttons, o ...
... Then you can use axon7tool to flash the original boot and recovery (stock or tenfar's signed TW ...
Click to expand...
Click to collapse
That did the trick. Thanks
Any idea on why when i tried to enter bootloader mode on my Axon 7 (that i received 1 week ago), it stays on ZTE logo and nothing else happens... What is weirder is that there's a red light and my computer detect it when i do "fastboot devices" but i can't unlock the bootloader...
I tried to downgrade on B02 firmware and nothing... i'm beyond going insane right now.... :-/ It's like ZTE blocked on purpose the access to the bootloader mode...
Hi guys, any help would be much appreciated! I have studied all threads on XDA on bricked and boot loop'ed Honor 5X phones. I'm not a complete noob -- I have been flashing CM/LineageOS for years on Nexus 4, 5, 7, 9 and 6P, and this is the first time I have been stumped.
My KIW-L24 has an early version of LineageOS 14.1, and also TWRP 3.1.1-0 on it. I used the LineageOS updater to download a later LineageOS build, and initiated the update. As expected, the phone rebooted into TWRP, briefly showed the TWRP boot screen, but then after about 1 second, the phone reboots to the Honor boot screen for about 3 seconds, and then boots back to TWRP ... and so the cycle repeats endlessly between the two boot screens until the battery dies.
I cannot seem to get the device into bootloader/fastboot mode so that I can reflash TWRP and/or LineageOS or stock ROM. I have tried every combination of hardware keys to get the phone into fastboot (including Power+Vol Down). I tried initiating the download mode back to stock with the update.app placed in /dload/ on the sdcard (Power+Vol Down+Vol Up). I tried plugging in the PC-USB cable + Vol Down. While plugged into the PC via USB cable, I tried issuing "adb reboot bootloader" while the TWRP screen momentarily pops up (I literally have a less than a half-second when adb recognizes the phone). All without any success.
I am truly stuck! Any ideas? I have a practically brand new paperweight at the moment. :crying: Thanks very much in advance for any suggestions!
Are you sure battery isnt flat ?
You can use twrp as fas as i understand.. Correct me if i am wrong..
You can download stock rom twrp backup for your model from repository thread and try to restore backup with twrp..
Thanks, but I cannot 'use' TWRP! If I could, my problems would be easily solved, I have plenty of experience re-flashing ROMs, boot images, radios, etc.
Also, the battery is fine. At full charge, the phone powers up and immediately enters the endless boot cycle I previously described.
As soon as the phone shows the TWRP boot screen, the phone reboots again. I cannot do anything at all with TWRP. As I previously wrote, I have even tried using adb to force a reboot into fastboot while the TWRP boot screen shows for that split second (the PC momentarily recognizes the USB Android device). Unfortunately , TWRP reboots the phone too quickly.
pet_zeus said:
Thanks, but I cannot 'use' TWRP! If I could, my problems would be easily solved, I have plenty of experience re-flashing ROMs, boot images, radios, etc.
Also, the battery is fine. At full charge, the phone powers up and immediately enters the endless boot cycle I previously described.
As soon as the phone shows the TWRP boot screen, the phone reboots again. I cannot do anything at all with TWRP. As I previously wrote, I have even tried using adb to force a reboot into fastboot while the TWRP boot screen shows for that split second (the PC momentarily recognizes the USB Android device). Unfortunately , TWRP reboots the phone too quickly.
Click to expand...
Click to collapse
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
swukjay said:
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
Click to expand...
Click to collapse
If that doesnt work use e-recovery to restore phone and recovery to stock
---------- Post added at 03:07 PM ---------- Previous post was at 02:53 PM ----------
This may help https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
GOOD LUCK !
swukjay said:
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
If that doesnt work use e-recovery to restore phone and recovery to stock
Click to expand...
Click to collapse
Thanks, I just spent the another hour trying to enter Fastboot and eRecovery modes, and I must be missing something! At this point, no matter which button combination I press, I can't seem to affect the boot cycling of the phone (between TWRP and Honor boot screens).
Maybe relevant, but I am unable to even turn off the phone, it won't stop the alternating boot loop -- I don't believe in coincidences, but perhaps the power button just died? I had one Nexus 5 that started bootlooping because of the power button issue, but that was a very different behaviour than this -- the Honor deosn't get as far as booting to the OS.
GOOD LUCK !
Click to expand...
Click to collapse
Thank you, looks like I'll need some! Will update if I can figure out a way out...
pet_zeus said:
Thanks, I just spent the another hour trying to enter Fastboot and eRecovery modes, and I must be missing something! At this point, no matter which button combination I press, I can't seem to affect the boot cycling of the phone (between TWRP and Honor boot screens).
Maybe relevant, but I am unable to even turn off the phone, it won't stop the alternating boot loop -- I don't believe in coincidences, but perhaps the power button just died? I had one Nexus 5 that started bootlooping because of the power button issue, but that was a very different behaviour than this -- the Honor deosn't get as far as booting to the OS.
Thank you, looks like I'll need some! Will update if I can figure out a way out...
Click to expand...
Click to collapse
Sound to me like you flash Non VOLTE firmware on a Volte enabled modem thats causing the boot loop, the best course of action is to restore using e-recovery, that uses a separate recovery partition so hopefully wont boot loop, remember it may take a few times to boot and you must use a usb lead that is connected to a computer, a usb charger WILL NOT DO IT !
When it boots to e-recovery select download latest firmware, you will need to connect to wifi, just follow instructions and let it restore
pet_zeus said:
Thank you, looks like I'll need some! Will update if I can figure out a way out...
Click to expand...
Click to collapse
Erecovery should work, connect your USB to a computer and volume down + power
Another new user who posts when he has a problem and doesn't reply with an update as to what solution solved his problem, this constantly winds me up, new users who do this and dont update the thread should be kicked off
SOLVED!
Sorry for the delay of the update--I got busy and left my phone to collect dust for a while.
The ONLY solution that actually worked was to rip the phone apart and physically disconnect the battery ( !! ). Then, reconnecting the battery while holding down [Power] and [Vol -] got me into fastboot recovery, as per instructions in this thread (I had to avoid booting normally, or into recovery -- TWRP -- since either would put the phone back into the bootloop):
https://forum.xda-developers.com/honor-5x/how-to/guide-entering-fastboot-using-key-t3400869
After that, it was smooth sailing; I was able to kill TWRP by flashing RECOVERY.img that I extracted from stock B140 image (using Huawei extractor https://forum.xda-developers.com/showthread.php?t=2433454), then force-update to stock B331, then latest TWRP and LineageOS. One hiccup: for whatever reason, I needed to do a factory reset/wipe in TWRP before it would flash LineageOS without giving error 7, despite the fact that I had just flashed the stock image.
Thank you all for your help and input!
I tried to install LineageOS, but after some steps the phone died out of nowhere, now the power button doesnt turn on the phone and I cant access to recovery or fastboot either.
What I did was:
Unlocking bootloader
Going to fastboot
fastboot flash boot LineageRecovery.img
fastboot boot LineageRecovery.img
It didn't went to the lineage recovery and was stuck on fastboot mode, couldn't go to another mode
Tried TWRP
fastboot flash boot TWRPRecovery.img
fastboot boot TWRPRecovery.img
This time it went to TWRP recovery mode (yay)
Tried to adb sideload Lineage rom
Stopped at 40-50% out of nowhere
Tried to factory reset and other stuff, it said some stuff was missing (maybe data or other stuff, I cant remember)
Then I rebooted to system, and it was at that time where everything went blank
Now holding the power button doesnt turn on the phone, neither does holding power button and volume up/down
When the phone is plugged to the PC and I hold the power button + volume up/down the pc makes a sound like I disconnected and connected something, but it doesnt do anything.
Sorry if my english is not the best but please I need help, thank you.
josilher said:
I tried to install LineageOS, but after some steps the phone died out of nowhere, now the power button doesnt turn on the phone and I cant access to recovery or fastboot either.
What I did was:
Unlocking bootloader
Going to fastboot
fastboot flash boot LineageRecovery.img
fastboot boot LineageRecovery.img
It didn't went to the lineage recovery and was stuck on fastboot mode, couldn't go to another mode
Tried TWRP
fastboot flash boot TWRPRecovery.img
fastboot boot TWRPRecovery.img
This time it went to TWRP recovery mode (yay)
Tried to adb sideload Lineage rom
Stopped at 40-50% out of nowhere
Tried to factory reset and other stuff, it said some stuff was missing (maybe data or other stuff, I cant remember)
Then I rebooted to system, and it was at that time where everything went blank
Now holding the power button doesnt turn on the phone, neither does holding power button and volume up/down
When the phone is plugged to the PC and I hold the power button + volume up/down the pc makes a sound like I disconnected and connected something, but it doesnt do anything.
Sorry if my english is not the best but please I need help, thank you.
Click to expand...
Click to collapse
Flashing dtbo.img + vendor_boot.img + boot.img is essential. With custom rom, boot.img will include recovery loss inside.
Aitra said:
Flashing dtbo.img + vendor_boot.img + boot.img is essential. With custom rom, boot.img will include recovery loss inside.
Click to expand...
Click to collapse
I see, but know that my phone is bricked or whatever state it is what do I do
Flash boot_ab boot.img
Flash vendor_boot_ab vendor_boot.img
Flash dtbo dtbo.img
Fastboot reboot recovery
josilher said:
I see, but know that my phone is bricked or whatever state it is what do I do
Click to expand...
Click to collapse
Fastboot -w
josilher said:
I see, but know that my phone is bricked or whatever state it is what do I do
Click to expand...
Click to collapse
To load the original rom, you need to reload the original dtbo.img & vendor_boot.img.
Aitra said:
To load the original rom, you need to reload the original dtbo.img & vendor_boot.img.
Click to expand...
Click to collapse
It's on EDL mode apparently, can I do that on this mode?
No! If in edl mode auth authorized account is required.
After a while using custom rom RIceDroi 8.5 I have returned to Miui14.
Aitra said:
No! If in edl mode auth authorized account is required.
Click to expand...
Click to collapse
Well I don't have an authorized account but I'm 90% sure it is on EDL mode because my pc detects it as Qualcomm QDBLoader so what am I suppose to do. Btw thanks for the fast replying
josilher said:
Well I don't have an authorized account but I'm 90% sure it is on EDL mode because my pc detects it as Qualcomm QDBLoader so what am I suppose to do. Btw thanks for the fast replying
Click to expand...
Click to collapse
Up rom without an authorized account can still be successful if it is not locked alti ronback.
Aitra said:
Up rom without an authorized account can still be successful if it is not locked alti ronback.
Click to expand...
Click to collapse
Can you elaborate further?
I ended up paying to have my phone saved from EDL mode, now it's working
I wanted to install basic android 13 on my 10T but accidentally forgot to remove the old vbmeta and put in the new one so it was kinda a mix of lineage's vbmeta (i tried to go from lineage os to android) and android's system and boot image files. It was bootlooping, then i figured out how to go into bootloader and i flashed half of the files with OOS 12.1 fastboot rom, then i powered it off to try to go into fastbootd mode and it didn't turn on, i tried holding the power and volume buttons in every single way possible but nothing worked. Can someone help me with what i can do to at least turn it back on and go into bootloader? I'm really desperate at this point, im ready to clear every single bit of data just to restore the phone, if it is possible of course.
Wembbu said:
I wanted to install basic android 13 on my 10T but accidentally forgot to remove the old vbmeta and put in the new one so it was kinda a mix of lineage's vbmeta (i tried to go from lineage os to android) and android's system and boot image files. It was bootlooping, then i figured out how to go into bootloader and i flashed half of the files with OOS 12.1 fastboot rom, then i powered it off to try to go into fastbootd mode and it didn't turn on, i tried holding the power and volume buttons in every single way possible but nothing worked. Can someone help me with what i can do to at least turn it back on and go into bootloader? I'm really desperate at this point, im ready to clear every single bit of data just to restore the phone, if it is possible of course.
Click to expand...
Click to collapse
If you connect the phone to the computer, is it recognised in some way in the Device Manager (perhaps in EDL mode)?
TheNewHEROBRINE said:
If you connect the phone to the computer, is it recognised in some way in the Device Manager (perhaps in EDL mode)?
Click to expand...
Click to collapse
nope, if it was i would've restored it already. Used to be recognized as a fastboot device when i could boot into bootloader but now it's just a permanently turned off brick.
Wembbu said:
nope, if it was i would've restored it already. Used to be recognized as a fastboot device when i could boot into bootloader but now it's just a permanently turned off brick.
Click to expand...
Click to collapse
When you can boot to fastboot/fastbootd than flash the stock rom to both slots with fbe and delete all.cow partition
Yeah uh well how can I get it to boot anywhere at all? It doesn't respond to any combination of power and volume buttons. I even calculated how many there are: 4×2=8 and none worked, computer as I said earlier doesn't see it as any device since it's turned off.
Wembbu said:
Yeah uh well how can I get it to boot anywhere at all? It doesn't respond to any combination of power and volume buttons. I even calculated how many there are: 4×2=8 and none worked, computer as I said earlier doesn't see it as any device since it's turned off.
Click to expand...
Click to collapse
Also just as an addition to my previous messages a wanna mention that it was originally a Chinese Ace Pro model which was idk how remade to think that it is 10T which could lead to some issues with restoring it idk.
Unfortunately if it's completely dead you have only one option to contact oneplus directly