Database Info

Stuck at "...unlocked...booting now..." Bricked?

Solved.
AL10, NXT-C900B133, rescue0.3, NEXT
I unlocked bootloader, installed TWRP, and rooted using SuperSU with no problem by following these directions:
http://forum.xda-developers.com/mate-8/general/guide-unlock-bootloader-root-install-t3301371
I then formatted data using TWRP wipe, then tried to install Stock Rooted No Encrypted Boot from
http://forum.xda-developers.com/mate-8/development/rom-stock-rooted-encrypted-boot-t3303606
The phone never gets past "...unlocked...booting now...." (I did not install insecure_boot because I had trouble finding it---it is not in Mate 8 Android Development, only in Mate 8 Original Android Development.)
I can get to fastboot and to the Huawei recovery in Chinese (which doesn't work---wifi downloading stops with an exclamation point), but TWRP is gone, and I can't get it back by reflashing it. I've tried HiSuite recovery, unbricking using the Italian knife following these instructions:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
with various roms, and I've tried force flashing an UPDATE.APP from /sdcard/dload. No joy.
I caused the problem by installing a B331 rom when I was at B133—dyslexic much? Once I got TWRP back, flashing a B180 rom worked fine.
The difficulty was getting TWRP back. To do that, I flashed the following files using fastboot—it may be overkill:
TWRP-2.8.7.0-ENG.img,
insecure_boot_b331.img,
and the files in
L29Fastboot.rar.
TWRP

Hey ho!
I had exactly the same problem yesterday.
I figured out my system only was able to boot when I hold down [vol-]&[power].
Then the "not trusted message" had a few more lines and the phone booted up.
When it's up again, you can use adb to reboot to fastboot: adb reboot bootloader
You can also try to go directly to recovery if you alrteady flashed it: adb reboot recovery
From threre you can try again.
btw: I had to use a complete different TWRP version. 3.x somewhat. I think it was from here: http://forum.xda-developers.com/mate-8/development/recovery-twrp-huawei-mate-8-t3298567
Info: I was NOT able to use [vol+]&[power] for Recovery, eRecovery or anything else. I was just stuck.
I hope it helps.

I recommend after getting your device back on track to use twrp to make a recovery on your microsd card. That way u have a sure chance of getting bwck to working order

Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?

iAngus said:
Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?
Click to expand...
Click to collapse
Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".

Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".
Click to expand...
Click to collapse
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".

iAngus said:
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".
Click to expand...
Click to collapse
you could fix the same problem I have is not to do help me

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

strange... brick? (SOLVED)

Hello friends
I have a problem, to see if you can help me
I was installing a custom rom, and when I tried to install the twrp, I did not get it
ADB apparently performs the process well, but when trying to enter twrp, it enters the recovery stock
the problem is that I do not have an operating system or access to twrp, so I do not know how to recover the phone
by not having access to twrp, it does not help me HWOta or Huru Updater ...
I have access to bootloader and to the recoveries of huawei
before the disaster was in oreo
The bootloader is unlocked
any ideas?

You want to flash TWRP correct? Well first I want you to confirm me following things.
What recovery are you using. You need an Oreo Compatible TWRP. Try the one in Elemental ROM thread in Honor 6X Roms.
What command are you using. This is the most common mistake people make. Just a reminder the command to flash TWRP recovery on EMUI 8 is :-
fastboot flash recovery_ramdisk RECOVERY-V2.img
RECOVERY-V2.img is the name of TWRP you will download from above-mentioned thread.
Now if you are doing all of the above, and still no success, tell me what the Command Prompt says when you try to flash. After you flash try to manually boot into TWRP by holding Volume Up and Power. Luck.

Mannan Qamar said:
You want to flash TWRP correct? Well first I want you to confirm me following things.
What recovery are you using. You need an Oreo Compatible TWRP. Try the one in Elemental ROM thread in Honor 6X Roms.
What command are you using. This is the most common mistake people make. Just a reminder the command to flash TWRP recovery on EMUI 8 is :-
fastboot flash recovery_ramdisk RECOVERY-V2.img
RECOVERY-V2.img is the name of TWRP you will download from above-mentioned thread.
Now if you are doing all of the above, and still no success, tell me what the Command Prompt says when you try to flash. After you flash try to manually boot into TWRP by holding Volume Up and Power. Luck.
Click to expand...
Click to collapse
thanks for your reply
Yes, I know the commands, and it's even the same recovery, from KingOfMezi
as I comment, he performs the process well:
PS C: \ adb>. \ Fastboot flash recovery_ramdisk RECOVERY-V2.img
Sending 'recovery_ramdisk' (9100 KB)............................................. OKAY [0.328s]
Writing 'recovery_ramdisk'........................................................................ OKAY [0.125s]
Finished. Total time: 0.516s
PS C: \ adb>
but when starting the phone with power + vol+ (releasing power when vibrating and without releasing it, I tried both ways) starts the recovery stock
the most curious thing is that I had done it more times, and I never had any problem with that, in fact, the last thing I did was in the twrp

That's odd. Try to reboot after flashing TWRP. Once you flash it instead of manually booting into TWRP type
fastboot reboot
Now when the device shows device has been unlocked message press Volume up to enter erecovery. From there turn off phone and then boot into TWRP by holding Power and Volume Up. Keep holding it until you see your device is booting now... Screen.
Alternatively try to use dload to restore the system.

about dload I have a doubt.
Being debranded as l22 and having installed oreo, where do I get update.zip? of a ROM l22 oreo, or of the l21 that corresponds to my device?

Download L22 Oreo from Firmware Finder website or Windows App

solved use the bat of kingofmezi, Elementary Kernel + ramdisk.zip.
this made the recovery disappear (if you tried to access, a screen appeared similar to when we accessed fastboot, saying there is no recovery) and then flashed twrp correctly. thanks for your help

You are in Elemental v2. Do you mind if I ask for a review. Was it a complete flash or in complete. i.ewas the wallpaper when you first booted Blue&Black or Pink one.

Mannan Qamar said:
You are in Elemental v2. Do you mind if I ask for a review. Was it a complete flash or in complete. i.ewas the wallpaper when you first booted Blue&Black or Pink one.
Click to expand...
Click to collapse
unfortunately I could not prove it. when flashing the bat, I only managed to recover twrp, and then I was able to return to stock, I did not dare to try it again out of fear (I feel the delay, I could not enter before due to personal problems)

vicent76 said:
solved use the bat of kingofmezi, Elementary Kernel + ramdisk.zip.
this made the recovery disappear (if you tried to access, a screen appeared similar to when we accessed fastboot, saying there is no recovery) and then flashed twrp correctly. thanks for your help
Click to expand...
Click to collapse
Where can i find the elemental kerrnel+recovery.zip....I am not able to find it in official thread

Stuck with fastboot mode.

Ok, so I had oreo in my 6x indian variant, and wanted to flash elemental OS V8. But for some reason the TWRP was not able to access the data partition. And when I read somewhere in XDA (in other device's forum) that changing the file system from f2fs to ext4 can help and did so and it worked. I could access my internal storage and everything on TWRP. But I didn't change the file system back to f2fs and sideloaded the elemental 8. It worked find and I installed it. When rebooting it got into bootloop. After that I tried to get into the TWRP but didn't work. I flashed the TWRP again which said flashed OK, but when I tried to enter it took me to the stock recovery. When I tried the dload method with the nougat B360 version, it gave me blank screen with red led blinking and nothing working after that. I tried dload with the oreo file which gave me back the stock recovery and erecovery, but again flashing TWRP didn't work. After dload, it reboots to erecovery and asks me to wipe data partition since it is severely corrupt but says factory reset failed. In some cases it does go factory reset but doesn't boot into OS. Since I do not have access to TWRP I am not able to bring it back. I had got into this situations before but the dload always worked. Maybe now it isn't because I am on Oreo and the partitions are different from Nougat? I also tried formatting/erasing partitions from fastboot but gives me error/ remote command not allowed. I also tried Multi-Tool8 and used the unbrick option. but doesn't work it gives me all flashed, and when i flash the oreo files gives me all flashed Error#1, Complete, Something went wrong and bootloops again or gives me blank screens.
I have attached a screenshot of my device info. If anyone could help me breath life into it.

casperskie said:
Ok, so I had oreo in my 6x indian variant, and wanted to flash elemental OS V8. But for some reason the TWRP was not able to access the data partition. And when I read somewhere in XDA (in other device's forum) that changing the file system from f2fs to ext4 can help and did so and it worked. I could access my internal storage and everything on TWRP. But I didn't change the file system back to f2fs and sideloaded the elemental 8. It worked find and I installed it. When rebooting it got into bootloop. After that I tried to get into the TWRP but didn't work. I flashed the TWRP again which said flashed OK, but when I tried to enter it took me to the stock recovery. When I tried the dload method with the nougat B360 version, it gave me blank screen with red led blinking and nothing working after that. I tried dload with the oreo file which gave me back the stock recovery and erecovery, but again flashing TWRP didn't work. After dload, it reboots to erecovery and asks me to wipe data partition since it is severely corrupt but says factory reset failed. In some cases it does go factory reset but doesn't boot into OS. Since I do not have access to TWRP I am not able to bring it back. I had got into this situations before but the dload always worked. Maybe now it isn't because I am on Oreo and the partitions are different from Nougat? I also tried formatting/erasing partitions from fastboot but gives me error/ remote command not allowed. I also tried Multi-Tool8 and used the unbrick option. but doesn't work it gives me all flashed, and when i flash the oreo files gives me all flashed Error#1, Complete, Something went wrong and bootloops again or gives me blank screens.
I have attached a screenshot of my device info. If anyone could help me breath life into it.
Click to expand...
Click to collapse
What command you use to flash TWRP? And what image are you trying to flash? Try this. In Fastboot flash RECOVERY-V2.img (Elemental ROM TWRP) via command.
fastboot flash recovery_ramdisk RECOVERY-V2.img
After it's flashed, press and Hold Power and Volume Up till you see Honor logo then let go. It Should boot to TWRP. If not then extract the Uodate.zip (the large one) and you will get Update.app and using Huawei Update Extractor extract System.img, Ramdisk.img and Recovery_ramdisk.img then boot phone to fastboot and flash them manually as
fastboot flash boot boot.img
fastboot flash recovery_ramdisk Recovery_ramdis.img
And,
fastboot flash system system.img
This should work. It's a boot error.

I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.

Mannan Qamar said:
What command you use to flash TWRP? And what image are you trying to flash? Try this. In Fastboot flash RECOVERY-V2.img (Elemental ROM TWRP) via command.
fastboot flash recovery_ramdisk RECOVERY-V2.img
After it's flashed, press and Hold Power and Volume Up till you see Honor logo then let go. It Should boot to TWRP. If not then extract the Uodate.zip (the large one) and you will get Update.app and using Huawei Update Extractor extract System.img, Ramdisk.img and Recovery_ramdisk.img then boot phone to fastboot and flash them manually as
fastboot flash boot boot.img
fastboot flash recovery_ramdisk Recovery_ramdis.img
And,
fastboot flash system system.img
This should work. It's a boot error.
Click to expand...
Click to collapse
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.

shashank1320 said:
I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.
Click to expand...
Click to collapse
I actually relocked and unlocked the bootloader again, just to be sure. But will try the B340 one, didn't try that. Thanks for the links will check them out

casperskie said:
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.
Click to expand...
Click to collapse
Yes, boot is ramdisk in oreo and recovery is ramdisk_recovery.

shashank1320 said:
I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.
Click to expand...
Click to collapse
So the B340 dload didn't work for me. Gives the same results. Always boots into erecovery and then fails to factory reset. Also the phone doesn't get switched on or boot into recovery without connecting to the USB. Only when it is connected it works, that too after 5-10 mins after I press the Power button or the Recovery key combination. And I used a 4GB memory card, could this be the reason the dload didn't work?

casperskie said:
So the B340 dload didn't work for me. Gives the same results. Always boots into erecovery and then fails to factory reset. Also the phone doesn't get switched on or boot into recovery without connecting to the USB. Only when it is connected it works, that too after 5-10 mins after I press the Power button or the Recovery key combination. And I used a 4GB memory card, could this be the reason the dload didn't work?
Click to expand...
Click to collapse
You may need 8 GB SD card if you have or can borrow and see if that helps. Whats the size of update.app file?

casperskie said:
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.
Click to expand...
Click to collapse
Nope flashing the files individually also doesn't work. it's all the same.

shashank1320 said:
You may need 8 GB SD card if you have or can borrow and see if that helps. Whats the size of update.app file?
Click to expand...
Click to collapse
Something around 3.3 GB. There's only some 250mb left in the card when I copy the update.app

casperskie said:
Something around 3.3 GB. There's only some 250mb left in the card when I copy the update.app
Click to expand...
Click to collapse
May be you can try with 8 gb once if it is easily available for you

Hi, so none of the methods work. But I could get back to TWRP for Elemental Rom. Still flashing roms from TWRP doesn't boot me in. And now the dload screen doesn't appear when I press the combination. All I have is fastboot mode, erecovery and TWRP installed. But none of the methods work. I am not able to figure what I am doing wrong!!

Try hurupdater.
http://https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
0.3 for nougat or 0.4 for oreo (in my case works)
And remember format data in first time
You need the firmware for your 6x...
Good luck!

hey i am in the same situation as yours, all i am able to boot into is fastboot, nothing beyond that is working, i have the extracted update.app for oreo , the last system i flashed was emui oreo , and nothing else is working i have tried all the options suggested.
could someone guide me on the actual steps needed to flash the .img files as i'm unable to boot into recovery of twrp or openkirin
any help will be appreciated.

ppawan said:
hey i am in the same situation as yours, all i am able to boot into is fastboot, nothing beyond that is working, i have the extracted update.app for oreo , the last system i flashed was emui oreo , and nothing else is working i have tried all the options suggested.
could someone guide me on the actual steps needed to flash the .img files as i'm unable to boot into recovery of twrp or openkirin
any help will be appreciated.
Click to expand...
Click to collapse
Just dload the b340 image of nougat and back to nougat.

Need help for soft brick (eRecovery not working)

What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?

hey i can help ! which version of twrp are you trying to flash ?

lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.

Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi

King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.

King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .

King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.

lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?

Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!

lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?

Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?

lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).

Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result

lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson

speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...

Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?

lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img

Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"

lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?

Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson