yashsingh1/xdaforums huggingface dataset:
[Magisk] JEANRIVERA:
but you haven't point out what is the issue there....
[Magisk] Benny100:
Magical new version Not working Samsung S8!
[Magisk] cantenna:
no luck here either S8+
[Magisk] kantjer:
Try at least to read the OP and the last few pages before posting.

Fat change your problem has and solution has been already be posted.

The endless stream of these useless posts are the main reason great dev's and contributes stop being active on XDA.
[Magisk] AniketDhoke:
After installing magisk, Amazon and Google app crashing.But after uninstalled Magisk everything works fine. On Moto g3 (Osprey)

How can I send a log ?
[Magisk] DirkStorck:
Thanks! you saved my day...such a simple and easy solution I never thought of. There is now only the question why....
[Magisk] Mayday_XL:
Runs fine (OP5), thanks. :)

Mayday@OnePlus5
[Magisk] dahawthorne:
Will people ***please*** stop posting stupid, useless and pointless "it's not working" comments...?

Will people ***please*** stop posting stupid, useless and pointless "it's not working" comments...?

Will people ***please*** stop posting stupid, useless and pointless "it's not working" comments...?

Will people ***please*** stop posting stupid, useless and pointless "it's not working" comments...?

Will people ***please*** stop posting stupid, useless and pointless "it's not working" comments...?
[Magisk] misterblue31:
Hello,

Phone: Samsung SM-G901F (Galaxy S5 +)

Magisk-v13.0 (c4377ed) :

Magiskhide does not work. When I validate apps, they are marked. I leave Magisk and open it again and apply it in magiskhide are no longer marked.

Test SafetyNet: all tests fail with this version of Magisk

In the Playstore NetFlix and Mario Run do not appear.

Magisk-v13.0 (54e6a79) (before c4377ed):

MagiskHide works perfectly, I have noticed anything abnormal

Test SafetyNet: all tests pass with success

In the PlayStore NetFlix and Mario Run are there.

The c4377ed version is not compatible with my phone, the previous one yes ;)
[Magisk] Didgeridoohan:
You forgot to attach the Magisk logs to your post (one for each version would be nice).
[Magisk] blast1987:
Hello, just to report, i've found a problem in magisk 13 beta (c4377ed)

using redmi 4 prime and latest ResurrectionRemix ROM 5.8.3 from this thread: https://xdaforums.com/redmi-4-prime/development/rom-ressurection-remix-v5-8-3-t3623666

when flashing magisk beta 13 it broke my fingerprint sensor, "fingerprint" option under security disappeared

now i can't enable SafetyNet apps on play store... have to download from another store or manually install because magisk12 hide is not working

EDIT: i can't attach log because i reflashed and wipe my phone like 6 times to understand the error... also reflashed stock miui, it clean also internal storage
[Magisk] Kiid:
Magiskhide not enabled on boot.

Samsung S6 920I

Change liveboot extension to view log.

Cheers
[Magisk] tdhite:
Toggle MagiskHide Causes Root loss on Zygote apps

[MENTION=4470081]topjohnwu[/MENTION] -- normally I do not directly reference you; as a dev on many kernels and ROMs, I totally understand the riffraff that ends up in these trails from folks *not* reading the OP (sorry folks, but too many of you honestly are not friendly to the dev unless you follow his requests).

With that said - I have found a striking issue that I believe bears consideration. Root is lost for zygote based apps (not shells, so add succeeds in your OP instructions). The trigger appears to be the need to toggle magiskhide off/on (in fact, any time that occurs I am seeing a loss of root for Zygote apps only, shells always succeed).

Logs are attached for the failed scenario. Note that (as mentioned) the adb shell succeeds to root, but a zygote app requiring root access fails (that is the image attached, which shows it cannot obtain root, thought the logs suggest otherwise).

