I am considering this phone as a replacement for Note 7, so I have some questions about root.
Does it break Android Pay, and if so, is it permanent? Like does it fry "secure element?" Or can one root, install adblock .hosts, but then reverse the effect?
Also, if the phone is rooted, can it still be secured? So, if I lose my phone, can someone plug it into usb and flash/wipe data? Or can it be secured, so that it could only be tampered by the owner?
Thanks.
nabbed said:
I am considering this phone as a replacement for Note 7, so I have some questions about root.
Does it break Android Pay, and if so, is it permanent? Like does it fry "secure element?" Or can one root, install adblock .hosts, but then reverse the effect?
Also, if the phone is rooted, can it still be secured? So, if I lose my phone, can someone plug it into usb and flash/wipe data? Or can it be secured, so that it could only be tampered by the owner?
Thanks.
Click to expand...
Click to collapse
Gentle bump.
At the current moment there's currently no root yet (although Chainfire did got seamless root working with boot image mods but is still working on getting everything done) and there's currently no custom recovery.
Also, Google hasn't used SE for the longest time since Verizon and other carriers has been locking out that chip on the SIM card for a long time. Instead they do some sort of emulation of sort which is stored in the data encrypted so if you ever wipe your phone you don't have to worry about the SE being all jacked up without unregistering it first.
In terms of being able to use Android Pay, it does check to see if the bootloader is unlocked but there's already a kernel out that bypasses that check and I'm able to use it just fine so even if you are rooted I'm sure you could just use that kernel and it'll still work (I'm not able to test with root since the root isn't publicly available yet but usually you can go into SuperSU and tell it to hide su and android pay should still work if it does check to see if su is installed on top of the bootloader being unlocked). So there's always ways around it.
Related
So, I have been searching a bit on how to root the Nexus 7 2013. The process I have found seems pretty simple, even for me, as someone who never worked with a Nexus device before.
Unlock bootloader, flash recovery and flash the root.
But the first step, unlock bootloader, has a problem: it wipes all the user data (including SD Card data!!). As the tablet isn't mine (but I was asked to root it), I can't simply just clear all of its data and do the whole process. Thinking of that, I googled a bit on how to root without unlocking bootloader, but I have found nothing (all recent Sony phones, with a few tricks and the right tool, can do that) regarding the 2013 model.
I'm not sure if there is actually no way to do that or my search skills suddenly got horribe... So, the thing is: Is there a way to do that? Root without having to unlock bootloader (and, thus, wiping all data)? Or I have to unlock it?
EDIT: I found this Toolkit, but did a search and nothing regarding that in the 22 pages of the thread...
http://forum.xda-developers.com/showthread.php?t=2389107
Another few questions that I'm lost: I still haven't quite understood why I have to flash the stock ROM back after I do the whole process... So, why?
And, also, what do I lose unlocking bootloader? I mean, the tablet isn't mine (it's from my younger brother), so the easiest, the best, so keeping OTA updates for example are essential. Do I lose it? What else?
It sounds, for me, some silly questions, but I'm still confused... Seems like doing that kind of stuff is easier with my Sony phone. I don't know if it is due me being used to it, but Nexus is sounding to be WAY more hard than everyone keeps saying it is...
Thanks in advance...
Tell them what is going to happen if they want root. Backup as much of their data as you can, then unlock it. You should be able to get most data backed up one way or another.
At the moment you cannot unlock without wiping because the bootloader enforces that. There might be a way to get around that in the future, but not right now.
When you root, use SuperSU v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
Versions prior to that had an issue with preventing OTAs from completing.
1.60 may have some other issues with changes to OTA survival mode.
Not sure where you read you had to flash the stock rom, but it isn't necessary.
You don't really "lose" anything by unlocking it. Someone might bypass your lockscreen to get at your data, but there is a big inconvenience factor leaving it locked (because eventually you'll want it unlocked, at which point it become more painful to backup/restore your data), so you'll have to decide if it is worth the tradeoff.
The issues with stuff not working after unlocking don't have to do with the unlock itself. They have to do with folks rooting and then using their root power to install changes, which then start breaking things.
If you just install SuperSU 1.55 and don't install themes, APM mods, etc. etc. then everything should still work (except apps which specifically won't work, for security reasons, if they detect root)
@sfhub
Thanks for the answers. As I said, I have some Android knowledge, but still got confused with a new "kind" of device. Once again, thanks
I've got a new t807a from AT&T. According to the "about device" settings page, SE is "enforcing." My understanding is that this conclusively indicates that my bootloader is locked. It's currently running Android version 4.4.2, build number kot49h.T807aucu1ank1
I don't need a custom ROM and I don't care about tripping my knox counter (per se). I just want root. I've asked this in several relevant threads this week and gotten contradictory responses. Is there or is there not currently a method to root my tablet?
If not: is there hope? This is a great tablet but I can't live with the bloat for 18 months until I can afford a replacement. I CAN still return it and eat the 70-dollar "restocking" fee.
Thanks in advance.
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
TheArtiszan said:
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
Click to expand...
Click to collapse
So what does that mean for my t807a?
thorvindr said:
So what does that mean for my t807a?
Click to expand...
Click to collapse
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
skeeterpro said:
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
Click to expand...
Click to collapse
Thanks. I have been following that. Just hoping someone knows something I don't I suppose.
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
DUHAsianSKILLZ said:
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
Click to expand...
Click to collapse
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
thorvindr said:
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
Click to expand...
Click to collapse
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
DUHAsianSKILLZ said:
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
Click to expand...
Click to collapse
Well that blows. I guess that's what I get for buying off-the-rack.
Is this info outdated?
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
JMVPSlash said:
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
Click to expand...
Click to collapse
The built-in app manager lets you move apps to SD but I also have not found a solution to install directly to SD (without repartitioning the card). After several months of despair, I'm just now checking back to see if there's been any development on the bootloader front. It appears not. You can get root with Kingroot (also check out supersume, if that's still around, to replace kingroot's su app with supersu) but apparently the bootloader being locked prevents any non-official ROM from booting.
I have an unlocked HTC 10. I recently received an OTA update.
I have been using android pay just fine with no issues. However after the most recent Android Pay update. I was getting an error message explaining I may need to "unroot" my device..
My device has NEVER been rooted and android pay has worked great!!!
As an extra precaution, I did a factory reset to my phone, and re-downloaded android pay.
Now I get a new error, but very similar. When I try to add a card after installing, now it says
"Android Pay can't be used
Google is unable to verify that your device or the software running on it is Android compatible".
After already factory resetting and uninstalling/reinstalling the app... I'm not sure what to do... I don't want to root or flash... but I am looking for options....
thanks
I read somewhere that flashing elemental X as the kernel will fix this, but I'm waiting for more people to confirm. I'm also guessing flashing a new kernel doesnt requiring wiping or anything? and lastly, how can i backup my existing kernel to reflash in case **** goes haywire? anyway, hope that helps.
Also using S-OFF and LOCKED bootloader will work.
tabp0le said:
Also using S-OFF and LOCKED bootloader will work.
Click to expand...
Click to collapse
RELOCKED bootloader status won't let android pay work?
GottaStayFly said:
RELOCKED bootloader status won't let android pay work?
Click to expand...
Click to collapse
I"m not sure about that.
SafetyNet is looking for the flag that the unlocked bootloader throws, someone more familiar with recent flags than me should know which way the flag is set upon relocking bootloader.
The ElementalX kernel has the option, but I believe that's another option for s-off users, I'm not sure if it will work for s-on unlocked users.
I think if it doesn't pick up "relocked" when it checks SafetyNet, it wont be long until it does. This is a cat and mouse game, and google has the right to "take its ball and go home" with root users, I just wish they wouldn't use that against us enthusiast users, who are their best advocates since we carry so much weight on advising all the non tech oriented unrooted consumers when it's time for them to purchase new smartphones. We are the ones that the rest of consumers call for advice or when something is broken.
Will taking this update break root or cause other issues? Just received the notice a few hours ago.
Current setup:
S-on
Unlocked
Rooted
Stock ROM still (obviously)
SW v1.80.651.1
Sprint
I waited for the N7, and returned it without opening it before the fiasco. Because I was going to wait for the Pixel, which ended up being astronomical in price. So I waited for the V20, only to find it has a "Verizoned" bootloader. And just this past weekend I settled on the HTC 10.
If anybody can provide me helpful information, I would appreciate the consideration.
ETA: NM - simply made a copy on sd card, then renamed with .bak in update folder and nag went away. Seemed to be a small incremental update from .1 to .6.
So it sounds like the lesson here is if you haven't unlocked your bootloader yet, don't, if you want to use Android Pay. From what I've read, using Sunshine to go S-off LOCKED will allow android pay to work, as long as you aren't rooted. Also there are a couple kernels you can use to disable to check for unlocked bootloader.
Is this all correct?
Sent from my HTC One_M8 using Tapatalk
I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!
If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?
jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.
alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?
The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?
Hi everyone,
So it has been a year since I have my S9 and still there is no exploit released to the public yet, and I understand that Samsung really locked down the security on their US variants.
On the Samsung S6, what I used to have, had an exploit where you can only have shell root access in terminal by modifying the boot.img and flashing it via odin, and thats using Android Nougat for root.
Could this perform a similar function to the S9? Like at least have an exploit where you can have shell root via ADB?
If not, is there any status on the G960U in terms of rooting?
AndroidFan16 said:
Hi everyone,
So it has been a year since I have my S9 and still there is no exploit released to the public yet, and I understand that Samsung really locked down the security on their US variants.
On the Samsung S6, what I used to have, had an exploit where you can only have shell root access in terminal by modifying the boot.img and flashing it via odin, and thats using Android Nougat for root.
Could this perform a similar function to the S9? Like at least have an exploit where you can have shell root via ADB?
If not, is there any status on the G960U in terms of rooting?
Click to expand...
Click to collapse
modifying the boot.img will cause the signature from sammy to fail as would anything else that isnt stock and properly signed.
No dice man. Still nada on the U devices. You do know that root is becoming less and less necessary, right? What are you looking to get done with root?
youdoofus said:
modifying the boot.img will cause the signature from sammy to fail as would anything else that isnt stock and properly signed.
No dice man. Still nada on the U devices. You do know that root is becoming less and less necessary, right? What are you looking to get done with root?
Click to expand...
Click to collapse
Ohh... Well that's kind of a dud.
I always want root mainly for more control with my device, for example, uninstalling bloatware (this way if I dare to factory reset my device, I dont need to disable the apps I dont want after performing a factory reset, unless if I have to reflash the rom).
Another thing is controlling the CPU's frequency speed (or governor) for either saving battery or pump out more performance, which is technically the #1 thing I want as root.
I also want to disable OEM updates from forcing me to update my phone after 10 defers (I found a bug to bypass this and it's by using the notification draw and click on the setting button).
I also want to configure access of changing the 4G LTE bands (which changing the config file in the /efs partition, which I assume, is locked without su access).
Like I have mentioned, the shell root is basically minimum for me, and I wouldn't mind on that. HOWEVER, if all that I have mentioned can be performed without root and have a similar function of doing these, please let me know.
AndroidFan16 said:
Ohh... Well that's kind of a dud.
I always want root mainly for more control with my device, for example, uninstalling bloatware (this way if I dare to factory reset my device, I dont need to disable the apps I dont want after performing a factory reset, unless if I have to reflash the rom).
Another thing is controlling the CPU's frequency speed (or governor) for either saving battery or pump out more performance, which is technically the #1 thing I want as root.
I also want to disable OEM updates from forcing me to update my phone after 10 defers (I found a bug to bypass this and it's by using the notification draw and click on the setting button).
I also want to configure access of changing the 4G LTE bands (which changing the config file in the /efs partition, which I assume, is locked without su access).
Like I have mentioned, the shell root is basically minimum for me, and I wouldn't mind on that. HOWEVER, if all that I have mentioned can be performed without root and have a similar function of doing these, please let me know.
Click to expand...
Click to collapse
youre not gonna get true debloating with this, but if you flash the U1 firmware with an unknown CSC, it wont install any carrier bloat and is very much akin to a GSI. Nice and stripped down. Over/unclocking, yup, you need root. I never see people talking about clockin the processor anymore tho as the new kernels are so adaptive and are written quite well. Ive also never not wanted to install an OEM update, so im not sure how to stave those off, or if ite even possible. To change the bands your phone is utilizing, you just need access to the special menu from the dialer.
Do you know what's the dialer code to access the service menu on the S9 on Verizon?
I'm pretty sure its locked but it's worth a try.