yashsingh1/xdaforums huggingface dataset:
[Magisk] bobonit:
Out of my 2 phones, the upgrade was successful on my HTC U11. However, on my HTC One M8, not so lucky. It was previously running this modified beta version "Magisk-v13.0(96f8efc)_dev_random_busybox_var_path.zip" and everything was fine. But when I tried to install 13.1, I get the Not Installed/No Root issue. I have tried:

Clearing Data on the Magisk Manager

Booting into twrp and run Uninstaller

Reboot

Boot into twrp and install Magisk 3.1

I have also tried uninstalling Magisk Manager and extracting the APK from Magisk 3.1 zip and installing it. No change. I've attached the recovery log and screenshots of Magisk Manager. I have no option for saving a Magisk Log.
[Magisk] JpegXguy:
Magisk v13.1 does not work on EMUI 4.03. Device is in my signature. I tried dirty flash, clean flash, fresh install. Most beta versions worked.

IT works fine on a custom ROM such as ResurrectionRemix.
[Magisk] Viggen66:
I know there's an option to disable upgrade notification, but is there a way for magisk 12 not to check for updates? I don't have any problem with version 12, sometimes is better to stay with what works.
[Magisk] Alvarote1998:
In Huawei P8 Lite:

Magisk v12 => Works

Magisk v13 (54e6a79) => Not work

Magisk v13 (c4377ed) => Works

Magisk v13.1 => Not work
[Magisk] Viggen66:
Gonna stick with Magisk 12, works for both my Android phone and gadget
[Magisk] pavan3999:
Getting this when i install magisk v13.1 in my redmi 3s
[Magisk] eXtremeDevil:
I'm trying to use Magisk 13.1 + SuperSU 2.82 SR1.

Stock boot, flash SuperSU, then Magisk, error -> Magisk says that boot image has been modified (I guess by SuperSU).

Is it only happening to me? Is there a workaround for this? Please help!
[Magisk] DodoGTA:
Partial Magisk SuperSU support is in progress
[Magisk] piero.17.:
Same problem with me. The 12.0 version is perfect. With upgrade to 13.1 root loss
[Magisk] eried1:
After I uninstalled Magisk I tried to restore a full TWRP-image I made a couple of days ago. For some reason the phone is still bootlooping after a restart. Doesn't look good. Just as if Magisk was updated without me taking any action at all.

Will clear Dalvik ART/Cache and Cache to see if that solves it.

Edit: Nope didn't work. Guess the last resort would be to go back to stock, reflash Magisk and then restore the nandroid.
[Magisk] eXtremeDevil:
So is it official that Magisk 13.1 does NOT work with SuperSU??
[Magisk] Didgeridoohan:
Yes.

https://xdaforums.com/showpost.php?p=72587983&postcount=22
[Magisk] GCalzo:
I bet that before upgrading Magisk from v12.0 to v13.1 one must first upgrade Manager v4 to Manager v5... :(

I just upgraded my Moto G2 "stock rom + Open GApps" and after the reboot I have lost the root... I'll try from TWRP to manually install v13.1

If the manager must be upgraded to v5 before upgrading to v13.1, I suggest to let it more clearly noted! :)

Addendum:

installing v13.1 from TWRP didn't reactivate "root"

installing currente manager v5.0.4 didn't solved and now after an "update check" lasted many seconds it reports

Magisk version updated: v13.1

Magisk not installed

not rooted

I'll try the latest uninstall script and then a re-install... :(
[Magisk] gozzaa:
Thanks, the reboot after uninstall did the trick
[Magisk] gewe:
Boot image location not auto detected

Hello,

I would like to upgrade to v13.1. Magisk Manager is showing the update. It is also showing "Cannot auto detect" as the boot image location.

Do I need to select the proper boot image location in order to successfully upgrade? If so, how can I find out which one of the 46 cryptic names I should select?

Phone is a Moto X Play, stock 6.0 ROM (apart from being rooted).

I currently have Magisk version 12.0 installed, and Magisk Manager version 4.3.3.
[Magisk] moquiwa:
I'm using Moto G 2013 (XT1033 - Dual SIM) with AEXT v4.3

