Database Develop

Temporary Root for Xoom?

Is there any work being done for a temporary Root option? I ask because it seems that I only need Root for certain issues!
Scenario: Access my hosts file, Tor...etc!
TIA

What is the benefit to only being rooted temporarily? Honestly there isn't a huge security benefit to it, and usability suffers because you have to root it when you want to do anything in your scenarios.
Why not just use SuperUser.apk and not have it remember any associations? That way you only authorize root privileges when you need them, but can stay rooted.

Temp rooting shouldn't even be released for this since we have a permroot so either root your xoom and leave it that way or stay stock

I wouldn't mind a temp root because I haven't rooted from the start, waiting for the 4G upgrade, and because fastboot oem unlock requires a wipe, I don't want to do it, then restore, then do it again. A temp root would be perfect.

I actually have to second Archon810's post. I also would like a temp-root solution so that I could backup my Xoom BEFORE fastboot oem unlock, due to the wipe. I moved all my games off my G2, and started playing further on the tablet screen. However, now I'm gonna lose all those save games. Kinda sucks...

flamingblue8z said:
I actually have to second Archon810's post. I also would like a temp-root solution so that I could backup my Xoom BEFORE fastboot oem unlock, due to the wipe. I moved all my games off my G2, and started playing further on the tablet screen. However, now I'm gonna lose all those save games. Kinda sucks...
Click to expand...
Click to collapse
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.

Not getting what the issue is here either. With superuser you have full control over what app has root access and which not. Root access can be granted and revoked at any time. So certain "things" can have root access, certain not...

cwizardtx said:
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.
Click to expand...
Click to collapse
I believe people want something like the "temp" root achieved for Sensation: http://forum.xda-developers.com/showpost.php?p=15260896&postcount=1; it works quite well for me (no unlock required, one can disable unwanted apps, Titanium works).
"Temporary", since after rebooting updated parts of a locked NAND are overwritten and the changes lost.

This would be useful if you wanted to watch movies from the Market but still wanted to use other things that required root access. Reboot clean, watch movies, run root app, make backups.
My wife's MyTouch 3G Slide had a temporary root app that she only needed when she needed to use the phone as a WiFi Hotspot.

JohannFaust said:
I believe people want something like the "temp" root achieved for Sensation: http://forum.xda-developers.com/showpost.php?p=15260896&postcount=1; it works quite well for me (no unlock required, one can disable unwanted apps, Titanium works).
"Temporary", since after rebooting updated parts of a locked NAND are overwritten and the changes lost.
Click to expand...
Click to collapse
The only reason this is out, is because they don't have real root. And yes you can disable apps...but they are still there.
Sent from my PG86100

I still think a temp root solution would have been nice. Because I just rooted (which is less root, more NAND unlock) so I could upgrade to 3.2 and have full root functionality from MyBackup Pro. Some stability issues, but I will try reflashing in a bit. Would have really been nice to back everything up first, though.

Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk

playya said:
Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
This is also why the first thing you should do is fastboot oem unlock. You haven't rooted and all apps will still work. But if you decide to root later, you will not loose anything.

playya said:
Guys it seems like everyone is concerned about saving apps prior to rooting. Fyi- you can use Androidcommander and back up all your apps and install apps prior to rooting or after rooting. So if thats your concern problem solved...Don't root if your scared but when you follow directions its really a simple root and you learn a little as well.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
No no, I have my apps already backed up by MyBackup Pro. Its my APP DATA, the save games n'at, that I was trying to back up. Its a moot point now, for me, since I already bit the bullet and rooted, but it would have been valuable to others.

bwcorvus said:
The only reason this is out, is because they don't have real root. And yes you can disable apps...but they are still there.
Sent from my PG86100
Click to expand...
Click to collapse
Not true at all. The Droid X could get permanent OR Temp Root from Z4root, as could MANY phones on froyo. It could Temp root 99% of phones on froyo or earlier according to the developer and the numerous people chiming in that it worked for htem. Some things i just want temp root, so i can backup or access some file. Otherwise, i don't need root full time on this tablet, didn't need it full time either on my Galaxy tab, which i also could Temp root with Z4Root. And did numerous times with ease and no problems
Some of us don't need permanent root. Why is that so hard to understand. I have full root on my X, don't need that on my tablet. Biggest reason is for what was listed, don't want ot have to wipe the whole device. That is just overkill and silly to me. If you want root with a Xoom you realy need to do it from day 1 so you lose nothing.

