yashsingh1/xdaforums huggingface dataset:
[Magisk] Naudiz:
I also updated to 13.1 and already wish I didn't :(

All my modules are gone, including xposed. If I try to reinstall them from repo, Magisk Manager refuses to do so and when I try to install the ZIPs from recovery, log says everything is okay, but after reboot they still don't show up.
[Magisk] unknown:
Logs :D

---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------

Try to uninstaller old version before flash v13.1

If bug not fixed , logs plz :D
[Magisk] Viggen66:
I guess the problem of Magisk 13.1 is not the code that is introduced on the kernel, but the way it reassembles again the kernel, from my experience when it stays on splash logo, it always related with assembly again the kernel
[Magisk] unknown:
Logs plz :D
[Magisk] hugo-spice:
Can you walk me through to get those logs? I have TWRP as recovery, at first i tried updating magisk through the app, as it didn't worked (bootloop) i flashed the uninstaller, then proceeded to flashing the 13.1. Also bootloop. Then i reflashed the uninstaller, booted normally, uninstalled the magisk manager app, reflashed the 13.1 zip, and still bootloop. If i knew what kind of logs you're looking for i could paste it here or somewhere else.
[Magisk] Krustak:
I don't have any had to recover from nandroid backup
[Magisk] Didgeridoohan:
Logs, please.

The module probably have to be updated for Magisk v13.1.

No issues at all on my OP3T on OOS 4.1.6 and Franco Kernel r25. Flashed v13.1 in TWRP over the last beta.

