[Q] Root 4.4.2 Dev Moto X [VZW] - Moto X Q&A

Rooting Unlocked Bootloader
Step oneDownloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
TWRP Recovery
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
CWM Recovery
http://forum.xda-developers.com/showthread.php?t=2612149
SuperSU
http://download.chainfire.eu/supersu
MFastboot(Used for flashing TWRP)
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
How to install TWRP/CWM Recovery and SuperSU
Now that you have your bootloader unlocked its time to install are custom recovery and SuperSU so we have Root
Before we worry about that phone please make sure you have installed the SDK and then copied the mfastboot files over to the directory your ADB is in.
also before we put the phone into bootloader mode we need to copy the SuperSU.zip over to are phone
Now that we have all that moved over everything that we need. it is time to get are phone into the bootloader you can do that by turning off your phone, Then turning it back on while holding volume down + the power button.
once into the bootloader plug your USB cable in and set your phone down.
now we need to open a CMD window and CD to the directory ware we placed the MFastBoot files.
this is my location but i use the Moto X toolkit yours is going to be ware ever you install the SDK
so in the CMD window type the command below but change the path to ware your files are located
Code:
CD C:\Program Files\stillthisguy\Moto X Toolkit
now that we are in the right location it is time to install TWRP/CWM we are going to do that by typeing the commands below
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
or what ever the name of your recovery img is
as soon as you type the above command to flash TWRP/CWM we need to boot the phone into recovery before we let it boot to android we can do that via the buttons below.
click the Volume - button until it highlights Recovery then press the Volume + button to select it and it should boot into recovery.
If you do not immediately boot your phone into recovery after you flash it, recovery wont work.
here is a step by step that might help everyone abit
Now click on Install and find your SuperSU.zip that we copied over and click on it and install it. when it is done installing you can reboot your phone and enjoy having root access.
Click to expand...
Click to collapse
Reference: http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358
Can we confirm that this works on a Bootloader Unlocked Dev Moto X running 4.4.2 on Vzw?
thanks!

You got an answer in that thread. Why start a new one after someone already answered you? ???
Sent from my Nexus 5 using Tapatalk

kj2112 said:
You got an answer in that thread. Why start a new one after someone already answered you? ???
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Because reading is hard.

Why are so many people so confused about rooting their Dev Editions?

See post above yours. LOL.
Sent from my Nexus 5 using Tapatalk

kj2112 said:
You got an answer in that thread. Why start a new one after someone already answered you? ???
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
imnuts said:
Because reading is hard.
Click to expand...
Click to collapse
Actually I noticed the QA thread AFTER I posted the first time in the original thread. And for future people, reading such a long thread is not always effecient. Now it may be easier for a new person (such as myself) to find.
nhizzat said:
Why are so many people so confused about rooting their Dev Editions?
Click to expand...
Click to collapse
Because we are noobs.
----PS: The root method does work on DE Moto X 4.4.2 for VZW

nhizzat said:
Why are so many people so confused about rooting their Dev Editions?
Click to expand...
Click to collapse
Because we are use to the VZ bs and when something appears easy, we think it is to good to be true.

James4.0 said:
Because we are use to the VZ bs and when something appears easy, we think it is to good to be true.
Click to expand...
Click to collapse
So those in question spent extra $ on an unlockable device for what purpose?
-Nexus 10-

I got mine during the Cyber Monday sale for the same price as the normal non DE version. I bought from Motorola to keep my VZ unlimited data.

One quick Google search, "root Moto x dev edition".....boom. answers in seconds. Why oh why is that too hard? LOL. Far quicker than asking and waiting for someone to answer, and the inevitable flaming.
Sent from my Nexus 5 using Tapatalk

CartlandSmith said:
The flaming is not inevitable. It is a choice made by the flamer.
Click to expand...
Click to collapse
Rules reminders aren't flames.
Its helpful. Helps cut down clutter.
Number 1.
http://forum.xda-developers.com/announcement.php?a=81
Sent from my Nexus 5 using Tapatalk