cwizardtx said:
Either I have completely forgotten how linux works, or you guys just don't get it. AFAIK there's no "temp root". You root, you're rooted.
Click to expand...
Click to collapse
No offense but by saying that you don't know how linux works... If you are on the command line in Linux and type SU or SUDO plus a command after it you gain TEMPORARY ROOT for that command once you put in the password. It is TEMP, after that command passes you are normal user again. Yes you can root yourself full time, but that is a silly thing to do on a linux system and removes a lot of security. Not hard to plug in a password the few times you need to access stuff or edit things

Legato Bluesummers; said:
don't want ot have to wipe the whole device. That is just overkill and silly to me.
Click to expand...
Click to collapse
that's my point, if I can root my HTC EVO without wiping why should I have to do that with my xoom?

Guys
Mybackup Root Androidcommander Titanium Backup can all put your rom back to where it was in minutes. It takes longer to.read why you don't want to root than it would take to restore IMO. Don't root of you don't want to but really do t use the my programs line..
No disrespect though just think with what we have today restoring is not that not big of a deal and after you root clockwork and nandroids are your best friends
Sent from my EVO rocking Evervolv Gingerbread

IceCreaMan said:
that's my point, if I can root my HTC EVO without wiping why should I have to do that with my xoom?
Click to expand...
Click to collapse
Yup thats holding me back, too. Unlike my phones (Hero and Desire) I have not rooted my Xoom on the first day just because I was unsure if I would keep it. Now I am stuck in this mess while one side of me wants to root and install 3.2 and the other side doesn't want to lose all the progress made in the apps/games/whatever...

Security Issues With Unlocking the Bootloader Without Rooting?

Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?

That's always a risk. Read playstore comments before installing anything.
Has nothing to do with being rooted or not...or boot loader state.
Sent from my Moto X cellular telephone...

Cozume said:
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
Click to expand...
Click to collapse
You could have asked at AC and I would answer it over there.
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified. I can flash custom recovery to your phone. Custom recovery give full root access to the phone. It is then easily possible to copy all your data from the phone and also disable the lock for your phone. Although if you encrypt your phone, then custom recovery will require the password to give access to the /data partition, which is where all the user datas are. I guess if someone is determine enough, then they can make an image copy of your phone and try to decrypt it.
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader. However, if the phone brick then you can't get back your data in the phone.

eksasol said:
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified.
Click to expand...
Click to collapse
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
eksasol said:
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader.
Click to expand...
Click to collapse
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.

Cozume said:
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
Click to expand...
Click to collapse
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system. Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Click to expand...
Click to collapse
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
If you have an older Android phone, you don't need to do anything except to enable USB Debugging and run a program to install root. But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection. But KitKat is much safer now.
You don't need root to install malware and virus to your phone. Just download an infected app or use unreliable app stores like Aptoide. Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Point I'm trying to make is, if the phone have unlocked bootloader, or even locked bootloader with custom recovery, and someone else have a hold of it, then all bets are off.

eksasol said:
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system.
Click to expand...
Click to collapse
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
eksasol said:
Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
Click to expand...
Click to collapse
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
eksasol said:
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
Click to expand...
Click to collapse
good to know!
eksasol said:
But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection.
Click to expand...
Click to collapse
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
eksasol said:
But KitKat is much safer now.
Click to expand...
Click to collapse
why is this?
eksasol said:
Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Click to expand...
Click to collapse
thanks, Amazon app store required that to be enabled to load apps from their app store.

Cozume said:
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
Click to expand...
Click to collapse
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
Click to expand...
Click to collapse
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA.
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
Click to expand...
Click to collapse
Yes. The actual component of root isn't the SuperSU app, but a 'su' binary. Without the SuperSU app, anything can have full fledged root access. You need SuperSU to control that access.
why is this?
Click to expand...
Click to collapse
For many reason, I'm not a developer so I can only talk about what I know and seen from a user perspective. It used to be that you can flash an exploited update.zip to modify the stock recovery of Android, in order to make it ignore the package signatures, so the recovery could flash any package without the correct signature. Now there are no such exploits for latest stock recovery. With USB Debugging enabled in Android 4.3 or newer, it would not even allow access when connected to a PC unless you accept to trust that PC in a pop up dialog in the phone, I'm not sure if it's mean the phone is totally invulnerable to exploits (like memory overflow), you'll have to ask someone smarter. Also apps like Framaroot that I just linked won't work anymore.

