Database Develop

Encryption (impact on unlock/rooted?)

Dev edition. Unlocked and rooted with TWRP.
Put the 4.4.2 exchange apk's in /system then found out my company requires full device encryption on phones without an SD card.
I want to stay stock. Only reason I rooted was to get the new exchange apks.
If I encrypt everything will I still be able to:
-Use adb to go back to stock recovery
-use root explorer to restore the stock system apps
-take an OTA while maintaining unlock and root?
Sorry for the dumb questions. Every phone I've used had an SD card and I never had to deal with this.
Sent from my XT1060 using Tapatalk

Prior to posting this I read about 50 google results and learned that Google sucks.

So I'm slowly figuring out these answers as I go since no one else knows.
First I unlocked and rooted my device using this guide:
http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
Immediately after installing TWRP reboot into recovery and then tell TWRP to reboot. It will ask if you want to root, say yes. Install Super su from play store.
Next I used root explorer to get the 4.4.2 exchange and exchange services into /system/app then disabled the old ones in the normal settings/apps menu.
Then I set up my phone and configured my work exchange account and let it encrypt my device.
Here is what I have discovered:
- TWRP still can be booted into, but it can't see the /data partition. So you cant make a full nandroid or flash any files you saved to your phone.
- You can still use adb to flash TWRP or the stock recovery
Unknown:
-If I wasn't already rooted would TWRP have been able to root the device after unlocking and flashing TWRP earlier? It can't see the data partition, does it need to?
I don't have time right now to "start fresh" and see, but when I do I will update this thread.

I wish I could be of assistance, but I would love for you to keep us posted. I thought about encrypting my phones many times but I didn't know if/what that would prevent me from doing.
MotoX Developer Edition, Bootloader Unlocked, Rooted, Stock with tweaks!

You don't need to install a custom recovery to root. I have a Verizon Moto X which I used the "SlapMyMoto" method. After rooting I was able to encrypt the phone just fine without any issues to my root. I don't have an unlocked bootloader (don't see a point personally, since I don't plan to install another ROM).
If you intent to install another ROM then you'll want to not have the phone encrypted unless TWRP can access encrypted files on your device.
If you don't want to install a custom ROM then I recommend using the SlapMyMoto method, which works very well though it is a bit cumbersome to get done, once it is done you shouldn't need to redo it unless you accept an OTA.
The basic process is to root it using methods for 4.2 (you have to restore to 4.2 prior to rooting), then disable write protection using the appropriate tool, I think it is calle MotoWPNoNo or something along those lines. After that, accept the OTA to 4.4 and run SlapMyMoto to get root back.

Thanks titan. I think my biggest question right now is "can you root a phone that is already encrypted?"
I know I can unlock (dev edition) and install TWRP (abd) but can I root if TWRP can't see the /data partition meaning I can't flash the supersu zip.
If you root *then * encrypt it works fine. But since un-encrypting requires a wipe it would be nice to avoid having to go though that.
Sent from my XT1060 using Tapatalk

Restola said:
Thanks titan. I think my biggest question right now is "can you root a phone that is already encrypted?"
I know I can unlock (dev edition) and install TWRP (abd) but can I root if TWRP can't see the /data partition meaning I can't flash the supersu zip.
If you root *then * encrypt it works fine. But since un-encrypting requires a wipe it would be nice to avoid having to go though that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Well, you don't actually need to see the /data partition to flash, if you have the ZIp somewhere else, or use ADB + TWRP (I think you can do that? I know you can with CWM). When you encrypt the OS isn't encrypted so /system isn't touched. The short answer is, yes, you can. TWRP should be able to read the encryption - in fact it should ask you for a password to decrypt when you boot into recovery.
I would still recommend using SlapMyMoto as it leave stock recovery in place, the reason this is good is because TWRP won't respond to an automatic wipe request from Android Device Manager or similar service. If you leave the stock recovery in place then you can still remote-wipe the device if you need to.
If you've already got TWRP in place it is simple... Does TWRP ask you to decrypt the phone before it goes in? If it does, can you see your internal SD Card and select a ZIP from it? If those are YES then, it'll work fine. TWRP can see the entire phone and thus you can install a zip without problem. If i can't, you'll need to get more creative, but I still would suggest seeing you can use ADB while you're booted into TWRP to push the SuperSU ZIP to the device to flash.
Here is a link from last year from Stack Exchange about TWRP and an encrypted device. I know that when I had my S3 running CyanogenMod TWRP would decrypt it just fine.
https://android.stackexchange.com/q...custom-recovery-work-with-an-encrypted-device
Should you need to do it, here is the link for using ADB with TWRP... (it is called Sideloading, forgot that)
http://teamw.in/ADBSideload

