Honor 8 loopboot - some partition errors in the flash - twrp - Honor 8 Questions & Answers

I can not find a way to avoid errors in the flash process, I attach some images.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.

AngelLestat said:
I can not find a way to avoid errors in the flash process, I attach some images.
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.
Click to expand...
Click to collapse
Flash EMUI8 and immediately wipe system and extract and flash https://github.com/phhusson/treble_...v300.l/system-roar-arm64-aonly-vanilla.img.xz (this is the compressed form extract using 7zip)
so that you flash system-roar-arm64-aonly-vanilla.img. into system partition.

AngelLestat said:
I can not find a way to avoid errors in the flash process, I attach some images.
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.
Click to expand...
Click to collapse
I think that the error 255 might be a bad download
-------------------------------------------
PLEASE TRY THIS SOLUTION
I think that the solution to fix this device is "Hurupdater" you just have to rename the 3 firmware files and flash the hurupdater in the same folder using twrp. It should flash the firmware file and also it keeps the bootloader unlocks. it works on honor 8. Hurupdater is also a better way to flash updates.
[Tool] [HuRUpdater] [0.4] [Flash official firmware in recovery
Here I present my tool to flash Honor stock firmware in TWRP recovery. I have tested it on all currently available firmwares for Honor 9 STF but still this tool is beta. HuRUpdater Huawei Recovery Updater Flash official firmware zip files Can...
forum.xda-developers.com
--------------------------------------------
But if hurupdater method does not work (Im sure Hurupdater would actually work though)
1. Restart device
2. When your on the "Your device has been unlocked and can't be trusted" quickly hold volume button (make sure you are doing it fast enough), it should boot into a stock recovery look alike screen.
3. Now click button that says about downloading latest firmware. Pick your wifi. DONE
Beware that this will relock the bootloader and also put your device on android oreo (EMUI 8)

CHECK_123 said:
I think that the error 255 might be a bad download
-------------------------------------------
PLEASE TRY THIS SOLUTION
I think that the solution to fix this device is "Hurupdater" you just have to rename the 3 firmware files and flash the hurupdater in the same folder using twrp. It should flash the firmware file and also it keeps the bootloader unlocks. it works on honor 8. Hurupdater is also a better way to flash updates.
[Tool] [HuRUpdater] [0.4] [Flash official firmware in recovery
Here I present my tool to flash Honor stock firmware in TWRP recovery. I have tested it on all currently available firmwares for Honor 9 STF but still this tool is beta. HuRUpdater Huawei Recovery Updater Flash official firmware zip files Can...
forum.xda-developers.com
--------------------------------------------
But if hurupdater method does not work (Im sure Hurupdater would actually work though)
1. Restart device
2. When your on the "Your device has been unlocked and can't be trusted" quickly hold volume button (make sure you are doing it fast enough), it should boot into a stock recovery look alike screen.
3. Now click button that says about downloading latest firmware. Pick your wifi. DONE
Beware that this will relock the bootloader and also put your device on android oreo (EMUI 8)
Click to expand...
Click to collapse
Nice but once hurupdater does not work and need to relock bootloader, the bootloader can be difficult to unlock again.

jjgvv said:
Nice but once hurupdater does not work and need to relock bootloader, the bootloader can be difficult to unlock again.
Click to expand...
Click to collapse
I think you can try the "Your device has been unlocked and can't be trusted" trick and from what i posted then clicking download latest firmware. But it would relock bootloader and put it into EMUI 8. Unlocking the bootloader is also easy anyways, once you get the bootloader code, you can write it down or put it in notepad to always have the bootloader unlock code.
The Honor 8 also has 2 recoveries, one from holding vol up from "Your device has been unlocked and can't be trusted" and also the normal recovery partition where you usually put twrp in (vol up + power button)
You can also use hurupdater to go from android 8 to android 7. The hurupdater method should work because it flashes all the partitions including "Cust.img".
If you dont want to use Hurupdater, then I think you should just do "Your device has been unlocked and can't be trusted" method because it downloads stock firmware including "Cust.img".
And also you dont have to flash "Cust.img". If you extract "Cust.img" you can manually the files on to /cust then It should maybe work.

CHECK_123 said:
I think you can try the "Your device has been unlocked and can't be trusted" trick and from what i posted then clicking download latest firmware. But it would relock bootloader and put it into EMUI 8. Unlocking the bootloader is also easy anyways, once you get the bootloader code, you can write it down or put it in notepad to always have the bootloader unlock code.
The Honor 8 also has 2 recoveries, one from holding vol up from "Your device has been unlocked and can't be trusted" and also the normal recovery partition where you usually put twrp in (vol up + power button)
You can also use hurupdater to go from android 8 to android 7. The hurupdater method should work because it flashes all the partitions including "Cust.img".
If you dont want to use Hurupdater, then I think you should just do "Your device has been unlocked and can't be trusted" method because it downloads stock firmware including "Cust.img".
And also you dont have to flash "Cust.img". If you extract "Cust.img" you can manually the files on to /cust then It should maybe work.
Click to expand...
Click to collapse
lol 2 recovery partitions
anyway maybe update.app can be extracted?

jjgvv said:
lol 2 recovery partitions
anyway maybe update.app can be extracted?
Click to expand...
Click to collapse
Yes, there is also a app called "ZArchiver" in Play Store. It can extract "Update.app". But I dont think it can extract .img files. You may need a computer to extract the .img files.

CHECK_123 said:
Yes, there is also a app called "ZArchiver" in Play Store. It can extract "Update.app". But I dont think it can extract .img files. You may need a computer to extract the .img files.
Click to expand...
Click to collapse
.img is easy, if you get system.img then nice, but i cant extract the super.img where system.img is in it.

Related

702L to 703 help. Pretty please.

Hi,
I could really use a hand with this guys. I haven’t rooted anything for years and I'm really struggling with this one. Not sure if I'm being a massive idiot or not with this.
I have a Mediapad X2 702L and I want to get all of the latest Huawei updates.
Am I correct in assuming that if I tricked it into thinking it was a 703L then I would get the updates?
If so, how would I do this?
I have spent the last few hours trying to solve this question. I'm really not the type of person who asks for help in an era of Google and I'm sorry if I come across as a noob.
I have managed to unlock the bootloader but that's as far as I can get.
Every attempt to get TWRP flashed onto my 702 has failed. I've spent all day scouring different guides but they all seem to differ slightly from one-another or omit details that halt my progress.
I would be very grateful if someone could give me an idiot's guide (or point me to one) that I can follow step by step.
Thank you for your help.
phorenzik said:
Hi,
I could really use a hand with this guys. I haven’t rooted anything for years and I'm really struggling with this one. Not sure if I'm being a massive idiot or not with this.
I have a Mediapad X2 702L and I want to get all of the latest Huawei updates.
Am I correct in assuming that if I tricked it into thinking it was a 703L then I would get the updates?
If so, how would I do this?
I have spent the last few hours trying to solve this question. I'm really not the type of person who asks for help in an era of Google and I'm sorry if I come across as a noob.
I have managed to unlock the bootloader but that's as far as I can get.
Every attempt to get TWRP flashed onto my 702 has failed. I've spent all day scouring different guides but they all seem to differ slightly from one-another or omit details that halt my progress.
I would be very grateful if someone could give me an idiot's guide (or point me to one) that I can follow step by step.
Thank you for your help.
Click to expand...
Click to collapse
That's why I made this
http://forum.xda-developers.com/mediapad-x2/general/mediapad-x2-unlock-bootloader-root-guide-t3212325
From the input of several 702L users, If you are on Android 5.0 you have to flash this twrp instead. Then flash the new 5.1.1 recovery after you update to B109.
https://docviewer.yandex.com/?url=ya-disk-public%3A%2F%2FvI5Y3Obeku4qzIrtHfPviJPL3yhTpSABBi9V4fM0UpU%3D%3A%2FRecovery%2FTWRP%2FX2_TWRP_CN_kangvip.rar&name=X2_TWRP_CN_kangvip.rar&c=5654a1e6657e
You need to flash it in fastboot. The instructions for how to flash are all over these threads. Just use the search on the left.
Thanks. Your guide was the one I was using, mostly. I came unstuck during the TWRP bit. I can't find a good enough fastboot step by step guide. All the guides I've seen so far confuse me.
I'll attempt another go. Already managed to change the DPI to 300 so that has hugely improved things.
phorenzik said:
Thanks. Your guide was the one I was using, mostly. I came unstuck during the TWRP bit. I can't find a good enough fastboot step by step guide. All the guides I've seen so far confuse me.
I'll attempt another go. Already managed to change the DPI to 300 so that has hugely improved things.
Click to expand...
Click to collapse
Download this and unzip it on your PC:
https://docviewer.yandex.com/?url=ya-disk-public%3A%2F%2FvI5Y3Obeku4qzIrtHfPviJPL3yhTpSABBi9V4fM0UpU%3D%3A%2Fadb%2Bfastboot%2Fplatform-tools.zip&name=platform-tools.zip&c=5654bd2be042
Download the twrp (second one in my guide) and put the file in the same folder. Then turn off your phone. Plug in the USB cable into the computer. Hold in volume down and power and then you should be in bootloader mode. Then on your PC, right click while holding in shift on the folder with the android tools and twrp in it and. choose open command prompt here. Then type in fastboot flash recovery twrp_cn.img
To fastboot flash something, simply put the img file you want to flash in with the Android platform tools folder and open a command prompt to that folder and type in fastboot flash and whatever the file you want to flash is. So if you wanted to flash a stock system you would type in fastboot flash system system.img. There are only 5 things you can flash with the x2. These are the things and the commands.
fastboot flash system system.img
fastboot flash cust cust.img
fasttboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash cache cache.img
Fastboot flash recovery recovery.img
If you fastboot flashed those you'd be back to a stock ROM (whichever stock one you downloaded)
You only have to fastboot flash recovery recovery twrp_cn.img though. Then flash one of my KangVIP ROMS and you'll be on b109 and pretty much up to date.
Thank you. I really appreciate the time you took to help.
I've tried to flash TWRP but this happens.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
EDIT: Oooooooh, might have figured it out, will update soon.
Right then.
Finally rooted.
The problem was with the boot-lock. Despite it stating it was unlocked, it doesn't appear that it was. I re-applied the unlock code and everything has been smooth sailing from there.
Couldn't get the English theme to work on TWRP though. Had to do it in Chinese.
I'll probably post again when I balls up the flash procedure
phorenzik said:
Right then.
Finally rooted.
The problem was with the boot-lock. Despite it stating it was unlocked, it doesn't appear that it was. I re-applied the unlock code and everything has been smooth sailing from there.
Couldn't get the English theme to work on TWRP though. Had to do it in Chinese.
I'll probably post again when I balls up the flash procedure
Click to expand...
Click to collapse
Make a folder on your internal storage called TWRP (if there is already one just leave it)
Make another folder in the TWRP folder called theme (caps matter so make sure the theme is all small letters)
Make sure the TWRP file says ui.zip put the ui.zip in the theme folder (again, caps matter, it should be all small letters)
When you boot TWRP it will be in English
That's exactly what I have done but TWRP is in Chinese. Could it have something to do with Windows messing with the theme when I rename it as a .zip?
I've tried extracting the files and renaming the extracted folder to ui.zip and I've tried renaming the untouched downloaded theme file to ui.zip but neither works.
EDIT: Done it.
I was literally typing ui.zip for the rename but I just renamed it to ui (without the .zip extension) and it worked.
phorenzik said:
That's exactly what I have done but TWRP is in Chinese. Could it have something to do with Windows messing with the theme when I rename it as a .zip?
I've tried extracting the files and renaming the extracted folder to ui.zip and I've tried renaming the untouched downloaded theme file to ui.zip but neither works.
EDIT: Done it.
I was literally typing ui.zip for the rename but I just renamed it to ui (without the .zip extension) and it worked.
Click to expand...
Click to collapse
If you want to enjoy 703's B110 ROM on your 702L you may go to:
http://forum.xda-developers.com/mediapad-x2/development/rom-stock-b106-gapps-t3230585
Thanks. I tried to flash your B109 rom last night but it got stuck in a boot loop.
I got it back to B015_KangVIP
I have a 702L but it is showing as a 703L in the system settings due to it running the KangVIP
Do I need to boot the 702L or 703L B110 rom?
Will the system settings show all the correct info after flashing?
Sorry for all the questions.
phorenzik said:
Thanks. I tried to flash your B109 rom last night but it got stuck in a boot loop.
I got it back to B015_KangVIP
Can I just TWRP your new B110 Rooted Debloated With GAPPS GEM-703L directly onto my phone, or would I need to something before this step?
Sorry for all the questions.
Click to expand...
Click to collapse
You need to be AT LEAST on B106 before you can flash anything higher eg. B109 or B110 because B015 is EMUI 3.0 with Android 5.0.5 whereas B106 onwards is EMUI 3.1 with Android 5.1.1 - major differences
Since you're on B015_KangVIP you're almost there. Follow guide below by "eenap" to reach B106 with TWRP 5.1.1 first
http://forum.xda-developers.com/mediapad-x2/general/how-to-flash-rom-x2-gem-703l-gem-702l-t3228915
After you reach B106 with twrp 5.1.1 then you can head to the below URL for custom B109 or B110 and preserve your 702L's Dual SIM selection:
http://forum.xda-developers.com/mediapad-x2/development/rom-stock-b106-gapps-t3230585
kpcheang2 said:
You need to be AT LEAST on B106 before you can flash anything higher eg. B109 or B110 because B015 is EMUI 3.0 with Android 5.0.5 whereas B106 onwards is EMUI 3.1 with Android 5.1.1 - major differences
Since you're on B015_KangVIP you're almost there. Follow guide below by "eenap" to reach B106 with TWRP 5.1.1 first
http://forum.xda-developers.com/mediapad-x2/general/how-to-flash-rom-x2-gem-703l-gem-702l-t3228915
Click to expand...
Click to collapse
This is where I come unstuck. I've tried to follow that guide and failed many times. I just don't get it.
Ever since I have been on KangVIP b015 rom, I can't get my PC to see the phone, so any flashing via adb cmd prompt won't work.
The PC just sees the SD card of the device because it thinks it's a memory card. It won't connect in HiSuite either.
phorenzik said:
This is where I come unstuck. I've tried to follow that guide and failed many times. I just don't get it.
Ever since I have been on KangVIP b015 rom, I can't get my PC to see the phone, so any flashing via adb cmd prompt won't work.
The PC just sees the SD card of the device because it thinks it's a memory card. It won't connect in HiSuite either.
Click to expand...
Click to collapse
You don't need ADB to work to flash the IMGs. Just go into bootloader (assuming your X2 is unlocked) then you can individually flash the 4 IMGs from the B106.
From B015 to B106 (after flashing and reboot) you need to reset/erase to get the B106 to properly work after setup
---------- Post added at 05:34 PM ---------- Previous post was at 05:18 PM ----------
I had the same issue before like you but once I managed to get the B106 working my ADB connection started working again
Why the hell can't I get this to work?
What am I missing?
Here's where I'm at:
1. Got the stock 703L ROM
2. Extracted the files this guide told me to via the Huawei extractor tool
3. Booted my device into fastboot
fastboot flash boot BOOT.img (successful)
fastboot flash cust CUST.img (successful)
fastboot flash recovery RECOVERY.img (successful)
fastboot flash system SYSTEM.img (ERROR CANNOT LOAD SYSTEM.IMG)
Needless to say, phone is now boot looping.
I can get into fastboot so what do I need to do to fix this?
Really getting frustrated by this now. I'll happily pay someone for a step by step guide that can fix this and get me running.
Thank you
EDIT. Out of sheer frustration, I kept at it, doing exactly the same thing and after about the 4th attempt, the system.img was flashed. No idea why it wouldn't work the previous times as I did nothing different.
Now it's booting up to the language selection screen and then rebooting in a loop. SIGH!
phorenzik said:
Why the hell can't I get this to work?
What am I missing?
Here's where I'm at:
1. Got the stock 703L ROM
2. Extracted the files this guide told me to via the Huawei extractor tool
3. Booted my device into fastboot
fastboot flash boot BOOT.img (successful)
fastboot flash cust CUST.img (successful)
fastboot flash recovery RECOVERY.img (successful)
fastboot flash system SYSTEM.img (ERROR CANNOT LOAD SYSTEM.IMG)
Needless to say, phone is now boot looping.
I can get into fastboot so what do I need to do to fix this?
Really getting frustrated by this now. I'll happily pay someone for a step by step guide that can fix this and get me running.
Thank you
EDIT. Out of sheer frustration, I kept at it, doing exactly the same thing and after about the 4th attempt, the system.img was flashed. No idea why it wouldn't work the previous times as I did nothing different.
Now it's booting up to the language selection screen and then rebooting in a loop. SIGH!
Click to expand...
Click to collapse
Do ensure you have the same ADB version as stated in the guide. (v1.42)
Rightfully you should be able to flash the system.img with no errors but usually the ADB drivers can cause issues if they were the incorrect ones.
Try this, instead of 4 you flash 6 IMGs extracted from the stock B015. You need to ensure you extracted them properly using the Huawei Extractor Tool. Each time you extract there is a corresponding header file which can be ignored because we only need the .img file.
1) boot.img
2) cache.img
3) cust.img
4) recovery.img
5) userdata.img
6) system.img
Then reboot. You need to get to B015 stock in order to go to B106.
Thanks.
Done that. I'm now on B015.
Currently doing OTA to B106
I've lost root access somehow, will that make a difference to anything?
phorenzik said:
Thanks.
Done that. I'm now on B015.
Currently doing OTA to B106
I've lost root access somehow, will that make a difference to anything?
Click to expand...
Click to collapse
Good you're making progress. Losing root now won't affect.
Once you reached B106 you can flash the B110 with root and Gapps to regain root.
Update to B106 failed.
Pretty much ready to throw the phone against the wall now.
phorenzik said:
Update to B106 failed.
Pretty much ready to throw the phone against the wall now.
Click to expand...
Click to collapse
Actually yes it is expected to fail because yours is a 702L - I had the same failure but this "failed" step is neccesary to do a bridge partial jump to B106.
Now go to bootloader and flash the same 6 IMGs from B106 ROM.
After that reboot and do initial setup.
Then do Settings--->Reset erase and reboot clean B106.
Finally flash twrp_5.1.1 so that you will have custom recovery in order to flash those custom B110 rooted plus Gapps plus Dual Sim.

