yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Ok... Magisk seems to crash straight away. Hm.

Does Magisk function otherwise? By that I mean modules and systemless hosts. What does the Manager report about the installed Magisk version and MagiskSU?

You could try uninstalling and reinstalling, to rule out any errors in the Magisk image or anything similar.
[Magisk] adhammagdy:
Everything is working.. but always get cts profile missmatch..

I found a temporary fix.. I disable and reenable magisk hide and safetynet passes straight away..

After restart it fails again until I disable and reenable magisk hide..

Magisk reports installed version correctly..

There could be remnants from magisk 12 still there.. I uninstalled 12 with uninstaller before installing 13 but found the settings of 12 still present in 13.. is there a way to cleanup 12 completely?

So it seems the problem is with magisk hide not starting successfully at boot

---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------

I did and it worked but the problem returns after reboot
[Magisk] Didgeridoohan:
Ah. You've got resetprop issues. Take a look in the OP, under "MagiskHide doesn't start on boot / system.prop in modules aren't loaded / resetprop doesn't work". There are instructions there on what logs to provide if you're having that particular problem.
[Magisk] Floydfire:
Thanks for this "solution" seems like that for me works (sometimes after a reboot I don't pass safetynet and disabling and enabling works) so I was thinking if I do a script (with exkernel manager) that does this at every boot should do it automatically? I've a script named magiskhide in /magisk/.core/post-fs-data.d that does

su
magiskhide --disable
magiskhide --enable

Is that correct and will run every boot or I'm doing something wrong?
[Magisk] BolintsMiki:
Don't use capital letters.
[Magisk] Floydfire:
Yeah, right in the script they're not capital, my bad :P
[Magisk] Didgeridoohan:
You don't have to put su in the script and post-fs-data.d is probably too early. Try service.d or run it with Tasker after boot is complete (there you'll need su).

Same thing applies to you: https://xdaforums.com/showpost.php?p=72832228&postcount=2093

Do that in a reboot where Magisk Hide hasn't started properly.
[Magisk] vitekrus777:
This I myself understood from the log. There was a similar problem earlier, then [MENTION=4470081]topjohnwu[/MENTION] solved this problem.

In the original 96f8efc this problem has appeared again.

In 96f8efc.v3 the problem was solved.

The problem is that there is a tight binding to system/lib64, And I have this library is on the way system/vendor/lib64. [MENTION=4470081]topjohnwu[/MENTION] Wrote that he solved this binding problem and so it was. Such a feeling that rolled back the commit before the assembly.
[Magisk] Floydfire:
Thanks, I'll try to get a log when I'll be back at home in 2 days, another question (sorry to bother again) in service.d I've created a sh file named magiskhide.sh with this code

#!/system/bin/sh
# This script will be executed in late_start service mode
# More info in the main Magisk thread
#### v INSERT YOUR CONFIG.SH MODID v #### MODID=magiskhide
#### ^ INSERT YOUR CONFIG.SH MODID ^ #### ########## v DO NOT REMOVE v ##########

magiskhide --disable
magiskhide --enable
########## ^ DO NOT REMOVE ^ ##########
#### v INSERT YOUR REMOVE PATCH OR RESTORE v ####
#### ^ INSERT YOUR REMOVE PATCH OR RESTORE ^ ####

I've copied the other things from another script in that folder should be good enough to do the toggle off on automatically, right?
[Magisk] BolintsMiki:
How's this for a report?

:cool:

Magisk Hide works on the Wear 2.0 port on my original G Watch. :victory:
[Magisk] Dzeb:
Could you elaborate on what ROM, kernel are you using? And is your bootloader kept unlocked? Would help with my 6P :)
[Magisk] angelo27093:
seems that the image is to big to flash on the s8+ again after the magisk edits on it, here is the log
[Magisk] Bat-Maniac:
I'm on stock - Android O DP3 - with stock kernel and my bootloader is still unlocked...

