Database Develop

Magisk works well - but MagiskHide reboot phone

Hi, I've decided to start this thread as I can't find solution in "Magisk General Support / Discussion". Hereunder I present summary of issue:
Device: Samsung S4 (i9505), Custom rom, Android 6.0 (Older version of Magisk is reported to works well on my rom Click)
Description of issue: Everything works well, root access is granted, system is stable - as long as MagishHide is turned off. When I turn it on and try to check SafetyNet, the phone reboot. I did succesfully check of SafetyNet but only once after first install, then it always reboot.
What I tried:
1. Reinstalling magisk with additionally restoring clear boot.img before new instalation.
2. Clearing Magisk Manager data.
3. Disabling DroidGuardService
4. Changing permission as suggested HERE
5. Reinstalling Magisk on different rom and different kernel to limit possibility it is rom-depended
My procedure to reproduce bug:
1. Open Magisk Manager and turn MagiskHide On.
2. Press SafetyNet check (also in Magisk Mager).
3. Phone reboot.
I attached Logcat of this procedure. It's quite fast so it is short log.
Thanks in advice for your help.

Karls0 said:
Hi, I've decided to start this thread as I can't find solution in "Magisk General Support / Discussion". Hereunder I present summary of issue:
Device: Samsung S4 (i9505), Custom rom, Android 6.0 (Older version of Magisk is reported to works well on my rom Click)
Description of issue: Everything works well, root access is granted, system is stable - as long as MagishHide is turned off. When I turn it on and try to check SafetyNet, the phone reboot. I did succesfully check of SafetyNet but only once after first install, then it always reboot.
What I tried:
1. Reinstalling magisk with additionally restoring clear boot.img before new instalation.
2. Clearing Magisk Manager data.
3. Disabling DroidGuardService
4. Changing permission as suggested HERE
5. Reinstalling Magisk on different rom and different kernel to limit possibility it is rom-depended
My procedure to reproduce bug:
1. Open Magisk Manager and turn MagiskHide On.
2. Press SafetyNet check (also in Magisk Mager).
3. Phone reboot.
I attached Logcat of this procedure. It's quite fast so it is short log.
Thanks in advice for your help.
Click to expand...
Click to collapse
I'm having a similar issue on my Sony Z3 compact. I've tried v11.1 and yesterdays unofficial v12 build. My only difference is that I don't actually need to click anything to cause the reboot. I wait for 10-15 seconds. The screen freezes and it reboots.
Sony Z3 compact , stock based custom ROM and stock kernel.
Base magisk install with the only setting changed is to enable hide and select a couple of banking apps
Sent from my Xperia Z2 Tablet using Tapatalk

In my case I had also self-acting reboot but only if internet connection was on. In other case I needed to manually triggered it, in the manner I descibed above.
Edit:
I think, I sorted out this. I changed two things:
1. Updated rom to android 7.1-based.
2. Changed GApps to smaller package (nano).
So far I can use MagiskHide, no random reboots.

"Magisk is not installed. Latest v18.1 (18100)"

Hello everyone,
I am having huge issues here. I set my phone back to factory settings after running TWRP, Magisk and fake gps and routes . Phone is as new but TWRP is still installed as a recovery mode available.
Whenever I try to install Magisk via TWRP flashing method I get "install magisk failed to mount '/data' (no such process)"
If I reset the phones file system so try EXT 2,3 etc and eventually set it back on EXT 4 then magisk installs seemingly but then my phone resets to factory and I do not see magisk anywhere once setting my phone up again. If I then install magisk manager it says "Magisk is not installed. Latest v18.1 (18100) I cannot seem to fix this and have been trying all day.
I want to reset my phone up for GPS spoofing but am running into multiple problems.
Please can anybody advise?

Quinn23 said:
Hello everyone,
I am having huge issues here. I set my phone back to factory settings after running TWRP, Magisk and fake gps and routes . Phone is as new but TWRP is still installed as a recovery mode available.
Whenever I try to install Magisk via TWRP flashing method I get "install magisk failed to mount '/data' (no such process)"
If I reset the phones file system so try EXT 2,3 etc and eventually set it back on EXT 4 then magisk installs seemingly but then my phone resets to factory and I do not see magisk anywhere once setting my phone up again. If I then install magisk manager it says "Magisk is not installed. Latest v18.1 (18100) I cannot seem to fix this and have been trying all day.
I want to reset my phone up for GPS spoofing but am running into multiple problems.
Please can anybody advise?
Click to expand...
Click to collapse
This is not the place for support on how to cheat and spoof.
You might want to get an iPhone and cheat with it since you aren't understanding the process you set up to cheat with.
BTW, the reason it's doing it is how you set up your cheating environment. Particularly the part that you're using to bypass the anticheat check system of the game you're cheating in.
Factory reset will fix it.

xNotta said:
This is not the place for support on how to cheat and spoof.
You might want to get an iPhone and cheat with it.
BTW, the reason it's doing it is how you set up your cheating environment. Factory reset will fix it.
Click to expand...
Click to collapse
Apologies did not know this. Did try a factory reset of the phone to no avail.