I messed up with Huawei Mate 9. Please Help.

Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?

Honor 8 impossibility to install stock ROM

Hello everyone !
I need some help because I am stuck with an Honor 8 that is not working. I have tried to install AOSP 8.0 [Open Kirin] and maybe I have done something wrong. Indeed, after flashing AOSP the device will be able to boot and start on it but Wi-Fi, SMS and GAPPS cannot work. So I need your help because I have tried all methods in order to install & flash the stock ROM i.e. dload + 3 buttons on start result : the installation stucked at 5% and Huawei eRecovery result : Getting software info. from server failed.
I have already flash BOOT.img, SYSTEM.img and RECOVERY.img but I cannot access to recovery i.e. start+ vol. + and with fastboot flash I cannot flash CUST.img and my computer says : failed not have the right permissions to write on this partition, something like that. I do not know if it has importance but I have already erase all with TWRP and in addition, erase calendar stockage when my devices worked properly. So what I needed is a 100% stock device on EMUI with maybe things that I have erased and I do not know what is.
Thanks for reading and helping
My devices :
- Honor 8 FRD-L09
- SD Card Sandisk 64 Go
- USB-C cable
- A computer under Ubuntu 18.04 with adb and fastboot commands installed
Ok so.. Since you said you've flashed boot and recovery, all you need to do is a dload install. There's a guide on xda here. As far as the aosp, I know it works because I ran it for months on mine. Seems you made an error somewhere in the installation process, but that's besides the point. Do a quick search for the dload installation method and follow it to a point and you should get back to stock no problem
Ok I will try one more time but I have already done this method and it stuck at 5%...
Thanks for reply
EDIT: Ok the dload method fonctionnated, in fact to install stock ROM we need first to install firmware package and then install vendor package.
Thanks, subject close.