I had the v12 with no issues, but SafetyNet wasn't working, then, I got the update notification for the v13.1..

So here is what I did:

01) Update via APP (Magisk Manager) to v13.1

02) Reboot

03) Twitter and Google apps stopped working but Safetynet worked

04) Reboot to TWRP

05) Flash the Uninstaller

06) Reboot

07) Reboot to TWRP

08) Clean cache and dalvik

09) Flash the v13.1

10) Clean cache and dalvik

11) Reboot

12) Twitter and Google apps stopped working but Safetynet worked

13) Check the "Use only CORE" on Magisk

14) Twitter and Google are working again, but no Safetynet

I saw that some guy had the same problem, but it was something with the WebView.. I think it's the same, but he said that he only fixed it by reinstalling the ROM..

Any suggestions to fix this without have to clean install EVERYTHING again???
[Magisk] ForSquirel:
I never had the manager installed at all (Magisk was installed before the play store fiasco) so updated to Manager 5.0.4 (I think) and then tried to upgrade to v13. Nothing works. Even uninstalling EVERYTHING and installing from scratch will not work. It's most likely a bug somewhere that will get sorted.
[Magisk] eXtremeDevil:
I thought it was only for the beta. Reverting to 12.0 then. Thanks very much for the info.

Is there a 12.1 version? I thought there was but I can't find it now, did I dreamt it?
[Magisk] dubstepturtle:
Temporary fixed i discovered. Disable both the systemless add blocker and magisk hide then restart. After rebooting, reenable both features to pass the safetynet check and no more force closing. Works with my rn3p aex 4.3 build radon 5.1
[Magisk] amageek:
The stable version of Magisk v13 didn't work on P8 Lite... No matter how many times I flash it, the flashing would be successful but still, the root access had problems. The previous version (v. 12) was working great...
[Magisk] D1stRU3T0R:
Third p8lite user having problem... So everyone have :)
[Magisk] vassagout:
can you confirm if Viper4Android works on 13.1?
[Magisk] GCalzo:
Same here with Motorola Moto G2 "stock + OpenGApps", after the uninstall script I have even restored to original boot image and then installed v13.1. Nothing changed and the manager still reporst "no root".

I'm going to revert to v12.0!

