Database Develop

[Q] Fastboot boot openrecovery hung my phone. Any hope?

I was trying to update recovery and I typed the wrong commands in fastboot.
Instead of
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
I typed:
Code:
fastboot boot recovery openrecovery-twrp-2.6.3.3-m7.img
When that failed because "recovery" didn't exist I still didn't notice my mistake, and went with:
Code:
fastboot boot openrecovery-twrp-2.6.3.3-m7.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.232s]
booting...
OKAY [ 0.003s]
finished. total time: 0.240s
Since then my phone pretty much stopped working. The screen is on, but is hung - the power buttons and volume buttons do nothing. Here are some commands I tried
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.588s
-------------------------------
fastboot devices
HT35CW91**** fastboot
-----------------
fastboot reboot-bootloader
rebooting into bootloader...
Even the reboot just hung there with no change in the device. Is it a paperweight now or is there a way back? Obviously I can't remove the battery and I've not unplugged the USB cable just in case

Teefee said:
I was trying to update recovery and I typed the wrong commands in fastboot.
Instead of
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
I typed:
Code:
fastboot boot recovery openrecovery-twrp-2.6.3.3-m7.img
When that failed because "recovery" didn't exist I still didn't notice my mistake, and went with:
Code:
fastboot boot openrecovery-twrp-2.6.3.3-m7.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.232s]
booting...
OKAY [ 0.003s]
finished. total time: 0.240s
Since then my phone pretty much stopped working. The screen is on, but is hung - the power buttons and volume buttons do nothing. Here are some commands I tried
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.588s
-------------------------------
fastboot devices
HT35CW91**** fastboot
-----------------
fastboot reboot-bootloader
rebooting into bootloader...
Even the reboot just hung there with no change in the device. Is it a paperweight now or is there a way back? Obviously I can't remove the battery and I've not unplugged the USB cable just in case
Click to expand...
Click to collapse
fastboot boot <name of recovery>.img no longer works; it only works on hboot 1.44
just reboot using POWER + VOLDOWN the flash recovery.

nkk71 said:
fastboot boot <name of recovery>.img no longer works; it only works on hboot 1.44
just reboot using POWER + VOLDOWN the flash recovery.
Click to expand...
Click to collapse
Thanks for the response. The phone doesn't respond to any button presses, so I can't VOLDOWN to Power Down. I have tried holding VOLDOWN + POWER like you said but the screen is still on and the phone hasn't done anything

Teefee said:
Thanks for the response. The phone doesn't respond to any button presses, so I can't VOLDOWN to Power Down. I have tried holding VOLDOWN + POWER like you said but the screen is still on and the phone hasn't done anything
Click to expand...
Click to collapse
no i meant press and hold POWER + VOLDOWN buttons (preferably under a bright light), then when it reboots, let go of POWER, but keep holding VOLDOWN and you're back in bootloader.
also it's safe to unplug it. once you do, bootloader may actually respond to normal presses again.

nkk71 said:
no i meant press and hold POWER + VOLDOWN buttons (preferably under a bright light), then when it reboots, let go of POWER, but keep holding VOLDOWN and you're back in bootloader.
also it's safe to unplug it. once you do, bootloader may actually respond to normal presses again.
Click to expand...
Click to collapse
Thanks very much, you're a lifesaver! When I unplugged the device the screen still didn't respond but pressing & holding POWER+VOLDOWN for ~10 seconds rebooted the phone and I'm back in business.

Teefee said:
Thanks for the response. The phone doesn't respond to any button presses, so I can't VOLDOWN to Power Down. I have tried holding VOLDOWN + POWER like you said but the screen is still on and the phone hasn't done anything
Click to expand...
Click to collapse
actually just tried, once unplugged bootloader still "hung", had to use the POWER + VOLDOWN as mentioned above to go to bootloader again

unable to flash recovery on CRR-UL00

Hi all - I'm not entirely stupid, but I'm probably doing something basically wrong here.
I'm trying to convert my Chinese CRR-UL00 to something a bit more western, but still with dual SIMs, so converting it to Middle East/Africa model seems like a good idea. I'm not interested in root or even a custom recovery in the long term. I just want to change regions.
I have been trying to follow the instructions both here and elsewhere but am getting stuck early in the process. I've tried a bunch of different things so my phone may be in an odd state.
I have, I believe, unlocked the bootloader via DC-Unlocker. When I reboot into the bootloader (using adb reboot bootloader) I get a white screen with a header that says "Fastboot&Rescue mode", an Android icon, and "Phone Unlocked" in red underneath.
Attempting to flash a TWRP recovery.img using fastboot doesn't seem to have any effect, even though fastboot reports it has successfully transferred the image. Trying to boot into recovery - either using adb/fastboot or vol+/power keys results in the phone hanging at the Huawei logo at bootup. I've also tried to flash back a "stock" recovery.img. At no time have I been able to get the fastboot menu on the phone - it's either the white screen with no options, or the phone hanging at the Huawei logo.
Despite all this the phone will still operate normally! When operating normally the phone now reports its running CRR-UL00C00B172.
Any ideas what I'm doing wrong? What recovery.img should I use?
Thanks for any help!
WD

