yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] pic2022:
Ok guys, i am trying to root my Moto X GSM Dev Ed.

I rolled back to 4.2.2 t-Mo RETAIL version/

I did the send SlapMyMoto.jar to phone thing, I go to Cydia Impactor and run the system 2222 thing, no errors pop up so I assume it worked. Payload pops up and then closes instantly.

I go onto cmd and type the telnet command and cmd tells me 'telnet' is not recognized...

What am I doing wrong? I am so lost guys. Please help.
[Moto X Original Android Development] somerandomname1:
Your first mistake is coming to this thread. You have a Dev edition. Unlock bootloader. Flash recovery. Flash su.
[Moto X Original Android Development] pic2022:
D'OH! -_- my bad. thanks :D
[Moto X Original Android Development] ReadyMadeFire:
Thanks so much!! Was not to difficult to accomplish and accomplished on the first try. Awesome!! +1 Thanks!!
[Moto X Original Android Development] anirudh412:
Glad to see you got it working, but please NEVER quote OP in any thread
[Moto X Original Android Development] ReadyMadeFire:
Thanks! Edited.
[Moto X Original Android Development] krazyrph@yahoo.com:
I don't know what I am doing wrong, but after the second dalvik command it says it will autoboot. I keep getting the following message -

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

SlapMyMoto 0.5

by Justin Case

PayPal or Google Wallet donations maybe sent to: jcase@cunninglogic.com

Special thanks to saurik and J2, you guys rock!

System is not write protected...

Executing step 3...

After reboot, attempt to apply 4.4 OTA

~ $

I have done this step several times, just cant get it to auto reboot. I am currently on stock 4.2.2 (.54)
[Moto X Original Android Development] sorullo_xgrx:
Can you do adb reboot... It was mentioned that you could toggle Bluetooth to speed up the process
[Moto X Original Android Development] krazyrph@yahoo.com:
I am able to adb reboot manually after each dalvikvm command. Also tried toggling Bluetooth, but did not work.
[Moto X Original Android Development] jason.912:
Went without a hitch.. Awesome work!
[Moto X Original Android Development] niteglo:
I had the same issue. I had recently applied the patch to permanently remove write protection and that's what was causing the problem. I could advance through the steps (although I had to manually restart when it detected that my system wasn't write protected), but when it got to step 6, I would get a permission denied error and couldn't proceed through the rest of the process. Post #450, jcase said, "I will update slap my moto as soon as time allows to work with devices who have no write protection." I tried the whole process a number of times and the issue persisted. I am assuming that since more and more people are disabling write protection that the fix will be released fairly soon. Until then, no root for me.
[Moto X Original Android Development] anirudh412:
Quick question, I am Slapped on 4.4. Could I just RSD back to Camera OTA and be Rocked?
[Moto X Original Android Development] Skyrocket2Paradise:
worked flawlessly.

THANK YOU!
[Moto X Original Android Development] ohmimpotence:
So pardon my ignorance but if I have a T-Mobile Moto X, I will be able to root it using this method without unlocking the bootloader and voiding the warranty? If so, what are the disadvantages of not having an unlocked bootloader?
[Moto X Original Android Development] Kittiesoncrack:
Will this work with the Sprint Moto X on 4.4?
[Moto X Original Android Development] jason.912:
So i had this working perfectly along with Motowpnomo, then i bricked the os when i was messing with the framework.

so here i am flashed back to the camera update, trying to get this working. now when i run

dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto

i just get

System is not write protected...

Executing step 3...

After reboot, attempt to apply 4.4 OTA

~ $

--

I then figured i could just start at the take the 4.4 ota step and move forward, but nope. at step7 i get access denied.

now what do i do?
[Moto X Original Android Development] lowvolt1:
You will have to wait until jcase updates the method. You are stuck with no root for now.

via my slapped KIT KAT moto X
[Moto X Original Android Development] anirudh412:
Bumping my question. Anybody?
[Moto X Original Android Development] gitku:
If you haven't used the wpnomo write protection exploit you can

---------- Post added at 05:20 AM ---------- Previous post was at 05:19 AM ----------

That was in response to anirudh412 .. Not sure how the wrong thread got quoted :)
[Moto X Original Android Development] mistermojorizin:
Actually you just need to have stock recovery and unfreeze all system apps. Root even survives the camera update.
[Moto X Original Android Development] anirudh412:
Did not use WPNOMO thankfully. Gonna give it a go
[Moto X Original Android Development] MaKTaiL:
Will I lose warranty if I root using this method?

