Database Users

Nexus S4G might be bricked, please help

I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks

Go look in the developer section, one of the stickies, the one that talks about the nexus s 4g cdma. You might have flashed something that was meant for the gsm nexus s. It has links to correct files and guides for the sprint version of the nexus.

Pm me and I will help u over the I'm client of your choice.

Basically, I have no service, and no card, so since I can access Fastboot Mode, and unlocked, is there a way to push a rom direct onto Sprint phone.
I looked in Developers Forums, I am not ready to jump in with custom rom yet (I have used extensively on other phones) but would like to start with stock, go with root and programs as needed.
So how would I push to phone via computer? and what programs, again, no idea of commands to use.

Have you flashed CWM yet? You can use that to reflash the stock ROM. Worst case you can use this thread:
http://forum.xda-developers.com/showthread.php?t=1072698
That will bring you to 100% out of the box factory settings

If you can get into fastboot, then you didn't brick it. You'll be fine, you just need to get in touch with someone that can walk you through the process of fixing it. Or search around, read, and take your time to figure out what to do.
It's not hard. The worse thing you can do is panic or rush to fix it.

Basically what you did when using superboot was you actually installed a boot.img file not meant for your device on your phone. What you should do is, go through the guide for your specific phone...you will have to install a recovery image and then install a custom rom or stock rom.
I do not know if you know your way around with fastboot....basically you could also ask a dev to send you the original boot.img and flash it using fastboot but the first stepi described is easier.
Sent from my Nexus S using Tapatalk

nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
If you are going to waste your brand new phone by being stupid how about giving it to me instead! Ill take good care of it.
Sent from my PC36100 using XDA App

Here Try this and let me know if it work:
1.Download this platform-tools.zip and extract it to your desktop
2.Connect your phone to the PC and enter bootloader mode
3.Press and hold Shift while right-clicking the folder you extracted 'platform-tools'
4.Click 'Open command window here' from the pop-up menu. cmd.exe window will open.
5.If the Bootloader is Unlocked continue to the next step. Type in the cmd.exe window 'Fastboot oem unlock' and follow the steps on the phone screen.
6.Type in the cmd.exe window 'fastboot flash boot boot.img'.
7.Type in the cmd.exe window 'fastboot reboot'.
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse

THANK YOU, for answer, but it didn't work.
I downloaded, opened, opened cmd from there.
My phone is unlocked, setting there with unlock screen, put it in bootloader mode, but when I type in instructions, it comes back "not recognized as internal, external command, program, batch file"
This is the problem I had when trying to unlock, so reading, used Superboot, probably wrong phone, so now it is wiped and empty.
I also read another thread suggesting Odin in this situation. Have downloaded that, SamsungSimpleDL, followed those directions, that doesn't work either. I have hacked and rommed Epic, very familiar with that, if it works, but cannot point to proper files (pda, pit, or bootloader).
So any other ideas, I am very good at directions, that is how I learned

My Phone is Fixed - YEAH
This did not work, but this link did
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
Basically used Odin (my old backup from Samsung Epic) and it worked when all these suggestions wouldn't.
I couldn't unlock easily, like all of these, therefore used Superboot. Would recommend no one touches that!!
I couldn't run any of the commands before this, and still couldn't use these.
So the instructions to dig thru the Developers section is correct, but so hard with so many customs, phones, carriers, to choose from. Makes it difficult
So use this link if stuck like me, I am just glad I con't have a brick, and I'm still pushing the Thanks button for all who helped, that's what will make this fun.

[Q] Atrix Special "Brick" Problem with touchpad - reset

So, guys...here's a real challenge for all of you.
I taught my friend how to enable multitouch on Atrix 4G and I did mine correctly, but he tried editing the touchpad.cfg file using the Atrix, removed the READ permissions of file and restarted the phone. Obviously, the phone can't read the touchpad.cfg anymore and touchpad is not working at all.
Gladly (yeah, this is sarcasm), the Android won't let he do a factory reset because the Froyo version needs an extra step of TOUCHING the screen to complete the recovery command.
I tried accessing it via ADB too, but it requires you to TOUCH the screen and choose your USB connection type.
So, touch is out of question. Is there any way to access this cell phone and make the files readable again (or replace the files, whatever makes it working). The phone has USB Debugging enabled, if it helps.
p.s: sorry if it's been posted before, but I search the forum A LOT and could only find two similar posts that were unanswered. (Please, let's not make this one be the third. We don't need that.)

Have you tried fastboot? try turning off the phone and holding power + volume down until you see the word Fastboot then press volume up. You should be able to do whatever from adb now. Try that or an official update.
this should be in Q&A btw
Sent from my MB860 using XDA App

