yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] easting:
That's what I was thinking as well. I'll give it a shot in a couple of hours.
[Moto X Original Android Development] mpegripper:
let us know how it works and which option you used. I see 3 options to root?
[Moto X Original Android Development] easting:
Success! 4.4 non-dev VZW XT1060 rooted using stillthisguy's Moto X Toolkit. Used option 11.

Only comments to other users: read carefully, type carefully.
[Moto X Original Android Development] ijeenyus:
I downloaded all the files and put them in the correct folders. But I get this window and the toolkit crashes. Did you get this screen or have any suggestions? Also have write protection to be "0".
[Moto X Original Android Development] easting:
My guess is that you don't have the 4.2.2 file in it's folder.
[Moto X Original Android Development] ijeenyus:
stillthisguy told me to reinstall the toolkit. Did so and have root on 4.4. Sorry 640k, didn't mean to highjack your thread, thanks for all your work.
[Moto X Original Android Development] nbogan1:
When I try to uinzip the .rar file it gives me an error saying it's not a valid RAR file
[Moto X Original Android Development] needleyepoke:
Man that really seems like a lot of stuff just to only root the phone. This was the first developers edition I've ever purchased..well worth the money still have warranty and was way easy to unlock. And it's been the only phone I've preferred stock...besides using xposed
[Moto X Original Android Development] mpegripper:
it is a lot of work and the most i've ever had to do on an android phone (i'm sure there's worse). but i absolutely hate having a pin on my phone when my exchange account is there. so it was worth it to me.

