Please can someone help I am using magisk to hide root and this was working great on lineage os 8.1. Due to a few problems I changed Roms to aosp android 9.0. I have installed magisk and the safetynet check shows it is working fine. However all the banking apps such as Halifax and Barclays are detecting the device is rooted even though they have been selected in Magisk.
Please can someone help with finding a fix for this.
Check if su exist
Hi,
To detect root may your bank app checks if these files exists on the system :
Code:
/system/app/Superuser.apk
/sbin/su
/system/bin/su
/system/xbin/su
/data/local/xbin/su
/data/local/bin/su
/system/sd/xbin/su
/system/bin/failsafe/su
/data/local/su
/su/bin/su
Check by yourself if these files don't exist to be sure that root is really hide...
The files do not exist on my device
ariaz786 said:
Please can someone help I am using magisk to hide root and this was working great on lineage os 8.1. Due to a few problems I changed Roms to aosp android 9.0. I have installed magisk and the safetynet check shows it is working fine. However all the banking apps such as Halifax and Barclays are detecting the device is rooted even though they have been selected in Magisk.
Please can someone help with finding a fix for this.
Click to expand...
Click to collapse
I gave up with this myself, the only way is to use the banks main sites with a good browser.
Related
I know, a lot of you are shaking your head after seeing the title lol. But I am trying to use DSploit on my home network, I saw that I need busybox fully installed on my device. So I downloaded it, installed it by opening the app and hitting install. Nothing seems to be working still. I keep seeing something about using commands or something. I am more or an iOS guy so I'm not an expert on android. Can anyone help me get DSploit/Busybox working?
Thanks!
tpayne174 said:
I know, a lot of you are shaking your head after seeing the title lol. But I am trying to use DSploit on my home network, I saw that I need busybox fully installed on my device. So I downloaded it, installed it by opening the app and hitting install. Nothing seems to be working still. I keep seeing something about using commands or something. I am more or an iOS guy so I'm not an expert on android. Can anyone help me get DSploit/Busybox working?
Thanks!
Click to expand...
Click to collapse
remove busybox then reinstall it, download a busybox checker app to verify this is working on your phone, if it is its the DSploit app thats encountering problems, if its not working on your phone download a different installer and install a ew different versions of busy box on your device
ricky310711 said:
remove busybox then reinstall it, download a busybox checker app to verify this is working on your phone, if it is its the DSploit app thats encountering problems, if its not working on your phone download a different installer and install a ew different versions of busy box on your device
Click to expand...
Click to collapse
Okay, I did that and all seems good. Ran a root checker that checks for SuperUser, busybox and SU and here are the results:
Status Rooted
Id Uid=0(root) gid=0(root
SuperUser Not found (which is weird because I so have SuperUser installed)
Busybox /system/Xbin/busybox
SU /system/Xbin/SU
What now? DSploit still seems to not be working
tpayne174 said:
Okay, I did that and all seems good. Ran a root checker that checks for SuperUser, busybox and SU and here are the results:
Status Rooted
Id Uid=0(root) gid=0(root
SuperUser Not found (which is weird because I so have SuperUser installed)
Busybox /system/Xbin/busybox
SU /system/Xbin/SU
What now? DSploit still seems to not be working
Click to expand...
Click to collapse
your phone isnt properly rooted, update su binaries or install supersu! if that doesnt fix the problem i am sorry i cannot assist you any further
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable. Instead, I was greeted with the same Error 40 that everyone with a rooted device got. It took me a couple of days of researching and playing and reflashing and..., but I've finally figured out the simple(r) method to bypass this stupid root check for DirectTV Now (AKA Error 40, QP1005)
This applies to the TX5Pro, but it should work on any s905x based AMLogic SoC running Marshmallow 6.0 (A95X, CQ9, TX5, TX3, X96, NEXBOX, +many more.) As I understand it, they all have similar Android builds using the p212 board and firmware. I also have a M8S s812 running Kit-Kat 4.4.2 that I'll work on breaking, next.
First things, first: If possible, find your firmware and do a clean flash. Not a requirement, but if you've been playing with this for a while and you've ended up here, you've probably mucked up your /system files in some way or another. I managed to screw up my su binary location a few times and couldn't get it back without a lot of work. Reflashing was a three-minute, headache-free task.
That said, you'll want to adb over tcp/ip as these devices don't like to play the USB cable game.
Code:
adb connect deviceipaddress:5555
Follow up with
Code:
adb shell
and
Code:
su
to get into a root shell (if you don't get one by default.) Mine came with SuperUser from ClockworkMod preinstalled as a system app. Mount your system folder
Code:
mount -o rw,remount,rw /system
and edit your build.prop file with Vim.
Code:
vi /system/build.prop
If Vim is new to you, search the interwebs for a Vim cheat sheet.
Here's the trick with this... DirecTV Now's shared object file in lib/armeabi/libdrmagent_downloadable_jni.so looks for a few keywords within a few properties. Those properties are:
Code:
ro.build.product
ro.build.tags
ro.build.type
ro.build.display.id
...and the keywords are:
Code:
"release-keys, OnePlus2, OnePlus, Z26CL, STUDIO_C, user" are keywords that it favors, while "cm, cyanogen, cyanogenmod, debug, userdebug, A0001" are disqualifying keywords. Supposedly, "test-keys" is a bad word, too.
In my case, I needed to edit my build.prop to eliminate any sign of the bad words. Example:
Code:
ro.build.display.id=p212-userdebug 6.0.1 MHC19J 20160909 test-keys
to
ro.build.display.id=p212-user 6.0.1 MHC19J 20160909 release-keys
Run through the file and replace anything that says userdebug with user and test-keys with release-keys until you get to "#end build properties" Then save and reboot.
After reboot, install Hide My Root (I used the one from Amphoras) and hide the Su binary. This is where things might be getting tricky for some of you... on the TX5Pro, the SuperUser app is a system installed app, meaning it can't be uninstalled (it can, but it's not exactly a simple task for everyone) so you'll need to go into settings -> apps -> superuser and disable the app from there. Reboot again. Now, with the su binary hidden and the app's manifest not showing up in the system, the error 40 message should go away. This option will allow you to quickly restore su and SuperUser without needing a bunch of additional steps. You'll still need to set the device location service to "battery saving" (or use mock locations) but that's a simple task anyone can figure out.
The app is a choppy on high def feeds for some reason. I can't tell if this is processing/memory issue or a feed (wifi) issue. By default, the app doesn't work on ethernet, meaning you'll have to use wifi until you can fix that issue. But hey, one thing at a time, right? Anyway, I hope this helps anyone with this particular headache.
Thanks for pointing me in the right direction...
Got DirecTV NOW working on my nexus 6 running pure nexus ROM... I just did the edits with super su root and root explorer. Then disabled super su and rebooted.
Now to update the the build.prop files on the lineage os 13.0 nexus 10, and my wife's kltevzw (on ting gsm network) running lineage os 14.1
hi please help i flashed wrong twrp recovery i think now my amlogic smartbox failed to boot in recovery mode and the main problem is my smartbox Encryption Unsuccessful Factory reset, when i click factory reset nothing happend please guide how to solve this
Sent from my SM-N910G using Tapatalk
jameson.donaghy said:
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable.
Click to expand...
Click to collapse
Any chance that you tried this out with Data Free TV/"Sponsored Data" with an AT&T wireless account? i.e. running the box through a Cellular Hotspot or tethered to your phone. I've been looking at if one could use one of therse Android TV Boxes to basically get Data Free TV.
my live tv app detect root try with magisk also but no success in my s905x help me guys
Sent from my SM-N910G using Tapatalk
is anyone help me out
Sent from my SM-N910G using Tapatalk
I edited my build.prop files to try and "hide" the root and I still get the error. I also tried root cloak with xposed and still nothing
Thanks so much
This really helped. I used Xposed module to hide those keywords. Worked a charm!
Samsung Galaxy S7 on latest April Patch. Giving access to Greenify through this "https://greenify.uservoice.com/knowledgebase/articles/749142-how-to-grant-permissions-required-by-some-features" method is not working. I tried using different version of it starting from v2.9 to 3.3. The older ones give me a notification that I do not have root privileges, but the latest version don't.
Is this method still viable or just not working for me?
Also if this method is something that is endorsed by the developer shouldn't it be good to put a force check on it?
PS: Was working before updating to 3.2.2, by which I mean it didn't use to give me the "No root" notification.
PPS: Used to different machines with both CMD PowerShell to grant the adb access.
Hey, guys. Redmi note4x (mido) After installing supersu using twrp to get root successfully, but then I found that using USB to connect the computer has a problem: USB can not be used, connect USB after the phone shows charging. Including USB debugging, mtp can not be used. Is this the reason for the kernel?
Please forgive me for bad English
Wrong place. But I think disabling adb fixes mtp. Not sure. Worth trying though.
Sent from my Redmi Note 4 using Tapatalk
Hawkeye007 said:
Wrong place. But I think disabling adb fixes mtp. Not sure. Worth trying though.
Click to expand...
Click to collapse
All MIUI stable version I have tried, almost all have this problem.
Now I have found a solution: do not use supersu. I downloaded and installed the latest beta magisk su. At present everything is normal, but the shortcomings are obvious. There are a lot of applications can not identify su files. Even if the use of magisk comes with the su get root but still prompted no root privileges. Probably this is the problem of compatibility bars
Andy，xu said:
All MIUI stable version I have tried, almost all have this problem.
Now I have found a solution: do not use supersu. I downloaded and installed the latest beta magisk su. At present everything is normal, but the shortcomings are obvious. There are a lot of applications can not identify su files. Even if the use of magisk comes with the su get root but still prompted no root privileges. Probably this is the problem of compatibility bars
Click to expand...
Click to collapse
No problem just go to /device /system and edit build.prop and add these lines
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
And save then restart also enable USB debugging ,it will solve ur issue.
Hey there,
I've rooted my OnePlus 7t Pro with an autoinstall jar, in cause of the twrp isssue (that twrp isn't available yet for android 10)
After doing this root tutorial, my device got rooted and magisk has been installed properly. So today I just thought about changing my
bootanimation like I did several times before, but when I tried to mount System as Read&Write it told me that this is Read only...
So after searching google for hours I maybe found the issue of my problem, because I had activated in Magisk "Preserve AVB 2.0/dm-verity" which helps to prevent
rootkits from breaking into the system. But I also heared that you block to remount your root filesystem with this option. So they told me to run following command:
"adb disable-verity". Buuut I've also read that this will crash my phone and will make it unaccessable. So before I do something weird and regret it after I wanna ask more
experienced people if they can help me..
MrLufus said:
Hey there,
I've rooted my OnePlus 7t Pro with an autoinstall jar, in cause of the twrp isssue (that twrp isn't available yet for android 10)
After doing this root tutorial, my device got rooted and magisk has been installed properly. So today I just thought about changing my
bootanimation like I did several times before, but when I tried to mount System as Read&Write it told me that this is Read only...
So after searching google for hours I maybe found the issue of my problem, because I had activated in Magisk "Preserve AVB 2.0/dm-verity" which helps to prevent
rootkits from breaking into the system. But I also heared that you block to remount your root filesystem with this option. So they told me to run following command:
"adb disable-verity". Buuut I've also read that this will crash my phone and will make it unaccessable. So before I do something weird and regret it after I wanna ask more
experienced people if they can help me..
Click to expand...
Click to collapse
Be for that try this first https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
System is now permanent read only in Android 10,Y ou can't change that.
Best way to change something is a magisk module.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
System is now permanent read only in Android 10,Y ou can't change that.
Best way to change something is a magisk module.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Yeah, you might be right with that, do you have a solution for this issue, because I'm not able to flash my new bootimage via Magisk and I also want a full
file system access again, like I had before