Database Info

[Q] I can't boot into recovery mode after rooting

Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.

cormyn said:
Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.
Click to expand...
Click to collapse
you need to flash a recovery via fastboot.
Download the clockwork recovery recovery-clockwork-3.0.0.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type...
fastboot flash recovery recovery.img
and hit enter
Click to expand...
Click to collapse

simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

distortedloop said:
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
fixed it, thanks!

simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
Huh, I thought the recovery reset itself... Thanks for the info.

Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think if I'm going to wipe my phone anyway, I'll just wipe it back to factory and leave the phone unrooted... Too much hassle with the internal SD getting wiped every time.

cormyn said:
Huh, I thought the recovery reset itself... Thanks for the info.
Click to expand...
Click to collapse
Only after a successful reboot to the normal system, and only if you're on 2.3.1 or greater, and only if you've not renamed the /etc/install-recovery.sh file.
cormyn said:
Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think I'm just going to unroot my phone. Too much hassle with the internal SD getting wiped every time.
Click to expand...
Click to collapse
Yeah, that sucks. I don't relock my bootloader.

Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.

cormyn said:
Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.
Click to expand...
Click to collapse
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?

distortedloop said:
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
i was using the older CW recovery 3.0.0.0 also, so i just decided to flash version 3.0.0.5. since im at work, i cant fastboot it to my phone. i did it via the terminal emulator on my phone. 1st time i got a bunch of out of space errors so i booted into recovery just to check, and it was gone. nothing there. so i rebooted and tried it again via terminal. 2nd time was a success. to flash the recovery in the terminal emulator, download the recovery and put it on the root of your sd card and rename it recovery.img . now open the terminal and type...
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)

well, apparently a factory wipe was a bad move, 'cause now the phone rebooted and is stuck at the Google logo, like it's trying to get back into the recovery.

cormyn said:
Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?
Click to expand...
Click to collapse
Factory reset won't remover the su binary and symlinks it makes. Factory reset only wipes the /data partition, not the /system one.
An oem lock, then oem unlock might, but I'm not sure...that definitely wipes the sdcard, though, unlike a factory reset does, so back that up first!
There's some thread on here someplace about how to completely remove root.

Pulled the battery, went back into bootloader mode, did a 'fastboot oem unlock', then flashed the crespo 3.0.5 img, and then 'fastboot oem lock' and the phone reboots properly.
Thanks again!