eksasol said:
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA. My guess is if you tried it with modified logo it will either fail or overwrite it.
Click to expand...
Click to collapse
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.

Cozume said:
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Click to expand...
Click to collapse
You already gave me enough thanks at AC.

eksasol said:
You already gave me enough thanks at AC.
Click to expand...
Click to collapse
what is your user name there?

Cozume said:
what is your user name there?
Click to expand...
Click to collapse
someguy

Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Sent from my Moto X cellular telephone...

eksasol said:
someguy
Click to expand...
Click to collapse
ok great!

kj2112 said:
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Click to expand...
Click to collapse
I am just trying to understand how all of this works.

Okay one thing why are you trying to unlock the bootloader without rooting?? Or did I read everything wrong? And yes unlocking the bootloader allows you to write to every partition of the phone. Except when HTC and you're s-on you have to manually flash the boot.img via fastboot. But with moto. There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty. Three it can disable functions on your phone like features, camera options I think and yeah etc. But if you follow instructions you won't have any problems ever rooting or shouldn't if you semi have a brain and know how to follow instructions if not well you can somewhat brick :$ I don't mess with moto much but I have. Sorry this thread was in my latest and scrolling through xda. Lol. You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
edit: link: http://forum.xda-developers.com/showthread.php?t=2575586&page=2

pball52998 said:
Okay one thing why are you trying to unlock the bootloader without rooting??
Click to expand...
Click to collapse
I rooted but a friend of mine is unlocked but not rooted. She wanted to be unlocked because it wipes your device so wanted to do it before she got the phone all set up. She is afraid of rooting. Anyhow, maybe she shouldn't have unlocked but she did.
pball52998 said:
There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty.
Click to expand...
Click to collapse
She has the dev ed so it doesn't void her warranty. And she may want to Wifi tether in the future so I told her she needs to unlock and root for that so get the dev ed. She did and unlocked but is afraid to go any further.
pball52998 said:
You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Click to expand...
Click to collapse
It increases the phone's resale value to unlock it.

eksasol said:
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
Click to expand...
Click to collapse
I thought I saw a thread where someone could relock the Moto X bootloader.
And what about this?
Re-Lock Your Bootloader

It should just be a command like fastboot_oem_lock or something but idk. And two if she has the dev edition. Root that thing!!! XD that's what it's for!! Just install twrp via goo manager. Wipe factory reset all that good stuff. After making a back up. Notice after backing up. Then flashing rom and gapps In that order. I mean its a lot easier than htc rezound or htc one, htc in general and such lol.
Sent from my crappy apple iPad.....

pball52998 said:
Wipe factory reset all that good stuff. After making a back up.
Click to expand...
Click to collapse
well, I didn't wipe and do a factory reset when I rooted so I guess I did it wrong, lol! That is what she is afraid of - not doing it right and messing up her phone.
And I don't have a backup, but do I really need one if I can flash the factory images?

For those of you on Republic Wireless, are you rooted and can you tether?

I'm strongly considering switching from Tmo to RW to save some money. I have the S4 currently, which is feature packed but just feels like a llittle kids phone. Since RWs version of the Moto X uses proprietary software for wifi calling, has this made rooting the device difficult in any way? If I want to run stock android but have root access with the X on RW will I have any difficulty or limitations/
Also, I tether occasionally, maybe once every few weeks when I'm on the go and want to use my Nexus 10 and there's no wifi around. I know RW opposes tethering. How likely are they to go after someone who tethers if they stay well below their monthly data? Have any of you heard back from them after tethering? And does androids built in tethering feature/app work once rooted, or will I have to use a third party tethering app?
Thanks.

