yashsingh1/xdaforums huggingface dataset:
[Magisk] jpwhre:
Just to add my $0.02

Sprint HTC M9

S-Off

Unlocked Bootloader

Stock Rooted Rom

XDA Labs informed (updated manager) and manager informed me of update. Yesterday it gave me option to install, and it then downloaded the zip and reboot option. When I noticed twrp didn't reboot automatically, I tried to install again manually. When it failed, I copied log to device before rebooting. recovery7-11.log attached.

Today I get popup again showing update. When I click to install, it does nothing. Had to visit https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 from my device to find download location of current version.

After manual download, using this app https://play.google.com/store/apps/details?id=com.beerbong.zipinst&hl=en it crashes in wierd ways when selecting 13.1 zip but does fine on others (tested before posting this)

Putting device into recovery and flashing file I manually downloaded fails. recovery7-12.log attached.

ROM

https://xdaforums.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355Running latest rooted.

Kernel

Unreleased from best of my knowledge as it was sent to me thru pm by developer for testing.

3.10.84Minimalistic-RC7_N
thicklizard@BadseedCustoms #15
SMP PREEMPT
[Magisk] jwrezz:
My issue (magisk not installed even tho magisksu was) is due to magisk manager not updating. Just checked and it was V4. Updated to V5 and now it shows magisk 13.2 installed and all is working as it is supposed to.
[Magisk] Didgeridoohan:
It's failing because you have SuperSU installed. SuperSU compatiblity has been dropped as of Magisk v13+... You'll need to unroot, restore an untouched boot image and start again. Your ROM comes rooted, but it does it by flashing the SuperSU zip at the end, so the boot image inside the ROM zip should be untouched and ready for Magisk.
[Magisk] divineBliss:
You mean Magisk v13.1 ;)
[Magisk] gewe:
I found the answer to my own question, well, to at least a part of it.

The boot partition can be found by looking in the directory /dev/block/platform/msm_sdcc.1/by-name, en check what partition the boot symlink points to. In my case it was mmcblk0p31.

I still don't know why Magisk Manager can't auto detect it, and whether it is necessary for proper installation. I upgraded the manager to version 5 via XDA labs. Trying to install Magisk framework v13.1 failed.

I then:

- booted into TWRP and flashed the Magisk uninstaller: OK

- rebooted: OK

- booted into TWRP and flashed Magis v13.1: OK. It detected the boot partition, recognised a stock boot image.

- rebooted: OK

- started Magisk Manager 5: Magisk not installed, system not rooted.

Why? :mad:

What did I do wrong?
[Magisk] Wesley32:
Maybe there is a super easy fix for my error here. but, I will attach recovery log.

basically always get this error:

- Data unavailable, use cache workaround
-Mounting /cache/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
[Magisk] Didgeridoohan:
You must be talking about this new feature of MagiskSU (from the changelog in the release thread):

- [MagiskSU] Introduce new timeout queue mechanism, prevent performance hit with poorly written su apps

Here you can read a little more about it: https://xdaforums.com/showpost.php?p=72587983&postcount=22
[Magisk] Lucas Reis Grand Prime:
Magisk 13.1

