Related
pretty much title.
sometimes i lose root twice a day, sometime 3day without lose, reboot/reflash magisk fix it
Same here
Enviado de meu LG-D295 usando Tapatalk
Just experienced the same issue. After installing some modules and rebooting
I am experiencing the same thing.. but when or how I don't know... I just take reboot and again root will be back. Might be some other app like clean master or auto killing apps kills magisk services???
I had the issue too, but it stopped when I disabled MagiskHide. That of course is only a solution if you don't actually need it.
Not being an expert, I never found a way to debug the issue or contribute otherwise.
I can confirme. Also when MagiskHide is on, I experience random reboots, which is bigger problem. Any fix for it?
Karls0 said:
I can confirme. Also when MagiskHide is on, I experience random reboots, which is bigger problem. Any fix for it?
Click to expand...
Click to collapse
Just a thought: have you added any system apps/processes to the Hide list?
No, i didn't. I don't use android pay, and i don't think that hiding root may be necessary for any other system app. When I turn MagishHide I have maybe 1 min before reboot. All was fine first few hours after installation, before first root losing.
If it will help, I'm on AOSP 6.0 custom ROM. My device is i9505. What's interesting it happens only if mobile data is on. Wi-fi doesn't do any troubles.
I will throw my experience into this thread as well. I am running Magisk 11.1 with DarkRom on my Nexus 5. Everything seems to work very smooth outside of randomly loosing root. I don't have to reflash, just reboot and it comes back. I do have MagiskHide enable for Android Pay. I also have the AppSystemizer model installed to covert Action Launcher 3 to systems. No random reboots, but loosing root is annoying. I may try to disable MagiskHide and see if that solves the root drop issue. Android Pay is handy though.
Ok Folks my 2 cents in regards to this trouble, i have did some work in reproducing this Magisk Root Loss.
say i have few apps like 1) SafetyNet Sample: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en & 2) RootChekerPro app and both these apps are hided them from root using MagiskHide.
So when i launch Magisk Manager app and checked safetynet Status and then opened app1 (safetynet Sample) ran the test and then immediately did Forcestop the Magisk manager app and launched back Magisk Manager app boom the root is lost and did a reboot everything is back fine again.
I've been trying to find the cause of this issue for a couple of weeks. This is what works for me so far
1. Open Magisk Manager when root is working (either immediately after rebooting or after disabling Magisk Hide).
2. Does Magisk BusyBox and Magisk Hide.
3. Reboot
4. Enable Magisk Hide, but keep Magisk BusyBox disabled.
5. Reboot
Check if root disappears anymore.
I think Magisk Hide is causing the issue, disabled the Magisk Hide and the root stays.
It may also be releated with GApps package - it could explain why some people have this issue with losing root/stability but others no. You can try with smaller package (picko/nano).
Magisk 11.5 seems to fix the issue for me
craigacgomez said:
Magisk 11.5 seems to fix the issue for me
Click to expand...
Click to collapse
No, it's just randomly occurring.
I was having the same problem with 11.1 and flashed the 11.5. It doesn't fixed.
Then flashed the ROM and 11.1 again the root is still there.
I don't know what exactly triggers the root to hide but there is something going on.
works on first flash of 11.1, then the next reboot breaks it again. uninstalling and reinstalling magisk fixes it again until the next reboot
I switch on MagiskHide only when I need it. So far it's quite good option, doesn't require any reboots.
did more testing, I don't lose root at all when I have MagiskHide disabled. Deleting /magisk/.core/magiskhide in recovery returns root.
Mostly a "me too" post. Issue still occurs on 11.6.
I tried replacing MagiskSU with SuperSU. But still the issue remains.
I was using the Xposed framework today and every app kept crashing so disabled Xposed framework and related modules.
However, afterwards my banking apps stopped working.
These apps are logging me off because they detect my phone has been jailbroken.
The app in question is Lloyds banking app (UK)
I have Magisk 16.0 on a Samsung S8 G950F with renovate ice 7.2 installed
Everything was working before
When I tap on safety net check i get all success
In Magisk hide the apps I want to hide the status of are checked (lloyds being one)
I uninstalled, cleared cache of the app, restart the phone and installed the app again, then before starting it up I checked the option in Magisk hide and then opened the app. However it didn't work.
Any idea what I am missing?
Thank you
http://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
Tried those options already
Hide Magisk manager but didn't work
I would uninstall the banking app or delete it's memory completely. The app might have stored the root status and a phone usually does not unroot anymore.
Unfortunately the banks do not see that the owner of a rooted phone usually works more on keeping his phone safe and free of ads.
I'm going to try that again but doubt it will work as I have tried it already. Maybe there's something residual left that can't be removed even after cleaning the data. I see a lot of apps folder in my file manager from apps that I deleted ages ago.
LLoyds bank
went to bank info and cleared cache and data
Uninstalled app
went to file manager and removed residual files folders
installed clean master and did a cache junk file clean up
restart phone in recovery and cleared cache and dalvic cache
rebooted phone and installed lloyds banking app
opened magisk manager before opening lloyds and ticked lloyds app in magisk hide
opened app and inputted login information
same error: your device appears to be jailbroken etc
Have you tried with Magisk v16.7 (MagiskHide has been improved since v16.0)?
Have you tried repackaging the Manager?
Have you tested if the app is detecting Magisk in the Manager name?
Have you tried grabbing a logcat, to see if it's possible to figure out what's happening?
Etc...
In other words: All of the things that are found in the link I gave you earlier.
is your kernel set to permissive? ive noticed if i set kernel to enforcing then my banking app works with magisk hide. im with santander uk
dead0 said:
is your kernel set to permissive? ive noticed if i set kernel to enforcing then my banking app works with magisk hide. im with santander uk
Click to expand...
Click to collapse
That is interesting. MagiskHide should be able to hide a permissive SELinux. I wonder why it doesn't seem to work...
Didgeridoohan said:
That is interesting. MagiskHide should be able to hide a permissive SELinux. I wonder why it doesn't seem to work...
Click to expand...
Click to collapse
it is strange... seems on latest builds of banking apps, they are somehow still detecting if kernel is permissive or enforcing.
cpu2007 said:
I was using the Xposed framework today and every app kept crashing so disabled Xposed framework and related modules.
However, afterwards my banking apps stopped working.
These apps are logging me off because they detect my phone has been jailbroken.
The app in question is Lloyds banking app (UK)
I have Magisk 16.0 on a Samsung S8 G950F with renovate ice 7.2 installed
Everything was working before
When I tap on safety net check i get all success
In Magisk hide the apps I want to hide the status of are checked (lloyds being one)
I uninstalled, cleared cache of the app, restart the phone and installed the app again, then before starting it up I checked the option in Magisk hide and then opened the app. However it didn't work.
Any idea what I am missing?
Thank you
Click to expand...
Click to collapse
If it's anything like Barclays's App, once it detects a rooted phpne, that's it - you're stuffed, as the App sends the phone's identity to Barclays's blacklist. The only way out is a reflash, which will give the phone a new identity.
.
DaystromLIVR said:
If it's anything like Barclays's App, once it detects a rooted phpne, that's it - you're stuffed, as the App sends the phone's identity to Barclays's blacklist. The only way out is a reflash, which will give the phone a new identity.
.
Click to expand...
Click to collapse
To follow-up, it appears that Barclays doesn't use SafetyNet, but something called libShield (??!).
Whenever Barclays detects root on one of my phones, I have to reflash it to stock, thus giving it a new identity.
I have to follow this sequence, in order to prevent tripping:
Reflash the device to stock
Make sure you get Magisk installed BEFORE re-installing the banking app.
Once you've installed the banking app, DO NOT RUN IT yet.
Make sure MagiskHide is ticked for that banking app (and any related apps, like Pingit).
Do the 'randomise Magisk\'s package name' thing.
Set the Superuser thing to 'deny' by default (Barclays seems to trip if it detects that a user is pressing DENY, by the longer time taken).
Reboot
Make sure everything is working
Then, start the app, and begin the reregistration process.
It's happened on me to. On Bank Mandiri App. On other Bank running normaly. The issues happened after upgrade into Magisk 17.1
On Magisk 16.x it's Work without any issue.
Any clues what going on and how to fix it?
repackaging the Manage with a random name is the trick,i did it and its works
In my case (RaiPay in Romania) I did all things except reflashing and it did not work.
Logcat: https://gist.github.com/eusebiu/8110ef85b1d4093c557b32a101fac299
eusebium said:
In my case (RaiPay in Romania) I did all things except reflashing and it did not work.
Logcat: https://gist.github.com/eusebiu/8110ef85b1d4093c557b32a101fac299
Click to expand...
Click to collapse
Hi, I also have RaiPay (Czech rep.), please try to change SELinux to "enforcing" with this module, it works for me:
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042
PlagueCz said:
Hi, I also have RaiPay (Czech rep.), please try to change SELinux to "enforcing" with this module, it works for me:
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042
Click to expand...
Click to collapse
Hey! Thanks for replying! In my case it was already set to "enforcing". I tried changing it using KA-Mod from enforcing to permissive and back but still same result.
eusebium said:
Hey! Thanks for replying! In my case it was already set to "enforcing". I tried changing it using KA-Mod from enforcing to permissive and back but still same result.
Click to expand...
Click to collapse
Hi, sry I didn't reply, too busy.
Please try following Magisk modules:
Busybox for Android NDK
Magisk SELinux Manager (set to enforcing)
MagiskHide Props Config
SafetyPatch
SQLite for ARM aarch64
Modules can be found in Magisk "Downloads" tab (except SELinux manager).
I have these modules installed and my RaiPay works, in combination with enforcing SELinux. I think both our RaiPay apps are very similar if not the same.
PlagueCz said:
Hi, sry I didn't reply, too busy.
Please try following Magisk modules:
Busybox for Android NDK
Magisk SELinux Manager (set to enforcing)
MagiskHide Props Config
SafetyPatch
SQLite for ARM aarch64
Modules can be found in Magisk "Downloads" tab (except SELinux manager).
I have these modules installed and my RaiPay works, in combination with enforcing SELinux. I think both our RaiPay apps are very similar if not the same.
Click to expand...
Click to collapse
Thanks for answering! I think the SafetyPatch was not correctly installed as I get an error message at boot (something with Android has an internal system error. Contact the manufacturer) => not working...
eusebium said:
Thanks for answering! I think the SafetyPatch was not correctly installed as I get an error message at boot (something with Android has an internal system error. Contact the manufacturer) => not working...
Click to expand...
Click to collapse
Yes, I get the same message, is your RaiPay working? And have you tried RaiPay without Magisk installed on your device?
I'm at my wits end trying to get Magisk back!
(The backstory is that I had been running a DirtyUnicorns OS for a year just fine, but then Pokemon Go started failing to login. So it was time to update.)
Using a Samsung Tab 4 (SM-T330NU)
Formatted and installed stock OS/boot
Used Odin to flash "twrp-3.0.0-3"
Used TWRP recovery to update to "twrp-3.3.1-0"
Installed "Lineage OS 17" (and added Gapps) - made sure it booted and all was well
Booted into TWRP recovery and installed the latest "Magisk-v20.4"
Wiped cache and rebooted
Installed the latest "MagiskManager-v7.5.1" and got "Magisk is not installed"
After a great deal of searching I learned how this is supposed to be corrected:
Took the boot.img from the Lineage OS 17 zip,
Used Magisk to patch it, creating "magisk_patched.img"
Used TWRP recovery to install "magisk_patched.img" to the boot section
Wiped cache and rebooted
Still getting "Magisk is not installed"
Booted into TWRP recovery and installed the latest "Magisk-v20.4" just in case
Still getting "Magisk is not installed"
This is all after roadblocks for hours a day for a week trying to pass safetynet using Magisk on Lineage OS 16 for about a week, so I thought this fresh start would be easier and now I'm pulling my hair out.
Any suggestions would be helpful. I just want to be able pass safetynet and my ctsProfile match fails. Which I can't even begin to work on without Magisk core.
Thanks in advance.
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Didgeridoohan said:
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Click to expand...
Click to collapse
Thanks for the quick reply!
How do I check to see where it's installed and/or reinstall it to the proper storage? Because that could be it.
There's no SD card or USB device plugged in and I couldn't find more information online (I even scoured didgeridoohan.com before posting here).
Also, and this may be helpful, it appears the device is not rooted. Fx file explorer and root checker apps confirm this. So it's possible even with the steps I followed that Magisk core really isn't installed and the apk is telling the truth (I'm just at a loss to know how that's possible after flashing the zip and flashing the patched boot file, both in twrp).
If you have no SD card installed adoptable storage won't be an issue.
You can easily verify through TWRP if the core Magisk files have been installed. Check in /data/adb/magisk. It should contain busybox, magisk, magiskboot and magiskinit binaries, together with addon.d, boot_patch and util_functions scripts.
Seeing the recovery log from when you attempt to install the Magisk zip in TWRP might show us something. Also try the could also be a good idea trying the Canary release to see if there's any difference from stable v20.4.
(This thread can be locked/(closed?)/answered)
I tried my damnedest and nothing worked. So I wiped/formatted lineage-17.1-20200512 and installed lineage-17.1-20200419. THIS was the ease with which I was accustomed to installing Magisk (Recovery install and immediately working on boot). Sadly, other problems abound and they are outside the scope of this subforum.
Just in case anyone reads this and cares:
- GPS Joystick was a no-go because apparently Lineage has a not-so-nifty feature that blocks the "draw over apps" android feature if your RAM is below some secret threashhold, which prevents the entire app from functioning.
- Fake GPS can take getting used to, and I'm used to it and love it, but the location and routing keeps crashing in the background, which means pogo closes when I tab back to start it back up again.
- Regardless of which I use I am rubberbanding back to my house... despite using all the tricks I can find or think of (yes, including 'smali patcher', specific app settings, systemizing the GPS app, setting off/on mock locations, etc)... but I think it's because this OS has no unique setting for the GPS data to be "device only".
Problems one and two are due to the ****ty ram on this Samsung tablet, which I've always known was an issue, so I suppose it might just be time to buy a phone specifically for this purpose. From what I read, the best cost effective option is an iPhone SE, and I'm truly not an Apple fan (I certainly would not risk my own phone being bricked or even merely wiped).
Not sure how I used it for the last year without this many issues, but it seems like that's over now unless I want to deal with DirtyUnicorn OS again, and that was it's own nightmare sometimes.
Thanks all for reading, but especially Didgeridoohan for replying and for all the resources on your pages and threads.
Hi, first time posting to XDA and I'll try to be concise, but I am tremendously confused and quite frightful of having to reflash/factory reset my entire device.
I got Magisk 6.1.0(165) after my Xposed Framework became more of a problem than a solution a long time ago, with a basic desire of rooting my device to control what apps boot at launch and examine Wakelocks and run an ad blocker.
For a long time, I did not update after the headache of clearing Safetynet and getting things functional.
Magisk prompted me to update, and I decided to after I had installed a few new apps that I now wanted to block from running on boot, but I never got around to finding a method to prevent apps from loading at startup like I desired with Xposed, i previously just disabled or uninstalled the problematic apps.
Before updating, I used TWRP to run a backup and rebooted.
After the update, Magisk informed me that the latest version i had updated to, was not supported and that it would behave asif it wasn't installed at all... Great...
I downloaded the zip to my device's SD card, and after a reboot noticed that I had Two installs of Magisk. When I held the icon to view app info, one of them would behave as I expected, and the other would show me additional options like modules, downloads, superuser and hide.
When I opened the second copy of Magisk, the first one vanished from my applications tray and cannot be found anymore, and Magisk now shows it's green checkmark next to Latest Version v20.4 and Installed Version 17.1 but Safetynet gives me an API error.
Clicking Update Magisk Manager from the menu offers to install v7.5.1(267) but I am wary enough that I am unsure if I should proceed and am not even sure if Magisk has a module that I am looking for-- Something to control what apps launch on startup.
Will updating Magisk Manager show a new list of additional modules to be downloaded and perhaps something that I am looking for? Should I be worried about bootlooping my device and needing to reset it?
I once used the Boot Manager found on the Xposed Framework, but it's long since become non-functional and became the reason why I simply uninstalled what was bothering me, but now I want to keep the new applications that I have and disable their bootup on start.
Is Magisk the place that I should be looking for such a feature?
Running a Samsung GalaxyS5.
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.