Database Info

Possibly Hardbricked Honor 8

Hey there Guys, first of all thanks for takeing the time and reading through this post.
I have used the search function on this board and on google to an unhealthy extend the last 5 Days because no matter what i try there is always something in the way of every method i have tried to the extend that i almost accept the fact that my phone might be Hardbricked in terms of internal memory.
So lets get on with some data.
Im using the Honor 8 FRD-L09 with currently no OS whatsoever.
The Device is:
-Rooted
-Fully Unlocked (Bootloader, OEM, FRP, Debugging Mode (Enabled before Brick)
I Bricked my Honor 8 when i tried to use the Backup function of TWRP to later change the OS from EMUI 5 to AICP
The first try to change to AICP failed, saying for whatever reason that i cannot install this Update on a EVA-L09 Device, (which is strange since the Phone clearly says FRD-L09 on the back aswell as responding good to all past upgrades that i did , which were all for FRD-L09), so i chose to rollback to the Backup, however the Backup was corrupted in the process somehow and so the phone is currently without any OS as i couldnt reinstall the original Backup.
Ok so now for stuff i have tried and the errors i recieve while doing that.
ERecovery
After ERecovery is connected to any WIFI it spits out the error that no Packages can be found.
Fastboot Flashing
I have tried to install the Stock EMUI 4 Boot.img and then use the Huawei Update Extractor to extract the files from the UPPDATE.APP after i made sure that i have the correct firmware downloaded (The oldest possible, FRD-L09C432B101).
I can flash the boot and recovery images just fine, but the System and Cust images throw me the following errors:
System.img Error
fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (427769 KB)...
OKAY [ 9.631s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 9.666s
Cust.img Error
flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (416830 KB)...
OKAY [ 8.920s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 11.151s
I have furthermore tested all other FRD-L09 Firmwares up to 130 and even the new B320 for EMUI 5 (for which i installed the EMUI 5 Boot.img) aswell as trying to use:
ZIP Flashing
I have tried to use the following command:
fastboot flash zip UPDATE.APP , which spits out the following error:
fastboot flash zip UPDATE.APP
target reported max download size of 471859200 bytes
sending 'zip' (81444 KB)...
OKAY [ 1.746s]
writing 'zip'...
FAILED (remote: Command not allowed)
finished. total time: 1.761s
I have then tried to lock and unlock the OEM to fix the Command not allowed issue which however did not work out.
MicroSD Updating
I have tried the method of using a MicroSD to install the above Update.APP's in a dload folder in the Root of the card with the stock recovery, however no matter what firmware or what Boot.img or what Stock Recovery.img i use, i always get the Software Incompatibility error.
TWRP Direct Recovery and ADB Sideloading
I have tried the method of directly installing or Sideloading the files through ADB with the help of TWRP, but i get the errors that either /data or /system or /internalstorage cannot be mounted.
I have tried the solution suggested on a few promising youtube videos to simply try a combination of formating to a different type and then back aswell as repairing and then trying again, which worked for /system and /internalstorage, but /data is still not able to mount.
So as you can see i have pretty much tried every trick in the book to get my Phone unbricked, however non of those methods work and im getting desperate.
If any of you have more ideas as to what i could try, please post them here.

Go onto MoDaco honor 8
Google it.
There is a guy called Paul O'Brien on there he will help you sort it out

@ newsupast
have you found a solution?
I have same problem with my FRD-AL10.
Also have checked MoDaCo, but help is very rare.
I've written to Huawei-Support to ask for a rollback-package, but they told me to ask my local support.
The have not replied my question.

Root: Stuck at "Your device is booting now"

Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!

if you have the boot backup then restore it.

venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.

if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip

I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img

Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).

Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery

Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.

V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.

venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .

Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.

Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.

Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone

question
​
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.

[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now

nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).

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.

Can't get into recovery mode

Hi.
After trying to upgrade my rooted P20 eml-l09 c605 with EMUI 9.x, I couln't get into recovery mode anymore (on button + vol up)
What I did was flash original ramdis.img and recovery_ramdis.img to unroot it, so i could upgrade it directly from the phone, but something bad happened so I couldn't get the recovey menu anymore.
Help please.
PS: (Bootloader is unlocked)
This message appears when I try to flash recovery_ramdisk
- Flashing TWRP recovery
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.577s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.590s

Where did you find the original ramdisk image from?
I need it too because i accidently flashed a TWRP version that doesent work

I can't flash anything, even with the original ramdisk (downloaded from firmware finder).
I really don't know what to do.
My phone is an EML-L09C605, it is working and rooted.
Only I can get to fastboot menu.

I still haven't got a solution but, Is downgrading it the way to follow?
Help please.