yashsingh1/xdaforums huggingface dataset:
[Magisk] bluemond:
Yes I did. Is there anything I can do to find out how to fix it? I attached two logcats, one complete with booting and one partial where I disabled and re-enabled magisk hide again.
[Magisk] Artim_96:
Can definitely be possible. If that's the only thing you changed and you double checked your results that's your cause

---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------

The part where the errors start seem to be

Start proc 26981:com.google.android.gms.unstable/u0a1 for service com.google.android.gms/.droidguard.DroidGuardService

So try to remove the app DroidGuard. Because before that there is only the SN error and after that the errors start. So I'd guess that's what's the cause
[Magisk] Karls0:
[MENTION=5125527]Artim_96[/MENTION] - AFAK, DroidGuard is not an app, it's part of google play services. How could i remove it without destroing Google Play store?
[Magisk] Artim_96:
There are also apps called DroidGuard. If it's not that, try disabling app verification in play services and verify apps over USB in developer options
[Magisk] Karls0:
[MENTION=5125527]Artim_96[/MENTION] - I know, I don't have DroidGuard app. USB debugging completely off, app verification off - still reboot. Are you sure DroidGuardService is a part of app veryfication?
[Magisk] Artim_96:
It'scom.google.android.gms/.droidguard.DroidGuardService, so it's something inside the play services. Either it's app verification or the device manager part to locate and erase a list phone
[Magisk] Karls0:
[MENTION=5125527]Artim_96[/MENTION] - I manually disabled this service (DroidGuardService). The system was unable to chceck SafetyNet at all. In the best situation it was endless checking, another try it took quite long then reboot. I think this service is part of SafetyNet check so crashing of it was not reason but effect of bug. What's next to try?
[Magisk] chrcol:
guys how do i activate magiskSU, oddly this is not mentioned in the install/FAQ posts, just a vague magisk manager wil manage it for you.

I had supersu root working so uninstalled it, now magisk manager shows I got no root but still has no option to enable magiskSU, is there somethingI am missing here.

Update, I tried to flash magisk 11 again in TWRP to see if that would install magiskSU but it detected a supersu image so proceeded to install in supersu mode, it offered me no choice, I did already do full unroot from supersu app so it seems that does not fully remove supersu.

I hope the answer doesnt involve a rom reinstall.
[Magisk] jhedfors:
Try osmOsis's unSU zip first, before uninstalling then reinstalling Magisk.
[Magisk] Didgeridoohan:
Full unroot might not be able to restore an unpatched boot image. Especially if your ROM comes with SuperSU pre-installed. You'll need a boot image without the SuperSU code...
[Magisk] chrcol:
Thanks I ran the unsu, on its own it didnt work but then based on the script author's guide, I then reinstalled the kernel which removed the supersu patch.

I am disappointed with magicksu tho I hoped it would allow my banking apps to work but safetynet check fails and none of the banking apps work (they are selected in hide magisk settings).

There is also a couple of apps including synapse which dont prompt for root they just fail root access.
[Magisk] Didgeridoohan:
There's a big misconception that the point of Magisk is to hide root and pass SafetyNet. It's not... That's just one of the functions of Magisk.

Magisk is a way to make pretty much any system modification and make it systemless.

If Magisk isn't working the way you expected it to, there might be something you've missed or your device isn't compatible.

If your device is set up correctly and/or compatible, Magisk and Magisk Hide works very well. If it's not compatible, upload your boot image to GitHub and wait for it to possibly be compatible in a future release... There's been a lot of work done on compatibility lately and the next release should see a lot more devices with Magisk support.

P.S. I installed Synapse, just to try it out, and it requested root access just fine... And if you haven't already, check out some tips for root hiding here:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] Maxxxel:
I also have the issue that magisk sometimes say i am not rooted but i have root Access lol... After a restart it is shown again
[Magisk] Artim_96:
No idea. Maybe a compatibility issue, the log is very short.

Sometimes the last kernel message (/proc/last_kmsg) contains something. At least that's what I was told to post to my ROMs Dev on random reboots but i don't know if I could even read them. But maybe someone else can
[Magisk] fracman:
Trying to install on pixel new dirty unicorns rom. TWRP errors with 1. Can't install magisk.zip. any suggestions?
[Magisk] Captain_Throwback:
Wait until Magisk is compatible with the Pixel?
[Magisk] Karls0:
It is short, hovewer complete. As I said, the procedure tor reproduce the bug is very short, it take just few seconds. In the logcat is all from the start of MagiskHide to crash (reboot ended the logcat). I even try to follow this guide for samsung: https://xdaforums.com/android/general/guide-bypass-safetynet-mm-custom-rom-t3534768 , but still it reboot phone. The strangest is that just after first install I could pass SafetyNet (3 green buttons) but only once. Then it always crash with MagisHide, even after reinstall of Magisk.
[Magisk] roxxxance:
Magisk xposed module can't hide

