yashsingh1/xdaforums huggingface dataset:
[Magisk] Pa-Jo:
Hi guys,

I'm tottaly dissapointed what Magisk v13 doing on my device (Xiaomi Mi5s Plus - xiaomi.eu Developer ROM Android 7).

Without Magisk:

3x success and CTS fail (picture 1)

With Magisk:

Fail (picture 2)

I have enabled MagiskHide + Core only mode without modules.
[Magisk] Setialpha:
When do people finally understand that

a) this is a beta

b) different devices behave differently

? What works for you, does NOT need to work for everyone else.

Plus all those 'bug reports' in 'not werk' style, guyz, come to senses, provide logs. If you don't know how to: there are plenty of how-tos here on XDA.

If you don't want to, stay aside until the official release, this thread is starting to get out of hand.

All the useful information gets burried by useless 'me, too' or 'here werkz' posts. Causing more and more 'can't find info xyz' posts, because you need to dig through all that redundancy.

Not to mention all this people who act like topjohnwu owes them something (lol).

Let's call this RTDSoD™ (reciprocal thread death spiral of doom™).
[Magisk] Artim_96:
https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431/page45

Try that one.

But it might be possible that the beta is too buggy. That was the case for me so either it only showed an empty modules list or just bootloop when flashed through TWRP. So if you have problems, go back to v12
[Magisk] WeWa2013:
Works whit Huawei Mate 9 too?
[Magisk] doomscooter:
I already try but still fail. Tia
[Magisk] iHack13:
fyi you need a reboot. Also I am on latest build 17.06.

flash latest zip + root addon + magisk 13 in recovery with same settings as mentioned and it should work like on mine.
[Magisk] doomscooter:
It mean in twrp

Flash last zip rom xiaomi and then flash magisk 13 then reboot?

Whats its mean root addon?
[Magisk] iHack13:
Sorry. I thought you were on Lineage OS.
[Magisk] doomscooter:
im on xiaomi eu 7.6.15

Problem fix in twrp 3.1.1-0 with Magisk 12

- uninstall magisk 13

- install magisk 12

- reboot

- open magisk +modul (universal safetynet)

- reboot

- open magisk and all green collor safetynet

But still fail in Latest Magisk 13
[Magisk] voetbalremco:
Latest beta zip fails on my device, while Magisk V12 installs just fine.
[Magisk] Hugo Libanori:
Moto g 2015

Good morning, I tried to install magisk on my device but I did not succeed. At the time of error flash. I'm updated with twrp. Does anyone know why?

I installed the rom stock 3 days ago and I am without root, pure system without modification.
[Magisk] z4ckit:
beta 13 (96f8efc)

ViPER4Android doesn't work
[Magisk] krasCGQ:
It's working for me...

Dirty flash from v12
[Magisk] doomscooter:
Dirty flash without flash magisk uninstaller?

EDIT :

I try dirty flash from 12 to 13. SN fail.
[Magisk] krasCGQ:
Yeah, along with all modules...
[Magisk] otonieru:
With beta v13, safetynet can pass,

But if anyone notice, app that listed in magiskhide will have slower opening time.
[Magisk] fatspirit:
Anyone who have 96f8efc build installed, what is md5 checksum corresponding zip has?
[Magisk] jenslody:
No real information, no logs, no error message.

If flashing fails with "Error 1", you might try my repackaged zip (with older install-scripts): https://xdaforums.com/showpost.php?p=72704270
[Magisk] Viggen66:
Tried both Magisk 12 and 13 beta on an Android TV with Lollipop, root works, but every time I reboot the device, it says apps are being optimized, and is a long way until full boot, besides of that, is a very good root method, really don't know why this happens on boot.
[Magisk] Artim_96:
ecb947c01bb21c423819db4cfa74a7b9

---------- Post added at 03:01 PM ---------- Previous post was at 03:01 PM ----------

...logs, logs, logs. We are not psychic.
[Magisk] Viggen66:
How do you do logs on boot?
[Magisk] Artim_96:
You can make logs of the flashing.

