I'm not sure what's wrong here but I patched a OxygenOS 10.0.1 stock boot img awhile ago and when I flash the patched boot img to get root, everything is normal but after a few days or a couple hours for some reason it'll revert back the stock boot img and I'll lose root and also my kernel will go back to the stock one.
Slot issue? maybe it crashes and reboots in the other slot
Instead of using patched images just boot to twrp and run the twrp installer then the magisk installer.
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.
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