yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] enjoimadcow:
Yo Jcase. Thank you for coming through with 1.0. I will try this tonight when I get off work. Thank you again!!!!!!
[Moto X Original Android Development] jcase:
Updated to handle phones that have no write protection (MotoWPNoMo)
[Moto X Original Android Development] sd0070:
How can I get busybox to work? Secure settings says i need to install busybox, but it won't install
[Moto X Original Android Development] tekhna:
Edit--answered my own question. Is there a way to downgrade to 4.2.2 on OS X or is RSD Lite required?
[Moto X Original Android Development] Droidjava:
Power on Greeting?

I have a second moto x arriving today and I've already rooted my first one, but I lost the power on greeting when I flashed back to 4.2.2 for the first moto x. Not that its really a big deal but it would be nice to be able to keep or add it back to the boot screen. Is there anyway this is possible?
[Moto X Original Android Development] bigv5150:
Jcase I have the maxx 4.2.2 and rooted with with write protection permanatly off. To use this exploit should I fxz 4.2.2 and start fresh I would assume so since this is to root 4.4 and I'm already rooted on 4.2.2
[Moto X Original Android Development] jcase:
untested with the droid line, sorry
[Moto X Original Android Development] sorullo_xgrx:
You need write protection off (motoWPnomo)
[Moto X Original Android Development] Einsteindks:
I can honestly say that SlapMyMoto 1.0 works for the Droid line, or at least it did for me. I had WP off, and kept data FXZ for a clean system. With a little help from the newb proof version of rock my moto, I adapted that onto the slap my moto, and it worked. One thing I do need to add to the instructions is to let the phone sit for about 5 minutes after OTA restart. Had the soak gotten to me when they said it would ('early'), I would be pre-FXZ and rooted. Turns out, it came after FXZ reboot, and I couldn't grab the update out of /cache. My Maxx rebooted once, early, during the update. I thought I had failed! But nope, probably just some backup prep work.

fat-fingered and Maxx-ed out.
[Moto X Original Android Development] bigv5150:
what do you mean you had to adapt rock my moto and slap my moto. Did the instructions for the above exploit not work correctly for the maxx.
[Moto X Original Android Development] ManHands:
That first paragraph is confusing the hell out of me.

1) Be on 4.2.2 Camera update

2) Use RockMyMoto to gain root

3) Use MotoWPNoMo to gain write access

4) Restore 4.2.2 Camera update??

Won't flashing the sbf remove root and write access? So then you're moving on to Step 1 of SlapMyMoto w/ an unrooted and write protected 4.2.2?

Honestly, the old 4.4 root method was easier (for me at least).

1) Be on 4.2.2 Camera update (or sbf back)

2) Follow SlapMyMoto instructions to gain root

3) Follow MotoWPNoMo to gain write access

Why the need for the first paragraph? Am I missing something, or did something change w/ SlapMyMoto 1.0?
[Moto X Original Android Development] bliu:
For somebody that's already rooted using SMM 0.5c and has performed WPNoMo, is there a "shortcut" method to have full 4.4? I'll admit I don't understand the technical differences between 0.5c and 1.0. If reverting to 4.2.2 again and running 1.0 is the only way to do it, I will - just hoping for a faster method for somebody in this position. Thanks!
[Moto X Original Android Development] Einsteindks:
The newb-proof RMM uses a small program to start the telnet function connection. All instructions for SMM 1.0 work. I only adapted a technique learned from RMM. SMM zip should be extracted into the ADB folder from which you run the command terminal, for the final step.

fat-fingered and Maxx-ed out.

---------- Post added at 08:13 PM ---------- Previous post was at 08:06 PM ----------

Before taking the OTA, You need WP off before FXZ a clean 4.2.2 in place. You can run WP off after being rooted, so you can do the last SMM advanced shell commands. WP off will survive.

fat-fingered and Maxx-ed out.

---------- Post added at 08:25 PM ---------- Previous post was at 08:13 PM ----------

Use SMM 1.0 with WP off, designed to go together. Just have WP off before starting SMM. In order: 1) be on 4.2.2, (FXZ back -keeping data- via HouseOfMoto). 2) have/be rooted via RMM 3) run WP off exploit. 4)flash stock recovery back on (that RMM wiped). 5) run SMM (allow phone to settle a couple minutes after the OTA reboot before continuing).

fat-fingered and Maxx-ed out.
[Moto X Original Android Development] bliu:
I thought once you already have WP off, it won't turn back on? Can't I just do the following: 1) Fastboot flash 4.2.2 images 2) take 4.4 OTA 3) run SMM

