Database Develop

Magisk Boot Loop Nexus 6P

Just upgraded magisk to 11 this morning from inside the app and it has been stuck rebooting the past ten minutes. Can anyone help?

can still get into Twrp though if that helps figure out solutions.

I have similar problem, on a OnePlus 3 with a CM13 based Rom.
After the update from 10.2 to 11 the start of Android never finished.
Temporary solution (until I have more time to produce a real bug report or someone else finds the problem) uninstalled Magisk via Uninstaller zip in TWRP and reinstalled Magisk 10.2 there.

Same problem for me on Pure Nexus when installing v11. Stuck on boot screen.

Had to flash Magisk Uninstaller, and re-flash Magisk 11 through TWRP. Seems to work, until I installed ViperFX (through Magisk) and it asked me to reboot - now I'm back in a boot loop.
Going to roll back to Magisk 10.2 until something gets fixed.

Flash the uninstaller script in TWRP and try again. And even if it seems to be bootlooping, let it sit. Mine stayed on boot animation for a good 5-10 minutes the first boot up on v11. If it still seems to be looping, try flashing a clean boot image and start over.
Nexus 6, Pure Nexus 01/21.

Okay, so I finally got it to boot doing the following:
1) Factory Reset
3) Format System
2) Reflash Rom, GApps
3) Boot into Rom
4) Reboot, flash Magisk
5) Boot back into Rom
I think the issue is if you are coming from 10.2 (or earlier) you need to remove SU before flashing magisk. Magisk has SU built in (though should work with SuperSU or phh's for now) but I think there is some issue when upgrading. Maybe try flashing your preferred SU package after you reboot into the rom after Magisk is installed.
---------- Post added at 03:20 PM ---------- Previous post was at 03:16 PM ----------
Didgeridoohan said:
Flash the uninstaller script in TWRP and try again. And even if it seems to be bootlooping, let it sit. Mine stayed on boot animation for a good 5-10 minutes the first boot up on v11. If it still seems to be looping, try flashing a clean boot image and start over.
Nexus 6, Pure Nexus 01/21.
Click to expand...
Click to collapse
Hehe, well, I only just found out about that before I nuked my phone.

OK for me the boot problem was fixed by restoring the boot partition from a backup without Magisk installed and the flashing version 11.
So the problem is mostly cased by something in the boot partition.
If you don't have a backup of the boot partition. Flashing the boot image of the ROM or the hole ROM should fix this.
At lest for me no need to reset everything.

Did a full unroot of supersu, told it to restore the backed up boot image, booted immediately into recovery, flashed magisk and magisksu stuck no problem. I like this all in one solution v11 brings.

It's viper4android now causing the bootloop... I flashed clean with magisk 11.1

lutanica said:
It's viper4android now causing the bootloop... I flashed clean with magisk 11.1
Click to expand...
Click to collapse
agreed. this seems to be unresolved right?

steveo17 said:
agreed. this seems to be unresolved right?
Click to expand...
Click to collapse
Still unresolved yes..

I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

steveo17 said:
agreed. this seems to be unresolved right?
Click to expand...
Click to collapse
denvit said:
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Proof:
Click to expand...
Click to collapse
And you've Viper4android installed and it's functioning?

I only heard about Magisk and its rooting abilities yesterday. So far I have always used SuperSU, but now I'd like to migrate. Now and again I'd like to use my banking app, and it's not allowed on rooted phones. I've tried rootcloak before, but for some reason I can't remember, didn't really work. So I would love it if this solution did.
However, when I install suhide required, it bootloops. So I reflash the whole system, bootloop remains. Only when I flash rm-suhide it does actually boot. But now I have to remove SuperSU and flash root again using the magisk.zip. When I do, it bootloops. Go figure.
I'm on the angler February update N4F26O.
Haven't tried the adb shell solution yet, but just about everything else.

denvit said:
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Click to expand...
Click to collapse
Verified working with an extra step: after you reboot, remove SuperSU if you have it (app drawer, drag to uninstall). This seems to default the SU method to the MagiskSU, which allows it to pass safety net as well. Before I uninstalled SuperSU, I was getting safetynet fail CTS mismatches.
Also, after doing the quoted method, it did take a little longer than usual booting, give it 5 min at least.
Lastly, Viper4Arise doesn't work (driver won't load), probably because of something related to the new magisk, or because it preferred SuperSU.
Thanks

