check #772 post at previous pageCan someone please link the patched magisk boot image for OP9Pro c44 glodal?
check #772 post at previous pageCan someone please link the patched magisk boot image for OP9Pro c44 glodal?
Should this also work with magisk canary? I'm not sure what the difference is between alpha and canary...I had no problems switching from A11 to A12 e.44.
Installed the alpha of magisk first (removed there old magisk app before this).
Did the local upgrade, patched boot at inactive slot and rebooted.
Only thing i noticed is, that the boot warning for unlocked bootloader is gone. Which i don't mind at all!
Read the first post. It says that the canary build is for Android 11. And Alpha and the one next to it are for Android 12.Should this also work with magisk canary? I'm not sure what the difference is between alpha and canary...
This seems way too easy. After reading several attempts and resulting soft bricks and whatnot, you're saying:I had no problems switching from A11 to A12 e.44.
Installed the alpha of magisk first (removed there old magisk app before this).
Did the local upgrade, patched boot at inactive slot and rebooted.
Only thing i noticed is, that the boot warning for unlocked bootloader is gone. Which i don't mind at all!
hi, cant open these telegram post links, because i'm not joined telegram group. can you provide link to group?
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.
As long as you use magisk alpha, yes.
why alpha ? and also i mean just flashing patched boot.img right ? on coloros i flash patched boot.img with vbmeta do i need to flash it also ?
Last canary only boot.img it's necessarywhy alpha ? and also i mean just flashing patched boot.img right ? on coloros i flash patched boot.img with vbmeta do i need to flash it also ?
What version did this change in? Must have been very recent...??
Just want to make sure that I won't brick my phone.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.
What I did exactly was I uninstalled the magisk app only. Then I installed alpha. There was an update in the app. I updated. Reboot my phone. I then installed the OTA. After that finished I opened up magisk alpha and installed to inactive slot. Reboot my phoneJust want to make sure that I won't brick my phone.
From magisk manager first you do:
1. uninstall magisk
2. Install alpha apk magisk
3. Install alpha magisk zip
4 Reboot
5 Update fro local
6 install in inactive slot
Is it correct?
Thank you
No, this is incorrect that wil remove root.Just want to make sure that I won't brick my phone.
From magisk manager first you do:
1. uninstall magisk
2. Install alpha apk magisk
3. Install alpha magisk zip
4 Reboot
5 Update fro local
6 install in inactive slot
Is it correct?
Thank you
For 2022, the first order of business is to fix the annoying "not supported" warnings that's shown to 9-series users on OxygenOS 12. This is an erroneous warning, mostly because the app can't make sense of the inconsistencies introduced in the new ColorOS-based versions. If you're one of these users, don't worry — the app supports your device, and it is still running OxygenOS. You can ignore those warnings for now, and enable "advanced mode" in the app's settings.
This was a great help, thanks for sharing. Could I inquire as to the process you used to extract the boot image and then patch? Thanks
Boot from the image, run Magisk, choose to install and choose direct install.So do I use this to boot from like in OP? It's been awhile. Do I install Magisk from apk first, or after booting?
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.