Hi.

It seems that the xposed module in magisk is detected by google. No safetynet, no root detected apps (like fire emblem heroes)...

I tried the 3 avaiable versions.

Any idea how to fix?
[Magisk] Artim_96:
Don't use XPosed or at least deactivate it and reboot. Can't be hidden by Magisk
[Magisk] roxxxance:
So magisk is able to hide but not xposed? Why? Getting rid of my control app is not a solution :(
[Magisk] Artim_96:
It just can't be unmounted like root
[Magisk] roxxxance:
With magisk I do not need to disable anything. I still have root 100% of the time.
[Magisk] Artim_96:
It is doing it itself...Xposed can't be unmounted that way
[Magisk] karthik km:
I Think in the future days Magisk will more than equal to Xposed
[Magisk] Karls0:
Again about MagiskHide rebooting phone - I tested on other rom, with other kernel. Everything is fine as long as MagiskHide is off. I can access root, phone is stable. When I switch MagiskHide on, it reboots phone after maybe 1 min, sometimes faster. I assume it is not kernel releated, as on both it is the same. What's more I have report, that few months ago, older version of magisk works with this rom (i don't know exact version). If it is compatibility issue (i doubt in it) it must be regression in development. Any idea how to fix it?
[Magisk] teclaap:
Good morning, I have the same problem, I lost my root for this application and I CAN NOT route again, help please
[Magisk] fralacos:
Workaround for Titanium Backup issues with Magisk

I have this problem too with Titanium Backup 8.0.0, using Magisk 11.1. But I'm able to freeze apps using FX File Manager instead. Also, I'm able to restore backups by first installing the apk (same version as backed up) and immediately doing a data-only restore with Titanium Backup.

I guess this could be a problem in Titanium Backup (or somewhere else), and not in Magisk 11.1.

BTW: I also did what is suggested here: https://www.xda-developers.com/psa-...broke-titanium-backup-substratum-heres-a-fix/ but it didn't solved TB issues. I'm using android 5.0.2 stock samsung odexed.
[Magisk] sansnil:
This is on 6.0.1 right? Sounds like you'd already have done this but I have to ask did you run the Magisk uninstaller first and also check in /data for any magisk or boot image backups prior to flashing?

I don't have that issue in my N6 but I use Elite kernel not stock which is permissive so might be another option if you're not wedded to the stock kernel.
[Magisk] Artim_96:
Have you enabled soft reboot somehow? That would kill Magisk with a reboot since it's not a real reboot and scripts might not be executed. Or is just root gone but everything else works? So do you have still the folders in /Magisk?
[Magisk] MDHACK:
ViPER4Android does not work for me. I have a Note 4 Stock ROM 6.0.1. The app keeps asking me to install the driver. Also, en uninstaller for this module would be help full to revert the changes. I was trying to see what files where created by the zip installer, but I did not want to mess things up.
[Magisk] linyuhc001:
I just want flash multirom= =# BTW,I think I can keep my phone safe.
[Magisk] wind0zer:
Flashed with success. Using Nexus 5X, stock N rom (NRD90M), TWRP 3.0.2-1, Magisk v6, and phh su app from play store. Safetynet app reports success. Hope to see maybe a widget in Magisk app to toggle on/off.