For bootup log you need a computer connected via adb (and debugging enabled in dev options).

Before the reboot (e.g. before booting from TWRP to system), enter

adb -d logcat

in the command prompt of your computer, the -d should let it wait with logging till your device reboots
[Magisk] jusztin:
Android Pay no longer works, since Google has updated the safetynet detection, clean install, LG G3
[Magisk] mdxdave:
Seqr Tap&Pay doesn't work with Magisk Hide, i'm using the newest beta v13 (96f8efc).

Any fix? ?
[Magisk] Artim_96:
https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431/page47

Try that one

---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------

If you pass SN it uses some other detection methods. And there will be no support for those in the near future, if any is even possible
[Magisk] amitabh15:
Safety net passes on my g3 with lineage os nougat.
[Magisk] amitabh15:
See screen
[Magisk] Frosthaxx:
I appreciate that.there's too many articles to follow and posts i wouldn't have known about that without guidance.this is the first phone ive had that uses magisk.just located this beta thread.not new to the modifying scene.just this particular thing.got a lg stylo 2 plus metropcs.before i was giving help on lg f6 and the htc one sv by boost.even the knowledgeable though need help time to time.worlds expanding.again much praise
[Magisk] cloudx720:
Does latest magisk beta work with Dolby atmos?
[Magisk] storm119:
Working great here (bacon with newly compiled AOSiP 7.1.2 rom) with latest beta Magisk v13.0 (96f8efc)...previously i had Magisk v12.0 installed and all settings from previous Magisk + superuser are intact (nice!) and here what i did...

1- Boot to recovery (Wipe dalvik/system/cache)

2- Flash rom + gapps + my mods + custom kernel + Magisk v.13.0

3- Wipe again dalvik/cache

4- reboot to system

Thx [MENTION=4470081]topjohnwu[/MENTION] :good:
[Magisk] milocj:
Safetynet pass Nexus6 PureNexus 7.1.2 v r17 BL4ACB1RD kernel v2.2.2 all modules deactivated

Last build beta zip and magisk installer 5.0.2

With all modules safetynet not works

Send from my Nexus 6
[Magisk] valeriogerva:
[BETA][2017.6.16] Magisk v13.0 (96f8efc)

Choose only app in superuser access
[Magisk] Nodens:
/deleted. Wrong thread. Blame my 500 tabs :p
[Magisk] milocj:
Thanks It works perfect, tnx again mate!