CartlandSmith said:
flaming was your choice of words, not mine. I was just pointing out that flaming is a choice, too.
Click to expand...
Click to collapse
Agreed.
It implied I was flaming. I think a moderator would disagree. Lol
And hopefully if one stumbles across this thread, he'll close it swiftly.
Sent from my Nexus 5 using Tapatalk

Please read forum rules before posting
Search before posting and ask your question only once
Thanks
FNSM

Related

[q] nexus 7 toolkit auto update v4.3.4

Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Nexus 7 toolkit auto update v4.3.4
NinjaMogglet said:
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Click to expand...
Click to collapse
Can anybody help please?,
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Confirmation
Logan_M said:
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Click to expand...
Click to collapse
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
NinjaMogglet said:
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
Click to expand...
Click to collapse
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Unfortunately having the SDK does not mean I can actually use it
I got in over my head, hence trying to learn/read about it it on XDA
I found the thread that appeared to offer what I want,
a toolkit that I should be able to use to unlock/root with.
Thanks
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
you dont have to know how to use the entire SDK, all you need to do is be able to follow directions. every nexus is rooted the exact same way. the only thing the toolkit does is hide the commands. you could take the few minutes to learn these commands
fastboot oem unlock
fastboot flash recovery nameofrecoveryfile.img
reboot to recovery
adb push SuperSU.zip /sdcard/ (or /data/media, whatever)
flash supersu.zip with your custom recovery....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Pirateghost said:
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
NinjaMogglet said:
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
Click to expand...
Click to collapse
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
All Understould
Pirateghost said:
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
Click to expand...
Click to collapse
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
not sure why you need to go anywhere other than right here on XDA....
theres a freakin sticky for it even...
http://forum.xda-developers.com/showthread.php?t=2150661
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Still not clear??
smt8544 said:
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Click to expand...
Click to collapse
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
NinjaMogglet said:
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
Click to expand...
Click to collapse
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Thanks
Pirateghost said:
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Click to expand...
Click to collapse
Thanks...
I did not ignore your link, I read all the pages.
Especially the one's that pointed out the ommisions, like un-lock first, and some of the key presses.
I will get back to this when I'm bright eyed, not 01:25 in the morning.... Just in case.
Thanks again

[Q] How would you root? I'm on day FOUR of unsuccessful attempts

It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).
Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.
ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus
Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.

Bricked? Say it ain't so.

