Related
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
MichRT said:
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
Click to expand...
Click to collapse
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
You have to use last magisk (above 19.4 if my memories are right).
HpNoTiQ said:
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Click to expand...
Click to collapse
This looks like it might work, so thank you! I found a similar, though different solution (below)
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
I ran into the issue that while boot-looping with a magisk patched boot img, I wasn't able to run the command, adb wasn't finding the phone. I tried again after booting TWRP and it basically threw an 'error - command not found'.
HpNoTiQ said:
You have to use last magisk (above 19.4 if my memories are right).
Click to expand...
Click to collapse
I think you are right, in beta/canary channel
@Tulsadiver gave me a hand with this, see here: https://forum.xda-developers.com/showpost.php?p=80398385&postcount=35997
Thank you guys!
I have a Twrp backup with the boot img patched with Magisk/Twrp boot to recovery boots GSI with magisk boot to recovery hold volume up while rebooting to recovery will boot twrp for this boot img to work u have to be on the vendor of the boot img which is also in the backup so the phone won't bootloop this vendor is modified to work with GSIs pass the magisk environmental setup and notch fix so swiping down is like swiping down on stock.... to implement notch fix go to developer settings hide display cut and choose the first hide option and your notch will be fixed...
Thanks @Spaceminer for the twrp for without this none would of been possible
please note twrp will only boot with a android 9 vendor and your GSI will only boot with magisk and twrrp with the vendor in the backup cause it matches the boot img, GSIs only boot when the vendor and boot img match
the boot img & vendor img in the backup is from Channel/Retail (PPY29. 105-160-4)
Instructions
If on android 9 stock
1. Boot to bootloader
2. fastboot - w
3. fastboot GSI of your choice
4. fastboot boot twrp.img
5. format data
6. Place the twrp folder you downloaded from the zip into your devices internal storage which will be available after u format data
7.Resize system
8.Flash gapps zip if gapps is needed
9.wipe dalvick
10. go to twrp restore boot and vendor
11. reboot to recovery and phone will boot after boot is complete install magisk manager it will do the environmental setup phone will reboot and u will have magisk.... ( if u want the best experience with magisk on this device I recommend that you use havoc cause with the lineage GSI magisk doesn't play nice but with havoc its stable also when making a backup it's boot, system image, vendor image, data if u chose system instead your backup will bootloop your device upon restoration)
Download (twrp img is in twrp folder remove it and place it in ADB folder)
https://mega.nz/file/7t03DLhL#jjS9vgrJMlDS-_-hsApyx4uJ6L8wXCN8HtjSqJrg2ds
if u wanted to do this manually to install the latest canary or stable version magisk need to patch twrp to the recovery flash phh root boot up install magisk manager give it root permissions with phh superuser from apk mirror now with elevated permissions the option patch directly will be avaliable cause u got root (it's the recommended option ?) chose recovery and leave the other 2 unchecked patch the img and reboot to recovery the phone will reboot os with magisk and u hold up while booting recovery will boot twrp after that backup that boot img in twrrp for future installation of the GSI of your choosing....
Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!
xcode22 said:
Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!
Click to expand...
Click to collapse
Everytime u flash a GSI just use the vendor and boot from the twrp folder and your android 10 GSI Will have magisk and twrp no need for data disabler zip cause my backup already has the vendor and boot patches enabled for decryption so twrp will be accessible via boot to recovery
([emoji88]Havoc GSI[emoji88])
Also have edxposed for Android 10 since the one in the repo won't work cause it needs a custom magisk with merged patches for xposed to work on android 10 this version has the patches in the edxposed so having to use a custom magisk won't be an issue cause as ya know obtaining magisk and twrrp in this device was unknown into this OP was made
([emoji88]Havoc GSI[emoji88])
Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!
xcode22 said:
Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!
Click to expand...
Click to collapse
Your on a GSI go in your system settings and activate advance boot and when u have to reboot just put reboot to recovery and you don't have to worry about manually rebooting to recovery everytime u have to reboot also no way u installed the rom to the recovery partion our device doesn't have a recovery partion the recovery lives within the boot img
([emoji88]Havoc GSI[emoji88])]
thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks
xcode22 said:
thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks
Click to expand...
Click to collapse
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])
PoochyX said:
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])
Click to expand...
Click to collapse
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
PoochyX on telegram dm me I walk you threw it
([emoji88]Havoc GSI[emoji88])
xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
The easiest way I know of is from the stock OS using termux and root.
Code:
su
setenforce 0
mkdir /mnt/x && chmod 0755 /mnt/x
mount -o loop /dev/block/by-name/vendor_a /mnt/x
Now navigate to /mnt/x and everything from vendor will be in there. Find the file and delete it with a root explorer. Then unmount the partition and the changes will be permanent. Doing it this way gets around FEC, which is what prevents you from changing anything in vendor.
Code:
umount /mnt/x
If you need to work on the other vendor partition just change out vendor_a with vendor_b
Any recommendation about what GSI to choice for XT1952-6 variant?
mickem said:
Any recommendation about what GSI to choice for XT1952-6 variant?
Click to expand...
Click to collapse
Chaos GSI Bluetooth works without disabling audio effects (so u can use viper with bluetooth headset) it's clean stock with minimum stuff added to it and works with gravitybox then you got havoc that has the majority of stuff gravity has off the rip so it's not as minimum so more memory usage is needed and Bluetooth only works with the phh disable audio effects work around also magisk works good on both of these lineage is good also if you don't care about magisk working cause with our device magisk has issues on lineage don't know if it was fixed on a recent bulid however if lineage is your preference there is a phh root for it so u can be functional
([emoji88]Havoc GSI[emoji88])
My device is xt1952-4. I downloaded the latest firmware (PPYS29-105-160-4-8), and installed it to both slots. I am currently using Resurection Remix Pie. Is your patched boot.img and vendor compatible with the newer firmware or will I get a downgrade error?
Quick and concise how to for obtaining a Stock Boot Image from your Oneplus 8, 8T or 8 Pro device and patching with Magisk to create a fastboot flashable patched boot.img.
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked, broken or dead devices. This is a high-level
* how to for users with a basic knowledge of ADB and Fastboot. YOU alone are
* choosing to make these modifications, and you are solely responsible for your
* device's fit for use and wellbeing.
*
* Backup your data!
*
*/
PREREQUISITS:
An unpatched Stock Boot.img running on your device
General knowledge and understanding of ADB and Fastboot
Download latest op8, op8p, or op8t Horizon Kernel img from [e.g., op8p_7.img]:
https://dl.akr-developers.com/?dir=oneplus/horizon_kernel/R/images
Download latest Magisk Canary build from Github [e.g., app-debug.apk]:
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
DEVICE/PC OPERATIONS:
→ ADB
Enumerate devices
Code:
adb devices
Boot into Fastboot
Code:
reboot bootloader
→ FASTBOOT
Enumerate devices
Code:
fastboot devices
Determine the current slot (A/B), whichever slot you're on should be the "good" img
Code:
fastboot getvar current-slot
Boot with the custom kernel downloaded from Horizon to use root [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot boot "C:\Users\User\Downloads\op8p_R7.img"
Code:
fastboot boot xxxxxxx.img
→ ADB
Copy the boot.img from each slot to the root of the device
Code:
adb shell
su
dd if=/dev/block/sde11 of=/sdcard/boot_a.img
dd if=/dev/block/sde35 of=/sdcard/boot_b.img
→ Android Device [NOTE: Some Android 11 devices experience patching issues on the Beta Channel like bootloop] [NOTE: Some users experience issues on Canary like no SIM detected; if so switch to Beta]
Install Magisk app-debug.apk (Canary)
Go to Settings → Update Channel → Canary
Go to Home → Install → Install → Select and Patch A File
Navigate to internal storage and select the stock boot.img [choose the img from whichever slot you're on]
When it’s done patching copy the file, named magisk_patched.img, from the root → Downloads of your device to PC
→ ADB
Code:
reboot bootloader
→ FASTBOOT
Test to ensure it boots before flashing; if not you'll need to patch the other img
Code:
fastboot boot magisk_patched.img
→ Android Device
If the device boots and you have root in the Magisk Manager app, reboot the device into Fastboot then flash the active slot [NOTE: Both slots do not need to be flashed; just the current active slot]
→ FASTBOOT
Flash the patched image file [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot flash boot_b "C:\Users\User\Downloads\magisk_patched.img"
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
- OR -
Code:
fastboot flash boot_a magisk_patched.img
fastboot reboot
- OR -
Code:
fastboot flash boot_b magisk_patched.img
fastboot reboot
ADDITIONAL RESOURSES:
→ FASTBOOT
If you need to set the other slot to be the active slot use:
Code:
fastboot --set-active=a
- OR -
Code:
fastboot --set-active=b
→ ADB
ADB Magisk Bootloop Fix
Code:
adb shell
magisk --remove-modules
→ OTA Help
Magisk stock boot.img missing fix [NOTE: Android 11 onwards, the /sbin folder might not exist, so Magisk will randomly create a folder under /dev and use it as the base folder]
Rename to: stock_boot_0.img
Compress with gzip = stock_boot_0.img.gz
Copy stock_boot_0.img.gz file to the root of: /data
Edit the config file: /dev/xxxxxxx/.magisk/config → Change SHA1= to 0
Magisk Manager → Uninstall Magisk → Restore Images
→ ADB
Determine the random folder name generated by Magisk on Android 11+
Code:
ls -laR /dev | grep '.magisk/rootdir'
→ ADB
Determine the Boot Image partition location [NOTE: Will list all partitions; look for boot_a and boot_b]
Code:
ls /dev/block/bootdevice/by-name/ -all
Tried some other way on android 11 but failed, so back to android 10.
maybe i won't get android 11 until TWRP is work.
can't easily backup data without root is very annoying, thanks for the work!
I have followed every step, but root only last until I restart my Oneplus.
What am I doing wrong? Why want the device stay rooted?
mrram said:
I have followed every step, but root only last until I restart my Oneplus.
What am I doing wrong? Why want the device stay rooted?
Click to expand...
Click to collapse
Guessing here, but have a second look at these two commands:
Code:
fastboot boot magisk_patched.img
△ This will NOT flash the rooted image, it will only boot up once so you can test it or use it for temporary root
verses
Code:
fastboot flash boot magisk_patched.img
▲ This will flash the rooted image and is used after you've tested the patched image to be sure it doesn't bootloop and to have persistent root
If I use this Horizon kernel to boot with root on 11.0.4.4, could I use directly Magisk 22.0 to root the device permanently? Thanks in advance.
MagikGab said:
If I use this Horizon kernel to boot with root on 11.0.4.4, could I use directly Magisk 22.0 to root the device permanently? Thanks in advance.
Click to expand...
Click to collapse
I only use the Horizon to boot then grab my kernel to patch with Magisk. You could use the Horizon kernel, but you would have to flash it, not just boot it. So, root device, backup stock dtbo, flash Horizon & dtbo, re-root if lost during flash. I would recommend against that until there's a custom recovery available in case there were any issues. Additionally, you must backup your stock dtbo if you ever want to return to stock. You should visit the Horizon thread for more details, but again if you're not familiar with kennel mods you might not want to start learning on a device without a custom recovery.
CarvedArt said:
I only use the Horizon to boot then grab my kernel to patch with Magisk. You could use the Horizon kernel, but you would have to flash it, not just boot it. So, root device, backup stock dtbo, flash Horizon & dtbo, re-root if lost during flash. I would recommend against that until there's a custom recovery available in case there were any issues. Additionally, you must backup your stock dtbo if you ever want to return to stock. You should visit the Horizon thread for more details, but again if you're not familiar with kennel mods you might not want to start learning on a device without a custom recovery.
Click to expand...
Click to collapse
I'd like only to root my device, remaining as more stock as possible, for now. If I want to avoid using a custom kernel (also for the rooting process), should I extract the boot.img with Python, then patch it with Magisk 22? Thanks in advance for your reply, but I'm coming from a Xiaomi that was quite easier to root
MagikGab said:
I'd like only to root my device, remaining as more stock as possible, for now. If I want to avoid using a custom kernel (also for the rooting process), should I extract the boot.img with Python, then patch it with Magisk 22? Thanks in advance for your reply, but I'm coming from a Xiaomi that was quite easier to root
Click to expand...
Click to collapse
Just follow the steps above -- that'll get you a stock kernel (your current kernel) patched with Magisk and permanently rooted. The above process is only using the Horizon kernel to boot your device with root so that you can extract your kernel and patch it. The final result will be as stock as you can get with root.
Hey everyone. OP8 Pro user here. Just took OTA going from 11.0.9.9 running Magisk Canary 23 to the newest 11.0.10.10. I restored images before taking the OTA and reinstalled magisk to the other slot like I always do to retain root. Ive now lost root and am trying to boot the last two versions of the Horizon kernel. Ive tried the two latest ones (r9.2 and r9.2.1 from February 2021) and while they do boot my phone, I cant get SU access to extract the stock images.
Anything else that anyone things I should try? All i want from Christmas is root.
Isn't there a more easy way to obtain root?
That's strange. I use OnePlus smartphones with LineageOS for years now and cannot remember to execute such a complicated procedure. Just now I got a OnrPlus 8, installed LineageOS and Magisk and restored my apps with Titanium. So, it definitely worked.
Now, after a Lineage system update, root is gone.
Unfortunately I cannot tell exactly how I installed Magisk. I have a very poor memory. Think I just installed the app and said either just "install" or patched the zip with TRWP
But I definitely never downloaded or extracted any boot image manually.
Has anyone an explanation for this?
Even more strange: I just tried to flash magisk.zip again with TRWP. Now it tells me
"Magisk patched boot image detected"
and later:
"Failed to mount '/system_root' (Device or resource busy)"
After reboot the Magisk app now offers me three choices in the install tab:
- choose a file and patch (only this one existed before)
- direct installation (recommended)
- install into inactive slot (after OTA)
I don't understand the last one and tried the recommendet one.
Now, root is there again. Do I have to do this after each update? With my OnePlus5 I didn't.
Unfortunately I have another problem with my OnePlus8 and Lineage:
I'm using AdAway which replaces the hosts file, but on my OP8 it cannot.
"Unable to cppy the hosts file to /System partition. Please check if the Magisk Systemless module is active"
What does it mean? The Magisk app says: "ramdisk yes"
tosho1 said:
Unfortunately I have another problem with my OnePlus8 and Lineage:
I'm using AdAway which replaces the hosts file, but on my OP8 it cannot.
"Unable to cppy the hosts file to /System partition. Please check if the Magisk Systemless module is active"
What does it mean? The Magisk app says: "ramdisk yes"
Click to expand...
Click to collapse
Magisk → Settings (Gear icon) → Systemless hosts ← Click it
tosho1 said:
Isn't there a more easy way to obtain root?
That's strange. I use OnePlus smartphones with LineageOS for years now and cannot remember to execute such a complicated procedure. Just now I got a OnrPlus 8, installed LineageOS and Magisk and restored my apps with Titanium. So, it definitely worked.
Now, after a Lineage system update, root is gone.
Unfortunately I cannot tell exactly how I installed Magisk. I have a very poor memory. Think I just installed the app and said either just "install" or patched the zip with TRWP
But I definitely never downloaded or extracted any boot image manually.
Has anyone an explanation for this?
Even more strange: I just tried to flash magisk.zip again with TRWP. Now it tells me
"Magisk patched boot image detected"
and later:
"Failed to mount '/system_root' (Device or resource busy)"
After reboot the Magisk app now offers me three choices in the install tab:
- choose a file and patch (only this one existed before)
- direct installation (recommended)
- install into inactive slot (after OTA)
I don't understand the last one and tried the recommendet one.
Now, root is there again. Do I have to do this after each update? With my OnePlus5 I didn't.
Click to expand...
Click to collapse
LineageOS is not the stock ROM so it's slightly different and not covered in this thread.
Thank you, CarvedArt. I wasn't aware of this.
Does anyone have the latest stable Android 13 patched boot image for the IN2015 that they can share with me ?
Hello,
I have a problem with my FP3. When I flash the Magisk zip with TWRP or when I flash the patched boot image through Fastboot mode, Magisk is not completely installed. I need to boot et click on the "Magisk app" with a standard icon to install it and to access Magisk Manager. Without this, Magisk is not really installed since "su" or magisk executable are not in /sbin.
I need a way to manually install/upgrade Magisk through recovery (TWRP) to obtain the su. In my context, I have constraints preventing the installation through GUI.
Have you already done this before ?
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
You could use DFE (If you want unencrypted data) or use magisk module for recovery. to remove unwanted magisk modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
There is magisk module which check on start of the phone if any module makes a bootlop and disable it. Magisk Bootloop saver on github
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
Power phone off completely. Power on and when MIUI logo shows on screen hold volume down button until phone boots, this will disable all magisk modules you have installed. It's called magisk safe mode. You can now enter magisk app and enable modules one by one until you find the culprit.
Sidenote: I upgraded from xiaomi.eu 12.0.6 to 13.0.3 using fastboot. TWRP was unable to decrypt when I booted to recovery to install magisk after update. I rebooted back to MIUI and disabled pin and fingerprint. Rebooted back to TWRP and was able to access data and install magisk from the downloads folder. So try disabling screen lock and see if TWRP is working then.
Well orangefox has magisk manager built in, so modules can be removed with a swipe
you can navigate to data/adb/modules folder in twrp file manager without decryption needed and delete module folder.
worked for me on android 12.
I got stuck at Xiaomi logo after installing some module. The storage is encrypted on Android 12, decryption in recovery is not possible at the moment. So using OrangeFox or deleting /data/... is not possible.
The only solution that worked for me was accessing the safe mode and running this command from adb shell.
magisk --remove-modules