I'm planning to root my Moto X. I have 2 options. Unlocking bootloader or using this.

If I lose warranty either way then I'll my unlock bootloader. Can someone answer me? Thank you in advance :)
[Moto X Original Android Development] codymoto:
So I have to ask, if this uses the same vulnerability as rockmymoto which is also based off of pwnmymoto, and therefore also motoroot (your first root method) does that mean I can take the 4.4 kit and not loose root if I am still rooted by motoroot (which did not touch the recovery). I took the camera ota a while back and it kept root. If I take the kit kat ota will I also maintain root?

[MENTION=2376614]jcase[/MENTION] thoughts?
[Moto X Original Android Development] lowvolt1:
Where are you getting your info.?

via my slapped KIT KAT moto X
[Moto X Original Android Development] Sharkeyd:
You always lose warranty when you root. If you have a dev edition you will not lose warranty by unlocking your bootloader.
[Moto X Original Android Development] MaKTaiL:
My device is not exactly a Dev edition, but it is unlockable. It is sold in Brazil. XT1058

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] Sharkeyd:
If you're worried about warranty don't root. Otherwise, if you can unlock your bootloader, I would root by flashing supersu, much easier.
[Moto X Original Android Development] mistermojorizin:
when the camera update came out i asked jcase on gchat and then I did it on my non developer edition droid maxx. just took the OTA camera update and kept my root without any extra hassles (besides having to re-freeze the system apps). BUT, and this is a big but, I had the stock recovery. most people don't have that (cause they use a system write protection off method that removes it) and that's why you see the posts "taking the update with root made my phone bootloop" - actually NO. it wasn't root, it was you running without a stock recovery to get write on system, totally different than just root.
[Moto X Original Android Development] lowvolt1:
When moto x came out it had 4.2 pre camera update. You had to root using pwnmymoto. In order to accept the OTA you had to unroot and have all system apps in tact. After taking camera update you could no longer root using pwnmymoto. This is why jcase developed Rockmymoto. After the 4.4 update which you could not take unless you were stock 100% you could not root using rockmymoto. Hence, slapmymoto. There wasn't even a write protect off until wpmotonomo. I think your info. Is scewed.

via my slapped KIT KAT moto X
[Moto X Original Android Development] jcase:
Guys/Gals/Bots, I have to step back for a while, I won't be answering most PMs nor replying to posts.

Concept behind SlapMyMoto 1.0 is done, so is most of the code (could take a rewrite, its messy but really simple) and if someone has both java and android experience, I would appreciate some help finishing it. It shouldn't take more than an hour or so, but right now I don't have the time, nor energy to do so. It does need to be fixed to work with devices that have been hit with MotoWPNoMo. If this fits you, an email jcase at cunninglogic dot com would be appreciated
[Moto X Original Android Development] ohmimpotence:
I thought you only lose warranty if you unlock bootloader. Doesn't this method root without unlocking bootloader?

If it's not unlocking the bootloader then I imagine it's possible unroot it without a trace of the device being tampered with unlike unlocking the bootloader so less risk of losing warranty, no? Only issue I can see is if your phone gets bricked/inoperable and you need to send it in but can't unroot it first.
[Moto X Original Android Development] funnyfarm299:
Wish you could have finished helping me with my problem, but I'm sure whatever your reason is, it was necessary. We'll still be here when you come back.
[Moto X Original Android Development] enjoimadcow:
Finally took the plunge and my at&t moto x is now slapped. Thank you for the root man. That was the only thing my phone was missing!
[Moto X Original Android Development] jcase:
I help a ton of people, and if they are not persistant, or catch me on IRC, its unlikely to get finished. Catch me on IRC. My family is more important than XDA users, so I am limiting my XDA time until things smooth out here
[Moto X Original Android Development] natezire71:
I would like to say that what you said is rude. Devs have lives too. ;)

However, if you ask politely, I'd love to help you.
[Moto X Original Android Development] funnyfarm299:
I think what I said was misconstrued. What I was saying was that whatever he has to deal with is more important than us, and while we could/would wait, whatever he needed to do might not.

Anyhow, I've tried the slapmymoto procedure 3 times now, and every time I get the su binaries not installed error when running supersu.

My procedure is as follows

1) flash to VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml

2) unzip slapmymoto, push to sdcard

3) run impactor, open telnet (I use putty), run slapmymoto