legato89 said:
I'm strongly considering switching from Tmo to RW to save some money. I have the S4 currently, which is feature packed but just feels like a llittle kids phone. Since RWs version of the Moto X uses proprietary software for wifi calling, has this made rooting the device difficult in any way? If I want to run stock android but have root access with the X on RW will I have any difficulty or limitations/
Also, I tether occasionally, maybe once every few weeks when I'm on the go and want to use my Nexus 10 and there's no wifi around. I know RW opposes tethering. How likely are they to go after someone who tethers if they stay well below their monthly data? Have any of you heard back from them after tethering? And does androids built in tethering feature/app work once rooted, or will I have to use a third party tethering app?
Thanks.
Click to expand...
Click to collapse
YES! I'm on RW with unlocked bootloader (thanks middleman), and the WiFi tether app works perfectly (NO native/built-in tether ability on the RW variant). If you unlock your bootloader (see the China Middleman Back??) thread in the general sub-forum. let me know and I'll link you to the appropriate instructions.
I don't know if this will work with tethered root (PIE), but I doubt it. I only KNOW that it works if you have unlocked bootloader.
Additionally, the tether app I refer to "hides" tether usage, so likely they will assume you are using that data on the device itself. I've had no issues, but stay WELL within the 5GB limit (rarely exceed 2GB).
Good Luck

samwathegreat said:
YES! I'm on RW with unlocked bootloader (thanks middleman), and the WiFi tether app works perfectly (NO native/built-in tether ability on the RW variant). If you unlock your bootloader (see the China Middleman Back??) thread in the general sub-forum. let me know and I'll link you to the appropriate instructions.
I don't know if this will work with tethered root (PIE), but I doubt it. I only KNOW that it works if you have unlocked bootloader.
Additionally, the tether app I refer to "hides" tether usage, so likely they will assume you are using that data on the device itself. I've had no issues, but stay WELL within the 5GB limit (rarely exceed 2GB).
Good Luck
Click to expand...
Click to collapse
Thanks for your reply. The tethering/mobile hotspot is completely removed from the Moto X RW ROM if I'm understanding you correctly then?
Which tethering app do you use? and please do link me to the instructions you used. Does OTA updating still work when you unlock the bootloader and apply root?

legato89 said:
Thanks for your reply. The tethering/mobile hotspot is completely removed from the Moto X RW ROM if I'm understanding you correctly then?
Which tethering app do you use? and please do link me to the instructions you used. Does OTA updating still work when you unlock the bootloader and apply root?
Click to expand...
Click to collapse
OTA updating will stop working at the point you flash a custom recovery (which is required to root). You can cross that bridge when a new OTA comes out, as we will no doubt have to advise countless people on what steps to take to be able to accept the OTA. Basically it involves disabling any modifications made to /system, disabling Xposed (if installed), and flashing back STOCK RECOVERY. Being unlocked has no affect on being able to accept the OTA.
Here is the relevant thread. http://forum.xda-developers.com/moto-x/general/solved-republic-wireless-unlocked-t2755730
Be sure to use the specific wifi-tether app listed in POST # 2 in that thread. You'll notice that it didn't work for me until I did a complete return-to-stock for unknown issues. The built-in hotspot feature has somehow been disabled by RW, and attempting to use it results in the RW app immediately "stealing" back WiFi, and a message saying something to the effect of "WTF? The phone just stole back WiFi access" appears on the screen LOL! Neither the Xposed module or the entitlement bypass worked for me, with any of the options (including the Sprint-specific build.prop tweak).
PLUS, native tether does NOT 'HIDE' usage, so they might know you are indeed tethering!!! I don't suggest trying...
Good Luck, let me know if you have additional questions.

I got my Moto X a few days ago and I'm very impressed. Republic has the 30 day trial period, but I'm more 90% sure I'm sticking with it, but if I do want to return it, can I unroot/lock the bootloader? Will they check to see if it has been rooted?
Are these the instructions I should follow? I'm on 4.2.2
http://forum.xda-developers.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233

You can always flash back to stock but you can never return the phone to its locked bootloader state. It would read "relocked" and not "locked"
Sent from my XT1049 using XDA Free mobile app

SuperSU and SafetyNet / Android Pay

This is the place to discuss anything and everything related to SuperSU and SafetyNet / Android Pay.
To clarify, I am not currently actively doing any development on having SuperSU pass SafetyNet detection, or having Android Pay work; the same way I put no effort into beating other root detection methods such as various enterprise security tools.
In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU.
While I may not agree with Google's stance, I'm not about to go messing with payment systems. Is it possible though? Probably yes.
This thread has been created because you guys simply cannot stop talking about this, so these posts can now go here, where I don't ever have to see them.

Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?

0.0 said:
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
Click to expand...
Click to collapse
Root is a no no with android pay and I think custom ROMs are also out at the moment
Sent from my A0001 using Tapatalk

