yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
No, not really... MagiskHide is a part of Magisk and that can under the correct circumstances help you pass SafetyNet. If you come in with nothing but: "SafetyNet doesn't pass", you're in the wrong place.

If you on the other hand come here with a proper bug report, with details and relevant logs as to why MagiskHide for some reason isn't working on your device on the current beta release, then by all means report away.
[Magisk] gothicVI:
If it works fine if it doesn't refer to op.

This is a developers forum not a support forum.

People should read the rules they agreed to upon registration.

If op asks, users should follow.

If users are devs or enthusiasts enough to provide proper logs or code that actually contribute to development they should do so - note the if through.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] Trainer_Red:
I tried to install the latest beta of Magisk on my Samsung Galaxy S4 running stock but after installing it, I get a constant notification that "Phone has stopped working" and making the phone unusable. I know that doesn't help much so how would I go about sending a bug report?
[Magisk] jojkaart:
Xiaomi Mi A1

I've got a brand new Xiaomi Mi A1 here that I'm not using for anything important yet. It's currently running with the stock firmware.

I've little experience with android modding, but I'm very much at home with linux console commands. So, if I can be of help in getting

some debug data out of my Xiaomi Mi A1 so we could get Magisk working on it, please contact me with instructions on what to do.
[Magisk] jenslody:
Good you found a working solution.

Uninstall via adb directly or adb shell would have been my next advice. I just had to do the same, when updating to a self-build MagiskManager to get logcats with time included.
[Magisk] CapnShiner:
I've already resolved the issue, but thank you for the information.

---------- Post added at 10:13 PM ---------- Previous post was at 10:06 PM ----------

That sounds like a problem with systemless hosts functionality. I think that's the only thing AdAway modifies. Did you have that enabled in Magisk Manager before you ran AdAway? I am using AdAway without issue, so it seems to be something specific to your ROM or configuration. You might need to reach out to the Lineage developer.
[Magisk] zagzag99:
Just to get in record, for maybe it's a known issue in 14.2 beta.

For some reason the Magisk Hide stopped working all of a sudden. I realized because an MDM app shot me a warning.

At that point I went to the MagiskManager and indeed all checkboxes were off. Turning them on, didn't get stored.

I've rebooted to stop the MDM app from shouting, and after reboot Magisk Hide kicked back in. All checkboxes were restored in UI.

I got no logs, because the reboot. But is there a way for Magisk maybe identify the failing of the Hide feature and either reboot or give a notification to reboot to quickly recover the Hidden state?
[Magisk] störte:
Hi i have a Note 8 and use happily Magisk.

One thing i observe is that it seems to break VoLTE and Wifi Call Icons in the statusbar.

If i use Supersu they are there but with Magisk not.

Does anybody observed that as well ?
[Magisk] jenslody:
After a reboot you should have "/cache/last_magisk.log".

That's the log from last start of magisk-daemon, the actual log is in "/cache/magisk.log" and on debug-builds another log is in "/data/magisk_debug.log".
[Magisk] cmmx:
Got the prompt to update Manager to 5.3.5, from 5.3.0, but the update failed repeatedly: clicked install, but then nothing would happen. Ended up updating manually. Same goes for Audio Modification Library 2.0, btw.

Everything else is running fine (currently installed: ART, F-droid, TZdata, Sysconfig patcher, Xposed sdk23).

Huawei P8 lite, Android 6, Emui 4.0.3 (c432b610) stock, stock recovery.

log: http://textuploader.com/d4s2s
[Magisk] demonoidmaster:
Delete
[Magisk] zagzag99:
Here's the logs you mentioned, I guess only the last_magisk.log is the relevant but I'll post them all. It happened at around the time I posted on XDA...
[Magisk] Didgeridoohan:
I'd start by reducing the number of apps in the Hide list. Only add the apps that really need to be there. Many of those I see on your list are not necessary...

