Related
My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.
Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/
I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.
Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?
I've got my FRD-L14 (64GB US honor 8) running stable with B360 firmware (released 02-13-17) bootloader unlocked, SU flashed via TWRP.
I wanted to try the latest B385 OTA firmware flash so I used fastboot to flash my current stock B360 System.img, boot.img, and recovery.img to be sure I am running all stock boot/system files before flashing the B360 OTA.
I rebooted from fastboot successfully and continued with the OTA interface to install latest system update, it rebooted into Huawei recovery interface, verifying, installing, and then fails to verify and install.
Do I really have to lock the bootloader and wipe the entire phone in order to install latest OTA and then re-unlock bootloader, reflash twrp, and restore data ?
Thanks !
Well, that wasn't hard.
I used the "download latest full package" in the top-right menu of the OTA updates screen. This successfully installed B385 OTA update package for me without failure, while bootloader unlocked. Imagine that. I hope this helps someone else! Now, to figure out how to use magisk rather than supersu....
[remove, accidental doublepost]
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
crowruin said:
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
Click to expand...
Click to collapse
I just got the new update
mine26135 said:
I just got the new update
Click to expand...
Click to collapse
same here hahaha updating now.
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!
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
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.