Do you have Manager v5.0.4 installed? If not, install it manually (you'll find the apk in the Magisk zip or in the release thread).

Logs, please.

Once again, there are boatloads of users with issues, but hardly any logs posted. Logs people, please!

Installation issues

If there are issues when installing in recovery, provide a recovery log. In TWRP this log can be saved after the failed installation by going to Advanced - Copy log.

Boot loop

If your device doesn't boot. Reboot to recovery and see if there is a file called magisk_debug.log in /data. Also, a recovery log might be useful (see above).

Edit: Another option is to see if you can get a logcat from boot.

Other issues

Always provide at least a Magisk log. It's saved through the Manager or can be pulled from /cache in recovery. A logcat and/or recovery log might also be useful.

When posting logs DO NOT paste them into your post. Attach as a file to the post or use a service like Pastebin.
[Magisk] xsycox:
Redmi Note 3 Pro International Edition (Kate model)

NX ROM (Android Marshmallow)

Radon 5.1 kernel

Magisk 12

Magisk Manager 4.33

I saw an update and installed 13.1 and the Manager app 5.04.

Magisk Manager app then crashed all the time by itself, not only when starting it.

I uninstalled Magisk Manager and I went back to recovery and flashed Magisk 12.

Boom ... phone is stuck at boot logo (MI screen).

I had to reflash NX ROM, Gapps, Radon kernel and Magisk 11.1, then 12 from beginning.

Phone is working again now with Magisk 12 and Manager app 4.33.

I will wait for 13.1 and Manager app issues to be fixed. :) ... or try again with uninstaller script first to have everything clean.
[Magisk] hugo-spice:
sorry, no magisk_debug.log in /data for me... :( Also, i don't know if it's related, but i can't see my adoptable storage using this recovery.
[Magisk] darzur:
Hi,

As 13.1 don't have integrated Busybox I've tried to install osmOsis Busybox 1.26.2 (found here) but it says that it's not Magisk module.

How can I install busybox then? I'd like to have it installed systemlessly.
[Magisk] Didgeridoohan:
Did you try clearing data for the Manager?

It's not a Magisk module... It just installs as one.

It's a unified installer and will install as a Magisk module if Magisk is detected. Flash in recovery.
[Magisk] djb77:
[MENTION=4470081]topjohnwu[/MENTION]

I'm noticing a problem with bundling magisk 13.1 in my ROM (which uses the AROMA installer)

With all the previous 13.0 betas it works without an issue, however the latest 13.1 release doesn't like it at all.
[Magisk] Pootch:
Does Magisk Hide work? Got several apps that do not run with root... It worked with v12, but doesnt with v13.1

Edit: cleared Data from Magisk Manager, and it works now.
[Magisk] Didgeridoohan:
It works.

If you've got issues, post logs (Magisk log).
[Magisk] young666:
It's working, thanks a lot :good:
[Magisk] mg_jishad:
Just a guess.. I had problem with latest beta v13 (c4377ed).. so i went back to v13(96f8efc) it works fine. Then i installed stable v13.1 works without any problem...

If You guys installed latest beta try by installing any other versions and flash v13.1. :D
[Magisk] adrenochrome25:
Xiaomi Redmi4X (santoni) / TWRP 3.0.3 / Android 6.0.1 MMB29M / MIUI 7.5.19 beta

v12 was ok (root&MagiskHide)

v13beta was only ok for root (MagiskHide never worked)

v13.1 get stuck on boot logo : adb report no root available, there's no /data/magisk_debug.log available in twrp filemanager

if there is any other file i can provide for investigation, just ask
[Magisk] shaggyskunk:
Simple question for a new user of Magisk - In Advanced settings there's Keep force encryption and keep dm-verity - I don't use encryption - But something tells me that I should put a checkmark in the Keep dm-verity box?

Sent by my SM-G930W8 From Down The Rabbit Hole ??
[Magisk] Didgeridoohan:
It depends... If you have dm-verity enabled it might cause your device not to boot (because it perceives your modifications as unauthorised and possibly dangerous). If you're unsure, I'd say leave it unchecked.
[Magisk] ~billie joe~:
i thought the codename is mido .. what made the difference. im also got 4x device but im using mido rom but it turn out fine.
[Magisk] mejobloggs:
I updated to 13.1 and now some of my apps crash on start.

How can I investigate the problem? Relay for Reddit, Adobe Acrobat both crash. Many work fine, but quite a few crash when I open them
[Magisk] shaggyskunk:
Thank you Sir ?

Sent by my SM-G930W8 From Down The Rabbit Hole ??
[Magisk] Didgeridoohan:
Logcat showing the crashes.
[Magisk] adrenochrome25:
"mido" is Redmi Note 4 qualcomm, you can check in the devices list tab, moreover in this version mido was already on Nougat when santoni was on Marshmallow
[Magisk] mejobloggs:
Thanks that's very interesting. Looks like any app that use Android WebView thing will crash.

Attached log with crash data
[Magisk] fatspirit:
I have hostname changer installed, that requires busybox to do its job. I've uninstalled magisk beta with latest magisk uninstaller, installed 13.1, and now hostname changer is working! How that's possible?
[Magisk] Rh7m3Pl4ay:
Device OnePlus 2, rom Aosp extended 4.4 build- new magisk 13.1 breaks Android Google web view and apps crash because of it. Here is log. Same problem as above.
[Magisk] NeoBeum:
This is probably going to cause problems for Sony devices when it comes to Recovery Restore
[Magisk] Didgeridoohan:
If you take a look in developer options, what does it say about WebView?
[Magisk] gozzaa:
Having the same issue on kenzo

Did you clean flash? I can't get it to work with just reflash everything :/

Also other apps are crashing too
[Magisk] Captain_Throwback:
Why not check the changelog to see what was added/changed? That's what it's for...

I'm pretty sure 11.1 was pre MagiskSU, but a look at the changelog will tell you for sure.
[Magisk] T4rd:
I've tried to install 13.1 a few times through Magisk Manager and every time it downloads, prompts me to reboot, but Magisk isn't installed upon reboot. No errors, messages, or indications of issues other than it not installing. Don't know what version I was on before and I haven't had to mess with Magisk in a while, so not sure what to do.

Running Pure Nexus ROM with Magisk on Nexus 6P, that's it (no Xposed or anything).

Any help is appreciated.
[Magisk] Hassanator:
Moto g5 plus support Magisk 13.1

I got the Magisk 13.1 update and it keeps displaying errors and not installing. Currently I'm running Magisk 13.0 (96f8efc) and its the only version that works for me. I've tried flashing the new update too and that didn't work either I think it stops at the boot.img stage and it displays an error. Before flashing I always uninstall Magisk with the uninstaller and reboot into recovery, flash novariety zip and flash Magisk zip. My device isn't in the unsupported list so I would love some help to get it to work and if its not supported yet I'll just wait. Thank you.
[Magisk] Didgeridoohan:
Try uninstalling and reinstalling from TWRP.
[Magisk] mejobloggs:
Only thing is webview implementation, and if I click it pops up blank.

I tried reinstalling webview but didn't help
[Magisk] Didgeridoohan:
What's the error?

---------- Post added at 14:39 ---------- Previous post was at 14:37 ----------

Ok... Try disabling MagiskHide and reboot to see if that changes anything.
[Magisk] mejobloggs:
Yes that worked! Thank you
[Magisk] Hassanator:
I've attached the error screenshot[IMG="Error screenshot"]https://goo.gl/photos/VvmXea4xg4fsAaAA7[/IMG]
[Magisk] daddylonglegs:
I feel like this is such a stupid question but how do I add a file to the /system directory with Magisk? I know I am not supposed to mess with the /system folder but I finally figured out how to modify the systemui.apk and I simply wanted to put it back there. Thanks in advance.
[Magisk] Didgeridoohan:
Could you do a test... Run this in a terminal emulator and see if that causes your issue:

su
resetprop ro.build.type user

If nothing happens, put the following inside a file, place it in /magisk/.core/post-fs-data.d, give it permission 755 and reboot:

#!/system/bin/sh
resetprop ro.build.type user

If that causes your issue we know the reason. If it doesn't cause the issue, could you try replacing "ro.build.type user" with "ro.build.tags release-keys" and redo the process? And if that doesn't work, use "ro.build.selinux 0" instead and try it one last time.

You can easily revert the changes made by deleting the file in post-fs-data.d and reboot again.
[Magisk] Hassanator:
so the error says the following ''UPDATE PROCESS ENDED WITH ERROR: 1

Error installing zip file '/sdcard/Download/Magisk-v13.1(1).zip'
[Magisk] Didgeridoohan:
This is what, the third time you ask this, no? The answer, every time, has been: Make a Magisk Module... :p

You need to provide the recovery log from right after the failed installation.
[Magisk] eried1:
I believe that is what caused my phone not to boot some weeks ago. I did several changes though but I'm quite sure that was it.

I think "if it ain't broken, don't fix it" certainly applies here.
[Magisk] shamsud:
I am using apps2sd to mount and pair folder from sdcard to internal. It was working with magisk 12 but with magisk 13.1 it does not work. tried clean flash also.

In apps2sd app it shows everything ok but in reality it doesn't mount any folder. Hope u understood my problem.
[Magisk] Hassanator:
What is the recovery log is that basically all the lines after the failed installation?
[Magisk] lambroslnk:
Hello guys i have been having a problem with Magisk 13 installation, after clean flashing the latest magisk.zip the Magisk Manager force closes when opened permanently.

I have a Xiaomi Redmi 3s using unofficial LineageOS 13 ROM (Fedosis los), which with magisk 12 used to work fine. I was using losSU before magisk, but i first uninstalled it in recovery then rebooted then clean flashed magisk 13 but still with no success. I cleared magisk manager data (which was zero anyways) didn't help, or multiple restarts.

Any suggestions guys? Thanks :)
[Magisk] Didgeridoohan:
If you're using TWRP, after the installation, go to Advanced - Copy log. It'll be saved to your internal storage. Attach that file to a post.
[Magisk] daddylonglegs:
Sorry. In all fairness the question is a bit different this time because I figured out how to modify and rebuild the APK. I was just confused because I thought I possibly could just push a file to /system by another means, maybe in TWRP or using an ADB command or something.

