I did this method with my EU model and after bricking it many times this worked. Now there's an update of magisk and I am hesitant to do it . Should I install it directly now or will still be using the inactive slot method?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.
It won't let me download the module. Maybe because I don't have a telegram? Not sure.FYI i just did the update from Magisk Alpha (23018) toStableBeta v24 and everything's looking good. Had to install a module called Shamiko v0.3.0 (link) to replace MagiskHide. Im on A12 C44EU btw.
If you are updating magisk only (no system update), install it directly. You only install to inactive slot after a system update.I did this method with my EU model and after bricking it many times this worked. Now there's an update of magisk and I am hesitant to do it . Should I install it directly now or will still be using the inactive slot method?
Yeah you need telegram to download it. I recommend that you download directly from telegram. Note its not a stable as the module is still in development but for now it works. With that said I'm going to leave the latest version that i used here as well as the guide i used.It won't let me download the module. Maybe because I don't have a telegram? Not sure.
Thank you. I don't want telegram lolYeah you need telegram to download it. I recommend that you download directly from telegram. Note its not a stable as the module is still in development but for now it works. With that said I'm going to leave the latest version that i used here as well as the guide i used.
Hi Everyone,
I am running a OP 9 Pro - Global/N.A.
I updated to C44 today, i ended up soft bricking my OP 9 Pro but got it fixed and wanted to give you some guidance if you did the same thing, and also provide you with files you need to use to re-root your phone again.
Here is the SOP I used, but will give you the commands you need to run in ADB - https://www.droidwin.com/root-android-12-via-magisk-patched-boot-img-without-twrp/
"fastboot flash boot magisk_patched_boot.img" (for flashing the Boot.img file, you can use this command to go back to stock or push your root .img file.)
I also noticed to make sure you are flashing the boot.img file to the active slot, if you push it to the inactive slot, your phone won't boot after you push the root boot.img file.
Stock C44 Boot IMG File - https://drive.google.com/file/d/1e79v-cjDrR6dfhH8yCDJNGwDZsmVsZos/view?usp=sharing
Root C44 Boot IMG File - https://drive.google.com/file/d/1TsyPinHESeux1JlvgbhyS5hm_7-ugSSO/view?usp=sharing
I hope this helps get you running root again, or gets you out of the softbrick.
I tried this. Doesn't seem to work with latest beta (v24).
You have zygist enabled?I tried this. Doesn't seem to work with latest beta (v24).
Play store still doesn't pass. Any other things i need to do? I can't find Play Store in DenyList.
Yes.
click on the right top buttom, you will see an option to shom system appYes.
I found the playstore in denylist, had to enable to show system apps.
After that i removed Data/Cache from Play Store. Now it is certified![]()
What exactly does this module please?Yeah you need telegram to download it. I recommend that you download directly from telegram. Note its not a stable as the module is still in development but for now it works. With that said I'm going to leave the latest version that i used here as well as the guide i used.
The module wasn't working for me. I had better results just using Zygist and denylist. Not sure why, maybe because it's in development still.
It is a new zygisk module that replaces magisk hide, but way better and more powerful.
Indeed, it is still in development, but won't take long for a stable version to be released, alongside with a new stable zygisk lsposed in the coming days.The module wasn't working for me. I had better results just using Zygist and denylist. Not sure why, maybe because it's in development still.
Do you pass safetynet? Universal safetynet fix solved the problem for me.Hey guys. I just updated to Android 12 on the AA variant. Everything is going well with Magisk Alpha. Though, my GPay (Google Pay) is still detecting root even after adding it to the deny-list in Magisk. Any suggestions?
Me too. Updated to Magisk v24 had to flash this module. Still on OOS 11 for now.Do you pass safetynet? Universal safetynet fix solved the problem for me.
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.