What generally resolves this is force closing MagiskManager, clearing the app cache (settings -> apps -> MagiskManager -> storage -> clear cache) and rebooting. Alas, on reboot, again (in this c4... beta) magiskhide does not start on boot, so enabling is required again, which does not trigger the cache clear need because MagiskManager is not yet running, so bootstrap scripts run ok, etc. (at least that's my current assumption).

Logs attached, zygote based app root loss attached (image only). That app is found with "com.af.synapse" in the logs if you happen to look.

magiskwu_log.txt: logs for failed root access

shell_log.txt: terminal log after reboot upon clearing MagiskManager cache

magisk.log: log of reboot (after clearing cache)

last_magisk.log: the prior magic log before reboot

magisk_error_20170704_081748.log: MagiskManager saved log of failed su access for zygote apps prior to clearing the cache and rebooting.

My current take is somewhere along the line of toggling magiskhide, MagiskManager is corrupting the app cache (bad data, possibly not updating, not quite sure).

This is a very strange issue -- cache clearing required to regain root for zygote based apps. Your work is fantastic, keep it up. I am looking into the code around this myself, but have not seen the connection quite yet.

Anyway -- I hope this helps. Magisk remains a bold idea and implementation for making root possible into the future.

=== update -- verified ===

I just verified the above. A particular app needed to be properly hid (which meant toggling hide *specifically* for that app, not even hide in general, since I'd already enabled it and root was working for all apps). Upon MagiskHiding that particular app, all zygote apps again lost root.

Log attached for that session as: magisk_error_20170704_091159.log

=== ===
[Magisk] multitrax:
Hi,

I'm experiencing a problem on Xiaomi.eu's MIUI Weekly 7.6.29 with Magisk 13.0 0980cb6: root (and Magisk as a whole) doesn't work. Because of it I also cannot get /data/magisk_debug.log (or is there any way? I don't see this file when booted into recovery -- I suppose it's removed by something).

Following are (Hopefully) relevant lines from logcat. I'll be happy to provide any additional information.

07-04 17:01:02.806 458 2851 E ProcessKiller: Process magisk_daemon (447) has open file /data/magisk_debug.log
07-04 17:01:02.827 458 2851 E ProcessKiller: Process logcat (451) has open file /data/magisk_debug.log
07-04 17:01:06.005 2866 2866 D Magisk : client: connect fail, try launching new daemon process
07-04 17:01:06.356 2867 2868 D Magisk : sepol: Starting large patch thread
07-04 17:01:06.356 2867 2867 I Magisk : Magisk v13.0(0980cb6) daemon started
07-04 17:01:06.364 2867 2869 I Magisk : ** post-fs-data mode running
07-04 17:01:06.394 2867 2869 D Magisk : resetprop: Initializing...
07-04 17:01:06.394 2867 2869 I Magisk : * Mounting /data/magisk.img
07-04 17:01:06.406 2867 2869 I Magisk : * Running post-fs-data.d scripts
07-04 17:01:06.408 2867 2869 I Magisk : * Loading modules
07-04 17:01:06.444 2867 2869 I Magisk : * Running module post-fs-data scripts
07-04 17:01:06.444 2867 2869 D Magisk : resetprop: failed to get [persist.magisk.hide]
07-04 17:01:06.754 2867 2868 D Magisk : sepol: Large patch done
07-04 17:01:07.130 2867 3044 I Magisk : ** late_start service mode running
07-04 17:01:07.131 2867 3044 I Magisk : * Running service.d scripts
07-04 17:01:07.139 2867 3044 I Magisk : * Running module service scripts
07-04 17:01:12.505 3475 3688 W PackageParser: Unknown element under <manifest>: meta-data at /data/app/com.topjohnwu.magisk-1/base.apk Binary XML file line #17
07-04 17:01:40.056 5886 5886 W RestStorages: Detected mount point=/magisk
07-04 17:01:40.056 5886 5886 W RestStorages: Available mounts=[/storage/emulated/0, /dsp, /magisk]
07-04 17:01:46.755 5886 6658 W RestStorages: Detected mount point=/magisk
07-04 17:01:46.853 5886 6658 W RestStorages: Available mounts=[/storage/emulated/0, /dsp, /magisk]
07-04 17:02:08.533 5886 7167 W RestStorages: Detected mount point=/magisk
07-04 17:02:08.539 5886 7167 W RestStorages: Available mounts=[/storage/emulated/0, /dsp, /magisk]
07-04 17:02:19.059 7272 7272 D Magisk : client: connect fail, try launching new daemon process
07-04 17:02:19.060 7272 7272 E Magisk : start daemon failed with 111: Connection refused
[Magisk] abacate123:
Magisk Hide seems to not boot anymore along with the rom (or at least it turn off, Idk) in the latest beta, I have to re-enable it everytime I reboot in order to pass the SN, for example (I hope I sent the right log, you can see my phone setup at my signature).
[Magisk] DodoGTA:
Please stop reporting this issue, because I know the root cause of it
[Magisk] abacate123:
Hm ops, sorry if I hurt your feelings lol, I didn't see that it was already a known issue. And that's the first time I report it anyways...
[Magisk] carlese:
Hi, are the bootloops on unencrypted oneplus 5 fixed in the latest beta?
[Magisk] DodoGTA:
Why don't you test it yourself (because you'll help others by providing some information)?
[Magisk] carlese:
Because I use the phone for work and I can't restore it right now if something goes wrong unfortunately.. I read that right now it bootloops if using unencrypted phone, that's why I asked if there were any news on this..
[Magisk] klaustroeger:
Sorry, but then you should not modd it.... that was my simple consequence (to stay on a TW-based ROM)..... or have a unmodified company phone as fallback (my final decision)
[Magisk] RandomPooka:
Just giving a quick update. HTC U11 on Sprint. Working fine with ElementalX kernel. Disabling core only mode allows SN to pass for any who care.
[Magisk] Sebboost:
Hello.

I have issue. With last Magisk v13.0(c4377ed), on first boot button "Magisk hide" is active automatically but functionality doesn't work because safetynet fail.

If I switch off and on, it's good, "Magisk hide" is active and safetynet success.

But if I reboot, I must reswitch button "Magisk hide" off and on for safetynet pass.

I have roolback on [BETA] v13.0(96f8efc). On this version, after activating button "Magisk hide", it stay activated and safetynet pass succes.

My phone:

Sony Z5 Compact E5823 and android 7.0.1

TWRP, ric and verity desactivated (rootkernel_v5.23_Windows_Linux.zip with no busybox and no supersu)
[Magisk] L.F.B.:
View attachment magisk_error_20170704_212137.log

View attachment magisk_error_20170704_212644.log

View attachment magisk_error_20170704_213052.log

Thanks master Johnwu...?

Latest update cts fail..

Edit. Safetynet fail after some time... In latest buid...After every reboot have to switch off and on magisk hide to pass check...

Edit 2. Log from my 3 devices. Nexus 5, 7 and GS4. .?
[Magisk] bluenote73:
On an Axon 7 A2017U, could someone have a look at my recovery log and tell me if there's something wrong here? Root never seems to work, I've posted those logs in this thread as well. I install stock boot.img and system.img then apply Magisk c4377ed.zip

I notice around line 301 I see 'Segmentation fault' after "Legacy property environment initialized'

Thanks for any suggestions
[Magisk] nathanchance:
Alright, new rules! (really they're the old rules, just being enforced)

With [MENTION=4470081]topjohnwu[/MENTION]'s permission, this thread is going to be moderated stricter.

SafetyNet issue? Removed.

Post with no logs or clear steps to reproduce? Removed.

Posts ignoring the OP? Removed.

Off topic? Removed.

This is a pure development and feedback thread. It's nearly impossible to read through 50 pages when 90% of them are irrelevant. Want your post to count? Provide logs, clear steps to reproduce, and keep on topic.

Those who are trying to help, please do not make posts regarding thread etiquette or chew people out. Please report the posts in question (or just the last one, we can determine if there is a lot of off topic) and let us handle it.

Thank you for your cooperation and thank you for making XDA great :good:

The Flash

Forum Moderator
[Magisk] kessaras:
Ok, here is an empty log of latest magisk 13 on lg g4.

And screenshots.

1. It's crashing

2. App doesn't work

3. But I have root.

4. Not even talking about safetynet.
[Magisk] FlavioV:
Clean data for the Magisk Manager app and try again, at least it worked for me after latest update. :)
[Magisk] kessaras:
Nope. Clearing data does nothing at all. It just asks again for root permissions.
[Magisk] fnldstntn:
Can you add option to select all on magisk hide tab?
[Magisk] DodoGTA:
This function isn't really useful because you don't need a lot of apps checked and Magisk Hide doesn't handle a lot of apps being checked well
[Magisk] bluesky1126:
Try to uninstall the magisk using TWRP, reboot, boot into TWRP, flash magisk again and see if it works.

I've once having problem with Magisk Manager that crashes every time in some condition, and reinstalling the whole thing just solve the problem miracally. (Even clearing the data of magisk manager doesn't work for my case!)
[Magisk] asusgarb:
Hi. Using search function I saw the way to remove addon.d that auto flash magisk at boot. Unfortunately I've already flashed magisk. Is there a safe way to remove it.