fyi, i'm guessing that the 4.4.2 update will kill root too, but hopefully since things like write-protection are gone from my phone now it will be a much quicker process next time.
[Moto X Original Android Development] needleyepoke:
Well I've got mad props to everyone that's been working on it
[Moto X Original Android Development] csos95:
I have a question about rooting the moto x. I've seen that to unlock your boot loader and root you need to get a key from the moto x website. One of the things I'm worried about though is losing my warranty. On most devices I don't care because either the warranty sucks or I can just flash stock and relock the boot loader. On the moto x i actually care about the warranty because it covers accidents (within reason). If I can just flash to stock like other phones then it's no problem but, If I get the unlock code from Motorola's website don't they have a log that I have an unlocked boot loader? If so does this method bypass that(it says locked boot loader in title and I don't see message of going to moto x website)?
[Moto X Original Android Development] ijeenyus:
Rooting does not require posting phone ID. Usually (85% of the time) you can unroot back to stock. I've seen relocking bootloader before, but it's rare. This is the choice you have to make if you want custom ROM (unlocked bootloader) or extra features (i.e. titanium backup, xposed, etc. only requires root)
[Moto X Original Android Development] momentman10176:
Well, I finally got root on 4.4 using this toolkit, taking the update, and the using the commands listed in Jcase's original "Slap My Moto" thread, just wish I had been able to get it back in 4.2.2 where I could have used safestrap.
[Moto X Original Android Development] tcollum:
You can use safestrap on 4.4
[Moto X Original Android Development] momentman10176:
Couldn't get the rom to boot...and yes it was a safestrap rom.
[Moto X Original Android Development] tcollum:
Try flashing it in the stock slot
[Moto X Original Android Development] csos95:
Been trying to root on 4.4 for the past two hours but unfortunately i'm getting the "The process cannot access the file because it is being used by another process" error on all 3 telnet steps.

EDIT: I'm now stuck on 4.2.2 I've tried selecting "6. revert Moto X to 4.4" but after the warning screen it just goes back to the main menu. I've tried using system update 3 time and it failed every time, I did a factory reset and tried twice more, redownloading all of the files and trying again but if that doesn't work I have no clue where to go from there. :(

EDIT2: I'm going through the steps manually and so far it seems to be going well.

EDIT3: doing it all manually worked but was a pain in the ass. Hopefully 640k can find a solution for the telnet stuff.
[Moto X Original Android Development] phinnaeus:
I think the problem is RockMyMoto added an equation you have to solve inside the telnet shell which this script is unable to parse/solve.
[Moto X Original Android Development] nm3210:
I spent a while rooting last night and came to the same conclusion. Would it maybe work to use an older version of RockMyMoto? Anyone have one?
[Moto X Original Android Development] phinnaeus:
It might be possible to programmatically solve the equation or proxy that bit of interaction back to the user. I'm on my work computer so I don't have the Go!.bat file to open it up and try it out but there's also the Moto X Toolkit in the other development forum which has an option to run RockMyMoto, not sure if it has a work around for the equation or not.
[Moto X Original Android Development] akhenax:
I think the answer for now is to use the version of RockMyMoto that does not have the equation.

Any idea as to why it was updated with an equation?
[Moto X Original Android Development] iifuzz:
Does this unlock the boot loader?

If I need to send the phone back in, can I return it back to how it was?
[Moto X Original Android Development] cawaller:
Still Working on this?

Or giving up on it for a while?
[Moto X Original Android Development] iifuzz:
Also , when the 4.4.2 ota comes out, will root still be kept?
[Moto X Original Android Development] Redjax:
I, for the LIFE of me, cannot root this phone.

Let me just type out the process I've gone through to see if anyone can see what I'm doing wrong.

1. Flash back to 4.2.2 camera using RSD or the manual fastboot flash xx method.

2. Skip setup, connect to WiFi

3. Go through RockMyMoto part of this script (doesn't seem to work for me anymore, all the steps complete, but SuperSU says the binary isn't installed).

4. I've already removed write protection, so I skip that step.

5. Flash back to clean 4.2.2 camera

6. Take OTA

7. Try using the install.sh (never works).

Am I doing something wrong? This just plain doesn't work anymore.
[Moto X Original Android Development] stillthisguy:
I know you were being helped in the other thread, but just in case.

Since you already have WP removed

1. Flash back to clean 4.2.2 camera update

2. Do the first part of slapmymoto

3. Install 4.4

4. Do the last part of slapmymoto

5. After issuing the last 3 commands of slapmymoto, wait about 1 minute, then reboot

6. After reboot, install SuperSU from play store and update binaries.

7. Profit.
[Moto X Original Android Development] themcfly:
Hello,

Just received my XT1052, european MOTO X. How can I know if this script will work with it? I can't find any info online on this model, also don't know to which US edition could be comparable. Thanks in advance.
[Moto X Original Android Development] Redjax:
Ok, I've tried this literally 15 times in the past couple days, and on the last step, I always get stuck with "/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission Denied."

I have tried rooting this device every possible way I can find on the Internet; I've used the official SlapMyMoto post, I've been pointed to a Reddit thread, I've used a theUnlockr guide, I've watched YouTube videos, I've followed steps users have given me to try, and I've tried a few "SlapMyMoto didn't work? Try this" threads, with ABSOLUTELY NO LUCK. This device is driving me absolutely nuts, I'm ready to stomp on it with all the force I can send through my leg. All I want is root access. Is there anything else I can try before just giving up and selling it, and getting a different device that actually works?
[Moto X Original Android Development] stillthisguy:
Since you have listed everything else, you could try my toolkit. Have had a lot of people report that it worked for them. After installing, choose option 11, make sure you have the correct files in the correct folders, then choose option 1. Answer the first question No, then answer the second question Yes. If you run into any issues you can comment in my thread as well.
[Moto X Original Android Development] razmalai:
How can I undo the changes generated by this script?

Used this script on T-mobile version, bootloader locked

No luck, did not gain root access, I believe, because had issues with telnet as other users have had. Back on 4.4 now

Would like to:

1) Accept the latest OTA (Blur_Version.161.44.25.ghost_row.Retail.en.US.zip) - installation aborts!

Tried installing the OTA manually however when in Recovery, when verifying current system, get error '"/modem/image/dsps.b00" has unexpected contents. Installation aborted

2) Install apps NOT from Play store, but can't because entering security tab is now impossible

Is it possible to fix this by completely restoring the original state of the phone somehow? Thanks.
[Moto X Original Android Development] ashrob:
"Moto X factory image was NOT found" and yet it's right there, in the folder, downloaded from the link in the OP. I've tried changing the filename etc but still the same error. EU Moto XT1052.

Any ideas anyone please?
[Moto X Original Android Development] Flexia32:
I was having issues with Telnet and I think it had to do with the Telnet server not being installed in windows. Make sure you go to Control Panel, Programs, Turn Windows Features On and OFF and Make sure BOTH telnet folders are selected.
[Moto X Original Android Development] 640k:
Ok. Here's the deal. There's going to be some manual work for you.