Pure Drive GT said:
Hey, thanks for your continued support for root on Android, was just wondering, is google making it harder to achieve decent root privileges, as in they don't want rooted devices or are they just unrelatedly changing up things which forces you guys to adapt?
On another note, is there any progress on root without the modded boot? This is by no means an ETA, just wanted to know if you think it's possible or the situation looks rather dire.
Thanks again for your many efforts!
Click to expand...
Click to collapse
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Many banking and financial apps restrict access on rooted devices; it's not just Google.
It makes sense in some ways: root access allows running things in the background to either circumvent, monitor, or interrupt program transactions. They're being paranoid, and I don't blame them.
I don't like the Google Pay concept (or Apple's either); like every other encryption or security system, it's destined to eventually be hacked.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Yep, I was able to add my debit card but not credit.
VZW LG G4

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...hy-android-pay-doesnt-support-rooted-devices/

shaggyskunk said:
Yet the Note 5 has been rooted for at least a couple of weeks
Click to expand...
Click to collapse
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.

Srandista said:
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Click to expand...
Click to collapse
I believe that it's only at&t and Verizon that locks the bootloader - And none in Canada and many other Countries.
Sent From my SM-N910W8 Running SlimRemix V5.1

Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.

NYZack said:
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
Click to expand...
Click to collapse
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.

Lrs121 said:
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Click to expand...
Click to collapse
I also found that having an unlocked bootloader will stop Pay working. When MM released I decided to go fully back to stock but kept the bootloader unlocked so I could flash MM. Pay still failed, so I've given up and gone rooted again.
Sent from my Nexus 6 using Tapatalk

Ch3vr0n said:
@Chainfire if you actually are able to pull off fully working stable root WITHOUT modifying the /system does that mean you MIGHT have opened the door into having root AND still being able to get OTA's?
Click to expand...
Click to collapse
osm0sis said:
Yup, all you'd need to do is reflash stock kernel to pass the boot partition EMMC check, or, we could automate restoring the previous stock kernel, flashing the OTA and then injecting the new stock kernel with root after flashing (à la AnyKernel2 or MultiROM). So many exciting possibilities there where custom recoveries are concerned.
Click to expand...
Click to collapse
Chainfire said:
Honestly it's not so different from using FlashFire to flash re-flash system, then OTA, then re-root. But it is easier, yes.
Click to expand...
Click to collapse
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Andrew Morykin 12:24
This should retain Android Pay, right?
Click to expand...
Click to collapse
Chainfire 12:58
+Andrew Morykin if it does, then it's by accident and not by design, and Android Pay will be updated to block it.
Click to expand...
Click to collapse
https://plus.google.com/+Chainfire/posts/aJbqUZ8PEP4
also, I was confused by this:
Chainfire said:
- I have not tested with encrypted devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935
Aren't
Nexus 6P / angler
angler-mdb08k-boot-systemless.zip
Click to expand...
Click to collapse
and
Nexus 5X / bullhead
bullhead-mdb08i-boot-systemless.zip
Click to expand...
Click to collapse
encrypted out of the box?

dabotsonline said:
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Click to expand...
Click to collapse
How is that a downside?
It's exactly the same with every other form of root you will ever see. They don't want to support Android Pay (and some other stuff) on rooted devices. If we find a root that allows it, they will update their system to detect and block it. That cat and mouse game will not end as long as Google doesn't want Android Pay on rooted devices.
Maybe someone will make apps/modules that help circumvent this, but it certainly will not be me.
also, I was confused by this:
Aren't
Nexus 6P / angler
and
Nexus 5X / bullhead
encrypted out of the box?
Click to expand...
Click to collapse
Still can't test what I don't have.

russlowe73 said:
Factory images
Click to expand...
Click to collapse
So basically I have to go back to 100% stock using ADB, and then flash the new SuperSU stuff with any custom ROM? If so, what are the benefits of this other than getting Android Pay while rooted?

I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of root on the Nexus 6!!