I know it's a useful feature, but I prefer to install magisk by myself. I was thinking to remove addon.d from system, but I don't know if it's a safe thing to do.
[Magisk] rignfool:
Remove the script from/system/addon.d
[Magisk] DodoGTA:
But that script will be readded on next Magisk install
[Magisk] rignfool:
And he'll have to remove it again?
[Magisk] fnldstntn:
i cant install new modules, it fails. i have installed 5x eis enabler and substratum systemles but when i try to install viper4andtoid, deep buffer remover it fails, i tried to reboot multiple times and clearing manager data. i am on 7ed.
[Magisk] DodoGTA:
Try to install them from recovery and attach the recovery.log
[Magisk] kessaras:
i am the rom's dev.

this is what i'm doing since yesterday. installing/uninstalling, formatting, flashing.....

i've done this more than 20 times since yesterday with magisk 13,12 (plus universal fix, i tried that too but this is out of subject here).

Guys don't flood the thread again with this. If there is no proper solution and working 100% please keep it down until topjohnwu fixes it.
[Magisk] jakito:
I also have the problem where to pass safetynet I need to disable and enable again Magisk Hide.

I have the OnePlus 3 and I'm using FreedomOS 2.10.2 (7.1.1).

(I hope these are the files needed, as this is the first time doing anything close to this...sorry for the inconvenience)
[Magisk] nathanchance:
Thread cleaned.