3b) wait a few minutes, run impactor, open telnet, run slapmymoto

3c) wait a few minutes, run impactor, open telnet, run slapmymoto

4) boot into bootloader, flash recovery (from the zip in step 1), reboot, wait a few minutes

4b) take the OTA to 4.4, I then waited another few minutes

5) flashed gpt.bin, motoboot, and logo

6) wait a few minutes, push all those files, and reboot

7) wait a few minutes, open shell, run echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper

7b) do it again

At this point, I have recieved no error messages, but when I install supersu, I get the su binaries not installed error

I've tried running step 7 another few times after attempting the supersu install but it didn't help.

I messaged jcase, and he asked me "

adb shell ls -l /system/xbin/su

adb shell getprop ro.boot.write_protect

adb shell ls -l /system/bin/log

and give me the output"

ls of /system/xbin/su returns no such file or directory

adb shell getprop ro.boot.write_protect returns 0

adb shell ls -l /system/bin/log returns -rwxr-xr-x root shell 230 2013-12-08 14:28 log
[Moto X Original Android Development] natezire71:
Edit: Nevermind, I misunderstood. Give me a few minutes and I'll see what the issue could be.

Edit2: It doesn't look like your "Step 7b" is correct. From my understanding, you ran "Step 7's" command twice. You need to run

echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper

then toggle bluetooth and let it reboot (it will do it automatically). Then after it's rebooted (let it sit for a few), do

adb shell

again, then run

echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper

then toggle Bluetooth again (just like before) and then the phone will reboot. After that, try to install SuperSU.
[Moto X Original Android Development] funnyfarm299:
I wasn't clear. I let it reboot after step 7 as specified in the OP. I then ran it again, let it reboot, and then tried to install supersu.
[Moto X Original Android Development] natezire71:
Yes, you're running the wrong command. At Step 7, there are two different commands you run. From what you've told me, it looks like you're running the same command twice and then trying to install SuperSU.
[Moto X Original Android Development] funnyfarm299:
aaand, it looks like I'm an idiot. Probably would have helped if I had manually typed out the commands instead of blindly copy/pasting. I'm reflashing now.
[Moto X Original Android Development] natezire71:
There ya go. :P Let me know if that did it--because that should have been it.

Edit: make sure you toggle the bluetooth.
[Moto X Original Android Development] ReadyMadeFire:
I know when I performed these steps on my device, I didn't have to toggle bluetooth. When I swiped to unlock phone, the device rebooted at that point.

Sent from my Slapped XT1060
[Moto X Original Android Development] natezire71:
Yeah, I know. I barely had enough time to do it. Doesn't hurt to try though.
[Moto X Original Android Development] ohmimpotence:
I just received my Moto X, never rooted it before. I need to flash back to 4.2.2 in order to get started with this? I'm getting a signature bugs unavailable error so I assume this is the issue. The link for file seems to be down though.

Also how do I find out which file I need

TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_CFC.xml.zip or

TMO_XT1053_4.2.2-13.9.0Q2.X-116-X-17-6_CFC.xml.zip
[Moto X Original Android Development] funnyfarm299:
Didn't work. Here's my output from the command line

C:\Users\Nicholas\Desktop\slap>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.240s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.442s]
finished. total time: 0.682s

C:\Users\Nicholas\Desktop\slap>fastboot flash motoboot motoboot.img
sending 'motoboot' (1588 KB)...
OKAY [ 0.350s]
writing 'motoboot'...
flashing sbl3 ...
flashing rpm ...
flashing tz ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
OKAY [ 4.850s]
finished. total time: 5.200s

C:\Users\Nicholas\Desktop\slap>fastboot flash logo logo.bin
sending 'logo' (2563 KB)...
OKAY [ 0.450s]
writing 'logo'...
OKAY [ 0.952s]
finished. total time: 1.402s

C:\Users\Nicholas\Desktop\slap>fastboot reboot
rebooting...

finished. total time: 0.001s

C:\Users\Nicholas\Desktop\slap>adb push su /data/local/tmp/su
2552 KB/s (104564 bytes in 0.040s)

C:\Users\Nicholas\Desktop\slap>adb push su /data/local/tmp/su
3927 KB/s (104564 bytes in 0.026s)

C:\Users\Nicholas\Desktop\slap>adb push install.sh /data/local/tmp/install.sh
148 KB/s (607 bytes in 0.004s)

