OTA failed with BootLoader locked/Stock Recovery !? - Ascend Mate 7 Q&A, Help & Troubleshooting

Hi Guys, I need some help
I am on MT-LV09xxxB137SP03/KitKat 4.4.2/EMUI 3.0 build. Recently I got a notification about an intermediate update before LolliPop: xxxB145: so I tried a OTA update which failed (no specific error, just "software update failed"). I downloaded manually the update, put that in the dload folder and tried a local update, failed for the same reason.
My phone is rooted via KingRoot (amazingly worked) but the bootloader is locked, so I wonder why the update fails.
With KingRoot there is an option to "Remove Root Permission" which I tried, thinking that it was the culprit. Then I tried to update and still it failed.
I was under the impression an OTA update fails only with a unlocked bootloader/custom recovery, but this does not seem the case. Any idea about what should I do?
Thanks,
Anubis
.

Hey man,
Just wanted to let you know: I have the EXACT same problem. Huawei AM7, KingRoot, OTA xxxB145 fail. I cannot further help, as I have no solution myself.
Hope someone can help.

Flash the stock image. Kingroot may have left some files behind even though you "uprooted" this the system is still seen as modified for purposes of the ota.

Milly7 said:
Flash the stock image. Kingroot may have left some files behind even though you "uprooted" this the system is still seen as modified for purposes of the ota.
Click to expand...
Click to collapse
Did a factory reset, still software update fail. Then tried to install stock rom over the stock rom, but software update still fails...

Did you try local update from internal or external SD card?

Yes, tried that, but same 'software update fail' problem...

Are you sure that you are flashing the correct file for your specific variant? You cannot flash TL10 on L09, etc. It will give the error if you do that.

I found the problem:
1) When installing an OTA there is a check on the file system first and if it fails, the update is aborted
2) KingUser/KingRoot leaves the file system in a dirty state (there is a kinguser.apk left in /system/app) so the check fails
3) to install a clean OTA you need to have a clean recovery so you need to:
3.1) unlock the bootloader (to be able to install a stock recovery)
3.2) download the update (e.g. ...B145) you want to install
3.3) use the Huawei extractor to get the recovery.img file from the package
3.4) flash the stock recovery
3.5) upgrate with the OTA
I discovered it step by step. Basically you need to unlock the bootloader to fix things and therefore it is a waste of time to user KingRoot/KingUser in the first place: but faster/cleaner to unlock the bootloader and install SuperSU.
Anubis

Still doesn't work I had the same but also had twrp recovery, I have my unlock code but no matter what adb I use I get remote command not allowed for trying to get stock recovery back or parse file failed with unlock code.
Any ideas would be much appreciated.

Anubis1965 said:
Hi Guys, I need some help
I am on MT-LV09xxxB137SP03/KitKat 4.4.2/EMUI 3.0 build. Recently I got a notification about an intermediate update before LolliPop: xxxB145: so I tried a OTA update which failed (no specific error, just "software update failed"). I downloaded manually the update, put that in the dload folder and tried a local update, failed for the same reason.
My phone is rooted via KingRoot (amazingly worked) but the bootloader is locked, so I wonder why the update fails.
With KingRoot there is an option to "Remove Root Permission" which I tried, thinking that it was the culprit. Then I tried to update and still it failed.
I was under the impression an OTA update fails only with a unlocked bootloader/custom recovery, but this does not seem the case. Any idea about what should I do?
Thanks,
Anubis
Click to expand...
Click to collapse
u need to be unrooted to proceed ota. ..

Okay,
I have been trying over and over but there is no way I can perform an OTA. Here's the situation:
- The bootloader is unlocked
- Current Firmware: MT7-L09 ... B137SP03. According to the updater it should go with MT7-L09 ... B145
- OTA fails: on WiFi, local update (SD), forced (three buttons)
- In the systems/app folder I have this "KingUser.apk" app, has been left hanging there by KingRoot when I removed it
I was told to reinstall the stock recovery and try a local update, here's what I did:
1) I downloaded again the current FW (B137SP03) from here: http://www.huaweiblog.de/huawei/firmwareupdate-b137-fuer-mate-7-ota/
2) extracted update.app, opened with the Huawei Extractor, got recovery.img from update.app
3) rebooted the Mate 7 (vol down + power) in fastboot mode
4) flashed the stock recovery: fastboot flash recovery recovery.img, got an ok
5) rebooted
6) put update.zip in the dload folder of the SD, performed a local update --> failed as usual
Is there anything I am doing wrong?
Anubis

Anubis1965 said:
6) put update.zip in the dload folder of the SD, performed a local update --> failed as usual
Is there anything I am doing wrong?
Anubis
Click to expand...
Click to collapse
"UPDATE.ZIP" ??? I wonder that stock recovery may flash a zip file.
Check elsewhere in this forum the matter of the trash files left by kingroot, intead...