Enviado desde mi Nexus 6 mediante Tapatalk
[Magisk] JJohnson1988:
Is your SELinux set to Permissive? If so, that's why V4A is working.
[Magisk] vsot13:
Yes, it does.
[Magisk] nlight84:
Error 1, tried another's fix on that. It's due to the language was set to German. No chance even on stock rom, 5.0.1 HTC m7(can't even covert apps to system). Viper rom works fine, but even with un-root Pokemon GO won't run. A nice guy had put up his own fix and used that with no luck. Have an Z3 Compact with unlocked bootloader, will try that too. Another question, any recommendations for stable Sony roms? Thanks in advance and all the people making MAGISK work!

Btw, should I switch default language to US?
[Magisk] swieder711:
Tried the default v13 and got ERROR: 1.

Tried v2 and installed with no errors.

Thanks!
[Magisk] nlight84:
I'll try that one, are you on stock rom or another one?
[Magisk] leo.riv:
[MENTION=4470081]topjohnwu[/MENTION]

! Magisk image mount failed......

Updater process ended with error: 1

error installing zip file
[Magisk] fatspirit:
See page 130.
[Magisk] Tesla:
How about searching for Error 1???????

There just might be a solution in the thread.

Error 1

Can't pass safetynet
[Magisk] leo.riv:
Thanks
[Magisk] swieder711:
Phone is Moto Pure X running a custom ROM, TruePureXMM 2.8.2
[Magisk] Codebucket:
Hey topjohnwu,

First of all, thank you very much for spending so much hours and effort into this project, it's nice to have such a nice platform for modules for different Android devices.

I am currently working on my Magisk FolderMount module, but noticed during testing on v13 that folders mounted with "mount -o bind" are not working anymore, while on v12 were working fine. Could you please help me or look into that issue? I already tried to change namespace seperation to global and rebooted, but it didn't fixed that either :(

Tested on:

Xiaomi Redmi Note 3

ViperOS 2.0, Android 7.1.2

P.S. I can give you logs later if you need some.

Greetings,

David (Codebucket)
[Magisk] lollyjay:
Er, please post as attachment...
[Magisk] foosion:
I was getting Error 1 trying to flash 96f8efc, so I tried flashing this. It rooted properly, but did not install the manager. I extracted magisk.apk from the zip and installed it normally. The v13 manager confirmed I was rooted with v13. Alas, it failed both safetynet checks. I reflashed v12 (after flashing boot.img and unistalling v13 manager), reinstalled manager v12 and now I pass safety net.

Nexus 5, stock latest MM.

I hope this is the appropriate thread. If not, apologies.
[Magisk] swieder711:
Tried the default v13 and got ERROR: 1. Tried v2 and installed with no errors.

Phone is Moto Pure X running a custom ROM, TruePureXMM 2.8.2.

SafetyNet fails. Tried the Universal Fix.

I have Xposed SDK23 running as a Magisk module which appears to be the reason that SafeNet is failing. If its a choice of running Xposed or passing SafetyNet, I am going to choose Xposed for now.

Does the group think that we will ever be able to run Xposed and pass SafetyNet or will Magisk replace Xposed at some point?
[Magisk] zulu99:
done in the original post
[Magisk] zeft64:
[MENTION=4470081]topjohnwu[/MENTION] bro do you think you could add the option to hide magisk on the app drawer? Tbh its the only thing that super su has over this at the moment
[Magisk] Kapiljhajhria:
Most launcher can do this already. Custom roms do this by hiding it from launcher as well. Change the launcher on such custom rom and u will see supersu icon.
[Magisk] Link_of_Hyrule:
Anyone had the "Failed to load cards" problem with their Google Now Card feed? I'm trying to figure out if it's Magisk causing it or something else.
[Magisk] ketwi15:
I'm getting stuck here at the constructing environment part for about 10 mins when flashing and it's not going past that.
[Magisk] ridobe:
You likely just need to clear data/cache on the Google app.
[Magisk] Klena:
Hey Guys,

Does anybody know how to restart magiskhide in Terminal? I flashed the new v13 and I get Basic integrety false and CTS profile mismatch. With my Mi5 I am on cpMIUI based on latest Developer Rom 7.6.15 with Android 7.0. The normal terminal command which works under V12 does not. He does not find the folder/file.

In the hidelist under /magisk/.core is just an entry with "com.google.android.gms.unstable" and nothing more.

Thanks guys.
[Magisk] ROTORGAMES:
Hi!

I have 12 version installed by manager, if i try to install the beta via ZIP i have this error

View attachment recovery.log

Note 2 Lineage os 14.1 lastest supersu, and no busybox

thanks!
[Magisk] Link_of_Hyrule:
Yeah I've done that and it fixes it but it keeps happening so just was trying to figure out if it's the new Magisk causing it or something else.
[Magisk] Spiricore:
Absolutely brilliant work! I haven't had much time to test, but v13 is a huge improvement in boot times! My only issue was the flashing process took over an hour (I fell asleep after that). When I woke up and booted normally I was pleasantly surprised.

Edit to attach log file.
[Magisk] Artim_96:
... It shouldn't take that long. Better go to /cache/recovery and get the last_log (rename it to .log or .txt for upload) going that flashing it was the last time you where in TWRP. Maybe someone can make out an error that caused that extremely long flashing. It shouldn't take longer than a minute and the bootup afterwards but more than 5 even on slow devices
[Magisk] KaMyKaSii:
[MENTION=1558651]sofir786[/MENTION], [MENTION=4507636]edzamber[/MENTION] this also applies to you. Thank you

Maybe it's the same problem that Chainfire quoted with SuperSU, since Magisk also creates a file that works as a partition. When possible you could go to TWRP, backup your boot.img, rename the /data/magisk.img file to /data/magisk.img.bak (if there is a magisk-something-merge.img do the same) , Follow the Chainfire tutorial and then install Magisk again? If the installation is fast as it should be, create an issue on github. To restore your functional installation of Magisk should only restore the backup of patched boot.img, delete new files created in /data and rename again the files cited for the original name

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post70985800
[Magisk] _litz:
*sigh* ... I'm getting nothing but fail out of this on a Nexus 9. This device is fully updated, to the June 2017 code (which, incidentally, included an update to the bootloader).

doesn't install right, doesn't install magisk manager, can't install modules (they seem like they install, you reboot, no module), just flat out fails in almost every aspect.

The only thing that doesn't fail is logging. There are ZERO errors, everything look s 100% normal (and yes, this is comparing to other devices where things are working correctly).

Something is blocking magisk from being able to modify it's /magisk partition, so it can't write any updates, install the modules, etc etc.

It is, sadly, just basically a complete fail.

Edit: I can MANUALLY flash modules in TWP, and those work. Cannot install anything from Magisk Manager.

also, Safetynet fails.
[Magisk] Nodens:
It has been reported before but on my Samsung Galaxy S6 Edge+ (928F) it takes 3+ hours to complete installation (on stock Nougat)

Log attached.
[Magisk] :
Oneplus X

Resurrection Remix 7.1.2

Modules:

Arise compatability module

Osmosis BusyBox

Emojione.

Everything works fine, but have to do a double reboot after installing new module. Safetynet passes with these modules
[Magisk] ZeOnEscofet:
HUAWEI P9 LITE VNSL31C432B380

http://imgur.com/a/nUyA3

Nice job
[Magisk] Nodens:
Thanks for this. This is actually correct , I just verified it and perhaps it should be put as a workaround in the OP.

It used to take anywhere from 2 to 4 hours to finish installation on my S6 Edge+.

Also you don't need to do anything complicated, you don't even need adb.

Just boot TWRP, got to Advanced-> Terminal and "mount -o bind /dev/urandom /dev/random" and then just install the beta.

This should work for everyone that has the very slow installation issue on TWRP.

For the technically inclined all this workaround does is bind /dev/urandom to /dev/random so anything that tries to read /dev/random accesses /dev/urandom instead.

The difference between the two is in their behavior. /dev/random will block and wait for entropy data when the entropy pool is empty so that the "quality" of randomness

is high. This is important for cryptography etc etc. /dev/urandom on the other hand will not block.

This is obviously a bug in TWRP and I will report it shortly (although it's most likely that Chainfire has done so already).

Meanwhile Magisk should probably default in using /dev/urandom in the installer since as far as I understand, there is no need for high quality entropy in its use case.

I will open a Magisk issue about this shortly.
[Magisk] shadavis08:
My voice services for Google and for my messaging app don't work very well. Is there anything you can do to look at this. I'll gladly send you a log or something. Not sure how to though.

LG V20 - NATF 5.0 - Magisk 13
[Magisk] demonoidmaster:
Any Modules?
[Magisk] shadavis08:
No just NATF with werewolf and newest magisk 13

LG V20 - NATF 5.0 - Magisk 13
[Magisk] LPW00:
What does it mean when safetynet check says "the respond is invalid" I never saw that before.
[Magisk] shadavis08:
Opps

LG V20 - NATF 5.0 - Magisk 13
[Magisk] LPW00:
I am in the magisk beta 13 Thread
[Magisk] zeft64:
1) I don't like using custom launchers 2)..... What ROM do you know of that does this without nova launcher
[Magisk] shadavis08:
My apologies I thought I was in the NATF thread. Geesh duh

LG V20 - NATF 5.0 - Magisk 13
[Magisk] rignfool:
You do realize viper isn't working on that setup right?
[Magisk] JaylanPHNX:
I was getting failed SN (both parts) on my Nexus 9, but after flashing the universal SN fix module, I'm also getting "the response is invalid."
[Magisk] auky:
It is working. It's just not processing.

Please share what did you do.
[Magisk] DEVILOPS 007:
This should be discussed in the appropriate thread and for processing problems removing deep buffer has often solved processing issues for me when I used to use that sound mod.
[Magisk] rignfool:
Processing=working...

Stone Cold guess... Deep buffering... Use the magisk module to remove it
[Magisk] otaconremo:
try playing some music and minimize it. then open again the status.

AFAIK, it won't process unless there's nothing to process.
[Magisk] pkdon123:
ON AEX 4.3, lots of apps FC when enable Magisk Hide in version 13, please check the issue, Thanks :)
[Magisk] yochananmarqos:
A ROM with Nova Launcher built-in. :laugh:

