Database Users

[GUIDE] Install Xposed without breaking safety net on Nougat.

Note: THIS WILL NOT WORK WITH SYSTEMLESS XPOSED, YOU MUST USE THE CLASSIC VERSION!
Configuration tested on:
Redmi Note 3 Kenzo 3gb goodix variant.
Officially unlocked bootloader.
Installed latest global dev rom (7.7.20) with miflash in edl mode then installed TWRP official 3.1.1-0 then installed 7.7.6 firmware from LineageOS 14.1 thread.
Latest LineageOS build (2/8/17) with Radon Kernel 5.3.
Steps:
1. Install latest global dev rom to make sure you have the proper nougat binary blobs on your device. Preferable to use miflash and phone in edl mode. Allow phone to boot one time so rom can partition the emmc properly.
2. Install latest TWRP official (3.1.1-0) by putting phone in bootloader mode and connecting to PC via usb cable. Copy the twrp recovery image to the same place that fastboot.exe is located. Open an elevated/admin command prompt and navigate to where fastboot.exe is located. Type "fastboot flash recovery NameOfRecovery.img" (without quotes of course). When that is finished type "fastboot boot NameOfRecovery.img."
3. Install zips in this order. LineageOS rom, OpenGapps, Radon Kernel 5.3 (selected all default settings), Magisk 13.3.
4. Reboot to system, set up phone and install any apps that need to pass cts safety net at this point. E.G. Super Mario Run.
5. Reboot to recovery.
6. Install the latest Xposed build for SDK25 ARM64 from PurifyOS Xposed thread - https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221. DO NOT USE THE SYSTEMLESS MAGISK VERSION.
7. Reboot to system.
8. Install latest Xposed Material installer by DVDAndroid - https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758. At this point you will fail safety net. The next step will fix that.
9. Install Root Switch 1.3.3.2 apk.
10. When you need to pass CTS Safety Net use Root Switch to disable Xposed. It will ask you confirmation to perform a soft reboot. After the soft reboot Xposed will be disabled and you will be able to pass CTS Safety net again. DO NOT USE THE DISABLE ROOT SWITCH! THIS WILL PERMANENTLY MESS UP MAGISK!
THIS HAS ONLY BEEN TESTED ON THE LISTED CONFIGURATION. DO NOT ASK IF IT WORKS ON ANY OTHER CONFIGURATION, TEST IT YOURSELF. I WILL NOT BE RESPONDING TO QUERIES, IF YOU FOLLOW THE STEPS AS LISTED YOU WILL BE JUST FINE.

Linn for root switch

tried this on rr rom redmi note 3 kenzo working absolutely fine highly recommend

Works on One Plus 3T with Oxygen OS 4.1.6!
Thanks!

If the root switch app disables xposed, then what is the use of it