Hey, Tayshun, thanks for the reply
I tried using Fastboot, but the device still can't be found by ADB shell. If you can point me some direction of what I may be doing wrong it would be great.
And I don't really understand when you say "that or an official update". How was I suppose to update the phone without touching it at all? Via Recovery Menu too? What is the option?
Thanks in advance

chapter81 said:
Hey, Tayshun, thanks for the reply
I tried using Fastboot, but the device still can't be found by ADB shell. If you can point me some direction of what I may be doing wrong it would be great.
And I don't really understand when you say "that or an official update". How was I suppose to update the phone without touching it at all? Via Recovery Menu too? What is the option?
Thanks in advance
Click to expand...
Click to collapse
if you can't access ADB to push a file, and you can't get recovery to work to reflash a fruitcake, then you're only choice is to sbf flash a 2.3.4 gingerbread sbf. either that, or the pudding sbf if you wish to stay unlocked.
it will give you a fresh, stock state of the phone. if he is on Gingerbread though, you can ONLY flash those two sbf's, any others will hard brick your phone.
EDIT: I just thought of something, it's a long run but you might be able to fix permissions in Recovery mode, i don't know whether it'll work or not though.

Alcapone263 said:
if you can't access ADB to push a file, and you can't get recovery to work to reflash a fruitcake, then you're only choice is to sbf flash a 2.3.4 gingerbread sbf. either that, or the pudding sbf if you wish to stay unlocked.
it will give you a fresh, stock state of the phone. if he is on Gingerbread though, you can ONLY flash those two sbf's, any others will hard brick your phone.
Click to expand...
Click to collapse
Well, he's running Froyo 2.2, so I guess this option is not available for us to try. Even though because I'm not really sure I can go throught all these steps.
Alcapone263 said:
EDIT: I just thought of something, it's a long run but you might be able to fix permissions in Recovery mode, i don't know whether it'll work or not though.
Click to expand...
Click to collapse
Can you please explain me this idea of yours in more details? I think that all I need is to be able to communicate with the device without using touch. I read somewhere that using Fastboot, I could do anything via ABD, but even putting the phone on this mode, I still get "device not found" on ADB console. Maybe I'm missing some extra step. But again, if you could please explain me about this permission thing in Recovery Mode, it would be great, Alcapone. Thanks!!!

Flash a pudding 2.2 sbf

[Q] Formatted Nexus 10

So I had the latest version of Paranoid Android on my rooted nexus 10. The keyboard was messing up so i wanted to run a factory reset and go all the way back to stock 4.2.1. In the process I accidentally wiped both the Rom and stock from my nexus 10 leaving it with no OS and nothing but the boot-loader. If i try and go to recovery mode all i get is the android laying down with an exclamation mark in a red triangle in it's stomach or the word Google with and unlocked padlock underneath it.
Any advice/help would be amazing! Thanks!

Download the factory image from Google: https://dl.google.com/dl/android/aosp/mantaray-jop40c-factory-0d641789.tgz
If you don't have fastboot already you need that too: http://downloadandroidrom.com/file/tools/fastboot.zip
Unzip the factory image tgz I linked to with 7zip/winrar etc
Unzip the fastboot.zip contents into the folder you just extracted
open a command prompt in the folder you just unzipped (mantaray-jop40c)
Boot your device into the bootloader by holding down BOTH volume keys and the power button
Connect your Nexus 10 to your PC
At the command prompt type
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader [wait for the device to reboot back to the bootloader]
fastboot -w update image-mantaray-jop40c.zip
This will wipe, repartition and install 4.2 straight from Google back to your device.. You will be prompted to update by Google to install the 4.2.1 update shortly after you boot up.
If you didn't have Fastboot already and had to download the zip I linked to, it's highly suggested to download and install the Android SDK so you have it and more native tools at your disposal. You can do that after the fact though and optional but highly suggested if you plan on learning your device more.

Will this work even if my device WAS Android 4.2.1 JOP40D?

Jamocobi said:
Will this work even if my device WAS Android 4.2.1 JOP40D?
Click to expand...
Click to collapse
Yep.

styckx said:
Yep.
Click to expand...
Click to collapse
Awesome thanks, I'll give it a shot once the files downloaded!

You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock

styckx said:
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
Click to expand...
Click to collapse
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?

Jamocobi said:
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Click to expand...
Click to collapse
How did you unlock and root this device in the first place?

styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
With the WugFresh Nexus Root Toolkit (Sorry, Can't post a link yet)

styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!

Jamocobi said:
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Click to expand...
Click to collapse
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...

styckx said:
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
Click to expand...
Click to collapse
Sorry about that, i was hoping you'd see it in time! You're definitely right about that, i was just worried i would totally mess it up if i did it myself but i can do that anyway with a toolkit so next time ill give it a shot without one.
Okay thanks, I'll take note of that one for sure! Really appreciate the help, thought i was doomed! haha!

You're welcome man.. It's no fault of your own for using the toolkit. To new users they're attractive and promise quick results.
Side note. It's extremely, insanely, stupidly hard to permanently screw up a Nexus device by flashing. There is always a way back from `the grave'.
Take care

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

How I Achieved Root on 4.4 Dev Edition

I know it seems like there's a lot of threads on Rooting already, but I was having the hardest time trying to find the correct thread for me because of the different variants of the Moto X. So I figured I'm not the only lost soul around here and wanted to take help someone else out. So here's I achieved Root after updating to Android 4.4. Keep in mind, Rooting Android 4.4 forced me to Reset my device and clear everything on it. I really didn't have a problem with it because I just got my device on 1/30/14.
1. Unlock the Bootloader
---- I made it easy on myself and followed QBKING77 on youtube http://www.youtube.com/watch?v=3sxgz7jxRMw
I have been following his tutorials since the days of the old htc EVO, great guy..
2. Install TWRP and SuperSU
---- I followed "" Guide for Unlocked Bootloaders "" by dray_jr http://forum.xda-developers.com/showthread.php?t=2603358
There are a few problems here though.
At Step 2: After installing the SDK, to make things easy for me I have always created a folder name "" Android "" at the root of the C drive and copied the SDK contents: eclipse, sdk, SDK Manager.exe, to it. It just makes it easier for me. So it in turn sets my path for the fastboot to C:\android\sdk\platform-tools
At Step 3: Make sure to copy TWRP "" twrp-2.6.3.1-ghost-4.4.img "" along with "" mfastboot.exe "" into the directory that your fastboot.exe is located. In my case it would be the C:\android\sdk\platform-tools directory.
After flashing the Recovery, the command "fastboot reboot recovery" didn't work for me. It doesn't have that command available. Instead, go to your phone and use your Volume Down button to choose Recovery on the Fastboot Menu and use the Volume Up button to select. I repeat, use the Volume Up button to select Recovery. I am so used to using the Power button to select that it kept turning the phone off and rebooting since I still had the USB cable plug into the phone. So learn from my mistake and don't waste your time by pressing the Power button.
Other than that, the rest of the instructions from the above guides worked for me. So thanks to qbking77 and dray_jr for their tutorials.

I didn't know qbking77 did motox videos. He was great in the GS2 and GS4 forums.
Sent from my XT1060 using Tapatalk

Thanks a lot, this was very helpful...pretty much every other thread in existence had me believing it was much more complicated than this and i wasted many hours before I saw this.

Jay10826 said:
Thanks a lot, this was very helpful...pretty much every other thread in existence had me believing it was much more complicated than this and i wasted many hours before I saw this.
Click to expand...
Click to collapse
Yeah I wish I'd seen this 24 hours ago. I had to figure much of this out myself. I swear it was easier to unlock and root my old GNex than it was to unlock and root my "unlockable" Verizon Developer Edition Moto X!

Roland Stone said:
Yeah I wish I'd seen this 24 hours ago. I had to figure much of this out myself. I swear it was easier to unlock and root my old GNex than it was to unlock and root my "unlockable" Verizon Developer Edition Moto X!
Click to expand...
Click to collapse
Well it should have been easier. That was a nexus....
Seriously though, how hard was this? Unlock bootloader given website key and flash TWRP and flash superSU zip. Took like 2 minutes. Of course it could be longer if you needed to figure out the Sdk.
Sent from my Dev Edition Moto X

Maybe I'm wrong....but with the boot loader unlocked....I'm pretty sure rooting this and my N7 was the exact same procedure.
Sent from my Moto X cellular telephone...

It was just annoying to have to jump through hoops just to GET the Unlock code, which was several lines of gobbledygook that had to be transcribed carefully and then retyped. Some people (like me) aren't conversant with ADB and command windows and such. (Yes I know, maybe people like me shouldn't be rooting around under the hood of our phones.)

May end up ordering a GSM Developer Edition tomorrow. I believe it's the same procedure as outlined here. Can someone confirm this.

larry62 said:
May end up ordering a GSM Developer Edition tomorrow. I believe it's the same procedure as outlined here. Can someone confirm this.
Click to expand...
Click to collapse
Yeah, all I did was unlock the bootloader, install TWRP, then installed the SuperSU zip and when I rebooted I was rooted.