Does that work?
[Moto X Original Android Development] Einsteindks:
No, SMM Runs an exploit while on 4.2.2 that creates a back door. Take OTA during SMM process, after making back door, then end with some ADB shell commands.

fat-fingered and Maxx-ed out.
[Moto X Original Android Development] Ryphez:
I'm looking for this too. Having recovery would be nice, I'm also trying to figure out a good list of why to upgrade and to update the clearer root guide on Reddit. http://www.reddit.com/r/MotoX/comments/1t5ei6/guide_root_verizon_nondeveloper_moto_x_44/

---------- Post added at 05:05 PM ---------- Previous post was at 05:04 PM ----------

From quick reading, you keep recovery with 1.0. Please correct me if I'm wrong
[Moto X Original Android Development] goose71:
Will this survive the 4.4.2 OTA once that rolls out? Only asking since the Moto G is getting that already, I can't imagine us being far behind.
[Moto X Original Android Development] jason.912:
Jcase, where can I send a donation? Paypal/google wallet/bitcoin?
[Moto X Original Android Development] M973:
I believe if you click on the "donate to me" button under his name in the OP there is an option for paypal (that's how I made my donation to him)
[Moto X Original Android Development] ManHands:
Appreciate the response. I think I'm following now. I'm currently rooted w/ SMM 0.5c and WP off w/ MotoWpNoMo on 4.4. I didn't realize that WP off would survive FXZ a clean 4.2.2. So in theory, shouldn't people in my situation simply be able to...

1) FXZ clean 4.2.2 (not worried about keeping data)

2) Follow steps 1-3 in OP to apply SMM
[Moto X Original Android Development] Mayze23:
After about 3 hours of trial and error I finally SlappedMyMoto! :laugh:

Thanks for the time and effort. Donation sent

Confirmation: 5NV215312A955313B
[Moto X Original Android Development] theascended:
If we've achieved root using .5c, is it reasonable to run MotoWPNomo and restore the 4.4 recovery?
[Moto X Original Android Development] enjoimadcow:
Hey on step 4 how long should it take to reboot? I ran the last commands and it seems like it did nothing.
[Moto X Original Android Development] ehusidic:
So, let me get this straight. I have a Verizon version on 4.4. In order for me to root this I have to go back to 4.2.2?
[Moto X Original Android Development] enjoimadcow:
yes
[Moto X Original Android Development] hakoda:
Same here. I ended up reexecuting the last couple of steps and still nothing. Eventually, I rebooted the phone myself which didn't help much.

It seems like I have a partial/broken root as /system/bin/su exists but doesn't want to update in SuperSU and no application will recognize its existence. "adb shell su" gives a permission denied. Any help would be appreciated, hopefully I don't have to do the whole thing over again.

EDIT: /system/bin/su is a symbolic link to /system/xbin/su which has permissions "rwsr-sr-x" owned by root. I'm fairly sure where the "s" character is, there should be an "x" to represent executable permission.

EDIT 2: Rebooted again and the permissions cleared to "rwxr-xr-x" but still no budge.
[Moto X Original Android Development] Rebel908:
Having the same problems. Last few steps won't work. Turning bluetooth on and off doesn't do anything
[Moto X Original Android Development] wwweeesss:
I have a maxx on 4.2.2 already rooted with RMM. Do I need to unroot/go back to stock 4.2.2 image and apply SMM? I'm unclear if there is another exploit used by SMM that RMM does not have and without it I won't be able to re-root on 4.4. I was trying to use HouseOfMoto to go back to stock 4.2.2 but keep my data and having problems, hoping it's not necessary.
[Moto X Original Android Development] sfetaz:
I had the same problem the other two had where triggering bluetooth did nothing and it never rebooted on its own. I just turned my phone off and on manually. However I did successfully install SuperSU, updated binaries and made SuperSU a system app. I have been using the phone for a bit, including reinstalling apps with titanium backup, and have had no issues as of yet with root.
[Moto X Original Android Development] krazyace35:
Ok I ran into a problem on my at&t moto x after running SlapMyMoto and downloaded the 4.4 update the phone just keeps rebooting over and over
[Moto X Original Android Development] hecantbreathe:
So if I'm stock 4.4, I RSD to 4.2.2 camera update, then rockmymoto, motowpnomo, then RSD again to 4.2.2 camera update to start step one?
[Moto X Original Android Development] h1ghland3r:
Yes.
[Moto X Original Android Development] mandrsn1:
You need to put the stock recovery back.
[Moto X Original Android Development] krazyace35:
How do I do that?

