yashsingh1/xdaforums huggingface dataset:
[Magisk] ShankkOG:
I had the same issue and I figured it out mate.

I believe it's because when you uninstall Magisk, it replaces your backed up boot.img. But if you're like me and installed v1, v2, v3, etc.. the latest backup it makes is actually a boot.img already modified by the previous Magisk installation. Obviously, when you install Magisk v5, you need to uninstall the one before it with the uninstaller, which restores a 'dirty' boot.img meaning root doesn't work.

Below are some instructions. I'd recommend reading them all beforehand and again while doing the procedure.

1. Get the boot.img of your ROM. That's as simple as getting the .zip for it, extracting it, and taking the boot.img file. I guess maybe the oldest Magisk boot.img backup would work too.

2. Make sure you also have the files for Magisk v5, the uninstaller, phh's Magisk Superuser 17, etc.. And uninstall Magisk Manager but still have the APK for it (needed in Step 11).

3. Boot into recovery.

4. (Possibly unnecessary) Mount all the partitions from your recovery, like Data and System and stuff.

5. Install the Magisk uninstaller.

6. If you installed any other mods, like Xposed, run their uninstallers.

7. (Possibly unnecessary) If your recovery has a file manager (I'm using TWRP and it does) then open it and browse to the places mentioned in the OP to delete Magisk and root files. I believe it's stuff like /supersu, /data/magisk, /cache/magisk, /data/busybox, /system/magisk.img, /system/bin/su, /system/xbin/su, etc.. You probably won't find any but a few because the uninstaller will probably do this for you if it works.

8. Flash that boot.img we got from Step 1. If you're using TWRP, make sure to press "Install Image" which is towards the bottom. You'll probably be asked what partition the image should be installed to: "Boot."

9. Now flash the rest of the files starting with Magisk v5. Your recovery probably supports queues, meaning you can chain the zips up to be installed one after the other. Make sure you add the mods AFTER Magisk. Obviously, make sure you include the root zip lol.

10. Reboot your system.

11. Install the Magisk Manager APK and phh's Superuser from the Play Store.

12. Hopefully, root now works.

Hope this helps.
[Magisk] topjohnwu:
Sorry for the frequent updates, many unexpected things pop out after release lol

As promised, I fixed the issue with adding folders. Required some serious algorithm adjustments

APIs are not changed, all mods should work fine. One thing to note is that I updated the template so people won't end up with broken permissions as I added a default permission for you :)

Lastly, the Magisk Manager is now 60% done (or maybe more as the rest is mostly UI stuff), the wip version can now manage mods.

Stay tuned for the new version, it will be awesome!

Changelog

v6

- Fixed the algorithm for adding new files and dummy system

- Updated the module template with a default permission, since people tend to forget them :)
[Magisk] xd4d3v:
Hi.

I was using one of your earlier systemless versions with no problems, I believe the ones that used su.d

I tried a liveboot, but I can't figure out what goes wrong, before the screen moves, what else Can i do to get a log?

PS: Will continue in the in the xposed thread or via PM.. just let me know. TY
[Magisk] Artim_96:
Well, in theory you only have to used the new modified version liked in the second post I think... But at least for me it doesn't work in v4 and v5, only writes in the log
[Magisk] xd4d3v:
yeah, thats what I used..
[Magisk] Wakamatsu:
I don't know about everyone else but I think that's a good thing.
[Magisk] k_l_o:
-deleted-

Wrong Thread
[Magisk] Small_Ku:
It seems like that the supersu with magisk is not compatible with flashfire
[Magisk] k_l_o:
You'll need to "Selinux Toggle" to OFF to make Selinux Status PERMISSIVE in Magisk Manager.
[Magisk] mobileman88:
Lots of steps for an upgrade. But it works! Thanks.
[Magisk] dimm0k:
HOORAY! many thanks for this as v6 allows me to install apps as system apps, as well as modify /system files without actually changing the originals... this was more than icing on the cake as the main draw for me was systemless root and Xposed with the added benefit of on-demand Android Pay!
[Magisk] Artim_96:
MagiskSU keeps getting lost within few minutes on v11.1 with manger 4.1 but I can't even provide logs since the logs tab just keeps showing a spinning wheel.

Install tab in the hamburger menu also just disappears.

A reboot fixes it for a few seconds
[Magisk] bmg1001:
I had this exact same bug. Try using the uninstaller, install 10.2 and Magisk Manager 3, update through the app (redownload the zip and everything), then update Magisk Manager, then enable ONLY MagiskHide. So far, this has been working for me. Not sure if enabling BusyBox would break it, so I have it off. I'm still worried that I'll randomly open the app and root will be lost and SN will not work, and like you mentioned, it's hard to get a log when it won't even load.