Thanks the side loading may be what I'm looking for If I ever go back to square one and want to root while encrypted. TWRP didn't ask to decrypt so no luck there.
Sent from my XT1060 using Tapatalk

Did you ever get this working? I just put TWRP on my MotoX DE, and I encrypted my phone (Exchange requirement). Anyway to have TWRP decrypt so i can sideload or root?

[How-To] Root and unlock the bootloader of the Nexus 4/5 without wiping data

This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
Note: I'm not responsible for any damage on your phone! You choose to do these modifications and you are responsible for any problems!
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
Devices you can root using this app:
- Nexus 4: 4.4.3, 4.4.4
- Nexus 5, 4.4.3
1. Install the towelroot app (xda thread) from the project site! Please thank geohot, he made this possible!
2. Open the app and click on "make it ra1n"
3. Wait 15 seconds and the phone will reboot!
Congratulations! Your phone is rooted now!
4. Install either SuperSu or Superuser
a) In the app update your binary the "normal way" (without a custom recovery)
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
This is it! You're rooted now and you can easily unlock/relock your bootloader using the BootUnlocker app without wiping any data
Note: This was not my work! I just wrote down some steps to root and unlock
How to unroot:
1. Reflash the stock recovery image/stock kernel/etc (only necessary if you are running a custom kernel/recovery/etc)
2. Open BootUnlocker and lock the bootloader. Now you are able to uninstall the app!
3. Open SuperSu -> Settings -> Full unroot. This will unroot your phone and the app will automatically be uninstalled.
4. Reboot and done

noob clarifications
Hey, came across your post in another post where you mentioned this method would prevent the posibility of the phone being wiped when unlocked + rooted via "traditional" methods using a PC w SDK etc. Phone at present is locked, unrooted stock Nexus 4 kitkat 4.4.4 stock.
Just wanted to clarify a few points since this is the first time I've come across a method where the phone is rooted and unlocked from within itself (I've rooted and unlocked a HTC desire back in my heydays).
--- Do I need to unlock the phone if I just want to change the kernel from stock to the Matr1x kernel? (I had taken unlocking as a given as it was the first step in every guide - there is no mention of steps on how to actually install the kernel but I was going to research that process once root and unlock was done successfully)
--- Any chance you can give steps on updating the binary the 'normal' way? (never done this before)
--- How do you install CWM using your method? Again, I have only seen it being installed via command lines from the PC
Apologies in advance for the dumb questions but searched and couldn't find any clear answers for those steps that I'm not understanding

salxtai said:
Hey, came across your post in another post where you mentioned this method would prevent the posibility of the phone being wiped when unlocked + rooted via "traditional" methods using a PC w SDK etc. Phone at present is locked, unrooted stock Nexus 4 kitkat 4.4.4 stock.
Just wanted to clarify a few points since this is the first time I've come across a method where the phone is rooted and unlocked from within itself (I've rooted and unlocked a HTC desire back in my heydays).
--- Do I need to unlock the phone if I just want to change the kernel from stock to the Matr1x kernel? (I had taken unlocking as a given as it was the first step in every guide - there is no mention of steps on how to actually install the kernel but I was going to research that process once root and unlock was done successfully)
--- Any chance you can give steps on updating the binary the 'normal' way? (never done this before)
--- How do you install CWM using your method? Again, I have only seen it being installed via command lines from the PC
Apologies in advance for the dumb questions but searched and couldn't find any clear answers for those steps that I'm not understanding
Click to expand...
Click to collapse
1. To flash a kernel you have to unlock your bootloader, that's right. You just flash it using your PC and fastboot, there are many guides on how to do that
2. If your phone is rooted and you have SuperSU installed there'll be a popup and it'll tell you to update the binary before using the app. You are able to select the "normal" way then without a recovery
3. You can install CWM/TWRP using your PC in fastboot mode!
No problem, just ask :good:

Can the usual commandline methods for other things be used after this?

PGvossman said:
Can the usual commandline methods for other things be used after this?
Click to expand...
Click to collapse
If you mean fastboot commands for example to flash another kernel/recovery/etc, yes! There's no difference between unlocking using this method or another "old" one, but this one doesn't wipe data

PGvossman said:
Can the usual commandline methods for other things be used after this?
Click to expand...
Click to collapse
yes. can also be used flashify to flash recovery.img without PC

