Magisk hell resolved??!!!!!!!??!!!!!!!!!!?? - ZTE Axon 7 Questions & Answers

im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR

works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!

I cant get to bypass safetynet V: other than that root works fine

J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed

Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.

desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...

try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431

also cant have xposed installed with the sn fix

Related

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.

Switch to Magisk from Super SU

Hey guys,
I apologize in advance if this is somewhere on the forum (I coukdn't find anything on it.)
So last evening I decided to do the fllowing: unlock, install twrp, root and install a custom rom. I'm comeing from a Note 3 so just getting familar with everything for Nexus.
I completed the unlock, twrp install and root (supersu) with the nexus root toolkit and made a backup as well (not through twrp), and flashed the latest pure nexus rom (stock kernal).
I would like to switch over to magisk so I can get the benefits of using it. How would I go about doing so ?
Thanks !
rich6619 said:
Hey guys,
I apologize in advance if this is somewhere on the forum (I coukdn't find anything on it.)
So last evening I decided to do the fllowing: unlock, install twrp, root and install a custom rom. I'm comeing from a Note 3 so just getting familar with everything for Nexus.
I completed the unlock, twrp install and root (supersu) with the nexus root toolkit and made a backup as well (not through twrp), and flashed the latest pure nexus rom (stock kernal).
I would like to switch over to magisk so I can get the benefits of using it. How would I go about doing so ?
Thanks !
Click to expand...
Click to collapse
If you want magisk then dirty flash your rom to get rid of magisk. After that flash the magisk zip from recovery then reboot and go to play store to update app. Why do you want magisk btw? I used it but drooped it for supersu as it made the splash screen (boot logo that said Google) stay for a while making boot time take a long time.
Ok so if I did the following would I be in the clear:
Full Wipe
Flash rom
Gapps
Elementalx kernal (want to try this kernal)
Magisk 12.0
Reboot
Install magisk manager
I'd like to have magisk to hide root, for things like netflix.
Also would it make any sense to run unsu while flashing everything else ?
rich6619 said:
Ok so if I did the following would I be in the clear:
Full Wipe
Flash rom
Gapps
Elementalx kernal (want to try this kernal)
Magisk 12.0
Reboot
Install magisk manager
I'd like to have magisk to hide root, for things like netflix.
Also would it make any sense to run unsu while flashing everything else ?
Click to expand...
Click to collapse
No need to flash unsu. If Netflix is the only reason you are using magisk then you could just use apkmirror. Also, I heard that the app detects unlocked bootloaders. You should be good to wipe the rom and flash all the stuff you said.
I'll look into apkmirror. Forgot to mentioned I'd like to used android pay as well. Can apkmirror help with that ?
rich6619 said:
I'll look into apkmirror. Forgot to mentioned I'd like to used android pay as well. Can apkmirror help with that ?
Click to expand...
Click to collapse
If you want android pay then you need magisk and need to hide magisk from it aswell as using the hide root settings. You also need to pass the SafetyNet check if you want to use android pay.
Ok thanks. So I will do everything I mentioned in the list as well as set magisk to hide in magisk manager settings ?
rich6619 said:
Ok thanks. So I will do everything I mentioned in the list as well as set magisk to hide in magisk manager settings ?
Click to expand...
Click to collapse
Yes, make sure to run a SafetyNet check.
Will do. Thanks for all the help !
rich6619 said:
Will do. Thanks for all the help !
Click to expand...
Click to collapse
You're welcome, hopefully all goes well?.
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
rich6619 said:
Will do. Thanks for all the help !
Click to expand...
Click to collapse
Also, make sure to check out my thread for better idle drain by blocking wakelocks if you haven't already seen it. I've built a version for pure nexus.
https://forum.xda-developers.com/nexus-6p/general/taking-wakeblock-requests-t3583397
I will for sure check it out. Thanks again !
DEVILOPS 007 said:
You're welcome, hopefully all goes well.
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
Also, make sure to check out my thread for better idle drain by blocking wakelocks if you haven't already seen it. I've built a version for pure nexus.
https://forum.xda-developers.com/nexus-6p/general/taking-wakeblock-requests-t3583397
Click to expand...
Click to collapse
So just an update. Did the following :
flashed
Rom
Gapps
Magisk
ElementalX Kernal
Reboot
Installed Magisk Manager, enabled magisk hide and systemless host (for adaway) and rebooted. Safetynet passes in magisk manager. Went to play store, checked settings device certification and it's certified. Searched netflix, still not available. I'm guessing this has to do with the bootloader being unlocked ? Is there a way around this or will I have to just download the latest apk from apk mirror ?
Going to test the phone out for a few days to see what battery life is like with elementalx (I was averaging around 4.5 hrs ost with stock). If I don't get any better I will def test out your wakeblock.
I would like to hijack this thread a little bit as it is on the same topic as well with slight differences, sorry!
I got a stock 6P with unlocked bootloader and rooted with systemless SuperSU. Fiddled around with Magisk manager before, it will fail SafetyNet check.
How do I switch to phh superuser and using magisk? Will this pass SafetyNet check? The bootloader will still be unlocked....
My main intent is to be able to use Android Pay.
This thread is right up my alley. I just got a Nexus 6 ( XT1103 ) unlocked bootloader, rooted using a Windows toolkit (don't remember the name) and have twrp installed. I read about Magisk after trying to use Android pay without any luck. I would like to use Android pay and believe Magisk would let me be able to do so with still having use of root apps.
Is it possible to go from root to Magisk without loosing my data?
how to keep magisk from uninstalling during a reboot!!!!!!???!!!!!!
im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM if also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know

Magisk 13.1 working for anyone?

Hi all,
My system was working fine with Magisk v12, I saw there was a big new update, I was interested and updated.
But using the latest Magisk Manager, it says root is not detected.
It's not a big problem, I will restore back to v12 for now, but did anyone else get it working?
Thanks
Asus zenfone 2 flash update manual Magisk 13.1 crash recovery recovery then AD
Same here with Xperia XZ. With v13.1 Root is not detected. v12 is working fine.
Have tried to reinstall it by completely removing and flashing from TWRP, but still no luck.
13.1 and 13.2 working on 7.1 with repacked stock kernel with drmfix fix. It will also work with newest genesis kernel
I upgraded Magisk 12 to 13 beta, then 13.1 and 13.2 without problems.
Even SafetyNet Check passes.
I'm using genesis-nodrm kernel.
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
qvmuhuuxz said:
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
Click to expand...
Click to collapse
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
realtuxen said:
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
Click to expand...
Click to collapse
Ok I'll try that.
I believe I flashed v13.2 straight over v12.
But when downgrading back to 12, I did flash the uninstaller first.
I'll try uninstalling and then updating
- Still no luck, it didn't work.
I tried updating Magisk 12 -> 13.1 thru the manager, and it would download the zip then do nothing. I found the zip in the Magisk directory, and installed it like it was a module, thru the manager, and it appeared to work. I got the new Magisk Manager (5.0.4) and it says I'm on Magisk 13.1 but that Magisk is not installed, and there is no root.
Following the installation instructions, I rebooted a few times, no change. So I flashed Magisk uninstaller, cleared cache/davlik, and rebooted. Uninstalled Magsick Manager. Rebooted. Booted to TWRP and flashed Magisk-13.1.zip. Rebooted twice. Same issues; Manager 5.0.4 says I'm on Magisk 13.1 but that it's not installed, no root.
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
voilsb said:
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
Click to expand...
Click to collapse
I didn't have to reboot after flashing magisk uninstaller, I just flashed v12 straight after.
And I just uninstalled the new magisk manager then the old one right away, I think?
Magisk manager 13.1 not working for me either tried installing thru app but it does not work
might be related to this https://github.com/topjohnwu/Magisk/issues/265
Also it might be related to this - https://github.com/topjohnwu/Magisk/issues/166#issuecomment-298765812
"Use rootkernel tool from tobias.waldvogel to fix drm instead of PoC TA fix. It seems to be incompatible to Magisk while rootkernel tool patched images work"
I swapped over to Genesis kernel (1.05, the current latest) to try and see if it would help my device pass safety net, since for some reason it is not passing anymore (I tried lots to fix it, flashing etc)
As I posted directly above, it looks like Magisk v13 doesn't like ta_poc, so I used the drmfix version, and Magisk v13.3 works great, and once again my device passes safety net

Rooting OREO (41.3.A.2.24)

I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148

[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

Categories

Resources