Man, not even 12 hours and there's already been several posts with SafetyNet issues, no logs, or vague bug reports. Please give this a read to make sure your post counts here :good:

The Flash

Forum Moderator
[Magisk] tanago:
Mine is dual sim btw. I use the tool in Z5 Android Development to make my own custom kernel with dm verity & sony Ric disabled and with drm fix. (I think it's your post with steps that I'm following)

So I'm trying to install the latest beta. Just checked the recovery.log and I get

...
- Flashing new boot image
cat: xwrite: Broken pipe
-Unmounting partitions
...

The twrp im using is https://xdaforums.com/xperia-x/development/twrp-3-1-0-t3580622 and it too gets me decryption failures and /system unmount errors despite it advertised to be able to
[Magisk] tanago:
Just tested your version too(54a6a79 )

...
- Flashing new boot image
dd: /dev/block/mmcblk0p22: No space left on device
16385+0 records in
16384+0 records out
cat: xwrite: Broken pipe
-Unmounting partitions
...
[Magisk] pratikone1:
I tested the newest version on RR that works fine for me.... CLEAN FLASH... TWRP 3.1.0.0...
[Magisk] tanago:
newest version - check

clean flash - check

twrp 3.1 - check

working - nope
[Magisk] pratikone1:
Which rom bro?
[Magisk] tanago:
7.1.1 stock
[Magisk] pratikone1:
Can you try RR?

---------- Post added at 08:28 PM ---------- Previous post was at 08:27 PM ----------