Roland Stone said:
It was just annoying to have to jump through hoops just to GET the Unlock code, which was several lines of gobbledygook that had to be transcribed carefully and then retyped. Some people (like me) aren't conversant with ADB and command windows and such. (Yes I know, maybe people like me shouldn't be rooting around under the hood of our phones.)
Click to expand...
Click to collapse
Next time copy the cmd text into notepad then copy/paste from there.

...

District said:
According to qbking77's video, when you unlock your phone, you wipe your data.
Does this wipe your MMS?
Click to expand...
Click to collapse
Yes. Text messages are part of data.

Roland Stone said:
It was just annoying to have to jump through hoops just to GET the Unlock code, which was several lines of gobbledygook that had to be transcribed carefully and then retyped. Some people (like me) aren't conversant with ADB and command windows and such. (Yes I know, maybe people like me shouldn't be rooting around under the hood of our phones.)
Click to expand...
Click to collapse
christ, you typed out the unlock data? :laugh:

^--you can't copy/paste from command line. I did the same thing.
I also agree this was a royal pain in the ass. Took me forever to find this information as well. This is not my first rodeo, btw.

Are you guys downloading and flashing SuperSU separately? Because when I flashed TWRP it advised my phone was not rooted and fixed it when I rebooted. I didn't have to download or flash anything separately. It was incredibly simple...after going through the website for the unlock code of course.
And yes, just like the Nexus devices, unlocking the bootloader automatically does a factory reset and erases all data as a safety precaution.

overthatscreen said:
...After flashing the Recovery, the command "fastboot reboot recovery" didn't work for me. It doesn't have that command available. Instead, go to your phone and use your Volume Down button to choose Recovery on the Fastboot Menu and use the Volume Up button to select. ...
Click to expand...
Click to collapse
right fastboot reboot recovery doesn't work.
You could do... fastboot reboot bootloader to get into bootloader instead of messing with holding buttons.

unsivil_audio said:
^--you can't copy/paste from command line. I did the same thing.
I also agree this was a royal pain in the ass. Took me forever to find this information as well. This is not my first rodeo, btw.
Click to expand...
Click to collapse
You can. It's in the video.

bengadget said:
You can. It's in the video.
Click to expand...
Click to collapse
Did not work for me so I manually input the code
Sent on my Gummy running Lenoto X

overthatscreen said:
I know it seems like there's a lot of threads on Rooting already, but I was having the hardest time trying to find the correct thread for me because of the different variants of the Moto X. So I figured I'm not the only lost soul around here and wanted to take help someone else out. So here's I achieved Root after updating to Android 4.4. Keep in mind, Rooting Android 4.4 forced me to Reset my device and clear everything on it. I really didn't have a problem with it because I just got my device on 1/30/14.
1. Unlock the Bootloader
---- I made it easy on myself and followed QBKING77 on youtube http://www.youtube.com/watch?v=3sxgz7jxRMw
I have been following his tutorials since the days of the old htc EVO, great guy..
2. Install TWRP and SuperSU
---- I followed "" Guide for Unlocked Bootloaders "" by dray_jr http://forum.xda-developers.com/showthread.php?t=2603358
There are a few problems here though.
At Step 2: After installing the SDK, to make things easy for me I have always created a folder name "" Android "" at the root of the C drive and copied the SDK contents: eclipse, sdk, SDK Manager.exe, to it. It just makes it easier for me. So it in turn sets my path for the fastboot to C:\android\sdk\platform-tools
At Step 3: Make sure to copy TWRP "" twrp-2.6.3.1-ghost-4.4.img "" along with "" mfastboot.exe "" into the directory that your fastboot.exe is located. In my case it would be the C:\android\sdk\platform-tools directory.
After flashing the Recovery, the command "fastboot reboot recovery" didn't work for me. It doesn't have that command available. Instead, go to your phone and use your Volume Down button to choose Recovery on the Fastboot Menu and use the Volume Up button to select. I repeat, use the Volume Up button to select Recovery. I am so used to using the Power button to select that it kept turning the phone off and rebooting since I still had the USB cable plug into the phone. So learn from my mistake and don't waste your time by pressing the Power button.
Other than that, the rest of the instructions from the above guides worked for me. So thanks to qbking77 and dray_jr for their tutorials.
Click to expand...
Click to collapse
After i follow the above steps for my GSM Moto X Developer Edition with Android 4.4, will i still be able to get OTA updates as long as I keep the stock ROM ? I like the stock ROM anyways. Also any issues with the hands free "OK Google Now" voice feature after rooting and unlocking bootloader?

After doing this we should be able to retain unlocked and rooted right?