I'm not home right now but from memory the one I've used was named somthing like TWRP-2.8.7.0-Carrera.img

Thank you for the quick reply. I've had some time to have another go at this. Still can't seem to get TWRP recovery onto the phone...
It seems to flash...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24454 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.242s]
finished. total time: 0.787s
but then rebooting and holding down various keys to get into Recovery, I either get a hang at the Huawei logo, or I eventually end up back at the stock recovery. (I think if it boots to the full OS it overwrites any TWRP recovery)
What is the actual key combo to get into recovery? Various web pages report different combos:
- vol+ and vol- and power
- vol+ and power
- ?? something else
Many thanks,
wd

wonky donkey said:
Thank you for the quick reply. I've had some time to have another go at this. Still can't seem to get TWRP recovery onto the phone...
It seems to flash...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24454 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.242s]
finished. total time: 0.787s
but then rebooting and holding down various keys to get into Recovery, I either get a hang at the Huawei logo, or I eventually end up back at the stock recovery. (I think if it boots to the full OS it overwrites any TWRP recovery)
What is the actual key combo to get into recovery? Various web pages report different combos:
- vol+ and vol- and power
- vol+ and power
- ?? something else
Many thanks,
wd
Click to expand...
Click to collapse
- flash stock recovery
- boot device normaly
- go into developersettings and look for OEM-Unlock
- if available, enable it. if not go to fastboot mode and use "OEM-Unlock" command with code again. (sometimes the bootloader isn´t unlocked fully on first try)
- then try to flash TWRP 2.8.7.0
- fastboot reboot
anyway whats your current build?
i can only access recovery via. "adb reboot recovery" command

