Related
I am interested in using Android Pay but understand the phone cannot be rooted.
I am curious I am would be able to Root for whatever purposes, and the unroot for day to day use to retain the ability to use Android Pay. I am willing to stay on the stock rom and install if needed.
Thanks
MoreGone said:
I am interested in using Android Pay but understand the phone cannot be rooted.
I am curious I am would be able to Root for whatever purposes, and the unroot for day to day use to retain the ability to use Android Pay. I am willing to stay on the stock rom and install if needed.
Thanks
Click to expand...
Click to collapse
I've seen threads that say to disable supersu, add cards, and reenable supersu and it should work. However, I tried this on the 6 and it never worked. As of now there doesn't seem to be surefire way to get Pay to work while rooted. If xposed is made for 6.0 a root cloak should work, but I can't be sure. Others may be able to provide addition info on this.
theycallmerayj said:
I've seen threads that say to disable supersu, add cards, and reenable supersu and it should work. However, I tried this on the 6 and it never worked. As of now there doesn't seem to be surefire way to get Pay to work while rooted. If xposed is made for 6.0 a root cloak should work, but I can't be sure. Others may be able to provide addition info on this.
Click to expand...
Click to collapse
What if you root your phone, apply an adblock, change your dpi, etc....and then unroot, leaving your changes intact. Then will android pay work?
ArkAngel06 said:
What if you root your phone, apply an adblock, change your dpi, etc....and then unroot, leaving your changes intact. Then will android pay work?
Click to expand...
Click to collapse
Some reports say the a DPI change causes AP to fail.
As far as the other, that should work fine.
Can anyone confirm this..? No Adblock is killing me.
I'm curious about this too. I've read that with nexus devices your have to lock the boatloader again as well as unroot. But then I've also seen people say these root then unroot tricks only work for adding cards, not for actually paying with them. I really like the idea of Android pay and hope nfc payments spread more, but everyday I ask myself "how many stores have nfc payment today vs how many things could I do with root today..." Not sure how long I can hold out.
It would be nice if we had a definitive answer or steps on how to add Android Pay but keep root. I'm using a systemless root now but have modified mixer_paths to increase headphone volume. I'm thinking about flashing stock boot then trying to add a card then going back to the modified boot.
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
new root method
http://www.androidpolice.com/2015/1...d-root-without-touching-the-system-partition/
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
New root method that does not modify the /system
exSD said:
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
Click to expand...
Click to collapse
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Good article on just what SafetyNet (Googles tamper checking for Android pay) does behind the scenes:
https://koz.io/inside-safetynet/
About 1/3 the way down the page it details the checks that are run to determine if the device has been tampered
Pretty interesting stuff, with a fairly important point: it does not reside on the actual device, its actually pulled down and run real-time when you fire up Android Pay. The interesting part about it is that could allow Google to disable some of the checks, to allow for things like Root, DPI changes, etc to actually NOT list the device as tampered. Will they? Who knows.
I have root and Android pay working fine. I've mad purchases multiple times this way
Sent from my Nexus 6P using Tapatalk
trebills said:
I have root and Android pay working fine. I've mad purchases multiple times this way
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You have systemless root.
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
That is what I'm saying.
You edit DPI by modifying your build.prop file. That file resides in /system.
If you make any change to /system, Android Pay will NOT work. Period. You can root cloak/add card/unroot after editing DPI/etc but when it comes time to actually pay, the SafetyNet will fail because you've modified your /system.
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
Confirmed.
Here's the testing ive done:
Unlocked bootloader...AP works entirely.
rooted...AP will not allow you add a card, or process a transaction. If you have a card added prior to root, AP will not allow a transaction.
Disable root in SuperSu...AP will work entirely after you disable root and reboot your phone with root disabled. If you enable root again, AP will continue to work until you reboot.
With a modded DPI/no root...AP will not process a transaction.
Modified hosts file via Adfree/Adaway-root disabled...adblocking with a modified hosts file has no effect on AP
Click to expand...
Click to collapse
Those tests are all completed transactions at a terminal.
exSD said:
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
Click to expand...
Click to collapse
This is not universally true. I tested/verified a working method for using AndroidPay on a Sprint LG G3 that had a modified /system partition. Obviously that's a completely different phone, but it's one of the first things I'll be testing once my Angler comes in on Monday. Same method works for enabling adding cards the same as making a purchase. Here's what worked for me.
I got it figured out as well and so here's my method. I honestly think, though, that its every man for himself out there on this and that what works for one is unlikely to work for another.
Mine does not use XPosed, I don't have it installed. Requires use of SuperSU as your superuser manager and be currently rooted. I am running BarePapA-TE_V3 and NavelA-V1.6.
Download RootCloak Plus (Cydia) and Cydia Substrate from the Play Store.
Open Substrate. It tells me "Note: something about your device made it impossible for Substrate to perform its internal safety check; can you please contact saurik via e-mail?". Doesn't seem to effect anything.
Open RootCloak Plus (Cydia). Here you are going to be adding apps to a list of ones you don't want knowing you have root. There are a bunch of defaults already which you can leave. Add AndroidPay (com.google.android.apps.walletnfcrel). Now beyond that, I went ahead and added a number of other Google Apps and be certain any of them are required, but its what I did. I added the new Wallet app, Google Play Services, Play Store, Google Partner Setup, Google Account Manager, and Google Services Framework. Basically, my reasoning was that given the commitment to blocking rooted devices from using AndroidPay, it'd be useful to cloak any of the other financial apps and core GAPPS as well . . . because who knows how they are checking for root?
Reboot device.
Open SuperSU and uninstall superuser.
Reboot device. AndroidPay now works, buy yourself an Oreo McFlurry with your phone you clever hacker.
Obviously, your rooted apps won't work. So, if you want them back you will have to open SuperSU and reinstall superuser. That is going to break AndroidPay. Each time you want to use it again, you have to repeat the last two steps. So, there's the compromise . . . you can either leave your phone unrooted or have to reboot every time you want to use it.
Click to expand...
Click to collapse
cabbieBot said:
This is not universally true. I tested/verified a working method for using AndroidPay on a Sprint LG G3 that had a modified /system partition. Obviously that's a completely different phone, but it's one of the first things I'll be testing once my Angler comes in on Monday. Same method works for enabling adding cards the same as making a purchase. Here's what worked for me.
Click to expand...
Click to collapse
My phone is rooted in the normal way by flashing SuperSu.
If you change DPI on the phone it no longer passes a check of hardware configuration, so the device fails.
Other files have no effect. Hosts file does not describe HW so it doesn't matter.
Build.conf can be modified but not in areas that don't match the hardware.
I've had xposed installed after adding cards and added root cloak and had no isses.
I am rooted with system less root and android pay works fine. N6p angler.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
That's correct do not edit stock dpi or pay will not work /at least as far as adding cards anyway (tested).
Thanks. I guess no AP for me. I root only to edit built.prop
puritan007 said:
I am rooted with system less root and android pay works fine. N6p angler.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
That's correct do not edit stock dpi or pay will not work /at least as far as adding cards anyway (tested).
Click to expand...
Click to collapse
Rooted with system less root and Android Pay works....are you referring to it works without disabling root and rebooting? Or it just works regardless?
Seems there are some posts saying it works as long as you reboot with root disabled, and others saying "it works" but need clarification of any process that needed to be done before using it.
chrisexv6 said:
Rooted with system less root and Android Pay works....are you referring to it works without disabling root and rebooting? Or it just works regardless?
Seems there are some posts saying it works as long as you reboot with root disabled, and others saying "it works" but need clarification of any process that needed to be done before using it.
Click to expand...
Click to collapse
With any root before 5.46 you had to Un root to add cards. With 5.46 system less I did nothing it just works how it should with no messing about
In preparation for the impending upgrade to Android 6 Marshmallow, I'm trying an experiment on my Android 5 based Zenfone 2. I'm going to see how annoying it is to give up root. The first thing I did on my first android phone was root it, so I've only every used rooted Android devices.
Prologue:
Root on Android 6 (usually) requires an unlocked bootloader, because root is achieved by modifying the boot image to inject su into the system. That way the system image is left unmodified and can continue to pass dm-verity checks.
At the moment, there does not appear to be anyway on the Zenfone 2 to unlock the Marshmallow beta bootloader, and it also appears to relock any unlocked bootloader. In fact, the droidboot binary in the droidboot.img of the Marshmallow beta contains the strings rm -rf /factory/asuskey and rm -rf /factory/asussignature. droidboot also contains the strings unlock successfully...reboot after 5 seconds and **** Unlock bootloader? **** as well as other strings referring to unlock (droidboot from the .184 Lollipop also has those strings). So, my hope is that there is a simple way to unlock the bootloader, which will be revealed by Asus, or discovered by somebody.
My thought is that worst case those of us who want root will use an unlockable Lollipop bootloader with a Cyanogenmod 13.1 based ROM created with updates from the Asus Marshmallow source code.
Experiment:
I've removed Xposed and SuperSU from my phone. Making it stock Android 5. I'm documenting here the functionality that I lose. The first goal is for my own amusement to keep a log of what I'm giving up.
The second goal, and probably the major one, is to solicit suggestions on what can be done to replace the functionality I'm losing.
What I'm giving up:
AdAway - No system wide ad blocking. Firefox with uBlock Origin should cover blocking ads on the web. I usually buy apps I use frequently, but I'll have to see which ones are annoying with ads. I'm aware of the VPN based ad blocking methods, but I'll have to wait and see if it comes to that.
AFWall+ - Using root to improve security... I mostly use this to prevent some apps from using mobile data, and to prevent some apps from gaining network access at all.
BetterBatteryStatus - It works in non-root mode, but not as well.
BusyBox - Without root, there isn't much need for this anyway.
Cryptfs Password - Once again, security is harmed by removing root. This allowed my encryption pin to be different (and much longer) than my screen lock pin. I don't want to type 10 digits to unlock my screen, but it's fine for booting.
Greenify - This definitely kept some aps in check, but perhaps Asus' Auto-Start Manager will be able to replace it.
GSam Battery Monitor - Like BetterBatteryStatus, this had a root component to provide more information.
Kernel Adiutor - For some reason my phone seemed to only go to 1.8ghz instead of 2.3ghz, so I used this to fix it.
Linux Deploy - I never used the Linux chroot image for much, but it was a cute toy.
Secure Settings - This let tasker automate adjusting some things which require root to change.
Titanium Backup - This is a massive loss in functionality. Simply having backups is tremendously important. The ability to freeze unwanted system apps is also nice. I can reload many of my apps from Google, but not all of them bother to save their settings in the Google backup. Ohh, the bloat!
Trimmer (fstrim) - Probably not really necessary, anyway.
Xposed
Amplify - It saved me lots of wakeups, but I don't know if it really did much to increase battery life.
Fix Lollipop Memory Leak - I don't know if this did anything, either.
GravityBox [LP] - I didn't tweak too much, but what I did change was really useful.
NetStrength - I like replacing my wifi bars with useful information.
ProtectMyPrivacy - The permission settings in Marshmallow would make this obsolete anyway.
YouTube AdAway - Nice, but not required.
What I'm gaining:
Android Pay - I guess I can play with this now.
AFWall+ - Using root to improve security... I mostly use this to prevent some apps from using mobile data, and to prevent some apps from gaining network access at all.
Click to expand...
Click to collapse
Asus has integrated a firewall iptables recent months.
Asus mobile manager -> User Data -> Restrict (bottom of screen)
For the rest, no root is to accept to take along twice monitoring tools of an advertising billboard.
Keep in mind that Google is an advertising agency that is desperate to earn money, including harassment to get the maximum information.
Its purpose, despite what he claims, is not to improve people's lives, but his bank account.
Android is a disguised tools for Google, not for the people who is a commodity to be exploited.
I'm gonna miss Adaway and Afwall+ the most. Afwall+ is much better than the Asus built in firewall. You can disable net access by default for newly installed app. You are notified to set firewall rules when you install an app. You can filter apps to be set. If only Asus could provide a such a bunch of feature for their firewall, I won't miss root so much.
Sent from my Asus Zenfone 2 using XDA Labs
IDEDALE said:
Asus has integrated a firewall iptables recent months.
Asus mobile manager -> User Data -> Restrict (bottom of screen)
Click to expand...
Click to collapse
Thanks for the info about the functionality in Asus Mobile Manager, I didn't know that.
As far as Adaway goes, try this https://block-this.com
Sent from my ASUS_Z00A using Tapatalk
IDEDALE said:
Asus has integrated a firewall iptables recent months.
Asus mobile manager -> User Data -> Restrict (bottom of screen)
For the rest, no root is to accept to take along twice monitoring tools of an advertising billboard.
Keep in mind that Google is an advertising agency that is desperate to earn money, including harassment to get the maximum information.
Its purpose, despite what he claims, is not to improve people's lives, but his bank account.
Android is a disguised tools for Google, not for the people who is a commodity to be exploited.
Click to expand...
Click to collapse
Agree with most of that... unfortunately the ASUS mobile manager "firewall" doesn't work any more on the current marshmallow beta.
It's still there, but it seems not to work for blocking apps.
The new app permission system in MM may be used to prevent apps from connecting around, in theory at least, but I'm not sure how effective that is.
This phone without root absolutely sucks. There's a thread on the ASUS forum, guy has links to pre rooted system images but I haven't tried it.
http://www.asus.com/zentalk/thread-39487-1-1.html
Sent from my ASUS_Z00AD using XDA-Developers mobile app
The thread mentioned was opened in September '15... Didn't try downloading the files but can't imagine that there's a pre-rooted file out there already. Somebody would have known and told us, I guess
If anyone tried and it works, may you leave a line!
sent from my Binford Z00AD using tapatalk
nfc expert said:
if you want stop ad without root, you can try this : https://block-this.com/
Click to expand...
Click to collapse
kenbo111 said:
As far as Adaway goes, try this https://block-this.com
Click to expand...
Click to collapse
There are several other VPN based ad blockers as well. AdClear, AdGuard, and I think some more.
I played with some of them when they first started coming out, but always returned to the host file based blocker, because it was easy and worked fine with root. I think the phone has plenty of RAM and CPU to run these VPN ones, but I haven't been annoyed to try them again. So far uBlock Origin in Firefox has been fine. In the almost two days since unrooting I've used one app which shows me ads.
IDEDALE said:
Asus has integrated a firewall iptables recent months.
Asus mobile manager -> User Data -> Restrict (bottom of screen)
Click to expand...
Click to collapse
Thanks for the tip, I didn't know about it. This was easy enough to setup, even if it doesn't have as many features as AFWall+. I haven't tested to make sure it works.
My idea to get root on Asus' Marshmallow release is to install just the system, but keep the unlocked bootloader and ifwi from Lollipop. It should be easy enough to modify the updater script to only flash the system and boot image, while leaving the bootloader and ifwi alone. I don't know if that will work, or if the system will crash when it finds an old ifwi, or if the bootloader will fail to load the new system. With an unlocked bootloader, root is trivial.
As long as the bootloader is in place, it should be easy to recover from a broken system.
Don't take my word for it though, these are just ideas, and I'm not ready to try them yet. My warranty is over at the end of the month, so I'll unlock my bootloader then.
Hi all, kinda new to this whole game.
Couldn't find anything about rooting 5.1.1, only 4.2.2.
If there's no way to root 5.1.1, would you recommend reverting to 4.2.2 and then rooting it? Are there any improvements from using that version over 5.1.1?
Rooting 5.1.1 is the same way as on 4.2.2, unlock bootloader, flash custom recovery and flash super su.
I would recommend you to revert to 4.2.2 if you want a better performance, but if you want to stay on 5.1.1 make sure to use parrotmod to increase performance
Nexus Root Toolkit make it very easy.
thanks for the tips. i was able to root it, but now i'm trying to install the Xposed framework and it's telling me
cp:write error: No space left on device
meanwhile there's about 5 gigs of space since i flashed it down to 5.0 from 5.1.1
interestingly enough, after i root it and try to install busybox, it tells me free space is unavailable for /system/xbin as well as all the other options i try to change it to (/su/xbin, etc).
anyone know if something went wrong at some point?
PlayerThirteen said:
thanks for the tips. i was able to root it, but now i'm trying to install the Xposed framework and it's telling me
cp:write error: No space left on device
meanwhile there's about 5 gigs of space since i flashed it down to 5.0 from 5.1.1
interestingly enough, after i root it and try to install busybox, it tells me free space is unavailable for /system/xbin as well as all the other options i try to change it to (/su/xbin, etc).
anyone know if something went wrong at some point?
Click to expand...
Click to collapse
Your /system partition is full, try to remove something you don't need
iwjosi said:
Your /system partition is full, try to remove something you don't need
Click to expand...
Click to collapse
Thanks for the advice. How do I know what i can remove? If i flashed the tablet multiple times (tried diff versions of android), would that have bloated the /system partition?
Is there something specific i should be careful to leave in?
PlayerThirteen said:
Thanks for the advice. How do I know what i can remove? If i flashed the tablet multiple times (tried diff versions of android), would that have bloated the /system partition?
Is there something specific i should be careful to leave in?
Click to expand...
Click to collapse
you can remove google apps like youtube, hangout, g+ etc
anyone know if the play store can detect that a device is rooted, and prevent pokemon go from showing up in the store?
or is it just not detecting on my tablet possibly from the model of tablet i have?
i checked the official requirements page and there's nothing 'targeting' specific devices, the device just needs to haev Android 4.4+, but i'm not seeing it in my play store for whatever reason.
(my device is a nexus 7, Android 5.0)
i do recall that, before rooting my device, i'm pretty sure i was able to see and DL pokemon go on this tablet when it was running 5.11 before the root was performed
nvm, i found a site hosting the apk for the app. now just trying to make all the pieces work together on the nexus 7
you need to install Magisk to play pogo on a rooted tablet. magisk will disable the root so pogo will load.
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Flash a custom rom and install the nano gapps from http://opengapps.org/ if you want to install more apps.
But I wouldn't recommend it since it lags a lot without parrotmod speeding things up. Use the N7 2013 instead.
Magisk will not install on a 5..1.1 ROM because it needs systemless root and this is availabe only on 6.0 or greater ...
Thanks for the added tips. It's too bad this Magisk program only works on 6.0+.
I've tried everything detailed in this guide, including hiding the root with modules in Xposed, but i can't get the logins i created for PoGo to authenticate. I think i'm going to have to throw in the towel on this one.
AndDiSa said:
Magisk will not install on a 5..1.1 ROM because it needs systemless root and this is availabe only on 6.0 or greater ...
Click to expand...
Click to collapse
you might want to rethink that. It works fine on my 5.1.1, as stated in the magisk post "Magisk supports all the way down to Android 5.0 (SDK 21+) (thanks to the new method and busybox environment)"
---------- Post added at 03:21 AM ---------- Previous post was at 03:01 AM ----------
PlayerThirteen said:
Thanks for the added tips. It's too bad this Magisk program only works on 6.0+.
I've tried everything detailed in this guide, including hiding the root with modules in Xposed, but i can't get the logins i created for PoGo to authenticate. I think i'm going to have to throw in the towel on this one.
Click to expand...
Click to collapse
Don't use xposed, either don't install or disable when you don't need it. Someone mentioned that pogo won't work if xposed was installed, but i didn't think twice about it since mine worked with xposed installed, until today. So today I disabled xposed, then restarted, and it works again.
oh, thanks man. i'll def try it out -- see if i cant get it to work with Magisk. I appreciate you pointing that out
g96818 said:
you might want to rethink that. It works fine on my 5.1.1, as stated in the magisk post "Magisk supports all the way down to Android 5.0 (SDK 21+) (thanks to the new method and busybox environment)"
---------- Post added at 03:21 AM ---------- Previous post was at 03:01 AM ----------
Don't use xposed, either don't install or disable when you don't need it. Someone mentioned that pogo won't work if xposed was installed, but i didn't think twice about it since mine worked with xposed installed, until today. So today I disabled xposed, then restarted, and it works again.
Click to expand...
Click to collapse
Pardon my newb, but this workaround method is what i'm trying to achieve through all this.
In short, rooting, then using Xposed modules to hide the fact that 'mock locations' is enabled and faking my GPS location with it. (we live in a tiny town and want the device location moved to a big city).
Without Xposed installed, is there any alternate way that I can hide from PoGo that mock locations is enabled? Per the method linked, that was the one way to make it work, at time of writing.
Or even better, since the linked method actually didn't work on my device (pogo account 'wouldnt authenticate' -- not sure why but assuming its caused by xposed or some kind of root detection), would you know of a different way to fake my GPS location and hide it from PoGo on a Nexus 7?
Just to clarify, I followed your advice and installed Magisk already.
So I have a Magisk-ready device, just not sure where to take things from here, since I realized my instructions uses Xposed specifically to circumvent PoGo
Help
I'm in the same position.
How to remove thee apps? nexus tab 7 2012 is rooted running 5.1.1
Whic ROM should i use?
PlayerThirteen said:
Pardon my newb, but this workaround method is what i'm trying to achieve through all this.
In short, rooting, then using Xposed modules to hide the fact that 'mock locations' is enabled and faking my GPS location with it. (we live in a tiny town and want the device location moved to a big city).
Without Xposed installed, is there any alternate way that I can hide from PoGo that mock locations is enabled? Per the method linked, that was the one way to make it work, at time of writing.
Or even better, since the linked method actually didn't work on my device (pogo account 'wouldnt authenticate' -- not sure why but assuming its caused by xposed or some kind of root detection), would you know of a different way to fake my GPS location and hide it from PoGo on a Nexus 7?
Click to expand...
Click to collapse
There is another way, but it will disable your ability to use gps . use lucky patcher to install your spoofing app as a system app, then you don't need to enable mock locations and don't need xposed since the xposed modules don't work anyways. after that, install an app called disableservice and disable the 3 locationsharing services in google play service. What this does is prevent your real gps to overwrite your mock gps data.
try at your own risk of being banned
g96818 said:
There is another way, but it will disable your ability to use gps . use lucky patcher to install your spoofing app as a system app, then you don't need to enable mock locations and don't need xposed since the xposed modules don't work anyways. after that, install an app called disableservice and disable the 3 locationsharing services in google play service. What this does is prevent your real gps to overwrite your mock gps data.
try at your own risk of being banned
Click to expand...
Click to collapse
Thanks mate, i'll give it a shot!
Dear XDA,
I'm just looking for some advice. I've been a power user for awhile. I have rooted all my nexus devices I owned but never a Samsung device due to knox breaking and thus making root irreversible. I've been getting into alot of cross architecture computing with arm and x86 (with a keen interest in simulation and research ). I found an app called gnuroot debian which allowed me to run Linux on a non-rooted device. Back with MM everything ran fine. Now with nougat and its pure SELinux enforcing some of the apps won't run because SELinux blocks shared executable stacks. Certain gui apps won't work while I can get some command line to work. Nougat brings me all my note features so I wanna keep that.
On the other hand on my rooted nexus 7 using linux deploy I'm able to run most packages and distros, all I need is to find away to get hardware acceleration. I can also change selinux via root but that defeats the purpose of using no-root app.
So idk what to do? I'm worried that root will kill some apps for me, which apps would I not be able to use with root?
I do not know if a lot op people know this:
I just checked on a Moto Z if the app "SafetyNet Test" reports an issue after I switch off "root access for apps and adb" in developer settings. It does not, it reports a safe device!
Switching root access on, "SafetyNet Test" recognizes immediately a problem.
I always thought, switching off root access would still case a problem.
Congratulation LOS team!
For root access I am using the addonsu-16.0-arm64-signed from LOS.
So, my question, what is the advantage of Magisk?
ischninet said:
I do not know if a lot op people know this:
I just checked on a Moto Z if the app "SafetyNet Test" reports an issue after I switch off "root access for apps and adb" in developer settings. It does not, it reports a safe device!
Switching root access on, "SafetyNet Test" recognizes immediately a problem.
I always thought, switching off root access would still case a problem.
Congratulation LOS team!
For root access I am using the addonsu-16.0-arm64-signed from LOS.
So, my question, what is the advantage of Magisk?
Click to expand...
Click to collapse
For LOS users who simply want superuser access (root) of the OS, the su add-on will certainly suffice. Magisk allows users to implement a fully systemless environment with which to manage & utilize root access. Magisk includes a myriad of systemless modules such as XPosed, BusyBox, audio mods, etc. These modules can be applied and used without touching the /system partition, which comes in handy for users who plan on installing future OTAs without breaking root. Magisk also includes a nifty feature known as "su hide" (Magisk Hide), which has the ability to hide root from certain apps that check for it (Netflix, Google Pay, etc), allowing these apps to run normally on rooted devices. And, as you've already noted, Magisk root can pass both basicIntegrity & ctsProfile within Google's proprietary SafetyNet protocol.
When deciding between the LOS root add-on and Magisk systemless interface, it comes down to personal preference and the individual needs and expectations of the user.
Viva La Android said:
For LOS users who simply want superuser access (root) of the OS, the su add-on will certainly suffice. Magisk allows users to implement a fully systemless environment with which to manage & utilize root access. Magisk includes a myriad of systemless modules such as XPosed, BusyBox, audio mods, etc. These modules can be applied and used without touching the /system partition, which comes in handy for users who plan on installing future OTAs without breaking root. Magisk also includes a nifty feature known as "su hide" (Magisk Hide), which has the ability to hide root from certain apps that check for it (Netflix, Google Pay, etc), allowing these apps to run normally on rooted devices. And, as you've already noted, Magisk root can pass both basicIntegrity & ctsProfile within Google's proprietary SafetyNet protocol.
When deciding between the LOS root add-on and Magisk systemless interface, it comes down to personal preference and the individual needs and expectations of the user.
Click to expand...
Click to collapse
Nice explanation. I've always used true root and not systemless and have never tried magisk. I am delighted by how easy lineage makes it to add root and that it's own privacy guard software handles the su permission. To me from outside looking in magisk just adds a ton of complications to simple access to the modify system files to which it doesn't actually modify because it's systemless. I definitely prefer traditional root access that lineage allows. In a perfect world Google would allow root access how lineage implements it. You have to flash a file and turn it on and assume all responsibility. I don't know what Google is so afraid of. People use the argument that people would be bricking their phones left and right but some how Microsoft and every Linux distro has allowed access to system files without issue.
Joe333x said:
Nice explanation. I've always used true root and not systemless and have never tried magisk. I am delighted by how easy lineage makes it to add root and that it's own privacy guard software handles the su permission. To me from outside looking in magisk just adds a ton of complications to simple access to the modify system files to which it doesn't actually modify because it's systemless. I definitely prefer traditional root access that lineage allows. In a perfect world Google would allow root access how lineage implements it. You have to flash a file and turn it on and assume all responsibility. I don't know what Google is so afraid of. People use the argument that people would be bricking their phones left and right but some how Microsoft and every Linux distro has allowed access to system files without issue.
Click to expand...
Click to collapse
It's a common misconception, but systemless root is "true" root in a sense that /system can be mounted as r/w, and can be modified if the user so chooses. It's really just a matter of preference. Root can be hidden from apps far easier in a systemless scenario. To my understanding, the biggest difference between system-wide root and systemless -- in terms of implementation -- is that the root binaries are introduced into the OS in two different manners -- one by modifying the /system partition directly and the other by way of the boot image. Both methods allow for system level modifications, and give the user full and unfettered access to the core of the OS. It's more about the method of achieving root than it is the final result. In sum, the term "systemless" root in no way means that the /system partition cannot be modified. Rather, it implies that the Android OS was rooted without the /system partition being modified or mounted r/w. This is especially necessary these days, with so many devices having dm-verity, Android Verified Boot (AVB 1.0, AVB 2.0), etc.