Database Info

Xposed on Sprint S6

I installed Xposed v86 arm64 successfully using TWRP recovery, after restart, the phone got stuck on a boot loop. i had to go back to recovery and install the uninstall zip. After that process it booted normally and updated the apps. That does mean i cant install or use Xposed on my device or there is something wrong somewhere?

I goofed up: Tapped wrong option to update Magisk and now I don't have a recovery

Please bear with me.
I was about to upgrade from Magisk 19.4 to 20 and I tapped on "Install to inactive slot (after OTA)" instead of the recommended option "Direct install), then clicked yes without reading because I though I tapped the correct option... and after that, without rebooting, I tapped the Direct install option and rebooted. (Yup, I effed up that whole part.)
Then, when booting up the phone got stuck in fastboot.
I followed @Arden144's steps to install twrp and I was able to boot into twrp and flash magisk.
If I go to power options and tap on reboot to OS, it boots fine and I have Magisk 20. My modules are still there and everything seems fine. Wi-Fi, fingerprint sensor and SafetyNet are fine.
BUT! Now, for my actual problem:
Whenever I use advanced reboot to go to the recovery, go to recovery through Magisk Manager, press Volume Down + Power to boot into recovery or even select "Recovery" in TWRP's power menu, the phone just goes to fasboot and I can't enter the recovery unless I "fastboot flash" a recovery.
Thankfully if I select "Start", the phone starts fine. Previously it just looped back to the fastboot but seems that reflashing twrp at least fixed that.
But yeah, I can't enter TWRP without a computer to fastboot, which sucks.
What can I do? Flashing twrp doesn't seem to stick.
Thank you for any advice you can give me!

Deses said:
Please bear with me.
I was about to upgrade from Magisk 19.4 to 20 and I tapped on "Install to inactive slot (after OTA)" instead of the recommended option "Direct install), then clicked yes without reading because I though I tapped the correct option... and after that, without rebooting, I tapped the Direct install option and rebooted. (Yup, I effed up that whole part.)
Then, when booting up the phone got stuck in fastboot.
I followed @Arden144's steps to install twrp and I was able to boot into twrp and flash magisk.
If I go to power options and tap on reboot to OS, it boots fine and I have Magisk 20. My modules are still there and everything seems fine. Wi-Fi, fingerprint sensor and SafetyNet are fine.
BUT! Now, for my actual problem:
Whenever I use advanced reboot to go to the recovery, go to recovery through Magisk Manager, press Volume Down + Power to boot into recovery or even select "Recovery" in TWRP's power menu, the phone just goes to fasboot and I can't enter the recovery unless I "fastboot flash" a recovery.
Thankfully if I select "Start", the phone starts fine. Previously it just looped back to the fastboot but seems that reflashing twrp at least fixed that.
But yeah, I can't enter TWRP without a computer to fastboot, which sucks.
What can I do? Flashing twrp doesn't seem to stick.
Thank you for any advice you can give me!
Click to expand...
Click to collapse
There's a known issue with Magisk 20 that makes TWRP not stay installed. Downgrade to 19.4 or hold tight without TWRP

Arden144 said:
There's a known issue with Magisk 20 that makes TWRP not stay installed. Downgrade to 19.4 or hold tight without TWRP
Click to expand...
Click to collapse
Oooh. What an awful moment to have this problem, then.
Unfortunately, I reflashed Magisk, (Manager now shows 19.4) but TWRP doesn't stay installed... What worries me is that not even the stock recovery is available to use, just fastboot.

Deses said:
Oooh. What an awful moment to have this problem, then.
Unfortunately, I reflashed Magisk, (Manager now shows 19.4) but TWRP doesn't stay installed... What worries me is that not even the stock recovery is available to use, just fastboot.
Click to expand...
Click to collapse
You can try using the Magisk Canary Uninstaller to completely clean up the Magisk install, or dirty flash the stock ROM

Magisk 20.1 works for me with latest TWRP.

have you tried installing TWRP as a magisk module?

Try this..
To solve the prroblem
1. Reflash the latest rom.you have using system.update...
2. Install magisk to inactive slot
3. Reboot
4. Goto magisk and flash twrp installer v70..
5. Install magisk again as recommended..
Reboot...

when that happened to me i grabbed magisk uninstaller and fadtboot booted twrp flash magisk uninstaller then twrp zip reflashed magisk 20. whatever new version of magisk is

Deses said:
What can I do? Flashing twrp doesn't seem to stick.
Click to expand...
Click to collapse
Flash twrp to ramdisk. It should stick. I have it installed to ramdisk. Also updated from 19.3 to 20 with twrp still there.

