yashsingh1/xdaforums huggingface dataset:
[Magisk] vitekrus777:
Quite possible. There they came hard to the folder "system/lib64". And the library that the installer can not find is in my "vendor/lib64" folder.

Android 7.1.1, alps project.
[Magisk] topjohnwu:
You have to give me more logs!!!! Please check the OP for resetprop issues!

Thanks, many people got this issue and I'll check.
[Magisk] topjohnwu:
OK, so most people has got the CANNOT LINK EXECUTABLE bug, which is really weird because I used shared library very early before.

I bet it is caused by the fact that I used my binary to call several commands, and the LD_LIBRARY_PATH is propagated through the calling process.

I specified the LD_LIBRARY_PATH due to the fact that many custom recoveries has too much flaws, some even run 32-bit code on 64-bit machines.....

I'll try to overcome this issue.

But for the resetprop issue, please follow in the instructions in the OP!! Magisk logs are not enough for me to debug!

A lot of people reporting here does not provide enough info for me to fix issues, please read the OP and understand how to help the development.

Thanks
[Magisk] vitekrus777:
[MENTION=4470081]topjohnwu[/MENTION] Many thanks, we'll be looking forward to it.
[Magisk] djb77:
If you need some Samsung testers again like you did with v12 let me know, we can always start up another group like we did for the v12 testing
[Magisk] DodoGTA:
https://github.com/topjohnwu/Magisk...72a2c9327eb8c4a3a2ce71#commitcomment-22141876
[Magisk] Chinaboy5216:
Note 3 HLTE running Trader RRN 5.8.3 flawless install, root maintained, Safety net fails but i believe this is because of being in China
[Magisk] Deic:
Why do you need help? This is not for use as daily driver, this is only for report bugs with useful logs to get a stable release as soon as possible. Is the developer (topjohnwu) who need help, so if you want help him, then read the first post, if not want help uninstall and go to Magisk v12 that is the version to use as a normal user, is the official (stable) version.

Please STOP with these useless posts people...
[Magisk] mr-tical:
Hi

Do Magisk v13 also the same "Remove dm-verity, forceencrypt..." stuff as v12 by default?

I want try update stock 7.1.2 by OTA to O DP3 by Flashfire.

Anyone tried that way instead of flashing img's manually?
[Magisk] aLexzkter:
I'm having an issue with Wakelock detector, you're supposed to install it as a system app but when doing so it shows "An error occurred mounting system rw. Aborted"

I have two phones, only the one running LineageOS 7.1.2 has this problem, the second one is on LineageOS 7.1.1. I've seen other people complaining about this, all of whom have Magisk.
[Magisk] veez21:
Try making a module for it or, search for systemizer modules in the Magisk Manager to make it a system app. Making system modifications on a software whose purpose is to not do that doesn't make sense :eek:
[Magisk] aLexzkter:
Tried installing App Systemizer but it says "Processing zip file...installing..." and then Error during installation ! :eek::eek:

Fortunately on my Axon7 I can install such module...there is clearly something wrong. I even reflashed Magisk V13 zip but same issues.
[Magisk] DodoGTA:
Yes and I didn't try that way
[Magisk] veez21:
Try the Terminal App Systemizer (I'm not advertising :D). It's an alternative
[Magisk] aLexzkter:
I can't install any module... Will try flashing zip from TWRP.

Edit: nope, the module says you can't install from recovery...
[Magisk] mr-tical:
Well I tried and everything is OK in that way :)
[Magisk] veez21:
No, for every module, you need to install in recovery, imo. Try doing it
[Magisk] justjr:
I can install modules from Magisk app no problems, its not a matter of opinion, IMO. LOL

(I only use Systemless Hosts)
[Magisk] aLexzkter:
I tried flashing both modules in TWRP and both failed in the process... As I said before, App Systemizer states you are not supposed to flash from recovery anyway.
[Magisk] DodoGTA:
I'll look into this issue
[Magisk] ksmueller:
Missing Magisk Manger

Just flashed Magisk Beta: v13.0 (c4377ed) (code: 1308)

but can not find Magisk Manger. As it is bundled I expect it is installed with Magisk, but does not show up?

Is there a direct download?
[Magisk] Didgeridoohan:
Just extract it from the installation zip.

It'd be interesting of you could repeat the process and save a recovery log to see if there's anything in there as to why it didn't install the app. Attach that recovery log to a post in the thread.