Addendum: sigh... the uninstall script Magisk-uninstaller-20170711 is not even able to find the backup that was just done a few minutes ago!!! :( :( :( I have to re-re-image the boot manually...
[Magisk] amageek:
Third P8 Lite users?
[Magisk] D1stRU3T0R:
I saw 3 comments related to P8lite, where we said that it's not working. It's not only you.
[Magisk] Redhawk2000:
What worked for me on LeEco Pro 3 running AICP 7.1.2 upgrading from Magisk 12:

1. Chose download/install via Magisk manager (the 4.3? version).

2. When it asked to reboot I said "later"

3. Downloaded and installed the new Magisk manager via the XDA labs app

4. Rebooted into TWRP and flashed the Magisk 13.1 zip that had been downloaded by Magisk manager

5. Rebooted phone

Everything works fine for me.
[Magisk] danilo_scala:
stranger, version 12 install and uninstall normal in recovery, version 13 no. xperia z5 premium android 7.1.1

mount -o bind '/data/media/0' '/sdcard' process ended with error: 255
[Magisk] GCalzo:
...I had to revert also the Manager loosing my prefs and module... :eek:
[Magisk] EXV:
Everything works fine regarding Magisk. However I now get force closes on a lot of my apps. But root works, safetynet passes,etc. Just some apps won't open.
[Magisk] Fry-kun:
success report:

OnePlus 3, Lineage 14

* upgraded the manager via xda app

* upgraded magisk via manager

* rebooted

== everything works great
[Magisk] patster98:
Device: op3

ROM: OOS Open beta 19

Modules: none

modifications: none

Hi guys, uninstalled magisk APK , flashee magisk uninstaller and flashee stock boot ImG.. rebooted, installled magisk 5.0.4 APK, wiped caches flashed magisk v13.1 wiped caches, rebooted... Igual cantidad retrieve magisk logs nor from the app neither from /cache folder, already tried with Core only enabled and disabled, root set to only apps and disabled/enabled magisk hide...

PROBLEM: when checking foro safetynet ir says check success but everything else states false (image attached), sometimes i even get am "invalid response" sign.. any idea?
[Magisk] eried1:
I'm also searching for a possible solution to this.

Since Magisk was notified of the update I'm not able to boot my phone. It keeps rebooting.

UPDATE. Looks like I solved it by uninstalling Magisk and then reinstalling it (same version). For the time being at least. It doesn't seem to play well with Lenovo P2.
[Magisk] Didgeridoohan:
Try disabling MagiskHide, reboot and see if they stop force closing.
[Magisk] kost7:
With the new version, all apps relying on Webview crashed (Google app, AquaMail) and the relevant selection in developers options was blank. No matter what I did, Magisk could not see that Google Webview or Chrome were installed. I then installed Chrome beta, and everything works fine.

It seems that the new version cannot detect the already installed Webview-capable apps. I guess I could try to uninstall and reinstall Webview, but as it is a system app, I tried the other way around. Everything else is working fine. Nexus 6p, Nitrogen ROM.
[Magisk] dari-woka:
I have the same problem, cannot use chrome or feedly.

Galaxy S7

edit: ok, magiskhide is breaking it.

I disabled it, rebooted, enabled it and everything is working, magiskhide and the apps
[Magisk] mg_jishad:
For me latest beta v13 had problem with google app.. V 13.1 has noooooo problem
[Magisk] Rh7m3Pl4ay:
Google webview implemented as I flashed it in aroma installer
[Magisk] piero.17.:
I after countless attempts, I opted back to version 12.0. Nothing to do with twrp and various changes. At least satefynet works in impeccable manner. On version 13.1 I did not even get root. Maybe we expect news from the developer. In version 12.1 so everything is simple
[Magisk] kost7:
If you have nothing showing under webview implementation in developers options, try installing chrome beta. It worked for me.
[Magisk] mg_jishad:
Everything works fine for me... :laugh::victory::laugh:

I had problems only with last beta.. it force closes google apps, and also device got laggy... Now with v13.1 no problems..
[Magisk] JERW28:
[MENTION=3217629]gozzaa[/MENTION] [MENTION=3504301]hugo-spice[/MENTION] [MENTION=7840989]Recycool[/MENTION]

To help help topjohnwu solve the Magisk 13.1 bootloop issue, you might consider flashing Magisk 13.1-170711 from here

As far as I can tell, it has the same code as the official release, but with the debug file called "magisk_debug.log" from topjohnwu's official betas still included, located in /data. This file will help him determine why your device is not booting.

My suggestion is to do these steps:

1. Reboot to TWRP and make a backup

2. Flash clean boot.img

3. Flash the file above

4. Wipe delvik and cache

5. Reboot system

6. Wait a few minutes

7. When device does not boot, go back into twrp and go to advanced> file manager

8. Browse to /data

9. select and copy the file magisk_debug.log and post it with device info.

P.S. I hope [MENTION=2226076]stangri[/MENTION] and [MENTION=289782]kanjer[/MENTION] continue to include the debug files, from the official code, to their builds for release versions of Magisk so that it can continue to help debug issues.
[Magisk] eavandijk83:
I'm not the only one with magisk hide problems on 13.1 so I'll keep it short. It only works after disabling and re-enabling it after boot. I'm running vanir ROM 7.1.2 on a HTC A9.

Here' the log

--------- beginning of main I( 418: 418) Magisk v13.1(1310) daemon started I( 418: 420) ** post-fs mode running --------- beginning of system I( 418: 437) ** post-fs-data mode running I( 418: 437) * Mounting /data/magisk.img I( 418: 437) * Running post-fs-data.d scripts I( 418: 437) post-fs-data.d: exec [00000000apps2sd.sh] I( 418: 437) * Loading modules E( 418: 437) umount /magisk failed with 16: Device or resource busy I( 418: 544) ** late_start service mode running I( 418: 544) * Running service.d scripts I( 418: 544) * Running module service scripts --------- beginning of crash I( 418: 8502) * Starting MagiskHide I( 418: 8502) hide_utils: Hiding sensitive props I( 418: 8502) hide_list: [com.google.android.gms.unstable] I( 418: 8502) proc_monitor: init ns=mnt:[4026531840] I( 418: 8502) proc_monitor: zygote ns=mnt:[4026535774] zygote64 ns=mnt:[4026535413] I( 418: 8502) proc_monitor: com.google.android.gms.unstable (PID=8531 ns=mnt:[4026535887]) I( 8536: 8536) hide_daemon: Permissive detected, hide the state I( 8536: 8536) hide_utils: Re-linking /sbin
[Magisk] moquiwa:
Same here..

Apps like Twitter and Google..

Please, someone help??
[Magisk] eavandijk83:
Oh, btw.. it's easy to complain but I appreciate your work and knowlegde in this project. Keep up the good work.
[Magisk] moquiwa:
I did that too, it worked

But Safetynet stoped working for me, is it working there without magisk hide??
[Magisk] mg_jishad:
Anyone do flash uninstaller and delete magisk manager app and then flash beta Magisk-v13.0(96f8efc).zip then check for updates if v13.1 available download and install. Waiting for someone 's reply.
[Magisk] Didgeridoohan:
That log is in the official code since June 7... It's not something specific for the unofficial snapshots.

Do NOT post your log like that... It's completely unreadable. Attach it as a file or use a service like Pastebin.
[Magisk] moquiwa:
If the phone reboots with MagiskHide enabled, the problem returns..

You have to disable, reboot, and enable again...

Any other solution?
[Magisk] brambles1234:
I will keep this short - I am getting an error when trying to install 13.1 zip saying that I have a problem with the boot.img, it needs reflashing to stock, the thing is I am using a custom rom and I do not have stock.img can anyone point me in the right direction please>
[Magisk] Didgeridoohan:
Your ROM comes pre-rooted with SuperSU, right? Take a look in the ROM zip. If you're lucky they just flash the SuperSU zip at the end of the ROM flash and you can use the boot image from the zip.
[Magisk] m4570d0n:
So I was using Magisk v12.1/MM v4.x on my Oneplus One running LineageOS 14.1 and even though I could pass the SafetyNet check, Netflix does not show up in the Play Store anymore and if I go to the play store page for it on my computer it says I don't have any compatible devices. I just upgraded to Magisk v13.1/MM v5.0.4 and again, I can pass the SafetyNet check, but still can't install/upgrade Netflix through the Play Store. Anyone know if there is a way to fix this?
[Magisk] ante0:
If your rom comes in a zip, you probably have boot.img in it. Flash that in TWRP.

If it's a pre-rooted boot image you'll get problems though.
[Magisk] brambles1234:
Yes sorry, I should have said - it does have SuperSU installed- the ROM is xXx_NoLimits_5.9 for my G900F. I will take a look in the zip file, if I can find it. Thanks
[Magisk] Poenster:
I've updated magisk 12 to 13.1 on my samsung s8. When the message came that my phone would reboot, this didnt happen. I've rebooted several times, and in the manager it says I'm properly rooted on v13. However no magisk installed and cts profile mismatch.

Log from magisk manager:

--------- beginning of main

I( 3123: 3125) ** post-fs mode running

--------- beginning of system

I( 3123: 3231) ** post-fs-data mode running

I( 3123: 3231) * Mounting /data/magisk.img

I( 3123: 3231) * Running post-fs-data.d scripts

I( 3123: 3355) ** late_start service mode running

I( 3123: 3355) * Running service.d scripts

E( 3123:10783) sqlite3_exec: no such table: settings

E( 3123:12057) sqlite3_exec: no such table: settings

E( 3123:12827) sqlite3_exec: no such table: settings

E( 3123:20817) sqlite3_exec: no such table: settings

Edit: solved by uninstall and install
[Magisk] Didgeridoohan:
FYI: there is an unpatched, stock image in the zip. xXx -> kernel -> stock -> G900F.
[Magisk] :
Or perhaps you can extract the boot.img from your original firmware. I keep a copy on my phone in case i need to flash it. I had to use it once after flashing unsu script.

Last custom rom i used (gromv6), i used the full cleanup in supersu and chose restore boot image but not recovery. Then magisk would patch. Did it last on v12 with my g900w8.
[Magisk] waau:
Some feedback, after flashing Magisk 13.1 all the CPU cores stay online even though there's no actual load, this behavior does not occur on 12.0
[Magisk] brambles1234:
I have just downloaded the zip and flashed the stock boot.img (thanks for the heads up on location), through flashify - I have flashed Magisk v13.1 successfully however, it does not pass SafetyNet, do you think this is because I still have SuperSU from custom rom ?
[Magisk] Didgeridoohan:
If you still have the SuperSU app installed that might be it, yes. There might be other things causing SafetyNet to not pass as well... Troubleshooting guide here: https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] brambles1234:
To be fair it's never passed SafetyNet but I only use it for Halifax App and I have just tried registering the banking app again after failing at root check since update and it works! - I will take that any day. Thanks a lot for your help today Didgeridoohan
[Magisk] viktor92:
Upgraded from v13 to v13.1 and is working perfect, pass SN in all tries :good::good:
[Magisk] DEVILOPS 007:
On magisk 13.1 magisk manager says magisk manager has stopped or magisk manager keeps stopping. It only happens when selecting the superuser tab to view my superuser requests. Any ideas? I'd rather not clear the data as I don't want to go through granting root permissions for all my apps again. Also, root does still work but I just can't view that tab. I have no substratum overlays installed and didn't have this problem on the beta. If a log would help then in be more happy to but need advice on which type of log. Any help is appreciated. Thank you:)
[Magisk] bobonit:
[MENTION=4667597]Didgeridoohan[/MENTION] I posted my recovery.log, but its already buried several pages back. Let me drop it here again.

Out of my 2 phones, the upgrade was successful on my HTC U11. However, on my HTC One M8, not so lucky. It was previously running this modified beta version "Magisk-v13.0(96f8efc)_dev_random_busybox_var_path.zip" and everything was fine. But when I tried to install 13.1, I get the Not Installed/No Root issue. I have tried:

Clearing Data on the Magisk Manager

Booting into twrp and run Uninstaller

Reboot

Boot into twrp and install Magisk 3.1

I have also tried uninstalling Magisk Manager and extracting the APK from Magisk 3.1 zip and installing it. No change. I've attached the recovery log and screenshot of Magisk Manager. I have no option for saving a Magisk Log.
[Magisk] mcnamaragio:
I can't find list of supported devices, is A5 2016 (A510F) supported ?
[Magisk] Didgeridoohan:
You'll have to clear data...

There's been a couple of posts in this thread today... :p 300+ since the update dropped. :laugh: It's quite easy for a post to get lost in that.

Your recovery log doesn't show much, except for a "cat: xwrite: Broken pipe" at the end. I have no idea if it's significant. In TWRP, can you check if the magisk.img is in /data and if you flash the zip a second time, does the output mention a stock boot image or a Magisk patched one?

---------- Post added at 21:35 ---------- Previous post was at 21:33 ----------

There's no list of supported devices. I've no idea what device that is, but I'm gonna make an educated guess and say it's a Samsung. Some Samsung devices have had issues installing Magisk in the past. Flash the zip and see what happens... Make sure to have a backup.
[Magisk] Asumos:
Magisk Manager 5.0.4 - OnePlus 5/OOS 4.5.5

when prompted to download new version if would "download" then nothing would happen. i eventually uninstalled and installed manually and everything worked fine there.

other then that everything else seems to be running great. Thx a load
[Magisk] android_smater:
Hi i installed magisk 13.1 over 12 it install successfully but after reboot it say no root in magsik manager already updated manager to still facing problen

Redmi note 3

It working well with magisk 12
[Magisk] mg_jishad:
I too did the same.. Worked for me too.. :highfive::laugh:
[Magisk] T4rd:
Thanks. Can you link to the uninstaller zip, please? I don't see it mentioned in OP or in the few other Magisk threads I've tried. I have the zip installers in my MagiskManager folder still and tried flashing 13.1 in TWRP and it still didn't install, so I need the uninstaller zip I guess.
[Magisk] Didgeridoohan:
It's in the release thread. Both as an attachment and a link.
[Magisk] jamy015:
After upgrading from v12 to v13.1 on my Nexus 5X, Magisk Hide doesn't seem to work if I turn on Core Only Mode. When I look at the Magisk log with Core Only Mode enabled, Hide doesn't even start (i.e. the line * Starting MagiskHide is not in the log when Core Only Mode is enabled).
[Magisk] Aid777:
I've updated to 13.1 from beta on LG G6 H870 and everything worked fine, no problems (so far!). Magisk was updated within the app
[Magisk] T4rd:
Ahh, missed that thread somehow.

Uninstall/reinstall fixed it. Thanks again!
[Magisk] zxcv741:
Posted, the 170650 is with core only off and 173815 is with core only on.

I can't make my phone to get Logcat log.

Though I don't think those logs i posted show anything reliable.

However, I'm pretty positive that magiskhide simply doesn't work on my phone, because I downloaded rootchecker, added it to hiding, and it stills detects root no problem.
[Magisk] hridhi:
Updated to 13.0 or something and boom all apps started to crash ;-; has to revert back to 12.0
[Magisk] rush77neo:
Trouble with Moto G4

I have a unlocked Moto G4 that is currently running 6.0.1 MM. The bootloader is unlocked and I have twrp installed. I have no installed any other root or a custom ROM on the phone since I have gotten it and have tried to install Magisk with no success. I have made a backup of my stock rom and everything also.

So, when I try to install it I have done it two ways. The first being using my stock kernel, as was suggested in another thread. That did not work as Magisk was not installed though Twrp gave me no errors. The second way was installing the elementalX kernel on my Moto G4 before flashing Magisk which, once again, passed in Twrp but in the Magisk Manager said that nothing was installed or rooted.

What am I doing wrong? Everything is as stock as it could be minus the unlocked bootloader and Twrp.
[Magisk] daddylonglegs:
OK thank you so much for replying. I have the new SystemUIGoogle.apk that I "rebuilt". I have a google pixel so for whatever reason, the file is SystemUIGoogle.apk. The only modification I made was one tiny line in one XML file).