Edit: never mind I figured it out I will just do it the way I always did with the Razr HD thanks for your help
[Moto X Original Android Development] wctaylor79:
For anyone curious.. I had previously rooted using SlapMyMoto and was running rooted 4.4. Last night ran motowpnomo and it worked no problem.. Course take no responsibility if someone tries and doesn't work for them, but it did work for me and didn't have to go back to 4.2.2 through RSD before doing motowpnomo...
[Moto X Original Android Development] wwweeesss:
Let me add that other than having root access I am on a stock 4.2.2 image, not a custom ROM.
[Moto X Original Android Development] lowvolt1:
Did you get it figured out?

Same thing happened to me. seemed like the final steps did nothing. I manually rebooted, installed supersu from the play store. opened it up, installed the binaries, and I'm rooted.
[Moto X Original Android Development] Mayze23:
Exactly what I did. I couldn't tell if the last commands did anything either. All I know is that it worked.
[Moto X Original Android Development] enjoimadcow:
Yeah I got it sorted out. Did the same thing as everyone else. Rebooted manually and installed supersu. Everything is running great.
[Moto X Original Android Development] phositadc:
Does this root method survive a factory reset from the settings menu? I like to factory reset every so often to get a clean start and, given the root difficulties on the bootloader locked Moto X, am curious if root will survive a factory reset. Thanks.
[Moto X Original Android Development] enjoimadcow:
I messed up my install with an xposed module and had to factory reset. I retained root with it so I suppose the answer is yes.
[Moto X Original Android Development] piskr:
As the new rooting method retains stock recovery, does it mean that after rooting you can accept any further OTA without modification of the system? And rooting phone also contains CWM or TWRP? Or if not is there any other way to flash zip files and make rom backups? Thanks.
[Moto X Original Android Development] shane1:
I wouldn't attempt the ota. Hashcode updated safestrap to work on KitKat.
[Moto X Original Android Development] zhp pilot:
Where is this?
[Moto X Original Android Development] shane1:
On rootzwiki a tester said 3.65 works on KitKat
[Moto X Original Android Development] ReadyMadeFire:
Has Hashcode acknowledged this?

Sent from my Slapped XT1060
[Moto X Original Android Development] shane1:
I believe he did on twitter
[Moto X Original Android Development] Gilly Monster:
I gave thought to doing something like this. I wish I further knew the ins and outs to exploits. I may give this a shot, not I don't know how to RSD and get back to stock. Done this many a time on my D2, 3, and 4.
[Moto X Original Android Development] lowvolt1:
Motowpnomo will work when rooted 4.4. I used it awhile back. Slap 1.0 is for those who rooted used motowpnomo but had to sbf. Now they can root again.
[Moto X Original Android Development] ReadyMadeFire:
SlapMyMoto 1.0

If I have used SlapMyMoto 0.5 beta, currently running 4.4, and have not used MotoWpNoMo, then what should be the process for using SlapMyMoto 1.0?

The only reason I can see that I need to use 1.0 is to get the stock recovery back after using SlapMyMoto 0.5.
[Moto X Original Android Development] bliu:
I'm still seeking some clarification on having 'full' 4.4 for those of us that used SMM 0.5c and WP off. What is the best path to having 4.4 boot and recovery images?

1) Can we just fastboot flash them since we're rooted with WP off? (Or would we lose root by doing so or miss some other components?)

OR

2) Go back to 4.2.2 and run SMM 1.0?
[Moto X Original Android Development] lowvolt1:
I would recommend option 2
[Moto X Original Android Development] krazyace35:
Still having this same issue. Can someone please help me figure it out.
[Moto X Original Android Development] Dark9781:
If you used SMM 0.5c and MotoWPNoMo you don't have to start from scratch. With SMM 0.5c in order gain WP off you needed to flash a few 4.2.2 files. Those files were gpt.bin, motoboot.img, and logo.bin. All you need to do is flash the 4.4 files along with the 4.4 recovery.img. If you really want to be sure thought you can always start from scratch and use SMM 1.0.
[Moto X Original Android Development] bliu:
Thanks for the info! I'm glad we can just fastboot flash them - much easier/quicker process!
[Moto X Original Android Development] krazyace35:
Ok now I'm no longer rebooting I have wp off and I'm on 4.4 but when I run the last step

adb shell

cp /sdcard/install.sh/data/local/tmp/install.sh

chmod 755 /data/local/tmp/install.sh

Echo "/data/local/tmp/install.sh" > /sys/kernel/unevent_helper

Get this
[Moto X Original Android Development] h1ghland3r:
I'm with SlapMyMoto 0.5, I'll wait until a new update of Android be released to Moto X to try another root process. XD
[Moto X Original Android Development] lowvolt1:
Make sure those files are in your fast boot directory.
[Moto X Original Android Development] krazyace35:
The files are in the fastboot directory I have managed to solve half of the issue I made it all the way to this part