2hdq said:
I only heard about Magisk and its rooting abilities yesterday. So far I have always used SuperSU, but now I'd like to migrate. Now and again I'd like to use my banking app, and it's not allowed on rooted phones. I've tried rootcloak before, but for some reason I can't remember, didn't really work. So I would love it if this solution did.
However, when I install suhide required, it bootloops. So I reflash the whole system, bootloop remains. Only when I flash rm-suhide it does actually boot. But now I have to remove SuperSU and flash root again using the magisk.zip. When I do, it bootloops. Go figure.
I'm on the angler February update N4F26O.
Haven't tried the adb shell solution yet, but just about everything else.
Click to expand...
Click to collapse
Firstly unroot the SuperSU, flash the latest Magisk zip file v11.1. You don't need the suhide as the latest version of Magisk already has the necessary files to root your device. Hope this helped you

At the risk of sounding dumb, I couldn't figure out how to decrypt my data partition. I don't know if what I did made any actual difference but I did a nandroid of my data, rebooted twrp, restored data, entered the adb command, then installed magisk. Reboot to system, all set!
Hope this helps someone out.
Sent from my Nexus 6P using Tapatalk

I'm getting a constant boot loop (stuck at boot animation) each time I try to install magisk on my Oneplus 3. with OOS 4.0, it worked fine on MM but no go since updating to nougat.
Edit:Fixed it! I hadn't ran the uninstaller first. Once I did this it worked fine. Doh!

Hi on my lg g5 (with fulmics custom rom Android 7.0) magisk 11.1 crashes settings app, any solutions? I could revert back to 10.2?

How to remove SuperSU after having installed Magisk?