I think I'll give it a try then (assuming there's no risk of bricking my phone or doing irreversible damage). On that subject, is there an easy way to lock the bootloader and unroot?

PGvossman said:
I think I'll give it a try then (assuming there's no risk of bricking my phone or doing irreversible damage). On that subject, is there an easy way to lock the bootloader and unroot?
Click to expand...
Click to collapse
Check the OP, there are already the steps given to unroot and relock

mihahn said:
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
Click to expand...
Click to collapse
I tested this on Android 4.4.4... it works fine!
Note: with TowelRoot v3 it isn't necessary reboot, but when I've tried to update SuperSu it fails so reboot and that's all
Thanks so much!

I apologize for asking so many questions but what exactly is "updating the binaries". Is that just for the app itself or does it do something to the phone?

PGvossman said:
I apologize for asking so many questions but what exactly is "updating the binaries". Is that just for the app itself or does it do something to the phone?
Click to expand...
Click to collapse
It updates the superuser binary that got installed by Towelroot I guess

will this method work on the nexus 5?

mihahn said:
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
Note: I'm not responsible for any damage on your phone! You choose to do these modifications and you are responsible for any problems!
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
1. Install the towelroot app (xda thread) from the project site! Please thank geohot, he made this possible!
2. Open the app and click on "make it ra1n"
3. Wait 15 seconds and the phone will reboot!
Congratulations! Your phone is rooted now!
4. Install either SuperSu or Superuser
F
a) In the app update your binary the "normal way" (without a custom recovery)
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
This is it! You're rooted now and you can easily unlock/relock your bootloader using the BootUnlocker app without wiping any data
Note: This was not my work! I just wrote down some steps to root and unlock
How to unroot:
1. Reflash the stock recovery image/stock kernel/etc (only necessary if you are running a custom kernel/recovery/etc)
2. Open BootUnlocker and lock the bootloader. Now you are able to uninstall the app!
3. Open SuperSu -> Settings -> Full unroot. This will unroot your phone and the app will automatically be uninstalled.
4. Reboot and done
Click to expand...
Click to collapse
Thanks, for the average user who doesn't use custom roms or anything really crazy, is super su or Superuser a better option? Or is it the same more or less? Thanks

anees167 said:
will this method work on the nexus 5?
Click to expand...
Click to collapse
Yes, it should work fine. Try it
dodgebizkit said:
Thanks, for the average user who doesn't use custom roms or anything really crazy, is super su or Superuser a better option? Or is it the same more or less? Thanks
Click to expand...
Click to collapse
These two are basically the same, as they are apps to manage the superuser permissions of other apps. You may use the one you like

That was easy
Of course I don't see this thread unitl after I spent the last hour setting everything up in Ubuntu to root the old fashioned way! Used this and was rooted in no time.

ota updates affected or not?
does using this towelroot will affect the ota updates i.e. if any ota update comes will i able to install as in the stock rom...?? please clarify this...

ashutoshchauhan211 said:
does using this towelroot will affect the ota updates i.e. if any ota update comes will i able to install as in the stock rom...?? please clarify this...
Click to expand...
Click to collapse
see towelroot only roots your device.
You can get OTA PROVIDED - You dont change any of the stock files.. Nothing should be changed.

mihahn said:
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
Click to expand...
Click to collapse
Hi, I have rooted Nexus 4 4.4.4 with towelroot app (and I have SuperSu app).
Now, If I install custom recovery, I will lost data? With custom recovery, I will get OTA update?
Thank you

blank nexus 4 without ROM
hi
i tried to install android L, forgot to backup the old ROM , unable to flash the new android L and i cant even restore the old ROM because i forgot to backup the ROM. Tried to do ADB SIDELOAD also....it says cannot read the (file)...tried so many times
i am unable to install a ROM in my nexus 4....only thing i can see in my phone is recovery mode....
Kindly please help.........anyone please reply to this post....and help me......

nexusfans said:
hi
i tried to install android L, forgot to backup the old ROM , unable to flash the new android L and i cant even restore the old ROM because i forgot to backup the ROM. Tried to do ADB SIDELOAD also....it says cannot read the (file)...tried so many times
i am unable to install a ROM in my nexus 4....only thing i can see in my phone is recovery mode....
Kindly please help.........anyone please reply to this post....and help me......
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

[Q] Rooting disables NFC?

I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.

goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
Rooted, and unlocked via NTK here. NFC works fine.

goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
what are you using to gain root? the latest supersu should not mess things up. the latest supersu is version 2.37 http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip

I've had no problems at all. I used the wugfresh toolkit over in the development section. Worked flawlessly and was pretty much the easiest root I've ever used. You just click buttons. Lol. Go back to full stock and use that.

I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.

goodfellaslxa said:
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
Click to expand...
Click to collapse
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.

simms22 said:
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
Click to expand...
Click to collapse
I used 2.36. I'll try 2.37 to see if it makes a difference.

goodfellaslxa said:
I used 2.36. I'll try 2.37 to see if it makes a difference.
Click to expand...
Click to collapse
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.

simms22 said:
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
Click to expand...
Click to collapse
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).

jj14 said:
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
Click to expand...
Click to collapse
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.

simms22 said:
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
Click to expand...
Click to collapse
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?

jj14 said:
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
Click to expand...
Click to collapse
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.

simms22 said:
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
Click to expand...
Click to collapse
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.

jj14 said:
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
Click to expand...
Click to collapse
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.

simms22 said:
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
Click to expand...
Click to collapse
Thanks
Yeah, I knew that (I already unlocked bootloader and rooted)

Well, after reflashing and not rooting I still lost NFC (though it took several hours and a few reboots before it stopped), so I decided to try not using google restore, and setup as a new device.
After manually reinstalling 300+ apps, reconfiguring everything, and rooting (using 2.37), NFC appears to be working fine. I *think* that some setting that was being restored from previous google backups eventually killed NFC.

I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.

lkevinl said:
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
Click to expand...
Click to collapse
I think its not a root issue. Did you restore a previous backup, or use the tap-to-import option? I think there is a setting that is being imported that causes this. Try resetting to stock, and when you go through the initial setup don't import a backup. That fixed it for me.

I used the original auto-root, and I still have NFC options available also. (and I never had to enable developer options. I unlocked the bootloader right out of the box).

Hmmm... was hoping to avoid doing the factory reset. I did try to the Tap to Go option but wasn't sure if it did anything. I'm mostly interested in getting my WiFi settings restored. I suspect your right about a restored setting mucking this up. I may have to do the reset anyway because of the other problem I'm having with Facebook that I posted about in an earlier thread.

Is there a root method that doesn't require unlocking the bootloader? (LRX22C)

I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks

arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
There is a way, I believe, by running TWRP on your PC and flashing SuperSU from your PC. However, it's not a recommended method as you will have no way of backing up. Also, if you get caught in a bootloop, you won't be able to recover without a custom recovery.

arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
and you don't have to "hack" a nexus as well, as google provided an easy way to unlock your bootloader and to obtain root. if you just got your nexus a few days ago, just unlock the bootloader and root it. loosing a few days of information is more than worth it for root. don't waste your time worrying over a few days of data.

Can be done but not recommended.

adb backup/restore can save a little bit of information for you, but I wouldn't go in expecting it to save everything
Sent from my Nexus 6

What did you set up? You can back up your messages, and your apps will re-download. Your photos are already syncing to Google. If it's not rooted, I can't imagine you've done that much customization.

Lesson learned: unlock should ALWAYS be the very first step you do on a new phone.

arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market

danr93 said:
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
Click to expand...
Click to collapse
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.

danarama said:
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
Click to expand...
Click to collapse
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up

danr93 said:
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
Click to expand...
Click to collapse
Good stuff. Once rooted, Flashify is a great tool to flash TWRP. With the nexus 5, you could unlock the bootloader with an app that didnt wipe everything, which was great, but Nexus 6 doesn't allow that, but always do go to settings > developer options > OEM Unlock (Set to enable). Without this set, you cannot unlock the bootloader from fastboot. Also, side note, developer options doesn't show up until you go into Settings > About phone then tap "Build number" several times to make the option visible. Think its 7 times.
It's interesting saying that you need kingroot to remain on the device. Thats a bit of a pain. Does it install SuperSU or not? If not, might be interesting to see what happens if you install the SuperSU app from Play - whether it allows it to be removed then.
My preferred method however is definitely unlock the BL, fastboot flash TWRP, From TWRP flash SuperSU zip (or rooted ROM).

For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?

arcooke said:
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
Click to expand...
Click to collapse
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery

danarama said:
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
Click to expand...
Click to collapse
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.

arcooke said:
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
Click to expand...
Click to collapse
That's lollipop for you. It changed everything.
It's still really simple.

Good to know. Thanks for the info!