efrant said:
Starting with Android 5.0, OTA updates are now block-based rather than file-based, so any modification to the system partition will cause the OTA to fail, even mounting the system partition as r/w.
Click to expand...
Click to collapse
Just to add to this, it's a whole-partition /system patch OTA if the device launched with Lollipop or later, anything that launched with KitKat is still receiving the old file-based patch OTAs. Modifying Settings.apk would likely trip either method for a lot of OTAs though, since it's a pretty central component.
galaxyuserx said:
I use Galaxy s6 G9200 HK with Kernel compiled by me, but i have problem with root 5.1.1 and i think in future too 6.0
These root method is integrated in kernel source or i can integrate with those "boot.img systemless" my selfcompiled kernel?(repack boot.img with kernel compiled by me)
Is possible to work this new root method to android 5.1.1?
I have problem with gain root when i use kernel compiled by me ( STOCK kernel have too this problem BOOTLOOPs and FREEZEs on boot system) and i don't know how slove it :/
I found on chineese forums root integrated in boot.img it working good and isn't comunicat "KERNEL is not SEandroid enforced" but when i try integrate my kernel with this boot.img error with boot system :/
Click to expand...
Click to collapse
Yup, it's all ramdisk changes so should be workable on any version of Android. Chainfire left instructions outlining the ramdisk changes in the WIP thread if you want to give it a try.
phishfi said:
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of on the Nexus 6!!
Click to expand...
Click to collapse
Yup, seems to be the case with most banking and root-detecting apps... for now.

Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.

secguy said:
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
Click to expand...
Click to collapse
Just ran it and it passed.

Went ahead and installed su on a stock nexus 5, so far working well, android pay does not work but that was me being stupid and changing the host file and dpi before setting it up
I do notice a little input lag after this, not enough to even make me consider removing root, but it is noticeable, anybody else with this?

Unroot and relock bootloader

I'm currently considering unrooting my turbo and relocking the bootloader but am not completely sure how. Looking for confirmation that I'll be doing it right.
1. Flash the fix to remove the unlocked bootloader warning
2. Uninstall all root apps (xposed and superSU)
3. Flash stock recovery
4. Fastboot oem lock
I'm already on the stock mm rom and I think I might have to flash a stock bootloader before the stock recovery, but not sure.
Thanks for any help.

Any reason why? Will be very hard -- almost impossible to unlock it again. OK, very hard.
subprime said:
1. Flash the fix to remove the unlocked bootloader warning
Click to expand...
Click to collapse
THAT should have already been done, when you first unlocked the bootloader.

ChazzMatt said:
Any reason why? Will be very hard -- almost impossible to unlock it again. OK, very hard.
Click to expand...
Click to collapse
I'm getting tired of carrying this phone and another for work. I need mobile iron for my emails and haven't found any solution to get it to work while rooted.
And you answered my next question too. Would I be able to unlock it again. If i don't take any updates can't I just follow the same process to unlock and root again?

subprime said:
I'm getting tired of carrying this phone and another for work. I need mobile iron for my emails and haven't found any solution to get it to work while rooted.
And you answered my next question too. Would I be able to unlock it again. If i don't take any updates can't I just follow the same process to unlock and root again?
Click to expand...
Click to collapse
In the beginning you could only use Sunshine one time per phone. I think some others have locked and unlocked, but I'm not sure the process. I think you have to contact Sunshine team? Others can answer if they remember how to do it.
Can you use Magisk to hide root? It seems to work with Android Pay and other stuff.

I'll take a look and give it a shot. Phone has to be encrypted too and from what I read I'm pretty sure I have to unroot for that.
Thanks

My phone is encrypted, rooted with Magisk, and I use Outlook for work

Bootloader logos to replace unlocked warning:
https://forum.xda-developers.com/showthread.php?p=72047829
Choices of TWRP or ADB.
I'm currently using the Dark Google ATAP.

TheSt33v said:
My phone is encrypted, rooted with Magisk, and I use Outlook for work
Click to expand...
Click to collapse
We used to be able to just use outlook, but they switched to touchdown with mobile iron. They don't control it to the fullest, but the permissions it has are ridiculous. They just recently completely disabled smart lock.
I have it set up on a 2nd gen moto x right now and would just swap the numbers but that thing can't do voice and data simultaneously, which I need regularly (gps and phone calls).

subprime said:
We used to be able to just use outlook, but they switched to touchdown with mobile iron. They don't control it to the fullest, but the permissions it has are ridiculous. They just recently completely disabled smart lock.
I have it set up on a 2nd gen moto x right now and would just swap the numbers but that thing can't do voice and data simultaneously, which I need regularly (gps and phone calls).
Click to expand...
Click to collapse
Lame. Well hopefully Magisk can work its magic...sk.