Edit: A logcat from the boot and 20-30 seconds after the device has finished booting might show something as well
[Magisk] tdunham:
Please learn how to use the xda search feature, this has been brought up many many times.

The apk is included in the zip. Extract and sideload it if necessary.
[Magisk] Davehimself:
hi!

The survival script only works if you flash whole zip files. If you flash small incremental update the script will be ignored and you have to manually boot into recovery and flash magsik again after every update. Any idea how to change the addon.d script, so it will trigger with incremental updates too ?
[Magisk] kramer04:
Just try f7f4146 but I can't install module and safetynet doesn't work.

Samsung Note 3 N9005

ROM Resurrection Remix 5.8.2

Xenial kernel
[Magisk] HamsterHam:
SafetyNet still fails for me on a reboot. Needs a toggle.
[Magisk] GatorsUF:
I'm having this same issue, app crashes ever time I click #superuser. It also just spins continuously on the safetynet check. I ran the uninstaller and reinstalled with no luck.

Running: Nexus 6P - 7.1.2 N2G47W
[Magisk] yochananmarqos:
Clear the app data for Magisk Manager.
[Magisk] GatorsUF:
That fixed it thanks! Not sure why I didn't think of that... Safety net still just spins, but it appears that is a common issue.
[Magisk] DirkStorck:
Disable and enable Magisk hide... On my side it is working.
[Magisk] nathanchance:
I can see this is going to be a daily occurrence but I've made my peace with that lol.

Guys...

L O G S

O

G

S

Seriously, if you are reporting or having ANY issue, include a Magisk log and a logcat, simple as that. If your post doesn't have them, it's going to be removed. It really is just rude because you're expecting the developer to just know how to solve your issue without them. Furthermore, it wastes their time having to ask you to get one before looking into your issue. Just have the logs and everything up front.

I have a guide on how to properly create a bug report here. Leave a VERY detailed description about how to reproduce your issue and include those logs to have people look over. It is not your call to exclude a log from your post. Let topjohnwu be the deciding factor.

Also, remember, SafetyNet success or failure posts are off topic here and will also be removed. Please read this post and this other one to understand what is being expected out of you.

Thank you,

The Flash

Forum Moderator
[Magisk] jenslody:
The out of memory message is not an issue.

It happened, because the flash-script writes the new boot-image to the block-device holding it, followed by zeroes from /dev/zero until the device is full and writing stops.

Some roms (including mine) have a dd, that does not recognize the size of the device, but just stops because the device is full.

Writing zeroes after the image makes sure nothing is left from former images.

It should not happen any longer with the latest beta.
[Magisk] isimsizkullan:
I think our posts deleted, but thank you [MENTION=4507636]edzamber[/MENTION], it did the trick.
[Magisk] abacate123:
If you read the second post above yours, you'll know why.

:)
[Magisk] Retr0=:
Error 1

I can't install in Samsung Galaxy Tab 2 P3100, I get error 1 in TWRP(latest version), LineageOS 13.0 Official (nightly) Stock kernel, don't have any old version of Magisk and clean uninstallation of SuperSU...

I changed language on TWRP so sorry for some portuguese words, if you want I can translate it or made a new .log in english. Please fix this tool for this device, Thank you.

Log: https://pastebin.com/gGxK0pUE
[Magisk] nathanchance:
Did you try dirty flashing your ROM first?

I also make your link valid, thank you very much for the log :good:
[Magisk] demonoidmaster:
Survival script is only for rom updates, logically.....

But incremential updates should work just the same as any rom update zip. My guess is survival script only triggers if a certain action is performed when doing a rom update (mostly roms simply format /system and then flash the image to it, which is why opengapps and Magisk has a survival script to tmp copy important stuff elsewhere like google play services, playstore, etc for example and put it back in /system when the rom zip flash is finished)
[Magisk] Retr0=:
Hello, thank you so much to reply, its work now.

Flashed the ROM like an update after the end he alone flashed Magisk addon

after this I flashed Magisk v13.0

works fine and don't have any error in TWRP

and SafetyNet: ctsProfile: False, basicIntegrity: True

