Related
Ive only found a couple of topics on this, one was for dev/unlocked tether on 4.4 and the other was for locked/unrooted thether on 4.4.4. so both just missing what i need.
what is the method, or is there one, for using the native tether on an unlocked Verizon Moto X?
TheWhiteChallenger said:
Ive only found a couple of topics on this, one was for dev/unlocked tether on 4.4 and the other was for locked/unrooted thether on 4.4.4. so both just missing what i need.
what is the method, or is there one, for using the native tether on an unlocked Verizon Moto X?
Click to expand...
Click to collapse
If you are unlocked and rooted the easiest way is to install Xposed framework and Moto Tether module.
no i dont want to do that. easy isnt my primary concern. my primary concern is cleanliness so i would perfer a real mod.
i just read this: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
if im reading it correctly i can simply add "net.tethering.noprovisioning=true" to the build prop but im not yet sure if i read it right
FWIW, on the XT1049 (4.4.2) I tried it out by modifying these two properties in /system/build.prop under # ADDITIONAL_BUILD_PROPERTIES:
ro.mot.tether_dun_required=0
ro.tether.denied=false
...and then I added the line:
net.tethering.noprovisioning=true
This seemed to work in a quick test loading a webpage, but I haven't used it beyond that.
TheWhiteChallenger said:
no i dont want to do that. easy isnt my primary concern. my primary concern is cleanliness so i would perfer a real mod.
i just read this: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
if im reading it correctly i can simply add "net.tethering.noprovisioning=true" to the build prop but im not yet sure if i read it right
Click to expand...
Click to collapse
Correct. The Tool in that thread works for the XT1060 which is bootloader unlocked and rooted.
The other way is to use the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
I use the wifi-tether APK on my Dev Edtion XT1060 for Verizon (unlocked and rooted, running 4.4.4, it worked on 4.4.2 and 4.4 also)
k_t_b said:
FWIW, on the XT1049 (4.4.2) I tried it out by modifying these two properties in /system/build.prop under # ADDITIONAL_BUILD_PROPERTIES:
ro.mot.tether_dun_required=0
ro.tether.denied=false
Click to expand...
Click to collapse
I don't see those in the XT1060 build.prop.
TheWhiteChallenger said:
no i dont want to do that. easy isnt my primary concern. my primary concern is cleanliness so i would perfer a real mod.
i just read this: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
if im reading it correctly i can simply add "net.tethering.noprovisioning=true" to the build prop but im not yet sure if i read it right
Click to expand...
Click to collapse
I think the best method is to use Xposed Installer and the X Tether (Moto Tether) module. This allows you to use the stock Mobile Hotspot app without having to modify/replace it. As easy as this is to setup (install Xposed Installer, install the module, reboot and done) it's just as easy to revert it when the next update comes out (just disable the module and Xposed Installer).
Bonus....you now have Xposed Installer so you can grab other modules if you like (ie...Root Cloak, Gravitybox, etc..).
tcrews said:
I think the best method is to use Xposed Installer and the X Tether (Moto Tether) module.
Click to expand...
Click to collapse
I agree and it is a snap to uninstall it. But for some reason, the OP doesn't want to do that - I am guessing it is a work phone maybe and he wants it to be less obvious?
tcrews said:
I think the best method is to use Xposed Installer and the X Tether (Moto Tether) module. This allows you to use the stock Mobile Hotspot app without having to modify/replace it. As easy as this is to setup (install Xposed Installer, install the module, reboot and done) it's just as easy to revert it when the next update comes out (just disable the module and Xposed Installer).
Bonus....you now have Xposed Installer so you can grab other modules if you like (ie...Root Cloak, Gravitybox, etc..).
Click to expand...
Click to collapse
Xposed does make changes to system, and some modules can caused reduced battery life.
Not everyone wants that.
Some just want to be simply stock, rooted and have the ability to tether. Xposed and its modules is extra stuff installed.
@TheWhiteChallenger
There are two "easy" and "light weight" options already posted in this thread. The app in the other thread that modifies the build.prop on the fly, and the wifi tether for root apk.
Or you can install Xposed and the Tether Module like the other suggested.
KidJoe said:
Xposed does make changes to system, and some modules can caused reduced battery life.
Not everyone wants that.
Some just want to be simply stock, rooted and have the ability to tether. Xposed and its modules is extra stuff installed.
@TheWhiteChallenger
There are two "easy" and "light weight" options already posted in this thread. The app in the other thread that modifies the build.prop on the fly, and the wifi tether for root apk.
Or you can install Xposed and the Tether Module like the other suggested.
Click to expand...
Click to collapse
Xposed itself is a very small modification and doing the Tether module is near the same as using the modified stock tether app. I've tried both methods and the Xposed method is cleaner and much simpler. Add in the bonus of an extremely simple method to revert without the hassle of removing/renaming/restoring the stock tether app and it's near perfect.
With that done....you can be done. The added bonus is you do have the option of adding in additional modules if you like.
tcrews said:
Xposed itself is a very small modification and doing the Tether module is near the same as using the modified stock tether app. I've tried both methods and the Xposed method is cleaner and much simpler. Add in the bonus of an extremely simple method to revert without the hassle of removing/renaming/restoring the stock tether app and it's near perfect.
With that done....you can be done. The added bonus is you do have the option of adding in additional modules if you like.
Click to expand...
Click to collapse
we'll have to agree to disagree here.
WiFi tether apk I use is a stand alone app, doesn't need to be undone to update, only runs when i launch it. etc. The app from the other thread just changes/updates the build.prop. It does nothing else. Nothing needs to be undone to update. No extra apps running, etc.
There are many options because one-size doesn't fit all.
ok...
first, can we plz stop the exposed debate be for it goes any further, those kind of answers are exactly the answers this thread was started to avoid. i appreciate the attempt to help but ur just ignoring the intent of the original question and further complicating the issue.
second,i found the solution: use build prop editor (or whatever u want to use) to add net.tethering.noprovisioning=true , delete VzwEntitlementService.apk and its .odex, done
TheWhiteChallenger said:
second,i found the solution: use build prop editor (or whatever u want to use) to add net.tethering.noprovisioning=true , delete VzwEntitlementService.apk and its .odex, done
Click to expand...
Click to collapse
I wouldn't delete them, just rename them. If you want to take a future OTA, you'll need to put them back.
TheWhiteChallenger said:
ok...
first, can we plz stop the exposed debate be for it goes any further, those kind of answers are exactly the answers this thread was started to avoid. i appreciate the attempt to help but ur just ignoring the intent of the original question and further complicating the issue.
second,i found the solution: use build prop editor (or whatever u want to use) to add net.tethering.noprovisioning=true , delete VzwEntitlementService.apk and its .odex, done
Click to expand...
Click to collapse
Hello, I also have an unlocked (via sunshine) verizon moto x, currently running 4.4.2 and rooted with towelpie because I have never installed a custom rom and don't want to muck anything up. But if it's not too hard to install a custom rom I may try. Is this what you have done?
All I have done is ran sunshine and unlocked the bootloader, it's still on 4.4.2 and rooted with towelpie. Do I have write since I unlocked the boot or do I have to install a twrp to gain write? I am familiar with sqlite editer https://play.google.com/store/apps/details?id=com.speedsoftware.sqleditor&hl=en
is this something like what you used to write the command to tether?
Thank you
doitinthedirt said:
Hello, I also have an unlocked (via sunshine) verizon moto x, currently running 4.4.2 and rooted with towelpie because I have never installed a custom rom and don't want to muck anything up. But if it's not too hard to install a custom rom I may try. Is this what you have done?
All I have done is ran sunshine and unlocked the bootloader, it's still on 4.4.2 and rooted with towelpie. Do I have write since I unlocked the boot or do I have to install a twrp to gain write? I am familiar with sqlite editer https://play.google.com/store/apps/details?id=com.speedsoftware.sqleditor&hl=en
is this something like what you used to write the command to tether?
Thank you
Click to expand...
Click to collapse
a text editor or notepad type app can be used to edit build.prop. SQLite or such wont work.
In theory, using Sunshine to gain unlocked bootloader should grant write protection disable, however I'm not familure enough with it to be sure. This post -> http://forum.xda-developers.com/showpost.php?p=45604505&postcount=33 should still work to allow you to check write protection status.
If you can undo TowelPieRoot (usually just rebooting, or at worst flashing system.img using mfastboot will work), you can easily flash TWRP and get a proper root and write protection disabled.
A custom rom is not needed to tether.
If you have root, and write protection disabled, two EASY ways to tether on Verizon are in Post #5 above...
doitinthedirt said:
Hello, I also have an unlocked (via sunshine) verizon moto x, currently running 4.4.2 and rooted with towelpie because I have never installed a custom rom and don't want to muck anything up. But if it's not too hard to install a custom rom I may try. Is this what you have done?
All I have done is ran sunshine and unlocked the bootloader, it's still on 4.4.2 and rooted with towelpie. Do I have write since I unlocked the boot or do I have to install a twrp to gain write? I am familiar with sqlite editer https://play.google.com/store/apps/details?id=com.speedsoftware.sqleditor&hl=en
is this something like what you used to write the command to tether?
Thank you
Click to expand...
Click to collapse
Not familiar with towelpie, but if there is a way to undo the root, possibly by going to supersu and doing a full unroot, then you can regain root (with proper r/w to system) by flashing a custom recovery like CWM or TWRP and flashing the supersu.zip ( http://download.chainfire.eu/396/SuperSU/ )
I read on another forum that Titanium Backup does not work if you're using systemless root. Can anyone verify if this is true ?
If TB does work, how would I go about upgrading stock Android 6.01 rooted with TWRP to 6.0.1 with systemless root ?
aparanoidandroid said:
If TB does work, how would I go about upgrading stock Android 6.01 rooted with TWRP to 6.0.1 with systemless root ?
Click to expand...
Click to collapse
Make backup's with TWRP.
NLBeev said:
Make backup's with TWRP.
Click to expand...
Click to collapse
I know how to make backups with TB. That wasn't my question. My question is, how do I go from 6.0 rooted with SuperSU to 6.0.1 with systemless root (assuming TB works in 6.0.1)
aparanoidandroid said:
... how do I go from 6.0 rooted with SuperSU to 6.0.1 with systemless root (assuming TB works in 6.0.1)
Click to expand...
Click to collapse
Read post 2153 of @Tylog in this thread
http://forum.xda-developers.com/showthread.php?t=3059493
NLBeev said:
Read post 2153 of @Tylog in this thread
http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
So is SuperSU 2.61 the ZIP for Chainfire's systemless root ?
aparanoidandroid said:
So is SuperSU 2.61 the ZIP for Chainfire's systemless root ?
Click to expand...
Click to collapse
Yes since version 2.6x.
NLBeev said:
Yes since version 2.6x.
Click to expand...
Click to collapse
What about Titanium Backup ? Can anyone verify if it works or not with systemless root ? I read a post on Reddit where someone said that they were not able to use it with this root method. Do root apps need to be specifically modified for this type of rooting so it can recognize it ?
Also just to be clear, I am on stock Android 6.0 ROM, rooted and with TWRP recovery.
so the order that I would need following according to the post that you gave me is:
Flash 6.0.1 ROM
flash Update-unSU
flash SuperUser 2.61 or 2.52
Is that correct ? Can I dirty flash 6.0.1 over 6.0 ?
aparanoidandroid said:
What about Titanium Backup ? Can anyone verify if it works or not with systemless root ? I read a post on Reddit where someone said that they were not able to use it with this root method.
Click to expand...
Click to collapse
Root apps with hard coded su-stuff needs to be updated for use with systemless root.
What I read....There is a new version 2.62 that solves compatibility issues. But Android Pay will not work.
NLBeev said:
Root apps with hard coded su-stuff needs to be updated for use with systemless root.
What I read....There is a new version 2.62 that solves compatibility issues. But Android Pay will not work.
Click to expand...
Click to collapse
Oh really ? From what I read, Android Pay and OTA both do work using systemless root although many people think that Google will find a way to block Android Pay again. Its one of the reasons I wanted to use systemless root in the first place.
aparanoidandroid said:
Oh really ? From what I read, Android Pay and OTA both do work using systemless root..
Click to expand...
Click to collapse
Not with version 2.62. Info in the SuperSU thread.
http://forum.xda-developers.com/showpost.php?p=64161125
NLBeev said:
Not with version 2.62. Info in the SuperSU thread.
http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
OK. Thanks for the info.
Yes, TB works with systemless root.
I was running stock 6.0 w/ root (a few xposed mods) and here's what I did:
Wiped system, flashed Cataclysm, flashed SU 2.61, rebooted, profit.
I also manually updated the radio by using fastboot, for what it's worth. AdAway made me create a simlink with the systemless root, but TB seemed to work just fine.
EDIT: I wiped system before anything as I knew it would get rid of any root files and anything related to Xposed. Phone has been running great, but I haven't re-done Xposed as the only modules I really used were GravityBox and YouTubeAdAway. Catacylsm has almost all the features I used in GB so no need to do both. I might put Xposed on tonight for kicks, but I don't really need it for anything right now.
hayzooos said:
Yes, TB works with systemless root.
I was running stock 6.0 w/ root (a few xposed mods) and here's what I did:
Wiped system, flashed Cataclysm, flashed SU 2.61, rebooted, profit.
I also manually updated the radio by using fastboot, for what it's worth. AdAway made me create a simlink with the systemless root, but TB seemed to work just fine.
EDIT: I wiped system before anything as I knew it would get rid of any root files and anything related to Xposed. Phone has been running great, but I haven't re-done Xposed as the only modules I really used were GravityBox and YouTubeAdAway. Catacylsm has almost all the features I used in GB so no need to do both. I might put Xposed on tonight for kicks, but I don't really need it for anything right now.
Click to expand...
Click to collapse
thanks but what happens when you wipe system ? What will I lose other than root ?
aparanoidandroid said:
thanks but what happens when you wipe system ? What will I lose other than root ?
Click to expand...
Click to collapse
Anything Xposed related will be gone, but other than that...nothing. All apps, settings, etc of mine were all retained. Wifi networks, bluetooth connections, all those stayed. Wallpaper, Nova Launcher setup/settings, stayed.
Most ROMs have built in their script to wipe the system partition before flashing anyway, so you're likely already doing it if you're flashing ROMs. I just wanted to start with a pretty clean slate and check to see if anything in data was causing issues, and nothing so far.
Titanium Backup 7.4.0.2 and System Root was working about 2 weeks ago FLAWLESSLY
My last Titanium Backup was on July 7, 2016 with Systemless root, with XPosed, Gavitybox for MM and Stock 6.0 ROM Build MPHS24.49-18-3. I have been using Titanium Backup since I got my MOTO X Pure (2015) in May of 2016, and everything is working great, except I just noticed that Titanium Backup v 7.4.0.2 states
"Error
Sorry,
I could not acquire root privileges.
This application will *not* work! Please
verify that your ROM is rooted, and try
again.
This attempt was made using the "/system/
bin/su"command."
CLETjB said:
My last Titanium Backup was on July 7, 2016 with Systemless root, with XPosed, Gavitybox for MM and Stock 6.0 ROM Build MPHS24.49-18-3. I have been using Titanium Backup since I got my MOTO X Pure (2015) in May of 2016, and everything is working great, except I just noticed that Titanium Backup v 7.4.0.2 states
"Error
Sorry,
I could not acquire root privileges.
This application will *not* work! Please
verify that your ROM is rooted, and try
again.
This attempt was made using the "/system/
bin/su"command."
Click to expand...
Click to collapse
Do you have Busybox installed? If not, that may be why. Had the same issue, installed Busybox to /su/xbin, and all is good now.
Gravity Box works with XPosed Framework, which ONLY works with "BusyBox on Rails", which I do have installed. Not sure if I can tell it where to install BusyBox, but it seems to be working now.
Does anyone have a clue to get magisk and titanium backup to work with each other... TB does not seem to ask for Root, seems to simply bypass it...
-----Nevermind, just make sure you have unticked Magisk Hide- in Settings. WORKS!
Hey guys! So I read around about rooting Android 6.0.1 and I only see systemless root. I am rooted right now using systemless root and it works fine, but my question is, is there a way to root 6.0.1 with traditional system root? Or is systemless the only way? Just curious really. Will systemless most likely be the future of rooting and the way it's going to have to be done from now on to keep Android Pay working?
Sent from my Nexus 6
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
Thanks for the response! And I wonder if it will be what it is for now! It's the only way to keep Android Pay working while the device is rooted correct? Android Pay refuses to work with a traditionally rooted device?
Sent from my Nexus 6
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
I did. I still use SU2.52. But only until this weekend. I'm switching to systemless too.
Actually building a permissive kernel is really straightforward, needs one line of code added. The build is about five minuters then with abootimg you can just replace the existing with the newly buil kernel in the boot.img, and flash it.
I can give you details if you're interested.
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
Mine works perfectly.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Krzysiek_CK said:
Mine works perfectly.
Click to expand...
Click to collapse
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
H4X0R46 said:
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
I tested 2.61, is problem fixed in 2.62.3? because I must flash 6.0.1 and setup phone again!
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
simms22 said:
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
Click to expand...
Click to collapse
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
H4X0R46 said:
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
Click to expand...
Click to collapse
ive no use for pay, so never tried. i assume its broken..
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
carmatana said:
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
Click to expand...
Click to collapse
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
H4X0R46 said:
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
Click to expand...
Click to collapse
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
I would say yes, I'm 90% sure but could be wrong. I would flash the a new update with fastboot.
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
Any mod stops ota's. Root, kernels....You will have to flash full images to get updates. You can skip the userdata part and save your apps and data. But you will have to flash.
Not a big deal, it an extra couple of commands just like the kernel you want to flash.
Thanks!
kamkar said:
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
Click to expand...
Click to collapse
Clean 6.0.1 followed by systemless root installation as expained in the Root done right thread.
I plan on rooting pretty much immediately, and was hoping to use FreedomOS (not sure it will be supported early, but I'll switch when it is). Either way, how difficult is it to set up systemless root and Xposed? I used to play PokemonGO on my LG V10, but I won't sacrifice root for one game that I use for walks/fun. Same applies here, but I heard systemless solves this issue. Any insight if this will be supported?
It's fairly easy. Unlock your bootloader as soon as you get your phone so you don't need to wipe, and setup your pc with fastboot/adb. Then once twrp is released it's just a matter of flashing that and using it to flash the zip files you need. You can find a lot of guides around XDA for how to setup ADB/fastboot and bypass root checks with xposed.
namanjr said:
It's fairly easy. Unlock your bootloader as soon as you get your phone so you don't need to wipe, and setup your pc with fastboot/adb. Then once twrp is released it's just a matter of flashing that and using it to flash the zip files you need. You can find a lot of guides around XDA for how to setup ADB/fastboot and bypass root checks with xposed.
Click to expand...
Click to collapse
I assume it's a per app basis on going systemless/bypassing root checks, or is it all handled in Xposed now? Just curious, and thanks for the answer!
You have to hide su per app with suhide for pokemon go. For safetynet apps you need a custom kernel and rootswitch to pass.
namanjr said:
You have to hide su per app with suhide for pokemon go. For safetynet apps you need a custom kernel and rootswitch to pass.
Click to expand...
Click to collapse
suhide not working with november update....
oTeMpLo said:
suhide not working with november update....
Click to expand...
Click to collapse
Systemless still work? Different install IIRC.
oTeMpLo said:
suhide not working with november update....
Click to expand...
Click to collapse
you can use suhide with a open source rom by removing this https://android.googlesource.com/platform/frameworks/base/+/b8be33b0bedec211708c4525b9d3f3b4effb385c
Anyone do any tests to get PGo working with root? I have SuperSU installed systemless, but when I tried to install SUhide or whatever it's called, my phone wouldn't get past the boot logo so I had to uninstall it.
banking app, not baking app, f**ks sake
Hello there. I have been using stock android 7.1.1 for a while and decided to try using roms again (Pure Nexus). One of the apps that i need is "Vipps" its a Norwegian banking app used to transfer money to friends and stuff, but its notorious for finding root. I used to use xposed and root cloak on android 6, but i know well it dosent work with 7. Magisk dosent hide it, suhide dosent hide it.
After installing Vipps it rejects opening promting me with "Vipps does not support rooted devices". Only thing is its running a ROM that comes with no root.
- Cheers, Kristiansja
edit: root checker doesn't find annything either
kristiansja said:
banking app, not baking app, f**ks sake
Hello there. I have been using stock android 7.1.1 for a while and decided to try using roms again (Pure Nexus). One of the apps that i need is "Vipps" its a Norwegian banking app used to transfer money to friends and stuff, but its notorious for finding root. I used to use xposed and root cloak on android 6, but i know well it dosent work with 7. Magisk dosent hide it, suhide dosent hide it.
After installing Vipps it rejects opening promting me with "Vipps does not support rooted devices". Only thing is its running a ROM that comes with no root.
- Cheers, Kristiansja
edit: root checker doesn't find annything either
Click to expand...
Click to collapse
Go into the root settings and remove root. Mind you this cause some of the features of the rom to stop working. Apps like that are not only looking for root but also for unlocked bootloaders. So if those apps are important to you then might want to stick to a fully stock set up and relock your bootloader.
zelendel said:
Go into the root settings and remove root. Mind you this cause some of the features of the rom to stop working. Apps like that are not only looking for root but also for unlocked bootloaders. So if those apps are important to you then might want to stick to a fully stock set up and relock your bootloader.
Click to expand...
Click to collapse
Pure Nexus comes without root
kristiansja said:
Pure Nexus comes without root
Click to expand...
Click to collapse
Go into developer option and turn off USB debugging. After that, reboot the phone and see if Vipps is working. If that doesn't work, I have one more suggestion.
It's probably checking ro.build.tags and/or ro.build.type. These are set to test-keys and userdebug on PN (if I remember correctly) and some apps need them to be set to release-keys and user. It could also be looking for other prop values and possibly also busybox (also included in PN, I believe).
Or BusyBox...
Sent from my Nexus 6 using Tapatalk