Same happened to me. No recovery partition it seems. Lol going to try ecompton's suggestion later.

aNGERY said:
have you tried installing TWRP as a magisk module?
Click to expand...
Click to collapse
Makes no difference. Also, the TWRP issues are pretty random. I have no issues on ob3 with Magisk 20 and TWRP 70

TheKnux said:
Magisk 20.1 works for me with latest TWRP.
Click to expand...
Click to collapse
Me too.

OK, so only way I restored access to my recovery was to flash the OTA update and the stock recovery was there... after that I reflashed TWRP and I can access it just fine.

Please help me i have mistacke i unstall magisk now i went to restore root

Recovery Bootlooop Please Help *Urgent*

I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks

Goooober said:
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Click to expand...
Click to collapse
Use the msm tool to recover your device...

Try booting into the mauronofrio twrp recovery from fastboot. Then wipe the system partition and reinstall your rom.
Then boot mauronofrio twrp again from fastboot and install the zip, and reboot to recovery.
Install custom kernel, Magisk.

Uninstall edexposed

People reply here with no clue and advise to just restore stock. How is this a solution and how did not OP think of it themselves?
This is too little too late, but maybe it helps someone else:
Unofficial TWRP for Android 10 is glitchy. E.g. nanodroid backups are not restoring properly. Given current A/B mess this is not at all surprising.
Solution: wipe everything, reinstall *same* lineageOS version as before, flash same gapps as you had, and if you took the nanodroid backup after magisk, install it as well.
Don't boot yet!
Restore the backup *partially*, e.g. only the data partition.
This should work.
Or, emh, it did for me with some minor glitches. But even Google Authenticator didn't notice spoofing (otherwise RIP my accounts). So, i definitely recommend trying this workaround.

Bootloop after magisk module install

Hello everyone,
I recently installed Magisk and TWRP and at first everything was working completely fine, than I installed the f-droid privileged extension module the device started bootlooping.
I managed to fix the issue through TWRP (Fix bootloop option) and completely uninstalled Magisk through the official uninstaller. Thing is every time I'm trying to reinstall Magisk the problem returns.
Please help.

Happened to me to....you need to uninstall that exact module from your system....
You can uninstall any modules even from TWRP...
go to file explorer on TWRP
Open data then adb an then modules and delete unnecessary folder otf module...

James Blode said:
Happened to me to....you need to uninstall that exact module from your system....
You can uninstall any modules even from TWRP...
go to file explorer on TWRP
Open data then adb an then modules and delete unnecessary folder otf module...
Click to expand...
Click to collapse
Thank you for replying but the adb folder is empty.

Anyone?

PsyCoil said:
Hello everyone,
I recently installed Magisk and TWRP and at first everything was working completely fine, than I installed the f-droid privileged extension module the device started bootlooping.
I managed to fix the issue through TWRP (Fix bootloop option) and completely uninstalled Magisk through the official uninstaller. Thing is every time I'm trying to reinstall Magisk the problem returns.
Please help.
Click to expand...
Click to collapse
This is strange normally when you flash magisk uninstaller every module will be uninstalled, it's used to do a clean flash of magisk, infact when you reinstall magisk no module will be there and you need to reinstall everything

Hitman478™ said:
This is strange normally when you flash magisk uninstaller every module will be uninstalled, it's used to do a clean flash of magisk, infact when you reinstall magisk no module will be there and you need to reinstall everything
Click to expand...
Click to collapse
Indeed. How should I proceed then? Could the "Fix bootloop option" in TWRP caused the issue?

PsyCoil said:
Indeed. How should I proceed then? Could the "Fix bootloop option" in TWRP caused the issue?
Click to expand...
Click to collapse
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way

I have just tried the first method and unfortunately it did not work. The device keeps booting into fastboot instead of system. I will try the second method tomorrow and report here. Just to make sure I have it right, dirty flash is flashing the ROM without wiping the data first?
Magisk version is latest stable v20.3
Hitman478™ said:
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way
Click to expand...
Click to collapse

