Magisk module for recovery used to work in my earlier phones, but doesn't work on Mi A2, I need to wipe my phone every time a wrong module starts a bootloop. Is there a simpler workaround without having to wipe my phone every time I install a wrong module?
Won't flashing the stock boot.img fix the bootloop?
Related
I want to install module "power nap" but I wanted to be prepared for a bootloop I wanted to know how to repair a bootloop I wanted to know if it is the correct method to repair a bootloop by xposed
Would it be flashing the "xposed-uninstaller-20160829-arm.zip" simply?
novatosuper said:
I want to install module "power nap" but I wanted to be prepared for a bootloop I wanted to know how to repair a bootloop I wanted to know if it is the correct method to repair a bootloop by xposed
Would it be flashing the "xposed-uninstaller-20160829-arm.zip" simply?
Click to expand...
Click to collapse
In case you encounter a bootloop after flashing Xposed (or installing any module), you can boot into recovery (TWRP recommended) and flash the uninstaller.zip file to solve the bootloop. Wipe cache&dalvik cache afterwards from within recovery to clear remaining stuff and reboot your device again.
For the latest uninstaller.zip, check the official announcement thread:
https://forum.xda-developers.com/showthread.php?t=3034811
Download the corresponding version for your device and transfer the .zip file to your device. I guess your device requires the "arm" version (identical to the one you mentioned above).
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
whoiam55 said:
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
Click to expand...
Click to collapse
You can remove a module via recovery (mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img to disable magisk then you can remove the module from the manager itself.
Sent from my MI 5 using Tapatalk
teddy0209 said:
(mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img
Click to expand...
Click to collapse
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
whoiam55 said:
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
Click to expand...
Click to collapse
You can find the latter in the download section, the first on the compilation of modules... Your unpatched boot.img/stock boot.img, you can find it inside your room zip, from your twrp backup if you did backup prior to installing magisk. Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Sent from my MI 5 using Tapatalk
teddy0209 said:
Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Click to expand...
Click to collapse
So your are saying that if it stuck on boot then I can go back to TWRP, select /data/boot.img and flash it to boot partition?
One more think suppose I install *X* module and it succeed, then I install *Y* module and it failed to boot. Now I flashed boot.img as written above will it contain *X* module or just a fresh boot.img?
Thanks again for the reply.
I've tried to install Magisk and I had no problems at first. I downloaded Magisk Module and tried to install some modules, I rebooted my phone and it was stuck on a bootloop. Luckily I had the rom availabe so installed it using hrupdater.zip. Everything was back to normal without magisk installed, I assume a module is causing the bootloop, so I did some investigating and found the unimod module, I tried too flash it from twrp and it keeps ending with error 1. The same thing happens with magisk uninstaller and mount magisk. I'm also unable to wipe cache but I dont know if that's a seperate issue
Please post the recovery log showing those errors. Impossible to definitely say what's wrong otherwise.
Read a similar problem from this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
I'm already unlocked and I was gonna stick with the China ROM for now, so I flashed Magisk. After an hour I noticed my root access WAS GONE. So tried restarting it and... bootloop! Magisk uninstaller fixed this BUT I want that Magisk. So I kept retrying... Fastboot, flash TWRP(another issue is TWRP wont stick no matter what it will be replaced by stock recovery), Install magisk, bootloop... Rinse and repeat.
I tried 2 methods installing Magisk. TWRP and the Boot Image Patching using boot.img from latest China ROM miui_RAPHAEL_V10.3.12.0.PFKCNXM_75ea367433_9.0.zip
Im running out of ideas, can anyone here help and share how they fixed it? Thanks!
you should change to Xiaomi EU rom, no issues with Magisk.
Try installing ver 18 or 18.1 magisk i had issues with ver 19 and up on pocof1. Also on pocof1 you had to install dfe (disable force encryption) and them twrp wouldnt be replaced with stock boot recovery. Also any update that comes when twrp is installed will rewrite it to stock recovery.
Wipe userdata/factory reset after installing magisk
I have the same issue and resolve it by install OrangeFox-R10.0_8-Stable & Magisk-v20.1.zip.
I have LLD-L31(C432) and a while ago I went through the process of unlocking bootloader and flashing magisk. I did this without custom recovery as it caused problems but it worked and I had magisk and root fully working. However, I think I tried to install a version of xposed that was incompatible with my os (EMUI 9). This caused bootloop every time I tried to boot into recovery(system with magisk).
I can still use the device but some apps can still see xposed and won't work. I can try to boot into the system with magisk but it loops - maybe because of xposed.
I have seen that you can flash xposed uninstaller, will this wipe data and will it work? Or is there a way to remove it and get magisk back without loss of data.
Alternatively (if this option results in a more stable magisk installation),could I flash twrp to recovery and then flash magisk to my system boot to have magisk permanently? and will this method wipe data?
Edit: I flashed twrp to recovery but when I boot to it, it just loads fastboot with reason bootloader 1 any help?
Thanks