I did not see a magisk_mount folder in my cache folder. Is it supposed to be there? Anyway, I created it. I pasted the modified SystemUIGoogle.apk in my newly-created /cache/magisk_mount/system/priv-app/SystemUIGoogle/ folder

I rebooted my phone and as soon as it starts up I get a "SystemUI has stopped" error and can't do anything on my phone. I am not sure what the reason is, though. My ROM is a stock Google Pixel ROM but I am (obviously) rooted with my bootloader unlocked. I am not sure if that matters.

Did I do all the steps right? Do the folders I made or the SystemUIGoogle.apk file need to have certain permissions changed?

Thank you and [MENTION=4667597]Didgeridoohan[/MENTION] again so much for taking your time to help me.
[Magisk] dovahkiin4756:
Thanks for the tip. My phone wouldn't pass the SafetyNet test after the update. Had to disable "core only mode".

Don't know if this is intended behavior or not.
[Magisk] Captain_Throwback:
You have a Pixel, which is an unsupported device. In that case, I can't really help you besides suggesting that you try creating a Magisk module and use the version of Magisk ported for that specific device. I'm not sure how/if cache mounts work on that build or not, but seems like either they don't or the issue is the odex file.
[Magisk] 4RK4N:
magisk v13.1 with magisk manager 5.0.4 passing safetynet and also bypass sparkasse app root detection if selected at magiskhide. awesome work [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] lokkiyo:
Same problem here.

KENZO under LOS 13