So here's what I did:
I have my Galaxy S7 with Android 6, rooted with SuperSU.
Upgraded it to Android 7 using Smart Switch. Root is lost, of course.
Assumed SuperSU was gone, went ahead and rooted with Magisk.
After a bit of fiddling, because the guy can't write English, I had it working perfectly.
Restored a backup of all my apps. SuperSU got installed as well, since it was part of the backup. So I deleted it again (just the app).
Decided to do the SafetyNet test. Result: CTS profile mismatch. This is usally due to remnants of SuperSU. So I guess it wasn't removed fully.
Reinstalled the SuperSU app (just the app, I don't dare installing it via TWRP).
Open SuperSU, only to find out "SU binary is occupied". So I can't let SuperSU do its automated full unroot either.
My goal is to:
Get rid of SuperSU completely
Use Magisk instead
Pass the SafetyNet check
I have tried:
I ran the Magisk uninstaller to see if I can let SuperSU do its "full unroot" thing. But it results in a boot loop. So that's a no go.
I ran this SuperSU uninstaller script through TWRP, but it doesn't appear to have done anything. The results are unchanged either way.
So, what do I do now?

Try uninstalling the one you have (I assume it's the magisk v12), install magisk v13 beta, and see what you get. Also, about the safetynet, there are plenty of others reasons that may lead it to not pass, not only supersu.

thany2 said:
So here's what I did:
I have my Galaxy S7 with Android 6, rooted with SuperSU.
Upgraded it to Android 7 using Smart Switch. Root is lost, of course.
Assumed SuperSU was gone, went ahead and rooted with Magisk.
After a bit of fiddling, because the guy can't write English, I had it working perfectly.
Restored a backup of all my apps. SuperSU got installed as well, since it was part of the backup. So I deleted it again (just the app).
Decided to do the SafetyNet test. Result: CTS profile mismatch. This is usally due to remnants of SuperSU. So I guess it wasn't removed fully.
Reinstalled the SuperSU app (just the app, I don't dare installing it via TWRP).
Open SuperSU, only to find out "SU binary is occupied". So I can't let SuperSU do its automated full unroot either.
My goal is to:
Get rid of SuperSU completely
Use Magisk instead
Pass the SafetyNet check
I have tried:
I ran the Magisk uninstaller to see if I can let SuperSU do its "full unroot" thing. But it results in a boot loop. So that's a no go.
I ran this SuperSU uninstaller script through TWRP, but it doesn't appear to have done anything. The results are unchanged either way.
So, what do I do now?
Click to expand...
Click to collapse
I used the SuperSu android app. It has a full unroot (or was it uninstall?) option.
But I am on the op3. So not a 100% sure if that'll apply for the s7.
Sent from my ONEPLUS A3003 using Tapatalk

Dirty flash should remove all su or magisk, then you can install magisk again

abacate123 said:
Try uninstalling the one you have (I assume it's the magisk v12), install magisk v13 beta, and see what you get. Also, about the safetynet, there are plenty of others reasons that may lead it to not pass, not only supersu.
Click to expand...
Click to collapse
Uninstalling Magisk results in a boot loop, like I said. So it's a no-go.
What other reasons could it have when SafetyNet doesn't pass with that error message?
tropicanapure said:
I used the SuperSu android app. It has a full unroot (or was it uninstall?) option.
But I am on the op3. So not a 100% sure if that'll apply for the s7.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
SuperSU has that option greyed out because of a locked binary, like I said, so that won't solve anything.
adekboreanaz said:
Dirty flash should remove all su or magisk, then you can install magisk again
Click to expand...
Click to collapse
Sorry, I don't understand what "dirty flash" is supposed to mean. It sounds like a risk.

thany2 said:
Sorry, I don't understand what "dirty flash" is supposed to mean. It sounds like a risk.
Click to expand...
Click to collapse
No it is not, dirty flash is flashing your rom again without deleting /system /data partition, that can replace your boot.img with the stock one, so the supersu will be disappeared

reflash boot.img from the rom you used via twrp on img mode (click zip or img to switch between modes) or reflash your desired custom kernel.

XiAOMI MI MAX 2 Official ROM Root twrp

So Guys ROM twrp Root etc Now available for MI max 2. [oxygen 2]
You can Download official ROM from http://en.miui.com/a-234.html
and Flash it with MI flash.
or if you have dead Device follow deep Flashing Guide Here.https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055
twrp ported From mido Download Here
Flash with fastboot
Code:
fastboot flash recovery recovery.img
Flash magisk From here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
in trouble watch video-

Thank you! TWRP worked as intended, installed root manually. Donated as well.

TiMbl4 said:
Thank you! TWRP worked as intended, installed root manually. Donated as well.
Click to expand...
Click to collapse
ok thanks for Donation..

Lineage OS available https://forum.xda-developers.com/mi-max-2/development/linageos-14-1-mi-max-2-t3634864

Great toolkit but I have a couple questions. In the instructions on your site and youtube video it has a step to flash noverity. Is this really needed or is it just a precaution? Also, could I just flash the recovery via fastboot and then just pull noverity and magisk from their source and flash them? I always like to flash things myself the normal way so I understand what's going on.

noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.

XN Logos said:
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
Click to expand...
Click to collapse
Thanks for the quick response. I have one more question. Can I substitute SuperSU in place of magisk? After using the toolkit, I tried to update magisk to the latest version (13.2) using magisk manager but instead it gave an error. It didn't brick my phone or anything but when I rebooted and went into magisk manager it showed the phone was still properly rooted but reported that magisk wasn't installed. Not sure if it's a compatibility issue or not. I also tried flashing the latest version of magisk using twrp and got the same error in magisk manager upon reboot.
At any rate, do you see any problem with using SuperSU instead?

Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.

XN Logos said:
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
Click to expand...
Click to collapse
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again

Did you have to unlock the bootloader for installing twrp?
ikecomp said:
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Click to expand...
Click to collapse

unlock with developer rom

XN Logos said:
unlock with developer rom
Click to expand...
Click to collapse
Since 5 days i have been trying to unlock bootloader. Every time I get "Device not bound to account". I have tried everything. Can you help me?? I am already on developer rom..

yes that means You have not applied for unlock, First of all apply for unlock then when you receive Confirmation msg wait 72 hrs, then login mi unlock app with same account and then try to unlock

Magisk not detect root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow all instruction,i flash no verity and flash xnmagisk.zipafter reboot magisk appear like that? Have format but still not detect root, can root manually flash superusu but i want magisk to for hide root. So what next stepp for solve this problem? Let me know. Thanks

Hi guys, any idea why when I flash magisk 14.0 over a fresh 7.9.7 global developer rom I get CTS profile mismatch? It still shows safetynet as passing but android pay refuses to work. Also, is it safe to install OTA updates with magisk flashed?

How to root after flashing the official miui9 ? (my device is rooted miui 8.5)
please help (Device Mi Max 2 )

Bootloop after magisk update

This morning, waking up I recieved the notification that a new magisk manager is available. I installed it as usual, except this time my device suddenly was not rooted anymore.
Si I press the install magisk button that pops up, it flashes magisk, and BAM. Phone restarts, and boot loop.
The phone's a OP5, android 7.1.1, and I had to do a factory reset twice before it would boot. Even using the magisk uninstaller did yield no results.
How come the phone suddenly got unrooted? Can I safely root it again now? Why wouldn't the first factory reset get it out of boot loop?
How can I prevent data loss in the future? Help?
Update 1 - Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.
So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)
Update 2 - TimMayle managed to run the uninstaller and re-flashing magisk v17 on TWRP, try this if you have the issue. (While the uninstaller wouldn't work for me, that might be a device specific issue.)
TimMayle said:
Hello,
I was on Magisk 16 and probably Manager 5.8.3.
Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.
Then I was in bootloop.
In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.
Bootloop Gone !
Tim
Click to expand...
Click to collapse
Update 3 - Thanks void74 for another potential procedure that might fix your issues.
void74 said:
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
I hope I have saved some lives.
Click to expand...
Click to collapse
Update 4 - Thank you Shampinger for giving ups a Linux-specific variation on the steps to follow.
Shampinger said:
Same issue here on Redmi Note 5 global (whyred). Thanks to this thread I could fix it.
Steps (on Linux):
1. boot into fastboot (vol down + power)
2. from folder with your twrp zip run:
Code:
sudo fastboot boot twrp-x.x.x-x-whyred.img
there might be an easier way to boot into recovery without having to use the zip on your computer that I don't know about
3. copy Magisk uninstaller and Magisk v17 to phone (if not already there)
4. flash uninstaller zip
5. go back and flash Magisk v17 zip
6. reboot
Click to expand...
Click to collapse
Update 5 - While a fixed version is being perfected, Mangraviti summed up what you should do:
Mangraviti said:
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
Click to expand...
Click to collapse
Update 6 - If you have Wi-Fi issues after update v17, you can attempt what TAJ_Rocks has found out:
TAJ_Rocks said:
Found fix for dead wifi
Delete this p2p supplicant.conf supplicant made wifi a c#nt:laugh:
Reboot after deleting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse

+1.
Exactly the same issue. The phone lost root and is now stuck in bootloop. How to recover? Any hopes of saving the data?
Please throw some light....

Same issue here... bootloop after update. I wish I didn't update.
Oreo 8 on Huawei Nexus 6p.

Same here on HTC U11 with Lineage 15.1
Feels bad man.
How do I fix?

I fixed bootloop by uninstalling magisk with magisk uninstaller. After that I installed v16

Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?

Same here (bootloop) after update from 16 to 17. I used unnistaller but ended in fastboot after reboot :laugh:
Had to install rom and v17 to work.
Redmi Note 5 Pro MIUI 9.6.4.0 Global

Same thing on s7 with Android 7.0 , now I'm resetting the device.

Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.
So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)

Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?

ZioArturone said:
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
Click to expand...
Click to collapse
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.
See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.

Didgeridoohan said:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Click to expand...
Click to collapse
Hello,
I was on Magisk 16 and probably Manager 5.8.3. (Xperia Z3C on OmniRom).
Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.
Then I was in bootloop.
In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.
Bootloop Gone !
Tim

Didgeridoohan said:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Click to expand...
Click to collapse
Yes. That's exactly what I did. OK. So I now ran magisk uninstaller, booted fine. Then installed clean v17.0 and it works now - no bootloop. Many thanks!

I am having the same problem with magisk manager 5.8.3 + v16 zip. After upgrading to v5.9.0(138) all my previous setting all gone. Plus i can install v17 zip at all.
This is on HTC U11+ with android v8.0

Same for me had bootloop on android 7.1.2 i was on magisk 16.0 stable. I got notification before an hour. I upadted the apk and it showed magisk not installed. So i downloaded the zip and flashed 17.0 stable zip and had bootloop. So i just cleaned cache and dalvik now phone is started and root and magsik working. But now wifi is unable to switch on

Also got a bootloop on my Samsung Galaxy S4 jfltexx running Resurrection Remix v5.8.5 (Android 7.1.2). Fortunately I took a TWRP backup before this upgrade and was able to restore it.
But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip
Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.

ZioArturone said:
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
Click to expand...
Click to collapse
I'm in the same situation with a s6. After another device (s7) has a bootloop I don't think that i flash the v17 from the manager

gkmac said:
Also got a bootloop on my Samsung Galaxy S4 jfltexx. Fortunately I took a TWRP backup before this upgrade and was able to restore it.
But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip
Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
In "Downloads" you have "Latest uninstaller" go to recovery and flash the zip, that should uninstall magisk.

Dacraun said:
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.
See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.
Click to expand...
Click to collapse
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.
It didn't work, I am unrooted.
This update ****ed up all...

ZioArturone said:
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.
It didn't work, I am unrooted.
This update ****ed up all...
Click to expand...
Click to collapse
Check the first post, I quoted someone flashing the uninstaller and flashing v17 again and it worked. Maybe that'll work for you?
I do suggest doing a total backup in twrp first though. Just in case.

Problem to unroot with LineageOS 17.1

Hi guys,
I rooted and flashed my realme X2 Pro (Europe) to install LineageOS 17.1 and it's great.
But, some app detect my rooted was rooted and doesn't works properly (payment with NFC disabled, few apps aren't in PlayStore and can't install with apk.
I tried to unroot my phone, but Root checker app tell me my phone is not rooted properly.
I think, the root was corrumpt when I installed LineageOS 17.1.
I tryied to root again with Magisk and TWRP (after Lineage installed) but my phone loop on bootloader after that.
I tyried also to install magisk uninstaller but same problem at reboot.
I tryied to unroot manualy with ES File manager, but when I activate "Root" in settings, it's tell me that my phone is not rooted.
And, when I want to go in /system/bin, File manager can't displayed items. I'm unable to find this folder in TWRP.
Also, SuperSU app, say "Sorry ! Device did not rooted properly".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tryied to go back on RUI stock image with tutos, but twrp 3.4 (manuforio) failed after decrypting Ozip file.
Can I unroot my phone and keep LineageOS ? If yes, how can I unrooted my phone ?
Many thanks in advance.
Catskan

Catskan06 said:
Hi guys,
I rooted and flashed my realme X2 Pro (Europe) to install LineageOS 17.1 and it's great.
But, some app detect my rooted was rooted and doesn't works properly (payment with NFC disabled, few apps aren't in PlayStore and can't install with apk.
I tried to unroot my phone, but Root checker app tell me my phone is not rooted properly.
I think, the root was corrumpt when I installed LineageOS 17.1.
I tryied to root again with Magisk and TWRP (after Lineage installed) but my phone loop on bootloader after that.
I tyried also to install magisk uninstaller but same problem at reboot.
I tryied to unroot manualy with ES File manager, but when I activate "Root" in settings, it's tell me that my phone is not rooted.
And, when I want to go in /system/bin, File manager can't displayed items. I'm unable to find this folder in TWRP.
Also, SuperSU app, say "Sorry ! Device did not rooted properly".
I also tryied to go back on RUI stock image with tutos, but twrp 3.4 (manuforio) failed after decrypting Ozip file.
Can I unroot my phone and keep LineageOS ? If yes, how can I unrooted my phone ?
Many thanks in advance.
Catskan
Click to expand...
Click to collapse
Did you have any solution for (unrooted +LineageOS) or NFC payments enabled with rooted LineageOS

Catskan06 said:
Hi guys,
I rooted and flashed my realme X2 Pro (Europe) to install LineageOS 17.1 and it's great.
But, some app detect my rooted was rooted and doesn't works properly (payment with NFC disabled, few apps aren't in PlayStore and can't install with apk.
I tried to unroot my phone, but Root checker app tell me my phone is not rooted properly.
I think, the root was corrumpt when I installed LineageOS 17.1.
I tryied to root again with Magisk and TWRP (after Lineage installed) but my phone loop on bootloader after that.
I tyried also to install magisk uninstaller but same problem at reboot.
I tryied to unroot manualy with ES File manager, but when I activate "Root" in settings, it's tell me that my phone is not rooted.
And, when I want to go in /system/bin, File manager can't displayed items. I'm unable to find this folder in TWRP.
Also, SuperSU app, say "Sorry ! Device did not rooted properly".
I also tryied to go back on RUI stock image with tutos, but twrp 3.4 (manuforio) failed after decrypting Ozip file.
Can I unroot my phone and keep LineageOS ? If yes, how can I unrooted my phone ?
Many thanks in advance.
Catskan
Click to expand...
Click to collapse
Try reflashing lineageos 17.1 or if you want to go back to stock rom update your vendor and flash