So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Magisk working on final android 10
oscar1823 said:
So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Click to expand...
Click to collapse
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
alliance1975 said:
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
Click to expand...
Click to collapse
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
sic0048 said:
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
Click to expand...
Click to collapse
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
omiCar said:
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
Click to expand...
Click to collapse
I installed it while still Pie.
sic0048 said:
I installed it while still Pie.
Click to expand...
Click to collapse
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
I made the mistake of having Magisk set to beta instead of canary when I did the Magisk OTA update, but no issues with the regular boot image patching method.
Simply follow the guide linked above and you should be fine.
omiCar said:
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
Click to expand...
Click to collapse
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
Got it to work.
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
sic0048 said:
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
All you really need to do is flash Pie back on the phone and start the process over. I realize that seems like a long process, but it really isn't that hard. Just be sure to backup any important data off phone before you start because installing Pie should wipe the phone.
Click to expand...
Click to collapse
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Thanks for the response, I will download the Andriod 10 and flash it into my phone, hopefully it will work
darkmeridian said:
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
I agree that normally that would work.
However, simply replacing the boot.img file doesn't completely uninstall Magisk. That is why there is a Magisk Uninstaller zip that can be used with TWRP. It normally isn't needed, but it is a great way to completely wipe Magisk if you are having issues. Obviously that isn't an option on Android 10 currently because TWRP doesn't work yet.
Hopefully he doesn't have any issues moving from stable to Canary Magisk versions. But if he does, he will likely have to flash a full factory image to completely wipe the phone and reinstall everything without traces of Magisk
flow5673 said:
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Click to expand...
Click to collapse
This worked for me. Thanks
darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
If you experience manager telling you that Magisk isn't installed after installing it through fastboot, uninstall manager and reinstall it. Deleting app data won't do the trick. Strange bug but I encountered that in the Q beta
Anyone else having issues with the canary build? I hard reboot and it shows magisk not installed, then I reboot again and its installed again?
Also Android Q is hella laggy for me?
Currently doing a full fresh image install
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Velcorn said:
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Click to expand...
Click to collapse
For now I disabled the unused apps. Similar behavior also in pie. One update app remover wouldn't work but titanium would, the next update the reverse would happen. I think the apps need updating so as to work with Android 10.
omiCar said:
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
Click to expand...
Click to collapse
I don't have a video but you can look up the individual steps. You want to do the OTA through ADB sideloading. Then patch the stock boot.img with Magisk Canary, which was linked to above, and then flash with fastboot.
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Uninstall and reinstall Canary Magisk Manager (NOT DEBUG). I had both force encryption and preserve avb CHECKED. Then patch boot.img and flash using fastboot.
Related
Just tested it this morning as all is working well. Now we are officially in the supported device (along side with Pixel 2 and 2XL). Thus means that we can now patch boot.img on the fly using Magisk Manager when there's an OTA update.
Steps would be the same as Pixel 2 series as our phones apparently using the same partition and logic method as the Pixel 2. Mentioned here : https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I would suggest anyone who uses magisk snapshot build to upgrade to this latest version for proper magisk patching without TWRP. For minimal issue :
1. install magisk manager 5.4.1 (your current app will prompt for update usually, if not sideload from the official magisk beta xda forum.)
2. Uninstall magisk using the manager app, this will restore your boot.img backup. DO NOT REBOOT, just tap close.
3. Tap update/install magisk. It will then ask which method of installation. Choose install right now (recommend).
4. Reboot and wait, latest magisk should be installed after reboot.
Note : if the backup boot img is not stock, not available or is already patched. You'll need to boot to fastboot, flash your current build boot img. And then boot twrp to flash the magisk 14.5 flashable zip.
Full details here : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Can you use Android Q on the pixel A along with rooting?
sillyshyme said:
Can you use Android Q on the pixel A along with rooting?
Click to expand...
Click to collapse
Unfortunately, not. The pixel 3, 3a as well as the xl versions of both currently do not have magisk for Android q. The dev is working on it though. Keep your ear to the ground
Sent from my Pixel 3a using Tapatalk
Yes. The Pixel 3/3a versions use logical partitions in the Q beta. and it sounds like it's taking a major re-write to support it. I believe it is called system-as-root. The developer John Wu has been posting about it on Twitter. https://twitter.com/topjohnwu
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
12paq said:
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
Click to expand...
Click to collapse
It's pushed to the Cannery build https://twitter.com/topjohnwu/status/1144159892430659584
Magisk and TWRP all in the same day!
@pharpe wait TWRP got released?
Tiebe said:
@pharpe wait TWRP got released?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413
did any one successfully root q ?
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
Yeah, can confirm, did this earlier today!
Just a question, did you have the issue that many apps show up in the appdrawer of pixel launcher, even if they shouldnt? (like Google PDF Reader, Sd Maid unlock or sideloaded Pixel livewallpapers etc.)
I guess its because of the bootloader is unlocked (for security reasons)?! Just really weird. No other issues observed till now.
peace!
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
removed
pharpe said:
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
Click to expand...
Click to collapse
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
bejunk said:
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
Click to expand...
Click to collapse
Interesting. I never realize that. I keep all my apps organized in folders so I only go to the app drawer for things I rarely use. I just assumed everything that was installed was in there.
pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
c_tho said:
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
Click to expand...
Click to collapse
That is my understanding from what I have read but I have not actually done it. You would uninstall via Magisk and it restores the original boot.img that it has backed-up. Then you are back to stock to take the OTA.
I'm using the canary version of Magisk for the Q beta 6. Yesterday I tried to install a self made module to get rid of screenshot sounds (the one on the rep isn't working because Google changed the path. But as I installed it, I can only remember that the last line was "Magisk manager will be removed and your device will reboot in a moment" or something like that
Well, the manager is still installed, but Magisk itself got uninstalled. Besides the fact that I have no clue why that happened, now I can't install it. TWRP doesn't support Q. So I got the Q image from Google, extracted the boot.img and let Magisk Manager patch it (with preserve force encryption and Preserve AVB 2.0/dm-verity turned on) and flash it through Fastboot (fastboot flash boot magisk-boot.img) but it's still not installed. And without TWRP of course I can't flash the uninstaller zip (no clue what was actually removed).
Is there a way through adb or fastboot to find out what's left of the Magisk installation and remove that? Or any other solution I didn't think of?
Ok, via adb is not an option since both /data and /cache refuse permissions so I can't even get logs to find out what happened.
Does anyone have a working pre-patched boot.img? I don't know if that Manual method isn't working because patching isn't really working or because the Magisk files are still present and the module is still conflicting with Magisk. And I don't want to do a factory reset
Nevermind. It was a faulty Magisk database, I had to uninstall and reinstall it to solve the problem
Hi!
This is a quick guide on how you can update your OP6 to latest Open Beta build from OnePlus with these changes:
Changelog
Added the notch area display options under Settings>Display>Notch display>Hide the notch area
Updated the GMS Package
Updated Android security patch to 2019.11
Improved system stability and general bug fixes
Sign up to get rewards, premium experience, and exclusive offers
- grabbed from OP community forum
If you are running stable 10.0.1 you can local upgrade to OB3 withoutno problem
But if you running open beta already you need to be in OB2 Q before updating to OB3 Q.
Here's the step by step guide:
Note: disable magisk modules and substratum first if ever you have. DON'T FORGET!!
1. Download OP6 OB3 firmware: https://otafsg1.h2os.com/patch/amaz...22_OTA_062_all_1912110952_cacdd5fe0385b33.zip
1-2. Download patched boot image: https://mega.nz/#!zBlXSQzC!RAQgiPqJXydFIXa-6sqntQiUOK34-QYdtot4wEu-mEQ
(Copy this to your PC you need this later)
1-3. Download Magisk Manager APK (if you don't have this installed yet.)
2. Update using local upgrade
3. Reboot
4. Allow it to boot up and wait few minutes to let finish the update completely.
5. Reboot to bootloader - fastboot
6. Type
fastboot flash boot_a "bootname".img
fastboot flash boot_b "bootname".img
(Without " ")
7. Type: fastboot reboot
- Install Magisk Manager APK, (if you don't have it)
8. Re enable your modules and everything then reboot one last time
9. Lastly, sit down and relax
Credits: @Siljorfag for OP6T stock boot image i asked. @Amirhussaini for OP6 stock boot image i asked
OP for OB3 Q update
From 10.0.1
download ob3 full
open magisk - uninstall - restore image
local update select ob3
dont reboot
open magisk
install - inactive slot
reboot
DONE
brmbjn said:
From 10.0.1
download ob3 full
open magisk - uninstall - restore image
local update select ob3
dont reboot
open magisk
install - inactive slot
reboot
DONE
Click to expand...
Click to collapse
That's totally different from what i did which i stated above. I used pc on my procedure which gives me no problem too. Steps may vary depending on user preference.
Can You please provide a guide to Update to OB3 Q with Magisik And TWRP as Well.
Currently my situation is i have bootloader unlocked and running on OB3 Q
When i try to install twrp and magisik i was getting stuck at Bootloader Unlocked screen.
Please help me to get Twrp and Magisik as welll
DroidPrince16 said:
Hi!
This is a quick guide on how you can update your OP6 to latest Open Beta build from OnePlus with these changes:
Changelog
Added the notch area display options under Settings>Display>Notch display>Hide the notch area
Updated the GMS Package
Updated Android security patch to 2019.11
Improved system stability and general bug fixes
Sign up to get rewards, premium experience, and exclusive offers
- grabbed from OP community forum
If you are running stable 10.0.1 you can local upgrade to OB3 withoutno problem
But if you running open beta already you need to be in OB2 Q before updating to OB3 Q.
Here's the step by step guide:
Note: disable magisk modules and substratum first if ever you have. DON'T FORGET!!
1. Download OP6 OB3 firmware: https://otafsg1.h2os.com/patch/amaz...22_OTA_062_all_1912110952_cacdd5fe0385b33.zip
1-2. Download patched boot image: https://mega.nz/#!zBlXSQzC!RAQgiPqJXydFIXa-6sqntQiUOK34-QYdtot4wEu-mEQ
(Copy this to your PC you need this later)
1-3. Download Magisk Manager APK (if you don't have this installed yet.)
2. Update using local upgrade
3. Reboot
4. Allow it to boot up and wait few minutes to let finish the update completely.
5. Reboot to bootloader - fastboot
6. Type
fastboot flash boot_a "bootname".img
fastboot flash boot_b "bootname".img
(Without " ")
7. Type: fastboot reboot
- Install Magisk Manager APK, (if you don't have it)
8. Re enable your modules and everything then reboot one last time
9. Lastly, sit down and relax
Credits: @Siljorfag for OP6T stock boot image i asked. @Amirhussaini for OP6 stock boot image i asked
OP for OB3 Q update
Click to expand...
Click to collapse
transfer quota exceeded .. anyone here willing to share the patched img from a different cloud .. thank you
brmbjn said:
From 10.0.1
download ob3 full
open magisk - uninstall - restore image
local update select ob3
dont reboot
open magisk
install - inactive slot
reboot
DONE
Click to expand...
Click to collapse
If you restored the image, how did you get to still have magisk?
ddaharu said:
If you restored the image, how did you get to still have magisk?
Click to expand...
Click to collapse
Restore image. Dont reboot and then select local update.....
brmbjn said:
Restore image. Dont reboot and then select local update.....
Click to expand...
Click to collapse
I'll give it a try.
Edited: I actually didn't have to restore images. I just needed to reinstall magisk in magisk before I rebooted and it worked.
I followed each step .. now i cant see install- inactive slot .. when i click on install it says to install latest apk which is already present
rohheat said:
I followed each step .. now i cant see install- inactive slot .. when i click on install it says to install latest apk which is already present
Click to expand...
Click to collapse
Magisk preinstalled. Just install latest magisk manager. No need to do anymore fancy
DroidPrince16 said:
Magisk preinstalled. Just install latest magisk manager. No need to do anymore fancy
Click to expand...
Click to collapse
I didn install latest magisk still same . I cant find
rohheat said:
I didn install latest magisk still same . I cant find
Click to expand...
Click to collapse
You can repeat clean install by updating again via local upgrade. Then do it again.
After updating my sim cards aren't detected. Also twrp is gone and I can't clear cache. Any advice?
Sent from my [device_name] using XDA-Developers Legacy app
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Bump
scuzzo500 said:
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Click to expand...
Click to collapse
You are on stable channel surely the notified upgrade is to version 10.0.11, so you can update and keep root and twrp working.
To do this follow the steps described by @strongst in the op7 forum and you will have no problems.
Here the steps to follow:
Optional but highly recommended, backup everything in case of issues.
Download the full rom zip file and the twrp zip installer file and place it into the phone storage memory.
Go to Magisk Manager and uninstall all modules.
Reboot phone.
Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, select the .zip file of the new firmware and wait for the installation to finish. Attention don't reboot yet!
Install TWRP within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+" select .zip file of the twrp recovery installer. Attention don't reboot yet!
Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit again install -> hit "install to inactive slot".
Finally reboot.
Reinstall your Magisk Modules.
Done! Your device is now updated and you keep TWRP and root.
Very important: At the moment this procedure is to be considered reliable only if used with firmware based on Android 10.
scuzzo500 said:
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Click to expand...
Click to collapse
As of right now there is no TWRP working some have had luck but unfortunately most havent. i have uploaded a patched boot.img that will let you root
how to install android 11 on gm 1925, if my phone does not see files via local update?????