Database Users

Magisk v11.6/Systemless Root works for our Moto X

Tested on a clean install of CypherOS. It installs and passes SafetyNet without doing anything complicated. Assuming it should work on any rom without root built in like Lineage OS.
Grab it here and thank @topjohnwu. Remember to enable Magisk Hide in settings or it will not pass SafetyNET.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

I tried this on an existing install but no luck.
On the new install did you have to flash the remove root zip from Lineage, or just ROM GAPPS and Magisk zips?
Thanks.

rsocon said:
I tried this on an existing install but no luck.
On the new install did you have to flash the remove root zip from Lineage, or just ROM GAPPS and Magisk zips?
Thanks.
Click to expand...
Click to collapse
On a clean install I just flashed rom, gapps, and magisk in that order.
BTW over night Magisk lost root, a reboot and root was back though. Might be bug, might be a one time thing, I don't know.

After trying everything listed still no luck getting this to work.
Guess no Android Pay for me

I tried to install on stock ROM, it seem it dosn't work, i'll try with a custom ROM

i'm running this just fine with just the core AND the latest version of magisk. safetynet check passes too on cypherOS.

Magisk on Stock (rooted) Nougat?

Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?

Flapjack said:
Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?
Click to expand...
Click to collapse
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk

Choose an username... said:
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk
Click to expand...
Click to collapse
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.

So install just boot.img from twrp and flash magisk.

Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
Either do what WesTD says or find a SuperSU uninstaller zip (i think there's one around), or wipe system and reflash the ROM

Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5

marcdw said:
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
Click to expand...
Click to collapse
Good stuff. Thank you!

I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.

AnonVendetta said:
I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.
Click to expand...
Click to collapse
Could you say which problems you had with Magisk?
If you had f2fs then of course. But usually Magisk works as it should and has the module system which is very useful too.

{SOLVED} Lost root after update and succesfull magisk flash

Hey guys,
Just flashed the latest Oxygen update the way i always do but this time i lost root.
Running stock rom with root (Magisk) and TWRP.
Flashed update
Cleaned dalvik/cache
Flashed Magisk.zip
Cleaned dalvik/cache again
Reboot
Twrp is still there, bootloader unlocked, magisk manager works to...... But no root, magisk manager says "magisk is not installed"
Never had this issue before....

g-member said:
Hey guys,
Just flashed the latest Oxygen update the way i always do but this time i lost root.
Running stock rom with root (Magisk) and TWRP.
Flashed update
Cleaned dalvik/cache
Flashed Magisk.zip
Cleaned dalvik/cache again
Reboot
Twrp is still there, bootloader unlocked, magisk manager works to...... But no root, magisk manager says "magisk is not installed"
Never had this issue before....
Click to expand...
Click to collapse
Which oxygenOS? Which magisk version? Did you tried to flash magisk uninstaller before flashing the oxygenOS update and go ahead with the further steps?

Latest Oxygen, and no dit not uninstall magisk before flashing the update, never did and worked fine....
Using Magisk 17.00 latest

g-member said:
Latest Oxygen, and no dit not uninstall magisk before flashing the update, never did and worked fine....
Using Magisk 17.00 latest
Click to expand...
Click to collapse
Which oxygenOS(stable or beta)? Try to install magisk again, use v17. 3 if not working, flash uninstaller as mentioned before

That did the trick, thnx

g-member said:
That did the trick, thnx
Click to expand...
Click to collapse
Which one? To help others you can mark the thread as [SOLVED] in the headline:good:

First flashed the uninstaller and reflashed 17.3 Magisk.
How do i mark this post?

g-member said:
First flashed the uninstaller and reflashed 17.3 Magisk.
How do i mark this post?
Click to expand...
Click to collapse
Edit the title and add [SOLVED] at the beginning.

Rooting help for OnePlus 6T 9.0.15

A little background: I was rooted before updating my OnePlus 6T from system settings, then after updating (through system settings) I no longer had root and TWRP recovery so what I did was flashed TWRP following this method now I do have TWRP recovery but I am not sure which method to follow for the root process, and I have few concerns as below:
Should I flash Magisk now if so which version and which method will work for 9.0.15?
Before flashing Magisk should I flash Magisk uninstaller as well?
Do I have to flash TWRP again after flashing Magisk?
I might be asking dumb questions but I don't want to mess it up.

Greetings.
Just straight up flash the latest Magisk version, worked for me. Flash it through TWRP.
Why would you flash magisk uninstaller? I mean, I suppose it's optional?
No, you don't have to flash TWRP again.
Cheers.

Flash Magisk.
Next time, without rebooting, use Magisk mod 'TWRP A/B retention script' (search for it in Magisk modules list) just after flashing OTA via local method, and then without rebooting yet, in Magisk manager install again Magisk selecting 'other slot after OTA' option. Then only you reboot, all babies intact and in good health

Update to oos 11 and keep root

Hey lads, i wanted to update to oos 11 and keep magisk root, I saw a video tutorial on how to do that but on a previous oos update.
By installing the update without rebooting and installing magisk on inactive slot after OTA.
This sadly didn't work for me so now I am stuck without root access on oos 11.
Do I need to reflash magisk boot.img again or could there be another way to enable it?
Flashing boot.img will delete all my data and apps and I would really hate installing all that again one by one manually...
Any tips on what I can do?
Thanks.

XxSUPRAxX said:
Hey lads, i wanted to update to oos 11 and keep magisk root, I saw a video tutorial on how to do that but on a previous oos update.
By installing the update without rebooting and installing magisk on inactive slot after OTA.
This sadly didn't work for me so now I am stuck without root access on oos 11.
Do I need to reflash magisk boot.img again or could there be another way to enable it?
Flashing boot.img will delete all my data and apps and I would really hate installing all that again one by one manually...
Any tips on what I can do?
Thanks.
Click to expand...
Click to collapse
1. It didn't work, because you took the wrong magisk version. Latest canary or beta works great with A11. I did it myself without issues.
2. There is only one way to get root. Patch the boot.img and flash it.
3. And no, flashing boot.img won't delete anything!

Kollachi said:
1. It didn't work, because you took the wrong magisk version. Latest canary or beta works great with A11. I did it myself without issues.
2. There is only one way to get root. Patch the boot.img and flash it.
3. And no, flashing boot.img won't delete anything!
Click to expand...
Click to collapse
Ohhh.. Thanks! I just realized that it wasnt boot.img that would delete my files as you said, and have now updated to oos 11 with magisk and safeteynet passed. Thanks.

I have a guide for this in the guides section..step by step.

For others with the same question and find this thread instead of the guide: Switch to beta update channel in magisk -> download and install OTA without rebooting -> magisk flash to inactive slot -> reboot & enjoy

Like I said, I have a guide for this.
https://forum.xda-developers.com/oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033
Read before you commit.. It's easy..