Echo "/data/local/tmp/install.sh" > /sys/kernel/unevent_helper

After entering that it tells me it can't install.sh" > / sys/kernel/unevent_helper access denied

WP is off I double checked it
[Moto X Original Android Development] Dark9781:
Sounds like something did not take during step 2 or Step 3 and that's why you are getting access denied. You may want to go back to 4.2.2 and run those steps again.

Sent from my Moto X on KitKat
[Moto X Original Android Development] krazyace35:
That's what I thought I am going to try again tonight when I get a chance. Thanks for your help :)
[Moto X Original Android Development] Summersett:
I'm on the MAXX, but I was getting that error as well. I tried downgrading to 4.2.2 and got errors , and then tried flashing 4.4 back overtop just to smooth things over and wave the white flag, and got another error about recovery.sh not being as expected. So I'm just leaving it alone now until root is achieved on 4.4 lol.
[Moto X Original Android Development] campzalot:
Just to make sure...

Hey guys,

I just wanted to clarify this: The whole SlapMyMoto process, is it meant for achieving root without unlocking the bootloader??

If so, does the rooting process with an unlocked bootloader just entail installing a custom recovery and then flashing Super-SU through recovery?

Thanks in advance.
[Moto X Original Android Development] rift999:
Correct if you are unlocked then just do it the easy way like you said.

EDIT: Sorry for the additional quotes they have been removed
[Moto X Original Android Development] campzalot:
Both methods void the warranty (in case of the non-dev edition). So why choose one over the other? Is it simply to provide more options of achieving the same goal? Or is it because some network providers just don't let you unlock the bootloader?
[Moto X Original Android Development] rift999:
I don't think it necessarily voids your warranty (don't take my word for that) but many of us are as you said unable to unlock the bootloader. If you have that ability definitely use that route.
[Moto X Original Android Development] digital_cha0s:
Well success after a half day of reading and trial and error.... nevertheless Success! A ton o' Thanks :D

Sent from my Moto X predecessor
[Moto X Original Android Development] lowvolt1:
This is root for 4.4
[Moto X Original Android Development] Summersett:
No, this is root for 4.2.2 with a method to keep root while updating to 4.4. If you're on stock 4.4 there is no way to get root (yet).
[Moto X Original Android Development] lowvolt1:
You are mistaken. Rockmymoto was root for 4.2.2. Even in this thread title it states 4.4 root.
[Moto X Original Android Development] Summersett:
I'll half apologize to you, since I wasn't aware that there was a difference with these root methods between the Moto X and the MAXX. In the MAXX/Ultra OP, jcase states "Unlike hte MotoX, you can not downgrade. This Must be preformed while on 4.2.2 before updating to 4.4." Hence why I'm stuck on 4.4 with WP off and no root.

krazyace35, you should be able to downgrade to 4.2.2 again and get it working.
[Moto X Original Android Development] shaneaus:
I can't get this to work.... I'm on an MotoX(ATT) [locked bootloader] with the OTA 4.4 update. I can NOT downgrade to 4.2. The bootloader verifies all the files when one is attempting to mfastboot or fastboot load them and will not allow most of 4.2 to be flashed...

From the OP "It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4." So, that means with the latest MotoX 4.4 update this is no longer possible.... As it is impossible for me to get to 4.2.2.... (I have tried several different methods)

If anyone knows any differently - please advise...
[Moto X Original Android Development] lowvolt1:
I know on vzw we have to remove the get var line from the XML before flashing. Try that.

Slapped the sh*t out of my X
[Moto X Original Android Development] shaneaus:
I did.
[Moto X Original Android Development] eagle_101:
2 Questions.

1) "First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update."

Why is MotoWPNoMo being used a second time?

2) "SlapMyMoto requires you to be on the 4.2.2 Camera update,"

I have to use RSDLite to downgrade to the 4.2.2 camera update correct? Where would I find the Tmobile update?

thanks
[Moto X Original Android Development] winn75:
Does this work with Sprint Moto X 4.4 too? Do I need to unlocked the bootloader first to use this root method?
[Moto X Original Android Development] eagle_101:
It should work with all variants of the Moto X including the Sprint one and you don't need an unlocked bootloader.
[Moto X Original Android Development] Dark9781:
1. You don't use it twice. Jcase is just stating that before you do anything you will need to run MotoWPNoMo. In order to run it you will need root so use RockMyMoto to gain root and then run MotoWPNoMo.