Bit I have a few problems too... After a reboot my banking app doesn't work anymore until I re-enable Magisk Hide.
[Magisk] king200:
I flashed Magisk-v13.0(54e6a79).zip and I did not get the magisk.apk in app drawer. I took out of archive and install failed. I must be doing something wrong. Is V12 magisk.apk in archive?

I must have done something wrong!
[Magisk] jenslody:
I get the out of memory error also for working versions, so this might be an issue, but is definitely not the root cause of my problem.

I finished my current project at work before the deadline, so I found some time for test today.

The porblem is, that the current beta blocks /sbin by renaming it to /sbin-tmp while flashing.

But the sed in /system/bin seems not to work under TWRP. If I run it from the TWRP-terminal it even segfaults.

I commented out the lines where /sbin is moved to /sbin-tmp (and vice versa) and it works.

Magisk and MagiskManager both work without problems on a (more or less) clean device (stock boot.img).

I attach the modified version that works for me, because I saw at least one other member with a similar issue.
[Magisk] ShadySquirrel:
Users, beware. This happened on my device (Honor 5X on Lineage 14.1.), but it's a possible scenario for other (64bit? I see someone else too had issues) devices:

Flashing latest LOS update with latest Magisk beta fails due to the survival script. Device first booted in "blue light" mode, after second try, booted into eRecovery. I was still able to boot into TWRP, so if you get something like this, boot into recovery, flash Magisk uninstall script and then reflash ROM (to recover boot.img), that should help you recover.

Other possible option would be to extract boot.img from update zip and flash it via fastboot (haven't tested that one, I don't have fastboot on my Windows PC so had to go harder way).

Cheers.
[Magisk] jenslody:
I see the same log entry, but this happens also for working versions.

I attached a modifed zip that works for me to my repvious post (two above): https://xdaforums.com/showpost.php?p=72835978&postcount=2105
[Magisk] plb-dev:
I have the same issue.
[Magisk] jenslody:
You can try my modified version from: https://xdaforums.com/showpost.php?p=72835978&postcount=2105
[Magisk] magico18:
Can't flash zip file of this or 12v on Nexus 7 2013 with nethunter. Can't it be the cause?

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Magisk] Evo_Shift:
Edit - I forgot to delete and install the latest Magisk Manager. ( at least I think this was the issue) Once I deleted the app and used the version that came with the zip everything works.
[Magisk] Marucins:
Hi

Where can I find the latest version MagiskManager?
[Magisk] :
Yep, for me and my OnePlus 3 it was the same, after LineageOS update the device booted into "white light" mode. Luckily I was able to reboot into recovery, deleted in /data the magisk folder and all magisk related files in /data directory manually, reflashed ROM and magisk.zip again. Restart and all was fine. It seems, something is wrong in the survival script (for arm64?) ...
[Magisk] BolintsMiki:
If you flash Magisk it automatically gets installed.
[Magisk] DodoGTA:
It's automatically installed while device is booting after Magisk v13.0 beta installation
[Magisk] Marucins:
Thanks, just make sure everything works.
[Magisk] grego3140:
Not working on SM-N9005 with LineageOS :(
[Magisk] DodoGTA:
Please attach the recovery.log

Note: What do you mean by "Magisk not working"? Does the "Magisk not installed" message show up in Magisk Manager?
[Magisk] grego3140:
No, Magisk successfully installed and MagiskManager say I'm rooted, but the safetynet don't pass with MagiskHide activate :/

I attach the recovery.logif you need another thing say me.

View attachment 4196021
[Magisk] DodoGTA:
Please attach the Magisk log from Magisk Manager
[Magisk] magico18:
But i can flash 11.6v ?

http://cloud.tapatalk.com/s/5953eaa714f82/recovery.zip

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Magisk] DodoGTA:
Please attach Magisk v12 recovery.log
[Magisk] ShadySquirrel:
I was reading around (only suggestion on device forums I found was a hard brick, lol) and found someone experienced similar issue after broken/bad ramdisk flash on Nexus 5X, so it may be that survival script is generating invalid ramdisk/boot image for arm64 devices. Waiting to see if someone on x86 or x86_64 experienced this, too.
[Magisk] magico18:
http://cloud.tapatalk.com/s/5953f5347cdbb/recovery2.txt.zip

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Magisk] DodoGTA:
Please uninstall SuperSU
[Magisk] grego3140:
This log ?
[Magisk] DodoGTA:
Post another log like that after disabling and enabling Magisk Hide and running SafetyNet check again
[Magisk] demonoidmaster:
You're doing it wrong... Jfc..