tuddu said:
"UPDATE.ZIP" ??? I wonder that stock recovery may flash a zip file.
Check elsewhere in this forum the matter of the trash files left by kingroot, intead...
Click to expand...
Click to collapse
Did you read what I wrote?
The OTA is called update.zip and you can perform an update by putting it into the dload folder of the SD card and then using the updater or with a forced update (three buttons boot).
The recovery file is called recovery.img and it is inside the archive update.app which is inside update.zip
Anubis

Correct. But you wrote "put the update.zip file in the SD folder".
I suppose you mean the EXTRACTED update.app file in the SD folder.
That's it.
Anyway, peace and love.

tuddu said:
Correct. But you wrote "put the update.zip file in the SD folder".
I suppose you mean the EXTRACTED update.app file in the SD folder.
...
.
Click to expand...
Click to collapse
No. I put the update.zip file in the dload folder of the SD card.
About removing KingRoot/KingUser after the self-removal option failed, I have only heard about installing SuperSu. Are you referring to it? Because that would imply to install a custom recovery, install supersu, clean-up, unroot via supersu, reinstall the stock recovery and then perform finally the OTA.
Paolo

:good:

oh well... Did everything (KingUser was removed with the support of SuperSuMe), reverted back to the stock recovery and guess what? Software update failed as before.
I guess I'll have to stay with my firmware until lollipop or a custom rom based on lollipop will come
Anubis

Anubis1965 said:
oh well... Did everything (KingUser was removed with the support of SuperSuMe), reverted back to the stock recovery and guess what? Software update failed as before.
I guess I'll have to stay with my firmware until lollipop or a custom rom based on lollipop will come
Anubis
Click to expand...
Click to collapse
Hello,
tuddu is wright. The file which must be put in the dload folder is update.app and no update.zip.

grofock said:
Hello,
tuddu is wright. The file which must be put in the dload folder is update.app and no update.zip.
Click to expand...
Click to collapse
I wish it would be that easy. It makes absolutely no difference whether I put in dload update.zip or its unzipped content.
the message is always "software install failed".
Anubis

Anubis1965 said:
I wish it would be that easy. It makes absolutely no difference whether I put in dload update.zip or its unzipped content.
the message is always "software install failed".
Anubis
Click to expand...
Click to collapse
You should do a clean install ( 3 buttons ) of the full B137 firmware, it was happening also with my phone and I solved the issue in that way.
After the flash you'll be on a clean stock B137 so you can put the "update.zip" in the "dload" folder ( it's an OTA update, not a full update.app firmware ) and be able to get the latest B145 :good:

Related

[Q] Question on updating through ota.

Hey. I was wondering if you could help me update my phone to the latest ota update. I'm rooted and have xposed installed, and anytime I try to update the zip fails to install. I've also tried removing xposed, but it still didn't work.
Any suggestions?
Marco_Mena said:
Hey. I was wondering if you could help me update my phone to the latest ota update. I'm rooted and have xposed installed, and anytime I try to update the zip fails to install. I've also tried removing xposed, but it still didn't work.
Any suggestions?
Click to expand...
Click to collapse
Use search, you can't use OTA on a rooted phone as rooting alters system files that the OTA expects to NOT be altered.
scott_doyland said:
Use search, you can't use OTA on a rooted phone as rooting alters system files that the OTA expects to NOT be altered.
Click to expand...
Click to collapse
In another thread they told me that I can update if my phone is rooted and with stock recovery.
What you can do is flash a custom recovery and then after copy the outs file from /cache to your PC. On your PC modify the updater-script and repack the zip file and flash it on your phone through custom recovery.
You can even unpack the contents of OTA. zip and manually copy it in your /system and fix the permissions.

FRD-L19C432B120 Stock Recovery

