Related
Hi all,
So I've just flashed Oxygen OS 4.0.1 for the OnePlus3T, flashed SuperSU 2.79, downloaded Magisk from playstore, installed it, uninstalled SuperSU app. Root is working fine
Two green ticks, installed and properly rooted, but the SafteyNet failes. I read that you need to enable Magisk hide, so I do, and it tells me to reboot, so again I do, but the option keeps resetting/.
Anyone else having this issue/ has a solution?
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Edit: New info added to OP after my answer... Magisk Hide does not work with SuperSU.
Didgeridoohan said:
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Click to expand...
Click to collapse
That's a shame ./. I'll ask reddit
Thanks
I'm using phh's superuser and Magisk hide is working for me on the open beta and people seem to say that the current beta and the release versions are virtually the same, so it might be an issue with how SuperSU is handled.
afaik Magisk Hide needs phh's root, not SuperSU
Snappiestjack said:
Hi all,
So I've just flashed Oxygen OS 4.0.1 for the OnePlus3T, flashed SuperSU 2.79, downloaded Magisk from playstore, installed it, uninstalled SuperSU app. Root is working fine
Two green ticks, installed and properly rooted, but the SafteyNet failes. I read that you need to enable Magisk hide, so I do, and it tells me to reboot, so again I do, but the option keeps resetting/.
Anyone else having this issue/ has a solution?
Click to expand...
Click to collapse
Ok... I believe you've added some information since my first answer...
Magisk Hide does NOT work with SuperSU. You have to use topjohnwu's phh's superuser that's provided with Magisk.
Didgeridoohan said:
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Click to expand...
Click to collapse
Nope, nope, nope. It's a problem with USERS who use magisk hide options. In THREAD is info about supersu + magisk hide = NOT WORKING. This is only fault of wrong su binaries, so it's not device specific issue.
And for this issue - probably flash a unsu script. It will (probably) delete all of supersu files, then in magisk manager or twrp flash modded phh binaries for magisk and then, finally install ph manager from google play. That is config to be able to use magisk hide.
ENJOY.
mucha.k1994 said:
Nope, nope, nope. It's a problem with USERS who use magisk hide options. In THREAD is info about supersu + magisk hide = NOT WORKING. This is only fault of wrong su binaries, so it's not device specific issue.
And for this issue - probably flash a unsu script. It will (probably) delete all of supersu files, then in magisk manager or twrp flash modded phh binaries for magisk and then, finally install ph manager from google play. That is config to be able to use magisk hide.
ENJOY.
Click to expand...
Click to collapse
Yeah, I know... OP edited with SuperSU info after my answer. I edited my post as well. Thanks for the reminder.
Not going to quote everyone, but YES! Removing SuperSU and using phh SU works just fine!
Thanks all.
On my Samsung Galaxy J5 (2016) DUOS with "6.0.1 J510xx SkiesROM UX Note7 Port (by KingRaheel)", Magisk Manager 5.3.0 crashes with Magisk 14.0 and BusyBox installed, even latest osm0sis 1.27.2, regadless if installed as module from inside Magisk Manager or via UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip. Crashes remain with all other forks/ ports of BusyBox I tried.
After installing Magisk 13.3 via TWRP, Magisk Manager 5.3.0 is stable again as it should, even with BusyBox.
Only other Magisk module installed: VIPER4AndroidFX
Can not run a Magisk Beta on this phone, sorry.
Anybody else?
Use Magisk busy box from download in Magisk Manager
RootedLee said:
On my Samsung Galaxy J5 (2016) DUOS with "6.0.1 J510xx SkiesROM UX Note7 Port (by KingRaheel)", Magisk Manager 5.3.0 crashes with Magisk 14.0 and BusyBox installed, even latest osm0sis 1.27.2, regadless if installed as module from inside Magisk Manager or via UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip. Crashes remain with all other forks/ ports of BusyBox I tried.
After installing Magisk 13.3 via TWRP, Magisk Manager 5.3.0 is stable again as it should, even with BusyBox.
Only other Magisk module installed: VIPER4AndroidFX
Can not run a Magisk Beta on this phone, sorry.
Anybody else?
Click to expand...
Click to collapse
Have you tried clearing data for the Manager? Many issues with the Manager can be fixed by that... If it doesn't work: logcat.
chudy_85 said:
Use Magisk busy box from download in Magisk Manager
Click to expand...
Click to collapse
even latest osm0sis 1.27.2
Click to expand...
Click to collapse
That is the busybox from the repo...
chudy, as I wrote, that's what I had first used.. when that caused MM 5.3.0 to crash w/ M 14.0, I also tried osm0sis' installer from the repo - no difference.
chudy_85 said:
Use Magisk busy box from download in Magisk Manager
Click to expand...
Click to collapse
Didgeridoohan said:
Have you tried clearing data for the Manager? Many issues with the Manager can be fixed by that...
Click to expand...
Click to collapse
yes, tried. Otherwise I would not dare to post here
Didgeridoohan said:
If it doesn't work: logcat.
Click to expand...
Click to collapse
OK, will figure out how to look at the log.
Didgeridoohan said:
That is the busybox from the repo...
Click to expand...
Click to collapse
interestingly it shows up in MM under modules the same way as when installed through MM Download, so I guess the functionality and system wide availability is the same, too (?)
Hi, I have a huawei p8 lite 2017 with magisk installed on it. I installed the systemless xposed module and then opened xposed installer. It says it's installed and working, but I don't have any logs, and modules are not working.
Use official Xposed by @rovo89. It's working even if you have systemless root. Cheers.
Sent from Redemi 4X Qualcomm arm 64 (Resurrection Remix based on OS 7.1.2)
I have to uninstall the module from magisk and install normal xposed via recovery, right ?
Edit: installed it via xposed installer. Same problem, it says it's active but my logs are empty and modules don't work.
andreyshch said:
I have to uninstall the module from magisk and install normal xposed via recovery, right ?
Edit: installed it via xposed installer. Same problem, it says it's active but my logs are empty and modules don't work.
Click to expand...
Click to collapse
Silly question but have to ask. Modules are activated and you rebooted? [emoji16]
Anyhind, never used systemless Xposed but I do know there's a specific Magisk(?) version of the installer app that might be more suitable. Check the systemless Xposed thread. The apk download is in the OP.
[2018.5.6][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27) -
https://forum.xda-developers.com/showthread.php?t=3388268
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
Yes, installed the modules, activated them and rebooted. I uninstalled the systemwide version and installed the normal one, still have te same problem. Any idea?
andreyshch said:
Yes, installed the modules, activated them and rebooted. I uninstalled the systemwide version and installed the normal one, still have te same problem. Any idea?
Click to expand...
Click to collapse
Did you give xposed installer storage and root permissions
Yes!
I recently rooted my new Mi A2 Lite using Magisk.
So my current banking app detected the root and now I cannot use it anymore. I tried Root Cloak and MagiskHide but both of them did not work either. It still shows the message saying my phone is rooted.
How do I debug that now. I need it to be working anyhow.
App: K-Plus; play.google.com/store/apps/details?id=com.kasikorn.retail.mbanking.wap
https://didgeridoohan.com/magisk/MagiskHideHidingRoot
arunsharmaofficial said:
I recently rooted my new Mi A2 Lite using Magisk.
So my current banking app detected the root and now I cannot use it anymore. I tried Root Cloak and MagiskHide but both of them did not work either. It still shows the message saying my phone is rooted.
How do I debug that now. I need it to be working anyhow.
App: K-Plus; play.google.com/store/apps/details?id=com.kasikorn.retail.mbanking.wap
Click to expand...
Click to collapse
I recently had the same problem, but with a different banking app.
What helped me in the past was to hide Magisk Manager with a random package name. It is an option in Magisk Manager itself. Unfortunately it doesn't work anymore but i could mask Magisk Manager with the Samsung app S Secure and now it's working again .
This was included in my Galaxy S7 ROM so you probably need to find the apk for the app or find a similiar working app for your phone model.
Hope this helps.
Daci54 said:
I recently had the same problem, but with a different banking app.
What helped me in the past was to hide Magisk Manager with a random package name. It is an option in Magisk Manager itself. Unfortunately it doesn't work anymore but i could mask Magisk Manager with the Samsung app S Secure and now it's working again .
This was included in my Galaxy S7 ROM so you probably need to find the apk for the app or find a similiar working app for your phone model.
Hope this helps.
Click to expand...
Click to collapse
Alright! Can you clarify what on how to hide Magisk with a different package name. I am still pretty new to Magisk. Thanks.
arunsharmaofficial said:
Alright! Can you clarify what on how to hide Magisk with a different package name. I am still pretty new to Magisk. Thanks.
Click to expand...
Click to collapse
Open Magisk Manager, go to settings and tap on Hide Magisk Manager. If your banking app doesn't work right away try a restart. If it still doesn't work try to mask Magisk Manager with S Secure or similiar apps.
The magisk hide feature does not work
nm180618 said:
The magisk hide feature does not work
Click to expand...
Click to collapse
It does work, the steps I took were:
1) Install Banking app
2) Open it and get notified about the phone being rooted
3) Use Magisk Hide feature to hide the Banking app
4) Go to phone's app settings
5) Baking app settings
6) Clear storage data (Clearing only the cache could work too, I didn't test it)
7) Profit!
Hope that works for you.
Magisk hide doesn't seem to be working for me. Magisk says it's working and safety net passes, but I've tested multiple apps and they can see that I'm rooted. Hiding magisk with a random package name doesn't work either.
Yesterday I installed magisk and went to hide options and checked my banking app. I was amazed to see banking app allowing me to do everything without limited functionality due to "root" like before. But today banking app detected root again and limited all functions, how? There haven't been any updates for banking app yet it seemed to no longer be fooled by magisk.
Same goes for me with the K-Plus app as well. (สวัสดีคับผม) Use Magisk Hide to hide the root access but it crashes the bank app instead.
Not sure what I've missed.
Gpay and banking are still detecting root/custom rom
Magisk and manager installed.
module SaMoDXv1 installed.
Safteynet is showing green
gpay and banking apps hidden
Using hide magisk function
removed all Magisk related stuff from SD card.
Cleared cache from gpay and banking apps .
Turned off usb debugging.
What else is there?
Just installed root checker basic, it sees root. I hide magisk from it and it still sees root. Is that right?
beythas said:
Same goes for me with the K-Plus app as well. (สวัสดีคับผม) Use Magisk Hide to hide the root access but it crashes the bank app instead.
Click to expand...
Click to collapse
Try following the 'Promon' section in https://github.com/Ingan121/UDSBypass
Hi,
I'ould like installing Fde.ai on my One plus 6 rooted with Ice Renovate 11.1 rom, but I'm not sure that installation is compatible with "Rice tweaks", a tweak app for this rom no my device.
Peraphs there is someone who does know the answer?
Tks and regards.
Roberto
What I do
Go to setting -> Magisk Hide -> disable then enable.
This way worked with me .
I used Magisk Manager v 7.2.0 (213).
Magisk v 19.3 (19300).
What worked for me is using the "Hide Magisk Manager" feature in settings. Now apps are not promoting about device being rooted and are running fine now.
Anyone solved this problem?
I still have a banking app with this problem. I tried many times but still not working.
Magisk hide dont work for this app.
nguyenlinh said:
Anyone solved this problem?
I still have a banking app with this problem. I tried many times but still not working.
Magisk hide dont work for this app.
Click to expand...
Click to collapse
So far there are very few apps that I've seen that can not be tricked with tips from the guide linked in the second post of this thread. Give it a shot...
Can you try it?
https://play.google.com/store/apps/details?id=vietcombank.itcenter.smartotpcorp
I Cannot run this app.
Thanks
nguyenlinh said:
Can you try it?
https://play.google.com/store/apps/details?id=vietcombank.itcenter.smartotpcorp
I Cannot run this app.
Thanks
Click to expand...
Click to collapse
Runs fine with the app on the Hide list and the Magisk Manager repackaged with a random name.
More:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Can someone check this for me?
https://play.google.com/store/apps/details?id=no.apps.dnbnor&hl=en_US
Iam using MH v60 with 19.3 still nothing. Iam fighting with that about 4 months now((((
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
If you can pass SafetyNet (cts profile) try to hide :
Magisk Manager with a random name (mandatory) ... and "Your banking app" must be hidden too along with Google Services of course !
There are currently several ways of detecting Magisk that MagiskHide can't circumvent.
If the app isn't using one of those (if it is you'll just have to wait for a possible update to Magisk), you can find some tips and tricks here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Magisk cannot hide:
Other known root apps (see "Detecting apps requiring root"). (Shouldn't be a problem since even with a renamed manager and magisk unflashed it still works.)
Remnants of previous root method, including any root management apps (a good way to remove most remnants of root is osm0sis unSU script). (Magisk is unflashed and app immediately works.)
Unlocked bootloader (see Unlocked bootloader). (Magisk is unflashed and bootloader unlocked, app still works. I also tried custom rom and the stock rom.)
A tripped Samsung Knox counter. (Not a samsung phone.)
Xposed (deactivate it or uninstall). It doesn't matter if it's systemless, Magisk can't hide it. (Never used.)
EdXposed. Detection of EdXposed can sometimes be worked around with newer release of EdXposed and/or features like the EdXposed Manager blacklist. (Never used.)
USB/ADB Debugging (disable under Developer options in Android settings). (Magisk unflashed and debugging on, app works.)
Developer options. (Magisk unflashed and developer options is on, app works.)
Some Magisk modules - Depending on what the module does, it may not be able to be hidden by MagiskHide. (Tried core only mode which should disable all modules, still don't work.)
Some modifications to /system. Make sure to use Magisk modules... (I'm not sure what this means :c)
From that list it looks like it's something from Magisk itself that's tripping the detection :/
Im going bald from this.
IcY~ said:
From that list it looks like it's something from Magisk itself that's tripping the detection :/
Im going bald from this.
Click to expand...
Click to collapse
If you've tested and confirmed everything else, it is very likely that the app is using a detection method that Magisk currently can't hide from.
Solution? Wait for @topjohnwu to possibly update Magisk/MagiskHide (alternatively, don't install Magisk). When? Whenever he feels like it...
Didgeridoohan said:
If you've tested and confirmed everything else, it is very likely that the app is using a detection method that Magisk currently can't hide from.
Solution? Wait for @topjohnwu to possibly update Magisk/MagiskHide (alternatively, don't install Magisk). When? Whenever he feels like it...
Click to expand...
Click to collapse
https://github.com/topjohnwu/Magisk/issues/2406
Looks like someone posted a potential fix. Will wait for it to reach the master branch!
Have you find the workaround? I am using the same app and face same problem. This app last update gives headache
I am hidding root and edxposed using Island and installing intune inside the sandbox. Maybe the same will be with bank apps.
@kubis111
i'm happy for you, but please...this isn't your thread so do not OOT, OP problem isn't solving yet
---------- Post added at 11:46 AM ---------- Previous post was at 11:03 AM ----------
Tomek0000 said:
I am hidding root and edxposed using Island and installing intune inside the sandbox. Maybe the same will be with bank apps.
Click to expand...
Click to collapse
can you share the apps link?
Any updates on this banking app? I've tried many TaiChi Magisk, Sudohide and Zuper module but no success.
ctsProfile all green, Rootbeer Fresh all green.
citi app also detected my rooted device( Mi 8 Pro) after update , even hide the App ..useless....
Heatexplorer said:
citi app also detected my rooted device( Mi 8 Pro) after update , even hide the App ..useless....
Click to expand...
Click to collapse
Had the same problem. Updated magisk manager and fixed it (even before updating my modules).
Anyone lucky on it? What about BBVA Spain app?
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Have you found a solution? With latest Permata and Magisk (23) the banking app still does not work...
timofonic said:
Anyone lucky on it? What about BBVA Spain app?
Click to expand...
Click to collapse
For me work
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Found a solution, but can't publish yet. Excuse me
Spartacus500 said:
Found a solution, but can't publish yet. Excuse me
Click to expand...
Click to collapse
Why?
hallo dare said:
Why?
Click to expand...
Click to collapse
So I ran the test quickly and it turns out that it works, for those who are interested, I will provide a solution, but a little later.
I managed to make it work,
Spartacus500 said:
For me work
Click to expand...
Click to collapse
Spartacus500 said:
For me work
Click to expand...
Click to collapse
No idea how. I'm worried about that Knox logo these days, but we'll..
Thanks!
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Sorry to be just now, but to the point of solution to this,
1. Install the disable services app and disable a process called "S17"
2. Done