Magiskhide is for hiding apps from detecting root and Magisk and any modules installed

Only tick apps that detect what i wrote above, Snapchat is one example, you need to manually add it in Magiskhide, clear it's cache then try to log in, if it doesn't log in or such grab a log and post it
[Magisk] magico18:
I did It, i have just repeated the process and only the 11.6v succededhttp://cloud.tapatalk.com/s/5953fd5fec984/recovery.log.zip

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Magisk] grego3140:
The file "magisk-su.txt" is the logcat when the su command is promt with the adb shell, I grant the root .

Thanks for the help you provide :)

View attachment Magisk_afterenable.log

View attachment magisk-su.txt
[Magisk] DodoGTA:
The first log is messed up

Can you remake the Magisk log from Magisk Manager?
[Magisk] demonoidmaster:
Here's your easy fix, flash the uninstaller first, flash your rom update, flash gapps, etc etc, flash Magisk

Easy, right? Could be the rom itself or actually the survival script that isn't working, if you want you can just remove the script from the v13(54e6a79) zip so it doesn't put it in /system/addon.d
[Magisk] DodoGTA:
Then your ROM's boot image might contain /sbin/launch_daemonsu.sh, /sbin/su, init.xposed.rc or init.supersu.rc file
[Magisk] grego3140:
Yes, i attach
[Magisk] magico18:
Any solution to avoid reflashing the rom

Thanks for the help you are providing

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Magisk] btb55:
Just to clarify why asked about keeping the number of 'ticked hidden apps to a minimum'.

Like the everyone else I had a small number of apps that needed to be hidden, without hiding they detected root and failed to open, and then once hidden they worked, so 'Magisk hide root' works great for me, and SN passes, great result, perfect. (Well almost except for one awkward app that still failed and was detecting root by another method, I followed a guide and decompiled the apk, removed root detection, signed and recompiled the apk and it then worked).

I was simply curious about the comment to keep only a small number of apps ticked, so as a test I ticked all apps except those needing root, to see what would happen, to test if it broke Magisk, and it didn't. I didn't notice any change in performance of the phone or Magisk, SN still passed, all my apps still worked, no slow down, apps opened just as before, there was no noticeable change to how any apps opened or the phone worked, it didn't break Magisk and didn't break Magisk hide or SN. In fact it didn't seem to make any difference that so many apps in the list were ticked.

Its not the way I normally run Magisk, and I'm not saying anyone else should tick more than are needed, but when I did everything still worked, Magisk didn't break, apps needing hide root all worked as did those not needing it, and SN still passed. It was just a test after reading the comment to keep ticks apps to minimum.

What does it prove? I don't know except to say on my phone OP3T, it made no difference. I couldn't break Magisk this way, just goes to show how good it is.
[Magisk] DodoGTA:
This log is fine, but other logs are messed up
[Magisk] DodoGTA:
Please send the boot image to me
[Magisk] grego3140:
I remake the log View attachment magisk_error_20170628_212610.log
[Magisk] magico18:
How to do it? [emoji28]

Something like this:https://goo.gl/C6RJs6

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Magisk] :
Samsung Galaxy S5 klte

CosmicOS 7.1.1 20170429

Magisk 13 (latest beta)

Hi, when Magisk is enabled (so without core mod) Snapchat and Twitter stop working but, when I activate the core mod Snapchat and Twitter works... Any ideas, to fix this ?

(wipe dalvik and cache, clear all data... Not working)
[Magisk] Marucins:
OnePlus 5 4.5.3 -> unlock -> restart -> TWRP -> Magisk-v13.0(54e6a79) -> restart

