Database Info

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.

Semi bricked honor 6x bln - L24. Please read, weird problems

So I got an honor 6x that I can't do anything with. I can't flash any ROMs or firmware here's the weird part of it.
Its on some version of EMUI that I can't have the system update menu and it has a button for app twin. It says BLN-L24C567B366 as the model number. Speakers don't work. I can't play videos on it and I can't use the camera in any app.
Here's the really weird part:. If I wipe all partitions and try to flash a room it boots to the same EMUI firmware not the custom rom I can't do anything to change what the rom is. It's like it's stuck in that weird Frankenstein EMUI firmware that I don't even know how I got. I tried restoring anback up cause I formatted my data partition on accident causing it not to boot or something and the backup I restored was not the backup that I made . The backup I made was a stock backup onto an SD card. When I restore it it's rooted and has some downloaded apps on it. And a different launcher. Not what I backed up originally.
I'm at a loss here. What do I do? Ihave full access to adb to flash with fastboot and can get into twrp or stock recovery. No ROMs I flash will work. In twrp it says it was successful. Ut when I boot it doesn't boot to that room, it boots to the weird emui os I can't get rid of.
Has anyone run into this issue or know how to fix it?

The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.

All my update.app files get stuck at 5% too. And I know honor/Huawei won't repair it cause the warranty is void or if they can they would charge you.
Honestly get the Moto G5s plus. Get the unlocked version at best buy if you're in the states. It's 239 for the 32gb/3gb. Ram model and 299 for 64gb and 4gb. Best budget phone you can get and dual cameras. The ROM support isn't as big as the honor but it is easy to unlock the bootloader and do things. My only ROM issue I've had with this was trying to update magisk the phone had to reboot to install and after that, I had a lock screen set up btw, when I went to enter the pin the screen would go black, the phone would buzz, and go back to the lock screen. And I tried restoring a backup I made but the phone wouldn't boot stuck at the boot logo before the animation.
But the stock firmware I acquired on XDA along with the steps to flash in adb every file in the stock firmware fixed it with no problems at all so at least there's an easy way to restore the stock firmware for my new phone. It's way better than the honor 6x

Seriously tho check out the Moto G5s plus. Out of the box it has Android 7.1.1 mostly stock without all of Google's bloatware. Front mounted fingerprint sensor that you can you for the home, recent apps and back button, and can lock the screen with it if you have fingerprint set up and activate the Google assistant. It also has a notification light that you need root to use. But it has this cool "always on display" type thing that shows a clock and notifications when you move the phone or get a notification. It isn't an AMOLED display tho. It's. 1920x1080p one. Ips good viewing angles. Honestly this is the best phone I've ever used. And it has a Motorola turbocharger in the box. It's really worth it

TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
i think it could be an issue with the kernel cause the eliteRom has a custom kernel in it.. i have the update.app file for the BLN-L24C567B366 ad B365 files that i can extract and give you all the images that they have and maybe try to get the stock kernel somehow that might help?

TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
Try flashing every single update version until one of them works. Once youve found one that works follow this guide: https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985

I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360

xinoxkai said:
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
Click to expand...
Click to collapse
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?

xSpartacusx said:
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
Click to expand...
Click to collapse
Yes, firmware finder showed me 3 zips, update.zip, update_data_full_public.zip and update_full_BLN-L24_hw_usa.zip, the later 2 are the "alternative zips". Just TWRP flash them.
Also, update_full_BLN-L24_hw_usa.zip might throw an error when flashing it, don't worry, by the stage it fails in its script it already did what it was expected to do and you will not have further problems.

do i need the stock recovery flashed in order to do dload?

well i followed the first half of your guide and it successfully "updated" but my storage is encrypted

xSpartacusx said:
do i need the stock recovery flashed in order to do dload?
Click to expand...
Click to collapse
Not really, I did it when I had TWRP installed

well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that

xSpartacusx said:
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
Click to expand...
Click to collapse
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really

okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?

xinoxkai said:
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP

RedSkull23 said:
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:

xinoxkai said:
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
Click to expand...
Click to collapse
Good one dude, maybe FF proxy method could help xSpartacusx to solve his issue too!

Upgrade form B394 to B402/403

Hello guys,
long story short, I had the notification that a new update was released for my honor 8 FRD-L09C432 (B403, I was on B402), so, since I was rooted and with TWRP installed, I decided to unroot and install the original eRecovery.
Something went wrong and the system was damaged, so I flashed the B360 version first and after the B394. Now the phone is working really good but I can't install the new versions (B402 or 403). I tried:
flash the update from TWRP, not working
search the update from the dedicated option in the settings, no update found
tried to have it from the original eRecovery, error to find the info from the server.
tried also to update from the version B394 before unlock the bootloader, but it failed.
Am I missing something?

Use the get update through DNS thing in FF. It worked for me at least. Make sure the firmware is approved.

