Database Develop

Tutorial: How To Protect and Restore Root (4.2.2 Pre-Camera Update Only)

This tutorial will explain how to protect and restore root for the OTA update.
Disclaimer: If you wish to keep root, DO NOT accept the OTA Update before running through these steps. PwnMyMoto will not work after updating since bug 9695860 (2nd Master Key) was patched. I am not responsible if this bricks your phone. Use at your own risk.
First I would like to thank JCase. If it wasn't for his original root method this would not be possible.
Prerequisites:
Moto X
A data cable (one that came with the phone woks fine)
Root - Grab JCase's program PwnMyMoto from this thread: http://forum.xda-developers.com/showthread.php?t=2444957
ADB & Fastboot (attached to post if anyone needs it)
RSDlite - Can find it here: http://www.4shared.com/rar/HkfWKoC5/RSD_Lite_615__MTK_Patch.html
SuperSU (in playstore, can't guarantee other Superuser programs can restore root)
SUPERCURIO's OTA RootKeeper or equivalent root keeper program (in playstore)
FXZ file for your carrier - Can be found here: http://sbf.droid-developers.org/ghost_rcica/list.php
Steps to Restore Root:
1. Make sure that there are no modifications to the system files. If there are the update will fail to flash. There are two way to go about this. You can flash back to stock using the FXZ for your carrier and rsdlite or fastboot (whichever you prefer) or remove the modifications if you know what they are. If you just removed all mods then skip to step 3.
Note: If you use rsdlite to flash back to stock remember to remove the getvar command from the xml file. If you use fastboot to flash back to stock use the following post as a reference how:
http://forum.xda-developers.com/showpost.php?p=45809324&postcount=3
2. Now you will need to install PwnMyMoto and then run it. After 2-3 reboots you should be rooted.
3. Make sure you install SuperSU and OTA RootKeeper.
4. Shutdown your Moto X. Then hold the power and down volume keys for about 5 seconds to boot into the bootloader. Scroll down with the down volume key to recovery and press the up volume key. You will be booted into android with write protection disabled.
5. Open up SuperSU. If it asks you to update the binary update it. You are going to want to make sure Survival mode is checked.
6. Open OTA RootKeeper. Grant it superuser rights and click Protect Root. It will save a backup of su. After that click Temp. un-root (keeps backup). This will hide root on your device.
7. Next we are going to flash the stock recovery. You will need fastboot, a command prompt and the stock recovery.img. For the recovery,img you can either grab the backup (recovery-stock.img) that is saved to the root of your device or you can grab the one from your carrier's FXZ. If you use the recovery from the FXZ you should also grab boot.img since we are going to be using it later. So unzip the fastboot files into a folder that you can easily locate. I placed it in C:\ for easy reference. Make sure your recovery and boot.img are in the same folder.
8. Now shutdown your Moto X and boot into the bootloader as we did in step 4. Open your command prompt by going to your start menu clicking run and typing cmd.exe (for windows 8 just use the search in the start screen and search for cmd under apps). This will bring up the command prompt. Now we need to change the directory to the folder you placed the fastboot and recovery files in. To do this type in
Code:
cd C:\ (example: cd C:\fastboot)
9. Make sure you connect your phone to you computer via your data cable and that all the moto drivers are installed. Windows will usually automatically detect them. Once your connected and set to got we are going to type the following command into the command prompt:
Code:
fastboot flash recovery recovery.img (replace recovery.img with recovery-stock.img if you pulled the backup from you device).
Don't exit the command prompt. We will be using it again shortly.
10. So now you are ready to take the OTA Update. Boot your phone up by either choosing Normal Powerup or using the following fastboot command:
Code:
fastboot reboot
Once rebooted flash the OTA Update.
11. Your phone will reboot into recovery for the flash. Once it is complete it will boot up like normal and optimize any changes made to the system. Once this is done SuperSU will try to automatically restore root, but will fail due to booting with write protection enabled. This is where boot.img comes into play
12. Shutdown your Moto X and boot into the bootloader again. Make sure to connect your phone to your computer via you data cable if you disconnected it after flashing recovery. Bring up your command prompt and type the following command:
Code:
fastboot flash recovery boot.img
This will allow you to reboot into android with write protection disabled by hijacking the recovery like JCase did with his original exploit.
13. Now boot into recovery from the bootloader. Once you are booted back up SuperSU will now be able to restore root automatically.
The next set of steps will show you how to pull the new boot.img from your phone so you can flash it to the recovery partition so there are no issues caused by using the old boot.img. These steps are completely optional. If you are uncomfortable doing this I recommend waiting for the fxz file for the update to be released to get the new boot.img.
Note: ADB is required to do this. It is now included with the fastboot files attached to this post.
14. After root access is restored you are going to go back to your command prompt. Type the following commands:
Code:
adb shell
su
dd if=dev/block/mmcblk0p33 of=/mnt/sdcard/boot.img
exit
exit
adb pull mnt/sdcard/boot.img
This will save a copy of the boot.img to the root of your phone and then save it to the directory that your fastboot and adb is in.
15. Now we are going to boot back into the booloader. Refer to step 4 for a reference how. Once booted into the bootloader type the following commands into the command prompt:
Code:
fastboot flash recovery boot.img
Now whenever you boot into recovery your phone will load with the new kernel and you should not have any more issues.
These next set of steps will allow you to fix the issue of the baseband failing to update during the OTA update.
16. If your baseband didn't update with the OTA then you will need to grab the FXZ of the update. Unzip the file NON-HLOS.bin and place it in the folder that contains fastboot.
17. Bring up your command prompt and and type the following commands
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
Now your baseband will be up to date.

hopefully someone makes a video
Sent from my XT1058 using XDA Premium 4 mobile app

Thanks so much for this! Quick question. If I am completely stock (never rooted this device before) I can start on step 2 correct?
Sent from my White Moto X

capathy21 said:
Thanks so much for this! Quick question. If I am completely stock (never rooted this device before) I can start on step 2 correct?
Sent from my White Moto X
Click to expand...
Click to collapse
Yup. Step 1 is only for those that have already rooted and have modded the system files.

I'm receiving my Verizon moto x tomorrow so if I read this right I don't except the update, root the moto x continue with these steps, and we will continue to receive updates and maintain root?

Dark9781 said:
Yup. Step 1 is only for those that have already rooted and have modded the system files.
Click to expand...
Click to collapse
Thanks! One last question I promise. Can I go ahead and go through the process up to step 10 that way I'll be ready when the ota comes, or should I wait till the ota comes then begin the process?
I've always rooted and flashed updates on past devices so I'm not real familiar with ota's and don't want to take it before I'm able to run this process.
Thanks in advance!
Sent from my White Moto X

capathy21 said:
Thanks! One last question I promise. Can I go ahead and go through the process up to step 10 that way I'll be ready when the ota comes, or should I wait till the ota comes then begin the process?
I've always rooted and flashed updates on past devices so I'm not real familiar with ota's and don't want to take it before I'm able to run this process.
Thanks in advance!
Sent from my White Moto X
Click to expand...
Click to collapse
Yup. You could do that.

Thanks! I really appreciate your work!
Sent from my White Moto X

mmad81 said:
I'm receiving my Verizon moto x tomorrow so if I read this right I don't except the update, root the moto x continue with these steps, and we will continue to receive updates and maintain root?
Click to expand...
Click to collapse
It should work on Verizon when they release an update. I can't say this will work for future updates or even for 4.3 when it comes around, but for this round of updates it will work to keep root.

Dark9781 said:
It should work on Verizon when they release an update. I can't say this will work for future updates or even for 4.3 when it comes around, but for this round of updates it will work to keep root.
Click to expand...
Click to collapse
what has been the success rate of this? I'm surprised more haven't jumped on this! Why are so many trying to unroot to get the camera update?

mj0528 said:
what has been the success rate of this? I'm surprised more haven't jumped on this! Why are so many trying to unroot to get the camera update?
Click to expand...
Click to collapse
I thought this method would work when I saw the T-Mobile update come out, but couldn't test it myself until 2 days ago. That's why I released a tutorial last night. For those unroofing to get the update, they were told prior to the release of the tutorial that they will lose root and have to return to stock to run the update. As for success rate I'm not sure how many have successfully done this and kept root. I'll add a poll to get an idea.
Sent from My Moto X

Dark9781 said:
I thought this method would work when I saw the T-Mobile update come out, but couldn't test it myself until 2 days ago. That's why I released a tutorial last night. For those unroofing to get the update, they were told prior to the release of the tutorial that they will lose root and have to return to stock to run the update. As for success rate I'm not sure how many have successfully done this and kept root. I'll add a poll to get an idea.
Sent from My Moto X
Click to expand...
Click to collapse
I'm ready to go. Un froze all my apps and just waiting for ATT to push my update. Anything special I have to do to get the OTA or is it just a slow roll out? Also, do I need the default recovery to see the OTA, or will I see the OTA before I change anything to prepare for it?

rmead01 said:
I'm ready to go. Un froze all my apps and just waiting for ATT to push my update. Anything special I have to do to get the OTA or is it just a slow roll out?
Click to expand...
Click to collapse
Right now the AT&T version is still in a soak test. A soak test can usually go for 3-7 day. After that there will be an official release. Just need to hang tight until the release. As of right now the saok has been going for about 2 1/2 days.

Dark9781 said:
Right now the AT&T version is still in a soak test. A soak test can usually go for 3-7 day. After that there will be an official release. Just need to hang tight until the release. As of right now the saok has been going for about 2 1/2 days.
Click to expand...
Click to collapse
Gotcha. Thought a bunch of people were saying they had the ATT OTA rolling out. Maybe I just misread and it was tmobile or something. I've never actually done an OTA update on any of my android phones. Always running a custom software, so I'm not 100% sure what needs to be setup correctly on the phone to receive it.
As of now, all system files are stock except for the hosts file which is modified from adfree. All apps on the phone are unfrozen and in their default from the store state. I still have the writable system recovery installed because I wasn't going to install the default recovery until I was absolutely ready to flash the OTA. I may still need root until then.

Dark9781 said:
Right now the AT&T version is still in a soak test. A soak test can usually go for 3-7 day. After that there will be an official release. Just need to hang tight until the release. As of right now the saok has been going for about 2 1/2 days.
Click to expand...
Click to collapse
do you have to wait on the official release for this too work? I know some people are putting the soak test build which is most likely the official release on their phone and upgrading from the stock recovery. Basically manually taking the OTA in case I explained that weird. Can you still use your method of keeping root by manually taking the OTA? I am on verizon so I will most likely be manually upgrading when the soak test comes out assuming I can still keep root.

jayboyyyy said:
do you have to wait on the official release for this too work? I know some people are putting the soak test build which is most likely the official release on their phone and upgrading from the stock recovery. Basically manually taking the OTA in case I explained that weird. Can you still use your method of keeping root by manually taking the OTA? I am on verizon so I will most likely be manually upgrading when the soak test comes out assuming I can still keep root.
Click to expand...
Click to collapse
The soak test versions usually end up as the official version. It is rare for a soak test version to not make it to official unless there are detrimental problems discovered during the soak. You can flash the OTA manually and use this method to keep root.

Dark9781 said:
It should work on Verizon when they release an update. I can't say this will work for future updates or even for 4.3 when it comes around, but for this round of updates it will work to keep root.
Click to expand...
Click to collapse
Just to confirm. Will this work on Droid Maxx? I haven't purchased yet, but root and tethering ability are very important to me. Also, does anybody know where Verizon is on the OTA schedule for the Maxx?

docslate said:
Just to confirm. Will this work on Droid Maxx? I haven't purchased yet, but root and tethering ability are very important to me. Also, does anybody know where Verizon is on the OTA schedule for the Maxx?
Click to expand...
Click to collapse
I would think it should work for the Maxx too, but I can't be sure until someone with a Maxx tests it. My sister just got the Ultra while she was on vacation. She'll be home this weekend. I'll see if she would let me play with her phone.

ready for the OTA and I'll give it a go
so what would the rsdlite to default look like if we took the OTA but then wanted to go back to complete stock one day. Would the rsdlite work since the OTA is installed?

mj0528 said:
ready for the OTA and I'll give it a go
so what would the rsdlite to default look like if we took the OTA but then wanted to go back to complete stock one day. Would the rsdlite work since the OTA is installed?
Click to expand...
Click to collapse
as long as the file packages are available you will always be able to go back to stock.

su for remix not working and its diag mode (read cdma/qpst)

I know there is not much support for the remix, though it's essentially a mini 2...too. I have it s-off and unlocked. I have twrp recovery on it. The all in one utility on one of these threads didn't work well for twrp so I flashed it via fast boot. I've tried running the utility for gaining root but nothing shows up in twrp under sdcard. I have pushed it to another folder, I find it and flash the zip file but even though it says it finished fine, when I reboot nothing is there. Weak sauce2 works fine, but that's just temp. I want permanent root.
That said anyone know how to enable serial/modem communication to cdma/qpst on the remix? I've been trying forever. Im trying to backup the prl.

jobzombi said:
I know there is not much support for the remix, though it's essentially a mini 2...too. I have it s-off and unlocked. I have twrp recovery on it. The all in one utility on one of these threads didn't work well for twrp so I flashed it via fast boot. I've tried running the utility for gaining root but nothing shows up in twrp under sdcard. I have pushed it to another folder, I find it and flash the zip file but even though it says it finished fine, when I reboot nothing is there. Weak sauce2 works fine, but that's just temp. I want permanent root.
That said anyone know how to enable serial/modem communication to cdma/qpst on the remix? I've been trying forever. Im trying to backup the prl.
Click to expand...
Click to collapse
I had the same issue today and was able to chat with the creators of Sunshine. They are super helpful and offer great support for their product. It took me a few tries but I have root. After you flash the latest version of Chainfire's supersu HERE , you have download the app from the playstore.
Not sure if this was related but right before I did the steps above, I switch over the the Nova launcher. One of the creators told me the stock blinkfeed launcher may give issues.

on1wheel said:
I had the same issue today and was able to chat with the creators of Sunshine. They are super helpful and offer great support for their product. It took me a few tries but I have root. After you flash the latest version of Chainfire's supersu HERE , you have download the app from the playstore.
Not sure if this was related but right before I did the steps above, I switch over the the Nova launcher. One of the creators told me the stock blinkfeed launcher may give issues.
Click to expand...
Click to collapse
How exactly did you accomplish it? Did you push su from recovery mode? I've been trying from just regular, ready to make calls, mode. Did you run a script or do it all manually? xbin or bin? I know some people like symbolic links to xbin/su within bin.

jobzombi said:
How exactly did you accomplish it? Did you push su from recovery mode? I've been trying from just regular, ready to make calls, mode. Did you run a script or do it all manually? xbin or bin? I know some people like symbolic links to xbin/su within bin.
Click to expand...
Click to collapse
I flashed the zip I linked above in TWRP recovery. You can connect your phone to a computer or download the supersu from your phone. After it is flashed, go to the play store and download the supersu app. I thought flashing would install the app on my phone but it didn't. After installing the app, pen it and it will prompt to install the binaries. After that I had root.
I'm not sure what you meant by xbin, bin, or symbolic links. I don't deal with any of that.

on1wheel said:
I flashed the zip I linked above in TWRP recovery. You can connect your phone to a computer or download the supersu from your phone. After it is flashed, go to the play store and download the supersu app. I thought flashing would install the app on my phone but it didn't. After installing the app, pen it and it will prompt to install the binaries. After that I had root.
I'm not sure what you meant by xbin, bin, or symbolic links. I don't deal with any of that.
Click to expand...
Click to collapse
OK, thanks. The Zip usually takes care of all that. I was having no success with a the zip file provided in the Windroid toolkit, so I was trying to push the same su that the toolkit downloaded to the phone and was trying it manually. I tried it with the one Weaksauce puts in the xbin folder as well temporarily. Both didn't work. I'll give this a go.
Thank you again!

Your welcome. I didn't use any of the methods you mentioned. I waited for the Sunshine 3 release to work and then tried the newest supersu zip. That did it. Now I'm waiting for a dev to port a rom to the HTC One Remix.

on1wheel said:
Your welcome. I didn't use any of the methods you mentioned. I waited for the Sunshine 3 release to work and then tried the newest supersu zip. That did it. Now I'm waiting for a dev to port a rom to the HTC One Remix.
Click to expand...
Click to collapse
I'm currently working on figuring out how to port it. Doesn't look like it should be too hard, but we'll see.

Txjacob said:
I'm currently working on figuring out how to port it. Doesn't look like it should be too hard, but we'll see.
Click to expand...
Click to collapse
I'll check back regularly. Which rom are you planning on porting. CM?

Successfully unlocked and s-off with sunshine. Then used su installer by the same guys for root yay! Now just waiting for devs to make or either port some Roms for the remix.

diag?
Was anyone able to get diag working on this phone yet?
I'm assuming after root you could use this program to get into usb settings and enable it:
https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite
But could someone confirm?

How to Root my N6 w/o PC?

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!

shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.

Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!

shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk

shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.

hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:

simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?

I can recommend the NTRT, the Nexus Telepathic Rooting Tools.

OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.

we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.

Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk

shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>

simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.

Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.

Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!

1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.

I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period

Moto X 2nd Gen XT1097 Root?

Hello all. First time posting on the forum. I've looked up on how to root the Moto x 2nd gen, but most I find is for the xt1095. I've read some information on how to unlock the bootloader for the xt1097 (I'm on AT&T). But it all just seems so confusing. I can't seem to find a source that has all the information I need all in one. I've found info from different sources but I don't wanna mess anything up by miss connecting the dots. If anyone has had success or knowledge on how to root this type of phone, I'd be very grateful! Thank you!

USA1791 said:
Hello all. First time posting on the forum. I've looked up on how to root the Moto x 2nd gen, but most I find is for the xt1095. I've read some information on how to unlock the bootloader for the xt1097 (I'm on AT&T). But it all just seems so confusing. I can't seem to find a source that has all the information I need all in one. I've found info from different sources but I don't wanna mess anything up by miss connecting the dots. If anyone has had success or knowledge on how to root this type of phone, I'd be very grateful! Thank you!
Click to expand...
Click to collapse
Hey, welcome to our forum.
You can use Kingroot (a one click root app) to root your at&t xt1097.
Then, if you want to unlock the bootloader, you can do it ONLY with sunshine app (an app that unlocks the bootloader, simple either), but in order to use sunshine app you need to pay for license or something like that, about 20-25$.
Sunshine works only if you have root, so you have to use kingroot.
Kingroot will not always work, but it should. Use it until it works, many reported it took them more than once.
That happens because you don't have offical bootloader unlock.
Have fun

OrenGazala said:
Hey, welcome to our forum.
You can use Kingroot (a one click root app) to root your at&t xt1097.
Then, if you want to unlock the bootloader, you can do it ONLY with sunshine app (an app that unlocks the bootloader, simple either), but in order to use sunshine app you need to pay for license or something like that, about 20-25$.
Sunshine works only if you have root, so you have to use kingroot.
Kingroot will not always work, but it should. Use it until it works, many reported it took them more than once.
That happens because you don't have offical bootloader unlock.
Have fun
Click to expand...
Click to collapse
Hey thank you for the information!! On the kingroot it said my phone was rooted, but then once I tried to do sunshine app, it said my phone was not rooted so I couldn't do that. Any idea why that is? Also, is kingroot and sunshine app the only thing I have to do? Or is after the bootloader unlocked there's other steps I must take to root the phone?

Was finally able to get kingroot to work and sunshine to unlock the bootloader after I did a factory reset. Now I'm confused as whats next. I read something about twrp and flashing logo?

I'm not trying to unlock the bootloader, only root the phone. KingRoot says "root successful," I download supersu, and it says my root binary (or something) isn't installed. However, SuperSu isn't able to install the binary for me.
An even worse problem: after KingRoot says "root successful" I check RootChecker, and it tells me I am NOT rooted. Also, every time I reboot, KingRoot claims I am not rooted. This makes me think that KingRoot incorrectly thinks it's rooted my phone. Because no other app seems to think I'm rooted, and when I reboot not even KingRoot thinks I'm rooted.
Finally, many of the KingRoot tutorials (as well as the app itself) say that KingRoot will likely reboot your phone a few times before it roots, and that after it roots it your phone will reboot. However, KingRoot has never rebooted my phone ONCE. This also adds evidence to my hypothesis that KingRoot incorrectly thinks it's rooting me. When I run KingRoot, it tells me not to be afraid if my phone reboots; well I am afraid because my phone is NOT rebooting.

Vegerot said:
I'm not trying to unlock the bootloader, only root the phone. KingRoot says "root successful," I download supersu, and it says my root binary (or something) isn't installed. However, SuperSu isn't able to install the binary for me.
An even worse problem: after KingRoot says "root successful" I check RootChecker, and it tells me I am NOT rooted. Also, every time I reboot, KingRoot claims I am not rooted. This makes me think that KingRoot incorrectly thinks it's rooted my phone. Because no other app seems to think I'm rooted, and when I reboot not even KingRoot thinks I'm rooted.
Finally, many of the KingRoot tutorials (as well as the app itself) say that KingRoot will likely reboot your phone a few times before it roots, and that after it roots it your phone will reboot. However, KingRoot has never rebooted my phone ONCE. This also adds evidence to my hypothesis that KingRoot incorrectly thinks it's rooting me. When I run KingRoot, it tells me not to be afraid if my phone reboots; well I am afraid because my phone is NOT rebooting.
Click to expand...
Click to collapse
Vegerot,
KingRoot accomplishes what's called a temp root (temporary root). After you reboot your phone, the temp root files will be deleted and you will not have root anymore. Also, installing a SuperSu binary will not work with a temp root. If you want to perm root your phone (permanent root), you will need to use KingRoot to root your phone (may take a couple of tries) and then you will need to use Sunshine to unlock your bootloader. After it is unlocked, you can flash a custom recovery and install the SuperSu binary.
Secondly, I've had that problem before. I would recommend using the PC version first, (which is in Chinese, but is easy to figure out) which will attempt the root, and if that doesn't work, use the phone version right after using the computer one. As I mentioned before, KingRoot is a temporary root that goes away after a reboot.
Lastly, usually reboots are not a measure of success. When I rooted, I did not reboot that often, so you should not be worried. If you think that something is not working, again, use the PC version; it seems to have a better success rate.
Contact me if you need any help.

R55770 said:
Vegerot,
KingRoot accomplishes what's called a temp root (temporary root). After you reboot your phone, the temp root files will be deleted and you will not have root anymore. Also, installing a SuperSu binary will not work with a temp root. If you want to perm root your phone (permanent root), you will need to use KingRoot to root your phone (may take a couple of tries) and then you will need to use Sunshine to unlock your bootloader. After it is unlocked, you can flash a custom recovery and install the SuperSu binary.
Secondly, I've had that problem before. I would recommend using the PC version first, (which is in Chinese, but is easy to figure out) which will attempt the root, and if that doesn't work, use the phone version right after using the computer one. As I mentioned before, KingRoot is a temporary root that goes away after a reboot.
Lastly, usually reboots are not a measure of success. When I rooted, I did not reboot that often, so you should not be worried. If you think that something is not working, again, use the PC version; it seems to have a better success rate.
Contact me if you need any help.
Click to expand...
Click to collapse
Thank you! Is it possible to use the TempRoot to remove bloatware?

Vegerot said:
Thank you! Is it possible to use the TempRoot to remove bloatware?
Click to expand...
Click to collapse
Yep. In the KingRoot app, after you have successfully rooted, you can uninstall the bloat apps.
---------- Post added at 07:47 PM ---------- Previous post was at 07:44 PM ----------
USA1791 said:
Was finally able to get kingroot to work and sunshine to unlock the bootloader after I did a factory reset. Now I'm confused as whats next. I read something about twrp and flashing logo?
Click to expand...
Click to collapse
After I unlocked my bootloader, I first flashed TWRP through the bootloader. I then did a full backup and installed a ROM. Flashing a LOGO is optional as it only changes the logos before the actual boot animation.
Contact me if you need any help with flashing or anything else.

After unlocking the bootloader, I'm having trouble installing Marshmallow. I tried following this tutorial but it hasn't helped either. This is my problem with that tutorial:
"When I run "fastboot flash system..." I'm stuck on "waiting for devices." Also, "fastboot devices" returns nothing. However, adb devices returns my phone.
Also, instead of system.img, the download link you provided gave me boot.img (along with a META-INF and system folder).
When entering TWRP, why must we go through that bootloader interface? I just do "adb reboot recovery" and that also opens TWRP.
Since fastboot isn't working, is there a way to do it through the TWRP GUI? Such as copying the file to my phone and then doing something with that?
Something strange happened. I decided to download the Marshmallow .zip on my phone, then booted into recovery and went to Install, and selected that file. I thought I would get an error (I'm trying to flash my phone from a file stored on my phone (therefor deleting itself)), but I didn't. I rebooted and all my apps were still there from before and my background, but the settings app says I'm running Android 6.0. What exactly happened?
There are some unexpected things happening though. For examples, I cannot swipe down with 2 fingers to access my quick settings In addition, the home button will not take me back to my app launcher (I have to tap the multitasking button THEN tap the home button to return to the launcher). When I look at my notifications, it still says "AT&T" at the bottom. Is that supposed to happen? This doesn't feel right and I would like to use the method you recommended in the article, but for now this is the only thing that will work.
"

????
Kingroot not works on my moto x 2nd gen xt1097 at&t ... How it works??

Como ser root
Ver contraseñas

Phone Stuck In Recovery

Hi guys. I somehow messed things up really bad.
I was running a modded ROM, but decided I wanted to go back to unrooted stock. I followed this instructions in this video: https://www.youtube.com/watch?v=6avEPGWB8E0
Unfortunately, things didn't work out. When I tried flashing the files it kept saying "system not found". Now I'm stuck in recovery forever. If I try to press start, nothing happens. If I scroll up to factory, nothing happens either. If I look at the Bootloader logs, all it says is "failed to validate system image. Boot up failed".
The one good thing is that the phone recognizes being plugged into my computer (Windows 10), so maybe there's a small chance I can get my phone back. If you guys have a solution, please let me know, as I'm pretty distraught right now. Also hoping there's a chance I can get my photos back that are on the device, though that seems unlikely now.

Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.

ChazzMatt said:
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
Click to expand...
Click to collapse
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.

Xpwnage123 said:
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Click to expand...
Click to collapse
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Also with custom ROMs you can still run the ROM and UNroot your phone. (I know you can with CM.) No need to go back to stock, unless parent company of Pokemon is clueless and demands stock.
Well, seems they are clueless and doing what Android Pay does:
http://www.xda-developers.com/lates...blocks-rooted-devices-from-entering-the-game/
What Niantic has managed to do with the update is kill off the enthusiasm in users who had root but were not cheating. Root is used for many more things outside of cheating in a game, and to assume that all rooted users are cheaters is just silly.
_____
After some more reading around, it seems Niantic is actually using the SafetyNet checks to check for root. XDA Senior Member MaaarZ found the SafetyNetService being called in the game code. Niantic is really making users jump through the whole nine yards, as this is the same method employed by Android Pay. This means that if you do need to run Pokémon GO on a rooted device, you need to go through the whole Magisk and systemless root way. Or stop playing completely, because that is what Niantic wants you to do.
Click to expand...
Click to collapse

ChazzMatt said:
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Click to expand...
Click to collapse
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.

Xpwnage123 said:
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.

Xpwnage123 said:
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.

ChazzMatt said:
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Click to expand...
Click to collapse
TheSt33v said:
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
Click to expand...
Click to collapse
Thank you guys. I was able to revive my phone from the dead using your advice. Unfortunately, I lost all of the photos from my trip to Europe, but overall I'm happy my phone is back and running. That will be a lesson to me to be less lazy about backing up my data.
Once again, thank you very much.

Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...