Thank you again and sorry my english.
[Magisk] Davehimself:
Yes, exactly! My thoughts are to extend the certain action, that triggers the script. obviously the certain action is missing when flashing just incremental updares, instead of the whole rom ZIP file. I'am using Mokee rom. Daily incremental updates OTA are a pretty nice feature, but become annoying if you have to download and flash the whole 600mb each day or boot into recovery and flash magisk again after incremental OTA update.
[Magisk] elex2000:
can you provide a link to previous version?
[Magisk] jusztin:
---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------

[/COLOR]

http://www.apkmonk.com/app/com.seamless.seqr/#previous
[Magisk] Poloasis:
Couldn't do without it. Great development. Donation sent. Keep up the good work. Tx
[Magisk] snickler:
All,

As posted in the OP:

[*] SafetyNet / CTS / XXX app won't work after enabling MagiskHide:

Unless you can specify how to improve MagiskHide, for example: what additional boot props to patch? What does the app detect? Or else

Please do NOT report ANYTHING related to these kind of issues!

Please re-read the last part over and over, before posting. Read before posting. Don't blindly post and wonder why your comment was deleted, before reading before you post.

That is all :).
[Magisk] demonoidmaster:
Back when i used to run Cyanogenmod (and tried LOS) there was this app on the play store called CyanDelta which did delta updates to your existing nightly zip of Cyanogenmod/LOS (now it even supports other roms) by patching it, neat feature

But the best feature of CyanDelta was that in it's settings you could add other zips to it's list of items to flash after CyanDelta finished flashing your update.

Edit: you could try out AutoFlasher on the Play Store, seems it's a standalone type of app that does what i was talking about
[Magisk] Davehimself:
That's a good workaround using AutoFlasher. Now I download the incremantal zip file with Mokee Update Center and use AutoFlasher after that to select the incremenatal zip and magisk zip together. Thanks for that :)

By the way, "CyanDelta" is now "Lineage Downloader". the old CyanDelta app doesn't work anymore. Lineage Downloader works great, but I it only supports LineageOS. I bought the pro version. You can even set an auto timer to download and flash your rom, so you never have to care about any updates again.
[Magisk] demonoidmaster:
CyanDelta still works, used it before for LOS nightlies, Lineage Downloader isn't made by the same person, besides i find it cluttered with features a normal person wouldn't use

And yeah I've used the pro version before, the whole "download this delta patch or full zip based on set number of star reviews" is meh, i don't like it, not many people would leave reviews which defeats the purpose of that feature
[Magisk] DodoGTA:
I built Magisk v13.0 beta again with the latest commits by [MENTION=4470081]topjohnwu[/MENTION] (It may fix magiskhide not properly starting on boot issues)

Source code: https://github.com/TheComputerGuy96/Magisk (branch better-32bit-support)

I've attached the Magisk installer and uninstaller to this post

Note: My Magisk installer uses Magisk Manager APK from [MENTION=4470081]topjohnwu[/MENTION]'s Magisk v13.0 latest official beta build (because I'm only running 32-bit version of Windows 10)

Note 2: My Magisk source only has better Magisk building support for 32-bit systems/OSs, and nothing else

Note 3: I'm a bit sorry for not posting this post in unofficial Magisk beta thread, but this Magisk v13.0 beta thread by [MENTION=4470081]topjohnwu[/MENTION] is more popular than that one

Fun fact: This day (July 7th, 2017) has quite a lot of 7s :D
[Magisk] LazerL0rd:
This is great :D I'll test if it has any issues ?
[Magisk] DEVILOPS 007:
It just says checking safetynet status for me and never actually says if it passes or not. I'm not sure if and which log would help with this though.
[Magisk] rocky78:
magisk crash log http://cloud.tapatalk.com/s/595fecf46cb4b/magisk_error_20170707_231733.log

hope that helps
[Magisk] iboyperson:
Initially after a reboot saftynet fails but after going into settings and turning Magisk Hide and Systemless Hosts off and on again the saftynet passes. Is this a bug or just a problem for me??
[Magisk] Paschfire:
https://xdaforums.com/showpost.php?p=72931842&postcount=2594
[Magisk] Hhunted:
Also installed the 777 [emoji3] version now. Mine does the same thing. I'm on a Sony Xperia [emoji769] Z5 running nougat 7.1.1
[Magisk] tanago:
Sadly, this isnt the case, after flashing c4377ed su & magiskmanager are missing again

If I install manually MM, it reports that magisk & root are not present.

Log attached. Still get that "xwrite: Broken pipe" (missing when I flash v12, which works for me)
[Magisk] ptn107:
Same here, even after a complete wipe and clean flash.