Days Tech said:
Use the get update through DNS thing in FF. It worked for me at least. Make sure the firmware is approved.
Click to expand...
Click to collapse
Hi Days Tech, could you please explain better what do you mean? Is there a link of some tut that I can follow?
Thanks!

Ok now I have the point, thanks for this tip!:good:

Flash TWRP.
use data.zip file and flash it via TWRP. (only download from FullOTA-MF PV file)
reboot and you are done. you will have updater in settings.
now you can flash the update.zip file via dload.
dlaod guide in my signature.

Phone stuck in "device is booting now" screen after oreo update

Hi guys,
I tried to update my Bln-l21 from emui 5 (nougat) to emui 8 (oreo) using the guide https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
It worked so I went on to install TWRP from https://forum.xda-developers.com/honor-6x/development/rom-emui-8-0-0-honor-6x-dual-sim-t3794079, as suggested in a comment on the guide.
Only then I realized that in order to install Gapps I needed GSM installer, so I downloaded it, but it didn't work because it loaded TWRP instead of the stock erecovery.
I started to panic real bad
I tried reinstalling the firmware using hwota8 (since i had upgraded i figured i had to use that), but it completely destroyed my phone.
Now it wont boot, recovery wont boot and neither erecovery. I can only get it to enter fastboot.
I know, I am a total noob, but PLEASE help me out on this, i'm desperate.
Thank you so much

If you can enter into fastboot, just install twrp, boot into twrp and flash the ROM using HuRUpdater. Use your external storage for the HuRUpdater and the ROM files. The instructions are here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279

Before flashing through Hurupdater wipe system Cache Data Internal and Dalvik/ART Cache.

galapagos said:
If you can enter into fastboot, just install twrp, boot into twrp and flash the ROM using HuRUpdater. Use your external storage for the HuRUpdater and the ROM files. The instructions are here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank you for the answer, I was able to boot in TWRP (the one in the original post) and I downloaded Huru, but I'm unsure of which firmware to use. I want to downgrade back to nougat and rebrand back to europe (since the guide in the original post made me change to china).
Thank you again

Just use China and then install a custom ROM

Mannan Qamar said:
Just use China and then install a custom ROM
Click to expand...
Click to collapse
which one should I choose from firmware finder?
Which rom do you recommend?

Bonny96 said:
which one should I choose from firmware finder?
Which rom do you recommend?
Click to expand...
Click to collapse
Just use the original files you used in the first place. The ones you downloaded from the thread. In terms of a custom ROM there is a thread in Custom ROMS section for Pixys OS. Just search stable Pie ROM for Honor 6x and install it. It's very smooth, etc.
This is a EMUI 8 ROM. If you want to go back to EMUI 5 don't use this. This will only restore EMUI 8. After that flash Custom ROM Don't go back to EMUI 5

Mannan Qamar said:
Just use the original files you used in the first place. The ones you downloaded from the thread. In terms of a custom ROM there is a thread in Custom ROMS section for Pixys OS. Just search stable Pie ROM for Honor 6x and install it. It's very smooth, etc.
This is a EMUI 8 ROM. If you want to go back to EMUI 5 don't use this. This will only restore EMUI 8. After that flash Custom ROM Don't go back to EMUI 5
Click to expand...
Click to collapse
Hi, I successfully flashed with Hurupdater and I'm going trough the installation of the pixys rom. The guide says that i need to flash the stock recovery for my device, where can I find it?
Can I pull it from the firmware I used for Huru? If that's the case, how?
Thank you again

I do have instructions over there but cause you asked I will tell.
Extract the Update.zip the large file. In it you will have an Update.app. Now serach for Huawei Update Extractor on XDA and Download it. Run the application and navigate to Update.app. Select it and in settings of Extractor uncheck the first option. Now extract Recovery_Ramdis.img and flash it. Luck.

Mannan Qamar said:
I do have instructions over there but cause you asked I will tell.
Extract the Update.zip the large file. In it you will have an Update.app. Now serach for Huawei Update Extractor on XDA and Download it. Run the application and navigate to Update.app. Select it and in settings of Extractor uncheck the first option. Now extract Recovery_Ramdis.img and flash it. Luck.
Click to expand...
Click to collapse
Thank you so much! Now the phone is working again, I'm only having trouble flashing magisk (it doesn't show up among the apps) but i guess i can live without it for now...
Have you got a paypal or something? I wanna buy you a coffe, it seems the least I can do to repay your kindness and patience!

Bonny96 said:
Thank you so much! Now the phone is working again, I'm only having trouble flashing magisk (it doesn't show up among the apps) but i guess i can live without it for now...
Have you got a paypal or something? I wanna buy you a coffe, it seems the least I can do to repay your kindness and patience!
Click to expand...
Click to collapse
Really there is no need for that. I did what anyone would do. Your thanks is enough.
Can you tell me what version you flashed. What TWRP did you use and what was the message after flashing.Now regarding Magisk, I am gonna assume you flashed the ZIP and the Magisk Manager app didn't show up, correct? To solve that just download Magisk Manager v6.0.1 and install the apk.
If that's not the issue then download any Root Checker app to see if device is rooted. Although I guess you need Magisk Manager to validate Root access. So just install Magisk Manager and let me know what it says. If it says device is unrooted then you probably need to flash Magisk again.
P.S: I don't have a PayPal. Not yet available in my country.

