Does someone mind providing this?
11.0.4.1GM21AA
I've updated to this version and I tried patching myself with magisk but I simply can't boot into the patched boot image.
Maybe one of yours will work
Please
Thank you!
I recently updated to 11.0.4.1 and lost Magisk root. Had root on 11.0.3.1, everything was fine.
Tried patching boot image via magisk, and then flashing it on both boot slots like I did with previous versions. But with this one, after patching and I boot into android, magisk says it has no root.
Anyone experienced this?
Thank you
Got OP7P Global version
can't seem to get root in any way
I'm running Android 11, A/B Partitions and Ramdisk: Yes
I've tried using patched boot image, it boots no root.
I've tried installing custom recovery, flash magisk.zip, it boots no root.
What more can I do? Please
Related
I have TWRP installed but any time I try to Flash magisk, the boot image seems to corrupt and leaves me on the 'Bootloader unlocked' screen. I have to boot back into bootloader and use the 'repair recovery boot loop' option just to get back into my phone which then doesn't have Magisk available and root has not taken. Does anyone have any advice? Is there a boot image I need to flash after Magisk maybe? I'm fairly new to all this.
Isadorian said:
I have TWRP installed but any time I try to Flash magisk, the boot image seems to corrupt and leaves me on the 'Bootloader unlocked' screen. I have to boot back into bootloader and use the 'repair recovery boot loop' option just to get back into my phone which then doesn't have Magisk available and root has not taken. Does anyone have any advice? Is there a boot image I need to flash after Magisk maybe? I'm fairly new to all this.
Click to expand...
Click to collapse
Hello, would love to know because I have same issue here …
In fact I could effectively have root and magisk installed once, then I installed viper which didn't work... I removed viper module from Magisk Manager, then reboot, then got into the issue you describe. The 'repair recovery boot loop' allows booting but magisk is removed. And if I flash magisk again from TWRP, then the phone won't boot.
I tried reinstall TWRP/Magisk without success, tried lock/unlock bootloader (don't do that ! I could get out of it but no more success with magisk), also tried to remove the viper module with TWRP file manager (I could but it did not solve the issue), not sure what to do now.
What versions TWRP and Magisk?
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Intruder_Alert said:
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Click to expand...
Click to collapse
When u have a customer recovery, download the last magisk.zip and flash it. Simple
Release Magisk v22.0 · topjohnwu/Magisk
RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN! Another major Magisk release! This time our focus is not the core Magisk implementation, but rather on improving the w...
github.com
In the installation guide they wrote that u have rename only the apk to zip. Very simple
joke19 said:
When u have a customer recovery, download the last magisk.zip and flash it. Simple
Release Magisk v22.0 · topjohnwu/Magisk
RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN! Another major Magisk release! This time our focus is not the core Magisk implementation, but rather on improving the w...
github.com
In the installation guide they wrote that u have rename only the apk to zip. Very simple
Click to expand...
Click to collapse
That is only for the Magisk app, not to root the phone. Rooting the phone is a totally different procedure.
Number ome was the last zip with I root my phone with simple flash and number 2 is the new one.
Look inside.
Here the how to from magisk for a customer recovery.
Download the Magisk APK
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.
Flash the zip just like any other ordinary flashable zip.
Check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.
Intruder_Alert said:
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Click to expand...
Click to collapse
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
wedgehog said:
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
Click to expand...
Click to collapse
Patching the images does not work. But installing the magisk.zip (the latest version) through TWRP or OrangeFox does work (tested and confirmed)! I don't get why it works when installing the zip and does not when patching a recovery.img but this is what we got...
Fun Fact, the instruction manual states you have to hold the HW key to enter recovery until the boot logo shows up, for me now the device is rooted on every boot without any issues, without the need to hold down any buttons.
wedgehog said:
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
Click to expand...
Click to collapse
I just decided to update to V12.1.3 yesterday and got the same problem as yours. Keep trying every version of magisk, from latest and its previous to no avail. It got stuck at MIUI logo even when I left for good half an hour. If I didnt flash magisk zip it loads just as normal but without root, but I still want magisk.
Today I just thought of trying different version of recovery. The current one is TWRP-3.3.2B-0219-XIAOMI_CC9PRO-CN-wzsx150 that got me stuck. Then I flash [email protected]_2.zip recovery. Flash V12.1.3 followed by Magisk-v22-0.zip using OrangeFox worked wonderful. Hope it can help you if you are still stuck like me. Now I can sleep at night.
pawn_broker004 said:
I just decided to update to V12.1.3 yesterday and got the same problem as yours. Keep trying every version of magisk, from latest and its previous to no avail. It got stuck at MIUI logo even when I left for good half an hour. If I didnt flash magisk zip it loads just as normal but without root, but I still want magisk.
Today I just thought of trying different version of recovery. The current one is TWRP-3.3.2B-0219-XIAOMI_CC9PRO-CN-wzsx150 that got me stuck. Then I flash [email protected]_2.zip recovery. Flash V12.1.3 followed by Magisk-v22-0.zip using OrangeFox worked wonderful. Hope it can help you if you are still stuck like me. Now I can sleep at night.
Click to expand...
Click to collapse
Right now I'm still in trouble, after a Magisk update, my phone got stuck in bootloop I had to wipe everything.
But nor the latest .Eu or Global ROM works with Magisk now. I followed the guide by topjonwho (Magisk dev) that says if I don't have a boot.img, I have to modify the recovery.
Well, no luck.
But! If I take the boot.img from the fastboot ROM, and modify that with Magisk, I can boot it up with root. But if I flash that boot.img I'm still stuck on boot. Same with original and TWRP recovery.
You say using [email protected]_2.zip I can just simply flash Magisk 22.1 az a .zip, like in the good old days?
insetta said:
Right now I'm still in trouble, after a Magisk update, my phone got stuck in bootloop I had to wipe everything.
But nor the latest .Eu or Global ROM works with Magisk now. I followed the guide by topjonwho (Magisk dev) that says if I don't have a boot.img, I have to modify the recovery.
Well, no luck.
But! If I take the boot.img from the fastboot ROM, and modify that with Magisk, I can boot it up with root. But if I flash that boot.img I'm still stuck on boot. Same with original and TWRP recovery.
You say using [email protected]_2.zip I can just simply flash Magisk 22.1 az a .zip, like in the goof old days?
Click to expand...
Click to collapse
Yup, tried that boot.img method doesn't work too.
It was magisk 22.0 when I upgraded to 12.1.3 but i guess 22.1 works the same. So nervous waiting the MIUI screen for about 15 minutes, relieved when it finally went through.
Now I'm already upgraded to 12.1.5 magisk 22.1 using the same method. Flash rom followed by magisk zip, like good old days.
pawn_broker004 said:
Yup, tried that boot.img method doesn't work too.
It was magisk 22.0 when I upgraded to 12.1.3 but i guess 22.1 works the same. So nervous waiting the MIUI screen for about 15 minutes, relieved when it finally went through.
Now I'm already upgraded to 12.1.5 magisk 22.1 using the same method. Flash rom followed by magisk zip, like good old days.
Click to expand...
Click to collapse
So I'll have wait at boot for about 15 min? I'm afraid of screen burn-in.
Hi, I always use Orange fox but after the Android 11 update I am not able to see any files after installing custom recovery (Orange fox latest). When I boot my phone into orange fox recovery, it is not showing my files. Files are shown as renamed as fkffqwhfjkfhsf something like that
mdalarian said:
Hi, I always use Orange fox but after the Android 11 update I am not able to see any files after installing custom recovery (Orange fox latest). When I boot my phone into orange fox recovery, it is not showing my files. Files are shown as renamed as fkffqwhfjkfhsf something like that
Click to expand...
Click to collapse
Can you see your files while your phone is booted into OS?
Chances are, the encryption type changed from FDE to FBE, meaning the master key no longer works.
I suggest you backup everything now to a computer, because you can end up like me, and lose access to any file on the phone.
If you saved everything you deem precious from your phone, you need to do a wipe, and then FORMAT /data in recovery.
This will factory reset your phone, but it will work proper with the recovery.
Hi all,
Yesterday I was messing around with V4A and following the final installation steps my phone got stuck in fastboot. To fix it I did the following:
1. I extracted the stock boot.img from my current OS version (10.3.12) and flashed it to boot_a and boot_b using fastboot. This restored the phone's ability to boot.
2. I booted the phone and went into the Magisk app to disable/unhide as much as possible and uninstalled the V4A app.
3. Rebooted into fastboot and booted into TWRP to remove Magisk, V4A and Vanced stuff from data/adb with the file manager.
4. Booted and flashed various combinations of TWRP versions (Mauronofrio, Bluspark) and Magisk (from 19.4 to 23.0). TWRP flashes fine and allows system to boot, but as soon as Magisk is flashed and a reboot is tried into system, it gets stuck on bootloader again and I have to repeat step 1.
(5. Tried patching stock boot.img file with the Magisk app. Same results as step 4.)
Does anyone here know what might be wrong? Is there another method I can try to regain Magisk without losing data?
Thanks in advance!
EDIT: really at a loss here. Idk why but as soon as magisk is flashed, the system refuses to boot. Without flashing magisk, system boots fine – am typing from it now. I figured at first that it had to do with remnants of AML, V4A and other Magisk modules not being properly removed, but I've removed those through TWRP file manager.
Really hoping one of you can point out something I've missed or think of something else I can try.
EDIT: solved! See update below.
UPDATE: solved it by forcing a local upgrade of the full OTA through phone settings (same version as mentioned above), causing it to switch slots. On the other slot, the system managed to boot after flashing TWRP and Magisk (latest versions).
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
May be the first thing I'd think of trying it to disable any/all Magisk module installed.
Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...
OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...
Hope that can and will point you into the right direction.
I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.
Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
wugga3 said:
May be the first thing I'd think of trying it to disable any/all Magisk module installed.
Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...
OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...
Hope that can and will point you into the right direction.
I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.
Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
Click to expand...
Click to collapse
Hello, thanks for the reply, I wanna get a few things straight before doing anything that have the potential to brick my phone.
1. My phone rn isn't rooted, so I cant uninstall or disable Magisk modules, I CAN root my device but it is very unstable and im not sure doing it is a good idea, maybe there's another way to disable them?
2. What do you mean by dirty flash? Using the device update section and selecting the official OOS version I downloaded from OnePlus.com?
1) may be forget about root for now as that's probably not the priority at this time. Getting a stable operating system is the priority. And skip TWRP (don't see the point of if being needed at this step either).
2) my best guess is that I've used oxygen updater from the play store to download the full update (not incremental update) that exactly matches the one you have installed now - or search here and find the match to download or used the OnePlus cite to get the file. Then once that is downloaded to your device - go to settings/system/system updates/local update and install and reboot. That's the dirty Flash as in don't wipe/reset your device either before/after the installation. I'm hoping that this method will clean up both the recovery and boot images to stock and hopefully restore stability to your device without the wipe/reset.
Hope that helps and restore the device stability without TWRP nor root.
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.
My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
NitayMa'ah said:
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.
My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
Click to expand...
Click to collapse
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
hammered58 said:
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
Click to expand...
Click to collapse
Ill try it now thank you
NitayMa'ah said:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
Click to expand...
Click to collapse
Here's a image file you can flash in fastboot. It's
NitayMa'ah said:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
Click to expand...
Click to collapse
Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..
fastboot flash boot boot-v9-root24.img...
Also it's easier to just flash both slots by this commands..
Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...
I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
Fixed!
Thanks so much for the suggestions, which I might didn't fully consider in a rush...
The solution was to root my phone, reboot it all shaky and try to disable all Magisk modules (took me 2 tries because of the crashes and stuff), then flash again the original boot image, rebooting, creating a rooted boot.img using Magisk and flashing it.
Littlemether said:
Here's a image file you can flash in fastboot. It's
Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..
fastboot flash boot boot-v9-root24.img...
Also it's easier to just flash both slots by this commands..
Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...
I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
Click to expand...
Click to collapse
First of all thanks for the help but I ended up fixing it in another way.
Second of all, not really related but do you know if I can use this recovery on OP7Pro A12 custom Rom? (and flash it)
Okay so I was rooted on Android 12 did the OTA patch in magisk before upgrading to Android 13. I was stuck on the logo for a very long time so I flashed the original Android 13 Boot and booted back up. So then I extracted the boot image and patched it in the magisk app and then flashed it and the same thing happened stuck on the logo. So I flashed the original boot image and booted back up. Next I found a modified version of TWRP so I was able to boot into it using fast boot everything was working within TWRP. I tried to flash magisk through there and it was a no-go I assume it's not possible to root Android 13 at this moment so I'm going to downgrade back to Android 12. If anybody has any ideas or suggestions or if you were able to keep Root let me know how you did it please
Use magisk 26.1 and patch boot.img. it will work. Twrp will be replaced by regular recovery. If you want twrp use "fastboot boot (twrp.img)" command from pc and dont replace recovery to twrp or you will lose magisk root
Please boot to twrp, go to /data/adb/modules and disable all of them by executing "touch disable" in each module folder. After this try booting with magisk patched boot.img, it should work.
chairman011 said:
Okay so I was rooted on Android 12 did the OTA patch in magisk before upgrading to Android 13. I was stuck on the logo for a very long time so I flashed the original Android 13 Boot and booted back up. So then I extracted the boot image and patched it in the magisk app and then flashed it and the same thing happened stuck on the logo. So I flashed the original boot image and booted back up. Next I found a modified version of TWRP so I was able to boot into it using fast boot everything was working within TWRP. I tried to flash magisk through there and it was a no-go I assume it's not possible to root Android 13 at this moment so I'm going to downgrade back to Android 12. If anybody has any ideas or suggestions or if you were able to keep Root let me know how you did it please
Click to expand...
Click to collapse