Plzz try RR... I think that'll do the trick if you don't mind
[Magisk] tanago:
RR doesn't support Xperia X
[Magisk] dahawthorne:
Cache & Dalvik wipe? If not done, do it now. Android will automatically rebuild it.
[Magisk] digital0:
Please don't delete my message. IMHO there's no point to provide logs, but I will if needed.

After every reboot timezone is set to GMT+08:00 China Standard Time. I suspect it started after I installed Magisk (current beta).

Does it happen to anyone else?

Edit: I changed persist.sys.timezone in build.prop and it helped. But IIRC it did not happen before Magisk install.
[Magisk] TanByv:
Works perfectly on my A510F with TouchWiz based ROM. Also fully bypasses SafetyNet check :)

Keep up the great work!
[Magisk] freaky2xd:
where can I find the newest beta apk file?
[Magisk] andy hall:
No details of ROM or device, try dirty flash of ROM and see if issues persist.

---------- Post added at 09:34 PM ---------- Previous post was at 09:34 PM ----------

OP
[Magisk] digital0:
There were details in deleted message - Intel Cherry Trail tablet, Android 5.1. So I assume it does not happen for others?
[Magisk] tanago:
cache can be wiped, but dalvik fails, we dont have official twrp for XperiaX and it has major flaws

but after all i think the problem lies in

dd: /dev/block/mmcblk0p22: No space left on device
16385+0 records in
16384+0 records out
cat: xwrite: Broken pipe

and it doesnt appear in v12
[Magisk] wrongway213:
Magisk doesn't edit your build prop, as the whole point of Magisk is to do all of the things we have known and loved in the past systemlessly - so given there's lines in your build prop that clearly set your time zone, and changing said lines fixed the issue - this is in no way, shape or form related to Magisk.

Please don't ask for messages not to be deleted when you've been given clear instructions from a moderator, ignored them, and do not understand what it is you are flashing and asking support for enough to even know you are in the wrong thread - one that has already required moderator intervention twice in under 24 hours.
[Magisk] nathanchance:
Not for me and yes, you should always provide logs regardless of if you think it is helpful or not. Most if not all processes have some form of logic. Also, have you isolated it to Magisk? As in, uninstall, test, reinstall, test?
[Magisk] digital0:
Yes, but these lines were there before Magisk, and the timezone was not changed (which was set manually after the first boot a few months ago) at every reboot.
[Magisk] digital0:
Just tested:

restored orginal build.prop

rebooted to recovery, uninstalled Magisk

booted to Android - timezone is correct (my manually set)

rebooted once more - TZ still correct

rebooted to recovery, installed Magisk

booted to Android - timezone is incorrect (the one from build.prop, not the manually set one).

dmesg without and with Magisk attached.
[Magisk] bluenote73:
On c4377ed on my Axon 7 A2017U, modules work, magiskhide works, safetynet passes, but SU doesn't work at all, here's my logs, if anyone can make something of them that would be great.

I note some entries, 'failed to open database file', and also SELinux : avc: denied { find } for service=package pid=4271 uid=0 scontext=u:r:su:s0 tcontext=u:object_r:package_service:s0 tclass=service_manager permissive=1

Here's my logs, thanks

EDIT: My previous logs, boot.img, etc on github: https://github.com/topjohnwu/Magisk/issues/229
[Magisk] nathanchance:
A logcat is probably going to be better for something like this but great for providing logs :good:
[Magisk] TatesMan:
Should we delete the modules before flashing OOS 4.5.5?
[Magisk] demonoidmaster:
Js but since Magisk now has survival addon.d script it reflashes Magisk right after a rom update, therefore meaning I'd flash ElementalX after i flash stuff like opengapps, bloat remover and then stuff like ElementalX and Busybox by Jrummy

Anyways js Magisk works even if you flash a kernel afterwards
[Magisk] MKRashka:
Is it possible to add an App to magisksu by myself?

I need root for f-stop.

if I set f-stop to ask for root, magisk doesn't do anything
[Magisk] demonoidmaster:
Mine showed it was locked, so i pressed the lock and it remounted it Read/write and i opened Build.prop and it didn't say it was read-only, i think it's just your device that's screwed up dude

