Database Users

MAGISK+ Root+ safetynet - Pixel Guide

Hi All,
Been a root user for a few years, so i know the power of the typical root apps such as SU, Magisk and Xposed.
I was messing around last night an managed to find a way to get magisk fully installed on my phone and it passed the safety net ( see pictures). There are pictures to prove i have got magisk, Also there may be a easier method but this is what i used.
Ensure you are on RR as i have not tested.
Here is my method:
1. Download both attached files
2. Reboot to recovery
3.flash SU
4.Reboot
5. Once system loads open up SU app and go through the initial setup
6. reboot back into recovery
7.flash Pixel Magisk RC112
8. REBOOT
9. go into the SU app and into settings, scroll down to full uninstall and click thorough the popups and uninstall.
10. your phone will reboot and go into the magisk app and thank me.
Thanks for reading
EDIT: ALTERNATIVE METHOD BELOW:
How I got this on pn, elemental and flashing the right zip in the op was the key for me, the 2 zips in the first post of this thread
Install pn
Install TWRP
Reboot system
Reboot recovery, install elemental
Reboot to system
Reboot recovery install magisk sr3 zip one on op
Reboot system
Set up super su
Reboot recovery, flash rc112
Reboot system
Super su full unroot, check yes to both
Should reboot system
Open and set up magisk manager,
Go to settings and check hide magisk and systemlesd
Seems to work better on pn
This follows the first post of this thread works good for pn
If magisk manger doesn't show up in your launcher
Install https://github.com/topjohnwu/MagiskM...ger-v4.2.6.apk
CREDIT: mac796

Here's another way new rr already comes with magisk manager on it. Just wipe in TWRP, flash newest rr, reboot system once and then flash this experimental magisk zip in TWRP
https://www.androidfilehost.com/?fid=457095661767148610
Also when your done make sure to check hide magisk inside manager. And also if your a titanium backup user, you need to go to preferences, troubleshooting, check force busy box, and sq lite. That will make it work with new magisk root
Remember to check busy box in magisk manager app,
And give it a couple reboots, takes a bit to kick in.
Edit no longer have to do anything to get titanium backup to work, just check Magisk hide and systemless
Edit. Will work on big and small pixel
Edit updated new Magisk zip
Credit Goodwinc

Looks promising, will it works on pn rom or is it rr rom exclusive for now?
Sent from my Pixel using Tapatalk

ansontyl96 said:
Looks promising, will it works on pn rom or is it rr rom exclusive for now?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Not sure I was taking to somebody last night who was trying it, he hasn't got back to me

Currently I'm using suhide, but I'll prefer magisk if it works since it's open source!
Sent from my Pixel using Tapatalk

ansontyl96 said:
Currently I'm using suhide, but I'll prefer magisk if it works since it's open source!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
At the very end of my method I had to reboot once to get it all working right.

For the full unroot part do I need to restore the boot and recovery img?
If I choose no it reboot with SuperSU app disappear but still rooted with SuperSU as shown in the magisk app

restore the boot and recovery, it should delete the app and no super su left on your device.

Awesome. Gonna try this out tomorrow morning.
Are there any other useful modules for magisk? I havent looked into them since it was in v6 or v7...

only thing i use is hide su or magisk
everything else seems irrelevant for me, but if you find something let me know.

Here is my procedure: I was on newest RR with ElementalX and SuperSU.
I followed these steps: recovery -> dirty flash RR and flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot = No SuperSU but magisk root works and safety net check failed in Magisk -> go back to recovery -> flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot, No SuperSU, magisk root works, safetynet passes, hide magisk from other apps in magisk setting -> profit (android pay, venmo, snapchat, all are working)

rohitece06 said:
Here is my procedure: I was on newest RR with ElementalX and SuperSU.
I followed these steps: recovery -> dirty flash RR and flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot = No SuperSU but magisk root works and safety net check failed in Magisk -> go back to recovery -> flash Elemental X, MAGISK experimental zip, TWRP zip -> reboot, No SuperSU, magisk root works, safetynet passes, hide magisk from other apps in magisk setting -> profit (android pay, venmo, snapchat, all are working)
Click to expand...
Click to collapse
Good deal. I had to do a clean flash. You might end up with bugs

mac796 said:
Good deal. I had to do a clean flash. You might end up with bugs
Click to expand...
Click to collapse
thanks, i'll keep an eye out.

Anybody know whether this decrypts the Pixel? I don't have a Pixel yet so I can't test
http://www.theandroidsoul.com/disable-verity-force-encryption-pixel-xl-decrypt/

xdadevnube said:
Anybody know whether this decrypts the Pixel? I don't have a Pixel yet so I can't test
http://www.theandroidsoul.com/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
I have not seen anyone say they have decrypted the phone, Magisk is just now working on a few roms. I wouldnt bother, this phone has the processor for decryption.