Thanks! The second solution did the trick. I'm pretty sure TWRP "Fix bootloop option" somehow caused the issue.
Hitman478™ said:
Let me think
Try this:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) Reboot to TWRP and flash magisk, don't let TWRP doing anything else
4) reboot to system, it must be works
Alternative is:
1) flash latest magisk uninstaller
2) reboot to system and make sure it's starting and working (no bootloop and/or no other problems)
3) reboot to TWRP, dirty flash latest oos (10.3.1), then TWRP, reboot to TWRP
4) same as point 3
5) once you've reboot to TWRP at least one time after flashing oos, flash latest magisk
6) reboot to system
Only question is: which magisk version are you using?
EDIT: If "Fix bootloop option" is a flashable TWRP file, then follow directly the alternative way
Click to expand...
Click to collapse

PsyCoil said:
Thanks! The second solution did the trick. I'm pretty sure TWRP "Fix bootloop option" somehow caused the issue.
Click to expand...
Click to collapse
Great! :good:
Because once you flash "Fix bootloop option" it will stay in system partition and the only way to remove is to reflash system through oos zip

hahaha i think magisk rooting method fail from safetynet check and module install. After a bootloader from specific module (disablerliboemencrypto) i restore my stuff to try another module (Bluetooth ..) a bootloop again happen
sorry but,GOOGLE beats YOU @topjohnwu.

Phone stuck at boot after uninstalling Magisk from app

I installed Magisk via twrp(Temp version). and installed a bunch of modules.
Then I decided to complexly uninstall Magisk. I've done that from the Magisk Manager apk(The Complete Uninstall button)..
The phone rebooted and stuck into the phone logo with red danger logo. which means perhaps the boot img is missing ?
I should have uninstalled the modules first, which might have caused this issue..
Now, I Flashed Magisk again via Temp twrp, but now few apps keeps crashing, even after uninstalling and installing them.
i don't have the stock bot image, otherwise i guess i can do fastboot boot boot.img to escape the boot issue after uninstalling Magisk from the app
Note : i tried flashing the uninstall zip file from twrp but that didn't work, Magisk framework still exists !
What should i do now ?
My HTC is the duel sim version (Asia) and i'm using Magisk 22 latest version

Have you tried cleaning dalvik cache?

XDHx86 said:
Have you tried cleaning dalvik cache?
Click to expand...
Click to collapse
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu

Coldz0 said:
I did, No luck. The reason I'm trying to unRoot my device is because a mobile banking app is detecting Magisk. the app keeps crashing after i add it to the Magisk hide menu
Click to expand...
Click to collapse
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root

XDHx86 said:
If it is just the banking app then you can get "MagiskHide" and "Safety Net Fix" modules from magisk.
If your phone stuck in bootloop or other apps are still crashing then you have to wipe dalvik cache again.
If you still need to unroot for whatever reason then try this:
Try updating magisk first then clicking uninstall from magisk manager
Try manually flashing uninstaller.zip from TWRP
Try flashing the uninstaller as a module as stated in this post
Finally if it's still no use, then you can factory reset the device and it will remove the root
Click to expand...
Click to collapse
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !

Coldz0 said:
I'm on the last version of Magisk. I tried to uninstall it from the app but it stuck at the boot logo with danger logo.
I also tired to flash multiple zip files but still Magisk exists after reboot.
That leaves me with last option. Factory reset. s it safe to do it even with magisk installed ? because the boot img is patched and when i try yo restore the original boot img, it just don't exist in Magisk !
Click to expand...
Click to collapse
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.

XDHx86 said:
No if it is a patched boot image then you'll have to flash the stock one.
Factory resetting a patched image puts the device in a bootloop.
Click to expand...
Click to collapse
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)

Coldz0 said:
Yes. This is what i was afraid of. I don't have the stock boot img. if you can help me with that, it will be great, my phone firmware (htc/imedugl_00401/htc_imgedugl 9/PQ2A. 190205.003/1088647.3)
Click to expand...
Click to collapse
You can find your device's ROM here (Literally first google results..):
HTC website
HTC dev center
GetDriodTips (Only for U12+)
**Disclaimer:** I don't own any of those ROMs and I don't hold responsibility whatsoever should you brick your phone or anything goes awry.

had exactly the same issue and exactly due to the same reason (I hate those pseudo-secure banking apps).
I couldn't wipe dalvik as TWRP is still not available for my P5.
But it was fixable really easy by reflashing the patched boot.img:
run command "fastboot flash boot magisk_patched.img"

btw I'm still looking for a solution for that stupid banking app.
I tried the above mentioned "magisk hide" and "safety net fix" and tried hiding the app itself but all that does not help.

Can we delete magisk and still use the phone rooted ? Or will it unroot my phone if magisk is removed. I’m planning to sell my s10 and the buyer does not want the application.

Good information from GetDriodTips (Only for U12+). Thank you.