Moto X Pure 2015 XT1575

AICP 12.1 arm64 20170707

opengapps aroma 7.1 arm64 20170707

magisk 13 c4377ed
[Magisk] G4 Man2:
Thank you! For the past day or so I've been having this issue and I've been pulling out hair trying to figure out why it sometimes fails and sometimes doesn't. The settings toggling workaround fixes it for me so thanks :good:
[Magisk] LazerL0rd:
It might clear some crap and reset something.
[Magisk] LazerL0rd:
Basically it's a normal magisk log but at the start of where magisk hide should be it says.. process hide daemon error failed to initialise.

I've gone back two versions.
[Magisk] simon.gleinert:
Viper4Android port dont work for me on v.13beta..

I thinks its the post-fs-data.sh..

The path "/data/magisk/*" is not using on v13..

"/data/magisk/sepolicy-inject --live "allow mediaserver mediaserver_tmpfs file { read write execute }" \

"allow audioserver audioserver_tmpfs file { read write execute }" "

But how i can fix it?

Gesendet von meinem LG-K350 mit Tapatalk
[Magisk] Hhunted:
Thanks... That also solved my issue. Safetynet check passed as well.
[Magisk] Didgeridoohan:
Usually a good idea to take a look in the module's support thread:

https://xdaforums.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058/post72812054#post72812054
[Magisk] Emenaria:
Thank you, that worked!
[Magisk] krkhaha:
Where I can find uninstaller?
[Magisk] keval_juthani:
Use the uninstaller in the main thread to uninstall any verison of Magisk installation
[Magisk] sillycat98:
If this is ready known forgive me, I'm on the latest beta and root isn't winning and neither is magisk hide, weird thing is the log is completely empty. Not sure how to troubleshoot this one, going to roll back. Just thought it was strange.
[Magisk] Jrhotrod:
I had to do the same thing. Root not working on my Moto G5 Plus, forced to roll back. Never passed SafetyNet in the first place, so I've long gotten over that.
[Magisk] asusm930:
so this mean I cnat flash this magisk on 64 bit Nougat rom is it? thanks in advance
[Magisk] DodoGTA:
No, you can flash it
[Magisk] asusm930:
alright will report results regarding magiskhide problem

edit: still magiskhide problems
[Magisk] jenslody:
The broken pipe has the same cause, as the out of memory message.

It only happens, if the bootimage the script writes to is not a symbolic link, but a real device:

if [ -L "$BOOTIMAGE" ]; then
dd if=new-boot.img of="$BOOTIMAGE" bs=4096
else
cat new-boot.img /dev/zero | dd of="$BOOTIMAGE" bs=4096 >/dev/null 2>&1
fi

It's just one more error-message that should be redirected to /dev/null also (it's the one from concatening the new boot-image with /dev/null).

The output of dd is the same as before (no space left ...) but the user can not see it, because it's redirected to null-device.

As we can see here, it confuses the user, because it looks like an error, but is just how it works. I guess that's the cause fore hiding it, even if it would also hide real errors.

The device that holds the boot-image is larger than the image itself.

The new boot-image might be smaller than the old one and therefore there can be leftovers (more or less random bytes) coming after the newly written boot-image.

By concatening the new boot-image with /dev/null they will be overridden.

But this leads to an error message with some roms.

First the dd command stops with an error (out of memory), because the device is full, and as second the cat-command with the output piped to dd stops, because the pipe gets closed after dd stops.

And that's the error message you can still see in the log.

You can safely ignore it.

It's not the root of your problem.

If you don't get root after first boot, try it a second time, this works often, but not always, also try to clear MagiskManager data or remove MagiskManager before booting into recover to flash Magisk.

And after flashing Magisk it is always a good idea to wipe Dalvik/Art cache
[Magisk] tanago:
I have tried so many times that I gave up, cleaned all and still not working. Gonna stick to v12 for now, it install without any issues
[Magisk] jenslody:
I can tell you what always works for me:

Uninstall MagiskManager

Boot into recovery

uninstall Magisk with uninstaller

just to be sure flash a stock boot.img

flash Magisk (latest beta)

