Hello! Today I decided I would give Xposed another chance (I tried installing it through Magisk before, resulted in bootloop). After installing it through TWRP, my phone got stuck in a bootloop. I tried using the Xposed Uninstaller. Didn't work. I tried entering Safe Mode. Didn't work. I tried resetting my phone in TWRP. Also didn't work. How can I get rid of it? Please help, I just want to uninstall Xposed so I can use my phone again). Thanks!
Ovidiu05 said:
Hello! Today I decided I would give Xposed another chance (I tried installing it through Magisk before, resulted in bootloop). After installing it through TWRP, my phone got stuck in a bootloop. I tried using the Xposed Uninstaller. Didn't work. I tried entering Safe Mode. Didn't work. I tried resetting my phone in TWRP. Also didn't work. How can I get rid of it? Please help, I just want to uninstall Xposed so I can use my phone again). Thanks!
Click to expand...
Click to collapse
I guess the only way to revert this is to flash the stock firmware over with Mi Tools.
I'm saying this as a layman, because I'm still studying before doing any dangerous experiments with my mido.
But I've read a few minutes ago that there are specific ports of Xposed for mido. Maybe you should try those. I don't have the links right now, but if you dig up in the forums, you'll probably find what you are looking for.
Those videos on YT also helps, but they're not 100% guarantee that will work at all. You should proceed by reading a lot before tinkering with this stuff, you know.
It's my 1st attempt as well, so I just hope I do everything right to do not result in something like you had. ?
Hi guys. I need some help for my rooted galaxy note 8. I had rooted my phone a long ago and all was working good. All apps including banking apps were working fine with magisk hide. But few days ago i wanted to update my phone so i flashed stock rom with odin and updated my device. Earlier my bootloader version was 6 and now its updated to version 8. Then after updating i flashed latest twrp and rooted with magisk. I flashed magisk version 20.1 and magisk manager version was 7.4.0 . Then magisk update was available so i updated to magisk version 20.2 and magisk manager to version 7.5.0 . Now the problem starts. I am facing 3 issues.
1- my phone starts freezing and then reboots randomly. It happens quite frequently atleast 2-3 times in a day. Every time i clear cache partition from twrp but problem persists. I had checked ram also but ram useage is also fine. Please help me with this issue.
2- while searching for the solution of above problem i read somewhere that it might be because of safety net check. Earlier safetynet check was pass but now safety net check was fail. I flashed bypass safety net mod. But when my phone reboot a warning appears that your device has some internal problem. Contact the manufacturer. I pressed ok and phone starts. It seems to work normal but then i realised my device was not connecting to any wifi network. When i click on available wifi nothing happened. So i uninstalled the safety net bypass mod and then wifi start working again.
3- now final thing i want to know. If the above problem did not solve then i have to unroot my phone which i dont want. But if i had to then i dont want to flash stock rom. I want to unroot from magisk app itself. I had edited build.prop file for using samsung health app. So now if i unroot from magisk app will the changes made by me in build.prop file remain or it will revert back. Also will banking apps work or not....
I know its very lengthy post but please help
Wow...
70 views no comment..... it seems all the developers and tech people are enjoying winter break
Try going back to previous version of Magisk. I have Snapdragon N8 so I have supersu. But I did update my A20g with newest Magisk and had an issue. I know you have N8 but was just saying maybe could be new Magisk.
My SM-N950U Still Rooted Note 8
Hey, everybody. First post. I need some serious help. I've been rooting and modding for years, but I don't know everything, so please don't assume that I do. Right, my Exynos G973F is rooted with Thunderstorm Kernel, and has TWRP installed. The phone functions perfectly and all of my apps pass root detection. However, if I restart the phone, it gets to the point where all my icons load and I can use the phone, then it suddenly goes back to the Samsung logo. The case used to be that if I left it long enough, it wouldn't continue to bootloop, but recently I'm having to restore TWRP images just to use my phone. I've done a factory reset, and tried to do the same thing with a custom kernel, but it will not pass safetynet. I've got Riru installed, LSExposed, safetynet patch 2.2.0 and Magisk Hide patch, with a different fingerprint set, and it absolutely won't pass cts. So, starting from scratch is not an option, because I've tried everything. How can I figure out what's making it bootloop? As I've said, the phone is perfect, other than this. It's really bizarre. Hope someone can help! Thanks in advance!
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Backup your data, then do a factory reset.
Thanks, I've tried that multiple times actually. Unfortunately it doesn't fix it
Same problem here. Flashed my phone with EU ROM, it will reboot to recovery mode several times before it starts up with normal MIUI. Note: Bootloader was in unlock status. Anyone has a solution?
hympe said:
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Click to expand...
Click to collapse
I have this exact same issue.....
I dont know why this happend and how to fix this annoying issue!!
Which ROM do you have installed?
Oceanone said:
Same problem here. Flashed my phone with EU ROM, it will reboot to recovery mode several times before it starts up with normal MIUI. Note: Bootloader was in unlock status. Anyone has a solution?
Click to expand...
Click to collapse
Could you explain what your situation is right now?
Im also flashed to EU ROM of Xiaomi Official. And phone boots into to the recovery on every reboot, after a few reboots the phone boots in to the normal OS.
Same issue, same topic:
Phone-Root boots into the Miui recovery with root (NON-TWRP)
Hi, Im testing my phone without, NON-TWRP. After root, and shutdown/restart the phone, the phone boots automaticly to Miui recovery instead of starting the phone normally... After 10 min, the phone starts in the normall mode with root. How to...
forum.xda-developers.com
aygul12345 said:
Could you explain what your situation is right now?
Im also flashed to EU ROM of Xiaomi Official. And phone boots into to the recovery on every reboot, after a few reboots the phone boots in to the normal OS.
Click to expand...
Click to collapse
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
I'm smashing my head around....
Oceanone said:
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
Click to expand...
Click to collapse
I'm smashing my head around this... Exact same issue....
Flashing the latest EEA from, and installing 2 modules to hide that I'm being unlocked the boat loader, from that point if I restart than occurs the recovery boot loop.
Same moment not 30 days later.
Oceanone said:
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
Click to expand...
Click to collapse
Did you test if you flashed fresh your EEA ROM, and doesnt installed one of the modules, does it then also reboot into the recovery bootloop? Im troubleshooting maby the module is corrupt (Magisk props hide / fingerprint).
hympe said:
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Click to expand...
Click to collapse
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
aygul12345 said:
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
I installed Universal SafetyNet Fix v2.2.1 (Author: kdrag0n) on my phone.
aygul12345 said:
Did you test if you flashed fresh your EEA ROM, and doesnt installed one of the modules, does it then also reboot into the recovery bootloop? Im troubleshooting maby the module is corrupt (Magisk props hide / fingerprint).
Click to expand...
Click to collapse
I didn't text that, because I need to use both Android Auto and Google Pay. To use AA, I have to unlock bootloader. To use google pay, I have to install a module to hide root.
Oceanone said:
I installed Universal SafetyNet Fix v2.2.1 (Author: kdrag0n) on my phone.
Click to expand...
Click to collapse
Im testing a few days, and it seems to be that the Universal Safetynet fix Author Kdrag0n , gives this bootloop Recovery. If I flash fresh a EEA ROM from scratch, and install ONLY this module, then it boots into the recovery WITHOUT TWRP into Recovery MUIU 5.0 and with TWRP in to Recovery TWRP.
Can you test it for me by disabling ONLY this module Safetyfix, and give your phone a reboot, if this still happens boots into the recovery?
aygul12345 said:
Im testing a few days, and it seems to be that the Universal Safetynet fix Author Kdrag0n , gives this bootloop Recovery. If I flash fresh a EEA ROM from scratch, and install ONLY this module, then it boots into the recovery WITHOUT TWRP into Recovery MUIU 5.0 and with TWRP in to Recovery TWRP.
Can you test it for me by disabling ONLY this module Safetyfix, and give your phone a reboot, if this still happens boots into the recovery?
Click to expand...
Click to collapse
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
Thanks for your confirmation.
As we speak im writing right now an issue. to the author. Let you know when its done.
aygul12345 said:
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
I actually have. I've got the v2.2.0. and I see there is no point in updating it cause you also have the same issue with the newer version. But great that we now know the source of the issue!! Definitely needs to be flagged to the devs
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
Thanks for the confirmation!!
aygul12345 said:
Thanks for your confirmation.
As we speak im writing right now an issue. to the author. Let you know when its done.
Click to expand...
Click to collapse
I saw your post on Github. Thanks for the effort! https://github.com/kdrag0n/safetynet-fix/issues/216
hympe said:
Thanks for the confirmation!!
Click to expand...
Click to collapse
hympe said:
I actually have. I've got the v2.2.0. and I see there is no point in updating it cause you also have the same issue with the newer version. But great that we now know the source of the issue!! Definitely needs to be flagged to the devs
Click to expand...
Click to collapse
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
The cause of this issue is being logged on to the author github:
Xiaomi Mi 11 Pro - Installing this module boots into the recovery continuously · Issue #216 · kdrag0n/safetynet-fix
Describe the bug A clear and concise description of what the bug is. After having Root enabled by TWRP OR Flashing Magisk_modified_boot.img, there is no problem with Root on this device. But after ...
github.com
@Oceanone
@hympe Don't need to update, if it happens below then it also is happening on the latest version.
But @hympe can you confirm when you disable the Safetynet fix module, the phone reacts normally and boots normally?