C:\Users\Nicholas\Desktop\slap>adb push rec.sh /data/local/tmp/rec.sh
51 KB/s (158 bytes in 0.003s)

C:\Users\Nicholas\Desktop\slap>adb push install-recovery.sh /data/local/tmp/inst
all-recovery.sh
48 KB/s (702 bytes in 0.014s)

C:\Users\Nicholas\Desktop\slap>adb push setup.sh /data/local/tmp/setup.sh
32 KB/s (165 bytes in 0.005s)

C:\Users\Nicholas\Desktop\slap>adb reboot

C:\Users\Nicholas\Desktop\slap>adb devices
List of devices attached
T062804H3Z device

C:\Users\Nicholas\Desktop\slap>adb shell
shell@ghost:/ $ echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper
echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper
shell@ghost:/ $

C:\Users\Nicholas\Desktop\slap>adb shell
shell@ghost:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
h" > /sys/kernel/uevent_helper <
shell@ghost:/ $
[Moto X Original Android Development] natezire71:
Try typing the commands when you do "adb shell". Don't copy and paste.
[Moto X Original Android Development] DogzOfWar:
Just an important heads up. I just got my phone. My phone shipping with the required version of 4.2.2 installed, so it's nice that I can skip that step.

More importantly, the link to http://sbf.droid-developers.org/ghost/list.php is down. I wonder if Motorola took it down? So people, if you downloaded some of those SBF files, don't delete them!
[Moto X Original Android Development] sorullo_xgrx:
If you have a T-Mobile moto X you really don't need this just unlock your bootloader, root and still custom recovery done.
[Moto X Original Android Development] sd0070:
Yeah, I finally just sat down to root and NOPE. Site down. Great.

I usually run into a couple speedbumps when using adb but its not a good sign when its before I even start.
[Moto X Original Android Development] ohmimpotence:
I don't want to unlock bootloader though, then I void the warranty without being able to revert back. If I just root then I can flash back to stock (if i can ever get a copy of stock firmware)
[Moto X Original Android Development] sorullo_xgrx:
Gotcha. I wouldn't mind helping but I only have the Verizon version
[Moto X Original Android Development] ohmimpotence:
I'm wondering if this what I'm looking for http://xdaforums.com/showthread.php?t=2477180&highlight=4+2+2 They claim it can only be flashed with unlocked bootloader though? Not possible to just flash stock using these files with RSDLite I suppose?

It's T-Mobile and the screenshot shows 4.2.2 but apparently there are two different 4.2.2 firmwares, the TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_CFC.xml.zip and the TMO_XT1053_4.2.2-13.9.0Q2.X-116-X-17-6_CFC.xml.zip

Which am I looking for?
[Moto X Original Android Development] cvhovey:
I've not been able to verify the info yet, but I saw a post somewhere today, I think on xda, saying sbf.droid-developers.org had experienced a hard disk crash (actually 2), but they'll be back up at some point when they've fixed things up. If that's correct, better a crash than a crack-down.
[Moto X Original Android Development] enjoimadcow:
Alright I am in a dilemma right now that is most likely my fault. I am rooted using the slapmymoto method on 4.4 att. I next used MotoWpNoMo and somehow softbricked my phone. The problem I am having is trying to perform a factory reset. right now a boot.img is blocking my path. Do i flash with fastboot the 4.4 recovery to be able to perform a factory reset?

edit: I decided to just flash stock. My question is now can I reroot using slapmymoto after flashing back to stock?

edit 2: Also, since links are broken for stock images, if I am allowed, I will rehost ATT_XT1058_4.2.2-13.9.0Q2.X-116-X-17-54_CFC_1FF.xml.zip.
[Moto X Original Android Development] rift999:
So when I finish I get the SU Binaries need to be updated message. I have tried this method 2x. Does anyone know a fix for this? I have been using .5c

Thanks Rift
[Moto X Original Android Development] mercado79:
Have you tried rebooting into "recovery"? If not, do that (which disables write protect), give it a few, and then open up Superuser and try updating the su binaries again.

Sent from my Moto X
[Moto X Original Android Development] rift999:
Yeah I tried that and it failed then too.

I did use "adb shell getprop ro.boot.write_protect" to verify that write protect was off. 0 as expected.
[Moto X Original Android Development] niteglo:
I did the exact same thing, with same result of soft bricking the phone, and flashing stock. However, until this root method is updated, it will not work with our phones since write protection had been disabled. Apparently it can and will be updated so we can re root, but just waiting for now.