I have a bit of a reading comprehension problem since childhood and trying to figure out how to make an entire magisk module just to place a single file in the /system folder is kind of much for me. But if it is literally the only way, I guess I will have no other choice.
[Magisk] Didgeridoohan:
Yes, of course you can do it, both with TWRP and ADB. But that's not the Magisk way... :laugh: It's much safer to do it with Magisk, because if you've messed anything up you can just delete the module in TWRP (after flashing the Mount Magisk script) and everything will be back to normal.
[Magisk] Gerard15799:
I installed v13.1 and I got this result...now I know there's a module that can fix that..but I'm curious why some phones like nexus phones,Xiaomi etc can pass safety net without using any safety net helper module.... I'm using an Asus Zenfone 2 laser (Z00L) running with RR 5.8.3. Attach here are also a log.
[Magisk] Didgeridoohan:
No worries... I know what that can be like.

If you're having to much issues, send me the file and I'll take a look at making a module for you.
[Magisk] Captain_Throwback:
It's the only way to make the modification systemlessly, which I assume is your goal. The template is relatively easy to use. In fact, you may not even have to use it.

You can put the updated file in /cache/magisk_mount/system/priv-app/SystemUI/ and Magisk will automagiskally replace it for you. Though that may not work if the ROM you're using is odex and your APK is deodex (though it might still work). Otherwise, a full Magisk module that replaces the SystemUI folder is your only solution.