It might not break things (or maybe that's what it did), but it'll likely have an impact on performance.
[Magisk] zagzag99:
I don't think performance crashed it completely. And I'd rather have all apps not see root-ability by default and this list should have been actually the list of allowed rooted apps.

It's more logical that app that is root allowed is the only app that should see Magisk existence.
[Magisk] jenslody:
But that's not how Magisk works (at the moment) and it will most likely not change in the near future, if ever.

So to be sure you should at least give it a try.
[Magisk] topjohnwu:
I need some testers with a Xiaomi Mi A1, please let me know if you'd like to help :)

[MENTION=7798903]mobadass[/MENTION] [MENTION=5423857]Ex-Hunter[/MENTION]
[Magisk] m.atif:
I would do
[Magisk] Ex-Hunter:
Thank you for giving your attention to our new device. I'd like to help any way I can.
[Magisk] Zwitterion:
A good method to force this proper install of Magisk Manager in this situation is to use XDA Labs' own Apps repository. When you attempt to install the latest Magisk Manager, it detects a "fingerprint mismatch" and uninstalls this lingering reference as you aptly put it, before installing the latest version (either stable or beta as you choose, though in our case beta is necessary).

Hope this helps someone.
[Magisk] LinoX:
That's true. It would be more logical that only "allowed apps" were able to detect magisk but at the moment magisk-hide works by simply "unrooting" the phone when you open an app present in the "hide list" and rooting it again when you close it.

As far as I know that is what causes the "magisk is not installed" and "phone not rooted" error that's not a memory problem, it's just that there's an hide-app running in the background.

If you close magisk manager AND all the apps and open magisk manager again it should report that magisk is installed.

Changing magisk-hide the way it should work (which, again, has a lot of sense) would require a rootkit-like functionality = redirect filesystem access by calling process.

In this way PID 1 (in the allow-list) calls a file-io routine and rootkit-magisk-hide shows the actual filesystem, while another process PID2 (not in the allow-list), at the same time, calls the same function and gets a "fake response"...but this would require a complete magisk-hide rewrite.

See:

http://www.phrack.org/issues/68/6.html#article

and

https://github.com/hiteshd/Android-Rootkit/blob/master/sys_call_table.c
[Magisk] Khotu:
How to use Xposed module? I've flashed it and it's enabled (in magisk) but how to use xposed? Or how to use for example Greenify with Xposed or Amplify? It says that there is no Xposed.

Btw Why I don't pass SatetyNet? :( (it's red)
[Magisk] linuxares:
Wrong thread?

Plus the Xposed module will never work with SafetyNet. Since it uses functions that will trigger it.
[Magisk] zagzag99:
Thanks, that explains a lot of things.

But at the specific point in time the manager still reported phone being rooted (as well as MDM app) but the list of hide for apps was reported clean. So I'm not sure it explains this phenomenon.

But if that's how the hide works, then it's a big problem, since Android goes more and more becoming better multi-tasked... It means MDM apps should just become resident and run always and there goes the ability to start a root needing app.
[Magisk] jenslody:
If I understand it correctly, the unmount only happens in the namespace of the process to be hidden and should therefore not affect other processes.

That's why at least a 3.8 kernel is needed (or a kernel which has a backport of mount namespaces feature)

---------- Post added at 04:16 PM ---------- Previous post was at 04:15 PM ----------

See above in this post..
[Magisk] ves626:
I would help
[Magisk] jojkaart:
Let me know what needs doing and I'll take a shot. I already tried Magisk Manager 5.3.5 with v14.2 and that only resulted in black screen after splash screen (or bootloop if I left it unlocked after flashing the patched_boot.img). I used fastboot for the flashing.

When unlocked, the bootloop would show an error message about the phone being unlocked and asking to lock it so it can be verified or something like that.
[Magisk] StegoStegmeier:
Hi,

cant get it to work on my Exynos Galaxy S7, latest Stock OS using the patched stock boot.img flashed via Odin.

I always get stuck at the Samsung logo after reboot.

Am i missing something?
[Magisk] mobadass:
You've probably got enough offers at this point but I'd be happy to help as well.
[Magisk] Fif_:
You are correct. This unmounting is triggered by Magisk monitoring logcat and grepping for pids.

This process is racy, and sometime gets confused, that's why you want to keep the Magisk hide list small.
[Magisk] olivercervera:
EDIT: Please delete.
[Magisk] Erik Rye:
14.2 install was easy and quick; working great on pixel XL alongside twrp 3.1.1

Thank you!
[Magisk] DodoGTA:
Not anymore
[Magisk] Captain_Throwback:
SuperSU is closed source, so how could it?
[Magisk] dirtyreturn:
Hey XDA,

I am wondering if you have any ideas - my n7 2012 7.x.x and 6p 8.0 both have the same thing happen after flashing magisk for some reason.

I no longer get the mute option when an app crashes.

And com.android.phone continually crashes.
[Magisk] osm0sis:
Sounds like permissions/ownership being bad when magiskboot creates the image since it remains working for the session where mine creates the magisk_merge.img.