So I take it that even with this it is one or the other with regard to having root (su) working or safety net passing for Magisk. You cant have true SU where you can alter system/app folders with Magisk root, you need true super su. So if I use Magisk root it limits me a little bit. But if I dont I cant use stuff like android pay, LOL

mac796 said:
Here's another way new rr already comes with magisk manager on it. Just wipe in TWRP, flash newest rr, reboot system once and then flash this experimental magisk zip in TWRP https://drive.google.com/open?id=0B1xZ4VKT4JKZTnhTdGxDcWlkMXM.
Also when your done make sure to check hide magisk inside manager. And also if your a titanium backup user, you need to go to preferences, troubleshooting, check force busy box, and sq lite. That will make it work with new magisk root
Edit. Will work on big and small pixel
Click to expand...
Click to collapse
Thank you, worked like a charm on my regular pixel with RR.

jawonder said:
Thank you, worked like a charm on my regular pixel with RR.
Click to expand...
Click to collapse
That's great. I'm trying to get a hold of another guy that said he got it to work on pn. I tried but ended​ up having to start over and flash stock. I'll tell u this if you haven't tried restoring a backup with rc2, don't, it caused all kinds of problems. I went back to rc1.

I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,

jawonder said:
I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,
Click to expand...
Click to collapse
You might have to reboot once, and I uninstalled and reinstalled it. It works. I even used it to back to my stuff after rc2 took it all away lol
---------- Post added at 09:29 PM ---------- Previous post was at 09:26 PM ----------
jawonder said:
I can't get Titanium Backup to work . I did check "force busybody and SQlite" in Troublshoot settings,
Click to expand...
Click to collapse
Make sure and enable busy box inside magisk manager settings. That might do the trick and I installed busy box like normal to, not sure if I had to, I think it might be built in to that app

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.

Magisk Systemless root how to OTA update? Help needed!

I'm following the topjohnwu's guide on how to update with Magisk but I do not find it clear enough. Are these the steps I need to take in order to not-brick and update my phone with the Feb update.
1. Uninstall Magisk by "restore images" option.
2. Install OTA
3. Reboot to reinstall Magisk on second slot
Magisk is NOT installed on the second partition! And I prefer not to flash back the original image just to do that. My system should be read only and I do not have twrp, I never had, I updated my Google services framework from apkmirror and I got the update, now how do I apply it without soft bricking?

Update
Step 2 failed, "installation problem". Wtf do I do in order not to lose Magisk or data?
Edit
I've uninstalled Magisk but haven't restarted, hoping to get a solution where I keep my sh*t since that's what the guide said...
Edit 2
I'm reading the other thread but I'm having trouble finding a single useful information there, quote one if you find it, it might be my autism that I don't see a solution in that three pages long thread. Tell me I need to MiFlash this sh*t so I calmly jump through my window instead of wasting the whole night on making it work, then wasting another day on backing my sh*t up.
Edit 3
Fully uninstalled Magisk by instructions of an indian guide. BOOTLOOP.
Note to self, stop following southern asian guides.
Downloaded ROM and MiFlash, flashed flash_all_except_storage.bat.
Shook for 4 minutes until "success" mark, successful reboot.
Edit 4:
follow the regular magisk flash guide https://forum.xda-developers.com/mi-a1/help/how-to-root-mi-a1-february-ota-update-t3757934

If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.

_mysiak_ said:
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
Click to expand...
Click to collapse
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?

A14DWIN said:
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
Click to expand...
Click to collapse
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.

_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Dang I really need that command.

_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Don't bother trying to find it, it exists, I'll make a dedicated thread at some point, thanks for the answer, BusyBox seems logical.
The correct way to install Magisk? I just flash Ranjit's patched img from the official thread on Magisk root, that should be the correct way.
I just use lucky to patch cirtain apps, so that shouldn't be a problem
Right now, I'm giving Magisk root perm to Greenify, Lucky Patcher and Unified Hosts. Also both Greenify and the Unified hosts adblock have their own modules in magisk.
Hopefully I still haven't touched my system partition.

I encountered the error as well after trying the Pixel OTA method. To flash the update successfully, I flashed stock January system and boot img via fastboot and it updated properly after. Then I just patched the stock Feb boot img and went back to fastboot. Once there, i did the fastboot boot command with the patched Feb boot.img so I got root back after updating.
Sent from my Xiaomi Mi A1 using XDA Labs