Magisk 13.1 don't work in lollipop 5.0.2 .....=(
[Magisk] JKL397:
Hi guys.. I have a problem with downloading Magisk v13.1. I had the magisk manager 4.3.3. I had Magisksu 12 And i got a notification today for Magisk v13.1. I clicked download and install. It said it was installed and told me to reboot my phone. When i rebooted, i opened magisk manager and it said there is no magisk version installed. I went recovery mode and flashed the zip myself but still same result. I found the new version of Magisk Manager, downloaded it. Still same thing it says my phone is not rooted. I tried using uninstaller zip and downloading. Didn't work. I downloaded magisk 12 with new magisk manager and it seems rooted now. When i try to upgrade by clicking download and install, it downloads the zip but says installing error and doesn't download it. Now i have latest magisk manager(5.04) with magisk 12.0. Seems rooted with Greenify app but i really want to update it. I have a HTC One (M8) European version and Android 6 with Sense 7. Can someone help me please ? Thanks in advance :)
[Magisk] android_smater:
It seem like has problem with kenzo....
[Magisk] Didgeridoohan:
A recovery log saved right after flashing the Magisk zip could shed some light on the issue. Attach (don't paste) it to a post in the thread.

Lot's of errors going on there... Not sure why, but your device isn't compatible, that's for sure. What's your device details (ROM, kernel, etc).

What's "don't work". Details (and preferably logs), please.

Using Magisk v12.0 with Magisk Manager v5+ might cause issues... Try flashing the v13.1 zip in recovery, save the recovery log and post it here (as an attachment, don't paste).
[Magisk] Cybertheo:
Problem

Hi guys, I have a problem with Magisk SU 13.1: When I try to flash Magisk 13.1 or with Magisk Manager, when the phone reboot, he stuck at boot logo so I have flash uninstaller but when I flash Magisk 12.0 it's work !

Any idea ?

My phone is a Honor 5x (KIW-L21) (kiwi)
[Magisk] Wesley32:
I can upload my stock boot.img, if that will help the dev. but anyway,

i'll attach this screenshot. I have an Honor 8 FRD-L04.
[Magisk] JKL397:
Here and thanks ^^
[Magisk] :
same issue on my HTC Desire 10 lifestyle, stock

maybe it is HTC only related?
[Magisk] JKL397:
I don't know but it shows in his profile that topjohnwu is using HTC too so i don't really think so :D
[Magisk] Didgeridoohan:
You could upload a copy of your boot image with the recovery log to a new issue on GitHub. Device support is probably not as prioritised as stability at the moment though...

Meanwhile you could try different ROMs and/or custom kernels.

That's a known issue and it's being worked on. Wait for a fix...
[Magisk] Ronisk8:
PLS .. help me !! :( :crying:

I have the latest version installed .. v13.1

Can I reset Knox with Magisk? Or remove Custom Availability Status? How do I do?

:confused:

When you download the Xposed Framework in Magisk, the installation error ...

Thank you very much in advance

:good:
[Magisk] JKL397:
Thank you again i guess i will download the older version of magisk manager and magisksu thank you again ^^
[Magisk] Raphsodyz:
13.1 is working on all 6.0 android devices? My magisk manager on my xperia e5 don't recognize it.
[Magisk] cygery:
Thanks, I read that post. However, it didn't sound like there'd be any problems similar to the ones I experience to be expected.

I'll try to dig deeper into this issue asap. Since this issue appeared after upgrading to 13.1 from 12, are you aware of any specific changes which could cause su requests/sessions not coming through/getting stuck?
[Magisk] NeoBeum:
Hopefully [MENTION=4470081]topjohnwu[/MENTION] manages to see this....

There's more at my picture guide :

https://xdaforums.com/z5-compact/general/recovery-nougat-7-0-android-bootable-t3609358
[Magisk] JpegXguy:
If you use core only move it's fine. But you can use the last 13 beta just fine with modules
[Magisk] LTMendarynas7:
Anyone manage to make V4A work on magisk 13.1? Im on sultan ROM for OnePlus One and can't get it working. 12.0 works fine. Maybe Im doing something wrong here.

1. Flash ROM/Gapps

2. Flash Magisk

3. Download V4A Magisk module and install it

4. Download V4A APK with link provided in module and install it
[Magisk] Didgeridoohan:
Well, if your app makes su requests in a rapid fashion and there's a new feature of Magisk that deals with just that kind of thing, I'd say it's a good chance they're connected somehow. Of course, there's been a lot of work to both Magisk and MagiskSU between v12.0 and v13.1...
[Magisk] jwrezz:
Yeah, sorry, 13.1
[Magisk] demlasjr:
Hey guys....is just me or whatever I do, I never pass ctsProfile and basicintegrity. I never ever could get SafetyNet completely green.
[Magisk] DodoGTA:
What's your device, ROM and kernel? And please attach Magisk log from Magisk Manager
[Magisk] hiimpig1:
Magisk Manager are not working with me sometime, it will worked after boot for few hours. But after reboot, it not working again. MagiskHide, SU, module working great.

LOS13, Android 6.0.1
[Magisk] demlasjr:
I'm using a Galaxy S4 with JDCTeam Optimized LineageOS 14.1 and Alucard kernel (https://xdaforums.com/galaxy-s4/i9505-orig-develop/jdcteam-optimized-cyanogenmod-14-0-t3479888). Not my main device but when the main one remains without battery, I'll like to use this one for payments and things I can't on any other rooted device.

Attached is the magisk log. http://cloud.tapatalk.com/s/5966a40203988/magisk_error_20170713_003005.log

Nevermind: after a magisk reinstall I made it work for the first time ever Yay!
[Magisk] divineBliss:
Force close Magisk Manager, then clear app data, then start it again and see if that fixes it.
[Magisk] Bobthahog:
One minute I have safetynet fail then try it again and it passes. But on root check app it fails every time starting about an hour ago. Well it was good while it lasted. Looks like I'll be using the module to pass safetynet again. I'm on Sprint Galaxy Note 5 running 7.0. Here's a log if that helps.
[Magisk] hiimpig1:
It didn't worked. I tried few times even uninstall & re-install
[Magisk] DJilaniE-070:
When I install magisk 13.1 I get a error that there is something with​ my boot image. I can now only use magisk 12. Can someone help me?

P.S. my phone is the huawei p8
[Magisk] JERW28:
Did you flash the Magisk Uninstaller zip or your clean boot.img? See Github
[Magisk] dpechiu:
Same here with my stock HTC One M8.

Had Magisk 12. From Magisk manager accepted the upgrade. Phone rebooted and appeared to be "not rooted".

Reverted to pre-root backup from TWRP. Reinstalled Magisk 13.1, and latest Magisk Manager, still no joy.

Reverted to version 12, and got root again, and SafetyNet Check failed as expected.

Downloaded Magisk 13.0(c4377ed), the last beta version, and that worked! Passed SafetyNet Check too.

If I try to update to 13.1 from within the app, it downloads, but I get a "installation error" message.

Some change made between 13.0(c4377ed) and 13.1 apparently breaks root on HTC phones.
[Magisk] dpechiu:
I'm in the same boat. I have HTC One M8 US version. Magisk 13.0(c4377ed) worked for me, and passed SafetyNet Check too :D
[Magisk] dudeperfect:
For those who are getting force closure of magisk manager after updating it, try disabling the substratum theme. Worked for me.
[Magisk] GBPackerFanForLife:
Since updating to 13.1 now I can't get Safety net to work..Worked fine till I did the Upgrade..
[Magisk] BRFNGRNBWS:
Hey, I had Magisk version 13.0 installed on my Nexus 6p, with everything working fine, and I just upgraded to 13.1 via Magisk Manager. Now it says I'm not rooted, even though I was before. Help is appreciated.
[Magisk] Bobthahog:
In the Magisk logs it says "beginning of crash" and was wondering if someone could help me find out what it means. Everything is running good besides safetynet starting to fail today. Here's a log.
[Magisk] Bobthahog:
Is anyone else having the issue of safetynet passing and then 10 minutes later failing? It just failed 10 minutes ago on root check app and in Magisk manager. Then 30 seconds ago I check and it passes in both places. What is causing it to fail then pass? And this just started happening today.
[Magisk] dryness:
I've been able to get Magisk 13.1 installed on my ZTE Axon 7 (model A2017U, stock rom, update b25) successfully, and it passes SafetyNet checks without any issues. However, whenever su is called, Magisk Manager (v 5.0.4) force closes and can not be re-opened unless I clear app data.

I'm unable to upload/attach my magisk_log.txt file, so I've pasted it behind spoiler tags below. I suspect this chunk is the source of my problems, but have no clue how to resolve it:

07-12 21:34:13.407 14045 14045 E SQLiteLog: (14) cannot open file at line 32463 of [bda77dda96]
07-12 21:34:13.407 14045 14045 E SQLiteLog: (14) os_unix.c:32463: (13) open(/data/user/0/com.topjohnwu.magisk/databases/su.db-wal) -
07-12 21:34:13.407 14045 14045 E SQLiteLog: (14) unable to open database file
07-12 21:34:13.407 14045 14045 E SQLiteDatabase: Failed to open database '/data/user/0/com.topjohnwu.magisk/databases/su.db'.

removed logs from being embedded. find them here:

https://github.com/topjohnwu/Magisk/files/1146794/magisksu_log.txt
https://github.com/topjohnwu/Magisk/files/1156070/recovery.log.txt

Any suggestions are welcome.
[Magisk] LGenius3:
So I tried to install magisk 13.1 for a while now but all I get is, not installed and not rooted in the manager. However, if I check safety net status it said that it passed. I'm on an HTC One M9 running the latest Lee droid (Marshmallow) with busy box. This ROM came with chain fire su or the option to not root (I've tried both). And the option for the stock kernel or the LeeDroid "optimised" kernel. I can provide logs if you wish but upon inspection there doesn't seem to be anything on the magisk installation...

So far, I haven't flashed anything else, just the OS, a TitaniumBackup zip with all my apps, and the magisk 13.1 zip. There is no other root on my phone.

Any help would be greatly appreciated!
[Magisk] premjeeth:
I'm having trouble with magisk 13.1. It installed fine but after a reboot, I get this error msg, rooted but no root permission, not allowed.

Tried clearing app data, flashed magisk Uninstaller, flashed magisk 13.1 again, but no luck. Enabled magisk core mode, magisk hide and systemless support for adblock apps. If I do not enable systemless support, adaway gives an error, no root detected.

Couldn't attach the log as log seems to be empty. Could anyone please help?

I'm using oneplus 3t, with h2os beta 9 with twrp 3.1.1-0.
[Magisk] Jaysp656:
Anyone have an issue where the Superuser menu crashes Magisk (newest version: 13)?

Also I found that with the FrakenKernel for the Moto X Pure this causes WiFi unable to turn on.
[Magisk] SDMU:
I solved this by clearing app data+ cache
[Magisk] Varun.Shanbhag:
Yes
[Magisk] Didgeridoohan:
Read here, under "Boot image patched by other programs":

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

Sounds like a known issue that's been fixed in source. And as a FYI, Magisk v13+ is no longer compatible with SuperSU.

Magisk logs from both the beta and stable release could be useful.

Try clearing data for the Manager.
[Magisk] Matts_:
Hi!

I managed to fix the installation error by updating to the latest manager version (d'oh!), but now SafetyNet fails which was working before.

I also tried installing Magisk again which succeeded, but didn't fix the SafetyNet issue.

Any thoughts?

Thanks!

posted mobile with oneplus3 freedomos 2.8
[Magisk] JERW28:
Which one did you flash?
[Magisk] Gerard15799:
So I saw this guy he fix his safety net issue by doing this...he copied his stock build fingerprint and paste it in the build prop...keep in mind his using a custom ROM too..will this work?
[Magisk] jenslody:
Sorry for the late reply.

Not a simple fix, just what I described in my post with using selinux file from latest beta.

But the real fix is committed, so a self-build Magisk should work (at least not segfault), and a new official version will probably come soon.
[Magisk] Varun.Shanbhag:
Magisk-uninstaller-20170711
[Magisk] jenslody:
It should be fixed in official sources, see: https://github.com/topjohnwu/Magisk/issues/278, so you can either use a self-build Magisk or wait for the next release.

I can attach an actual build here or upload it to my server.

---------- Post added at 07:02 AM ---------- Previous post was at 07:00 AM ----------

Can you attach a recovery-log taken right after flashing Magisk ?
[Magisk] exodius48:
[MENTION=4470081]topjohnwu[/MENTION] Magisk Manager v5.0.4 always fc in LOS 13 rom.

Logcat attached.
[Magisk] LGenius3:
Okay thanks, so how would I use the source? Seems like I have to build it? Or do I need to wait for the next release?
[Magisk] pavan3999:
okay i'll wait for next release because i don't have pc to build it myself
[Magisk] Didgeridoohan:
Yes, that's a known workaround for devices/ROMs that doesn't have a proper CTS profile.

Must admit I did not look at the log (not gonna do that on my phone)... :p But, do you have a Substratum theme on the Manager? If so, disable it and see if that fixes anything. Also, clearing data for the Manager might be a good idea.

You either build it yourself, use an unofficial snapshot built after 170713 (none yet as of writing this) or wait for the next release.
[Magisk] JERW28:
Try

1. Reflashing clean boot.img using twrp (don't use uninstaller)

2. Flash Magisk13.1 170711/URL]

3. Wipe delvik and cache

4. reboot system

5. Wait a few minutes boot back to twrp using file manager and go to /data

6. Is magisk_debug.log there?

7. If so, post it here with information about your device
[Magisk] Didgeridoohan:
Once again: You don't need to flash the unofficial snapshot to get the magisk_debug.log. It's in the official release (and has been in the code for a while)... The unofficial 170711 snapshot should be exactly the same as the official v13.1.
[Magisk] Gerard15799:
Ohh ok...I think I might try it... just need my sister's phone...haha
[Magisk] exodius48:
Bro, LOS13 (LineageOS 13) does not support Substratum. It already have prebuilt CM13 theme engine.

And tried clear data still have that bug. So i downgrade to magisk 12 for now to make magisk installed iin my device.
[Magisk] Pupet_Master:
I had a funny thing to happen to me.

I had Magisk 12 and it Magisk APK installed. How ever i did uninstall Magisk (but not the APK) as i was debuging what app was making my SIM card unavaliable after deep sleep to make calls or use 4G (it wasn't Magisk).

Ok.. so the apk push a notification telling me that v13.1 is available. As my debug tracked the issue with the SIM card, i was going to install Magisk again anyway.

So i downloaded the APK and zip from the official thread, push the zip from my pc to my sd card (so i can flash it) but when i push the apk to the SD card (to install it) my phone file manager crashed every time i open the folder that i copied it.

So via TWRP file manager i deleted it and the folder got access normalized.

I downloaded again but saved it via my onedrive and installed the APK (before flash magisk zip via TWRP though) via cloud to the phone. It installed but it crashed every single app of my phone after. Launcher, even settings crashed.

I had to (via TWRP file manager again) delete the apk folder on data/app and data/data to reboot to my system and have the phone working again.

Is it normal to happen if i install the APK without flash the zip first? Also i had the older apk installed so i did the installation on top of the old version). Even though the apk to crash my sd card folder on file manager was odd too.

My phone is a Moto G LTE first generation with the latest CM13.1 snapshot and a custom Kernel called Zero Byte

https://xdaforums.com/moto-g/4g-development/gpl-zer0-byte-kernel-t3503640

Also Xposed is installed too

Magisk v12 was working fine
[Magisk] Turisti13:
I get this randomly, I'm on 13.1 and everything else is working ok. Rebootting and/or toggling magisk hide on off seems to work everytime and after that I pass safetynet again.

I'm on clean install of sultans LOS-Rom
[Magisk] Kiid:
Could you, if you have time, build it and upload it please? Not keen on downgrading to Beta or v12 since the problem persists in those versions as well. I've had a look at the build guide to maybe build it myself and have absolutely no clue what it means
[Magisk] kantjer:
There is one now ;)
[Magisk] JKL397:
Hey thanks a lot now i downloaded Magisk 13.0(c4377ed) and it's working :D
[Magisk] Didgeridoohan:
I don't use either LOS or Substratum, so I'm just throwing out ideas. Could the CM13 theme engine be the culprit, maybe?

No need. There's an unofficial snapshot available now.
[Magisk] theking_smen:
encountered the same problem as you on custom kernel... but magisk works fine when i flashed everything back to stock....
[Magisk] otyg:
For Xiaomi Redmi note 3 (kenzo) / possibly other Xiaomi devices - Magisk build "bdbb3c6" (170713) fixes the frozen MI boot issue

you will either build it yourself or check the unofficial build-bots for the latest snapshot.

I haven't tested other features yet, but appears rooted and working, boots.
[Magisk] 5uGun:
Any users trying Magisk v13.1 on Yu Yureka ??
[Magisk] Didgeridoohan:
A quick search for "Yureka" in the thread shows an amazing number of 2 posts about that device, both almost a year old. So I guess you're going to be the first to give it a go and report back if it works or not.

Make sure to have a backup of your device before starting...
[Magisk] pavan3999:
can you please provide link for that
[Magisk] premjeeth:
I'm on Stock kernel and hydrogen os.
[Magisk] Paschfire:
You could have easily used the search function for "Unofficial v13 Magisk" , though I will share you the thread link.

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
[Magisk] hugo-spice:
I flashed the uninstaller, as i don't have the clean boot.img. And i really don't want to reflash the entire rom again (i just finished moving my apps and debloating).
[Magisk] Varun.Shanbhag:
No debug log
[Magisk] pavan3999:
safetynet is not pass in the latest magisk snapshot
[Magisk] Baconat0r:
v13.1 Battery drain

I've been experiencing some battery drain with the latest version. Android OS uses a lot more power than normally. Tried reinstalling Magisk multiple times (using the uninstaller zip), but it the battery drain persists.

I can't post an URL yet, so here's the pastebin URL for the logcat: pastebin[dot]com/PxvUa7xr

This line seems to be repeated way too many times.

dup2 failed with 9: Bad file descriptor

The Magisk log doesn't seem to contain any errors.

My device info:

OnePlus 3

OxygenOS 4.1.6 (Android 7.1.1)

Magisk 13.1

Magisk Manager 5.0.4

TWRP 3.0.4-1

Any suggestions on how to fix the battery drain?
[Magisk] cygery:
Thanks. Do you think this issue will be worked on/fixed in Magisk/MagiskSU? I had a short glimpse at some MagiskSU commits. However, as you said, there's been a lot of work and I'm not familiar enough with the code and couldn't spot any related bugs.
[Magisk] dlnraja:
Hello sir with the 13.1 , how to fake the Samsung Knox 0x0 to use Samsung pay ???

Best regards.
[Magisk] LOCKhart:
Flash magisk 13.1 thru twrp. Same Happened to me
[Magisk] danmaman:
Nothing to do with magisk...

On my 3T you can see ... Android os is 1%
[Magisk] Baconat0r:
I think it actually is related to Magisk. The battery drains only occur when Magisk 13.1 is installed. When I roll back to Magisk 12.0, the drains disappear and Android OS stops consuming battery excessively. I've tested this multiple times.
[Magisk] DarkGenesis:
Up

Up
[Magisk] Borbingo Boy:
Busybox is still mentioned in the latest version of Magisk Manager, yet in the changelog it says it is removed. Is it just a leftover? Is it safe to flash busybox like normal?
[Magisk] Alexx5:
I just installed Magisk 13.1 on my Galaxy Tab S2 10.5, and it appears to be working but there is a major problem:

Whenever I attempt to do anything at all that required root, the device simply reboots. :confused:

I can grant root access to apps no problem, but upon performing the action that required root the device immediately reboots instead. I've previously used Magisk 12.0 and never had this problem. Is this a known issue?
[Magisk] gewe:
I tried again, flashing the uninstaller, wipe cache/dalvik, reboot, reboot into twrp, flash Magisk v13.1, wipe cache/dalvik, reboot.

Magisk Manager v5 still reports that Magisk is not installed, not rooted, and there is a notification that Magisk v13.1 update is available.

Attached is recovery.log.
[Magisk] DodoGTA:
Try to disable Magisk Hide
[Magisk] quebec1:
I installed magisk 13.1 on my phone. I have a custom rom miui 8 stable v3 (cm base). Now when I open magiskmanager and I try a control safetynet I see this. (attack image).

It's ok?

Sorry for my engliah