So try the cachemount way, and if that doesn't work, you can take up [MENTION=4667597]Didgeridoohan[/MENTION] on his offer to help you create a Magisk module using the new module template.
[Magisk] tytydraco:
Hello, I just upgraded to the latest 13.1 and the device is looping at the boot logo (before the animation). It fails after flashing via TWRP. It fails after uninstalling and reinstalling Magisk entirely. Reverting back to 12 boots.

Here's our logcat.

EDIT: no magisk log found.
[Magisk] Didgeridoohan:
If you can pass Basic integrity but not CTS profile it means that Magisk is working as it should, but your device and/or ROM causes it to not be recognised by Google as a trusted device. The solution can be to spoof your devices fingerprint with the one from a trusted device/ROM (that's what the Universal SafetyNet Fix module does, among other things). You could try to find the fingerprint props from your device's stock ROM and use the resetprop tool to change the one for your current ROM.
[Magisk] daddylonglegs:
That is so incredibly nice of you. Just send you my systemui.apk?

By the way, a lot of people would find the module very useful! It would remove the need for xposed/gravitybox for a lot of people, which would be a blessing since it does not work on Nougat!
[Magisk] xsycox:
Yes, I tried this, too.

I will go for another run tonight, but do a Nandroid backup before that, just in case ...
[Magisk] Gerard15799:
Where do I get that resetprop tool and will there be any side effects...and oh yeah regarding the universal safety net fix module...you know there's a version which I can change the build fingerprint in that module...the problem is that it's a zip file so how do I change it?,
[Magisk] romskidd:
Wait, does that mean you can't install Xposed even if you use magisk, because pokemon go will see xposed and not work ? no?
[Magisk] JudgeDread11:
Search and you will find there is a while dedicated tread for magisk and Android pay.
[Magisk] cire27rn:
If i do unmount, am i able to use the spoofing app on xposed? Coz what i understand when unmounting is not rooted?
[Magisk] JudgeDread11:
Do you manually place the files in the magisk directory?

Because then the image file will never get adjusted.

The module template will adjust the image size automatically.

I'm not sure if this will solve your problem, but it's worth looking into if you haven't yet.
[Magisk] AvisAile:
I try to flash, but I have strange problem : I can't change the brightness of my screen ... When I unsinstall magisk, it's ok ...

Thanks for your help :)
[Magisk] Artim_96:
Then provide some logs like mentioned in the OP, maybe there can be something found why so the dev can fix it when he has some time.

And please provide some information about your device (which, which ROM...)

---------- Post added at 11:00 AM ---------- Previous post was at 10:53 AM ----------