Hello!
I own a FRD-L19C432 device loaded with B120 FW, TWRP flashed to erecovery, the recovery partition is stock (?) since I haven't flashed anything on it and it is also rooted.
A few days ago, I got the notification of the availability of B131 update. According to some info I've read over the web, the erecovery isn't/wasn't used for anything, so I tried my luck and proceeded with updating operation from UI. It booted to recovery, failed to install, showed some error and booted to OS, that stills on B120.
Introduction made, the question is:
I already downloaded the FRD-L19C432B131 full update zip, can I simply flash it through the dload method, or, must I first unroot and flash stock B120 recovery in order to perform the dload flash?
If so, where can I get the B120 stock recovery and erecovery? I'm not finding it while using the Firmware Finder app by Team MT.
Hope you can give some help.
Tks,
RM
you can extract the recovery.img using huawei update extractor and then flash via adb or the multitool
jkccl9 said:
you can extract the recovery.img using huawei update extractor and then flash via adb or the multitool
Click to expand...
Click to collapse
Thank you for trying to help, but that's not what I'm asking in first place:
I already downloaded the FRD-L19C432B131 full update zip, can I simply flash it through the dload method, or, must I first unroot and flash stock B120 recovery in order to perform the dload flash?
Click to expand...
Click to collapse
Thank you.
RM
omartins said:
Thank you for trying to help, but that's not what I'm asking in first place:
Thank you.
RM
Click to expand...
Click to collapse
well you have to unroot and install stock recovery before being able to update
jkccl9 said:
well you have to unroot and install stock recovery before being able to update
Click to expand...
Click to collapse
Stock recovery from B120, right? If so, where can I find this recovery since I'm not finding the full B120 FW zip?
omartins said:
Stock recovery from B120, right? If so, where can I find this recovery since I'm not finding the full B120 FW zip?
Click to expand...
Click to collapse
Try huawei firmware Updater by team mt (can't remember full name) to search for the last update and extract using tool from post 1 ^^
omartins said:
Hello!
I own a FRD-L19C432 device loaded with B120 FW, TWRP flashed to erecovery, the recovery partition is stock (?) since I haven't flashed anything on it and it is also rooted.
A few days ago, I got the notification of the availability of B131 update. According to some info I've read over the web, the erecovery isn't/wasn't used for anything, so I tried my luck and proceeded with updating operation from UI. It booted to recovery, failed to install, showed some error and booted to OS, that stills on B120.
Introduction made, the question is:
I already downloaded the FRD-L19C432B131 full update zip, can I simply flash it through the dload method, or, must I first unroot and flash stock B120 recovery in order to perform the dload flash?
If so, where can I get the B120 stock recovery and erecovery? I'm not finding it while using the Firmware Finder app by Team MT.
Hope you can give some help.
Tks,
RM
Click to expand...
Click to collapse
It's weird and sad to hear that you flashed twrp to erecovery.
Let me explain u briefly what erecovery does . when u use dload method (while flashing an update.app) , erecovery extracts all .img and .bin files and later it flashes the each file (image files) to its respective partition .
In ur case. The normal stock recovery flashed the update.zip which was included in the script . but it failed to extract update.app in the update.zip and finally output u got is error.
Solution:
The only solution for this problem is ..
Download a full update package of stock ROM...
Extract Update.app (use huawei update extractor) and then find erecovery.IMG
Install adb and fastboot drivers ..
Put your phone in fastboot mode .
Connect to PC ..
In the terminal (command prompt) , type this command and hit enter .
fastboot flash erecovery erecovery.img
(From here u can reinstall the update.zip ) if it fails .
And then try to shutdown the phone , later put full update.app in dload folder ..
Use the 3 button combination to install full package of update.app and thats it .
It reboots to stock again .besure to take a backup of your data before attempting above step . after everything done check for update from settings and install it normally
hello!
Thanks for a proper answer
At the moment I'm stuck (paused) at the TWRP backup operation, since I don't seem to be able to perform a full back to internal storage (with the previous NEXUS phones I owned it was possible...) I need first to get an USB-C adapter in order to use USB OTG to perform the safety backup.
After That I'll flash B120 stock recovery and erecovery, unroot and dload the new FW version.
Meanwhile, another question: Using the FW Finder APP from Team MT on Windows it gets a FRD-L19C432B131 result, while on the Android version of the same AP it only finds B130, not B131 (?). On the other hand, I can only find the B120 full FW over Android APP, and don't seem to find it while using Windows... Any idea why this occurs?
RM
Hello!
Task accomplished! TWRP full backup made, flashed stock recoveries from B120 and after that flashed B131 update.app though dload method.
Everything went OK except for the fact I got bootloader relocked after the second flash. I miss the simplicity of the Nexus devices...
With the TWRP backup made before I was able to restore most of the definitions though. It would be nice to digg a workaround to flash update.app without getting bootloader relocked...
I wonder if extracting boot, system and recoveries IMGs and flash all this through fastboot wouldn't work!? Did anyone tried?
RM

My honor 8 refuse update

hello, i will try to explain my problem :
My honor was bricked by an error of flash.
I have "repair" it by a way found here on xda : flash boot.img, cust, recovery, system, and after i have could make the update by dload.
Then all was ok under the firmware LO9C432B131.
But now, i can't update to B360...
Before my brick, i had the ota update to B360... but now i have nothing....
If i try the update by dload, it says : "problem compatibility"
I have downgraded to B120 and ota update was good for B131. But nothing for B360
If someone can explain me...thank you so much (actually the phone is no rooted and relocked)
Hi there. Go through the entire rollback procedure and you will be fine: https://forum.xda-developers.com/honor-8/how-to/guide-downgrading-unlocked-rooted-twrpd-t3549281
Put the update.app file in a folder called dload on a SD card. If you haven't got one, flash twrp in fastboot and when in twrp you'll be able to transfer them to internal storage from your pc. Then follow the instruction above. That's how I unbricked mine. Good luck.
sysak said:
Hi there. Go through the entire rollback procedure and you will be fine: https://forum.xda-developers.com/honor-8/how-to/guide-downgrading-unlocked-rooted-twrpd-t3549281
Put the update.app file in a folder called dload on a SD card. If you haven't got one, flash twrp in fastboot and when in twrp you'll be able to transfer them to internal storage from your pc. Then follow the instruction above. That's how I unbricked mine. Good luck.
Click to expand...
Click to collapse
I don't think you understood what OP is saying. He successfully rolled back to MM but he cant go to Nougat anymore.
takichiman said:
I don't think you understood what OP is saying. He successfully rolled back to MM but he cant go to Nougat anymore.
Click to expand...
Click to collapse
Yes, but I believe the issue comes from manual flashing of partitions. I have also tried that when my phone was dead and the recovery and eRecovery always threw "package incompatible" error. I think restoring the entire file system to factory condition (which happens during the rollback process) is the sure best way to fix all issues.
Thanks for your answers,
I finally got the update with the charlie app...(not easy this method !)
But now i don't know if ota will be ok...
I will perhaps do the rollback as you said to restore the entire file system...

How to flash via TWRP a stock ROM in my problematic phone

Hi everyone.
I am facing a LOT of troubles with my phone (as stated in this thread).
Anyway now I have again unlocked bootloader, installed TWRP 3.1.1, rooted but I have a strange ROM installed by a service tech shop after the phone became unusable.
The problem is that this ROM does not show an update option in settings so I am stuck at 1st march security patches.
Here attached my actual Build Prop file.
The ROM seems to be a BLN-L21C900B300 (never heard of this and not even found on Firmware Finder) and the fingerprints show a "test keys" rom:
device: HWBLN-H
Display: BLN-L21C900B300
Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys​
If I try to flash via TWRP a BLN-L21C432B360 (which was my previous stock ROM) it does not work and on TWRP appears the following:
......
write radio image
check_write_data_to_partition
write data error
E; unknown command (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with ERROR: 7
error installing zip file '/external_sd/update_full_BLN-L21_hw_eu_zip'​
I cannot flash the FULL zip file with the core of the ROM but I can luckily flash the data, so I could get back Radio Fm and possibility to install themes....
To make the story short: is there someone who knows what this error is? Maybe I can get a solution.
Moreover: maybe this strange "device: HWBLN-H Display: BLN-L21C900B300 Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys" is preventing me to flash?
Changing build prop file can be useful?
Thanks to all.
Diamantes said:
Hi everyone.
I am facing a LOT of troubles with my phone (as stated in this thread).
Anyway now I have again unlocked bootloader, installed TWRP 3.1.1, rooted but I have a strange ROM installed by a service tech shop after the phone became unusable.
The problem is that this ROM does not show an update option in settings so I am stuck at 1st march security patches.
Here attached my actual Build Prop file.
The ROM seems to be a BLN-L21C900B300 (never heard of this and not even found on Firmware Finder) and the fingerprints show a "test keys" rom:
device: HWBLN-H
Display: BLN-L21C900B300
Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys​
If I try to flash via TWRP a BLN-L21C432B360 (which was my previous stock ROM) it does not work and on TWRP appears the following:
......
write radio image
check_write_data_to_partition
write data error
E; unknown command (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with ERROR: 7
error installing zip file '/external_sd/update_full_BLN-L21_hw_eu_zip'​
I cannot flash the FULL zip file with the core of the ROM but I can luckily flash the data, so I could get back Radio Fm and possibility to install themes....
To make the story short: is there someone who knows what this error is? Maybe I can get a solution.
Moreover: maybe this strange "device: HWBLN-H Display: BLN-L21C900B300 Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys" is preventing me to flash?
Changing build prop file can be useful?
Thanks to all.
Click to expand...
Click to collapse
U should use dload method
Sent from my BLN-L22 using Tapatalk
arshilhonor6x said:
U should use dload method
Click to expand...
Click to collapse
I forgot to mention: dload not working. Always error.
That's why I think TWRP is the only solution
B300 (at least for the BLN-L24) is the first of two update packages to rollback from Nougat to MM. The first update will take you from the latest firmware to B300 and then the second update will complete the rollback to your device's stock firmware.
dload this package to complete the rollback then do a factory reset and wipe cache partition in stock recovery. After that download and update to the latest firmware and proceed to unlock BL and flash twrp and you should be good to go.
Dazed No More said:
B300 (at least for the BLN-L24) is the first of two update packages to rollback from Nougat to MM. The first update will take you from the latest firmware to B300 and then the second update will complete the rollback to your device's stock firmware.
dload this package to complete the rollback then do a factory reset and wipe cache partition in stock recovery. After that download and update to the latest firmware and proceed to unlock BL and flash twrp and you should be good to go.
Click to expand...
Click to collapse
but you mean that I have to downgrade from Nougat to MM again?
And before doing it I have to flash the stock recovery?
My phone was, we can say, flashed in some way by the tech shop to this strange version of Nougat and with the "test keys" fingertips.
With the files you provide I should "dload"?
I do not understand your post.
please explain better.
Thanks.
Diamantes said:
but you mean that I have to downgrade from Nougat to MM again? Yes
And before doing it I have to flash the stock recovery? No
My phone was, we can say, flashed in some way by the tech shop to this strange version of Nougat and with the "test keys" fingertips. Like I said they did half of the rollback process which is why you are on B300 firmware that you cant find available for download
With the files you provide I should "dload"? Yes
I do not understand your post.
please explain better.
Thanks.
Click to expand...
Click to collapse
Download the zip I linked above from Huawei website. Extract the update.app and put it in dload folder on your external SD card and force flash (power vol - vol +). It will flash all the stock images and return your phone to factory firmware android 6.0 EMUI 4.1. It might bootloop after this but booting into stock recovery (power vol +) and perform factory reset followed by wipe cache partition will get you booting. Then you can OTA update to latest firmware and root again.
Well, I will try this weekend. Now the risk to stay without phone during working days is too high
Ah, BTW, thanks for suggestion.
Dazed No More said:
Download the zip I linked above from Huawei website. Extract the update.app and put it in dload folder on your external SD card and force flash (power vol - vol +). It will flash all the stock images and return your phone to factory firmware android 6.0 EMUI 4.1. It might bootloop after this but booting into stock recovery (power vol +) and perform factory reset followed by wipe cache partition will get you booting. Then you can OTA update to latest firmware and root again.
Click to expand...
Click to collapse
Well, I changed my mind and tried anyway now. I was just too curious.
result:
Software install failed.
Incompatibility with current version.
please download the correct update package.​
As usual. Huawei sucks. Full stop.
Diamantes said:
Well, I changed my mind and tried anyway now. I was just too curious.
Click to expand...
Click to collapse
Haha I know the feeling. First time I went to rollback i jumped the gun and said screw it only to have my phone brick and no access to adb/fastboot until the next morning.
As usual. Huawei sucks. Full stop.
Click to expand...
Click to collapse
I agree 100%
Since you have nothing to lose right now just try the whole rollback process. Here is the update that the service center used to get your phone to BLN-L21C900B300. You can try flashing that again through dload or skip to trying to flash this. There are two different firmwares listed as the 2nd part of the rollback and you already said the last one I gave you failed so give this one a shot. Let me know how it works out for you:good:
Dazed No More said:
Haha I know the feeling. First time I went to rollback i jumped the gun and said screw it only to have my phone brick and no access to adb/fastboot until the next morning.
I agree 100%
Since you have nothing to lose right now just try the whole rollback process. Here is the update that the service center used to get your phone to BLN-L21C900B300. You can try flashing that again through dload or skip to trying to flash this. There are two different firmwares listed as the 2nd part of the rollback and you already said the last one I gave you failed so give this one a shot. Let me know how it works out for you:good:
Click to expand...
Click to collapse
nothing mate.
I tried, gives me always error after entering erecovery. Same as above,
Software install failed.
Incompatibility with current version.
please download the correct update package.​
Will try another method suggested in another thread.
Will keep you updated just for your curiosity...
Cheers
Diamantes said:
nothing mate.
I tried, gives me always error after entering erecovery. Same as above,
Software install failed.
Incompatibility with current version.
please download the correct update package.​
Will try another method suggested in another thread.
Will keep you updated just for your curiosity...
Cheers
Click to expand...
Click to collapse
Have you tried the Team MT huawei multitool to flash the images from the firmware? Use the Huawei update extractor tool to get the boot,cust,recovery,system and userdata.img from the firmware you tried to flash and then put them in the unbrick folder in the multi tool. Put phone in fastboot and run the Multi tool and use the unbrick option. I know your phone is not bricked but this way it will flash all 5 images in order through fastboot. You could actually try and flash the most current firmware with this method and avoid having to system update from MM to Nougat.
yes, exactly, I am trying with multitool . another bro suggested me how to do it even if with a slightly different method.
"You need flash the oeminfo via multi tool and then same firmware file for your current version via dload. It should be fixed".
WTF....never sweat so much for a phone. And never had those problems flashing samsung... and I was flashaholic
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Diamantes said:
yes, exactly, I am trying with multitool . another bro suggested me how to do it even if with a slightly different method.
"You need flash the oeminfo via multi tool and then same firmware file for your current version via dload. It should be fixed".
WTF....never sweat so much for a phone. And never had those problems flashing samsung... and I was flashaholic
Click to expand...
Click to collapse
Thats me i guess :silly:
---------- Post added at 08:13 AM ---------- Previous post was at 08:12 AM ----------
Dazed No More said:
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Click to expand...
Click to collapse
I am still learning and everytime its different result . Someitmeit works and sometimes it doesn't
Dazed No More said:
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Click to expand...
Click to collapse
When I go to multitool "unbrick", it asks for custom.img, but in no update.app of my firmware is present.
Moreover now I just can enter erecovery. It does not boot. I can enter fastboot only. Multitool is now not recognizing the phone. Do you know how to proceed?
I put in dload the firmware .app, but it says "software install failed"
Pheew...I managed to have again that fuc..ng C900B300.
I entered fastboot and repeated the unlock bootloader process. That way the phone got a hard reset and started over. Believe me when I say I tried all the methods I knew.
I think there is something locked somewhere in my partitions (I am not an expert of course) that prevent me to do deep modifications. Now I just can TWRP data but not the core. And again I have no update option. I think I am stuck forever at this stage with 1st march patches and nougat 7.0.
I do not think I will be ever able to have Oreo.
Amen. I am really tired to waste my time with this s**t. Next phone will be again a Samsung or One+. Full stop. Stop chinese brands.
Where are you located, Europe?
Yes
Ok bro I really hope this is it. Full firmware BLN-L21C432B151. I already downloaded it myself and checked with extractor tool it has all the images you need. Since you have fastboot back use the multi tool unbrick again and now that you have all the necessary images cross your fingers it will work.
And I agree with you about the phone. Made up my mind im giving this turd to my sister and getting the OP5T in a few weeks.
Thanks. I will do it this weekend. Today I spent 5 hours to get back my configuration after the hard reset with the apps I use for work. Cannot risk again tomorrow.
In another thread, sashank suggested to change OEM file because probably phone doesn't recognize the firmware I want to install.
It didn't work and lead me to start from scratch with the same strange build.
I will try your method but first I must study better the procedure because I don't want to mess up everything and risking to throw the phone in the garbage (where it belongs in the end...).
Thanks.

Possible To Flash Oreo Rom Via TWRP Recovery?

I am currently on Android Nougat stock.
The bootloader has been unlocked and TWRP recovery has been installed.
I would like to update to Oreo but have been unable to do so.
This guide was followed [urlhttp://www.droid views.com/install-android-8-0-oreo-based-emui-8-0-huawei-mate-9/][/url] (but was unable to get past option 4) (I left a space after droid as the link is getting blocked, just put ********** together.)
''Double-click on the Replace_Recovery.bat file in the extracted HWOTA8 folder. This will install TWRP recovery on your device.''
I keep getting a failed notification when trying to do so. The handset was in fastboot mode but refuses to update recovery.
Am I able to update to Oreo with the old TWRP recovery & update it after? I am running the old Nougat version.
Option 7 I also got stuck on. '' Create a folder named HWOTA8 on your device’s internal storage.'' whilst connected via USB to the computer.
I am unable to view internal or external storage when the USB is connected to the computer. When viewing internal/external memory normally I can see items as normal in external SD card but the internal memory files all appear jibberish even in recovery.
What am I doing wrong? I have been unable to find any clear guides of how to update from Nougat to Oreo including flashing the rom, flashing recovery and root.
Thanks for those able to help.
PS. I'm a new Huawei Mate 9 owner and have only just received the device several hours ago which is why I'm rusty. Compared to my previous Sony Xperia XZ Premium it is much more complicated. Sony was far easier to flash recovery and flash roms via recovery.
I am having the MHA-L29 international version.
Device now bootloops after following the guide of flashing SuperSU in recovery. I did what was said and received ''error 9'' after flashing the files.
Now bootloop.
Good news at least recovery is working but unable to boot. How to I update to Oreo with updated recovery & root?
Otherwise is THIS guide safe to follow:
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Could not even get past option 4. ''Do oeminfo backup in twrp,you should have a folder name twrp, inside this folder there is many subfolders.
In last folder there is 2-3 files,those files should be replaced with c636 oeminfo: http://www.mediafire.com/?szws87sk7rrkqr6''
Permission denied error.
kanej2006 said:
Could not even get past option 4. ''Do oeminfo backup in twrp,you should have a folder name twrp, inside this folder there is many subfolders.
In last folder there is 2-3 files,those files should be replaced with c636 oeminfo: http://www.mediafire.com/?szws87sk7rrkqr6''
Permission denied error.
Click to expand...
Click to collapse
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.
ante0 said:
Unless you want to rebrand to a different cust, don't follow this.
Do you know what your current firmware build is?
MHA-LxxCxxxBxxx
Click to expand...
Click to collapse
Good thing I never went ahead with that!
I'm on international MHA-L29C185B182.
Thank goodness I was able to restore Nougat as I backed up with TWRP recovery.
However, what is the easiest way to upgrade to the latest Android Oreo 8? At the moment I'm on stock 7 Nougat but am rooted with TWRP recovery.
kanej2006 said:
Good thing I never went ahead with that!
I'm on international MHA-L29C185B182.
Thank goodness I was able to restore Nougat as I backed up with TWRP recovery.
However, what is the easiest way to upgrade to the latest Android Oreo 8? At the moment I'm on stock 7 Nougat but am rooted with TWRP recovery.
Click to expand...
Click to collapse
Check my post, I edited while you posted this.
Or you can use this one, it's basically the same anyway, only difference is that you use a .bat file: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Use the same steps as I wrote above for downloading the update files as this was not the way to do it when that guide was written.
^ It seems the model I have is not found? After several attempts it is not finding my model.
kanej2006 said:
^ It seems the model I have is not found? After several attempts it is not finding my model.
Click to expand...
Click to collapse
http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C185&firmware_page=0
Here are links you need:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v120294/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...94/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
Rename update_data_full_public.zip to update_data_public.zip and update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
There is a B371 too, but it was released before b370 so probably a test build.
That guide in OP seems to be a mixup. It uses the HWOTA8 files, which are for Oreo, so that's probably why it gave you errors.
ante0 said:
http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C185&firmware_page=0
Here are links you need:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v120294/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...94/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
Rename update_data_full_public.zip to update_data_public.zip and update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
There is a B371 too, but it was released before b370 so probably a test build.
That guide in OP seems to be a mixup. It uses the HWOTA8 files, which are for Oreo, so that's probably why it gave you errors.
Click to expand...
Click to collapse
Thank you so much ante0 for all the information, it was very helpful. I am now downloading the above three files. Once complete I will rename them as mentioned and flash hwota7_update.zip in TWRP recovery. Will let you know shortly the outcome!
Cheers ante0, finally got my phone fully updated to Android 8 Oreo following your guide. Thank you so much! If it was not for you this would not have been possible!
The other links I was looking at were outdated as you mentioned and the instructions you provided were better. I appreciate your time to help me.
Upon booting, my EMUI version is now 8.0 and Android Version 8.0.
I will now follow this link for getting root:
https://forum.xda-developers.com/mate-9/how-to/discussion-root-mate9-oreo-emui-8-0-how-t3712495
@ ante0, I was able to get recovery and root but had to once again unlock bootloader...
kanej2006 said:
@ ante0, I was able to get recovery and root but had to once again unlock bootloader...
Click to expand...
Click to collapse
Great. I would suggest Magisk but that's up to you to decide
Bootloader getting locked is normal when updating Nougat to Nougat and Nougat to Oreo. Oreo to Oreo is stays unlocked.
ante0 said:
Great. I would suggest Magisk but that's up to you to decide
Bootloader getting locked is normal when updating Nougat to Nougat and Nougat to Oreo. Oreo to Oreo is stays unlocked.
Click to expand...
Click to collapse
I did not see any guide for Magisk, guess I missed it.
Anyway there are pros and cons for both, though I also prefer Magisk. Either way they both do the job, root access.
All is good now. I am very happy with the phone. Still not even been 24 hours since I received it yet already the bootloader has been unlocked, TWRP recovery and root. Nice :good:
Great and very helpful thread. thanks for everyone who's contributed to it. I'm trying to do the exact same thing coming from ROM Aur. Do you think I can use the same exact process is yours coming from a custom ROM? Did you have to do the boot loader unlock in order to Root? If there are no custom roms then perhaps the boot loader unlock is unnecessary? In order to install Magisk to root, what are the prerequisits? Do I need to reinstall TWRP? If so , is there a link to the correct version? Are there any other pointers that you can give me that you found out while doing this whole process? Thank you so much
kanej2006 said:
I did not see any guide for Magisk, guess I missed it.
Anyway there are pros and cons for both, though I also prefer Magisk. Either way they both do the job, root access.
All is good now. I am very happy with the phone. Still not even been 24 hours since I received it yet already the bootloader has been unlocked, TWRP recovery and root. Nice :good:
Click to expand...
Click to collapse
---------- Post added at 01:33 AM ---------- Previous post was at 01:02 AM ----------
Thanks for the guide!! Very helpful. However, Before I can even start following it, I'm running into some issues. The challenge that I'm facing is that I'm currently on a custom ROM (ROM AUR) and I do not know what my firmware build is. The box only tells me what the model number is and it's the MHA-L29. how would I find my firmware build ? The phone was purchased at bestbuy in the US.
Thanks again
ante0 said:
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.
Click to expand...
Click to collapse
seti007 said:
Great and very helpful thread. thanks for everyone who's contributed to it. I'm trying to do the exact same thing coming from ROM Aur. Do you think I can use the same exact process is yours coming from a custom ROM? Did you have to do the boot loader unlock in order to Root? If there are no custom roms then perhaps the boot loader unlock is unnecessary? In order to install Magisk to root, what are the prerequisits? Do I need to reinstall TWRP? If so , is there a link to the correct version? Are there any other pointers that you can give me that you found out while doing this whole process? Thank you so much
---------- Post added at 01:33 AM ---------- Previous post was at 01:02 AM ----------
Thanks for the guide!! Very helpful. However, Before I can even start following it, I'm running into some issues. The challenge that I'm facing is that I'm currently on a custom ROM (ROM AUR) and I do not know what my firmware build is. The box only tells me what the model number is and it's the MHA-L29. how would I find my firmware build ? The phone was purchased at bestbuy in the US.
Thanks again
Click to expand...
Click to collapse
You can do the exact same process, however, I strongly suggest you follow the above guide from ante0. His guides are clear and upto date. Other guides were unclear and old not being upto date.
And yes, you must have an unlocked bootloader to flash a rom, however it is very easy to do. There are many guides which tell you how to do so. Simple fastboot commands when your phone is set to fastboot mode. You only need the unlock code via Huawei's website.
With regards to Magisk/SuperSU, yes, you must have a working recovery in order to flash either one. Without recovery you cannot get root access. I suggest you flash SuperSU as it is far easier than Magisk, a simple two step procedure!
What Android version are you on? Nougat or Oreo? Beware that when flashing recovery and root, it must be for the correct Android version. And of course if updating to Oreo, once again you will need to flash recovery and root made to run on Oreo to prevent issues and boot loops.
Do you not have the box that came with your device? I am guessing you have the international MHA-L29 version as I do, but you must be sure.
ante0 said:
Bootloader getting locked is normal when updating Nougat to Nougat
Click to expand...
Click to collapse
The bootloader (i.e. fastboot) is always locked (btw, is there an easy way to unlock FB Lock ?), you probably mean the 'USER Lock'. And the 'USER UnLock' is damaged only if you flash some random oeminfo files (which is a very dumb decision anyway).
This mechanism is documented in the USENIX paper i have linked in the OEMINFO thread.
---------- Post added at 12:19 PM ---------- Previous post was at 12:00 PM ----------
kanej2006 said:
Sony was far easier to flash recovery and flash roms via recovery.
Click to expand...
Click to collapse
It may be "easier", but Mate 9 is probably one of the most unbrickable smartphones that i know, because it can be recovered even if you manage to destroy 'partition table+xloader+fastboot' (the really critical parts, other partitions can be recovered without opening the phone case).
kanej2006 said:
You can do the exact same process, however, I strongly suggest you follow the above guide from ante0. His guides are clear and upto date. Other guides were unclear and old not being upto date.
And yes, you must have an unlocked bootloader to flash a rom, however it is very easy to do. There are many guides which tell you how to do so. Simple fastboot commands when your phone is set to fastboot mode. You only need the unlock code via Huawei's website.
With regards to Magisk/SuperSU, yes, you must have a working recovery in order to flash either one. Without recovery you cannot get root access. I suggest you flash SuperSU as it is far easier than Magisk, a simple two step procedure!
What Android version are you on? Nougat or Oreo? Beware that when flashing recovery and root, it must be for the correct Android version. And of course if updating to Oreo, once again you will need to flash recovery and root made to run on Oreo to prevent issues and boot loops.
Do you not have the box that came with your device? I am guessing you have the international MHA-L29 version as I do, but you must be sure.
Click to expand...
Click to collapse
Yes I intend to follow the awesome guide from ante0 (thanks for that ante). I'm on Nougat currently. After following the above method, I guess I will have a fully factory locked phone? SO, I will have to first install recovery, then root. Correct? I do have the box but it only says the model number MHA-L29. Nothing on firmware but since its a US phone bought here, I'm fairly confident that its a MHA-L29C567B183. Although when i installed ROM AUR I used the version for L29C432 and it worked. Which one would you try if you were me? Will I brick the phone if the version is incorrect? If that happens, how do i return to oreo stock from there? Do you have any links for the right Recovery and root?
Thanks and sorry for so many questions.
UPDATE-- So have an update. I was able to install oreo using the method listed above. everything seems to be working fine. however I'm getting an error 255 message while creating a backup I'm using TWRP. Thinking that my data partition needed decrypting, I deleted it and rebooted the phone. Set it up and then went back into TWRP. I'm still getting the same backup error. any ideas? The route also installed and works fine . My concern now is that I would end up with I found that cannot be backed up with TWRP. BTW. I installed TWRP 3.2.1-0 from here https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967.
Thanks
^ 1 Thing hopefully you did not forget, before flashing the rom, you must ''wipe data'' from TWRP recovery otherwise you will get bootloop and the encryption issue. Did you wipe data from recovery prior to flashing? Encryption is removed/disabled when wiping data in recovery.
Glad you got somewhere at least. If it wasn't for the guide from Ante0, I'd still be bootlooping on Nougat.
ante0 said:
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.
Click to expand...
Click to collapse
@ante0
can i use these commands to upgrade to O as well
the only difference in the folder should be the hwota8 and the update zips for O ?
L09C316
d if=/external_sd/HWOTA/MHA_RECOVERY_NoCheck.img of=/dev/block/sdd33
dd if=/external_sd/HWOTA/MHA_RECOVERY2_NoCheck.img of=/dev/block/sdd30
echo --update_package=/sdcard/HWOTA/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA/update_all_hw.zip >> /cache/recovery/command

Categories

Resources