I'd love for someone else to chime in too.
[Magisk] Artim_96:
At the moment, uninstalling and completely reinstalling it though TWRP had fixed it (which hadn't worked in v11.0), let's see for how long
[Magisk] bmg1001:
I did this many times myself and it seemed fix for awhile but I got the same issue after some time. It's such a frustrating issue, glad I'm not alone.
[Magisk] Artim_96:
Yes. Just checked back, it's back to no root. Let's try it without BusyBox
[Magisk] preusstang:
+1 on that. I've left my other devices on marshmallow in order to use rootcloak. I've tried turning off the busybox built-in to magisk (that's one of the things rootcloak hides I think,) to no avail. The Playsation Vue app is terrible anyway. Its frustrating that they make it so difficult to peruse their clunky, laggy interface
[Magisk] nimjk:
I had a problem with v11.1 I'm using lg g3 f400s with Fulmics v6.9 and gabriel kernel. This bug doesn't exist with v11 so I downgrade it. After few seconds I booted my phone with v11.1, my phone was black-out and it doesn't wake up... so i can't get my log...
[Magisk] GryphonBR:
Yep, you guessed right, Goodix with one of the peculiar front cameras. Where did you get Rootswitch from, if you don't mind me asking? And thanks for the tip about Stable/Developer, I would never have guessed that!

As for my Lineage installation, I'm not in the official channel because I'm still holding out on Nougat for now; I'm using Gismo0's build (Marshmallow-based), and maybe something changed between Lineage 13 and 14 that allowed for su management to happen outside the system? I might give that a try just for curiosity, but given what you mentioned about SafetyNet working on Global Stable I'll probably stick with that for now.
[Magisk] teddy0209:
Try completely removing magisk, restore boot.img and reflash magisk in twrp...
[Magisk] Captain_Throwback:
I just installed this app, and it works fine on my device after being added to the Magisk Hide list. So there's no special detection going on. Did you actually add the app to the Magisk Hide list?
[Magisk] yochananmarqos:
Can you boot into recovery? If so, run the Magisk uninstaller, reflash your kernel and reinstall Magisk 11.1. You may need to bump your boot.img again, but I'm not sure as I had the G3 D850.
[Magisk] nimjk:
i already did this but... it doesn't work... maybe i do it one more time.
[Magisk] bmg1001:
I already tried this, as well as dirty flashing my ROM again and more. Only thing I haven't tried is a 100% clean flash.
[Magisk] DarkLanternX:
U have to enable superuser from the magisk manager 4.0 settings, disable it from the dev opt.
[Magisk] DarkLanternX:
I had this same issue, but i realized it wasnt due to magisk. It was because of the play services . I rolled back to android mm flashed new gapps, fixed my issue. Are u using Android n?
[Magisk] yochananmarqos:
Well, then it's either kernel or ROM related. Change one of the two and try again, perhaps.
[Magisk] ryaniskira:
Is Magisk 11.1 bootloop city for anyone else? Install V11.1 from the app? Bootloop! Wipe data, set the entire phone back up? Bootloop! Wipe data, then instantly reboot the phone onces it boots back up? Bootloop!
[Magisk] bmg1001:
Yep, Android N. Lineage OS to be exact. So far, after doing a few tests, disabling Magisk's BusyBox makes Magisk work normally, but enabling BusyBox causes the "Not rooted" random error. I'll do a few more tests but I've been using Magisk normally since disabling BusyBox.
[Magisk] DarkLanternX:
Lineage os, exactly, now i think its some bugs with the ROM. Not sure though. Cuz i never had this problem with any other roms. Is the safetynet tab working now or is it still stuck in "loading"
[Magisk] bmg1001:
Yeah, everything works fine with BusyBox disabled. I just rebooted many times and everything works fine. Enabling BusyBox seemed to cause the error again.

SafetyNet works perfectly when the bug isn't present, though it never got stuck loading. It would just say "CTS Mismatch." Paid for both a drink from a vending machine and an Uber today using Android Pay, and this is a heavily modded system I'm running. I've got modified camera libs, Viper4Arise installed in system, and some build.prop stuff and Android Pay worked.
[Magisk] namthienvo:
yeah none of my modules work anymore
[Magisk] yochananmarqos:
Not a single report of such a thing. What device, ROM and kernel?
[Magisk] Didgeridoohan:
Ha ha! You keep throwing me these mentions just when I've gone to bed. :D

Looks like you're getting some good help already. But if you want to capture some more logs here's a handy tutorial:

https://xdaforums.com/showthread.php?t=1726238

With that you can catch part of the boot up as well, but unfortunately not the important parts for Magisk.

You can also use a logcat app. I like this one:

https://play.google.com/store/apps/details?id=com.pluscubed.matlog

Ultimately, though, I think your problem, and several of the other people having issues, is down to compatibility issues with the boot image. If, in the end, you can't get it working it might be a good idea to save some logs and upload those with a copy of your boot image as an issue on GitHub.
[Magisk] jagadeesh16:
I have a similar issue, I'm on nexus 5 aosp 7.1.1 by santoshm and i am stuck at Google logo until i reboot into recovery and do a dirty flash
[Magisk] Didgeridoohan:
If you don't have root you can't access the logs through the Manager. You'll have to pull the magisk.log from /cache in TWRP. Sounds like a good idea to capture a logcat of the event as well.
[Magisk] Artim_96:
It seems the problem is busybox. Disabling it and reboot seems to fix it, at least I haven't lost root over night
[Magisk] logo20heli:
Another successful update to Magisk 11.1

Hi. I just wanted to report a successful upgrade from Magisk 10.2 and Magisk Manager 3 up to Magisk 11.1 and Magisk Manager 4.1. This is on a Nexus 6P running Nougat 7.1.1. The February Security Patch OTA was just released and I wanted to install that at the same time as upgrading Magisk. To install OTAs I previously had to flash the Magisk uninstaller in order to restore the unmodified boot.img so that the OTA would install successfully. So I did the same thing this time. I flashed the Magisk uninstaller, rebooted, applied the February Security OTA, then flashed Magisk 11.1 in TWRP, installed Magisk Manager 4.1, uninstalled phh super user app. Then I enabled systemless host, busybox, and hide. Passes SafetyNet just as it did before on 10.2.

Another happy customer here!

Thanks topjonwu! Awesome job! :good:
[Magisk] ryaniskira:
Nexus 6P with PureNexus ElementalX. I think I nailed down what it is, It is Viper4Android. Also, you might want to check the forum again bud,

there is an entire thread with users confirming this issue left and right:

https://xdaforums.com/apps/magisk/magisk-boot-loop-nexus-6p-t3551809

---------- Post added at 01:31 AM ---------- Previous post was at 01:24 AM ----------

I think I tracked down what the issue is, you have to uninstall all Viper4android because it is doing something odd and causing bootloops.
[Magisk] Didgeridoohan:
Still... Sounds like a bug that needs fixing, so a logcat is probably good for troubleshooting. Maybe you could investigate more and open an issue on GitHub.
[Magisk] Artim_96:
If I find some time for that, I might. But since I'm not the only one having that problem maybe someone else can get some logs too
[Magisk] Didgeridoohan:
Could also be that the developer hasn't experienced the problem you're describing... I'm using older modules with no problem.

---------- Post added at 07:37 ---------- Previous post was at 07:36 ----------

Yeah, I'd love to. But, I'm not experiencing the problem...
[Magisk] GryphonBR:
If only it were that easy... I did that, several times, including removal of su on recovery. Never got it to work at all. Only thing Magisk Manager would give me is the "rooted but no permissions" message.

[MENTION=4313166]Filip013[/MENTION] just tried your suggestion, MIUI 8 Stable. CTS mismatch from the get go, just plain installed ROM from recovery (I use ZCX TWRP, which allows for OTA updates) but still SafetyNet would not pass, despite PoGo working, weirdly. After installing Magisk, though, PoGo wouldn't work and I still have CTS mismatch - care to share what and how you managed to get SafetyNet to work on yours, mate?

Sorry about that, mate, hahahahahaha... I'm about to hit the sack myself, so I'll give those suggestions of yours a go tomorrow. If I can be of help to improve Magisk's compatibility (and, who knows, get it to work properly for myself in the process? =D), that would be pretty good, I'd say.
[Magisk] Jsilver73:
Just to report that this morning I woke up to no root, rebooted and it was fine again.
[Magisk] Jaizu:
Root missing after some time it's a big bug I guess, I will try my best when I'm home to get logcat and help tracking the issue, thanks for the update so far
[Magisk] GryphonBR:
Did you manage to get MagiskSU to work on your phone with LineageOS? If so, mind sharing any steps you've taken? I've been trying for a couple of days now, and can't get it to work at all...
[Magisk] Didgeridoohan:
Magisk log won't be very useful in this case. Try catching a logcat from the instance you loose root.
[Magisk] 101_North:
Same issue here with disappearing root. Disabling busybox appears to stop this happening for now at least. LG G3 D855, LineageOS 6th Feb. Will try and grab some logs.
[Magisk] Schrotty35:
I have a problem with Titanium Backup. Whene i delete a System app and reboot the phone the app is back. Is there a fix?
[Magisk] Filip013:
OK, CTS mismatch from the get go is normal. That's because we have an unlocked bootloader. Am I right in guessing that at least your root problems are gone?

As for me, I can't get Magisk Hide to work with Magisk v11.1 and Magisk Manager v4.1. I have to stick to Magisk v11+4.0. To do that, you should disable Magisk Manager auto-update in Google Play.

For Magisk v11+4.0 to work you need to disable Magisk Hide, reboot and re-enable Magisk Hide. Then wait a few seconds (a minute?) for Magisk Hide to start properly, refresh the log to see what it's doing. You should also get a toast notification "Magisk Hide starting". When you see "Unmounted (/magisk)" in the log, it means it's ready. Test SafetyNet, you might want to use SafetyNet Playground from Google Play because it gives you more info.

As for Rootswitch you can find it here, but I use this version.

Finally, I don't think I ever tested Magisk on CM/LOS 13. I'll flash it in DBP just to check and report back here.
[Magisk] Didgeridoohan:
I'm gonna quote topjohnwu from currently known issues in the release thread:
[Magisk] Schrotty35:
Which app can mount system rw?
[Magisk] tag68:
You can enter the mount command in a terminal, or any file explorer supporting root should do like Total Commander, it has a button for this action.
[Magisk] bmg1001:
I'm not too experienced with logcat, so I just ran adb logcat and it started capturing from my phone right during the boot process, so there might be a lot of junk to swift through. If you want me to run it again a certain way, I can try. I haven't looked through it myself. Sorry if it isn't useful. Hopefully someone else can provide some logs too.

https://drive.google.com/file/d/0B4CYHidtQWQGU1kyc3B1anN4S1E/view?usp=sharing
[Magisk] seenahermes:
Hi,

When I update Magisk (v10 -> v11, and v11 -> v11.1) I cannot enable my wifi connection unless I reflash my kernel (Blu_Spark), is this expected behaviour ?

I'm on a Oneplus 3T with OOS 4.02
[Magisk] eto demerzel:
hello. I'm nexus 5 user with Pure Nexus custom rom 6.0.1. I try install magisk v11.1 with xposed framework (sdk23) (the phone is porperly rooted) but the safetynet test failed. what to do to past the test? thx. I have instaled Superuser.
[Magisk] gqukyo:
I just updated to the Feb patch also but installing 11.1 bootloops me...
[Magisk] Artim_96:
I don't think so. Maybe the are some logs in /cache from the installation
[Magisk] Filip013:
[MENTION=4062470]GryphonBR[/MENTION]

OK, so I flashed CM nightly 20161117 (I just happen to have it on my phone) and Magisk v11. I installed Magisk Manager and saw that it was properly rooted. Then I tried some root apps like f.lux and Titanium Backup, but they couldn't get root access. So I went to Magisk Manager Settings, scrolled down to Superuser Access and selected Apps and ADB. That fixed it.

But you were saying something about rooted, but no permissions? I didn't find that anywhere.
[Magisk] Didgeridoohan:
Disable Xposed.
[Magisk] 29988122:
EDIT: All of the titanium backup function broken, doesn't work at all(included restore)

Also using htc 10, I can confirm that magisk 11.1 make titanium backup's freeze / defroze function broken.

Magisk 10.2 is perfectly OK.

Please check logcat in the attachment.

Check the last few lines - I terminated adb logcat soon after I press defroze in titanium backup, but somehow logcat got really big.
[Magisk] mel2000:
How can we tell if our Android phone supports the Magisk rooting method?
[Magisk] Wesley_NL:
guys, i just installed android n for note 5 on my s6edge+ sm-g928f but i can't seems to pass SN someone can support me on this mather ?

and i have enabled magisk hide, since i run stock kernel kernel aduitor dont work for permissions

thx
[Magisk] wiQbold:
will there be a fix for adb?

cause I activate it over system.prop.

and now the device has a funny behavior..
[Magisk] Fild5x:
I had to start all over again and now am good
[Magisk] eto demerzel:
this my first thing what i do. no succes.
[Magisk] Didgeridoohan:
And you rebooted after disabling? Here are a few tips you could try as well:

https://xdaforums.com/showpost.php?p=70426733&postcount=7120
[Magisk] DarkLanternX:
I use lineage os too, I have been running magisk without any problem, though the safety net show " CTS mismatched" I can bypass safety net , not sure about android pay though

---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------

Complicated, idk flashing gapps might remove the bug, in gapps android n pico version got a bug, that crashes play services, if u running pico try a diff one
[Magisk] seenahermes:
I don't see anything in the log, and I've rebooted since then, is it silly to 'magiskify' v11.1 over v11.1 to generate new logs ?
[Magisk] naveenfre:
hello i get cts profile mismatch whether any module is available for active my headset moto g3 with RR 7.1.1
[Magisk] Didgeridoohan:
I'm sorry, but I give up. At least you're in the right thread now...
[Magisk] naveenfre:
give steps.plse
[Magisk] bmg1001:
Uh... Can you repeat your question a bit more precisely?
[Magisk] Didgeridoohan:
That's not gonna happen.

But, I can, for the third and last time let you know what I'd like you to do.

Give details. Lots of them. We get that your device triggers SafetyNet, but what else are you trying to achieve? What have you done up until now? What's your setup? Provide a Magisk log!

If you aren't able or unwilling to do so, please use the search function and search this thread. Because I promise you that whatever you're trying to do most likely already has been covered.

Good luck.
[Magisk] GryphonBR:
Well, so I got it to work with 4 + 11 as well - including CTS and all, yay! Disabling systemless BusyBox was what did it for me, apparently (or maybe it was the patience to wait for Magisk Hide to be reenabled, now that you mentioned it...). But when I tried updating to 11.1 I got a bootloop, and since then I can't escape the bootloop even with reflashing 11 anymore. Since I'm just experimenting here, I'm gonna reflash from scrap and observe this behavior you mentioned...

As for your other post on CM, I guess I also have a previous version somewhere on my SD, I'm gonna give that a try - it could point to some customisation in the Lineage I'm using, so one more step towards a possible solution, hopefully.

For me, what got Titanium Backup to work again on MIUI was changing SELinux to permissive (pseudo didn't seem to work as expected) and enabling USB installation (since I got a prompt from the system asking if I wanted to allow the app I was restoring - Snapchat, maybe? - to be installed from USB).

Our phone doesn't have NFC, so Android Pay could never be supported anyway... Which Lineage version are you using, 13 or 14.1?
[Magisk] Artim_96:
Probably yes.
[Magisk] Skcyte:
Does Magisk SU binary going to be overwritten when I updated my ROM by dirty flash it,?
[Magisk] kantjer:
Thanks, do you by any change know a solution to run this in Tasker?

Tried your sugestions above but I can't get it to work for a few sqlite commands I use.

sqlite3 /data/data/com.android.providers.contacts/databases/contacts2.db "delete from data_usage_stat";
[Magisk] 101_North:
I wasn't aware of a bug with pico version which is what I had flashed. I've now re-flashed Magisk 11.1 and OpenGapps Nano version. I've enabled busybox and rebooted. So far it's held root longer that it had previously. Root has also survived multiple reboots. Only been a few hours so probably too early to tell for sure. I'll keep an eye on it and report back.
[Magisk] DarkLanternX:
I flashed the nano version and everything was working alright.

I am pretty sure about the bug, cuz I reflashed the whole thing like three times...still nothing. And then I tried the nano and bingo
[Magisk] Filip013:
Is your problem actually a bootloop? I've experienced a strange problem when I first experimented with Magisk v11 in that my phone could boot, but I couldn't access UI. The screen was just black, but I know it booted because I could receive calls (well at least the phone rang). I'm not sure what caused that. Maybe it was my dumb idea to select System UI in Magisk Hide. Maybe it was systemless Xposed 86.2 that I used with suhide (although I flashed uninstaller). Whatever it was, Magisk just wouldn't let me use my phone, but as soon as flashed Magisk uninstaller I could use my phone again until I flashed Magisk again, and so on...

As for Titanium Backup and MIUI (sorry for slight offtopic), I didn't need to set SELinux to permissive, just allow USB installs.

And finally, Magisk and LOS. I think that the latest version of LOS 13 should work, no need for anything older (I just installed old CM because I already had it on SD and couldn't bother downloading anything newer). But you can give it a go. I'm particularly interested if LOS can pass SafetyNet. I think not. I think you'll be able to pass Basic Integrity in SafetyNet Helper, but not CTS profile match on anything other than Global Stable. Pokemon GO should work though (my guess).