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.
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Thank you :fingers-crossed:
I'm still on Android 8.1 and waiting stable Android 10
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
ony89 said:
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
Click to expand...
Click to collapse
If you have a locked bootloader, you can't do anything.
Magisk and root is separate to TWRP on this phone. This image will help you get Magisk installed.
Instructions here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
a1291762 said:
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Thank you!
wassupjg said:
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Click to expand...
Click to collapse
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
a1291762 said:
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
Click to expand...
Click to collapse
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
wassupjg said:
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
Click to expand...
Click to collapse
I'm not totally sure...
There are links to the OTA zips around. A thread about Android 10 showed how to install one using the stock recovery... I guess the same works for 10.0.20.0?
As a Linux user I would be inclined to try and use command line tools to install the OTA zip... But I don't even know if that's a thing
wassupjg said:
...
Click to expand...
Click to collapse
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
a1291762 said:
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
Click to expand...
Click to collapse
Thanks dude, I did find it here in the posts, I guess the OP isn't updated anymore, I've just had too many problems with Q, it sucks imo, once I back up everything I'll give it a go, by any chance do you know any good app and general backup apps that make things easy?
wassupjg said:
by any chance do you know any good app and general backup apps that make things easy?
Click to expand...
Click to collapse
I bought titanium backup pro a long time ago and still use it. Back in the day, the free version was annoying for whole device restore. But it's let me move across 5 devices and saved me from losing data on many occasions so I consider it money well spent.
I backup and then rsync /sdcard to a computer daily (CLI tools from cron). For restore I copy the files back (if needed) and then restore.
I only backup user apps, call history and SMS. System apps don't restore properly these days.
A few months ago I followed one of tutorials and unlock the bootloader, installed twrp, magisk, and gain root. I am normally a flashaholic but lately I been busy and working and have stay on the stock rom and haven't touch it. So I don't know much about how things work. I noticed I have a notification for the new update. What steps do I need to take to download the new update from oneplus and stay rooted? Or can I just download the updated as is?
Edit: Also, if I wanted to install an Android 11 rom, are they stable enough for daily use? If so, any recommendations?
Thanks in advance.
J3STUR said:
A few months ago I followed one of tutorials and unlock the bootloader, installed twrp, magisk, and gain root. I am normally a flashaholic but lately I been busy and working and have stay on the stock rom and haven't touch it. So I don't know much about how things work. I noticed I have a notification for the new update. What steps do I need to take to download the new update from oneplus and stay rooted? Or can I just download the updated as is?
Edit: Also, if I wanted to install an Android 11 rom, are they stable enough for daily use? If so, any recommendations?
Thanks in advance.
Click to expand...
Click to collapse
There is specific guides. Regarding this. You use a app to download the update. Apply it don't reboot. Then in magisk flash a twrp retention zip. And magisk install on inactive slot. Then reboot. Is the jist of it
TheMadScientist said:
There is specific guides. Regarding this. You use a app to download the update. Apply it don't reboot. Then in magisk flash a twrp retention zip. And magisk install on inactive slot. Then reboot. Is the jist of it
Click to expand...
Click to collapse
Thank you!
Hi guys. I know there has been a million topics about this and I've read most of them but does anyone know which route is currently the safest for an ota update? I have a 7pro rooted with Twrp and magisk. I'm on 10.0.5 and looking to update to 10.0.10.
Should I use trwp recovery and flash everything from there or can I flash locally and then use magisk along with the a/b retention script? I messed up rooting the phone originally and lost some data and now I have a mental block around which method is safest to do without losing my data or bootlooping. I want to make sure both slots update correctly and I'm unsure of the correct method.
Any help would be appreciated before I give it a go, thank you.
I'm also wondering if I've edited the build prop in any way with the build prop editor, will this cause a boot loop or will a full ota zip return it to normal anyway?
Thanks
Bxperiaz3 said:
Hi guys. I know there has been a million topics about this and I've read most of them but does anyone know which route is currently the safest for an ota update? I have a 7pro rooted with Twrp and magisk. I'm on 10.0.5 and looking to update to 10.0.10.
Should I use trwp recovery and flash everything from there or can I flash locally and then use magisk along with the a/b retention script? I messed up rooting the phone originally and lost some data and now I have a mental block around which method is safest to do without losing my data or bootlooping. I want to make sure both slots update correctly and I'm unsure of the correct method.
Any help would be appreciated before I give it a go, thank you.
Click to expand...
Click to collapse
the typical and safe route to take an OTA and keep your root is:
download OTA using oxygen downloader app
Use the sytem update app to install the file above using the local upgrade option. DO NOT REBOOT.
Use magisk to install the twrp a/b keeper script. DO NOT REBOOT.
Use magisk to install magisk to the inactive slot. Then reboot.
I have the gm1913 phone which is a different variant, but I'm sure that the concept is the same.
Good luck.
Thanks for the reply. Did something similar to this
What I ended up doing incase anyone else needs to know..
Disable all magisk modules and reboot
Flash full update from local storage
Don't reboot
Go to magisk and flash twrp zip
Don't reboot
Flash magisk zip to separate slot (ota option)
Now phone reboots its self
Re enable modules in Magisk
Reboot
Profit
Hi folks, I am running a Pixel 6A that I rooted with magisk back in December. I stupidly did not disable OTA updates. Last night the QPR2 update came down and wiped root from my phone.
Bootloader is still unlocked and magisk app is installed.
I am confused about the best way to restore root. I see that the QPR2 beta required the use of the pixel 7 boot image. Does that still hold for the stable QPR2?
Also, the magisk app offers a way to choose and patch an image within the app. Can I get the pixel 7 boot image and patch it in magisk, or do I have to use the ADB/ fastboot method?
Sorry for the trouble. I promise I will disable OTA updates in the future. Thanks for any help.
Hello! I am also root user and if it is true that there was an update with the boot 6a not root and I had to use the pixel 7 or 7 pro (I do not remember which was) but if in doubt I would try only with the 6a just in case, the procedure is to download the full rom of the same version you have now, extract the boot.img, patch it with magisk and flash it by adb from the pc, is the method I use in each update and no problems until today, good luck and greetings!
If you are using Magisk Stable 26.1 or Canary 26101, you can use the Pixel 6a boot image to root as the problems mentioned above have been fixed with these versions of Magisk.
Problem solved. Y'all rock.
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
RimWulf said:
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
Click to expand...
Click to collapse
Download and open the zip => open "image-bluejay-tq2a.230305.008.e1.zip" => find your boot.img