So trying any and everything to remove safestrap and install the latest ota i think i wiped all my data and my system cause now i just sit on the blue motorola m forever. I have an at&t moto x. the only thing i can do is fastboot with vol down and after that none of those options bring me anywhere. am i completely f'd or is there some way to fix this? thanks for the help guys.
Rsdlite back to stock
Sent from my Nexus 7 using Tapatalk
zeer.row said:
So trying any and everything to remove safestrap and install the latest ota i think i wiped all my data and my system cause now i just sit on the blue motorola m forever. I have an at&t moto x. the only thing i can do is fastboot with vol down and after that none of those options bring me anywhere. am i completely f'd or is there some way to fix this? thanks for the help guys.
Click to expand...
Click to collapse
Do you have any experience with fastboot? If not, google how to download it for whatever type of computer you have. I'm on a linux machine so its pretty straight forward, but I think its easy on any machine. If you're on windows you'll need the motorola drivers as well. You'll also need a factory stock image for at&t moto x.
After that it's just a matter of flashing the image to your phone and starting over.
I'm sorry, forgot about the locked bootloader. Listen to the guy before me.
If there are any pictures or stuff like that on your phone, i'm afraid those will probably be lost.
I will try to find helpful links for all this stuff, but I just wanted to give you something to look for while I did that.
Anthony04x said:
Rsdlite back to stock
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
lnstalling rsdlite now. will update. thanks a ton.
Okay, got it.
1. Go here and download that (hopefully you're on a windows machine):
http://forum.xda-developers.com/showthread.php?t=1348587
2. then go here and download the AT&T one. The third one down is KitKat, so just go with that, since it's what you're trying to do anyway.
http://sbf.droid-developers.org/ghost_rcica/list.php
3. Make sure you have these drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Now, go into RSDLite, click on load or open or whatever it says and go to the FXZ from step 2.
Click start.
Should be that easy, let me know if there are any hiccups.
thank you sooo much!
Hey no problem, we've all been there at some point. Did you get it working?
ps. Don't forget about that thank you button.
Sent from my XT1060
You can use the moto x toolkit here in this forum too. Install, open as administrator, install drivers from main menu, pick back to stock from main menu. Follow on screen instructions and it will do the rest from there
http://forum.xda-developers.com/showthread.php?t=2477132
This is in the completely wrong section. Needs to be moved to Q&A. Questions and help posts don't belong in a Development section.
Sent from my Nexus 5
Moto X was Bricked - Fixed - Thanks for the help
Thank you - it worked -
For some reason VZW wouldn't update my Moto X from 4.2.2 to Kit Kat. I bricked it trying. RSDLite fixed it with your instructions and now I'm on 4.4 Kit Kat.
Thanks!
JetOhmNet said:
Okay, got it.
1. Go here and download that (hopefully you're on a windows machine):
http://forum.xda-developers.com/showthread.php?t=1348587
2. then go here and download the AT&T one. The third one down is KitKat, so just go with that, since it's what you're trying to do anyway.
http://sbf.droid-developers.org/ghost_rcica/list.php
3. Make sure you have these drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Now, go into RSDLite, click on load or open or whatever it says and go to the FXZ from step 2.
Click start.
Should be that easy, let me know if there are any hiccups.
Click to expand...
Click to collapse
OP - you can use my script here:
http://forum.xda-developers.com/showthread.php?t=2603051
choose Advanced Menu and then #2 - Flash Binaries (no wipe)
it uses the mfastboot method and may be able to save your data.

[Q] Reliable method(s) of rooting.

I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
SlapMyMoto
nhizzat said:
SlapMyMoto
Click to expand...
Click to collapse
This.
Don't ask any questions, just follow the steps to the letter and you will be fine. I'm on a VZW model that I had to downgrade, and kept asking question after question.
You lose stock custom recovery forever, that's the risk on a non-dev-edition.
jl33 said:
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
Click to expand...
Click to collapse
I am in the same boat after recently getting a Moto X and coming from a Galaxy Nexus that seemed to have more consensus, or least clearly indicated. It was a bit daunting to trying to start to learn the process again after over 2 years.
User dray has got you covered though regardless of what Moto X you are using and what version of Android you are on. Go here http://forum.xda-developers.com/showthread.php?t=2603358 and thank dray for his efforts.
I recently finished rooting my xt1060 starting at 4.2.2 and could show you what I did if you are in the same boat.
You can't compare a nexus to a device with a boot loader that can't be unlocked. A little research before purchasing would have shown you that its not as easy to root.
If you had a Moto x with an unlockable boot loader...then it would be just as easy as a nexus to root. Same steps in fact. So its not device immaturity ....its the fault of the particular one you bought.
Just saying.
Sent from my Moto X cellular telephone...
kj2112 said:
You can't compare a nexus to a device with a boot loader that can't be unlocked. A little research before purchasing would have shown you that its not as easy to root.
If you had a Moto x with an unlockable boot loader...then it would be just as easy as a nexus to root. Same steps in fact. So its not device immaturity ....its the fault of the particular one you bought.
Just saying.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
slapmymoto
Just saying.
syntrix said:
slapmymoto
Just saying.
Click to expand...
Click to collapse
That's nothing like the unlocked boot loader method...which is the same as the nexus method. And I can see how it intimidates new people.
So maybe quit quoting me with smart ass comments all over this forum and read the opening posts a bit more carefully.
He knows about slap ....its just a chore was his point...compared to flash recovery in fastboot...say yes to fix root.....reboot and done. Lol
Do us both a favor and put me on your ignore list....before this escalates.
Sent from my Moto X cellular telephone...
jl33 said:
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
Click to expand...
Click to collapse
here is a complete guide that i made up hope it helps
http://forum.xda-developers.com/showthread.php?t=2603358
syntrix said:
This.
Don't ask any questions, just follow the steps to the letter and you will be fine. I'm on a VZW model that I had to downgrade, and kept asking question after question.
You lose stock custom recovery forever, that's the risk on a non-dev-edition.
Click to expand...
Click to collapse
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
dray_jr said:
here is a complete guide that i made up hope it helps
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
I appreciate that thank you.
jl33 said:
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
I appreciate that thank you.
Click to expand...
Click to collapse
np at all let me know if you have any issues
I did it with twrp-2.6.3.1-ghost-4.4.img, i flash it in fastboot, enter the recovery, go to reboot/system, select root, reboot and you are rooted, its simple, its work for me in 4.2.2, 4.4 and 4.4.2
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
if you can read spanish (or translate the page)
http://www.htcmania.com/showthread.php?p=12297991#post12297991
here's everything to change modem, recovery, root and even change the bootloader ulnock logo at the start
rivas1981 said:
I did it with twrp-2.6.3.1-ghost-4.4.img, i flash it in fastboot, enter the recovery, go to reboot/system, select root, reboot and you are rooted, its simple, its work for me in 4.2.2, 4.4 and 4.4.2
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
if you can read spanish (or translate the page)
http://www.htcmania.com/showthread.php?p=12297991#post12297991
here's everything to change modem, recovery, root and even change the bootloader ulnock logo at the start
Click to expand...
Click to collapse
Unfortunately, that method is for unlocked bootloaders
Try it anyways you dont loose anything trying
Enviado desde mi XT1058 mediante Tapatalk
rivas1981 said:
Try it anyways you dont loose anything trying
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
Guaranteed it won't work . Otherwise no one would ever unlock their boot loaders.
Sent from my Moto X cellular telephone...
syntrix said:
This.You lose stock custom recovery forever, that's the risk on a non-dev-edition.
Click to expand...
Click to collapse
Not forever. And what's a stock custom recovery? The only thing you lose "forever" is write protection if you use MotoPwnNoMo.
jl33 said:
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
Click to expand...
Click to collapse
I don't find it to be ridiculous at all. Rebooting into "recovery" adds maybe a minute to the whole process.
I'd like the same question as OP answered for the 1053 version. It really grinds my gears that there aren't separate forums for the different versions like they did with the variants of every other god damn phone (Galaxy Nexus as an example).
Sent from my XT1053 using XDA Premium 4 mobile app
elpeterson said:
I'd like the same question as OP answered for the 1053 version. It really grinds my gears that there aren't separate forums for the different versions like they did with the variants of every other god damn phone (Galaxy Nexus as an example).
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do they need separate forums? They all use the same root exploit with firmware specific to their model. There isn't enough development to justify separate forums.
Unlocking the bootloader is the same across the board as is rooting a locked bootloader. The only thing that differs in the entire process is the firmware.
nhizzat said:
Why do they need separate forums? They all use the same root exploit with firmware specific to their model. There isn't enough development to justify separate forums.
Unlocking the bootloader is the same across the board as is rooting a locked bootloader. The only thing that differs in the entire process is the firmware.
Click to expand...
Click to collapse
this phone is very simple let me break it down for you
locked bootloader
unlocked bootloader
lock need to use slapmymoto
unlocked and just install TWRP then install SUPERSU via custom recovery.
my guide tells you what phones can unlock there bootloader and what ones can't.

Can someone please post bootloader unlock instructions

This would be great to begin the Development section.
Links to Motorola drivers
Link to SDK & where to put it
Enabling unlock on the phone
When / how to run the fastboot commands
So if one of you could do this before someone else temporarily soft - bricks their phone? Please?
The instructions are no different from unlocking any nexus device with the exception that you need to check a box in developer settings. Just do a Google search.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
The instructions are no different from unlocking any nexus device with the exception that you need to check a box in developer settings. Just do a Google search.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I myself have no problem with this, but
IMHO, I think the instructions need posting in said section. Lots of folks are getting a Nexus for 1st time. Are we going to advise all of them just to do a Google search? If that is the consensus, then so be it.
wtherrell said:
I myself have no problem with this, but
IMHO, I think the instructions need posting in said section. Lots of folks are getting a Nexus for 1st time. Are we going to advise all of them just to do a Google search? If that is the consensus, then so be it.
Click to expand...
Click to collapse
Fair but then write them or provide a link.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
Fair but then write them or provide a link.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think there are many more qualified than I to do that. But I will try to devote some time this week to finding drivers, lollipop SDK for windows, etc. Then, when I get the phone unlock it and record all the steps. Then (if successful) post them. Hoping all the while that someone else beats me to it.
Well for one thing you won't need to download the SDK at all.
Just get this: [TOOL]Minimal ADB and Fastboot Just tested it on Windows 10 and it works fine.
I searched for N6 drivers and couldn't find any. Motorola has a "software & drivers" section but it's empty right now.
No TWRP yet, either.
wtherrell said:
No TWRP yet, either.
Click to expand...
Click to collapse
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command
Pilz said:
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command
Click to expand...
Click to collapse
Thought I would use TWRP to flash SU update zip.
Guess I could root 1st, then flash recovery later.
Pilz said:
It will come after root but google needs to post the factory images first.
Also of you download the google SDK then tap build number 7 times to enable Dev options you will be able to check he box that says allow OEM unlock. Then it's just a quick fastboot command
Click to expand...
Click to collapse
It seems to work even without checking the OEM unlock in developer settings. I forgot all about that and ran fastboot unlock the second I opened the box and it worked without any issues.
wtherrell said:
Thought I would use TWRP to flash SU update zip.
Guess I could root 1st, then flash recovery later.
Click to expand...
Click to collapse
Yeah but TWRP took a week or two to get on the Nexus 9 after it was rooted so it will be a while. I just want root so I can install a new camera app that I have to manually move.
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
eep2378 said:
It seems to work even without checking the OEM unlock in developer settings. I forgot all about that and ran fastboot unlock the second I opened the box and it worked without any issues.
Click to expand...
Click to collapse
Someone else did that without hitting the box and they got a softbrick so you got lucky. It's dumb that they added that extra step but I'm glad it's still unlockable.
Pilz said:
Someone else did that without hitting the box and they got a softbrick so you got lucky. It's dumb that they added that extra step but I'm glad it's still unlockable.
Click to expand...
Click to collapse
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.
akellar said:
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.
Click to expand...
Click to collapse
Yeah I let it sit for a while to do its thing then rebooted from fastboot. No issues. Not sure what is going on with the OP he said he let it sit for a long time and still nothing.
eep2378 said:
Yeah I let it sit for a while to do its thing then rebooted from fastboot. No issues. Not sure what is going on with the OP he said he let it sit for a long time and still nothing.
Click to expand...
Click to collapse
It could be something else that he did or and on his phone.
akellar said:
If you're referring to the other thread here, that isn't what caused his problem. Him powering down while it was formatting something likely was.
Click to expand...
Click to collapse
One of the softbricks came from selecting an incorrect device, IIRC.
gtalum said:
One of the softbricks came from selecting an incorrect device, IIRC.
Click to expand...
Click to collapse
Selecting an incorrect device? Not sure what you're referring to there.
akellar said:
Selecting an incorrect device? Not sure what you're referring to there.
Click to expand...
Click to collapse
Ignore that, I remembered something incorrectly.
Bjray said:
I searched for N6 drivers and couldn't find any. Motorola has a "software & drivers" section but it's empty right now.
Click to expand...
Click to collapse
You need to use the Google USB Drivers found here http://developer.android.com/sdk/win-usb.html#
akellar said:
Selecting an incorrect device? Not sure what you're referring to there.
Click to expand...
Click to collapse
That one was using the Wugfresh NRT somewhat prematurely. Quicker to use fastboot, I think.
jay_em113 said:
You need to use the Google USB Drivers found here http://developer.android.com/sdk/win-usb.html#
Click to expand...
Click to collapse
Thanks for the drivers link.

Categories

Resources