Mannan Qamar said:
Really there is no need for that. I did what anyone would do. Your thanks is enough.
Can you tell me what version you flashed. What TWRP did you use and what was the message after flashing.Now regarding Magisk, I am gonna assume you flashed the ZIP and the Magisk Manager app didn't show up, correct? To solve that just download Magisk Manager v6.0.1 and install the apk.
If that's not the issue then download any Root Checker app to see if device is rooted. Although I guess you need Magisk Manager to validate Root access. So just install Magisk Manager and let me know what it says. If it says device is unrooted then you probably need to flash Magisk again.
P.S: I don't have a PayPal. Not yet available in my country.
Click to expand...
Click to collapse
I really appreciate your kindness,
I flashed the latest version of magisk available from the official thread using the same TWRP from before (king of mezi TWRP from elemental rom thread) and it looked fine... Yes, the app didn't show up, I will try with the manager and I'll let you know.
[edit] I installed the manager and turns out it actually worked the first time and I'm already rooted!
Thank you again, you've been wonderful!

Glad to help.

[Q]How to change root from phh.superuser to Magisk and upgrade firmware?

Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot

itenos said:
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
Click to expand...
Click to collapse
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
With that said:
If you want to keep your data, make a backup using Hisuite.
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.

Just stumbled over your reply, didn't get an email notification from XDA. Thank you so much. Let's see if I can follow your instructions.
irony_delerium said:
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
Click to expand...
Click to collapse
Yes, I still have the code
irony_delerium said:
With that said:
If you want to keep your data, make a backup using Hisuite.
Click to expand...
Click to collapse
Done
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Click to expand...
Click to collapse
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
irony_delerium said:
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Click to expand...
Click to collapse
I don't think that I modified any other partitions, at least not willingly. I even left the system in read-only state. Don't know if phh.su did something by itself?
irony_delerium said:
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Click to expand...
Click to collapse
Will continue to do the above after your kind confirmation of my last questions. Thanks again

itenos said:
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
Click to expand...
Click to collapse
The order shouldn't be particularly relevant, just that it's safest to reflash all of them:
- boot because phhsu may have modified the boot image to add su to it
- recovery and recovery2 because you loaded TWRP. recovery2 is specified because it's used to be recommended to flash to erecovery as well as normal recovery.
- system because I'm pretty sure that's the biggest thing modified Hy phhsu, and any other system changes you may have made.
Theoretically, other modified partitions won't matter since the upgrade to 8.0 replaces most (all, I think) of them anyway, but if you have to go through update steps through EMUI 5 first before it'll give you 8, then it's safest that they aren't modified. I mentioned other partitions because, with root & TWRP, you technically could have modified any and all of them.

irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically.
Click to expand...
Click to collapse
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip

itenos said:
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
Click to expand...
Click to collapse
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.

irony_delerium said:
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
Click to expand...
Click to collapse
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.

itenos said:
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
Click to expand...
Click to collapse
Easy way:
Unlock phone, if you haven't yet again.
Download and flash TWRP from here: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353 (has decryption support) (flash to recovery_ramdisk as Huawei decided to split recovery partition into different parts)
Boot to TWRP, input pin (if you set a pin, else it will decrypt automatically)
Download Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Transfer Magisk to phone.
Flash Magisk zip in TWRP.
Reboot and you're done.
You might have to tinker around with Magisk Hide and hide apps if your banking apps still detect root.

As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all

itenos said:
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
Click to expand...
Click to collapse
The erecovery method won't work unless you can change the DNS settings on the network being used - it hijacks some of the requests to Huawei's servers to force the update. (And even then it's a bit finicky; I have yet to successfully use it, all things considered.)

Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.

itenos said:
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
Click to expand...
Click to collapse
The reason recovery boot is needed for Pie is because Huawei removed the ramdisk - in Pie, it's system as root with no way of forcing a ramdisk except by a recovery boot. So as a workaround, Magisk takes over recovery.
The installation instructions for it on Pie are pretty much the same as Oreo, except:
* Patch recovery_ramdisk, not ramdisk. Latest stable Magisk should work (18.1, iirc, has the patches to support recovery boot.)
* When booting, go to recovery. Magisk will start from there and take over the startup process.

irony_delerium said:
The installation instructions for it on Pie are pretty much the same as Oreo, except:
Click to expand...
Click to collapse
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?

itenos said:
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
Click to expand...
Click to collapse
TWRP on this case, don't bother.
Extract your stock recovery from your firmware's update.app file, patch with Magisk Manager, and flash the patched image. When you want to flash an ota, put the stock recovery back.