Bootloop and eRecovery fails, dload fails - no way to recover

Hi people,
I need some help here and I hope anybody got an idea to get my FRD-L09 (C432 - on B521 base with OpenKirin's RROS Oreo) to work again somehow.
Situation is: After a failed attempt to upgrade the firmware base to B562 my device is now bootlooping, and goes into eRecovery, after one or two tries to boot, which is then offering to "Download and recovery". That fails at getting package info ("Getting package info failed").
Next I tried to install full OTA-PV package (extracted UPDATE.APP) via dload folder on my SD - that fails at 5 % ("Software install failed!"). For this I took the service ROM from this thread (see post #24 for Oreo version) and version B521 for FRD-L09C432 from firmware finder.
I also tried to get into TWRP 3.2.0 from Huawei Multi-Tool by TeamMT but this suddenly reboots after a few seconds everytime - so this is also useless (I tried several TWRP versions I found - maybe 'bootcomplete=false'?). I hoped to flash the extracted .img files with it.
Flashing the extracted .img files (specially the vendor image, because I think I destroyed it somehow) via fastboot also fails with error "command not allowed". Replacing the eRecovery with TWRP is also not possible (not allowed).
Flashing to system, recovery_ramdisk, kernel etc. via fastboot is possible without any problems - which shows that bootloader and frp are both unlocked.
Info btw: in this few seconds in TWRP I could see that vendor partition cannot be mounted - which shows that it's likely an error on this partition.
Is there any way to flash any "other" (vendor) partition via fastboot? Or do you guys have any ideas to this what I can try - except for bringing this thing to service center for repair :silly:? And please ask, if something is not clear or I forgot to give any info.
Any help is very appreciated.
cypher187 said:
Any help is very appreciated.
Click to expand...
Click to collapse
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.
cypher187 said:
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.
Click to expand...
Click to collapse
In my case eRecovery save my a*s 2 times
ScardracS said:
In my case eRecovery save my a*s 2 times
Click to expand...
Click to collapse
Usually dload did the job well for me. I don't know why it didn't in that case.
But I'm still looking for an easy way to upgrade the firmware base for future use (in case we get some) :laugh:
Next time just use HiSuite windows version with Firmware Finder's DNS trick to flash any stock ROM version what you need, only works with version 5.0.2.300. I've got the same issue and recoered by this method ease.
You can download it here.

Downgrade/Unbrick Honor 9 with IMEI fix

First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
View attachment nvme.zip: got it from [url]https://t.me/huaweihax[/URL]
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.​Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).​
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
Close DC-Phoenix and open ChimeraTool. Cholera will see your phone, if everything went right. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot:
Code:
fastboot flash kernel kernel.img
It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting.
Code:
fastboot reboot
If it doesn’t boot, go back into fastboot. Flash TWRP:
Code:
fastboot flash recovery_ramdisk twrp.img
.
Go into TWRP by holding volume-up and power. Be sure your phone isn't charging, otherwise it will boot into erecovery. In TWRP you need to flash NVME.zip (you need to flash it 4 times, it's a security precaution). After flashing NVME.zip it should be possible to fastboot flash vendor and reboot correctly.
Check your security patch in settings/about. If it's lower then June, then you've done everything right. Before you use HCU, you need to flash the right recovery_ramdisk (recovery_ramdis) again. Extract it from update.app and flash it with fastboot. Reboot again and let now the magic begin with HCU.
Check in settings/about if you can see your IMEI. If so, then you can use Hisuite to go back to an official firmware.
Hi, I followed your instructions, and unfortunately it did not work. I was able to revive the phone but only with the latest (STF-L09 8.0.0.385 (C432) - STF-L09C432E2R1P5B175 (9.0.1.175)) firmware, everything else is XLOADER error ... My problem now is that I use the IMEI can not fix. Do you know what I can do there? Thank you.
tomek5 said:
Hi, I followed your instructions, and unfortunately it did not work. I was able to revive the phone but only with the latest (STF-L09 8.0.0.385 (C432) - STF-L09C432E2R1P5B175 (9.0.1.175)) firmware, everything else is XLOADER error ... My problem now is that I use the IMEI can not fix. Do you know what I can do there? Thank you.
Click to expand...
Click to collapse
Did you tried the last steps with flashing a lower firmware version with fastboot? I think it also could work when you're on B385.
Item 8, which firmware "update.app recovery_ramdisk" B385 or B366?.
There is no recovery_ramdisk there are both recovery_ramdis.
tomek5 said:
Item 8, which firmware "update.app recovery_ramdisk" B385 or B366?.
There is no recovery_ramdisk there are both recovery_ramdis.
Click to expand...
Click to collapse
You have to use B385. Recovery_ramdisk is equal to the partition named recovery_ramdis.
TWRP (stf-twrp-zxz-0.3.img) hangs on startup image.
Item 5. Should I flash everything (kernel, system, vendor and ramdisk) or just kernels?
tomek5 said:
TWRP (stf-twrp-zxz-0.3.img) hangs on startup image.
Item 5. Should I flash everything (kernel, system, vendor and ramdisk) or just kernels?
Click to expand...
Click to collapse
Weird. Yes, you have to flash the four files.
I did everything that flashed the firmware (STF-L09C432B378 (8.0.0.378)). All without success, always the same, as soon as I flashe the kernel, the system, the manufacturer and the Ramdisk starts the phone to Honor picture and boots again into the Fastboot. TWRP will not work anymore.
fastboot flash kernel KERNEL.img
fastboot flash system SYSTEM.img
fastboot flash ramdisk RAMDISK.img
fastboot flash vendor VENDOR.img
tomek5 said:
I did everything that flashed the firmware (STF-L09C432B378 (8.0.0.378)). All without success, always the same, as soon as I flashe the kernel, the system, the manufacturer and the Ramdisk starts the phone to Honor picture and boots again into the Fastboot. TWRP will not work anymore.
fastboot flash kernel KERNEL.img
fastboot flash system SYSTEM.img
fastboot flash ramdisk RAMDISK.img
fastboot flash vendor VENDOR.img
Click to expand...
Click to collapse
Have you tried booting with volume up and power button pressed? If the blue screen comes up, you can stop pressing the power button. Did you already ones succeeded to get into TWRP?
yes, here I come to the erecovery.
tomek5 said:
yes, here I come to the erecovery.
Click to expand...
Click to collapse
You have to unplug your phone. It may not be charging when you try to get into TWRP.
OK, I did it, the IMEI is back. Did it without TWRP. After flashing the kernel, system, vendor and ramdisk I did a Factory Reset. Then HCU.
Thank you for your help!!!
Clarification
waterboy1602 said:
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
View attachment 4766798: got it from https://t.me/huaweihax
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.​Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).​
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
View attachment 4766797
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
View attachment 4766799
Close DC-Phoenix and open ChimeraTool. If everything went right, shall Chimera see your phone. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot:
Code:
fastboot flash kernel kernel.img
It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting.
Code:
fastboot reboot
If it doesn’t boot, go back into fastboot. Flash TWRP:
Code:
fastboot flash recovery_ramdisk twrp.img
.
Go into TWRP by holding volume-up and power. Be sure your phone isn't charging, otherwise it will boot into erecovery. In TWRP you need to flash NVME.zip (you need to flash it 4 times, it's a security precaution). After flashing NVME.zip it should be possible to fastboot flash vendor and reboot correctly.
Check your security patch in settings/about. If it's lower then June, then you've done everything right. Before you use HCU, you need to flash the right recovery_ramdisk (recovery_ramdis) again. Extract it from update.app and flash it with fastboot. Reboot again and let now the magic begin with HCU.
Check in settings/about if you can see your IMEI. If so, then you can use Hisuite to go back to an official firmware.
Click to expand...
Click to collapse
Just for clarification, am sorry if am being a dummy, Step 3: after closing DC phonix, do i use chimera tool for only checking the phone's visibility or I close it again and flash with DC phonix? Please help
Trig18 said:
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
: got it from https://t.me/huaweihax
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.
Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
Close DC-Phoenix and open ChimeraTool. If everything went right, shall Chimera see your phone. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot: It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting. If it doesn’t boot, go back into fastboot. Flash TWRP:
Just for clarification, am sorry if am being a dummy, Step 3: after closing DC phonix, do i use chimera tool for only checking the phone's visibility or I close it again and flash with DC phonix? Please help
Click to expand...
Click to collapse
You should use Chimera to flash the firmware.
Thanks
waterboy1602 said:
You should use Chimera to flash the firmware.
Click to expand...
Click to collapse
Thank you very much , my device is now fully operational on EMUI9 though I used Dc phonix to flash it in upgrade mode.
Thanks again ??
Hi, waterboy1602!
Are you sure that for HCU works only with security patches LOWER than June 2018 ?
I am trying to find out exactly this dates, and firmware to downgrade.
BTW. On 4pda admins wrotes that it is not possilbe to downgrade to no_gpu_turbo version.
Do you know something about it ?
daemonserj said:
Hi, waterboy1602!
Are you sure that for HCU works only with security patches LOWER than June 2018 ?
I am trying to find out exactly this dates, and firmware to downgrade.
BTW. On 4pda admins wrotes that it is not possilbe to downgrade to no_gpu_turbo version.
Do you know something about it ?
Click to expand...
Click to collapse
Yes, after a lot of trial and error I found out that it only works with a firmware lower then June 2018. I know that most people say it's impossible to downgrade to no_gpu_turbo. I found this way to work with my phone. I've put a lot of time into it to find this way. I hope it will also work for you.
Hi, such a question, what should I do if I short-circuited the wrong contacts and after flashing the phone is forever detected as a comport and will not turn
DydoserLolekDrago said:
Hi, such a question, what should I do if I short-circuited the wrong contacts and after flashing the phone is forever detected as a comport and will not turn
Click to expand...
Click to collapse
Honestly I have no idea. If the testpoints don't work anymore, I dont think you have a lot of options.
how exactly do i ground the testpoint?
i connect it with gnd? or just press it with the
paperclip?
can it break the phone?

Categories

Resources