Are you using the FX root addon? Even if you can gain root access with the FX manager app you'll need the addon

No, it's a known issue, can't you read? Holy jfc man..

Attached reference of the op since you didn't read first before saying "magiskhide doesn't work"

That's pointless, after the script kicks in after you do a rom update and it reflashes Magisk, wait for it to finish and then flash the Magisk zip then flash your other stuff, clear Dalvik & cache, reboot

In any case i tested it out last time there was Resurrection Remix update, no issues with Magisk, script does what it's supposed to do, heck i even flashed a kernel after it reinstalled Magisk so tbh imo it's safe to flash a kernel like ElementalX after Magisk, dunno about other kernels though
[Magisk] Epikarus:
Hi.

Trying out the newest beta on my stock galaxy s6 on 7.0 nougat.

My phone no longer loses root completely, instead I lose root in some/most apps.

I am able to gain root access through ADB and through terminal emulator. I lose root access in apps like Adaway, System UI tuner, and my file explorer (FX)

Some reboots restore root access to these apps but sometimes it doesnt.

I ran the resetprop log before i lost root, then again after root was lost for most of my apps.

Magisk Manger indicates that root is working. Superuser tab shows that all my root apps are granted root access.
[Magisk] tanago:
https://github.com/topjohnwu/MagiskManager/issues/192

similar problem to mine

a90e8b6_recovery.txt

dd: /dev/block/mmcblk0p14: No space left on device
2817+0 records in
2816+0 records out
11534336 bytes transferred in 0.155 secs (74415070 bytes/sec)
cat: xwrite: Broken pipe

How come there is no space on device? or is this broken pipe the real error?

I think something is changed in v13 that doesn't allow me to flash it because I don't really have that issue with v12
[Magisk] DodoGTA:
I finally made magiskhide start on boot without removing this commit

Source code: https://github.com/TheComputerGuy96/Magisk (branch setns-check-dirty-fix)

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: That setns check seems to still be quite unreliable

Edit: I attached the new Magisk ZIP which doesn't stop magiskhide if setns check fails (It's Magisk-v13.0(f7f4146).zip, by the way)

Edit 2: I rebuilt both Magisk and Magisk uninstaller ZIPs to show correct version string
[Magisk] digital0:
Attached are logcats without and with Magisk.

I see in them:

Kernel timezone updated to -180 minutes west of GMT - it is the correct TZ (manually set)

Kernel timezone updated to -480 minutes west of GMT - incorrect TZ (from build.prop, ignores manually set)
[Magisk] DEVILOPS 007:
Seems to work fine. Do these include the fix to the apparent critical error you said about? Thanks for the update:)
[Magisk] DodoGTA:
This ZIP includes that fix
[Magisk] hoost_pt:
I've updated to f7f4146 but in magisk shows d67b1 3b
[Magisk] DodoGTA:
I'm cleanly rebuilding Magisk now

Edit: I updated the main post with new Magisk and Magisk uninstaller ZIPs
[Magisk] Chocklety Boyee:
[MENTION=6429309]DodoGTA[/MENTION] i am facing masik hide auto disable error ..which zip should i flash? Which of the zip made by u is based on latest beta ? Plz let me know..thanks for ur fix...
[Magisk] shadavis08:
The newest build of Magisk v13 c4377ed

Works fine for me h918 v20 , should I update to the newest Magisk you just updated or just stay where I'm at now?
[Magisk] Paschfire:
Yes

Both I believe, the second one v13(f7f4146) is the latest.
[Magisk] aamadorj:
Thanks for your work about this issue. It seems magiskhide is still not starting automatically on boot with your newest Magisk-v13 f7f4146 build at my N6P running latest PureNexus and latest ElementalX kernel. But magiskhide works fine after I manually disable / enable it with the Magisk Manager settings switch.

Magisk log is attached.
[Magisk] whalesplaho:
https://xdaforums.com/showpost.php?p=72925433&postcount=2572