Database Users

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

Magisk v13.1, Safe to upgrade?

Just like the topic says. I'm currently running Magisk 11.6 and was told not to install or upgrade to v 12 since it was buggy. Well it looks like v13 is available (13.1 actually). Is this safe to upgrade?
Rom: NATF 4.0 for H910 (AT&T) - Android v7.0
Sidenote: What is preventing SafetyNet from passing (CTS Profile mismatch) ? Is the due to the DirtyCow exploit? Debugging is disabled and Magisk hide is on.

is definitely safe if you have a US996 variant of the LGV20 as I'm using it on that... about to try it out on my H918 variant of the LGV20, but should be fine with since I went through all the betas fine

I flashed 13beta on my h918 without doing anything special and it works just fine

Well I took the advice and upgraded. It didn't go so smooth. The update feature within Magisk manager didn't work. First it didn't let the device reboot. I had to pull the battery since all the shutdown commands did nothing.
2nd time trying to upgrade, it rebooted this time and when I checked the manager again it said magisk wasn't even installed. So I manually got the zip and updated in recovery and then manually installed the latest apk for the manager and finally I'm up to date. All is well (aside from safetynet).

When switching to Magisk 13.1 from anything lower you should use the magisk uninstaller before flashing the newer Magisk . Anything lower than Magisk 13 is not compatible with the newer v5 Magisk manager as far as I know.

shadavis08 said:
When switching to Magisk 13.1 from anything lower you should use the magisk uninstaller before flashing the newer Magisk . Anything lower than Magisk 13 is not compatible with the newer v5 Magisk manager as far as I know.
Click to expand...
Click to collapse
I completely overlooked the uninstaller. I don't know how, I just did.

Updated to 13.2 and SafetyNet seems to pass now. Although I'm still "Uncertified" in the Play store.
Well goddamn, it must be working because I was able to get Google Wallet to work and Android Pay lets me add a card, although it says my card is not supported. I don't have a second card currently to test it. Maybe I need to enable it on the banks end. I'll call them tomorrow and ask.
Edit: Nope. It's my bank, not the card.

What sort of problems will I encounter if I root the stock rom for T580?

I am planning to eventually root the stock rom of SM-T580 to use AdAway and Greenify.
What sort of problems / side effects if any might I run into after rooting the stock rom?
Also I do not plan on using SuperSU as I will be using Magisk.

Some apps can not be installed anymore. (Netflix from playstore, super mario). Magisk does not prevent this. Use a browser with an ad blocker.

bert73 said:
Some apps can not be installed anymore. (Netflix from playstore, super mario). Magisk does not prevent this. Use a browser with an ad blocker.
Click to expand...
Click to collapse
Not even with Magisk hide enabled?

Not on my tab s2 with magisk.

Netflix working fine here with Magisk 13.0 and Stock Android N. But on my OnePlus One Netflix isn't available even with Magisk.

Shadowghoster said:
Netflix working fine here with Magisk 13.0 and Stock Android N. But on my OnePlus One Netflix isn't available even with Magisk.
Click to expand...
Click to collapse
When updating Magisk is it better to use the uninstaller zip and flash Magisk again or is using the built in updater fine?

You can't go wrong any way you use magisk. Mostly everything can be flashed directly from magisk. Remember magisk is root and has control. You won't have any problem updating magisk right from it's interface. The only time I've had a problem, has been from flashing a magisk module that doesn't support my device. Best regards.

Axon 7 doesnt boot with Magisk 13.4 - 14

Hi,
my A2017G (B05 Nougat) doesnt boot with Magisk v13.4 or above. I tried beta versions and also the brandnew v14. The bootanimation is stuttering but thats all.
Im using 13.3 and Manager v5.3.0, which is working so far.
I cant deinstall systemapps. 'reboot disemmcwp' has no effect. I think its because of magisk. With SuperSu i can deinstall systemapps. But i use some modules with magisk so i want stay with magisk, but it seems not working properly. Can someone confirm this issues?
Where's the problem?
Any ideas?

I'm pretty sure stock has issues with Magisk in general. I'm using the latest 14 on RR with no issues.

works fine for me, ive ran 13.6 on B05 and B06

MaxRink said:
works fine for me, ive ran 13.6 on B05 and B06
Click to expand...
Click to collapse
Whats flashed on your phone? Bootstack + System with Magisk 13.6 only?
I dont understand why magisk 13.3 works without any problems, but every version above has this issue on my phone.

Stock B06 with B06 bootstack, 13.3, 13.6 and 14 work just fine

Hi,
i think i found the problem. If i flash xposed (systemless v87 sdk25 by PurifyOS), my phone cant boot up.
So i have to wait and use magisk 13.3, until xposed get an update, to work with magisk 13.4 and versions above.

Magisk hell resolved??!!!!!!!??!!!!!!!!!!??

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