Yes and no. If it can find XPosed you have to deactivate it and reboot in order to use it. When it only uses the SafetyNet API and has no custom ways to detect XPosed it should run with XPosed enabled since the API won't detect it (yet). But you can check that on your own, there is an app called SafetyNet helper, which shows what an app would detect using the API.

When PoGo still won't work you'll need to wait for a module that is able to remove the detection.
[Magisk] AvisAile:
I have a motorola g 2015 x1541 with aosp rom android 7.0 (http://xdaforums.com/2015-moto-g/orig-development/rom-android-source-project-t3457061)

And how send the log ?

Thanks
[Magisk] Artim_96:
Attach it or upload it to a could and post the links
[Magisk] Wlkchnbndgr:
Sorry, i am new to magisk. I habe installed all

How do i unmound root? Just doing the toggel dosent work.
[Magisk] romskidd:
Ahh.. ok thank you.

Toggle the "Root toggle" maybe?
[Magisk] dabenaute:
Doesn't work for me...

Impossible to uncheck the root toggle...i also tried to unroot via supersu setting but the same prob impossible to unroot...any idea...

Envoyé de mon SM-N9300 en utilisant Tapatalk
[Magisk] AvisAile:
http://www.partage-facile.com/OI1TC3K99M/bugreport_nrd90s_2016_09_11_12_14_23.zip.html

:)

Edit : sorry : link is in frensh
[Magisk] Blueblob:
Yes you are right, unmount = unroot

Where is my Pure Nexus ROM ? ?
[Magisk] Hakem:
Maybe you should use phh's SuperUser instead if supersu.

Verstuurd vanaf mijn SM-G935F met Tapatalk
[Magisk] Artim_96:
... Are you really running SuperSU?

What does the OP state on that topic? Unmounting is not possible with SuperSU. Use phh's SuperUser
[Magisk] Wlkchnbndgr:
When i use the toggle its switching back.
[Magisk] chris9000:
Flashed my Nexus 6P to factory 7.0, flashed a custom kernel, didn't root. Flash Magisk and Magisk manager. I can move the root toggle to the left, but it just moves right back to the right side. Android Pay doesn't work and I still can't get the latest version of Pokemon Go.

Did I miss a step?

EDIT: Also forgot to add I flashed phh's SuperUser.
[Magisk] cire27rn:
So how can i cheat the game if its unrooted?? I thought that magisk can cheat PoGo app through xposed
[Magisk] Wlkchnbndgr:
Same here. I didnt get the point, were things go wrong. :crying:
[Magisk] Artim_96:
...I can just hope the answer is "you can't", lazy asses:rolleyes:
[Magisk] Hassanator:
Just attached the recovery log
[Magisk] danmaman:
[MENTION=4470081]topjohnwu[/MENTION]

You do a great job.. Buddy...

Flashed stable trough TWRP ... On opo 3t / Oos open beta 10

All modules working...SU working...:good:

Thanks
[Magisk] Didgeridoohan:
No worries. Try the suggestion by [MENTION=1162986]Captain_Throwback[/MENTION] first (I completely forgot about cache mounts) and if that doesn't work send me your edited file.
[Magisk] cfhsncb:
Anyone have 13.1 working on a Nexus 6? I did the upgrade, and it booted initially, but would only pass safetynet in Core mode. I then decided to try re-flashing 13.1 manually to see if it would fix it, and this caused me to get stuck at the boot animation. I then flashed the stock kernel back, followed by Franco, which worked just fine. Then I tried 13.1 again, and it gets stuck at the boot animation again. I then flashed the stock kernel again, then Franco (all good) then tried flashing 12.0 and it fails to boot again. Any suggestions?
[Magisk] eried1:
Did you upgrade the Magisk Manager to v5?

I have a general question about the app. When you click the "install & update" button, what is supposed to happen? It didn't look like it did anything. I couldn't tell if it was working in the background and was afraid I might have rebooted too early.