[How-To] Update to G870A(Active Model)_OJ3 - 5.1.1 (Unrooted Stock ROM)

**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Note** Rooting all Samsung 5.1.x builds currently requires a modified kernel therefore, due to the locked bootloader, achieving root on this build/device is not currently possible.
Downloads:
- G870A_OJ3_Stock_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to *"Download."
6. Press the lightning bolt then "Ok" to begin the **flash .
7. Once the flash is complete and the device reboots into "Download" mode, flash the G870A_OC5_Bootloader using Odin's PDA/AP slot.
*If you are already on the OC5 bootloader, set "Reboot" setting to "Normal" and skip Step 7.
**The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
Once complete your device will reboot and pause on the AT&T splash screen for about 1 - 2 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Recommended: Package Disabler Pro to disable unwanted bloatware (root access not required).
Known Issues:
- None!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery. The bootloader will not be flashed in order to allow for downgrading to previous firmware versions.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2

Sweet! I have been anxiously waiting for this for my active. Thank you!
Sent from my SAMSUNG-SM-G900A using Tapatalk

I want to try it so bad, but I need my root!
Could everybody tell us what you think performance/battery wise though?
Thanks a lot!

Awesome gna do some flashn!

Thanks @muniz_ri.
Sent from my SAMSUNG-SM-G870A using Tapatalk

Followed the directions and it worked fine.
Used the suggested package disable pro with the defaults and then updated everything. Phone seems to be working fine so far.
I did read in one of the other threads that the battery life and such might not be as good as expected because we are still on the old bootloader, is this true or does the bootloader have nothing to do with the operating system?

Oh man....now do I...or don't I....

Install went well. Now to test.
Sent from my SAMSUNG-SM-G870A using Tapatalk

AnarchoXen said:
Oh man....now do I...or don't I....
Click to expand...
Click to collapse
Do it!
Sent from my SAMSUNG-SM-G870A using Tapatalk

If it requires root to flash... I would hope that I could then keep root after the flash.
I'm holding off on 5.1.1 until root is available. Just can't do without it I don't think.

Well i went ahead and did it, no problems at all. Now to see if I really can live without root!

Gonna try my hands at rooting this >_> i will update status.
Did some testing bricked my device 5 times. doesnt get past the bootloader part, so :/
For those of you that are testing this yourselves. You will ave to use the stock firmware for 4.x to unbrick. and then upgrade from 5.0 -> 5.1 in that order. So i guess im going to ave to wait for a root method too >_>
Within further testing, the files do update via flashfire, i just ave no clue how to get the system files to mount/unmount without bricking because it's unpacked.

Very good. Running smooth and fast. I do miss some root features.
SM-G870A Peace

Teranode said:
Gonna try my hands at rooting this >_> i will update status.
Did some testing bricked my device 5 times. doesnt get past the bootloader part, so :/
For those of you that are testing this yourselves. You will ave to use the stock firmware for 4.x to unbrick. and then upgrade from 5.0 -> 5.1 in that order. So i guess im going to ave to wait for a root method too >_>
Within further testing, the files do update via flashfire, i just ave no clue how to get the system files to mount/unmount without bricking because it's unpacked.
Click to expand...
Click to collapse
You can save yourself some time, or not, but all that has already been tried. No current way to root 5.1.1 on locked bootloader devices.

Meh I have a bunch of nexus and 2 one plus phones I just wanted to see of I can get this working on a s5 model. Att still committed to their locked bootloaders

berniesteven said:
Do it!
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
I am! Now...at the ATT logo screen currently.
Well that was quick.

So use to this tutorials that I didn't read (or see) the UNROOTED part.....darn it
Can this be undone ?
If so, how
Thanks!

orion2323 said:
So use to this tutorials that I didn't read (or see) the UNROOTED part.....darn it
Can this be undone ?
If so, how
Thanks!
Click to expand...
Click to collapse
Odin back to ne4. See the op.
SM-G870A Peace

berniesteven said:
Odin back to ne4. See the op.
SM-G870A Peace
Click to expand...
Click to collapse
Thank you...did it; up and running with the previous build
"4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process"
I was afraid to try it but needed my root
I'm hoping to get a 128GB card next week and wanted to erase my phone anyway...

orion2323 said:
Thank you...did it; up and running with the previous build
"4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process"
I was afraid to try it buy needed my root
I'm hoping to get a 128GB card next week and wanted to erase my phone anyway...
Click to expand...
Click to collapse
Glad it worked out well for you. If I helped, don't forget to hit thanks.
SM-G870A Peace