1. Close out of the script.

2. Open a CMD window and change to the directory this script is located.

3. Type the command, "ADB kill-server", hit enter, and do it again.

4. Download the new script and either start over, or use the advanced menu to go through each step.

Thanks for your help and patience!! I'm going to be taking off for the day. Your phone is currently usable, just not rooted. If you want to stop and pick up tomorrow, that's cool. I'll try to hop on the forums later to check in. This is the only pesky little bug I hadn't been able to tackle. I think I've got it, however, so please try again. Starting over won't hurt anything, just take extra time. But I recommend it just so we can run the script from end-to-end.

THANKS AGAIN!
[Moto X Original Android Development] lucky13:
Anyone on Verizon 4.4 use this? Once done, are you back on 4.4? (I'm downloading the 4.4 from Motorola along with both of the 4.2.2 ones didn't know which so I grabbed both). Or will it prompt for a 4.4 OTA and do you take that? Not new to rooting, but I always want to be prepared for everything. Thanks for this btw, I just hadn't had time to sit down and root via the other means yet.
[Moto X Original Android Development] 640k:
I developed this script for/on my device, which was at 4.4. You will be flashing 4.2.2, exploiting the root and then take the update to 4.4. The script will walk you through everything.
[Moto X Original Android Development] lucky13:
Awesome thanks.
[Moto X Original Android Development] lucky13:
I'm stuck here also. When I close impacter, it won't connect. Tried what you posted but says ADB is an unrecognized command and doesn't do anything.

EDIT: I was wrong, I did do this successfully (user error) and still no luck.
[Moto X Original Android Development] lucky13:
Here's what it shows. As an aside, when the impacter thing is running, it goes from starting activity to stopping really quick, is it doing it's thing?
[Moto X Original Android Development] lucky13:
FYI I'm on win7, have enabled telnet, disabled antivirus, and firewall, and still can't get past the impactor step. Really want to help out. I might be done for the night trying, will check in tomorrow if I'm not back on tonight.

I have also been through every setting on the moto to enable usb sideload etc.
[Moto X Original Android Development] noc215:
I gave it an attempt on my XT1053, and this is the exact step where it fails for me as well. I tried two times; once with following the tip in OP about connecting to wifi before enabling USB debugging. I am guessing it is a router setting issue, I'll try to give it another go this weekend
[Moto X Original Android Development] Bobbar:
It appears to be failing the 4.4 -> 4.2.2 downgrade.

You mention that 4.2.2 will be flashed twice. But after the first attempt, the script continues to the impactor step while the device is still on 4.4.

***DISREGARD***

Downloaded wrong 4.2.2 firmware. Need Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.

---------- Post added at 10:45 AM ---------- Previous post was at 09:49 AM ----------

I'm also getting stuck on the TELNET step. I can manually connect with TELNET, and even NC connects. But it fails in the script with an unknown error.
[Moto X Original Android Development] 640k:
Hi guys been sick as a dog all day today so I haven't been able to troubleshoot. The issue is the telnet isn't passing the commands. I won't be able to troubleshoot until maybe Monday.
[Moto X Original Android Development] tango41:
Is this working or do I need to wait to try this? Do I have to be on 4.4 to start (on 4.2.2 now)?

Sent from my vzw moto X
[Moto X Original Android Development] lucky13:
Not working yet, it fails trying to telnet to the device. Author said he'd try to work on it tomorrow. You can be on any build, it walks you through it.
[Moto X Original Android Development] enkryptik:
At that point, I installed telnet via windows programs and features. I then manually performed all the telnet steps successfully.
[Moto X Original Android Development] lucky13:
Yeah, I'm at that point also. I am not loving being on 4.2, and need to have root. I'm going to try it now, was just hoping for the easier solution lol. I haven't had to mess with adb and such since rooting my OG droid on release day, so I'm a bit out of practice.

Edit: Nevermind, continuing at MotoWpNoMo.
[Moto X Original Android Development] derik123derik123:
looking forward to the fix for this.
[Moto X Original Android Development] hawkdown77:
Doing this way...it erase all in the phone??

I dont wanna lost all my things in the phone.

Enviado de meu XT1058 usando o Tapatalk 2
[Moto X Original Android Development] lucky13:
Any way you do it that will happen. No way around it.