HI,
I have a redmi5+ rooted. I use luckypatcher (i applied some patchs to some apps) and i have installed once BusyBox (didn't do anything in special).
I want to know if it is secure to flash the full update?
PS: how do I confirm if the system files and vendor are ok to proceed?
Thanks

cant you flash the ota in twrp and then reflash magisk if needed?

robgee789 said:
cant you flash the ota in twrp and then reflash magisk if needed?
Click to expand...
Click to collapse
Yes, I can do that.
I Know the procedure to flash full zip file via TWRP. Via this toturial: youtube.com/watch?v=oUUzxYHV_ac&t=1s&index=11&list=WL
But i want to know if it is secure to flash, because i used these two applications.

Magisk problem with oreo and twrp without encryption support

hi, i had successully upgraded my x compact to oreo, installed twrp 3.2.1 (without encrytion support) and rooted with magisk. Everything has been working fine until i messed up magisk with some module (busybox).
My phone hanged at Xperia logo after rebooting, and i had to recover it by flashing the firmware again, but now magisk no longer works. Whenever i install it, boot will hang. Without magisk it can boot, but then i don't have root.
It seems i couldn't uninstall Magisk cleanly, so the problematic module remained there. The magisk uninstaller zip failed at twrp, which i suspect it is because it cannot access some data as twrp does not support decryption.
now i have no idea how to fix this. appreciate any suggestions!
Sent from my F5321 using XDA Free mobile app

dohanin said:
hi, i had successully upgraded my x compact to oreo, installed twrp 3.2.1 (without encrytion support) and rooted with magisk. Everything has been working fine until i messed up magisk with some module (busybox).
My phone hanged at Xperia logo after rebooting, and i had to recover it by flashing the firmware again, but now magisk no longer works. Whenever i install it, boot will hang. Without magisk it can boot, but then i don't have root.
It seems i couldn't uninstall Magisk cleanly, so the problematic module remained there. The magisk uninstaller zip failed at twrp, which i suspect it is because it cannot access some data as twrp does not support decryption.
now i have no idea how to fix this. appreciate any suggestions!
Sent from my F5321 using XDA Free mobile app
Click to expand...
Click to collapse
You can always do a clean install, right?
Time consuming but you'll get your phone back, with Magisk, and have to wait for a fully working TWRP (like many of us X Compact owners, I think).

yes, but wiping everything would cost me a lot of time, and should be the last resort. i didn't even wipe /data when upgrading from nougat to oreo. i was hoping someone can teach me how to remove the problematic magisk module, like using adb or whatever.

just an update... my issue is fixed. Some expert in the Magisk forum suggested me to place a file with name ".disable_magisk" in /cache to disable the modules, and it worked.

dohanin said:
just an update... my issue is fixed. Some expert in the Magisk forum suggested me to place a file with name ".disable_magisk" in /cache to disable the modules, and it worked.
Click to expand...
Click to collapse
I was gonna say that you can disable the module by erasing a cache file, via adb, but here you go.

[HELP] - Unable to use Magisk 17.1 + A2017U B35 boot unlocked

Guys,
Anyone successful so far in setting up Magisk 17.1 on stock B35 A2017U + TWRP 3.2.1.0?
I tried following ways but everytime I flash the Magisk 17.1 using TWRP, it boot loops to recovery mode. I tried clearing Dalvik + cache everytime but in vain.
1. Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop.
2. Flash Super SU, Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop
I cannot use Super SU, blanket root due to bank & workplace apps security restrictions.
Any help/guidance will be is appreciated.
Cheers

Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.

marcdw said:
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
Click to expand...
Click to collapse
Thanks.
Thinking of trying with v16.7 first. If that works then great.

mandrax.prime said:
Thanks.
Thinking of trying with v16.7 first. If that works then great.
Click to expand...
Click to collapse
it does. i'm staying on 16.7

It would be nice to always have a working version of Magisk as Google updates their Safety Net. We have to update as they update.

I ran into problems today with Magisk 18.1 on the latest official LineageOS 15.1, nothing I did was able to get magisk to work (no icon, no error messages).
Has anyone else tried?

Magisk should work fine on LOS, I use it (Magisk) when I have to (i.e. when there is a particular use for it, like converting a systemless mod to a system-installed mod).
On B35, no go, phone will bootloop. Magisk should work fine on stock ROMs up to B15 N, maybe also with the B25 and B32 OTAs too. I'm not a ZTE stock ROM fan, I dont spend alot of time rooting stock, but from the few tests I did,those were my results.
If you have an exFAT SD card, installing Magisk on stock ROM may make your SD falsely show up as corrupt, only solution is to use the inferior/antiquated FAT32 filesystem.
Maybe one day I'll write my own open source root solution, just to show the Android community that Magisk isnt the only game in town for rooting modern ROMs on modern devices. I dont need to hide from SafetyNet, I dont need stupid systemless mods, I just need root that work reliably. I know this will fall on deaf ears, but Magisk is more trouble than it's worth, I'd recommend staying unrooted instead of using it. @topjohnwu is a genius and means well, I'm sure, but in the real world Magisk just isnt reliable enough.

I tried Magisk 17.3, 18.0, and 18.1 on Axon 7 B19 and B35- bootloop on every try