Thanks for the help. Clearly I'm doing something wrong.
On rebooting normally after flashing recovery I don't see an OEM-unlock option in Developer Options. Attempting to fastboot oem unlock again gives me failed, already unlocked.
I've tried four different downloads of TWRP recovery from different places, I've even tried different adb/fastboot binaries to make sure that's not the issue. The TWRP recovery images I have are:
25,040,896 bytes (three different downloads, and I've seen one or two sites that claim this is only for the L09 version)
25,378,816 bytes (from a random Chinese web site that says its for the CRR-UL00 B131)
I'm on CRR-UL00C00B172. I wonder if I need to flash everything back to something earlier? (e.g. I have a full download of UL00C00B153).
wd

OK, success!
At some point I ended up in stock recovery and it suggested to download and install UL00C00B131. (why B131? Maybe because at some point I had been using the Chinese download with B131 on it?). Did so.
adb reboot bootloader
relock and unlock to confirm unlock is definitely working in fastboot
fastboot reboot
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
adb reboot recovery
...now I'm into TWRP!
Thanks all for your help.
wd

...and now I've got it localised to MEAFNAF (C433) - so still dual SIM but with Google Play by default etc. Running CRR00-UL00C433B146 which is available from Huawei.
I followed these instructions. (based on the original Russian post but much better than Google Translate
At the end, the install of update.app hung at 90%. Using vol+/power to get into recovery dropped me into a Chinese recovery (probably from the recovery.img I flashed back to remove TWRP). Factory resetting from recovery resulted in booting to the full OS, but I didn't get the option to enter a Google ID in setup and the full OS was dog slow with a black home screen.
Doing another factory reset, I was then asked for a Google ID during setup, and this time resulted in a fully functioning Googley OS.
I understand I won't get OTA updates as I've changed my localization, so I'll keep an eye out for the final Marshmallow release from Huawei's web site.
I hope this thread is useful to others.
wd

I need Help PLZ

So this is my problem
i tried to install Xposed installer and ****ed up
at the end i wiped everything on my phone using twrp
and then (like a total idiot) i flasht the wrong boot.img and recovery.img
my phone now only can boot into rescue mode ( which is useless) and fastboot mode
NOW THE BIGGEST PROBLEM
i cant falsh anything using fastboot and i tried every driver i could find
apperently it must be a special fastboot 2.0 driver
thast btw the same ways my device is listet in device manager in windows 7
PLZZZZZZZ Help

ladres said:
So this is my problem
i tried to install Xposed installer and ****ed up
at the end i wiped everything on my phone using twrp
and then (like a total idiot) i flasht the wrong boot.img and recovery.img
my phone now only can boot into rescue mode ( which is useless) and fastboot mode
NOW THE BIGGEST PROBLEM
i cant falsh anything using fastboot and i tried every driver i could find
apperently it must be a special fastboot 2.0 driver
thast btw the same ways my device is listet in device manager in windows 7
PLZZZZZZZ Help
Click to expand...
Click to collapse
normaly i would say "you fu***** it up because you didn´t read the other threads before you do some random s***" but i´m not going to write it today.
There are no special drivers for fastboot. the "Minimal ADB & Fastboot" package has everything needed.
If you phone isn´t recognized as android device:
- delete the drivers in the device-manager from windows. (Sometimes a restart solve problems)
- disconnect your phone from the computer first.
- boot your phone into fastboot mode.
- reconnect it.
then you should be able to flash via fastboot.
If fastboot shows something like "command not allowed", your device is probably FRP locked right now.

Tuerkay said:
normaly i would say "you fu***** it up because you didn´t read the other threads before you do some random s***" but i´m not going to write it today.
There are no special drivers for fastboot. the "Minimal ADB & Fastboot" package has everything needed.
If you phone isn´t recognized as android device:
- delete the drivers in the device-manager from windows. (Sometimes a restart solve problems)
- disconnect your phone from the computer first.
- boot your phone into fastboot mode.
- reconnect it.
then you should be able to flash via fastboot.
If fastboot shows something like "command not allowed", your device is probably FRP locked right now.
Click to expand...
Click to collapse
well the FRP locked is absolutly true do you know how i can unlock it ?
btw when i uninstall the fastboot driver for my phone and reconnect it only says
driver not found
thx for replay

ladres said:
well the FRP locked is absolutly true do you know how i can unlock it ?
btw when i uninstall the fastboot driver for my phone and reconnect it only says
driver not found
thx for replay
Click to expand...
Click to collapse
you have to search the drivers manualy. path should be minimal adb folder.
the frp unlock can be removed vie developer settings but you can´t access them.
which boot.img and recovery.img did you flash? if it´s from a mate s rom, then it shouldn´t affect your phone.
you could also try something else. take a micro sd card. place the dload folder with your current update.app in it. then boot your phone with vol+ (or vol + and vol-) and power. it then should do an force update.

Tuerkay said:
you have to search the drivers manualy. path should be minimal adb folder.
the frp unlock can be removed vie developer settings but you can´t access them.
which boot.img and recovery.img did you flash? if it´s from a mate s rom, then it shouldn´t affect your phone.
you could also try something else. take a micro sd card. place the dload folder with your current update.app in it. then boot your phone with vol+ (or vol + and vol-) and power. it then should do an force update.
Click to expand...
Click to collapse
I have a CRR L09
I restored everything using a twrp backup from a CRR L00 version
and since i wante to keep my hand off root and everything i decidet to falsh the boot.img and recovery.img
that i extracted from an original UPDATE.APP
i did that all with falshify
btw it seems that i have the right fastboot driver but fastboot wont let me falsh
eaven tho i falshed befor without FRP Unlock
and just so you know
i have sam os x and windows 7 and both give me the same error
lols-Mac-Pro:~ lol$ fastboot devices
UBE0215923001497 fastboot
lols-Mac-Pro:~ lol$ fastboot flash recovery /Users/lol/Desktop/recovery-B303.img
target reported max download size of 471859200 bytes
sending 'recovery' (28226 KB)...
OKAY [ 0.596s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.596s
lols-Mac-Pro:~ lol$

ladres said:
I have a CRR L09
I restored everything using a twrp backup from a CRR L00 version
and since i wante to keep my hand off root and everything i decidet to falsh the boot.img and recovery.img
that i extracted from an original UPDATE.APP
i did that all with falshify
btw it seems that i have the right fastboot driver but fastboot wont let me falsh
eaven tho i falshed befor without FRP Unlock
and just so you know
i have sam os x and windows 7 and both give me the same error
lols-Mac-Pro:~ lol$ fastboot devices
UBE0215923001497 fastboot
lols-Mac-Pro:~ lol$ fastboot flash recovery /Users/lol/Desktop/recovery-B303.img
target reported max download size of 471859200 bytes
sending 'recovery' (28226 KB)...
OKAY [ 0.596s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.596s
lols-Mac-Pro:~ lol$
Click to expand...
Click to collapse
well... i already wrote it in other threads that using an twrp backup, which is not yours can FRP lock you device. since you can´t boot your device, you also can´t remove the FRP lock. with the FRP Lock you can´t flash any files.
so you need an uncorrupted TWRP backup from someone with the same mate s model you have.
if you´re on stock recovery, try what i wrote the last post. Place dload folder with the Update.app for you model on an sd card and boot into update mode with VOL+ (and VOL- depending on the recovery version) and Power button at the same time.

Tuerkay said:
well... i already wrote it in other threads that using an twrp backup, which is not yours can FRP lock you device. since you can´t boot your device, you also can´t remove the FRP lock. with the FRP Lock you can´t flash any files.
so you need an uncorrupted TWRP backup from someone with the same mate s model you have.
if you´re on stock recovery, try what i wrote the last post. Place dload folder with the Update.app for you model on an sd card and boot into update mode with VOL+ (and VOL- depending on the recovery version) and Power button at the same time.
Click to expand...
Click to collapse
no the werid thin is
when i restored the twrp backup it actually booted thats when i tried to falsh the stock recovery and boot image
and i already tried with the hardware buttons
Vol+ gets me to Huawei eRecovery (tries to download firmware over wifi but failes)
Vol- gets me to fastboot mode
and btw that only works when i turn the phone off and hold the button and connect the usb cable
without the cable i automaticly get into rescue mode
with eiter
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed!)
or
Error!
Func NO : 11 (boot image)
Error NO : 2 (load failed!)

You have Ton press vol+ and vol- and power button all at the same time with the cable Unplugged. If you have an Update.App on your SD Card it will automatically Start the process without asking any questions.

Tuerkay said:
You have Ton press vol+ and vol- and power button all at the same time with the cable Unplugged. If you have an Update.App on your SD Card it will automatically Start the process without asking any questions.
Click to expand...
Click to collapse
i already tried that it only takes me to rescue mode

ladres said:
i already tried that it only takes me to rescue mode
Click to expand...
Click to collapse
with how much % does it fail and which reason does it show?

Tuerkay said:
with how much % does it fail and which reason does it show?
Click to expand...
Click to collapse
i get eiter
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed!)
or
Error!
Func NO : 11 (boot image)
Error NO : 2 (load failed!)
an thats it

can you make a photo of the screen this message appears?
it looks like you haven´t done what i have said since these aren´t messages which appear in the update mode.

Here you go
Sent from my HTC One using XDA Free mobile app

ladres said:
Here you go
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
well i don´t know where to start. just give an short explanation about the Huawei Recovery system.
The Huawei Mate S hast 2 ("TWO") recoverys installed. Recovery.img and Recovery2.img. just for safety reason if someone or something f***s up the primary recovery.img (first recovery). the first one is also the one you normaly swap with the TWRP backup.
The Huawei Mate S can be booted in 4 ("four") different modes
1. normal boot into android
2. boot into fastboot&rescue mode
3. boot into reset mode (twrp recovery if you swap recovery.img)
4. boot into update mode
you can reach menu 2-4 with vol+ and/or vol-. As long as you haven´t replaced bot recovery images. the button combinations vary depending on the flashed recovey(2).img version.
mode 4 only starts if you have an FULL UPDATE file in an dload folder in your internal or sd storage.
the update mode is the one that takes up to 30 seconds to start after the vibration. Keep holding the associated buttons and the power button until the device vibrates. then relase the powerbutton but keep holding the other buttons. then wait. after a while a cirlce with "EMUI update" will appear and install the update file you placed into the dload folder.
this method worked for me when i f****ed up and i also found some other thread with the same problem you have. did the same thing i just explained

Tuerkay said:
well i don´t know where to start. just give an short explanation about the Huawei Recovery system.
The Huawei Mate S hast 2 ("TWO") recoverys installed. Recovery.img and Recovery2.img. just for safety reason if someone or something f***s up the primary recovery.img (first recovery). the first one is also the one you normaly swap with the TWRP backup.
The Huawei Mate S can be booted in 4 ("four") different modes
1. normal boot into android
2. boot into fastboot&rescue mode
3. boot into reset mode (twrp recovery if you swap recovery.img)
4. boot into update mode
you can reach menu 2-4 with vol+ and/or vol-. As long as you haven´t replaced bot recovery images. the button combinations vary depending on the flashed recovey(2).img version.
mode 4 only starts if you have an FULL UPDATE file in an dload folder in your internal or sd storage.
the update mode is the one that takes up to 30 seconds to start after the vibration. Keep holding the associated buttons and the power button until the device vibrates. then relase the powerbutton but keep holding the other buttons. then wait. after a while a cirlce with "EMUI update" will appear and install the update file you placed into the dload folder.
this method worked for me when i f****ed up and i also found some other thread with the same problem you have. did the same thing i just explained
Click to expand...
Click to collapse
ok first of all the for all you help so far
secendly i did not whipe the recovery2 file since i never had the option
method 4 didnt work but maybe ist because my micro sd card is in exfat mode
ill try fat32
and one thing i havent mentiond yet is that i cant turn my phone off
i also only can enter fastboot and Huawei eRecovery mode by pressing the volume buttons and then plug the
phone into my computer

ladres said:
ok first of all the for all you help so far
secendly i did not whipe the recovery2 file since i never had the option
method 4 didnt work but maybe ist because my micro sd card is in exfat mode
ill try fat32
and one thing i havent mentiond yet is that i cant turn my phone off
i also only can enter fastboot and Huawei eRecovery mode by pressing the volume buttons and then plug the
phone into my computer
Click to expand...
Click to collapse
you don´t need to power it off. you can also reboot into the updatemenu from fastboot menu. just hold all buttons long enough and wenn the screen goes black, release the powerbutton after vibration.
sd card musst be fat32 i think

Tuerkay said:
you don´t need to power it off. you can also reboot into the updatemenu from fastboot menu. just hold all buttons long enough and wenn the screen goes black, release the powerbutton after vibration.
sd card musst be fat32 i think
Click to expand...
Click to collapse
didnt work
sd card is in fat32
i tried it exsactly like you toled me
and it took me to rescue mode again
btw the Vol up and vol down methoid used to take me to twrp
ive never seen the upadte mode

can you do an factory reset in the eRecovery?
if not, try
fastboot erase userdata
fastboot erase cache
in fastboot&rescue mode.
it´s possible that there is an incremental update file in your internal storage.
which update. app did you use? should be the last working version you used.

Tuerkay said:
can you do an factory reset in the eRecovery?
if not, try
fastboot erase userdata
fastboot erase cache
in fastboot&rescue mode.
it´s possible that there is an incremental update file in your internal storage.
which update. app did you use? should be the last working version you used.
Click to expand...
Click to collapse
eRecovery is aperently just for falshing using huawei server
but mate s seems not to be supportrd
fastboot gives me the same error as usual
sh-3.2# fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2# fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2#
i tride B115
and B114

ladres said:
eRecovery is aperently just for falshing using huawei server
but mate s seems not to be supportrd
fastboot gives me the same error as usual
sh-3.2# fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2# fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2#
i tride B115
and B114
Click to expand...
Click to collapse
CRR-UL00 or L09?
the eRecovery differs depending on the version used. i for example can factory reset via eRecovery.
It´s also strange that you can´t access the force update mode. this is an basic function you can´t erase.

Honor 4x factory reset and recovery menu not work

Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.

If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).

oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....

Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.

oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX

Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked

thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down

shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.

zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!

I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.

Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.

Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...

Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.

Recovery bootloop

Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?

ziembus said:
Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?
Click to expand...
Click to collapse
Dear
Press and hold vol - and power button together, then your phone will boot into fastboot mode.
then simply you can use fastboot commond below to flash recovery.
fastboot flash recovery recovery.img

OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?

ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
I want to know which recovery you tried to flash through fastboot. It may not allow you flashing twrp ultill oem is locked. You can try flashing stocking recovery.

ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
When in fastboot mode, you can try to boot twrp from the pc with
Code:
fastboot boot nameoftwrp.img

JamBax said:
When in fastboot mode, you can try to boot twrp from the pc with
Click to expand...
Click to collapse
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far

ziembus said:
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far
Click to expand...
Click to collapse
Try Leeco AIO tool kit to reboot your device into recovery . It's working for me

leco le 2 x520 recovery problem
I have a problem with recovery in le 2 x520. It installs via fastboot by unlocking the bootloader but stops at the Le recovery logo and nothing else happens. I installed from version 3.0.2.0 to 3.1.1.1 and nothing happens, I do not have recovery and writes everything okey went. what is going on ??

I have same problem. how to fix

I have a new one (acutally two, got them for U$D 108.99 each one)
Using ADB devices it recognize the UID like 0123456789ABCDEF, so I think the recovery is corrupted, intentional or not, it is blocking fastboot and recovery to load normally.
At this point I can't do anything.... any suggestions?

You solved it ?
I having the same issue maybe the issue is with stock rom since i flashed in normal twrp,chinese twrp and also that stock recovery.
****!