Might make another attempt of installing v13.1 tonight after a proper removal of all modules and then using Magisk uninstaller.
[Magisk] vykintazo:
Hello, i have this issue since i updated to v13 beta (after updating to v13.1 now, issue remains)

The problem is that if I try open Superuser panel Magisk Manager crashes every time... I have root, and I can accept/deny su requests, but cant manage them. Can anyone help me?

I have galaxy s5 klte running android 7.1.2 on Resurrection Remix rom
[Magisk] Ahmer Jamil Khan:
FIX!

Here's how I fixed it:

1. I cleared the data on the Magisk Manager app

2. Rebooted into TWRP and flashed the uninstaller

3. Rebooted the phone

4. Rebooted into TWRP and flashed 13.1

It works like a charm. I am experiencing some lag though, may be unrelated.
[Magisk] kantjer:
It should show a new menu with an install option.

After hinting install a toast message is shown indication the zip is being downloaded, when that is done you will get a reboot option.
[Magisk] InsaneNutter:
Just providing some feedback as i'm not sure if this is expected behavior or not, I've updated from Magisk 12 to 13.1 today on my OnePlus One.

On Magisk 12 I had Magisk's "Core Only Mode" enabled and could pass the safetynet check.

However when I upgraded to Magisk 13.1 both the ctsProfile and basicintegrity checks failed if Magisk Core Only Mode was enabled, however if core mode only is disabled then ctsProfile and basicintegrity both pass fine.

OnePlus One running Sultanxda's Unofficial CyanogenMod 13.0 rom
[Magisk] fliptechnologies:
thanks i`ll give this a whirl tomorrow, after several fails today trying to install 13.

the only thing i didnt try was using the uninstaller.
[Magisk] kgr:
Flash the zip from TWRP.

It works for a lot of people, as per other posts here.
[Magisk] Didgeridoohan:
The resetprop tool is a part of Magisk. More info here. And yes, you can edit the module to add your own fingerprint. Unpack the zip, edit the post-fs-data.sh file (the required lines are almost all the way at the bottom) and rezip.

For some reason the Magisk image can't be mounted... Unclear as to why.
[Magisk] kgr:
Here's the Magisk log. Be glad for anyones suggestions.
[Magisk] Gerard15799:
I can't find it tho the resetprop tool..haha.. sorry. I'm new to this..
[Magisk] rocky78:
[MENTION=4470081]topjohnwu[/MENTION]

is there a way to hide this one?
[Magisk] tanago:
No version after 12.0 is working for me

Attaching recovery & logcat logs.

Tried clearing cache, dalvik, factory reset. Flashing v13. 1, not working, flashing over it again, still not working.

su not found

Xperia X - drm, ric, dm-verity patched kernel
[Magisk] Hassanator:
Could you mention someone who could look into it? Would the developer see this on the thread? Is he on this often?
[Magisk] xsycox:
Yes, after the bootloop scenario described above, I did dirty-flash

my ROM, Gapps and kernel.

Do not worry, you can just uninstall the Magisk Manager app

and go into TWRP recovery and use the Magisk uninstaller zip

to remove it completeley. You can get this file in the main

thread.

Then you reboot into your Android device and reboot to TWRP

again and install/flash Magisk 12 and after that install an older

version of Magisk Manager app (like 4.33).

Magisk 13.1 seems to have a big problem with Android Webview

or whatever that thing is called, therefore a lot of apps crash

with the newest Magisk version.

I guess, the Magisk mastermind will sort this out soon. :)
[Magisk] mg_jishad:
I didn't upgrade magisk manager.. I flashed magisk beta v13 it automatically installed manager app... And today morning v13.1 came I downloaded and installed. It works.
[Magisk] DaRdamnDoG:
Not able to flash Magisk V13, be it through TWRP nor Magisk Manager downloaded via XDA. Tried again with MagiskSU (root) or NON root on Samsung Galaxy Note 4 Exynos Android 6.0
[Magisk] gordopa1:
Thanks [MENTION=4470081]topjohnwu[/MENTION] ! I've sent a donation your way. Transaction ID: 5E252729V0602172R