I did retry slap my Moto, and while it didn't hurt my system to try, there were multiple steps that couldn't complete. Ended up just leaving the 4.4 stock and will live with it for now.

Edit: additionally, see post 504 for the most recent update on the status of what we're waiting on.
[Moto X Original Android Development] oplix:
what happened to the website? I need to get original ROM. 4.4 Breaks video playback on Moto X. Cannot render 60 fps 720p or 1080p video.
[Moto X Original Android Development] cvhovey:
If I'm understanding correctly, I could still update to 4.4 and root my Moto X (Verizon consumer/retail) that I'll receive via FedEx today, since write protection hasn't been touched as of yet?

If that's the case, then I'd only be partially-rooted ... due to write protection limitations, correct? If so, I'm going to have to decide quickly if I want to even keep this Moto X or sell it new-in-box, since it sounds like fully-functional root would be totally contingent upon an update to SlapMyMoto.
[Moto X Original Android Development] rift999:
Well in theory you should be able to root with SlapMyMoto then use MotoWpNoMo to remove write protection. I haven't been able to get the SlapMyMoto part quite yet but that is my plan. Those people were having problems trying to use SlapMyMoto after removing WP. jcase's program using WP status in order to determine which part of the script it needs to run. If it sees no WP then it assumes an already rooted phone that has been booted into recovery and skips the first 2 steps.
[Moto X Original Android Development] DarthSudo:
As long as your phone has the camera update on 4.2.2, then you can use this method. Just skip step 1, since you are already there. You have write protection off in recovery boot when you want to modify files in /system.
[Moto X Original Android Development] sd0070:
Is there a mirror for the download? Am I unable to root until this one specific link is back up? grr
[Moto X Original Android Development] sheltem:
From the RockMyMoto thread:

Can anyone verify the root check part?

*Edit* Found another source:

https://forums.motorola.com/posts/78f197711d
[Moto X Original Android Development] ohmimpotence:
[delete, misinformed]
[Moto X Original Android Development] MaddHatt3r:
The process needs to be started on the 4.2.2 camera update. This exploit plants the bug in 4.2.2

Sent from my XT1060
[Moto X Original Android Development] h1ghland3r:
Need I to remove RockMyMoto before try this method when I get KitKat? I'm in 4.2.2 + camera update + root by RockMyMoto.
[Moto X Original Android Development] bzwolf:
If you are doing this from 4.2.2, I assume you take the OTA update after Stage 3 (in step 4). But then how do you downgrade the boot loader back to 4.2.2?
[Moto X Original Android Development] rift999:
Just use fastboot to flash the files. jcase has the needed commands listed in the OP.

From the bootloader

"fastboot flash partition gpt.bin

fastboot flash motoboot motoboot.img

fastboot flash logo logo.bin

fastboot reboot"
[Moto X Original Android Development] bzwolf:
Don't I need to obtain those files from somewhere though? I figured they came in that SBF download. Can I back them up from 4.2.2 before taking the OTA? Or am i just missing something completely and can just run those commands?

Thanks.
[Moto X Original Android Development] rift999:
you are right they do come from the camera download. If you need the att ones I have those.
[Moto X Original Android Development] bzwolf:
Nope VZW. Since development on this is on hiatus I will probably just take the OTA, regret not being able to afford the dev version, and settle for stock. :confused:
[Moto X Original Android Development] Rebel908:
I might have done something incredibly stupid.

I've had some issues with some of the mods breaking SystemUI and I've gone back to 4.2.2 and done SlapMyMoto to get back to 4.4. I recently enabled the disable r/w protection Mod that beaups released.

I had another SystemUI problem and went back to 4.2.2 to start the process again a few hours ago. Now I can't replicate the process, because it immediately tells me that the process is on step 3. I managed to flash recovery but I cannot get the final steps to finish, mainly the:

adb shell

echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper

adb shell

echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper

Did I screw something up?
[Moto X Original Android Development] rift999:
you will be able to flash back to 4.2.2 at any time so you won't be stuck

---------- Post added at 04:03 PM ---------- Previous post was at 03:58 PM ----------

With the WP off mod slapmymoto won't work without some adjustments to the program. It checks the WP status to determine which step to use. Thus if WP is disable it skips to step 3 thinking that 1 and 2 have already been completed. I was thinking that it might be possible for someone to change the program so that the user specifies what step they are on.