ctsProfile: false

basicintegrity: false

I never had SuperSU installed. Is this the cause of the error/false?

Did I do something wrong?

[IMG="false??"]https://s20.postimg.org/puzyx4419/IMG_0400.jpg[/IMG]

Root Checker Basic say its all OK.

??

//edit

Everything is OK.

I forgot to turn on "Magisk Hide"
[Magisk] adhammagdy:
here's the logcat with the procedure stated in the op's post

Lenovo vibe p1

android 7.1.2

AOSP Extended 4.3

Fire Kernel 3

Magisk latest beta

Magisk12 worked well with core only mode and passed safetynet
[Magisk] bluesky1126:
Hami Wallet not working

Hami Wallet not working for the latest update, but the SafetyNet passed...

Magisk v13 beta(54e6a79)

Sony Xperia X Performance (F8132) Android 7.1.1

Not sure if it detects magisk manager now

Hami Wallet blocks root:

http://imgur.com/a/XdYtX

SafetyNet Passed:

http://imgur.com/a/MfvPg

Hami Wallet on Google Play:

http://imgur.com/a/pP81C

I use Hami Wallet everyday for Metro, train, 7-11, Familymart,etc.....

Life is so inconvenient without an easycard, please help......T_T
[Magisk] bluemeda:
It breaks webview implementation
[Magisk] Peterlymo:
Failed to flash,,,, Samsung j500f running rr 7.1.2",,,file log attached
[Magisk] Okaham:
That worked, thanks!
[Magisk] igorinolw:
Magisk hide not working properly

redmi note 4 snapdragon, xiaomi.eu rom 7.6.25 Nougar latest magisk with safetynetfix module, behavior is the same without module
[Magisk] Shen Ron:
Magisk_merge.img not mounting for module Terminal Systemizer
[Magisk] smashingtool:
My call recorder is no longer working on my Nexus 6P on the 13 beta. Magisk claims to have root, and Greenify doesn't have issues with root, so maybe I just need a new call recorder app. Does anyone here have a suggestion? I am using Skvalex's Call Recorder, which was delisted from the Play store in april and hasn't been updated, so that may be part of the issue.
[Magisk] bluesky1126:
Updated:

I've found out the actual reason. It's my fault, the new Hami Wallet detects stericson's busybox, so I have to remove it to make the new app works.

It seems that even if you enable magisk hide, apps can still detect if others' busyboxs is installed.

But by the way, is there anyway to install custom busybox without being detected?
[Magisk] apophis9283:
I think osmosis has a module that's systemless busybix but don't hold me to it
[Magisk] will5:
Hi, tried but doenst work. Maybe root is embedded on boot.img?
[Magisk] bluesky1126:
In fact, Magisk busybox is still working, but the problem is that now you have to type "busybox" before every busybox commands, and some apps that requires busybox don't support it.
[Magisk] shadowseed:
I just flashed the latest v13 over v12, everything seemed to run well but the SafetyNet-Test still fails...

I flashed only the latest systemupdate-zip (OP3T official OOS) and the magisk zip.

Any advice?
[Magisk] Skittles9823:
Would it be possible for someone to make a module to edit magisk so the commands didn't begin with busybox?
[Magisk] slimdick:
Check another combination, magisk v12 and last safetynet fix [MODULE][v1.10.1/v2 Beta 2] Universal SafetyNet Fix | Try to bypass SafetyNet

MI4C xiaomi.eu 7.6.22
[Magisk] igorinolw:
Already tried, no sucess, even with beta v2 of module :\
[Magisk] magico18:
but I need to root the device before I can extract boot.img :confused:
[Magisk] kessaras:
Great work ??

Latest beta pass safetynet right away in LG G4 and OP3T that I test it.
[Magisk] DodoGTA:
You can use TWRP to extract the boot image
[Magisk] magico18:
got it :good:
[Magisk] DodoGTA:
I removed SuperSU from the boot image and I attached that boot image here

TWRP has a "Flash image" function inside the Install menu of TWRP, so you can flash that boot image using TWRP