Seriously though, most ROM's come with either Launcher3, Google Now Launcher or Pixel Launcher. None of which can hide apps from the drawer.
[Magisk] _litz:
after spending way, far, too much time this weekend on things, been able to come up with a few fixes ...

On my moto x pure (running latest available stock), finally --- I think --- licked the persistent failure of magiskmanager (and therefore loss of SU services) ... installed Memory Lock (available in Play Store, also is on XDA), and locked Magisk Manager. This nifty little app changes an application's priority, making it less likely for the OS task killer to 'clean' it up. Seems to be effective with MM.

On the nexus 9, there's all kinds of broken stuff going on in the installer ... it's just flat out failing to install/config stuff correctly on a fresh magisk install ... stuff it's doing :

1) failing to install the magiskmanager apk

2) failing to setup any of the default systemless ghostings (e.g. hosts file, etc)

3) failing to setup any of the default RESETPROP settings (e.g. persist.magisk.hide and persist.magisk.root)

Was able to get magiskhide running by manually doing the appropriate RESETPROP commands, and was able to work around the missing systemless host mappings by installing the adblock module.
[Magisk] Rom:
Because the launchers that you mentioned are not an advanced launchers.

About stocks launchers, certains have this options, not all.

About advanced launchers, i speack about Nova, Apex and other similar launchers.
[Magisk] Aimphetamin:
From Nubia Z11 6gb+64gb on RR newest build...

