Related
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible :crying: Thanks for help
b*_gently_*d said:
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible [emoji14] :crying: Thanks for help
Click to expand...
Click to collapse
In rootcloak, did you specifically add the securego app to it's block list?
Sent from my SCH-R220
Hi there!
Yes, in "RootCloak Plus", the entry de.fiducia.smartphone.android.securego.wl does exist.
There's another confusing circumstance: I don't know how to launch the Xposed Installer programme. The only way - for me right now - is to navigate to "downloads", and then to re-install some downloaded *.apk as an update. Then, and only then, I'm inside the Xposed Installer.
Under "Remove native root detection for apps", the box "SecureGo" is checked.
b*_gently_*d said:
Hi there!
Yes, in "RootCloak Plus", the entry de.fiducia.smartphone.android.securego.wl does exist.
There's another confusing circumstance: I don't know how to launch the Xposed Installer programme. The only way - for me right now - is to navigate to "downloads", and then to re-install some downloaded *.apk as an update. Then, and only then, I'm inside the Xposed Installer. [emoji14]
Under "Remove native rott detection for apps", the box "SecureGo" is checked.
Click to expand...
Click to collapse
In your app drawer (if Xposed is properly unstalled) should be the Xposed app. After you install an Xposed module you have to activate the module in the Xposed app and reboot for it to work. Sounds like that hasn't been done. How did you install Xposed?
Sent from my SCH-R220
OK, let's have a look: I've got a sort of menu that is pushed from the left side into the app "Xposed modules". Within this menu drawer, there's: Modules, Install Xposed Framework, More modules, Root, XDA, latest 24 hours, all unread, all marked, downloads, synchronise now, settings (translated from German).
The apps "Xposed modules" and "RootCloak" are installed from stalk Google Play Store.
The device was restarted several times, and from a certain moment on, everytime it started, I had to confirm elevated privileges (for rootcloak).
:angel:
b*_gently_*d said:
OK, let's have a look: I've got a sort of menu that is pushed from the left side into the app "Xposed modules". Within this menu drawer, there's: Modules, Install Xposed Framework, More modules, Root, XDA, latest 24 hours, all unread, all marked, downloads, synchronise now, settings (translated from German).
The apps "Xposed modules" and "RootCloak" are installed from stalk Google Play Store.
The device was restarted several times, and from a certain moment on, everytime it started, I had to confirm elevated privileges (for rootcloak).
:angel:
Click to expand...
Click to collapse
Ok, that doesn't sound can you post a screenshot of what you are talking about including the list of modules installed in Xposed?
Sent from my SCH-R220
Pardon. What does it sound like? :cyclops: Anyway, I was wrong about the Installer. I actually can access it. But I still can't launch SecureGo properly. I'm posting a *.zip file containing a log and several shots.
b*_gently_*d said:
Pardon. What does it sound like? :cyclops: Anyway, I was wrong about the Installer. I actually can access it. But I still can't launch SecureGo properly. I'm posting a *.zip file containing a log and several shots.
Click to expand...
Click to collapse
Sorry, didn't notice the typo, it looks like you are using and old version of Xposed and a BETA version of rootcloak, have you tried the stable version?
Sent from my SCH-R220
Let's have a look on what has changed:
uninstalled the beta and experimental versions
now, there's only one "RootCloak" v2.1.1 (and no longer a "RootCloak Plus" next to it), downloaded and installed from "Xposed Installer"
downloaded and installed the *.apk of "Xposed Installer" v2.6.1
I took the version numbers from the Android OS settings menu
the icon for "Xposed Modules" is no longer shown
however, I did not remove SecureGo while making changes.
I didn't have to grant elevated privileges (only when Xposed Installer installed RootCloak)
I'm posting the latest log-file!
Still not working ...
b*_gently_*d said:
Let's have a look on what has changed:
uninstalled the beta and experimental versions
now, there's only one "RootCloak" v2.1.1 (and no longer a "RootCloak Plus" next to it), downloaded and installed from "Xposed Installer"
downloaded and installed the *.apk of "Xposed Installer" v2.6.1
I took the version numbers from the Android OS settings menu
the icon for "Xposed Modules" is no longer shown
however, I did not remove SecureGo while making changes.
I didn't have to grant elevated privileges (only when Xposed Installer installed RootCloak)
I'm posting the latest log-file!
Still not working ...
Click to expand...
Click to collapse
Have you taken a look at this, maybe this could help : http://forum.xda-developers.com/showthread.php?t=3450396
Sent from my SCH-R220
Quoting the article linked above: "Requirements ... Android 6.0" ... Don't know if an OS-installation would defeat the object ...
b*_gently_*d said:
Quoting the article linked above: "Requirements ... Android 6.0" ... Don't know if an OS-installation would defeat the object ...
Click to expand...
Click to collapse
It would allow you to utilize this workaround
Sent from my SCH-R220
I don't even see the mere possibility to install Android 6 ... Or do you detect anything on the specific page?
b*_gently_*d said:
I don't even see the mere possibility to install Android 6 ... Or do you detect anything on the specific page?
Click to expand...
Click to collapse
b*_gently_*d said:
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible [emoji14] :crying: Thanks for help
Click to expand...
Click to collapse
Check the thread for your device, a quick Google search shows some MM ROMs for your GT-I9070P
Sent from my SCH-R220
still failure
Inspired by your previous posts and having followed your advice, I now have a phone running Android 6.0.1 Marshmallow.
I tried to install Suhide and SuperSU systemlessly [?] (or at least I think, I did it that way because I was in Recovery Mode/TWRP. There, I simply clicked "install" and did nothing but install both zip-files.
The line that stated, that a boot image had not been found and therefore the process was aborting patching the boot.img, attracted my attention.
Within the restarted Android-OS, I never found an app icon for SuperSU or Suhide. Nevertheless, I found out SecureGo's UID (10xxx) and gave the following command:
Code:
/data/adb/suhide-add 10xxx
for adding SecureGo to the blacklist.
But nothing has changed ... SecureGo still denies its job.
b*_gently_*d said:
Inspired by your previous posts and having followed your advice, I now have a phone running Android 6.0.1 Marshmallow.
I tried to install Suhide and SuperSU systemlessly [?] (or at least I think, I did it that way because I was in Recovery Mode/TWRP. There, I simply clicked "install" and did nothing but install both zip-files.
The line that stated, that a boot image had not been found and therefore the process was aborting patching the boot.img, attracted my attention.
Within the restarted Android-OS, I never found an app icon for SuperSU or Suhide. Nevertheless, I found out SecureGo's UID (10xxx) and gave the following command:
Code:
/data/adb/suhide-add 10xxx
for adding SecureGo to the blacklist.
But nothing has changed ... SecureGo still denies its job.
Click to expand...
Click to collapse
Check the suhide thread, other people have the same sort of issue, in that you are using CM SuperSU that is not systemless, need to disable it for systemless su to work
Sent from my SCH-R220
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Do I need ADB installed? I'm asking because it appears in the commands.
I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
b*_gently_*d said:
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
Click to expand...
Click to collapse
Yes, at least how it's implemented in the ROM
[*]I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Click to expand...
Click to collapse
Is your Busybox up to date?
[*]Do I need ADB installed? I'm asking because it appears in the commands.
Click to expand...
Click to collapse
If you have to issue these commands from your computer to the phone you would need ADB on your computer. Is ADB turned on in developer options?
[*]I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
Click to expand...
Click to collapse
Did you type su in Terminal Emulator?
[*]But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Give me some time, I'll do a backup and see what you are seeing.
Sent from my SCH-R220
---------- Post added at 12:33 PM ---------- Previous post was at 12:11 PM ----------
b*_gently_*d said:
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Do I need ADB installed? I'm asking because it appears in the commands.
I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
Click to expand...
Click to collapse
In looking at Chainfire's thread to install Systemless root, I discovered that there are special boot.img files that need to be flash, my device is not on that list. But he does have some things that might shed some light on the issue.
1) Is your device one of the supported devices?
2) If so, did you do a clean flash? Did you flash the boot.img and su zips immediately? The thread says you need to make sure to flash the systemless stuff before the built in su does anything because the systemless flashing doesn't clean up other root implementations and can create problems. That's why it is mandatory for a clean flash of the ROM.
3) After you do all that, install the SuperSU app from the play store and see what happens
Sent from my SCH-R220
I don't know how to check whether Busybox is up to date or not (I was talking about the TWRP-Terminal outside Android-OS).
When I type 'su' into the Terminal Emulator - similarly to GNU/Linux -, I have no longer got the first line, but the second of the following:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $
(This is a true quote from my in-OS terminal.)
I'll have to look for those boot images and the list of the supported devices ... Or would you give me a direct link? (I already gave the exact name of my device.)
What exactly is a "clean flash", and which *.img or *.zips would have to be flashed? Do you mean something like from my own smarty history? From this list I basically only did step 4 when installing MM/CM13.
There's something else: Under "Developers' options/settings" (don't know how it is in English), you can choose between "never", "when debugging via USB" and "when loading". Has this something to say?
Please give me a short reply if I should perform the whole list of steps or similar or not because I don't want to waste time only to repeat it again and again
b*_gently_*d said:
I don't know how to check whether Busybox is up to date or not (I was talking about the TWRP-Terminal outside Android-OS).
When I type 'su' into the Terminal Emulator - similarly to GNU/Linux -, I have no longer got the first line, but the second of the following:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $
(This is a true quote from my in-OS terminal.)
I'll have to look for those boot images and the list of the supported devices ... Or would you give me a direct link? (I already gave the exact name of my device.)
What exactly is a "clean flash", and which *.img or *.zips would have to be flashed? Do you mean something like from my own smarty history? From this list I basically only did step 4 when installing MM/CM13.
There's something else: Under "Developers' options/settings" (don't know how it is in English), you can choose between "never", "when debugging via USB" and "when loading". Has this something to say?
Please give me a short reply if I should perform the whole list of steps or similar or not because I don't want to waste time only to repeat it again and again
Click to expand...
Click to collapse
http://forum.xda-developers.com/app...rshmellow-t3219344/post63197935#post63197935
Sent from my SCH-R220
I recently had a problem (see here) with SuperSU, so I decided to give MagiskSU a try. As it turns out, it seems to have the same issue. When I run a process that requires su, it stalls for a while. In the case of MagiskSU, I then get "Permission denied" after about 20 seconds.
Here's what I get with a few basic commands:
Code:
[email protected]:/ $ su
Permission denied
Code:
[email protected]:/ $ su -v
8:MAGISKSU (topjohnwu)
Code:
[email protected]:/ $ su -V
8
Additionally, when I view the log with adb logcat, I see the following message attributed to su:
Code:
exec am failed with 2: No such file or directory
It looks like this is a message produced here, related to loading am.jar. Unlike in my SuperSU situation, this error happens regardless of whether Magisk is set to "prompt" or "grant".
Any idea how I can debug this? Thanks in advance.
Just to make sure: Have you updated the Magisk Manager so that it's just not the stub installed by the Magisk zip?
And if so, does the Manager report you're properly rooted?
I figured it out. In a previous cleanup attempt, I failed to restore the link named /system/bin/app_process that points to /system/bin/app_process64. This fixed it:
From the TWRP terminal:
Code:
mount /system
cd /system/bin
ln -s app_process64 app_process
Frankly I'm surprised this didn't render my phone unbootable! Nothing else was noticeably affected.
I have the same problem, just logcat says:
W/Magisk: su: request rejected (2000->0)
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
I found in the Magisk app under Superuser that "shell" had the toggle turned off. Once I turned it on, su worked in ADB.
Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
You are my Hero...
:good::good::good:Thank You Very Much brooo... :good::good::good:
Hi all,
I have Magisk v18.1 and I'm also trying to get root access from shell. When I run 'su' in a terminal emulator, I get the message 'Permission denied'.
I did install "ADB & Fastboot for Android NDK" as suggested above. I also checked the root options in the magisk app (v7.0.0) and they are all the default, nothing unusual there.
Could you kindly advice if there is anything I can do in order to get root access from the shell with Magisk?
Thanks a lot in advance
I have a same issue on kitkat
Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!
geo909 said:
Oh boy, I have *absolutely no idea* what I did but it works now. Well, what I did was that I removed the adb & fastboot module and rebooted. When I ran 'su' again in the terminal, I got a request from magisksu to grant authorization. Not sure what's going on, but it works!
Click to expand...
Click to collapse
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.
madbat99 said:
Why did you install the ADB and fastboot module? That's for using that device to control ADB and fastboot of another device as if the device with the module were a computer.
Click to expand...
Click to collapse
Honestly, that was a classic case of not knowing what I'm doing and just blindly following what other people tried. But good to know what the purpose of that module was, I was wondering!
Hint: Perfdump is the adb shell program, do not disable SU for it
I add my hint: after getting this error message, I checkd the list of apps in Magisk SU: it turned out that I had disabled the "Perfdump" app, because I did not know what it was. It is the adb shell indeed!
I had exactly the same problem on my Android 6.0 with Magisk v19.3 + Magisk Manager v7.3.1. I tried everything, what you wrote (enabled, disabled the "ADB and fastboot" stuff, checked the symlink, ...), but nothing helped me. FYI: previously, I used LineageOS 16 (Android 9.0) on the same phone with this latest Magisk without any problem (but I decided to turn back to the original OS version to avoid instabilities). But now I'm fighting with this dragon.
My wife has Android 6.0 also w/ Magisk, but she got Magisk v18.0 and this works well now... I tried this at me, and surprisingly, that was worked well. Now, I decided to find out, which is the last working version, where is the bug.
The results:
* the Magisk v18.0 with the bundled Magisk Manager - GOOD
* the Magisk v18.0 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v18.1 with the latest Magisk Manager v7.3.2 - GOOD
* the Magisk v19.0 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.1 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.2 with the latest Magisk Manager v7.3.2 - BAD
* the Magisk v19.3 with the latest Magisk Manager v7.3.2 - BAD
I don't know, the freshest working Magisk v18.1 + Magisk Manager v7.3.2 is a good combination for all cases, but looks working.
Lletfrix said:
I found a solution that worked for me, go to Magisk Manager and install "ADB & Fastboot for Android NDK" module, then reboot.
Click to expand...
Click to collapse
Yup thanks it still works up to date
Solved
i had the same problem on my redmi note 7 and the most easiest way is unistall your magisk 20.xxx and install a older one 19.xxx and that should do it but remember bouth zip file (flashibile zip) and magisk apk has yo be older than 20.xxx becouse the devs has made a mistake in the coding( or at leat this is what i think hope im wrong)
just update the magisk manager and install automatically the boot and reboot the phone it will be okay
Solution that works for me GalaxyS9 (starlte)
### restart adbd as root
adb root
### then
adb shell
### WORKS.
### I see '#' in prompt, `whoami` responses: 'root'
### My Magisk version. Reported by `su -v`
23.0:MAGISKSU
Hi,
Freshly installed Magisk today. I have tried to install the 'Sony Framework' module from (Seyaru Module by eric9401 work).
However as title it says 'Module will be updated at next reboot'. I can disable the module, but the option to delete using the trashcan doesn't work either. Has anyone else come across this with any tips to resolve?
I am running a galaxy s8
Thanks
stephenwatson2010 said:
Hi,
Freshly installed Magisk today. I have tried to install the 'Sony Framework' module from (Seyaru Module by eric9401 work).
However as title it says 'Module will be updated at next reboot'. I can disable the module, but the option to delete using the trashcan doesn't work either. Has anyone else come across this with any tips to resolve?
I am running a galaxy s8
Thanks
Click to expand...
Click to collapse
Some modules require full uninstall and reboot before you update them (AML, for example). To fix this, you'll have to uninstall Magisk and reinstall it and the modules you want to use. Make sure you download the update and that it's in your magisk folder before you uninstall everything.
BIGWORM said:
Some modules require full uninstall and reboot before you update them (AML, for example). To fix this, you'll have to uninstall Magisk and reinstall it and the modules you want to use. Make sure you download the update and that it's in your magisk folder before you uninstall everything.
Click to expand...
Click to collapse
Or u can manually uninstall modules from twrp if u have magisk mount already flashed. And the u go to magisk directory and deleted individual modules. No need to uninstall/reinstall magisk.
This is how I fixed it. I had same trouble with AML
TahirZX said:
Or u can manually uninstall modules from twrp if u have magisk mount already flashed. And the u go to magisk directory and deleted individual modules. No need to uninstall/reinstall magisk.
This is how I fixed it. I had same trouble with AML
Click to expand...
Click to collapse
Thanks. I was able to uninstall the modules this way. I still can't get the Sony framework working but i will keep trying
Dang.
Maybe good tip. My busybox had a red update mark but it was kind of working. Then i disabled modul, by doing i saw network sign (!) is gone so i "dicided" to full uninstall magisk.
Now my phone hang on bootlogo.
Not sure how to restore with flashfire backup i dumped. Maybe possible to push/install magisk manager via adb?
No twrp atm just stock recovery^^
Fixed by flashing magisk custom boot.img which was used to get root but now not able to install busybox modul :/
Switched to SuperSu busybox now working.
stephenwatson2010 said:
Hi,
Freshly installed Magisk today. I have tried to install the 'Sony Framework' module from (Seyaru Module by eric9401 work).
However as title it says 'Module will be updated at next reboot'. I can disable the module, but the option to delete using the trashcan doesn't work either. Has anyone else come across this with any tips to resolve?
I am running a galaxy s8
Thanks
Click to expand...
Click to collapse
Mount magisk through twrp remove it and update m
stephenwatson2010 said:
Thanks. I was able to uninstall the modules this way. I still can't get the Sony framework working but i will keep trying
Click to expand...
Click to collapse
I think it could be the module's problem, try this one: https://forum.xda-developers.com/ap...apps-enabler-systemless-t3620100/post77621189
I am using oneplus 6 with latest oos magisk 19.3
Banking app like sbi anywhere, icici detecting root can't use upi.
Also adadhar app detecting root event safety net pass already done magisk hide
Can some help me there or use other versions of magisk
Please help
android_smater said:
I am using oneplus 6 with latest oos magisk 19.3
Banking app like sbi anywhere, icici detecting root can't use upi.
Also adadhar app detecting root event safety net pass already done magisk hide
Can some help me there or use other versions of magisk
Please help
Click to expand...
Click to collapse
Use Hide Magisk manager in settings or Core only mode.
Sent from my MI 8 using Tapatalk
Dexer125 said:
Use Hide Magisk manager in settings or Core only mode.
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
Didn't work either. I guess will have to wait for an update. I have tried so far:
Settings > Magisk Core Only More - On
Magisk Hide - Check against the banking app
Clear app cache
Reboot
Also - Magisk v19.3, Magisk Manager v7.3.1(222)
gagan007 said:
Didn't work either. I guess will have to wait for an update. I have tried so far:
Settings > Magisk Core Only More - On
Magisk Hide - Check against the banking app
Clear app cache
Reboot
Also - Magisk v19.3, Magisk Manager v7.3.1(222)
Click to expand...
Click to collapse
disable developer mode?
and you need to hide magisk manager itself.not just magisk hide.
Try executing
Code:
su -c chmod 000 /proc/net/unix
in a terminal. Several banking apps now use a very stupid and shaky root detection heuristic that is circumvented in this way.
(see https://github.com/Ingan121/UDSBypass).
A banking app on my phone (keytradebank, belgian bank) worked fine with Magisk Hide but after an update stopped working.
Disabling read access to /proc/net/unix did the trick for me!
Looked it up, this rootbeerFresh code is really brain-dead, even the presence of busybox will make isRooted() return true
No concern for false positives at all.
el_perro said:
A banking app on my phone (keytradebank, belgian bank) worked fine with Magisk Hide but after an update stopped working.
Disabling read access to /proc/net/unix did the trick for me!
Looked it up, this rootbeerFresh code is really brain-dead, even the presence of busybox will make isRooted() return true
No concern for false positives at all.
Click to expand...
Click to collapse
Remember that app says it COULD be root.
If anyone is paying attention to it yet.
Also
https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up
Busybox
Some apps detect Busybox and see this as a sign of your device being compromised (rooted). Magisk should be able to hide any Busybox installed as a Magisk module. osm0sis has a great Busybox module available in the Magisk repo (install from the Magisk Manager, under "Downloads").
Figuring out if an app has dependencies, looks for "sensitive props", Busybox, etc
It can be tricky figuring out if an app is dependent on another app or process for detecting root, expects certain prop values, doesn't like Busybox or whatever is triggering a root warning within the app. Apart from trying one thing/prop at a time, finding this out could mean you have to decompile the apk to look at the source code (use search), grab a logcat when the app is detecting root, etc.
Detecting apps requiring root
There are apps that detect known apps that require root and refuse to work properly or even start if that is the case. Usual suspects include (but aren't limited to) busybox apps, Xposed installer, root hiding apps, etc.
This can be worked around by uninstalling or possibly freezing (Titanium Backup can do this, among others) the offending root app when you need to use an app detecting root apps and reinstalling/unfreezing it afterwards. Cumbersome, but it might work. There are also some Xposed modules that can hide apps from other apps, but having Xposed installed might cause other issues with tampering detection...
@mrspeccy Thank you for pointing out that workaround. Works for me too for the Keytrade app
el_perro said:
A banking app on my phone (keytradebank, belgian bank) worked fine with Magisk Hide but after an update stopped working.
Disabling read access to /proc/net/unix did the trick for me!
Looked it up, this rootbeerFresh code is really brain-dead, even the presence of busybox will make isRooted() return true
No concern for false positives at all.
Click to expand...
Click to collapse
How did you do that?
su -c chmod 000 /proc/net/unix didn't work for me.
robuser007 said:
How did you do that?
su -c chmod 000 /proc/net/unix didn't work for me.
Click to expand...
Click to collapse
yes, in a terminal on your phone or using 'adb shell'
be aware it's not a permanent fix, a reboot will restore the old permissions on /proc/net/unix
so you have to remove read access after every reboot.
Quite clumsy.
To make this easier on the go, I installed termux, created in the home directory a small file 'hide' with the one-liner,
Code:
su -c chmod 440 /proc/net/unix
Note: 000 works just as well, but 440 is closer to the original permission and works too.
so after a reboot i open termux terminal and type the command
Code:
. hide
gagan007 said:
Didn't work either. I guess will have to wait for an update. I have tried so far:
Settings > Magisk Core Only More - On
Magisk Hide - Check against the banking app
Clear app cache
Reboot
Also - Magisk v19.3, Magisk Manager v7.3.1(222)
Click to expand...
Click to collapse
Thanks it work...
Got that app working successfully today. Hiding Magisk itself worked I guess. I locked bootloader also.
android_smater said:
I am using oneplus 6 with latest oos magisk 19.3
Banking app like sbi anywhere, icici detecting root can't use upi.
Also adadhar app detecting root event safety net pass already done magisk hide
Can some help me there or use other versions of magisk
Please help
Click to expand...
Click to collapse
Try these...
1. From your magisk, install these 2 modules: Riru - Core, and Riru - EdXposed (Sandbox or Yahfa is okay]
2. Reboot your device to activate both modules.
3. Install Xposed Installer APK by DVDandroid. You can get it here: https://dl-xda.xposed.info/modules/d...v33_36570c.apk
4. Reboot to activate the Xposed Installer app
5. Inside Xposed Installer app, go to downloads and install the HiddenCore Module.
6. Reboot and go back to Magisk, and hide.
7. Test to see if everything is now okay.
wittymav said:
Try these...
1. From your magisk, install these 2 modules: Riru - Core, and Riru - EdXposed (Sandbox or Yahfa is okay]
2. Reboot your device to activate both modules.
3. Install Xposed Installer APK by DVDandroid. You can get it here: https://dl-xda.xposed.info/modules/d...v33_36570c.apk
4. Reboot to activate the Xposed Installer app
5. Inside Xposed Installer app, go to downloads and install the HiddenCore Module.
6. Reboot and go back to Magisk, and hide.
7. Test to see if everything is now okay.
Click to expand...
Click to collapse
Nope! It Doesn't Work With SBI YONO Or BHIM.
My Cofidis app also keeps detecting root.
Have latest version magisk, latest version of magiskmanager and renamed it. Magisk is hidding. App is in magisk hide list.
chmod suggestion did not work
Running latest version of lineageos on my htc u11. I think the issues started when I installed the latest build (11/08).
Any suggestions to fix this?
Same issue here with this app:
https://play.google.com/store/apps/details?id=eu.mobeepass.nfcniceticket
Is there any way to troubleshoot what triggers the root detection?
Ps24u said:
Same issue here with this app:
https://play.google.com/store/apps/details?id=eu.mobeepass.nfcniceticket
Is there any way to troubleshoot what triggers the root detection?
Click to expand...
Click to collapse
Using my app VD INFOS you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
And then you can fix what needs to be fixed.
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com
So, an OTA caused a loss of root (pixel 6 pro, unlocked). Tried to go into a hidden magisk and disable modules, but everything greyed out, unable to. Tried to uninstall the manager (I was using an old MagiskAlpha build), and thought it worked, though it must have left something behind. Updating wouldn't work - would give me a failure.
Flashed new factory image, installed new magisk manager, patched boot.img in new magisk manager, loaded boot.img, and I have root; adb shell su works, all my old apps that worked with root work, but no magisk manager recognizing that I have root - and therefore no modules - working. So, no charging management, safetynet is borked, etc. Have uninstalled/reinstalled mm numerous times. No luck. Tried loading it from adb, etc.
I've dug through adb shell pm list packages and can't find anything that looks like an old version of magisk at all anywhere anymore. I think I had three different versions on the phone. They are all gone. But no luck with a freshly installed manager. Still can't see root even though it's there. Any ideas?
Of note: I have a work profile and two users on the phone. However, I can't find anything even using --user for all three users. Only thing even close I see is com.lsposed.manager still installed. That shouldn't be a factor, but I can't think of anything at this point.
TB checker, under "check root" gives pass for everything except SU binary, 2nd SU binary, root via native, and magisk specific.
Under Check xposed, I have fail for dual/work profile and xprivacyLua, and com.topjohnwu.magisk under PM Sundry APIs. Everything else is Pass.
I had never granted TB checker root before; Termux on the other hand works fine with su (as does adb shell), and Root Essentials shows root fine.
Magisk Manager was downloaded from topjohnwu's github, then I manually added the canary URL, and updated to canary. No luck.
Any other ideas?
One other thing... /data/adb/magisk was dated; all the other directories in /data/adb were new, but magisk was from my last update of MagiskAlpha, and when I looked at util_functions.sh it was aligned to my old (uninstalled) magisk alpha build
So, the /data/adb/magisk tipped me off. I pulled the hidden apk info from the magisk.db, and from there was able to (while rooted) manually delete all the references to the hidden apk string (just did a find /data/* | grep [hidden package name] ) and once they were all deleted, deleted everything from /data/adb - the magisk.db and everything - and then next time I went into magisk, it informed it was incorrectly configured, I pressed okay, it fixed itself, and full root in magisk was restored.
had to reinstall all modules, but that wasn't a very big price to pay. Safetynet fixed (google pay worked just fine at the store yesterday), xprivacylua, etc., all worked.
As of right now, other than a citi app *****ing that I'm possibly rooted (and then it still works fine anyway), haven't had any issues with leaving magisk unhidden, so not going to hide it again unless I need to. Wasn't worth the PITA to fix it if something like this happens again.