flash universal saftey net fix v2 beta 4 (https://xdaforums.com/showpost.php?p=72877684&postcount=681)

flash busybox from [MENTION=4544860]osm0sis[/MENTION] odds and ends thread (https://xdaforums.com/showthread.php?t=2239421)

flash other modules I need

wipe dalvik/art-cache

reboot

wait until MagiskManager is installed (might take some time)

everything works
[Magisk] simon.gleinert:
For me this way Not work coz /data partition is encrypted in Recovery..

For me magisk Install to /cacheif its boots its copy from cache to decrypted /data..

But this not work good..

After reboot i have /data/magisk.img /cache/magik.img and if i install moduls /data/merge-magik.img too

But only one can be mounted../data/magisk.img - only works if i delete /cache/magisk.img, /data/magisk.img and rename /data/magisk-merge.img > /data/magisk.img..

Thats a suck way..test it last night soo much..but no other way work :(
[Magisk] bomblader:
Result on Galaxy S5 (stock rom with boeffla kernel)

- root works

- safetynet works, however I have to toogle Magisk hide several times to get it working.

- if I press the "+" in modules tab, app crashes

Any idea how to fix the crash?
[Magisk] yochananmarqos:
Try clearing the app data for Magisk Manager.
[Magisk] bomblader:
Looks like it was crashing because I had no file manager installed. :silly:
[Magisk] Tanker Bob:
I'm running Magisk 13.0 (c4377ed) on a MotoX Pure 2015 with AICP 7.1.2, 7/6/17 build. Magisk passes the safety check. However, when I tried to use Android Pay today, it refused to work. I got a pop-up box that said something about Google could not verify my device or operating system, or something like that. I didn't have time to write it all down. I rechecked the safety check and it still passed. It looks like Google may have upped the ante again in bypass detection.
[Magisk] ketwi15:
Everytime I pass safety net, apps don't detect root so i guess root is gone. Here's a log. Galaxy S6 edge.
[Magisk] johnholley123:
Try enabling Magisk hide for play store and play services.
[Magisk] Ta3hi:
I tried to use magisk v13 with app version on 5.02 and it didn't work on the United arlines app on my phone when I opened the app and tried to play a movie on the plane and it said can't play w/ root. So I went and clicked on safety net check it wouldnt load and I tapped the screen and the app crashed. BTW no internet at the time and I had checked United app in magisk Manager
[Magisk] Aid777:
For me as well. On LG G6 H870. I un-rooted while it was working okay, then OTA, then re-rooted and it was not working, this 'fix' rectified the problem. Unless it stops again after a reboot. This is with version Magisk-v13.0(54e6a79)
[Magisk] kgr:
I just clean flashed my ROM today, along with the latest v13 beta (c4377ed), and Magisk Hide doesn't seem to be working on boot. I mean the toggle is on, but Hide isn't working. Apparently this is a resetprop issue, and I have attached the requested logs... I'd be glad for anyone's input on how to solve this.

Thanks!
[Magisk] Paschfire:
Very strange on v13(f63e2c6) Beta, Magisk hide enabled on boot also Magisk Safety-Net Check status was successful on first try.

After the fact upon reopening Magisk manager Safety-Net Check status failed, even after toggling Magisk Hide and Systemless Host, check status still remains to fail.

Device information in signature below.
[Magisk] murphyjasonc:
I have the problem with Magisk 13. Everything works with 12 though. Thought it was just me.
[Magisk] Tanker Bob:
Thanks for your suggestion. I had already hidden play store. Can't find play services in the list, but had already hidden Google Services Framework. I am now hiding com.google.android.gms.policy_auth and .gms.setup to see if that helps.
[Magisk] DodoGTA:
Did you install Magisk v12 or v13.0 beta?
[Magisk] ToriRobobo:
I'm new to this, sorry for the questions.

I just did a clean install of LineageOS and added Magisk 13.0 beta before the reboot. How do I turn on root now? Is there any special process I still have to go through now?

I'm in developer settings and Manage root accesses is grayed out. I don't see anything else root related.
[Magisk] DodoGTA:
Use Magisk Manager app for root management
[Magisk] ToriRobobo:
Oh it seems root is already on. I'm trying to download the apk from the v12.0 thread but it keeps saying the package is corrupt. What do I do?

Edit: Nevermind, it was already installed.
[Magisk] DodoGTA:
Magisk Manager v4.3.3 (found in Magisk v12.0 thread) is incompatible with Magisk v13.0 beta
[Magisk] DodoGTA:
https://xdaforums.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549