Are these infos helpful?

if not, obviously to L8

x)
[Magisk] Nos_20:
I'm struggling to pass safety net on my Oneplus one.

I am running the latest aicp nightly. I flashed the ROM, then the Magisk uninstaller followed by the latest Magisk v13 beta.

It fails to pass the safety net. Any tips on getting the green ticks instead of red crosses ??!
[Magisk] krasCGQ:
Nah, I'm running enforcing SELinux and using V4A module provided by [MENTION=5357345]ahrion[/MENTION].
[Magisk] ThisWasATriumph:
Make sure you have no other SU apps installed/enabled, then try using Magisk Hide on Google Play Store and Google Play Services.
[Magisk] Nos_20:
I don't have any other root apps installed Magisk used to be included in the ROM I use.

I had not used Magisk hide on those, have just aelected them and rebooted and tried again, unfortunately safety net still fails.....
[Magisk] p34rp34r:
With all the clutter in the thread, would it be useful to make a sort of "Possible Fixes to Common Issues" post?

Error 1 during installation of v13.0 (96f8efc)

Users who get Error 1 during installation of v13.0 (96f8efc), specifically those who get the following error in the recovery log:

ioctl LOOP_SET_FD failed: Device or resource busy

[MENTION=8340552]jenslody[/MENTION] has made a modified version of (96f8efc) that fixes the problem for many users. LINK HERE. This version uses an older updater-binary script that correctly identifies non-64-bit paths to install Magisk (afaik).
​

SafetyNet fails with v.13.0 (96f8efc)

