Related
Hello guys,
I had some problems with my Honor 6x L21 so I tried to flash new custom ROM that I didn't like in the end. I tried to revert back and found update.app method. I somehow relocked my bootloader and now tried to install update.app which fails at 5 % and says it is not compatible.
Now, I have erecovery with me that can get nothing after connecting to wifi. No update from SD Card option available.
When I try to unlock bootloader again, it fails.
Also, when I run command 'fastboot oem get-bootinfo' the following lines do come in result:
<bootloader> unlocked
OKAY [0.009s]
Finished.
However, my phone shows Phone Relocked and FRP lock.
Any help guys?
@amannan: I have a US BLN-L24, I was able to use the dload method to roll back to Marshmallow from Nougat. I'm not sure why it sometimes fails at 5%, I think Huawei recently implemented something to cause the update to fail if you haven't passed an online verification check. So basically, no upgrading offline for some of the newer firmwares, someone correct me if I'm wrong. I think it has something to do with Nougat too.
In your case, all hope isnt lost as long as you can access eRecovery and fastboot. What you need to do is find the stock MM packages for your device. This will most likely consist of a small rollback file and a much larger firmware file. Go search Huawei's downloads section on their website until you find what you need, use your model as a reference point. There should also be a PDF file with instructions in it, read it.
For each of the 2 files you get, extract the zips, make a folder called dload on your MicroSD (not internal phone storage). In my case I had to first place the update.app file from the rollback zip into the dload folder, boot to eRecovery (hold volume up and volume down, then hold Power, let let of Power when logo appears but continue to hold the other keys). From there the file will automatically flash. Then I had to extract update.app from the large firmware zip and put in dload, repeat same process again. You should be back on MM.
If either file wont flash then go download Huawei Firmware Extractor. Use it to extract boot.img and recovery.img from the rollback zip's update.app, then boot to fastboot mode while phone is powered off. Plug in a MicroUSB charger into phone then plug other end into PC.
Then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Make sure to install drivers for the phone first, just install HiSuite on Windows is easiest way. For ADB and fastboot, install '15 seconds adb fastboot" (Google it). If the terminal on your PC says something like "file not found", then either use the cd command (change directory) to move working directory to boot.img/recovery.img location, or move the files to C:\adb.
Once you're back up and booting you can then proceed to bootloader unlock, root, ROM flashing, etc.
Hope this helped!
AnonVendetta said:
@amannan: I have a US BLN-L24, I was able to use the dload method to roll back to Marshmallow from Nougat. I'm not sure why it sometimes fails at 5%, I think Huawei recently implemented something to cause the update to fail if you haven't passed an online verification check. So basically, no upgrading offline for some of the newer firmwares, someone correct me if I'm wrong. I think it has something to do with Nougat too.
In your case, all hope isnt lost as long as you can access eRecovery and fastboot. What you need to do is find the stock MM packages for your device. This will most likely consist of a small rollback file and a much larger firmware file. Go search Huawei's downloads section on their website until you find what you need, use your model as a reference point. There should also be a PDF file with instructions in it, read it.
For each of the 2 files you get, extract the zips, make a folder called dload on your MicroSD (not internal phone storage). In my case I had to first place the update.app file from the rollback zip into the dload folder, boot to eRecovery (hold volume up and volume down, then hold Power, let let of Power when logo appears but continue to hold the other keys). From there the file will automatically flash. Then I had to extract update.app from the large firmware zip and put in dload, repeat same process again. You should be back on MM.
If either file wont flash then go download Huawei Firmware Extractor. Use it to extract boot.img and recovery.img from the rollback zip's update.app, then boot to fastboot mode while phone is powered off. Plug in a MicroUSB charger into phone then plug other end into PC.
Then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Make sure to install drivers for the phone first, just install HiSuite on Windows is easiest way. For ADB and fastboot, install '15 seconds adb fastboot" (Google it). If the terminal on your PC says something like "file not found", then either use the cd command (change directory) to move working directory to boot.img/recovery.img location, or move the files to C:\adb.
Once you're back up and booting you can then proceed to bootloader unlock, root, ROM flashing, etc.
Hope this helped!
Click to expand...
Click to collapse
Dear AnonVendetta, Thank you so much for the help. I was able to use the dload method. I read somewhere that the last firmware version needs to be updated using dload method. I had B361 before it got all messed up so tried that update and it started working.
Also, the fastboot won't flash any img file since the FRP was locked somehow.
Thank you for the help
@amannan: Glad it worked out, you must have already made progress before I posted, your response was too quick.
I do believe you cant flash anything via fastboot if the bootloader is still locked.
I've only owned my Honor 6X for about 2 weeks, I've had to do an emergency recovery several times due to various issues. This is my first Huawei but I've owned many Android devices before, and rooted/custom ROMmed most of them, so I'm just a newbie to Huawei but not Android in general. I'm getting the hang of things.
Good luck!
amannan said:
Dear AnonVendetta, Thank you so much for the help. I was able to use the dload method. I read somewhere that the last firmware version needs to be updated using dload method. I had B361 before it got all messed up so tried that update and it started working.
Also, the fastboot won't flash any img file since the FRP was locked somehow.
Thank you for the help
Click to expand...
Click to collapse
Yes, dload method is the only way to restore the device in such scenario. If frp is locked then condition is worse as you can not flash anything but only dload will help you. Correct package should be flashed and will succeed.
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
prestonmcafee said:
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
Click to expand...
Click to collapse
By a generic system image, you are referring to wanting to install an aosp image (treble ROM), correct?
Yes.
prestonmcafee said:
Yes.
Click to expand...
Click to collapse
And obviously you still have your bootloader unlock code?
Also what Mate 9 version do you have and what exact firmware is it running?
I can help ya out no problem. Just obviously want to make sure you avoid going through that again
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Sorry, MHA-L29 8.0.0.360 (C567)
prestonmcafee said:
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Click to expand...
Click to collapse
Oh...You're already bootloader unlocked that makes it even easier.
I'm using the system.IMG form the thread below this paragraph. Tried a few different aosp ROMs and it seems to be the best so far. Aside from a couple things of course. And the honor 8 Pro is the same CPU, GPU found in the mate 9.
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564.
In the main post of that thread, just follow step 2 and 3 and you'll be good to go for having an aosp ROM.
As for magisk/root... You can follow my guide below that I posted the other day. Just let the aosp ROM boot up once first. Also I can extract the ramdisk.IMG you'll need if you can't once you check it over.
https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Basically in a nutshell to get setup on an aosp ROM is as follows
1 Download the ROM from the first thread i posted
2 Extract the system.img to where your adb folder is
3 Run command prompt from there
4 With your phone powered off. Hold the volume up button and connect it to your computer (fastboot screen)
5 Run command fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset
8 Reboot the phone and should be good to go
Need to do first boot on its own before rooting
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
prestonmcafee said:
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
Click to expand...
Click to collapse
Yeah, fairly happy about it. A few bugs though but nothing major. Get better standby drain and about the same SOT time as EMUI. The only thing that is lacking is the camera in aosp doesn't use both cameras.
There is the stock camera port (works with magisk) but it's lacking a few things like video recording doesn't work... And umm not sure what else.
I needed to install an update, enable developer options and enable OEM unlocking (which was greyed out) before it would install. Here is my earlier post:
Dang, didn't work. Here is what I did.
-reset phone, but did not enable developer options.
-extracted and placed system.img in the minimal fastboot and adb folder. Ran a command prompt with administrative rights (win 10)
-shut off and connected Huawei mate 9 by USB, holding vol up
-vol up brought the EMUI restore screen. Shut off and tried again, same outcome. So shut off and tried vol down, and that brought up the fastboot screen. It reported phone unlocked but FRP locked.
-ran command "fastboot flash system system.img" and get:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 11.167s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 11.183s
I suspect this is due to the FRP locked condition.
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
prestonmcafee said:
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
Click to expand...
Click to collapse
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
OK, now that I have it up and running, here is the procedure I used, fixing what are either typos or variations because my system was slightly different. I unlocked the bootloader using instructions from:
http://www.teamandroid.com/2017/04/08/huawei-mate-9-unlock-bootloader/
I used Minimal ADB and Fastboot from
https://forum.xda-developers.com/showthread.php?t=2317790
I downloaded and extracted the system image from the link Wirmpolter provided:
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564
Here is a slightly edited set of instructions that worked for me:
a. unlock bootloader
b. reset phone
c. enable developer mode (settings/system/about phone tap on build number until developer mode is enabled), enable OEM unlock and USB debugging
d. check that FRP unlock and bootloader unlock worked by booting into fastboot screen (for me, hold VOL DOWN while booting)
1 Download the ROM from the thread above
2 Extract the system.img to where your adb folder is
3 Run command prompt from there (or use MA&F's desktop icon, which does the same thing)
4 With your phone powered off. Hold the volume DOWN button and connect it to your computer (fastboot screen)
5 Run command: fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset [eRecovery didn't have this option, so I rebooted a couple of times while holding vol up and it eventually gave me the option to factory reset]
8 Reboot the phone and should be good to go
Up and Running!
Wirmpolter said:
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
Click to expand...
Click to collapse
I'm up and running. Thanks! So far, the only glitches are:
While Android can see and format the SD card (a Samsung 64GB), the SD card is invisible over a USB connection and Google Maps and my music player can't see it. File explorer and copy files to the SD card, so the SD card works.
The camera is terrible, but you have a fix for that.
I'm quite lost about how to install Magisk and a camera module
At the risk of asking too much, I have another request. I'm looking at how to install the stock camera on my Mate 9 with the AOSP, and here is my pathetic understanding of the steps.
First, I looked at your (Wirmpolter) instructions:
1. Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/app...mless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
2. If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
3. Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Here are some questions:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager -- this is an android app? Do I sideload it?
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Finally, the camera image is here:
https://forum.xda-developers.com/showpost.php?p=75848917&postcount=2
It isn't clear to me how to flash using Magisk, but perhaps that will be obvious once I have magisk operating.
prestonmcafee said:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
Click to expand...
Click to collapse
Firmware Finder (they have Windows desktop and Android apps for it, and there's also http://pro-teammt.ru/firmware-database/ which does the job just as well, though it's all in Russian.)
Find the FullOTA-MF firmware that corresponds to your model, download the 'update.zip' that goes with it - on the website, it's under the link 'update' in the same row. If you do it on your phone in the Firmware Finder app, hit "Download" on the relevant detail screen and it'll prompt you for which files you want.
Once you've got the update.zip, extract it, you'll find a file UPDATE.APP, which is what the extractor wants. If it throws up an error, disable CRC checking of the extracted content. (I don't recall what the label for it is and I don't have it installed on the machine in front of me...); and yes, you'll want RAMDISK.img from it.
prestonmcafee said:
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Click to expand...
Click to collapse
Magisk Manager wants to create a patched ramdisk image. When it updates, it'll want to update the ramdisk image on your device (which it'll be able to do since it's running with root privileges itself anyway), but for the first pass, it needs that image provided and for you to manually flash it.
Thanks!
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
prestonmcafee said:
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
Click to expand...
Click to collapse
The magisk manager app apk you just run on your phone to install it, no side loading required.
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
That worked
prestonmcafee said:
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
Click to expand...
Click to collapse
That seems to have worked.
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?
Bricked my phone by doing the following:
Honor View 10 ROMs are compatible with P20 Pro, I installed and used them all. Then the other day they made a mod that force the EMUI 9 update so I ran it. The mod ended rebranding my entire phone to Honor View 10 followed by boot loops like crazy. So then I went into twrp and tried to format thinking it would help. It ended up deleting everything including eRecovery. The only this I had access to was fastboot. Yes I brought this on my self lol. I paid a lot for Funky Huawei but nothing worked. I tried every tool they had.
Fix: (Turns out my phone's structure is now EMUI 9\Android 9)
1- Downloaded my phone image (CLT-L04 - EMUI 9 version), extracted the update.app file from it.
2- Used EMUI extractor app to extracted everything from the update.app file (Lots of image files)
3- Noticed userdata.img wasn't in the extracted files so I downloaded multiple images that are similar models to my phone until I found it.
4- Used fastboot command to flash the userdata.img, followed by eRecovery.img, followed by the rest I pulled from that update.app file.
after about three reboots I was back into my phone except I now have EMUI 9.
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
QuazIqbal said:
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
Click to expand...
Click to collapse
Can you try this.
Files that you will be downloading are,
update.zip
update_full_CLT-L29_hw_eu.zip (Or whatever model of phone you have)
Get them here by searching for your model and click filelist
Prep:
a. Rename update_full_CLT-L29_hw_eu.zip to update_all_hw.zip
b. Download this Flash tool and extract in to a folder in your PC
c. Copy update.zip and update_all_hw.zip to ZIPS-HERE folder (you can find this folder where you have extracted Flash tool
How to flash Firmware
1. Double click to run the file cmd-here.exe. It opens command prompt in the same folder where you are.
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.
Vedrick said:
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.
Click to expand...
Click to collapse
Thanks for offering your help. Mine case looks different....
I have tried this, after flashing twrp in the fastboot the device fails to boot into twrp recovery, it's all black, only fastboot is accessible in the black screen.
I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?
przival said:
I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?
Click to expand...
Click to collapse
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.
QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone
Deano1889 said:
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.
Click to expand...
Click to collapse
I will do my best to answer tomorrow, God willing. Please wait
---------- Post added at 09:04 PM ---------- Previous post was at 08:55 PM ----------
black_1986 said:
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone
Click to expand...
Click to collapse
After this process your bl will be in 'locked' state. If you had my kind of downgrade brick the imeis and serial will number will not be disturbed. You may simply use your old bl code to unlock. However I messed up my oeminfo but due to my own stupidity, I'm looking to restore my imei and will try to unlock again.
If possible, could you share the files you use?
WARNING
By doing this you may lose your data, this is intended for when you have nowhere else to turn to.
Back Story
Hi All,
Like a massive child I stupidly jumped on the Pie bandwagon away from a very well maintained Honor 10 ROM which ran beautifully on my P20 Pro..
After restoring EMUI, the PIE update quickly made itself visible, so i took a deep breath and committed.
After the installation, I tried to install a bunch of ROM's, I messed up a bit.
Anyway, what I found was, I was unable to recovery from eRecovery OR HiSuite, so I then found myself on the wobbly road that is restoring each parition via the bootloader using fastboot, tried to install just the recovery_ramdisk, didn't work, tried to install, kernel / cust / system / recovery_ramdisk..... STILL Didn't work.
So i downloaded another firmware, this time the exact version i was using albeit for the L-09 and not the L-29, I needed to extract the update part of the zip then read it using a tool called firmware extractor.
Ton of files in there, the files i just mentioned which are all .img files and some others.
In the end i needed several to get a perfect restore which has worked every single time without fail.
As it was a massive ballache and a learning curve for me as I'd never done it before, so I thought i'd share my experience and the files required on Mega so there aren't any ads blocking your way Yaay, also what to do and where to obtain the firmwares from my experiences.
Hope it helps someone avoid the pain I had to go through when downloading firmwares for 5 hours at a time, wasn't fun.
Good luck, any questions let me know. :good:
START HERE
*NOTE: You can do this from scratch by downloading the firmware for your device, i required 9.0.0.190 for the L29 - c432.
The best place I found was this site https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=105974
They require an account to be made but besides that they were faster and had more choice.
Once you have the firmware you'll need the Extractor, then you'll need to move several of the files into the ADB folder for flashing, see below...
Anyway, moving on........
FILES
At the foot of this guide is a link, inside it is everything you should require in order to complete this guide
ADB - Move this folder to the root of C, it should be like this C:\ADB (reason for this is it's much easier to navigate to, most people will already have this)
IMG Files for 9.0.0.190 - All of the file names you see below are img files which we'll be using to un-brick / recover / restore your device to a functional state.
Move all of them after downloading to the ADB folder in C:\ADB
CACHE.img
CUST.img
ERECOVERY_RAMDI.img
KERNEL.img
RECOVERY_RAMDIS.img
USERDATA.img
VENDOR.img
SYSTEM.img
EMUI Extractor - Not a part of this guide but you will need it should you need to download your own firmware and obtain the above files.
Pre-requisites
- A device on a maximum firmware of 9.0.0.190 (If you are on a higher firmware, then use the link above to obtain it)
- A device variant of either L-09 or L-29 (others may work but i have not tested)
- A device variant of c432 (the 782 may work but i have not tested)
- Access to the bootloader (white screen with vol down and power whilst connected to a laptop)
- Drivers so that fastboot / adb commands can be sent to your device (I won't show how to do this, it's pretty standard stuff)
- I have an unlocked bootloader myself and OEM unlocking is on (REQUIRED)
- A Windows based PC /Laptop and a functional USB-C cable. (I'm sure you can
GUIDE
On your computer / laptop
STEP 1 Download all the files from the mega link provided.
STEP 2 Copy the ADB Folder to the root of C: so it looks like this
C:\ADB
STEP 3 Open the folder called "IMG Files for 9.0.0.190" Copy the .IMG files to the ADB folder so they are loose.
STEP 4 Press Start / Windows key and type in cmd then press enter, a black window will appear
STEP 5 In the black window type the following:
cd c:\adb then press Enter
STEP 6 Connect your phone to your laptop using the USB-C cable and allow it to be seen by windows
On your Phone
STEP 7 Press and hold the power button and volume down, don't let go, your screen will go blank, once it turns back on, release the power key but continue holding vol down, a white screen should appear, you can now release the power volume key, you are now in fastboot mode and can input commands.
On your computer / laptop
Step 8 Click the CMD window and type in the following commands, you will have to wait for them to go all the way through, some take longer ie: System.img
*NOTE: For speed you can use the tab key to pre fill certain words or files, so if you've typed in "Fastboot flash cust "
You could then press the tab key and scroll through the files in the folder.
eg: if you were to press enter with this command listed fastboot flash cust c after pressing tab it would say fastboot flash cust CUST.img
PRESS ENTER AFTER EACH COMMAND, MAKE SURE EACH ONE COMPLETES.
fastboot flash cust CUST.img
fastboot flash cache CACHE.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash userdata USERDATA.img
fastboot flash kernel KERNEL.img
fastboot flash vendor VENDOR.img
fastboot flash system SYSTEM.img
STEP 9 Once they've all been flashed, in CMD simply type the below command and allow the device to boot up, you can disconnect now.
fastboot reboot
If all has worked and it should have, then you will have a stock ROM of PIE on 9.0.0.190
You can then root and use your device as you see fit.
Here is the link to the said files (WHICH WILL NOT BE TAKEN DOWN )
NOTE: they actually now have, sorry
https://mega.nz/#F!qdMWDKZA!5PIsAnakvENegV-4GPWKdg
Any questions, please ask away and i'll do what i can to help
c:\ADB>fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (176429 KB)...
OKAY [ 4.121s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.130s
OEM is LOCKED
@mdda7
You must have an unlocked bootloader.
titi66200 said:
@mdda7
You must have an unlocked bootloader.
Click to expand...
Click to collapse
bootloader is unlocked
but
OEM is locked
mdda7 said:
bootloader is unlocked
but
OEM is locked
Click to expand...
Click to collapse
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
dladz said:
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
Click to expand...
Click to collapse
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
mdda7 said:
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
Click to expand...
Click to collapse
OEM unlocking needs to be off mate, 108 shouldn't matter but i believe that it's the version that has the OEM greyed out.
There is a way around it but i'm not sure.
any way?
mdda7 said:
any way?
Click to expand...
Click to collapse
Certainly not with this method as you don't meet the pre-requisites.
That being said I suppose some kind of low level flash tool may work, like i said before a paid for service maybe?
Lets find out everything there is to know.
So your bootloader is unlocked.
Have do you have TWRP installed?
Did any of the images i've listed actually flash successfully?
Have you tried to use eRecovery? or Hi Suite (neither of these worked for me hence this guide)
Beyond that i suppose the only way would be a paid service but their pre-requisites may be the same as mine. In that case I would say you're out of luck, afaik this guide is essentially the lowest you can go. I don't believe anything will work without OEM unlocking turned on.
How do you get onto the firmware you're currently on ? 108 and what state is the phone in right now?
What works? Whats accessible?
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
~clumsy~ said:
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
Click to expand...
Click to collapse
Haha no worries fella.
dladz said:
Haha no worries fella.
Click to expand...
Click to collapse
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
chrissyyyw said:
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
Click to expand...
Click to collapse
Weird. Not sure pal. This is what I did when I was stuck. Did you read everything and follow to the letter? A higher or same firmware?
On fastboot reboot the pc saying it's disconnected is correct. Should have come on.
Does anything ever come on screen?
Thank you, life saver!!
:good:
Johnny Eng said:
Thank you, life saver!!
Click to expand...
Click to collapse
You're very welcome Use the thanks button buddy :good:
dladz said:
:good:
You're very welcome Use the thanks button buddy :good:
Click to expand...
Click to collapse
Done buddy ?
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Johnny Eng said:
Done buddy
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Click to expand...
Click to collapse
Which FW version did you flash? I’ve got the same on .282
chrissyyyw said:
Which FW version did you flash? I’ve got the same on .282
Click to expand...
Click to collapse
As i'm still on 190 I wouldn't know this, but would it be possible that userdata isn't actually a part of the update app no more?
Seeing as it still works I would assume that is the case.
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
chrissyyyw said:
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
Click to expand...
Click to collapse
No because you're going to be picking them via fastboot anyway, I don't believe the name matters.
The ones in the update I used were not named like that IIRC.