On a separate note, I never got phh-superuser-17-magisk.zip to work; it flashed ok, but it doesn't show up in the app drawer nor gives root access. I tested it on cm13 and stock N. Both times I installed phh su from the store. Both are needed.
[Magisk] Artim_96:
The zip is only for the binaries, there is no apk included. That's why the OP stated you need both. The app from PlayStore is just the interface.
[Magisk] reekotubbs:
Has anyone tested this on Samsung Galaxy Note 7?
[Magisk] wind0zer:
After reading the OP and seeing that there's a separate magisk version of supersu, xposed, viper4android, and liveboot, I thought phh-superuser-17-magisk.zip is the magisk version of the playstore app. Now I know both are needed : )
[Magisk] smohanv:
I tried with several combinations (between SuperSu and Phh's) and had to reflash dload few times this week.

If i have magisk base, magisk xposed and phh's installed, i am able to use AP. But I badly need Chainfire's SuperSu (i used magisk's SuperSu) for the reasons to run cf Lumen, Recently, TiB and few more apps. I flashed magisk SuperSu and enabled all these apps with root and fully unroot from SuperSu and flashed Phh's root to achieve working AP. But AP doesn't work...

ghrrrrrrr.................................... I am sort of giving up but seriously do not want to give up.... i will be keep looking here for any further updates..
[Magisk] milesian:
I believe an unlocked bootloader is required for Magisk, so Note 7 is out of the running barring a massive leak from Samsung.
[Magisk] steveo17:
/Rant

since when does restoring or flashing the stock boot.img also restore factory recovery?!?!?.

I went to uninstall magisk to test something with V4A and now my recovery is back to stock and i have no way to flash the recovery again being that i am not rooted and not around a computer where i can use fastboot
[Magisk] KAsp3rd:
Amazing. I just checked out your latest commits to the UI. I love the idea of being able to disable the modules as well. Great concept and implementation.
[Magisk] bobwegle:
What phone are you using? On the opo, if the replace recovery in developer options is ticked, it will replace the recovery with a fastboot system and boot image flash.
[Magisk] steveo17:
Nexus 6P
[Magisk] Shockz:
Read the OP.

---------- Post added at 06:32 PM ---------- Previous post was at 06:19 PM ----------

Use fastboot to flash twrp....
[Magisk] steveo17:
i know how to flash twrp. i'm not at a computer where i am able to right now if you read my post
[Magisk] Shockz:
Your post says nothing about no access to a computer. Sorry for the misunderstanding either way.
[Magisk] smohanv:
ViPER4Android works fantastic. What I have done is described below.

Flashed magisk version of viper and found few convolver which works better for me. Also I have fine tuned settings for headphones, speaker and bluetooth.

I have named profile as eargasm. Unzip and pasted ViPER4Android folder in to the location where viper is reading files from. Also don't forget to install viper all. I have attached viper apk as well.

Using some root app move installed viper apk to system.

To find drive and folder where from viper reason profile info, open viper and create a profile (save profile option in settings) name it as test. Now using file browser find where rest is located. Copy my files (kernel, profile) in to the root of the folder where you find the profile test.

Let me know if sound effects are good. Feel free to change Viper bass from the currenty set 10dB to 6dB.

http://cloud.tapatalk.com/s/57bf343625fff/ViPER4Android.zip

http://cloud.tapatalk.com/s/57bf3458c8018/ViPER4Android_FX_v2401_A4.x-A6.x.apk
[Magisk] stangri:
Magisk (v6) compatible LED Enabler for Nexus 6 (shamu) is attached. Enables (always on, non-blinking) green and white notification lights on Nexus 6.

Tested on NPD90G (where can I complain that N6 owners are left in the cold without official Nougat release?).

PS. I did not create the original lib, I just repackaged it for magisk.
[Magisk] karthik km:
Magisk perfectly working on nougat

Thanks devs
[Magisk] Karls0:
Thanks for your previous help with the bug. I've decided to move discussion to separate thread. In the case you could help, here is a link:

https://xdaforums.com/apps/magisk/magisk-magiskhide-reboot-phone-t3571882
[Magisk] Honeycd:
I download the module xposed inside the app magisk and then comes out error in safetynet, what can I do?
[Magisk] jhedfors:
OMG. Please do some basic searching before posting. Magisk cannot hide Xposed! This had been repeated many, many times.
[Magisk] matif525:
I can't use Magisk Hide.

The steps I did:

Use unsu.zip unroot.

Flash xposed-uninstaller.zip which download from Xposed App, wipe cache/dalvik, then uninstall Xposed App.

Flash boot.img from my rom file.

Boot into system, uncheck USB debugging.

Passed SafetyNet

, root checkers shows unroot.

Flash Magisk 11.1.

Magisk Manager shows Magisk and MagiskSU success installed.

Enable Magisk Hide.

Check Root Checker and SafetyNet attest box in Magisk Hide menu.

Root Checker still ask if I give it access or not.

SafetyNet attest still shows fales.

SafetyNet check in Magisk Manager also shows failed.

Disable Magisk Hide and reboot to system, then enable Magisk Hide.

SafetyNet and Root Checker still recognize my system is rooted

.

My phone info: HTC M7, ROM: ARHD 93.0, Android 5.0.2, HTC Sense 6.0.

Magisk Manager Log:

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
MagiskSU: Moving and linking /sbin binaries
MagiskSU: Exposing su binary
MagiskSU: Starting su daemon
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute scripts
* Stage 5: Mount mirrored items back to dummy
** Magisk late_start service mode running...
MagiskHide: Removing tampered read-only system props
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Killing com.joeykrim.rootcheck
MagiskHide: Killing com.scottyab.safetynet.sample
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
MagiskHide: [com.joeykrim.rootcheck]
MagiskHide: [com.scottyab.safetynet.sample]
Zygote(0) ns=�

MagiskHide: com.google.android.gms.unstable(PID=3925 ns=[0 3925 10018 com.google.android.gms.unstable service com.google.android.gms/.droidguard.DroidGuardService]
)

Please someone help me, thank you very very much!
[Magisk] lipton3651:
On some roms Magisk hide doesn't work. You have a custom rom right? Is it based on aosp or stock rom? Already tried other root hiding methods?
[Magisk] matif525:
Thanks! It's based on stock rom, I remember (not sure) that I tried old Magisk and passed SafetyNet.
[Magisk] lipton3651:
I think phh can hide root too but dont know much about. More i cant help sorry. For hidesu ur Android Version is too old.. U dont have cm or los for isu. Maybe U find newer rom for ur phone
[Magisk] chrcol:
yep I read that post (albeit after I posted) and some other posts also. Thanks for testing synapse, but for whatever reason synapse did not generate a root request prompt on my phone, but other apps did so magiskSU was working.

I have some good news regarding hiding root tho.

So here is some results of tests.

With magisk hide enabled and app selected in the configuration. (doesnt matter if magiskSU is in use or not).

Barclays and barclaycard apps crash on launch.

Tesco bank app launches but detects a hook and then refuses to work.

With magisk hide disabled.

Barclays and barclaycard app detects root and refuses to work.

Tesco bank detects root and refuses to work.

MyEE app and safetynet always fail in both above tests and with either supersu/hidesu combo and magisksu.

However I ran some more tests right after I reinstalled kernel (to get rid of supersu) and before I installed magisk again so without root.

Safetynet passed (both checks)

MyEE worked

Barclaycard and barclays still detected root, suggesting some remnants still left somewhere.

Tesco bank worked

I then this morning played around with selinux and made my own policies.

I now have working MyEE even with no magisk hide enabled

Barclays works but only when magisk hide is disabled otherwise crashes.

Tesco banking refuses to work due to selinux compromise :D (tough nut to crack that app)

Safetynet still fails but I dont care about this as long as my apps work

So it seems at least in the short term by refusing apps the ability to check what other apps exist and also refusing them access to the filesystem via selinux policies one can get them to work, as essentially they been refused permission to check if root, magisk, xposed exists. After I have done more work I will try to make a module which adds the selinux rules.
[Magisk] Didgeridoohan:
Another FIY: I installed Barclays Mobile Banking and added both it and Phone services (com.android.phone) to the Hide list and it started just fine...
[Magisk] westeight:
Barclays, Barclaycard, Tesco, Amex, Lloyds, RBS, Santander and HSBC all work fine with latest Magisk + Magisk Hide. :good:
[Magisk] spetrie:
Barclays, RBS, Amex, Sabadell, all working with Magisk V11.1
[Magisk] candiesdoodle:
Add to that.. Hdfc, amex, Citi, SBI, .. In India :D:cowboy:
[Magisk] JotaC19:
I have not yet been able to run magisk, it gives error to flash zip by recovery, since from the app gives error. It does not work for me based on Nougat ROMs, in the device Moto X 2014 (Victara). Could someone give me a solution?
[Magisk] teddy0209:
Logs?
[Magisk] Captain_Throwback:
Can you try the unofficial Magisk version from today and see if that works?
[Magisk] JotaC19:
The log is the same one that fails at all. I now log with the official zip.

---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------

And now I'll try the last snapshot
[Magisk] JotaC19:
[MENTION=3615867]teddy0209[/MENTION] There is the recovery log.
[Magisk] JotaC19:
[MENTION=1162986]Captain_Throwback[/MENTION] The last build 20170312 (snapshot), it works.
[Magisk] HSNP:
After installed Magisk on S6 Nougat, I keep getting session expired from Samsung account and can't login anymore. Any solutions?
[Magisk] leolawliet:
I was wondering, is it possible for sysctl.conf to be used systemlessly? If yes I don't know how to go about it and I could use some help. This is still one of the only mods I'm using that has to be written to system.
[Magisk] kgb88:
After installing Xposed framework systemless, it showed CTS profile mismatch
[Magisk] Didgeridoohan:
Yes, it does. Solution: disable/uninstall Xposed if you need to pass SafetyNet.

(This has been brought up many, many times and with a simple search you would have found that Magisk cannot hide Xposed, even the systemless version.)

---------- Post added at 10:39 ---------- Previous post was at 10:37 ----------

I don't know anything about sysctl.conf mods... But a quick search got me curious. How is it set up at the moment?
[Magisk] M4rt1n94:
So, now I found the time to test and reproduce the problem with the App "VR-SecureGo" (de.fiducia.smartphone.android.securego.vr) and catched the MagiskLog (this is quiet useless ass it does not show much) & a CatLog.

So sometimes it works and sometimes not.. after a restart I had the best chance to start the App without getting detected. After turning off and on "Magisk Hide" and very fast opening the App sometimes it worked too. I seriusly dont know why this isnt working allways the same but maybe the big [MENTION=4470081]topjohnwu[/MENTION] can figure out what it is (or the best would be, you just install this app at your own device and test it for some hours) ---> https://play.google.com/store/apps/details?id=de.fiducia.smartphone.android.securego.vr

I will attatch the Logs even if I think that the MagiskLog is not showing to much

More infos about my Device:

OnePlus 3T (OxygenOS 4.0.3 official)

Android 7.0

Magisk Version: 11.1

MagiskManagerVersion: 4.2.6

MagiskSU: Yes
[Magisk] chrcol:
yes but clearly doesnt work for everyone so on some phones/roms magisk hide is unable to prevent detection and i can confirm phone was also selected

barclays in my case just force closes tho it doesnt like whatever magisk hide does

it may be in my case that the mix of su files from my switching between su systems has caused the behaviour but i am not prepared to clean setup my phone again at this time
[Magisk] Didgeridoohan:
Yeah... And I suspect that it once again has to do with Samsung and incompatibilities with their devices.
[Magisk] chrcol:
what phone and rom? just saying me too it works doesnt help much
[Magisk] m0han:
is this the location of the file(s)?
[Magisk] M4rt1n94:
Yes it is, this are the Snapshots (Unofficial). I personaly prefer official Builds, but maybe there are some hotfixes etc
[Magisk] EvoWizz:
Hey guys, I have a bug with Magisk, and I don't know what to do :/

I've posted an issue on GitHub: https://github.com/topjohnwu/Magisk/issues/108

Do you guys have any ideas​ about that bug?
[Magisk] Didgeridoohan:
There's been a few users reporting this issue and that Magisk Hide seems to be the problem.

Your issue title is a bit misleading though. Magisk is still installed (as you can see in the screenshot), but MagiskSU has been disabled. From what I've seen, a reboot should fix it, but if it doesn't for you, try reinstalling Magisk.

Before you do that, though, could you save the Magisk log from a reboot where MagiskSU is still disabled when you boot up? You can find it through recovery in the /cache folder. It'd be interesting to see if it shows anything.

You could also upload your boot image to the issue on GitHub. It might be much easier for [MENTION=4470081]topjohnwu[/MENTION] to fix the issue that way.
[Magisk] EvoWizz:
Thanks :) So to fix the bug, instead of directly rebooting, I've powered off my device, and powered it on, I don't know why, but it has fixed the bug (just for now)

Also for the title, I now understand thanks to the guy who has replied to my issue, but I now know that Magisk is still here :)

Well thanks for your help :)
[Magisk] matif525:
I remember

old Magisk able to hide in my phone

, and found the prove below:

So, could someone tell me will it be fixed or I need to install old Magisk? Thank you, and thank you.
[Magisk] Captain_Throwback:
Open an issue in github and provide all the logs and boot.img.
[Magisk] leolawliet:
It's a file placed in /system/etc that runs an assortment of VM tweaks, kernel tweaks, and net tweaks. You could do quite a lot with it. In order for it to run on startup, you would need an init.d folder or su.d for SuperSU or the service.d folder within Magisk, in which you place a script that runs the command line to activate sysctl tweaks on startup. I have a couple of AIO scripts running from service.d along with the scripts needed to keep Arise going.
[Magisk] Didgeridoohan:
Can't you then just make a module that adds the sysctl.conf file to /system/etc and with the necessary command line in service.sh (in the module)?
[Magisk] leolawliet:
Thing is I would have to make sure the location of the file is recognized. When running this command from the terminal it kinda expects the file to be located in /system/etc but I wanna change that. I've never made my own module, I was asking because I was curious about seeing if sysctl was possible through Magisk. I might just go ahead and work on a module for it if I ever get around to it.