[SOLVED/THANKS GUYS] hopeless boot loop.. :(

was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
can i RUU or something?

wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try

wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
Can you relock the bootloader? If can then download the official RUU(here is 2.20 firmware http://www.htc.com/us/support/htc-one-x-att/software-updates) and that'll probably save your phone.
oh, you can use the all in one toolkit(http://forum.xda-developers.com/showthread.php?t=1952426) to relock your bootloader if you can.. good luck

TheEmpyre said:
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
Click to expand...
Click to collapse
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing. tried to mount SD card: windows wants to format it. **** me

wdkingery said:
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing
Click to expand...
Click to collapse
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.

iElvis said:
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
Click to expand...
Click to collapse
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?

wdkingery said:
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
Click to expand...
Click to collapse
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM

TheEmpyre said:
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
Click to expand...
Click to collapse
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.

wdkingery said:
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
Click to expand...
Click to collapse
Does your TWRP not have a "Format Data" Option in the Wipe Menu?
Edit: Just read your most recent edit, happy flashing hope everything works out. Oh and add [Solved] to your title if you don't mind

it does, but even that didn't work..

[Q] Nexus 5 stuck on boot, and wont go into recovery help?

Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
You need to find a driver that works so it'll recognize the device. Once you do this, you need to flash boot.img to restore the recovery since not working. Then, redo the ROM or restore from backup if you can. Flashing a new recovery boot.img should fix the issue.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.

GUGUITOMTG4 said:
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
Click to expand...
Click to collapse
Thanks! got to recognize any way to do this without loosing data?

2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.

2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
May be able to dirty flash but most likely, since you had the screen dimmed too much, you'll have to wipe data in order to override/remove the problem. You can try this way but may just send you back through this whole process if problem reoccurs. I'd just wipe the data to be safe.

2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Oy vey! You shouldn't have been tinkering as you clearly don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
No, and if you had done your homework you would know that. If the data is so important, back it up before modding.

GUGUITOMTG4 said:
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
Click to expand...
Click to collapse
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall

2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
Reflash the recovery.img

2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.

jd1639 said:
Reflash the recovery.img
Click to expand...
Click to collapse
GUGUITOMTG4 said:
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
Click to expand...
Click to collapse
Did that and get a
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
sending 'recovery' (13272 KB)...
OKAY [ 0.620s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 44.593s
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>

But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed

2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
You have a couple of options depending on how much data you can afford to lose on your phone. The least intrusive is to adb push a Rom on to your phone when you're in twrp Then flash that rom in twrp
The easier, but you'll lose all data on your phone is to flash the flash-all.bat file in fastboot
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
Then, it seems recovery now is good. If you have rom zip in the storage. Just wipe system and cache, flash the rom and see what happens

When in the twrp I can't get fastboot to recognize it as a device, or adb either

2point said:
When in the twrp I can't get fastboot to recognize it as a device, or adb either
Click to expand...
Click to collapse
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.

jd1639 said:
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
Click to expand...
Click to collapse
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash

GUGUITOMTG4 said:
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
Click to expand...
Click to collapse
How do i do that?

2point said:
How do i do that?
Click to expand...
Click to collapse
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp

jd1639 said:
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
Click to expand...
Click to collapse
I have the factory image from google for my nexus 5

Please help i cant boot into recovery

hello all this what happens I flash a bad room and it keeps rebooting and I cannot go back to recovery check this video if someone have an idea or fix it before.
thanks in advance.
https://www.youtube.com/watch?v=Qh5BTDVhGOY
https://www.youtube.com/watch?v=Ya-0WwswJi8

kasey348 said:
hello all this what happens I flash a bad room and it keeps rebooting and I cannot go back to recovery check this video if someone have an idea or fix it before.
thanks in advance.
https://www.youtube.com/watch?v=Qh5BTDVhGOY
Click to expand...
Click to collapse
You can try re-flashing TWRP which may clean it up and allow you in. Power down the phone (pull the battery and put it back in), hold down the volume down, and plug your phone into your computer while keeping the volume down pressed. Should get you into fastboot/bootloader. From there you can do "fastboot flash recovery twrp-3.0.2-0-h918.img". You can then reboot via "fastboot reboot". Now I'm not too familiar with the h918 model so I'm not for sure you can do this in fastboot/bootloader but if you can it's worth a shot.
Try "fastboot erase cache" instead. Your TWRP seems to be getting stuck running an OpenRecoveryScript which is located in the cache partition according to documentation. If you clear the cache it should theoretically let you into TWRP instead of running the script on start.

redshorty4 said:
You can try re-flashing TWRP which may clean it up and allow you in. Power down the phone (pull the battery and put it back in), hold down the volume down, and plug your phone into your computer while keeping the volume down pressed. Should get you into fastboot/bootloader. From there you can do "fastboot flash recovery twrp-3.0.2-0-h918.img". You can then reboot via "fastboot reboot". Now I'm not too familiar with the h918 model so I'm not for sure you can do this in fastboot/bootloader but if you can it's worth a shot.
Try "fastboot erase cache" instead. Your TWRP seems to be getting stuck running an OpenRecoveryScript which is located in the cache partition according to documentation. If you clear the cache it should theoretically let you into TWRP instead of running the script on start.
Click to expand...
Click to collapse
thanks man
but I can only lock or unlock my boot-loader it doesn't take any other commands to reboot into recovery i need to make work adb shell.
thanks for your advice.

kasey348 said:
thanks man
but I can only lock or unlock my boot-loader it doesn't take any other commands to reboot into recovery i need to make work adb shell.
thanks for your advice.
Click to expand...
Click to collapse
Was worth a shot. If you can get an adb shell you should be able to fix recovery. Did you try locking and then unlocking the bootloader? It wipes userdata and cache when you lock/unlock. That could fix your TWRP.

redshorty4 said:
Was worth a shot. If you can get an adb shell you should be able to fix recovery. Did try locking and unlocking the bootloader? It wipes userdata and cache when you lock/unlock. That could fix your TWRP.
Click to expand...
Click to collapse
yes i did that too it wipes the phone then it boots into the system but all the apps keeps crashing all i get is a black screen.

Mine is doing the exact same thing,,, Except I don't get passed the LG logo. I'm on the same version of TWRP also.

The G.O.A.T. said:
Mine is doing the exact same thing,,, Except I don't get passed the LG logo. I'm on the same version of TWRP also.
Click to expand...
Click to collapse
crap i have the whole week without phone i guess the only way we can fix this is loading or flashing a tot file i just need a dll file that one have it anywhere,
but if i find a solution i will let you know my friend, don't give up we are get it fix trust me.
keep looking on this tread i'm downgrading my pc to windows 7 today I been installing a lot crap to make this phone work and nothing i read that windows 7 works better.

Very hard brick

Hi!
Okay, this case is really weird and of course is thanks to my negligence. I'm gonna post it hoping someone can help me, or at least keep other people aware about trying stupid things lol
I tried to update to Nougat with an unofficial method (I don't consider necessary to tell what method...) and I just messed it up, badly. I'll try to give a detailed explanation:
The phone has the bootloader unlocked. After trying to update to Nougat, it got stuck when rebooting. After the unlocked bootloader warning message, the phone won't go further than that, it just stays there. If I hold and press the power button for more than 10 seconds the phone won't shut down, it will restart to get stuck again after the unlocked BL warning, making impossible to turn it off completely.
I try to enter to stock recovery by pressing vol + and power button at the same time (tried other combinations, vol - and power button & vol -, vol + and power button) but I have no luck, it just gets stuck at the same point.
I already tried extracting BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img from an official update.app and flash them in that order via fastboot (yeah, I can enter to fastboot mode). The process is successful in terminal (I use Linux) but when I reboot the phone, it gets stuck again after the warning.
The only recovery that is actually working is TWRP, the one ported for the Honor 8 (flashed via fastboot), but it won't let me install any custom ROM, it just stays in "patching image unconditionally" forever, making me press and hold the power button but this won't shutdown the phone, it reboots, gets stuck and... so on *infinite loop*
Btw, when I wipe cache, dalvik and data in TWMP, the message "failed to mount /cust" with red letters appears, so it's probably a very corrupted system partition. also, It's impossible to repair the custom partition. This appears:
Repairing Custom using e2fdck...
/sbin/e2fsck -fp /devblock/mmcblk0p44 process ended with ERROR: 8
Unable to repair Custom.
Click to expand...
Click to collapse
Tried HiSuite from Huawei (in Windows) and it doesn't even recognize the phone.
Hope somebody could possibly give a solution, if there's any. If not, I'm afraid I have a beautiful paperweight now...
Oh yeah, one very important part: my Honor 8 is the US version (FRD-L04), and yes, I'm making sure I'm getting the current update.app for this model.
Any help would be greatly appreciated. Thanks in advance.

Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this

chongns said:
Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this
Click to expand...
Click to collapse
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons... But I'll try it.
Edit: Trying your method right now, hope it goes well...

El Brillantinas said:
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons...
Click to expand...
Click to collapse
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Edit: Fastboot erase {partition} before flash back the image maybe help

chongns said:
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Click to expand...
Click to collapse
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Software install failed!
Get help from: http//www.emui.com/emotionetcetc.
Click to expand...
Click to collapse

El Brillantinas said:
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Click to expand...
Click to collapse
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access

chongns said:
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access
Click to expand...
Click to collapse
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!

El Brillantinas said:
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!
Click to expand...
Click to collapse
Good to know you succeed.
please tag a moderator to move your thread to Guide, News and Discussion section..
most of the time ppl search solution at there.

Guide in another Huawei phone XDA forum.
http://forum.xda-developers.com/mate-8/general/fuss-debrick-restore-mate-8-t3457969

Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.

Glad you fixed it bro. That was very critical.

El Brillantinas said:
Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.
Click to expand...
Click to collapse
good to hear u go phone back , and there is another guides already exist to restore a framware throw the same method , thank you for sharing ur experience .

Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated

bho01 said:
Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated
Click to expand...
Click to collapse
Is your frp status lock in fastboot?

faizalotai said:
Is your frp status lock in fastboot?
Click to expand...
Click to collapse
No it's unlocked

bho01 said:
No it's unlocked
Click to expand...
Click to collapse
Your phone status?

faizalotai said:
Your phone status?
Click to expand...
Click to collapse
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images

bho01 said:
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images
Click to expand...
Click to collapse
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.

Try using the dload method of flashing

faizalotai said:
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.
Click to expand...
Click to collapse
Also unlocked