Related
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.
Hello everyone! Thanks in advance for taking a look at this thread.
I recently upgraded from a Pixel 2 to a Pixel 5 and decide to root my old phone and mess around with that before doing the same with my new phone. It's been several years since I've messed around with rooting a device, so I've spent some time this week refreshing myself on how to do so.
I've already unlocked my bootloader, but the main issue that I'm running into is when I try to install TWRP or Magisk. For some reason, when I try to flash TWRP (version 3.3.0.0), I've managed to install it properly but loading into recovery mode just leaves me stuck at the TWRP splash screen, while booting directly into it doesn't allow me to backup my data (kicking out an error 255 each time). It would be nice to have TWRP to be able to back up rather than starting from scratch each time, even if I've gotten quick at flashing the stock image when I screw up later.
As for Magisk, I've tried flashing the patched boot image through TWRP and received errors (size of image is larger than target device) as well as the .zip file which just caused a bootloop. I know you can install Magisk without TWRP, so I've tried doing that as well. I've been working with both Magisk 23.0 and the Canary build with no luck; after patching the boot image and attempting to flash it using fastboot flash boot magisk_patched.img, I just repeatedly get an error showing "FAILED (remote: 'Error flashing partition')".
So far I've not really been able to find any solutions on how to fix this, so I feel a bit stuck at this point (and definitely questioning my ability to just follow directions). Any advice on how I might get around these errors?
Hello mate,
With regards to installing twrp, I think there is a workaround in the official twrp thread to get twrp installed with working decryption and working pin by rolling back to a pie build prior to encryption being broken for twrp. Personally I just fastboot it when needed to flash anything but sadly twrp back ups don't work (I'm on A11).
It sounds as if you have tried to install magisk a few ways but I found the simplest way was to install the latest magisk.apk then rename it to magisk.zip and flash it via fasbooted twrp.
It sounds as if you tried patching the image etc so may pay to reflash the stock boot.img and then do the APK/zip method to get magisk running.
Lastly, if you don't mind losing your data it may well pay to reflash a full stock.img and then try magisk again. It's solved a few dramas for me when stuff didn't seem to work first time round.
Hello everyone, today i was updating the phone as i always do, installing magisk in the idle slot, after installing the update, and then restarting the phone.
Unfortunately this time for an oversight I restarted the phone without installing magisk in the inactive slot and I lost root permissions.
Because i don't have the trwp recovery how can I get the permissions back? Can I flash the boot image directly from the magisk app?
Now my OOS is 10.3.12 and i can't find an image boot for this version.
I hope someone can help me thank you.
You have to patch via magisk the boot.img file of the 10.3.12 rom then flash it via adb flash boot_patched.img
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)
Just so that everyone is aware because no one here seems to be aware of anything...
TWRP version twrp-3.6.1_11-0-redfin.img from here: https://dl.twrp.me/redfin/
Works just fine if you just temp boot from fastboot with the most recent OTA SPA2A.220405.003
And you DO NOT HAVE TO INSTALL A KERNEL FOR IT TO WORK, THIS BUILD ONLY
With this build, you can indeed backup and restore your system. I have used this build since it was live, and it works no problem.
I cannot confirm it works with any other build, nor can I confirm you can install it to ramdisk and get it to work.
But it works just fine with temp booting from fastboot. Backup, Restore, etc works just fine for me. I have gone back and forth from my build to the OTA no problem whatsoever, and have been able to restore all userdata from the most recent OTA.
BIG THANKS TO TWRP, AND bigbiff for his work
and, btw, you have to reboot anywhere from 1 to 3 times after a restore for it to completely boot.
You'll see the old boot logo first and it will freeze, then the new boot logo and it could freeze, then the third time it boots just fine. They even have this listed on TWRP's site I believe.
So, if you're having trouble after a restore, just reboot a few times but wait until it hangs before you do. It will eventually come up.
Also, it is possible to install this same recovery to your boot.img ramdisk. You cannot flash this image directly or else you will end up in a boot loop.
In order to install permanently to the ramdisk, you have to disable verity and verification just like for root, then temp boot the twrp.img, then while in recovery adb push twrp.img /
Then go to install, and choose the twrp.img and it will ramdisk install it. Then wipe all userdata--must be done, no way around it.
Reboot to recovery, and backup the boot.img only. Then copy the boot.emmc.win to somewhere on your internal SD card as twrpboot.img.Then you need to boot into the system, install magisk app, and then patch twrpboot.img, then reboot to bootloader and flash the patched boot.
After all of that you will have both a rooted boot.img with permanent recovery in the ramdisk.
I do not know anything about safety net as I don't use any kind of banking apps at all so that will be your own responsibility to deal with.
That's so good to finally hear, looks like I'm going to have to do this. Thanks for the update, off topic but considering making a guide with as many links to projects, roms, kernels, etc that are being made or in process specifically for our phone and differentiating a11 and a12 support
stayboogy_Officially said:
Then copy the boot.emmc.win to somewhere on your internal SD card as twrpboot.img.Then you need to boot into the system, install magisk app, and then patch twrpboot.img
Click to expand...
Click to collapse
This worked for me. I have Magisk and TWRP installed on stock Android 12.1 version 220305.
I was worried because I did not actively Disable Verity or Verification , or unencrypt anything.
But I am able to make full backups, and restore them, which is what i care about
I updated to Android build SP2A.220505.002 (via TWRP 3.6.2, magisk 24.3, and the May 2022 ota update file).
No problems yet..
has anyone updated to Android13 ?