Help!!! Is my Honor 8 bricked?? - Honor 8 Questions & Answers

I'm in a really bad position right now. I flashed TWRP on my phone to flash stock recovery on my phone. I attempted to wipe everything before I flashed something, but it gave me errors that it failed to mount Cust, Product, Vendor, and Device. I was able to get rid of the Cust error, but the other three remained. Now my phone does not boot into anything. I tried flashing stock and it did nothing.
I just tried following this: https://forum.xda-developers.com/showpost.php?p=70158202&postcount=5
I was able to extract everything, but when I tried to unbrick the phone I got some errors.
RNV0216811011914 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15490 KB)...
OKAY [ 0.334s]
writing 'boot'...
OKAY [ 0.378s]
finished. total time: 0.720s
target reported max download size of 471859200 bytes
sending 'cust' (258509 KB)...
OKAY [ 5.576s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.597s
target reported max download size of 471859200 bytes
sending 'recovery' (37044 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 0.878s]
finished. total time: 1.685s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (433185 KB)...
OKAY [ 10.174s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.575s
As you can see, it failed to both write to cust and system. Due to this I still cannot boot into anything other than TWRP and Fastboot mode. Not the operating system (EMUI), not Huawei eRecovery.
Please help me...is my phone bricked for good, or can I fix this?

Quick update: I am able to reach Huawei eRecovery. However, if I try to download the latest version and recovery, it ultimately ends up at "Getting package info failed". Maybe I can do something with eRecovery?
Just to recap: I can access fastboot mode, TWRP, and eRecovery. I can not access the OS.

cosmopath said:
Quick update: I am able to reach Huawei eRecovery. However, if I try to download the latest version and recovery, it ultimately ends up at "Getting package info failed". Maybe I can do something with eRecovery?
Just to recap: I can access fastboot mode, TWRP, and eRecovery. I can not access the OS.
Click to expand...
Click to collapse
In twrp, select storage, how much is it?,internal not sdcard?

faizalotai said:
In twrp, select storage, how much is it?,internal not sdcard?
Click to expand...
Click to collapse
It shows 24104MB. I have the 32GB model.

cosmopath said:
It shows 24104MB. I have the 32GB model.
Click to expand...
Click to collapse
What about data partition, what type does it show..f2fs or ext

faizalotai said:
What about data partition, what type does it show..f2fs or ext
Click to expand...
Click to collapse
I'll just share all of the stats about it:
Mount Point: /data
File system: ext4 (I believe this is what you're looking for)
Present: Yes
Size: 24148MB
Free: 24104MB
Removable: No
Used: 0MB
Backup Size: 0MB

cosmopath said:
I'll just share all of the stats about it:
Mount Point: /data
File system: ext4 (I believe this is what you're looking for)
Present: Yes
Size: 24148MB
Free: 24104MB
Removable: No
Used: 0MB
Backup Size: 0MB
Click to expand...
Click to collapse
So far nothing wrong with your storage,
What software ver are you on with before this happened

faizalotai said:
So far nothing wrong with your storage,
What software ver are you on with before this happened
Click to expand...
Click to collapse
I was on the official beta build of EMUI 5.0, but I flashed it. I was trying to go back to stock so I could get the official update now that it rolled out in my region.

cosmopath said:
I was on the official beta build of EMUI 5.0, but I flashed it. I was trying to go back to stock so I could get the official update now that it rolled out in my region.
Click to expand...
Click to collapse
In beta, you use what ver of twrp?

faizalotai said:
In beta, you use what ver of twrp?
Click to expand...
Click to collapse
I'm using 3.0.2-0, the build from this post in particular: https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262
I tried a couple other builds which didn't work.

cosmopath said:
I'm using 3.0.2-0, the build from this post in particular: https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262
I tried a couple other builds which didn't work.
Click to expand...
Click to collapse
So youre using nougat, and you flash MM images??
Try this, find your rollback package, donload and put updated.app in dload folder(create new one in sdcard)
Let it updates with 3 button pushed.
Find your full firmware package, download it than you need to replace the updates.app in dload folder with full firmware one.
Let it updates with 3 buttons pushed also.
You'll loose twrp and bootloader locked again

I am also faced same problem. Just follow my steps
1.grab stock recovery.img form stock firmware by extracting update.app in Huawei update extrator .
2.flash it in fast boot.
3.switch off ur device.
4. Copy stock update.app to SD/dload.
5.then force update by all three buttons
Boom it works for me :good:

faizalotai said:
So youre using nougat, and you flash MM images??
Try this, find your rollback package, donload and put updated.app in dload folder(create new one in sdcard)
Let it updates with 3 button pushed.
Find your full firmware package, download it than you need to replace the updates.app in dload folder with full firmware one.
Let it updates with 3 buttons pushed also.
You'll loose twrp and bootloader locked again
Click to expand...
Click to collapse
VenuGopalu said:
I am also faced same problem. Just follow my steps
1.grab stock recovery.img form stock firmware by extracting update.app in Huawei update extrator .
2.flash it in fast boot.
3.switch off ur device.
4. Copy stock update.app to SD/dload.
5.then force update by all three buttons
Boom it works for me :good:
Click to expand...
Click to collapse
It worked!!! To be specific, I followed faizalotai's guide because I thought that updating the rollback package would fix it, but VenuGopalu's guide was very similar. I'm now running EMUI 4.1 without any problems. Apparently I don't have the update to EMUI 5 yet, but I'm sure I'll be getting that soon. Thank you so much, guys!

cosmopath said:
It worked!!! To be specific, I followed faizalotai's guide because I thought that updating the rollback package would fix it, but VenuGopalu's guide was very similar. I'm now running EMUI 4.1 without any problems. Apparently I don't have the update to EMUI 5 yet, but I'm sure I'll be getting that soon. Thank you so much, guys!
Click to expand...
Click to collapse

When I am tried install twrp by adb in fastboot mode isee infromation" target reported max download size of 471859200 bytes" and failed

Mysia said:
When I am tried install twrp by adb in fastboot mode isee infromation" target reported max download size of 471859200 bytes" and failed
Click to expand...
Click to collapse
Make sure your device is unlocked bootloader

Related

i (think I) killed my Honor 8

I rooted my Honor 8 yesterday and it was working fine, I went to install BusyBox, and accidentally installed SuperSU, and now I couldn't pass the SafetyNet checks, even with Magisk installed. I used TWRP to wipe my device, and went to install the backup. Wouldn't you know, the backup I made was no good.
I'm able to get into TWRP and eRecovery, but since I unlocked the bootloader (and no longer have access to the code), i can't use eRecovery.
anyone want to earn a nice hug for helping me figure this out?
I've been trying to flash the BOOT, CUST, RECOVERY and SYSTEM IMG files I extracted from Update.APP. The first 3 flashed fine, but System is too large.
Microsoft Windows [Version 10.0.16257.1]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 10.731s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.778s
aNGERY said:
I've been trying to flash the BOOT, CUST, RECOVERY and SYSTEM IMG files I extracted from Update.APP. The first 3 flashed fine, but System is too large.
Microsoft Windows [Version 10.0.16257.1]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 10.731s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.778s
Click to expand...
Click to collapse
i too got this error.
flash the images by unbrick option in huawei multi tool it works
venugopalu007 said:
i too got this error.
flash the images by unbrick option in huawei multi tool it works
Click to expand...
Click to collapse
i struggle with russian. any idea where i can find the english build?
aNGERY said:
i struggle with russian. any idea where i can find the english build?
Click to expand...
Click to collapse
can you provide the information of build number and which build you want?
i found an english build, here's what it's doing:
what would be sick, is if someone could share a TWRP backup of their device.
aNGERY said:
what would be sick, is if someone could share a TWRP backup of their device.
Click to expand...
Click to collapse
Bro in which emui are you on, if emui 5 just do a roll back using rollback packages.
venugopalu007 said:
Bro in which emui are you on, if emui 5 just do a roll back using rollback packages.
Click to expand...
Click to collapse
I am pretty positive I no long have an OS installed on this device, TWRP is saying I have 0mb in the system partition.
However, the phone WAS on EMUI 5.
venugopalu007 said:
Bro in which emui are you on, if emui 5 just do a roll back using rollback packages.
Click to expand...
Click to collapse
https://club.hihonor.com/in/eyestow...-marshmallow-this-is-what-you-should-do.11907
that's the guide i found.
Now I'm getting:
"Software install failed! Incompatibility with current version. Please download the correct update package"
aNGERY said:
https://club.hihonor.com/in/eyestow...-marshmallow-this-is-what-you-should-do.11907
that's the guide i found.
Now I'm getting:
"Software install failed! Incompatibility with current version. Please download the correct update package"
Click to expand...
Click to collapse
Bro you cannot install another build roll back...
Tell me your build number ...frd-L09or frdl19or...??
FRD-L04
venugopalu007 said:
Bro you cannot install another build roll back...
Tell me your build number ...frd-L09or frdl19or...??
Click to expand...
Click to collapse
FRD-L04
aNGERY said:
FRD-L04
Click to expand...
Click to collapse
Download this http://www.hihonor.com/us/support/details/index.html?DOC_ID=92098 extract and copy update.app to dload folder of sd card now make sure your device is off, now press and all 3 buttons after vibration release the power ,it will update successful.
And now download this ad again copy to sd card dload folder (replace it ) http://www.hihonor.com/us/support/details/index.html?DOC_ID=89264
Do the same power and hold buttons......
And after successful you device will works.
If it stucks at blue screen just do a factory reset once in recovery mode.
venugopalu007 said:
Bro you cannot install another build roll back...
Tell me your build number ...frd-L09or frdl19or...??
Click to expand...
Click to collapse
venugopalu007 said:
Download this http://www.hihonor.com/us/support/details/index.html?DOC_ID=92098 extract and copy update.app to dload folder of sd card now make sure your device is off, now press and all 3 buttons after vibration release the power ,it will update successful.
And now download this ad again copy to sd card dload folder (replace it ) http://www.hihonor.com/us/support/details/index.html?DOC_ID=89264
Do the same power and hold buttons......
And after successful you device will works.
If it stucks at blue screen just do a factory reset once in recovery mode.
Click to expand...
Click to collapse
i love you <3
will i be able to update to Nougat pretty easily?
aNGERY said:
i love you <3
Click to expand...
Click to collapse
Report me after it works.
venugopalu007 said:
Report me after it works.
Click to expand...
Click to collapse
it seems to be hung up at 5 percent for a few minutes now, is that pretty common? how long does it take.
aNGERY said:
it seems to be hung up at 5 percent for a few minutes now, is that pretty common? how long does it take.
Click to expand...
Click to collapse
In which zip ? First or second?
venugopalu007 said:
In which zip ? First or second?
Click to expand...
Click to collapse
i actually reset it in the middle and it worked fine! thanks. updating to Nougat now
aNGERY said:
i actually reset it in the middle and it worked fine! thanks. updating to Nougat now
Click to expand...
Click to collapse
Just check if a system app is missing (like NFC or keyboard) as it did happen to many users

I messed up my Mate 9, bricked?? Help a noob please

Hello XDA,
i had a fully working device, rooted unlocked bootloader MHA-L29C432. After i clicked in superSU to deinstall it, everything went bad. My smartphone was totally fu*
I got this message Error Mode Attention! Func 10 Bootimg and 2 Load failed i followed this https://forum.xda-developers.com/mate-9/help/bricked-mate-9-please-help-t3722133 post and got rid of the message but know when i boot my phone its restarts after the huawei logo into e recovery permanent.
I dont know what to do know its frustating like my english i guess... lol
I got a unlocked bl and have my twrp back.
calby17 said:
Hello XDA,
i had a fully working device, rooted unlocked bootloader MHA-L29C432. After i clicked in superSU to deinstall it, everything went bad. My smartphone was totally fu*
I got this message Error Mode Attention! Func 10 Bootimg and 2 Load failed i followed this https://forum.xda-developers.com/mate-9/help/bricked-mate-9-please-help-t3722133 post and got rid of the message but know when i boot my phone its restarts after the huawei logo into e recovery permanent.
I dont know what to do know its frustating like my english i guess... lol
I got a unlocked bl and have my twrp back.
Click to expand...
Click to collapse
Follow the instructions here
Shadowprince94 said:
Follow the instructions here
Click to expand...
Click to collapse
I get this error
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.442s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.454s
and i can disconnect now...
calby17 said:
I get this error
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.442s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.454s
and i can disconnect now...
Click to expand...
Click to collapse
Did you use the files in that link? If so, you flashed Oreo.
Whatbwas your firmware before SuperSU? Lx9C432Bxxx
ante0 said:
Did you use the files in that link? If so, you flashed Oreo.
Whatbwas your firmware before SuperSU? Lx9C432Bxxx
Click to expand...
Click to collapse
I did... also i already have twrp why does this weird tool try to install it aigen?
I'm a bit confused and really want to get my phone back to normal
My firmware was EU C432 oreo 8.0.0... something else. I dont remember it so good
calby17 said:
I get this error
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.442s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.454s
and i can disconnect now...
Click to expand...
Click to collapse
dude help me please
calby17 said:
I did... also i already have twrp why does this weird tool try to install it aigen?
I'm a bit confused and really want to get my phone back to normal
My firmware was EU C432 oreo 8.0.0... something else. I dont remember it so good
Click to expand...
Click to collapse
Well, that tool is for Nougat so it's no good for Oreo.
Flash this: https://mega.nz/#!YaIUhZhQ!ewDfrlQC5-fQ1oHfEj2YOo-2rDyi6b-dUoM4qx13e9A
fastboot flash recovery_ramdisk TWRP-3.0.3-for_Oreo.img
Then download this:
https://mega.nz/#!YaJX3LzL!H71Fl2OSHInk7OH7KWbWj7KFrR0lJi9oN9QB2hpMaTM
Flash ramdisk using fastboot flash ramdisk b361_ramdisk.img
B361 is the released oreo in EU. If you had a beta I'll have to find some other ramdisk. I have B329 too if that one doesn't work.
Sorry it took a while, I was sleeping.
ante0 said:
Well, that tool is for Nougat so it's no good for Oreo.
Flash this: https://mega.nz/#!YaIUhZhQ!ewDfrlQC5-fQ1oHfEj2YOo-2rDyi6b-dUoM4qx13e9A
fastboot flash recovery_ramdisk TWRP-3.0.3-for_Oreo.img
Then download this:
https://mega.nz/#!YaJX3LzL!H71Fl2OSHInk7OH7KWbWj7KFrR0lJi9oN9QB2hpMaTM
Flash ramdisk using fastboot flash ramdisk b361_ramdisk.img
B361 is the released oreo in EU. If you had a beta I'll have to find some other ramdisk. I have B329 too if that one doesn't work.
Sorry it took a while, I was sleeping.
Click to expand...
Click to collapse
Thanks.
During flash no problems, but my phone keeps rebooting into eRecovery after your Device has been unlocked and cant be trusted.
calby17 said:
Thanks.
During flash no problems, but my phone keeps rebooting into eRecovery after your Device has been unlocked and cant be trusted.
Click to expand...
Click to collapse
Was it long ago you installed Oreo?
ante0 said:
Was it long ago you installed Oreo?
Click to expand...
Click to collapse
i didnt use the beta. I upgreaded from hicare/ normal systemupdate to oreo when its was out. A few days ago.
calby17 said:
i didnt use the beta. I upgreaded from hicare/ normal systemupdate to oreo when its was out. A few days ago.
Click to expand...
Click to collapse
Ah, good.
I'll extract it when I get home.
Its the boot I sent then. I extracted it from my phone and I'm rooted. That's probably why it doesn't work.
ante0 said:
Ah, good.
I'll extract it when I get home.
Its the boot I sent then. I extracted it from my phone and I'm rooted. That's probably why it doesn't work.
Click to expand...
Click to collapse
Okay Btw yesterday when i was in twrp it showed me NO OS do you really want to shut down? Is this true?
calby17 said:
Okay Btw yesterday when i was in twrp it showed me NO OS do you really want to shut down? Is this true?
Click to expand...
Click to collapse
If a fresh boot image doesn't work you can always use HWOTA8 and reinstall Oreo.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
ante0 said:
If a fresh boot image doesn't work you can always use HWOTA8 and reinstall Oreo.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
Click to expand...
Click to collapse
D. Create "HWOTA8" directory in MTP sdcard.
E. Put hwota8_update.zip, MHA_RECOVERY8_NoCheck.img, and three huawei update package (update.zip, update_data_public.zip, and update_all_hw.zip) files into "HWOTA8" directory.
F. TWRP install sdcard hwota8_update.zip, it will reboot and install update automatically.
I dont understand these steps right i think...
Okay iam stupid. I did not know i can transfer data with my PC in twrp. Now i need these update.zp public and the other one. I need to go in a few minutes, if you can send me a link please where i can find these ante0
Where can i get update.zip data_public und all hw?
calby17 said:
D. Create "HWOTA8" directory in MTP sdcard.
E. Put hwota8_update.zip, MHA_RECOVERY8_NoCheck.img, and three huawei update package (update.zip, update_data_public.zip, and update_all_hw.zip) files into "HWOTA8" directory.
F. TWRP install sdcard hwota8_update.zip, it will reboot and install update automatically.
I dont understand these steps right i think...
Okay iam stupid. I did not know i can transfer data with my PC in twrp. Now i need these update.zp public and the other one. I need to go in a few minutes, if you can send me a link please where i can find these ante0
Where can i get update.zip data_public und all hw?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v107979/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/MHA-L29_hw_eu/update_full_MHA-L29_hw_eu.zip
http://update.hicloud.com:8180/TDS/...79/f1/full/public/update_data_full_public.zip
Rename update_data_full_public.zip to update_data_public.zip, rename update_full_MHA-L29_hw_eu.zip to update_all_hw.zip
Make a folder on external SD named HWOTA8, put files in there.
ante0 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v107979/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/MHA-L29_hw_eu/update_full_MHA-L29_hw_eu.zip
http://update.hicloud.com:8180/TDS/...79/f1/full/public/update_data_full_public.zip
Rename update_data_full_public.zip to update_data_public.zip, rename update_full_MHA-L29_hw_eu.zip to update_all_hw.zip
Make a folder on external SD named HWOTA8, put files in there.
Click to expand...
Click to collapse
yeey ^^ my phone works aigen like charm.
Thank you ante0 great guy good to see that somebody helps here

Flashed magisk patched boot image - killed phone :(

I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
thecdn said:
I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...gisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
Click to expand...
Click to collapse
You need to restore your original ramdisk. Also, you have to patch your own ramdisk.img with Magisk Manager if you want to try rooting your device.
And btw, this is a development forum, not General or Q&A one. Read carefully before trying to mod this device, or you will end up with an expensive brick.
please contact me on hangouts i may be able to help [email protected]
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
Edit: Link updated
[email protected]_USA said:
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kf...yiH2t-srYBBvN3
Click to expand...
Click to collapse
I"m getting a web page not found 404 when I try that link.
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
Same
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
freeza said:
Same
Click to expand...
Click to collapse
look like chris didnt updated the link,
bdw here you guys go https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
thecdn said:
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
Click to expand...
Click to collapse
You need to restore ramdisk, not recovery_ramdisk.
Pretoriano80 said:
You need to restore ramdisk, not recovery_ramdisk.
Click to expand...
Click to collapse
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
thecdn said:
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
Click to expand...
Click to collapse
Try to also flash kernel : fastboot flash kernel kernel.img
Pretoriano80 said:
Try to also flash kernel : fastboot flash kernel kernel.img
Click to expand...
Click to collapse
No joy yet but I do appreciate all the help.
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Did you tried a factory reset from stock recovery?
Pretoriano80 said:
Did you tried a factory reset from stock recovery?
Click to expand...
Click to collapse
I've tried two factory resets after completing the above mentioned actions. Both times reported they were successful it still won't boot to the os, goes to the EMUI screen after several boot attempts.
Same problem here on a US BKL-L04 =(
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
akasek said:
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
Click to expand...
Click to collapse
Flash stock kernel, ramdisk and recovery ramdisk for your model in fastboot and you'll be able to boot again
Rommco05 said:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Use this tool for flash full fw
Click to expand...
Click to collapse
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Finally back up and running - Thanks Tecalote!
FYI: I am finally back up and running - Tecalote's post worked perfectly (and BKL-L04 update zips are linked earlier in the thread also): https://forum.xda-developers.com/showpost.php?p=76331841&postcount=46
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
try to install twrp and then do hruupdate from twrp
get your files from firmware finder and search xda forums to how to install those files
its very easy and your system will be back in stock format
after that you can try to root and install custom rom
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Hi, what helped you there? I have a similar situation.
"Hi,
I need some advice on what can be done with my Honor View10 as it keeps gracing a bootloop followed by fasrboot mode.
Mine is a C675 variant and I was on 190 when I decided to unroot and update the device to 218. Once that was done, I flashed a patched recovery_ramdisk boot image that was patched using magisk to support it. Worked fine. Did a reboot and it got stuck in a bootloop.
I have tried flashing other patch.imgs too, due instance tried extracting recovery.img of the current version of rom, flashed it, no luck!
Tried flashing the patched version of that, still did not help.
I am on EMUI9, any help please?
Also can anyone help me with the link of one of the latest versions of C675 update please? "
This is what happened to me

Partition error when trying to restore stock recovery with fastboot

I successfully unlocked the bootloader, flashed TWRP, and installed SuperSU, but now I sold my Mate 9, and the guy would like it back to stock. I extracted RECOVERY.img (the stock recovery) from Update.zip, and used the command: fastboot flash recovery_ramdisk RECOVERY.img and got this output:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (54884 KB)...
OKAY [ 1.749s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.796s
Any suggestions come to mind what I may be doing wrong?
No, you can not do that. You can use erecovery to back stock or use dload method (https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656)
gazavn said:
No, you can not do that. You can use erecovery to back stock or use dload method (https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656)
Click to expand...
Click to collapse
With all due respect, don't think all that is necessary. I have been following this comprehensive guide:
https://forum.xda-developers.com/mate-9/how-to/hacking-customizing-managing-huawei-t3589996
and this fellow says I should be able to simply extract the recovery.img from update.zip, and fastboot flash it. If I'm not mistaken you are talking about rebranding it as if I were going to update the phone. I'm not trying to be combative, just seems like a lot of monkeying around...
UPDATE:
I was using the wrong image. I had confused an UPDATE.APP from a different file. Plus I had an olde version of HuaWei Update Extractor. The correct .img file was labeled recovery_ramdis.img, I had been trying RECOVERY.img.

huawei mate 8 bricked rooting

hi guys hi tried to root my mate 8 but something went wrong and it goes in bootloop. now , there are no roms , i tried to flash stock rom unsuccessfully (dload metod it fail, from twrp error 7, hi suite not working, erecovery i can enter but not reset)
i tired to flas boot,system,cust and recovery img but these are the problems
QHC0216219001678 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (29094 KB)...
OKAY [ 0.623s]
writing 'boot'...
OKAY [ 0.589s]
finished. total time: 1.214s
target reported max download size of 471859200 bytes
sending 'cust' (230521 KB)...
OKAY [ 4.904s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 4.914s
target reported max download size of 471859200 bytes
sending 'recovery' (43930 KB)...
OKAY [ 0.938s]
writing 'recovery'...
OKAY [ 0.911s]
finished. total time: 1.851s
target reported max download size of 471859200 bytes
sending sparse 'system' (436384 KB)...
OKAY [ 9.752s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 9.797s
Premere un tasto per continuare . . .
what i can do now? thanks
Which official version you were on last? What else did you do?
It shows partition error which means you must have cross flashed something wrong.
apat26 said:
Which official version you were on last? What else did you do?
It shows partition error which means you must have cross flashed something wrong.
Click to expand...
Click to collapse
i was on the last b582 with emui 5 and android 7. i tried to do the root but it entered in a bootloop and i don`t know how , now there isn`t any rom.
Post your full version. L29C185 or L29C432 ....or.......
apat26 said:
Post your full version. L29C185 or L29C432 ....or.......
Click to expand...
Click to collapse
how i can know this? it was the europe version, i think the L29C185
rikyca said:
my version complete of what? sorry
Click to expand...
Click to collapse
You said B582.
Whats your full build no?
L29C185B582 or L29C432B582 or L29C636B582? or something else?
You are not on chinese AL or DL ...etc, right?
apat26 said:
You said B582.
Whats your full build no?
L29C185B582 or L29C432B582 or L29C636B582? or something else?
You are not on chinese AL or DL ...etc, right?
Click to expand...
Click to collapse
my version was the europe L29C185B582
rikyca said:
how i can know this? it was the europe version, i think the L29C185
Click to expand...
Click to collapse
That is Africa and Middle east. Europe is C432 and Asia is C636
---------- Post added at 09:51 AM ---------- Previous post was at 09:49 AM ----------
Ok...try dloading rollback package and you should be through. On SD Card, not internal memory.
Worked???
apat26 said:
That is Africa and Middle east. Europe is C432 and Asia is C636
---------- Post added at 09:51 AM ---------- Previous post was at 09:49 AM ----------
Ok...try dloading rollback package and you should be through. On SD Card, not internal memory.
Worked???
Click to expand...
Click to collapse
no, i can`t enter in dload mode and in twrp i cant clear cache!! the error is failed to mount `/data`(invalid argument)
failed to wipe dalvik ecc...
rikyca said:
no, i can`t enter in dload mode and in twrp i cant clear cache!! the error is failed to mount `/data`(invalid argument)
failed to wipe dalvik ecc...
Click to expand...
Click to collapse
You said you were able to dload. May be you flashed TWRP after that. Flash Stock recovery and try dload rollback package.
apat26 said:
You said you were able to dload. May be you flashed TWRP after that. Flash Stock recovery and try dload rollback package.
Click to expand...
Click to collapse
in TWRP there is (internal storage 0MB) i thin there is a bad problem. p.s dload continue to not work
rikyca said:
in TWRP there is (internal storage 0MB) i thin there is a bad problem. p.s dload continue to not work
Click to expand...
Click to collapse
Ok...Through TWRP, use Hurupdater and flash all three files you were on last. It will work.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Follow the instructions exactly and change the file names exactly.
apat26 said:
Ok...Through TWRP, use Hurupdater and flash all three files you were on last. It will work.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Follow the instructions exactly and change the file names exactly.
Click to expand...
Click to collapse
Ok thanks I will try it tonight
apat26 said:
Ok...Through TWRP, use Hurupdater and flash all three files you were on last. It will work.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Follow the instructions exactly and change the file names exactly.
Click to expand...
Click to collapse
ok, I`ve installed the official rom but there isn't the keyboard, the updater etc. where I can find the complete version? thanks!!!!! P.s if i press power button + volume down it say: ''your device failed verification and may not work properly....'' the phone still start but sometimes it freeze for 3-4 seconds when i open an app, ex settings. i think something isn't installed. i don't know if the bootloader is just unlock.
rikyca said:
ok, I`ve installed the official rom but there isn't the keyboard, the updater etc. where I can find the complete version? thanks!!!!! P.s if i press power button + volume down it say: ''your device failed verification and may not work properly....'' the phone still start but sometimes it freeze for 3-4 seconds when i open an app, ex settings. i think something isn't installed. i don't know if the bootloader is just unlock.
Click to expand...
Click to collapse
Go to system updater and press look for update. you should get official one again.
apat26 said:
Go to system updater and press look for update. you should get official one again.
Click to expand...
Click to collapse
i've typed that tere isn't the updater
apat26 said:
Go to system updater and press look for update. you should get official one again.
Click to expand...
Click to collapse
If i'm not able to use the emui (because with this limitation isn't a smartphone but a phone?) i can flash a custom rom that not required the root? Thanks
Now you can use dload roll back package. Go back to MM and again upgrade to Nougat.
hi, I've unlock the bootloader on my Huawei mate 8 nxtl29c432. After the reboot the only screen on my phone is
Error mode please update system again
Error!
Func NO 11 recovery image
Error no 2 load failed!
What I can do?! I can't enter in fastboot mode only this screen!!
Looks like you are just playing around. You said all working but few app. Now you landed in error mode.
Well. let the battery dry down totally and switch off.
Then connect your phone to usb pressing vol- button n you will enter fastboot. Rest i leave it upto you to flash.

Categories

Resources