2. You can either use RDSLite or flash it manually using fastboot. If you are uncomfortable using fastboot I would recommend RSDLite. However, RSDLite does have issues running on machines with USB 3.0 ports. If you decide to use fastboot here is a link on the steps to use.

http://xdaforums.com/showpost.php?p=45809324&postcount=3

You can find the T-Mobile files here:

http://sbf.droid-developers.org/phone.php?device=0
[Moto X Original Android Development] havi007:
I am stuck on the telnet step where I have to put

I got the ip info I am on wifi. I have usb debugging on. I keep getting link failed file exists. Someone please help!!!
[Moto X Original Android Development] mikewelch5:
Sorry if this has been covered I have been looking through all of the pages. But I'm on 4.2.2 Verizon camera update. I have rooted with rockmymoto, just ran MotoWPNoMo succesfully, and when I did step 2 of this process:

Connecting over telnet, and run Stage1 with this command:

Code: dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto

I get the following error: SlapMyMoto does not support rooted devices.

What am I doing wrong?

Thanks and sorry for the noob question.
[Moto X Original Android Development] tacitus54:
Write protection

How do you re-enable write protection in case you need to send device in for repair? Understand that flashing firmware will not re-enable it.
[Moto X Original Android Development] DssTrainer:
Same here.. I am rooted with RockMyMoto on 4.2.2 latest cam patch

I just ran the MotoWpNoMo and that worked fine

Now I am at the Step 2 and after starting telnet with impactor, I get the same error

"SlapMyMoto does not support rooted devices"

Seems a bit odd...

-EDIT-

Ah, I see we have to flash back to stock 4.2.2 patch.... how to do that? using RSD Lite and the latest camera sbf (139.14.1.ghost_sprint.Sprint.en.US) from http://sbf.droid-developers.org/phone.php?device=0 ?

I assume sbf won't wipe my phone?
[Moto X Original Android Development] Dark9781:
To run MotoWPNoMo you need to be rooted. Since you are already rooted there is no need for SlapMyMoto. However, if you plan to go to 4.4 you will need to flash back to stock 4.2.2 camera update and then run SlapMyMoto. If you don't want to flash to stock you could try OTA Survival Mode in SuperSu. However, that feature is part of the pro version which is for sale on the play store.

You can't. This is a permanent change

It will only wipe your phone if you erase userdata. If you run it through RSDLite you may want to remove the following line from the xml file:
[Moto X Original Android Development] mikewelch5:
Ok that is my problem then. Thank you! I plan to go to 4.4 so I need to RSD the 4.2 files, then run SMM? I'll do that now. Thanks for the help!
[Moto X Original Android Development] DssTrainer:
arggg.. read this forum update right before running the command...

Someday devs will mate with proper guide writers and their children will put all this info upfront. Ah well... Luckily I backed up my latest game saves to dropbox

---------- Post added at 12:34 AM ---------- Previous post was at 12:22 AM ----------

what is the correct version for this "stock 4.2.2 with camera patch" ? Seems odd for something so specific we use such a vague reference.

I assume "139.14.1.ghost_sprint.Sprint.en.US" ?
[Moto X Original Android Development] mikewelch5:
I'm honestly not sure I'm on Verizon. But I would say this one..... Android 4.2.2

Blur_Version.139.14.1.ghost_sprint.Sprint.en.US

So yes, the one you said

I just RSD back to 4.2 on my phone in a matter of minutes, ran this tool, and am taking the OTA now. Pretty painless.

---------- Post added at 01:12 AM ---------- Previous post was at 12:52 AM ----------

Ok, I believe I did everything. When I get to the last step of:

adb shell

cp /sdcard/install.sh /data/local/tmp/install.sh

chmod 755 /data/local/tmp/install.sh

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

I typed that in, and toggled bluetooth. But it never rebooted. I manually rebooted, and installed SuperSU from playstore and it seems to be working. That means I'm rooted, correct?

Sorry to clutter this with probably easy stuff to figure out.

Thanks!
[Moto X Original Android Development] tacitus54:
What happened to the flashing recovery.img, before taking the update to 4.4 and then flashing the 4.2.2 bootloader. Can I indeed omit these steps?
[Moto X Original Android Development] sp47:
So i don't need to flash stock back 4.2.2? And can update normally to 4.4? I have pro version of supersu.
[Moto X Original Android Development] DssTrainer:
Same here... I manually rebooted and installed supersu and I also appear to be rooted. I downloaded root checker to be sure and it confirms.

Thanks for the method!
[Moto X Original Android Development] tallgrasshawk:
Is your phone & computer on the same wifi network? Did you run Cydia and it went through?