My only other thought is that I umount the image at the end of my scripts but I don't undo the losetup or anything (didn't think you had to?), so maybe it's left half functional that way. That bad parameter error you got with the template mounting should point [MENTION=4470081]topjohnwu[/MENTION] in the right direction I think.
[Magisk] SuperSandro2000:
As soon as magisk resizes magisk.img to 128mb it just breakes everything and no modules work until I delete the img file. S8, Note8 Port, Xposed, log after reboot attached

Edit: installing iYTBG and xposed will already trigger the limit but they are combined not even close to 64 mb. I checked IMG file with a file explorer and it is still 64 mb after the resize.
[Magisk] jenslody:
I would be interested, if users with this issue have the universal safetynet module installed.

If yes, please uninstall it and dirty flash Magisk again after uninstallation and try it again.

Disabling it and dirty flash magisk should work also.
[Magisk] pakino2004:
My experience is: uninstalled 14 then installed 14.2. Magisk manager is 5.3.5 but without root! Fulmics 4.5 LG g5 JFI back to 14 with Uninstaller then install 14 and I got root again! Modules download and install working now 4 me
[Magisk] SuperSandro2000:
I found the problem! Magisk uses this command (resize2fs /data/magisk.img 128M) to resize the img file to 128 mb but for some reason my S8 with note 8 port does not like that and wants a higher size. If I use the command with 256M it works like a charm.
[Magisk] r80ies:
I have random reboots, after I reboot my device via tasker. This never happened before installing 14.2. Attached is my debug. I am not to strong at debugging so please excuse my lack on info.
[Magisk] Slypnslyde:
Getting this and I can't find where my logs are
[Magisk] Didgeridoohan:
It's always a good idea to read the OP...

(Hint: there are instructions on how to get logs there.)
[Magisk] elborak:
Yes, 14.2beta fails to install on Pixel C for me as well, but 14.0 installs and runs fine.
[Magisk] NeoDaemon:
i would like to help too, i'll be receiving my mi a1 in less than a week.
[Magisk] koraymers:
Ver 14.2 working perfectly here.

RR OS 7.1.2 Sirius
[Magisk] sharkie405:
Forgive me if it's been mentioned before. I did a search for slow and reboot, but it's kind of hard to search for this as those words lead to so many other post.

In any event I've tried Magisk several times with several different versions, and I always get the same result. It takes one to two minutes for root apps to gain root access after a reboot. Since I like to mess with apks and flash a lot, I'm often rebooting my phone and need my file explorer (FX) to be able to gain access to /system ASAP after a reboot. With magisk that doesn't happen, and me trying to get into /system causes FX to freeze. I end up having to manually close the app and open it again and just wait. The same thing happens when I try to use Advanced power menu right after reboot to reboot my phone into recovery or bootloader. The app just freezes, I end up having to close it down and then just wait. So does anybody have any advice on how to speed this process up, or is that just the way Magisk is?

SuperSu (sorry if that word is forbidden here) grants immediate access after a reboot.
[Magisk] EvilKing009:
Check wether your kernel is compatible with magisk or not.

This error is usually occurs when kernel Doesn't compatible with magisk.
[Magisk] ACHILLES R32:
Is anyone having this issue,

I tried to update to the latest OTA 8.0 with October security patch (Pixel). I followed all steps . Disabled auto ota, installed stock boot via magisk . Tried to install update, but it fails at step 1 .

When i completely uninstall magisk 14.2, twrp(3.1.1) bootloops until i install magisk again.

Sent from my Pixel
[Magisk] Mike_jnz:
Just posting some info FYI.

Had been running RR nougat rom on Pixel XL, first with SuperSU but more recently with Magisk. But with Oreo I decided to return all stock except root with Magisk.After returning stock, installed Magisk 14.2 flawlessly. Today, followed update instructions for the October security update. Happy to report, again, worked flawless and passes safety net. This stock update method is truly genius. Never has root been so easy to manage (don't tell Google lol). Thanks Topjohnwu for all your time on this - (another) donation coming.

---------- Post added 6th October 2017 at 12:14 AM ---------- Previous post was 5th October 2017 at 11:59 PM ----------

My update installed very well today, with stock recovery. Have you seen this tutorial by Topjohnwu? If you haven't, there is a section regarding custom recovery toward the bottom.

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
[Magisk] ACHILLES R32:
Thanks , did look at that guide just didn't scroll far enough lol.

Sent from my Pixel
[Magisk] dr.higgins:
I've been forced to reflash magisk several times due to lost of root. When doing a search it seems I'm not the only one with this problem. I haven't been able to figure out why though.

Any thoughts?

I'm on the latest superstock kernel (2.90), SuperMan rom v2.60 (S7 Edge) And Magisk v14.2(1420)

Btw, nothing worth mentioning has occured before loosing root. It's just gone all the sudden. Quite undramatic. And after reflashing everything goes back to normal.

One last thing - after loosing root magisk manager wants to reinstall v14.0 (ie. Non beta) I wouldn't expect anything else though.
[Magisk] Paschfire:
Next time this happens try simply rebooting the Device, 9/10 this solves the issue of the disappearing root.
[Magisk] EViollet:
You need to reflash your kernel after installing Magisk.

Otherwise your will have this behaviour.

Regards
[Magisk] pakino2004:
Now I installed the 14.2 directly with the manager app and it's working fine! JFI
[Magisk] dr.higgins:
Thx!

Although, It would be great to know why this is happening, and if I can avoid it somehow. :)
[Magisk] kpoverdorf:
I'm having this issue on my Pixel XL... I get "Installation problem".

