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

Stock rom 8.1 July - rooting sometimes causes hangs during boot

Did anyone notice that doing a "fastboot boot boot-patched.img" for installing magisk sometimes hangs during boot or a stock recovery error msg "Could not load Android system. Your data could be corrupt....."
I need a few tries before it boots properly. And then installing the systemless expose module gives a similar error.
edit- It doesn't seem to be happening anymore. I tried reproduce the problem but couldn't get it to hang after many tries.
Others have reported seeing this issue as well.

Use TWRP for Magisk installation + check here https://forum.xda-developers.com/mi-a1/help/rooted-device-freezes-booting-secure-t3819483

_mysiak_ said:
Use TWRP for Magisk installation + check here https://forum.xda-developers.com/mi-a1/help/rooted-device-freezes-booting-secure-t3819483
Click to expand...
Click to collapse
Will installing magisk via TWRP break OTA? I'm assuming you boot(not flash TWRP earlier) into TWRP and flash the Magisk framework zip.
From the thread, it sounds like Magisk 16.7 beta has problems with common apps.

barrack1 said:
Will installing magisk via TWRP break OTA? I'm assuming you boot(not flash TWRP earlier) into TWRP and flash the Magisk framework zip.
From the thread, it sounds like Magisk 16.7 beta has problems with common apps.
Click to expand...
Click to collapse
If you boot TWRP to flash magisk it won't break OTA.
I installed 16.7 yesterday and no problem so far with any app.

pantezuma said:
If you boot TWRP to flash magisk it won't break OTA.
I installed 16.7 yesterday and no problem so far with any app.
Click to expand...
Click to collapse
Do you know why flashing magisk after booting into TWRP won't cause problems VS booting into patched boot.img and installing Magisk via "direct install"?? It didn't cause any big booting issue pre 8.1 for me until the last update.

barrack1 said:
Do you know why flashing magisk after booting into TWRP won't cause problems VS booting into patched boot.img and installing Magisk via "direct install"?? It didn't cause any big booting issue pre 8.1 for me until the last update.
Click to expand...
Click to collapse
I think you booted an image patched with 16.0 and not 16.7 (you can try to get an image patched with 16.7 beta just to verify).
As said before, it seems 16.0 has some issues regarding booting and secure boot solved in 16.7.

Magisk V17 - V17.1

Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.

Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.

iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
I'll try right away.

iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thank you bro, I followed same steps however, I got a bootloop ;(

MaZeNsMz said:
Thank you bro, I followed same steps however, I got a bootloop ;(
Click to expand...
Click to collapse
I can't say what else would help sorry, those are the exact steps I followed and they worked.
Perhaps you could post in the Magisk part of the forums with some info about your device and see if someone could help.

MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
This is a magisk issue and shouldn't be posted here
Sent from my LG-H910 using XDA Labs

I had the same problem till I went to twrp recovery and flashed the zip that magisk downloaded and it works great. Only problem left on the side is trying to get Xposed to work again through the new magisk on H918 Super Rom, it's not working ATM but I think it's fixable somehow I guess. Magisk is effecting all phones, not just V20 btw.
Check out the video about the API and safetynet by the YouTuber HighOnAndroid. That video let's u know what's up with magisk the day before new magisk update came.

Is it possible that someone backup and share with me boot partition, and from my side I recover it ?!

I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?

I was able to directly install Magisk 17.1 from Magisk itself without issues.

SebTech33 said:
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
Click to expand...
Click to collapse
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0

KawaiiNek0 said:
I was able to directly install Magisk 17.1 from Magisk itself without issues.
Click to expand...
Click to collapse
Very locky,
I did the same here by I end up with a nice boot loop

MaZeNsMz said:
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
Click to expand...
Click to collapse
Have you tried another kernel?

Anyone could test sixaxis compatibility checker?
(free on store)
Only on h990ds. 910 and other never were affected by this problem with previous magisk.
Dont know if v17 solved this problem.
Thanks

SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
I'll try today, do you recommend any kernel?

SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
Tried D.O.T.S and failed, bootloop
I am thinking if someone can backup the boot and share it with us. So we can recover it
Regards..

Has anyone found a way to make 17.1 work on the H990DS? It took me several flashes to get it to boot but after a couple restarts it started bootlooping again so I had to downgrade to 16 and 16 works just fine

Just stay on v16 until they can work the bugs out with v17 -- you aren't gaining anything by going to v17.
-- Brian

iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thanks, that did the trick for me on lg h910r

MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
Note 26.10.2018 :
I upgraded to Oreo V8.0 from here and everything is fine now

{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.

T580 was working fine. Updated Magisk through MM and now I am on a bootloop

Hi Guys,
Magisk had an update so I installed in through the recommended way in the MM app. Now I am stuck in a boot loop
I tried flashing magisk unistaller to see if that could fix, and it did not
I also tried reflashing magisk and nothign has changed at all.

sjbayer3 said:
Hi Guys,
Magisk had an update so I installed in through the recommended way in the MM app. Now I am stuck in a boot loop
I tried flashing magisk unistaller to see if that could fix, and it did not
I also tried reflashing magisk and nothign has changed at all.
Click to expand...
Click to collapse
Boot to download mode and flash stock firmware