[Magisk v17.3] help needed.

Hi!
So this is my first post on xda, so please be nice
I rooted my Samsung s8 sm g950f with ambasadii, and running magisk.
When I first flashed the rom everything went ok. The first time I entered the Magisk Manager app there was a note that said that I can update the manager app to v18.1. When opened the app got a message that the app was unsupported by magisk manager. So I flashed the rom again and just didn't updated the manager app. That's one problem, here is the next one.
When I enter my banking they use a 2 step verification system. I have to go to the phone and enter a code that verifies the login. Now since I've rooted the phone I can't use it, is there any solution to this problem? The banking app does not support either a rooted phone. One of the reasons I rooted with magisk is the Magisk Hide. But I don't think it is working for me . The verification goes through the sim card.
Let me know if you need some more info to help me solve this problem!
PS: I am new to rooting
Thanks!

Welcome to XDA, Magisk and root world.
Quick tips:
Every time before trying the problematic app again, under Android settings/app, stop it and clean its cache and data. Even better to unistall it, reboot, install it again from play store. Even better before reboot go to recovery mode and wipe cache, dalvik (only those!).
Hide Magisk Manager (=repack it with a random name). You do that on Magisk Manager settings menu. After that its visible name will be only Manager (on your app drawer).
read everything here, special attention to SafetyNet and hiding other rooting tests apps may use:
https://www.didgeridoohan.com/magisk/HomePage
install MagiskHide Props Config module and use its improve hiding settings: (available for download on the Dowload menu of Magisk Manager)
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Try updating Magisk/Manager to 18.1/7.0 (last stables):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Do backups and try updating to last Canary builds. Read last posts on its thread:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Maybe the module ShellHide works better than standard Magisk Hide on your device, I don't know. Read thread:
https://forum.xda-developers.com/apps/magisk/magisk-shellhide-t3855616
For general Magisk support, usually better search and ask for help on official support thread:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

Snapchat won't sign in, how to fix?

Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks

JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
The reason I'm having this issue is because Snapchat randomly signed me out today and my restore point in titanium backup was too old

I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.

JayTheKid said:
Alright so I'm running magisk 18.0 on OnePlus 3T with xposed framework. I was able to sign into Snapchat before xposed when I used magisk hide and all the other things you're supposed to do. I'm obviously aware I triggered safety net by using xposed, what's the fastest way to get safetynet to pass again so I can sign into Snapchat? Is it as simple as disabling xposed? Please walk me through this, thanks
Click to expand...
Click to collapse
vonDubenshire said:
I had it too. Sign out clear data and cache and forced stop
Go hide in Magisk.
Reboot.
Clear data and storage again m
Open MM & turn off Magisk Hide.
Wait a few seconds.
Toggle Magisk Hide back on.
Force stop and clear Snapchat again.
Now before rebooting go ahead give it the permissions you want it to have.
Theory: don't give it the "phone" permission at first it at all if you can help it.
Reboot
Let everything finish loading and settling in, wait a couple minutes then try again.
If it's still messed up, is the account locked on their end until you call?
Let me know.
Click to expand...
Click to collapse
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it

JayTheKid said:
I turned off xposed in magisk and the installer, retoggled magisk hide for Snapchat and rebooted. Account was locked, what triggers this? I was using snap with Xposed undetected for months and then it randomly acts up. You mentioned not giving it phone permission, is that how they catch you? The only other thing I could think of that caught me was my cable app (spectrum TV) makes me disable usb debugging to use it
Click to expand...
Click to collapse
The phone permissions allows the app to see the phone's IMEI code. I think maybe that detected you are on a rooted phone using that information.

How to use Snapchat with magisk (After Ban)
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX

No such item in xbin
I tried that too but i dont find any item such as busybox my Snapchat account can't be locked because its has been open in different phones
So give a solution what should i do i uninstall edxposed tried everything root switch root clock hut none of them really works its say oh on your temporarily login fails please try again later help needed seriously its been days
Running
Magisk 20.4 stable
Ed xposed 0.4.5.6 justins forks snadhook
Android 10

Magisk Zygisk + LSPosed Zygisk = black screen after boot

Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.

i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too

rf9992003 said:
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
Click to expand...
Click to collapse
Exactly this, bank apps can't detect the new zygisk, at least for now, just hide magisk app, delete TWRP folder and use SNF zygisk module and the black list

hi
MisiekDP said:
Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
Click to expand...
Click to collapse
Hello, were you able to solve this?

maycomathias93 said:
hi
Hello, were you able to solve this?
Click to expand...
Click to collapse
No. You have this same problem (phone not turning on)?

yes, the only solution in this case is to run uninstall magisk and install again without lsposed. For now use edxposed without safetynet (sorry for my google translate english)

Man, I solved this problem, going from Android 9 (custom ROM where I had the problem) to 10 (also custom ROM). I hope it helps you, greetings.