I have stock recovery, stock everything. The only root apps I have are AdAway, TiBackup and Root Browser. Could AdAway have made a change to cause this?

I rebooted to try and resolve the issue and it uninstalled Magisk as per the documentation. I was going to try reinstalling but I'm not sure if that is the right course of action in resolving this issue. Does anyone have any insight to throw my way?
[Magisk] guest4711:
AdAway changes the content of your hostfile, nothing more. So it's hardly the culprit of your issue.
[Magisk] kpoverdorf:
That's what I figured, but I wanted to be sure since there is a setting in Magisk that mentioned systemless ad blocking. I assume that might be for Magisk modules though.

I am looking to get root again at the very least. Currently working to reinstall Magisk. ADB is giving me driver issues though.
[Magisk] Zwitterion:
I wonder why TopJohnWu coded Magisk to make Adaway host file access an option and not a default. Is there a reason why one would not want a seamless arrangement for the host file?
[Magisk] kpoverdorf:
The Magisk manager asks if I want to install "Magisk-vnull.zip", I assume due to my reboot uninstalling Magisk. I flashed stock recovery and boot to be safe. OTA still won't install. Magisk fails to install via stock recovery due to a signature verification and I can't temporarily boot to custom recovery, it just loops.

When I originally went to take the OTA, I selected "restore stock boot". This happened incredibly fast, it made me think nothing actually happened. Is that normal?