Note: Please remove /data/su.img file using TWRP
[Magisk] thewild:
Hi, and thanks for the excellent work done on Magisk !

Yes, that's probably the way most apps will go now. My device passes all tests (SN, etc.), but my banking app (which was working with Magisk) now refuses to start. So I guess they just do it the stupid but efficient way.

About some ways to go around that : is Magisk Manager still needed once Magisk is configured ?

Could it be uninstalled, only to be reinstalled when needed, or would this break Magisk operation ?

Another way might be to disable it, but does disabling hide the app from PakageManager ?

Cheers !
[Magisk] DodoGTA:
Do you pass basic integrity in SafetyNet test?
[Magisk] nick1467:
Hey guys!

I have a problem with superuser access

If any app ask for root access and select option 10min,20min and grant it. Then it asks again immediately, this is happening only With latest build (54e6a79)

Here's the error log from magisk manager

Should I provide any other logs?

Thanks

Edit:- if I set Superuser root access to 'forever' it doesn't ask again
[Magisk] magico18:
Have you already tried this?

It worked, now I'm able to flashboth magisk 12v and 13v. Thanks a lot for your help I really appreciate that :)

12v works pretty well after flashing universal safetynet fix due to cts mismatch.

however on 13v root doesn't work, not a big problem since 12v works, but I attach a log anyway (unable to find the other one: /data/magisk_debug.txt) :)
[Magisk] DodoGTA:
Reboot your tablet and make a regular logcat (after you installed Magisk v13)
[Magisk] magico18:
Flash succeded but magisk manager says no magisk installed ?http://cloud.tapatalk.com/s/5954d878df74f/recovery1.zip

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Magisk] Lordsinko:
It works for me on my samsung galaxy s6 sm-g920I magisk 13 and su but i notice it takes a while to work again once phone is turned off and back on again it says no root for about a minute then says rooted and get 5 green ticks :cool: works

Also certain modules when i install them makes bypass fail but i just remove them not sure wat moduels to use yet with my device
[Magisk] DodoGTA:
Please try to fully uninstall Magisk and then flash Magisk v13.0
[Magisk] magico18:
Already done, I've also tried restoring your boot image to make the flash as clean as possible but nothing, same result[emoji53]

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Magisk] DodoGTA:
Please use Magisk uninstaller to uninstall Magisk and then restore my boot image and then flash Magisk v13.0 beta
[Magisk] magico18:
That's exactly what I did [emoji28]

Inviato dal mio Redmi Note 3 utilizzando Tapatalk
[Magisk] DodoGTA:
Please post the recovery.log
[Magisk] magico18:
Here you arehttp://cloud.tapatalk.com/s/5954f6545edc6/cleaninstall-recovery.zip

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Magisk] DodoGTA:
Now, give me Magisk v12 clean installation recovery.log
[Magisk] grego3140:
In doubt I restor my phone to stock ROM,

So the Safetynet pass

but when I flahs Magisk zip the apk don't install, I install the apk in /common/magisk.apk

and when I open MagiskManager say I'm not rooted

I attache all log, recovery.log is the recovery.log and the magisk-su.txt is the logcat from "adb logcat" when prompt su in adb shell, return "/system/bin/sh : su : not found"

magisk-su : https://drive.google.com/open?id=0B_INFvgyPC2JX1ZJQ0dJUWNKMmM

recovery.log : https://drive.google.com/open?id=0B_INFvgyPC2JOVdCZXJRUFRIY2M
[Magisk] tcnineteen:
I searched U11 as the key word and nothing was found, so I hope this device hasn't been reported before. I just unlocked my HTC U11, but v13 beta couldn't be flashed into my phone via TWRP. v12 was flashed successfully, but no root privileges was detected, and the built-in magisk manager asked me to download the latest version from Play Store where we all know it's not there anymore. I extracted the APK from the v13 beta and the app works fine, but SafetyNet test failed. That's all I found, and log is attached below.

Edit: thank you [MENTION=6429309]DodoGTA[/MENTION], after installing magisk manager v4.3.3, I got root!