---------- Post added at 07:16 PM ---------- Previous post was at 07:09 PM ----------

And if nothing else, I have this script to thank for finally getting me off my ass and rooting manually, so thanks again! I got root, albeit I had to do it.
[Moto X Original Android Development] 640k:
playing catch up today, hope to have a resolution for this script issue soon. thanks to all the early adopters and people willing to help.
[Moto X Original Android Development] 640k:
Hey guys I made a quick adjustment to the TELNET line. I'm hoping it's what I was missing. Is anyone at the right step that they can continue to test?
[Moto X Original Android Development] wncoulte:
:good: Is there a video of this running available?
[Moto X Original Android Development] 640k:
just curious, what would the video benefit?
[Moto X Original Android Development] wncoulte:
If I wrote to you I saw 'Michael Jordan dunked all over LeBron James last night', many would praise that bit of content alone, similarly to the praises contained in this forum of your slam-dunk software (script) ... and you ask me what would the video benefit?
[Moto X Original Android Development] 640k:
the script is doing what is already documented on these forums. i'm not claiming anything outside of the fact that it automates the instructions you can manually perform yourself. the script is provided in clear text, as a batch file, for anyone to follow.

so to answer your question, no there is no video at this time.

if i get my hands on a device that isn't rooted, i can make one. unfortunately there are steps that take place that are permanent that won't give the same results on a second pass.
[Moto X Original Android Development] addictedhacks:
640k Thank you so much for this. You are the man!
[Moto X Original Android Development] drsuse:
maybe i am a moron.. actually i bet it is user error, .. but i downloaded the new script after the last update.. ran it.. i get to 4.2.2 then it reboots

i enable wifi and add it to my wireless, then go to build.. to get developer and enable usb... then it runs impacter... then i to the telnet 2222... then it goes back to the screen after waiting to complete.. no popups on my phone aside from allow unknown.. i allow.. once i hit x on the impacter.. it says cannot connect to the device. am i missing something i have done it about 9 times last night and yesterday
[Moto X Original Android Development] 640k:
without more details, it sounds like you're having the same telnet issue everyone else is having. does the script say, "TELNET to 192.x.x.x failed!" and then a bunch of stuff about your device not being connected? If so, can you open the file, TELNET.ERR and paste the contents here for me to see?

Thanks!
[Moto X Original Android Development] drsuse:
im going to get to the point now and get the telnet.err details to you.. because now its blank give me 10 min
[Moto X Original Android Development] drsuse:
i cannot figure out how to read the telnet.err. i tried it with notepad but nothing. here is the error and what shows in the telnet window
[Moto X Original Android Development] 640k:
ok so the telnet session in the window on the upper-right is basically waiting for a command, so that's bad. do you see a "rockmymoto.txt" in your folder? (correct answer should be: yes)
[Moto X Original Android Development] 640k:
download this file and overwrite the one in the install folder and try again. exit the current script and close any terminal windows still open and then run GO!.CMD again. choose option 1a. and you won't have to reflash 4.2.2 again.

this is going to pause at the telnet part and not do anything. i need the output of this string:

ECHO START /MIN /WAIT "Telnet Session" NC %IP_ADDRESS% 2222 ^< "%~1" ^> TELNET.ERR

>>file removed<<<
[Moto X Original Android Development] drsuse:
thanks doing it now and yes i have the rockmymoto txt
[Moto X Original Android Development] drsuse:
here you go
[Moto X Original Android Development] 640k:
i know what the problem is, i just don't know how to fix it yet.
[Moto X Original Android Development] drsuse:
Do you think maybe we could possibly have a workaround? So that we can continue using the script? I don't know exactly what the problem is but I can keep testing whatever you want to try
[Moto X Original Android Development] 640k:
give me a minute, on a call right now. brb.
[Moto X Original Android Development] 640k:
ok try this one. when you get to telnet, and it says, press any key to continue, don't. :) give me a screen shot of all of the terminal windows on your screen.
[Moto X Original Android Development] easting:
[YOUTUBE]http://www.youtube.com/watch?v=KMEHars4nU0[/YOUTUBE] Perhaps a new 4.4 root coming?