I'm not sure where I went wrong to cause this mess, but I'm sure I probably just made it worse with my attempts. :( It appears my only solution is a factory reset unless any of the more smarter people have an idea. :fingers-crossed:

EDIT: I was able to recover Root. I connected to a network Magisk could communicate through, re-ran the installation process of patching boot image, etc. I am hesitant to try installing the OTA again though. Does anyone have any suggestions to help remedy this issue? If any logs help just let me know. I'm not as advanced as most, so your patience and help is appreciated. Thank you.
[Magisk] tag68:
Yes, think so. To modify /etc/hosts it probably remounts system rw. I have no idea if it will detect systemless hosts by Magisk and then omit this action. As I learned today, mounting system rw is sufficient to toggle the detection that something is modified, even if you don't modify anything.

Maybe using DNS66 is a better idea. It does not need the power of root, and it does never modify system.
[Magisk] kpoverdorf:
Ahhh, interesting. I will try uninstalling Adaway and reverting back to stock Hosts and see if that helps... Hopefully the "damage" is reversible.

EDIT: OTA Still failed. :(
[Magisk] Didgeridoohan:
If you have Systemless Hosts enabled in the Manager settings, AdAway can't edit /system directly. It'll only be editing the hosts file in /magisk/.core, that has been Magic Mounted over the original hosts file in /system/etc.

If your /system has been modified somehow, there's nothing that can fix it except a full re-flash of the system.img (and since I know next to nothing about A/B devices, maybe more images).
[Magisk] kpoverdorf:
Thank you for the info. I was actually just doing a little research on flashing system on the Pixel XL. I will seek that as a possible solution first and if I can't find anything or it is unsuccessful I will just start from scratch.
[Magisk] cyprien T:
the Magic gapps module does not work on my Nexus 5 and 4
[Magisk] Ja_som:
But that is not a issue with Magisk, contact dev of that module.
[Magisk] Zwitterion:
Just uninstall Magisk and then flash factory image of the latest month with removal of "-w" from the flash-all.bat file. Boot with TWRP boot file and reflash Magisk. I honestly don't think OTA flashing is as seamless and reliable as it should be yet with Magisk installed.
[Magisk] kpoverdorf:
That's basically what I found. Thank you for the verification. I have strong feelings that I did something to cause this issue. I think I installed Adaway before I enabled the setting in Magisk to prevent system modification. But you could be right and it could just be buggy.
[Magisk] jenslody:
It's a known issue, but hard to reproduce reliable, as there are at least two kinds of lost root: one where the Manager shows system is unrooted, but still is able to grant root for adb shell and one where the su-command itself does not work. The first can be reproduced on my J5 with actual GZR-Validus in 6 or 7 from 10 cases after a hot reboot, but the real cause is hard to find. The second one just happens from time to time, but very rarely.
[Magisk] chenrp:
Running latest rr rom

On the latest update of magisk, the oneplus 3t is running very slowly..

Please assist.
[Magisk] akenis:
Do u have stock recovery?
[Magisk] ubercool786:
Xiaomi Mi A1

Any luck getting it to work on Xiaomi Mi A1 [MENTION=4470081]topjohnwu[/MENTION] You asked for testers and many of us are willing to test. Please update us with the status of it. Can we expect magisk on Mi A1 or not?
[Magisk] chenrp:
Istalled on android tv s912 cpu and on my oneplus 3t and comparing 13.3 to 14.2/14 both devices running slowly!
[Magisk] Didgeridoohan:
You're gonna have to provide a lot more info/details/benchmarks/logs/whatever could be applicable if you're expecting any kind of help.

It might be something specific to your device/setup. I don't experience anything similar on any of my devices, one of which is a OnePlus 3T...
[Magisk] chenrp:
tried many things, only reflash kernel solved the slow issue
[Magisk] Didgeridoohan:
Ok... Cool story... :p

Anyway... Like I said, unless you provide something more than that to go on there's not much anyone can do.

Sounds like there might be something about your setup that doesn't play well with Magisk.

It might be something about Magisk that [MENTION=4470081]topjohnwu[/MENTION] could fix, in which case you reporting this would be great since it would mean you'd found a bug.

Or it could be that Magisk is working fine, but there's a bug somewhere in one of the apps/services you're using that's causing the issue.

Or it might be something completely different.

Either case, it's quite likely nothing's gonna happen without some more work from you...
[Magisk] simonsmh:
Error occurs on 8.0 device when installing large modules. See log attached below.
[Magisk] guest4711:
Perhaps a similar problem as mentioned above: https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post74043626
[Magisk] simonsmh:
Cool but I have to say that it just working on 7.0. That's weird but I don't know what's wrong with it.

Edit: Debug log uploaded. It seems that nothing wrong with the magisk_merge.img.
[Magisk] Jon_Irenicus:
Sony Xperia Z1 Compact (Android 5.1.1 - 3.4.25-lp-mr3-Advanced) 14.5.A.1.236

Magisk Hide is not shown in the side menu, Magisk Manager tells that Magisk is not installed and Not rooted, but SafetyNet check PASSES.

Is there a way to run Magisk Hide on Xperia Z1C?
[Magisk] bbender716:
Anybody ever have the issue where when using Magisk, Viper4Android will randomly stop working in the middle of playing music? After rebooting and re-enabling permissive within V4A, it works again... temporarily
[Magisk] fusk:
Can't update to 14.2 either through magisk or twrp. Unable to unpack boot image.
[Magisk] ShadySquirrel:
Reopen V4A app when processing stops. It usually means v4a background service got killed.
[Magisk] clambert11:
I'm struggling to get TiBu working on my Pixel XL. It might not have anything to do with Magisk 14.2 but I thought I'd give SuperSu a shot until I am able to restore my 6P backups.

Can I just install the boot.img of my ROM to remove Magisk?
[Magisk] Sgace:
Yes I have. On my Pixel I want this so I can take Ota's and still have root in an easy way:D
[Magisk] vs4vijay:
Google Pixel

Hey,

Will in work on Google Pixel? I have stock Google Pixel running Android Oreo 8.0 without root/supersu. Also my bootloader is locked? Will Magisk work?
[Magisk] Pkt_Lnt:
Yes there are *dozens* of posts here about it and full info in the release thread.
[Magisk] Dejvid50:
Hi, I'm new in Magisk.. When I want flash magisk (all zip versions 14.2/0; 13.5 ..) it says error in TWRP. I try unroot script before flash magisk..

Thanks for reply..

My phone : Samsung Galaxy S4 Mini (GT-I9195) ; resurrection remix 5.8.4 - Android N

here's log :