I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0
Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!
Related
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
dont mess with itttt leave it until someone replies we need to extract your firmware, hold onto it if you not messing around, im not experinced enough but someone will pm you im sure
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=54642044
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Apparently there are many different circumstances under which the splash screen says custom, which have nothing to do with the bootloader being locked or unlocked. I seem to recall it showing up for people when they just switched to ART runtime, and in some cases it didn't even go back when they switched back to Dalvik. Many of the methods for making this not appear just involve cosmetically hiding it, not actually cleaning up whatever it is that is being detected.
What I wouldn't give to have this bootloader unlocked
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
If there is a dev that wants a s5 to experiment with to get the bootloader unlocked I'll be happy to donate my s5 if I can get it back after finding an exploit . But the dev needs to come with unanimous recommendation by the devs. Let me know I can still use my s3.
Sent from my SAMSUNG-SM-T537A using XDA Free mobile app
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
MGArcher007 said:
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
Click to expand...
Click to collapse
Sadly. ...We may never see the bootloader unlocked without a factory method...
It's encryption prevents us from even being able to open it into a usable state...
We need either an encryption key....or a new bootloader entirely...
Not happening any time soon....g
#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!
#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.
How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated
Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!
Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues
thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.
Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6
CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
jsmithfms said:
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
Click to expand...
Click to collapse
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
KennyG123 said:
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
Click to expand...
Click to collapse
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Honestly for the time being I wouldn't bother with ROMS for that Device and carrier at the moment. Especially being that its someone elses device. Towelroot should be a good start. If Im not mistaken I don't think its supposed to trip knox.
Sent from my HTCEVODesign4G using XDA Free mobile app
jsmithfms said:
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Click to expand...
Click to collapse
This is the riddle of the Sphinx my friend. I am sure the super devs have tried their best so far to crack it. It has been an ongoing effort to make phones more and more secure, not against the amateur developers and rooters, but against the hackers. These smartphones are now our personal computers, diaries, personal assistants, financial operator, and more. They basically are a person's (and business's) life. AT&T and Verizon have taken the big steps to appeal to the Exchange clients, corporate, government and military contracts. Even the general public want to know their phone is secure. This is what keeps me stuck on the Sprint network.
Have you tried Kingroot?
I successfully rooted my wife's AT&T S4 on OC3 lollipop (supposedly unrootable) with the desktop version. Mobile version didn't work but desktop did without a hiccup. Maybe it'll work on the S5.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
S5 on lollipop has a new nasty boot loader.... it was a miracle on its own that they ever came up with safestrap to duck the boot loader on earlier versions of android
Hi, long time lurker here. I want to start by saying how great and informative this site is. Anyway, my nexus 6 came in from the mail like 5 hours ago, did all the updates from 5.0 to 6.0 and it's now running Marshmallow mra58n. Question is should I root it immediately and if so, are there any guides I can follow? Much love to you all, I'm not exactly pro at this kind of things but I can follow instructions since I have competently rooted my past phones which were an HTC M7, M8 and a Samsung Galaxy Note 10.1 tablet.
Thank you.
Edit: Phone is also unlocked, I currently have no SIM card
start here..
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've been looking at the Nexus Root Toolkit since I am kind of confused on how to proceed with anything at all, is that ill advised since I've read that there are problems with the USB cable disconnecting during reboot?
Also, thank you for the reply.
I used the NRT without issue. Just follow the guide step by step.
Sent from my Nexus 6 using Tapatalk
and, dont touch the usb cable while the phone is processing your commands!
j/k, never even heard of the USB cable "problem"
I just used the toolkit today to unlock and root my N6.
Sent from my Nexus 6 using Tapatalk
I rooted last night initially using manual method described in the first link provided, however after some driver issues ultimately used the 2.1.0 rootkit to uninstall and reinstall all drivers. That too alone saved me tons of time and either method is simple if you can follow instructions.
Totally recommend rooting and then experimenting with custom roms, its like getting a new phone everyone you install a new rom.
Have fun!
Kristine,
In answer specifically to your question "Should I...?" my answer is "No". It really depends on what you think you'll get from it - why do you want to do it? What specific benefits do you want?
The reason that I say "no" is that I've been rooted on all my several phones for years, and I've decided that for me the annoyance of having to manually flash ROMs outweighs the benefits - particularly now that Google are releasing frequent security updates. The moment you root your device the OTA (over the air) updates no longer work.
For me the major reason for rooting was to have a firewall. The other things (wakelock detection, double tap to wake, auto-hibernation...) were great but not showstoppers. Now that there is a non-root firewall (Netguard) I'm happy to leave my phone unrooted. I haven't had an OTA to apply yet, so if I have any problems then I might change my mind, but my advice would be to think hard about why you want root before you buy yourself into a world of tinkering...
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Dammit, are you kidding me? I just downloaded and setup everything, figured I'd do all everything else tomorrow... Oh, well I can do it again I suppose.
Kristine-N said:
Question is should I root it immediately....
Click to expand...
Click to collapse
Because I don't want a white interface, rooting is necessary. Google forces to many things, like forced encryption, useless apps and a white interface (battery drain). When rooting was impossible I would not have bought a Nexus.
Short answer: No!
Long answer: Well, it's sill no, but you can or even should do a couple of things.
First if all, allow OEM Unlocking in development settings. There are gazillion how-tos to switch developer mode on, and tick that switch. Google has borked OTAs already, and if your phone doesn't boot, and the switch is off, then you're boned, you can send it for repair. But if you can unlock you bootloader, then you can flash a custom recovery and make your phone working again.
Second, if you do plan to root your phone in the near future, you should unlock the bootloader now, while it's still new, because it will erase everything (IMHO this would be sufficient as a security measure, the Enable OEM Unlocking is overkill).
As for the main question if you don't have any specific ideas what you want the root for, then don't root your phone. It's a clear and present security risk, and you're just one too many "Allow" taps from letting someone acquire your passwords, clone your IMEI, and download your personal stuff. My motto is, if you don't know what exactly root is, what it does, then you don't know how to prevent exploits that need it to run.
Also if you modify your phone in any way, and that includes rooting, you won't receive the monthly OTAs, and will have to flash it manually.
And finally, don't use toolkits on a Nexus. Spend another hour reading about the matter and you will find out typing adb and fastboot commands is a easy as clicking buttons on toolkits. There is nothing extra in them, they just download the images to flash, and "type" these commands for you.
Unlock bootloader and don't root it for now. After some time, if you feel like you're missing some features that you can obtain only with root, then go ahead. But for now I would strongly recommend to stay stock and see how it goes...
Hi I've been using a custom rom for quite some time now but I decided to go back to stock as I don't really see the benefits.
the issue I'm having is despite flashing a stock rom in Odin and seemingly completely unrooting the device, apps like google pay aren't allowing me to use them as they say the device has been rooted or modified in some way.
in the settings it clearly says my device is official status, does anyone know how to overcome this issue please? I prefer to use google pay to my cards as I often lose them if I take them out
thanks
Drizzy xS said:
Hi I've been using a custom rom for quite some time now but I decided to go back to stock as I don't really see the benefits.
the issue I'm having is despite flashing a stock rom in Odin and seemingly completely unrooting the device, apps like google pay aren't allowing me to use them as they say the device has been rooted or modified in some way.
in the settings it clearly says my device is official status, does anyone know how to overcome this issue please? I prefer to use google pay to my cards as I often lose them if I take them out
thanks
Click to expand...
Click to collapse
well it was probably written in every thread when you downloaded twrp and followed the guide to root that this was going to happen. its pretty wide spread knowledge if you'd care to have investigate a bit before jumping ship. been like this for years and years so nothing new or "hidden".
reading goes a long way. even now if you'd have taken a minute to investigate you'd see the futility of what you want to accomplish. ( going to stock and expecting it to be as it once was before knox was tripped)
moreover there are guides on how to hide google pay and installing a version that does not detect root or a modified system.
search is your friend.
edit
there is one thing that i just though of that you might have forgotten to do and just might work though.
during the rooting/twrp process you had to go to dev options and toggle the OEM unlock.
go there and lock back OEM. this will wipe device so beware.
also when you fully flashed back the 4 md5 files with odin, was data wiped?