[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

Updating Already Rooted (via Magisk) Pixel 2 XL from Android 8.x to 9.x

I am hoping I can bounce my plan of attack for updating my Pixel 2 XL that is already rooted (using Magisk Manager + Magisk) and currently running Magisk Manager 5.6.4 + Magisk v16.0 and Android 8.1 (build OPM1.171019.021) to the latest and greatest version of Android (looks like its currently v9.0 w/ build# PQ1A.181105.017.A1)
First off, I didn't use TWRP when originally rooting android v8.1 on my Pixel 2 XL previously, I didn't think I needed it and had no plan to ever install a custom ROM. I am still in this boat and would prefer not to install or use TWRP if possible. I went the route letting the magisk manager app on my phone update the (at that time) newest factory image of android then flashing that image back onto my phone via fastboot and everything went great.
Anyway - If anyone would look over my approach here and let me know if this should work or not I would appreciate it!
My plan for updating to android 9.0 and keeping root:
1. Download the last android factory image from google (currently PQ1A.181105.017.A1)
2. Backup everything on my phone I care about (pictures, etc)
3. Use fastboot to flash the latest factory image to my phone (I understand this will reset everything on my phone and I'll lose root for the time being)
4. Download magisk manager apk from ******************
5. Make sure my phone is setup to allow installation of apps from unknown sources, then install magisk manager on my phone
6. Use Magisk Manager to install magisk and use the option to "patch boot image file" to patch the boot.img file from the latest factory android image (currently PQ1A.181105.017.A1)
7. Use flashboot to flash the patched version of the latest factory android image (currently PQ1A.181105.017.A1) to my phone, then finally check that root is working by using Magisk Manager. Then restore my backed up files to my phone (e.g pictures)
Thanks in advance for the advice!

I'm rooted with magisk, i took the ota, knowing full well it wasn't going to complete while I'm rooted. Haha me... It took. Didn't lose a thing except root. 10 minutes later, I'm rooted on pie. No issues for me.
As for twrp, you don't flash it, you boot it. It runs until you reboot. I turn off security on the phone before I re- boot into the bootloader. Twrp did or still does have an issue with patterns. Otherwise it works great for my needs.

Flashing Magisk in TWRP Making Bootup Hang

Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.

Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Have you tried to change your twrp? What's the exact file name of it? Did you tried magisk 17.1?

Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Phone is starting is a bug on cr droid, los also. I don't know fixes. But don't worry you are not the only one with this issue.

Try Magisk beta 19.0. I had the same problem as you with 18.0 and 18.1, but 19.0 solved it for me...

Help from Rooting to Xposed, rookie explanation

Hi guys. I had a multiple day struggle and all the manuals were only partial, so I try to summarize all the steps taken to unlock my phone, root it with magisk and install Xposed SDK28.
1) Unlock bootloader
It takes time and I had to wait that mentioned 168h (it may differ) and there is nothing you can do about it on your K20/9T
I used the official xiaomi unlock tool, latest version, and followed all the steps there.
2) Install TWRP
Oh god, on this phone it gave me headache and I almost bricked my phone and it convinced me to write you a manual just in case you are lost as I had been. Here you go.
There are three versions of TWRP on this forum and I selected the Chinese one (no greek nor russian)
After unlocking the bootloader, I only flashed the twrp (no other files, just the img with the rom) and then did fastboot reboot.
It stucked on booting. Here I pressed volume up and power and it took me to the newly installed TWRP. This didn't work with an other TWRP than Chinese. I ended up in the bootloop to fastboot only.
Then I installed the ROM. In my case Pixel Experience, latest version. The manual mentioned in this forum tells you to install Magisk together with your ROM. It again caused a bootloop on my device, so I wiped my device in TWRP, installed clean Pixel Experience ROM, and let it boot without magisk and permissive.
I checked via root checker if my device is rooted. And it was not.
3) Root via Magisk/SU applicable
Then I downloaded
Magisk Manager 7.3.2.apk and installed it with confirmation in settings that I allow the whatever file manager to install apps from unknown source.
In the Magisk Manager I downloaded a zip with Magisk and rebooted to TWRP (turn off the device, and then volume up and power)
I flashed the zip downloaded by that manager - no wipe
rebooted back to system and checked the root. Rooted.
4) Xposed
Download Magisk manager 7.3.2.
Install modules via Magisk Manager
- Riru Core v19.4 or higher
- Riru - EdXposed v0.4.5.1._beta(4463) (YAHFA)
restart your device
Then install EdXposedInstaller_V2.2.4-release.apk and check if it works.
restart your device and you can start installing modules. Even Gravitybox (P) works!
I really hope I briefly helped you guys. Viva la modding and enjoy your cool Xiaomi. Thanks to all the contributors on xda, thanks to them I was able to summarize this little manual.
In case you stuck somewhere and need to recover anything such as boot.img or any other shananingans you did with your phone, as I did too, you need to download the miflash tool, in this case the latest version didn't work so I used 2014.05.09.0, and downloaded the official fastboot rom davinci_eea_global_images_V10.3.7.0.PFJEUXM_20190602.0000.00_9.0_eea_eab1d1cc52, flashed it with miflash (around 6 minutes), stucked again in bootloop, rebooted to TWRP via volume up and power during the bootloop, and followed the steps from flashing the TWRP (after MiFlash it has only the default MiRecovery) and installed my ROM.