P.S. [MENTION=4470081]topjohnwu[/MENTION], I tried to donate something to you today, but since we're all from Taiwan, my Paypal account doesn't allow my transaction:(:( Any other ways to show my gratitude and support?
[Magisk] DodoGTA:
You can get Magisk Manager v4.3.3 from here: https://tiny.cc/latestmanager
[Magisk] fndpena:
Working like a charm in 6P running DP3. Great work [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Edde3d:
Working great RR 5.8.3, Android 7.2.1. VS985. Thanks for the work you put into this.

Kickin' it on my vs985
[Magisk] brian 11:
All the ones I've installed
[Magisk] vitekrus777:
In the end I'll get a bunch of trash in the system, such as the 12 version binaries! Better wait for what the developer says. I see a similar problem not only for me.
[Magisk] brian 11:
Which is the newest version Magisk-v13.0(0b4baad) or Magisk-v13.0(0980cb6)?
[Magisk] DodoGTA:
The former one
[Magisk] brian 11:
Thanks I just installed the old over the new
[Magisk] knpk13:
Does the new unified binary have any advantages from an end user standpoint, or does it make magisk modules easier to make or better or something?
[Magisk] DodoGTA:
You should read https://xdaforums.com/showpost.php?p=72293984&postcount=20 and https://xdaforums.com/showpost.php?p=72293984&postcount=22
[Magisk] SketchyStunts:
Working fine on LG V20 running lineage based ROM.

My note 5 shook it's head no but... Samsung
[Magisk] koekoek91:
Thats correct yes.

First click full unroot, then click continue, then click yes two times and your phone should reboot by itself.

You can then reboot into recovery and flash magisk zip if you have downloaded it to your phone ;)
[Magisk] knpk13:
I already read those posts when they were released (like I always do), but I was hoping for some kind of clarification as I'm not sure my interpretation is correct. The post mentions multiple scattered binaries working in loose combination; so does that mean a unified binary has performance advantages?

Btw working splendidly on OP3T OOS OB8
[Magisk] danilo_scala:
one question please , i found in download Latest Magisk Beta: v13.0 (0b4baad) to flash , but where i download Magisk Manager: v5.0.1 (apk) ?
[Magisk] Didgeridoohan:
It's bundled in the Magisk zip now.
[Magisk] danilo_scala:
thanks, yes two times? in recovery in click yes too? and no lose
[Magisk] koekoek91:
Im not sure what you mean?

If you just do as I explained in my previous post, you should be fine.

I've personally uninstalled magisk and switched to SuperSU just to do a quick test for you :p
[Magisk] magico18:
http://cloud.tapatalk.com/s/5954fd8dda69d/cleaninstall12v-recovery.zip

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Magisk] kgr:
Try [MENTION=4544860]osm0sis[/MENTION]' BusyBox Installer from his thread here: https://xdaforums.com/showthread.php?t=2239421

It works like a Magisk add in - its been working well for me.
[Magisk] bluesky1126:
[MENTION=4392154]apophis9283[/MENTION] , [MENTION=3919724]kgr[/MENTION]. It just works like a charm!!! Thank you guys for telling me such a great stuff:):)
[Magisk] DodoGTA:
The recovery.log doesn't contain anything about Magisk installation (make recovery.log after installing Magisk ZIP but before rebooting your phone)
[Magisk] DodoGTA:
It looks like that Magisk v13.0 beta can't properly repack the boot image
[Magisk] Lordsinko:
Just out of curiosity what kernel are u using on ur device
[Magisk] grego3140:
sorry here is the good log

View attachment 4196911
[Magisk] grego3140:
now the stock Kernel ^^
[Magisk] Lordsinko:
I had the similar issue and used arter kernel which fixed my issue wat kernels have u tried
[Magisk] grego3140:
You have a SM-N9005?

I tried the lss kernel
[Magisk] Lordsinko:
No i dont have that device

Wat method of root did you use
[Magisk] grego3140:
I used Magisk v12 but I needthe safetynet pass :/