@Deic has made a module that might solve the issue. LINK HERE. It should be noted that this doesn't fix every possible issue, since some modules like Xposed Framework will trigger SafetyNet no matter what you do. Try disabling all your modules, verify that SafetyNet passes, then one-by-one reactivate the modules to identify the culprit.
​

Viper4Android doesn't work (multiple causes)

Status: Abnormal

If you are using v.13.0 (96e8efc) and V4A installs but the Driver Status says "Status: Abnormal," user [MENTION=7836278]LazerL0rd[/MENTION] provided a solution HERE. Download the .txt file and place it in /magisk/.core/post-fs-data.d/, then change the '.txt' to '.sh'. Change the permissions to 0755.
​

Processing: No in apps like YouTube

This can be remedied in some devices by removing the deep_buffer in the various audio_policy and audio_effects system files. You can make a script to remove these lines yourself or use the Universal Deep_Buffer Remover [AUDMODLIB] module by [MENTION=5357345]ahrion[/MENTION] if you are already using his ViPER4Android FX 2.5.0.5 [AUDMODLIB] module (note that this is not the one found in the Magisk Manager modules repo!).
​

Installation of v.13.0 (96e8efc) takes hours!

According to many patient users, the installation will succeed, even if it takes hours. [MENTION=571197]Nodens[/MENTION] explains what the problem is, and a solution for it, in this informative post: LINK HERE.
​
[Magisk] CryonicCore:
Try this.

[MODULE][v1.10.1] Universal SafetyNet Fix | Bypass SafetyNet on trusted systems

https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431
[Magisk] slimdick:
It works. Stop provoking me.
[Magisk] Klena:
I have the same problem with my Mi5. Have installed the Universal Safetynet Fix but then the "response is invalid".

Any ideas? :confused:

And then Google Play Store does not open if I check it and the Framwork Services in MagiskHide.
[Magisk] Nos_20:
Thanks for the link....

Installed the module via Magisk.... Safety net still not passed.... ??
[Magisk] slimdick:
https://xdaforums.com/showpost.php?p=72719455&postcount=471
[Magisk] CryonicCore:
Alright. Well I see some weird stuff going on there. Try uninstalling magisk then use custom recovery and install version 12 and not 13 and try the the fix again.
[Magisk] jusztin:
installed clean a new Nougat , ViperOs 7.1.2, SN passes now, but Magisk can no longer hide SEQR:(
[Magisk] Klena:
V12 is working. Bad that V13 is not ;)
[Magisk] Fentadroid:
Cannot install on LG G3 with Fulmics 7.5 ROM (Android 6 based).

- Mounting /system(ro), /cache /data
- Device platform: arm
- Constructing enviroment
- Creating /data/magisk.img
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Download/Magisk-v13.0(96f8efc).zip'

I guess it's ROM-related but i don't know what to do.

ROM is with Magisk 12 on board. If i uninstall it and try to install 13 beta, that is the error.

Once removed v 12, i'm not able to install it again.
[Magisk] Nos_20:
Safety net has passed after flashing the uninstaller and flashing V12 in twrp.
[Magisk] otonieru:
Did you put it in magisk hide ?

But v13 indeed has problem hiding stuff. The loading time is much slower

But this is beta after all, so nothing to blame :)

It's good that we still can pass SN.
[Magisk] demonoidmaster:
Why are you using not only the uninstaller but also installing v13 beta Magisk on a modified version of v12 that came IN your custom rom? The problem isn't the beta or the uninstaller, only thing left is logically your rom, hopefully you'd understand why on your own. Reflash your rom and stick to the custom v12 your rom uses

Tl;dr don't use the Uninstaller or install Magisk on a modified baked in rom Magisk.
[Magisk] Rom:
Have you edit your boot img file ?

I don't remember me if xpirt change the boot image of the stock ROM to make his final ROM.

And just for information, with an custom ROM (so custom bumped kernel), you don't have this problem because the official Magisk build doesn't support yet default LG boot image, maybe in the futur, i don't know.