Follow the guide in the OP, except use magisk alpha. Looks like boot.img for OOS12 versions still need to be added, but you can find the stock boot.img in this post and use magisk alpha to patch it.Anybody share the full rooting process running Android 12..
Thanks advance
So I need only patch booth image using magisk alpha .. or also need vbmeta patches ..Follow the guide in the OP, except use magisk alpha. Looks like boot.img for OOS12 versions still need to be added, but you can find the stock boot.img in this post and use magisk alpha to patch it.
With magisk alpha, you only need boot.img.So I need only patch booth image using magisk alpha .. or also need vbmeta patches ..
It is well described in Post #818 and I can confirm that it works.Anybody share the full rooting process running Android 12..
Thanks advance
So basically remove magisk manager app, right?No, this is incorrect that wil remove root.
Just remove the Magisk app it self (either long press and choose remove or through the android settings app section).
After uninstall, install alpha (first post).
Local upgrade.
Open Magisk app (alpha).
Install root to inactive slot.
Reboot.
Yes, just the app.
This worked a treat on my Global model. Only thing I did different was install Magisk Canary (23018) app. Canary's have been working with Android 12 since (23016). Op chart needs updated...My method:
-Uninstall magisk stable app (leave root active).
-Install magisk alpha app.
-Check the app if root is detected, otherwise reboot.
-Local upgrade. Don't reboot!
-Open Magisk alpha app and install root to inactive slot.
-Now Reboot.
This is what I did, and worked.
European model.
Ah, thanks for that info.This worked a treat on my Global model. Only thing I did different was install Magisk Canary (23018) app. Canary's have been working with Android 12 since (23016). Op chart needs updated...
Thanks. Canary works.This worked a treat on my Global model. Only thing I did different was install Magisk Canary (23018) app. Canary's have been working with Android 12 since (23016). Op chart needs updated...
Canary uses Deny List.Ah, thanks for that info.
But does Canary also have Magisk Hide?
Download thisOp9 pro EU rooted with magisk alpha. No modules and Deny list working ok but Google Play says no certificated device. Deleted cache in store and services. Any help, please?
I'm on A12 with Magisk v24. Seems to be working fine. You should use the full OTA. Post #818 explains how to update.Is the new Magisk 24.0 compatible with Android 12? Also I am using the Global/US 9 pro... Do I use option 1 or option 2 when upgrading my phone to C.44 full update 4+GB?
Same here. Are you on Android 12?Perhaps a silly question - does anyone know what could be the reason that I am now missing Advanced Reboot option in Developer Options?
You can simply use an alternative launcher, like Nova launcher. Has your phone retained L1 widevine after root (you can check it with DRM Info App from playstore).Also, the status bar has overlapping icons and even the button icons at the bottom are duplicated.
Pretty sure I would have messed up during some step which is causing these issues as I couldn't find anything about these in the quick search that I did. (Any tips on how to fix these without reinstalling WhatsApp etc would be greatly appreciated!)
Have you installed the Qualcomm drivers that come with MSM tool? If you have, some people have reported that you actually need to klick the "start" button in MSM tool before you connect the phone. The restore process will then start once you connect it and cant be interrupted.I have managed to brick my phone and can't seem to revive it through MSM as well since apparently the MSM Tool linked in the first post by OP is for Android 11 / devices manufactured before Mar'21 only)
Yes, I was on 12 before managing to brick my phone y'day evening :-(
and C.47 (EU version)
I had the same situation: phone updated to android 12 (C.47 - EU version)), then rooting failed, then phone fell into a fastboot loop, tried to get out of it and ended up phone not even turning on (only qualcomm mode was left). MSM restored it to the factory state with Android 11. Do everything as described, the most important thing is to upload the appropriate drivers, this is the most important thing for MSM to work.I have managed to brick my phone and can't seem to revive it through MSM as well since apparently the MSM Tool linked in the first post by OP is for Android 11 / devices manufactured before Mar'21 only)
Yes, I was on 12 before managing to brick my phone y'day evening :-(
and C.47 (EU version)
Magisk Variant | Stable / Beta / Canary | |||
Release | Official | |||
Android / OOS | OOS 11 and above | |||
Maintainer | topjohnwu | |||
Project Link | GitHub | |||
Zygisk | No | |||
DenyList | No | |||
MagiskHide | Yes | |||
Modules Repo | Yes | |||
Download Link | GitHub |
You can download the EU stock boot.img that's in this thread (2nd post), download the latest magisk canary manager and patch that boot.img. Then you can temporarily gain root by rebooting to bootloader and booting that image ex. "fastboot boot boot.img"( your boot.img name will vary after patching). After the phone boots you can just go into magisk manager and do a "direct install" and that will patch your global boot.img to gain permanent root.
My method:This seems way too easy. After reading several attempts and resulting soft bricks and whatnot, you're saying:
Uninstall magisk (or just the app?)
(Won't this leave you unrooted and unable to install magisk alpha?)
Install magisk alpha
Reboot
Local update to a12
Don't reboot
Install magisk (alpha) to inactive slot after ota
Reboot
I'm holding off on a12 until a kernal or two are available, bugs are worked out, and a crystal clear update method.