640k, I'm having driver issues I haven't been able to work out. Frustrating, to say the least. Haven't messed with rooting since my Bionic so I'm moving a bit slow in getting this solved.
[Moto X Original Android Development] drsuse:
here ya go
[Moto X Original Android Development] 640k:
getting the drivers working is step one to anything. download from the link on the main page. i did it on my win8 machine at home and worked flawlessly.
[Moto X Original Android Development] 640k:
do you have another CMD terminal somewhere "Telnet Session"

what files do you see? do you see telnet.err? telenetgo.bat? rockmymoto.txt?

thanks!!
[Moto X Original Android Development] easting:
I'm with you on that but I've uninstalled, reinstalled, etc., rinse, repeat. THE MACHINE LIES! ;)
[Moto X Original Android Development] drsuse:
back at my desk... im trying it now
[Moto X Original Android Development] 640k:
FYI - leaving in about 10-15. will troubleshoot as much as I can. hopefully i've got this one nailed down.
[Moto X Original Android Development] drsuse:
should i press continue?
[Moto X Original Android Development] 640k:
what do you see in the telnet.err file? open it with notepad. if nothing, say nothing, otherwise, paste the info.
[Moto X Original Android Development] drsuse:
ÿýÿýÿûÿû

dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto

exit

~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto

RockMyMoto 1.0

by Justin Case

PayPal Donations maybe sent to: jcase@cunninglogic.com

Special thanks to saurik, you rock!

System is not write protected...

Executing step 3...

~ $ exit
[Moto X Original Android Development] 640k:
that's a good thing, but looks like you've already done a few steps, maybe outside of the script? see if you can run the script "normally" (hit a key to continue). each time the telnet pauses from now on, just let it go. let me know if you run into issues.
[Moto X Original Android Development] JonBsbB:
This work on all Moto X variants? AT&T especially
[Moto X Original Android Development] drsuse:
i tried it and got it rooted on 4.2.2 it bootlooped when going to 4.4.2 .. so i started over on your script to just do it the right way.

i got this message now.. it went all the way through but stopped here
[Moto X Original Android Development] 640k:
you've already removed WP - you'll get an error that beaups failed. just tell it to proceed to next step. you're beyond "rockmymoto" only the "slapmymoto" applies to you.

i need to add some logic to test for WP. the whole first half of the script could be skipped.
[Moto X Original Android Development] 640k:
if jcase/beaups methods work on at&t devices, then yes. just follow the directions.
[Moto X Original Android Development] Deenybird:
Thanks for your work on this 640.

I don't know enough to be a 'tester', but i am eager to proceed once i hear someone has had success with the AT&T version.

If anyone has rooted the AT&T variant with this method, please report back.

Again thanks to OP and all those who have been testing for him along the way.
[Moto X Original Android Development] drsuse:
thanks 640, all i had to do was the slapmymoto and i am now on 4.4.2 and rooted. you rock!!!

---------- Post added at 06:30 PM ---------- Previous post was at 06:15 PM ----------

Deenybird, i have AT&T and root works fine on 4.4.2
[Moto X Original Android Development] 640k:
drsuse FYI moto x is only 4.4.
[Moto X Original Android Development] drsuse:
Crap sorry... Got it confused with 4.2.2
[Moto X Original Android Development] ijeenyus:
I'm stuck on the same process. Verizon Moto X too
[Moto X Original Android Development] tducote:
AT&T Moto X here. The downgrade to 4.2.2 seems to have worked fine, but I'm stuck at the step after closing the Cydia Impacter that says "Attempting TELNET session to 10.0.0.88...".

I get the following:

"TELNET to 10.0.1.88 failed!

Your device is not connected!

Your device is not ready!

You must be on 4.2.2 and run Cydia Impactor using

the instructions provided in these steps.

..."

I don't think the Cydia Impactor failed, but honestly, I really don't know.

Thanks for all you've done so far. Let me know if there is any more info I can provide to be any help.

EDIT: So it seems as though maybe I wasn't patient enough or something. The script ended up doing a few more steps that looked like the rest of what it was supposed to do, but then at the end, I didn't have root. :( I think I'll give it another try.
[Moto X Original Android Development] 640k:
i've updated the script with a different telnet method. please re-download and try again.
[Moto X Original Android Development] dano1282:
Theoretically....if this works the Verizon MotoX...it should work on the Ultra/Maxx/Mini correct? I don't have a problem with wiping my device...everyting is backed up anyways...