yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] gmmurphy:
I have read been reading thread after thread. I am about all set to root my VZ moto x. It was shipped with 4.2.2 camera update. I want to be sure my I understand the steps. Seeing I am 4.2.2 can I start with slap my moto, or have to Run RockMyMoto.

MotoWPNoMo then slapmymoto? and if i obtain root will i have to rsd back to take 4.4 update. Should I just take ota 4.4 and root from there? thanks for any help
[Moto X Original Android Development] thrgk:
I just got my moto x, its on 4.2.2 and I want to root it and safestrap it. Should I just follow the OP instructions or should I take all the OTA updates that I can, and then follow the OP instructions? Just a little confused.

Thanks
[Moto X Original Android Development] syntrix:
So just to be clear..

I have to do a bunch of stuff, and then fastboot or mfastboot the older image. Won't that overwrite the prior motowpn and rockmymoto thingy? Or is that a mod that is irrelevant of the flashing and does something underlying?
[Moto X Original Android Development] xpsychox:
ok, I'm SOOOOOO lost.. I've ready thread after thread.. .and I don't know what to do. This is what i've done. I (obviously) have the Moto X, currently running 4.2.2 WITH root access. Used RockMyMoto to do it. Tried to use SlapMyMoto instructions (step 2 says to use RockMyMoto) and I get root. On SlapMyMoto says to take the OTA 4.4 I do and it keeps rebooting, and won't stop. So I use RSD to go back to 4.2.2 Then I got root again (same way) and stop. Now, as I am doing more research I see that you are NOT suppost to take the 4.4 OTA.. I tried to use Moto-Wp-NoMo... I tried to do it on regular boot. failed, tried to power down, and held power and volume down, didn't work. I use Eset Smart Security version 6.0 and I disabled the AV AND firewall.. tried both ways, didn't work again... I really don't know what to do...PLEASE HELP!!!!
[Moto X Original Android Development] stonesaber:
After you gain root on 4.2.2 camera update and then use motowpnomo then you have to go back to 4.2.2 camera update again and start there with a fresh unrooted, stock phone. Then follow the guide. The 1st post states that you must be on a clean 4.2.2 for this to work.

Also, if you get to the last step and your phone doesn't reboot, manually reboot it and you should have root.
[Moto X Original Android Development] Icon000:
Here's what Happened:

1. Rooted 4.2.2

2. Ran MotoWPNoMo

3. Ran SlapMyMoto and take OTA

4. Permission denied on

5. 4.4 Root Failed

6. RSD back to 4.2.2 Attempt root again

7. On round 1 of RockMyMoto I get this message

8. Attempt to install Supersu and get message

9. Spent past 2 hours in thread reading from 12/1 [ Date MotoWPNoMo was released] and found no solution to my problem

The only recommendation for this problem that I could find was to Flash 4.2.2, reroot and rerun MotoWPNoMo and to continue with the instructions on how to root 4.4. I've been unable to achieve root in 4.2.2 now.

I'm at a loss of what to even do next. Thanks in advance for any help.

If [MENTION=1722087]Dark9781[/MENTION], [MENTION=4520932]lowvolt1[/MENTION], and or [MENTION=3640868]Einsteindks[/MENTION] could help that would be great. I've seen your name all over this thread.

[MENTION=2811771]havi007[/MENTION], I think we might be having the same if not really similar issues. Hope people answer and this helps.

Also what does FXZ & sbf mean?
[Moto X Original Android Development] havi007:
I got it figured out. I ran into the same thing. Except the system is not write protected message.slapmymoto has to first work. Try putty for telnet stuff i think is what its called that helped me. After that I had to flash 4.2 about three times to get root access
[Moto X Original Android Development] lowvolt1:
I can help you in a few if you still need it.

Slapped the sh*t out of my X
[Moto X Original Android Development] Icon000:
That would be amazing thank you.
[Moto X Original Android Development] Einsteindks:
After you rooted 4.2.2, you had no stock recovery. It was hijacked for write protection off. You need to put back the stock 4.2.2 recovery. Can be done either before or after MotoWPNoMo, but must be in place before running any SMM step.

FXZ and sbf are used somewhat interchangeably, but are different files. Sbf, or single binary file, is what they used to be known as. FXZ Is what they are called today. More technical in nature, and they do more when being flashed. I don't know what those letters stand for, though.

fat-fingered and Maxx-ed out.
[Moto X Original Android Development] Icon000:
How do I put it back? With adb? RSD?
[Moto X Original Android Development] xpsychox:
Sbf is the original and fxz is what u do with rsd... Same thing it means to reinstall the is with rsd
[Moto X Original Android Development] lowvolt1:
You stated earlier that you already ran motowpnomo. And that when you tried to use rockmymoto it told you that you were not write protected.

The reason you have to use rock is to run motowpnomo. You have already achieved that. You don't need to use rock again.

Just flash back to 4.2.2 camera update if not already on it and then run slap.

Slapped the sh*t out of my X
[Moto X Original Android Development] xpsychox:
U just contradicted ur self.. U just added to the confusing list... I am on 4.2.2 now I have root access again I tried to usemotowpnomo and it failed..
[Moto X Original Android Development] Icon000:
Does it matter that I don't have root now? Also last time I ran the command I got a permission denied. What should I do to make sure that doesn't happen again.
[Moto X Original Android Development] Einsteindks:
Hopefully, the Kit Kat update failed completely, and you still have a somewhat stock 4.2 .2. I'd first try using HouseOfMoto, and full flash (both stock system and recovery) keeping data. Write protection off will still stay, but you will be unrooted. That's okay, because the first part of SMM puts a backdoor access for root onto 4.2 .2. Then run the OTA from your stock recovery. It should boot once early, then finish off the update for a while. Let it settle a few minutes, then finish SMM, running the adb commands from a terminal (where you should also have placed the files from the SMM download) reboot manually, install supersu, update the binary.

I'm no super techno guru, but I fudged my way around here often enough to get a pretty good idea of what should be done, and when. If this fails, you'll have to install KK, and not have root. If you want, you can simply reroot after HouseOfMoto, And restore the recovery using fastboot commands, freeze the Motorola update program, and just wait until someone comes up with a pre-rooted KK FXZ.

fat-fingered and Maxx-ed out.
[Moto X Original Android Development] Icon000:
When you say HouseOfMoto do you mean RSD? I just ran SMM and will be apply the OTA soon.

Thank you again for this help. Even if you aren't a "Super Tech Guru" you're still doing a lot of good.
[Moto X Original Android Development] Einsteindks:
You can't reroot once you have write protection off, and you can't turn write protection back on so that RMM will run. That's okay, because you can still flash a clean system and recovery onto the phone, and the first operation in SMM will set the phone up to have a root done after OTA

fat-fingered and Maxx-ed out.

---------- Post added at 01:26 PM ---------- Previous post was at 01:23 PM ----------

I suppose you could RSD without using HouseOfMoto. RSD is an option in HoM. I like HoM because it also has a built-in option to keep your data!

fat-fingered and Maxx-ed out.
[Moto X Original Android Development] Icon000:
Is HouseOfMoto another program or something?
[Moto X Original Android Development] lowvolt1:
I'm telling you, you have already done some of the process. Now just flash back to 4.2.2 if not already on it and run slap.

Slapped the sh*t out of my X
[Moto X Original Android Development] Einsteindks:
Yes, one of the originals, I guess you could say. There are directions included. Follow them carefully, and it will work. Stay calm there, it'll get slightly involved, but not computer-sciencey.

fat-fingered and Maxx-ed out.

---------- Post added at 01:45 PM ---------- Previous post was at 01:35 PM ----------

I've been admittedly a little cheap when it comes to donating to these magnificent developers. Tight domestic budget, and all. I figure I can pay them a little bit in some way if I field some questions for them. I certainly hope they correct me if I'm ever (hugely) wrong. I got a little lucky with the KK soak. I took some safe risks, but I also did some research. Hell, okay, a LOT of research.

fat-fingered and Maxx-ed out.
[Moto X Original Android Development] xpsychox:
Help..please? Lol.. I adb pushed pushed slapmymoto and then used rockmymoto to get root on 4.2.2 now how do I get back on 4.4 and keep root?
[Moto X Original Android Development] lowvolt1:
You can't. You have to root using rockmymoto then run motowpnomo then flash back to clean 4.2.2 then root using slapmymoto

Slapped the sh*t out of my X
[Moto X Original Android Development] Einsteindks:
Wrong order.

Start with your/any 4.2 .2.

Root with RockMyMoto (newb-proof version for Windows).

Run MotoWPNoMo.

Flash clean stock system&recovery with HouseOfMoto.

Run SlapMyMoto.

Reboot manually, install supersu, update the binary.

Detailed instructions for each exploit is found in their respective original posts. Some OTA downloads may be corrupted. As always, your phone your risk. I'm just telling you the way I did it. If something gets screwed up, you'll be stuck with having to install Kit Kat ( understanding string theory may be easier, but it is possible.) and not having root

fat-fingered and Maxx-ed out.
[Moto X Original Android Development] dhoppy:
lost root?

I rooted my phone on the first or second day of SlapMyMoto (version .4 or something), and I just noticed that the su binary is missing. I hadn't needed to use root (although it was working, I have used titanium and root explorer). Today I wanted to try a screen recording app that needs root and wasn't able to. SuperSU tries to update but says "installation failed."

Has anyone else experienced this?
[Moto X Original Android Development] lowvolt1:
You need to "reboot recovery" by powering down phone and holding power and volume- until fastboot shows up. Navigate to recovery with volume- then use volume+ to select. Your device will boot normally but with write protection disabled. Then update supersu binaries.

Slapped the sh*t out of my X
[Moto X Original Android Development] dhoppy:
Awesome, thanks for the rapid help!
[Moto X Original Android Development] stonesaber:
I didn't contradict myself. Read the OP. "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."

This is exactly what I did with no problems.
[Moto X Original Android Development] xpsychox:
U said u need to gain root on 4.2 then use motowpnomo then go back to 4.2 with no root fresh copy..
[Moto X Original Android Development] lowvolt1:
This is correct. You need to start on 4.2.2 camera update. Root with rock. Use motowpnomo. Flash back to clean 4.2.2 camera update then root using slap.

Slapped the sh*t out of my X
[Moto X Original Android Development] winn75:
Is there a simpler way to basically just root 4.4 Sprint Moto X.
[Moto X Original Android Development] lowvolt1:
Unlock your boot loader, flash custom recovery, flash supersu

Slapped the sh*t out of my X
[Moto X Original Android Development] winn75:
Any one-click root method?
[Moto X Original Android Development] lowvolt1:
Nope.

Slapped the sh*t out of my X
[Moto X Original Android Development] jtc276:
Two questions that I'm probably going to look stupid for asking.

1. Can I do this on the GSM variant (T-Mobile). I know I can unlock the bootloader straight from Moto, but I really don't want to wipe my device unless I absolutely have to. Which brings me to my second question.

2. Does this wipe your device?
[Moto X Original Android Development] Dark9781:
1. Yes you can.

2. It won't wipe your device if during the flashing steps of 4.2.2 you decide not to wipe your data, but you may have issues if you chose to keep your data.

Sent from my Moto X on KitKat
[Moto X Original Android Development] ckelly33:
I have a Moto X that I bought for my daughter who didn't want it. I cannot decide if I want to return it to Motorola or trade it for my Galaxy S4 and use it for myself. Doing some quick reading on rooting, etc. and have a question or two.

As opposed to the S4 with it's TW, I don't see alot off the bat I want to change about the X. However, I do want to 'reserve' the ability to make changes in the future - so maybe root but run stock for now. Reading the OP, it looks like steps 1-3 are getting it back to the point where my phone is now (ready to accept the 4.4 update, and nagging me to do it). I haven't accepted the update yet because I want to root (once I decide if I am keeping the X).

Should I then just go ahead and accept the update then start at step #4 or is there a better root method for me (pre-KitKat)?

Thanks
[Moto X Original Android Development] jtc276:
Just to make sure. It's not going to wipe my data even though I have to revert back to 4.2.2? And I'll need to download the GSM firmware instead of AT&T and Verizon firmwares linked in the OP, right? Thanks again!
[Moto X Original Android Development] syntrix:
This is the same question I had, but asked in a different way many pages back, didn't get a reply.

If you flash back to the old update, then why do you do the prior steps? Won't they be wiped out when you go to the older camera update?
[Moto X Original Android Development] dray_jr:
if i understand what your asking you have to push the files over to your phone before you update and run the telnet commands, then you can update

but if you are allready rooted with custom recovery you have to restore to stock first because the update wont take with a custom recovery.

if i am not understanding the question correctly explain more and ill see if i can help
[Moto X Original Android Development] stonesaber:
If you want to root, I would go ahead and do it now then run MotoWpNoMo to kill write protection because in order to root on 4.4 you need to complete those steps anyway.

So, lets say you take the update to kitkat and then decide to root.You have to go back to the version you're on now, then root, then run MotoWpNoMo, then go back to 4.2.2 camera update and start SlapMyMoto 1.0 from there. The reason you need to do these steps is to permanently kill write protection so you don't have to boot into recovery when you want to change something that requires wp to be off. So, it makes no sense to update to kk now if you want to root. If it were me, I'd root now. I hope this answers your question and didn't confuse you even more. Some people have had a hard time grasping some of this.
[Moto X Original Android Development] ckelly33:
I guess the question is: is it better to take the update

then

do steps 1-3 OR is there a different (or better) root method for whatever firmware I am currently on (MSM8960PRO_BP)? Or does it even matter?

I just don't want to be in the Galaxy S4 predicament where if you don't root prior to a certain baseband then you are limited in what you can do. I have no plans to run anything but stock at them moment but I don't want it to be "too late" if I decide that I want to flash a custom recovery or custom ROM in the future.

Does that make sense?
[Moto X Original Android Development] dray_jr:
you have to do step 1-3 before you update to 4.4 in order to root and there is no other root method as of right now for 4.4

but if you update to 4.4 and dont root it you can still use RSD to downgrade back to the 4.2.2 camera update and then follow the guide to achieve root
[Moto X Original Android Development] gigawatt:
followed steps and when update was applyed I got bootloop, and flashed back to 4.2

Hi, I was originally on 4.2.2 and did things in the following order

ran rock my moto through all of the reboots, and installed supersu and had root.

then ran motowpnomo and it completed successfully.

then ran slap my moto and went through all of it's steps.

then took the update.

when the phone restarted to apply the update, it would come up with out applying the update, and after about ten seconds, it would say shutting down.

So, I flashed back to 4.2.2.

But now when I run rock my moto, it starts at step 3.

Is there a solution?

Because when I run

adb shell getprop ro.boot.write_protect

it shows 0

but when I run

adb shell su -c "id"

it says it's not rooted.

So, I know I'm doing something wrong.

I also used Motorola fastboot and wiped cache and user data.

thanks

Isaac the blind guy
[Moto X Original Android Development] Dark9781:
After running MotoWPNoMo it is required to flash 4.2.2 again. You did that after getting stuck in a boot loop. Now that you are back on a clean 4.2.2 you can skip running RockMyMoto and go straight to SlapMyMoto since write protect is already disabled. RockMyMoto will look for write protection. If it sees its off it will not run the first 2 steps because it thinks it already has.

Sent from my Moto X on KitKat
[Moto X Original Android Development] gigawatt:
rock my moto skip

Hi, so since write protection is off, if I just go to slap my moto, after it reboots twice, do I then take the ota, and can I instead of taking the ota just use the files in fast boot, and then, how do I install the su binary again, since it's not installed
[Moto X Original Android Development] Dark9781:
You would take the ota and finish the steps for SlapMyMoto. SlapMyMoto installs a backdoor on 4.2.2 that allows you to gain root access on 4.4. If you try to use fastboot you will erase the backdoor when you flash system.IMG.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
OK...so if I'm understand what uve said u use rockmymoto to get root then the motonomo to wipe wp perm. Then re red back to clean 4.2.2 then use slapmymoto to take 4.4 kk update while still having root?

If correct, I've done all that but motonomo won't run on line says error each time..should I just rsd back tob100% stock no root 4.2.2 and start again? Thanks for The help!!
[Moto X Original Android Development] dray_jr:
My bootloader is unlocked and I was all ready on the 4.2.2 update rooted so all I did was restore to stock and start at the step of pushing the slapmymoto jar and just kept going from there
[Moto X Original Android Development] a1exus:
Can I do factory reset and keeping root? I'm on 4.4
[Moto X Original Android Development] Dark9781:
Partially correct. You use RockMyMoto on 4.2.2 to gain root and then run MotoWPNoMo. You only need to do this if you haven't successfully ran MotoWPNoMo already. After you have write protection disabled you will flash 4.2.2 again in order to have a clean, non-rooted 4.2.2. Then you will run SlapMyMoto according to the instructions Jcase layer out in the opening.

Can you provide some more info on what you did?

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
Basicly what u said.. I had 4.4 used red to go back to 4.2.2 and used jcases directions for adb push of slapmymoto and got root access with rockmymoto I found out I needed to usemotowpnomo so I tried.. I was on fastboot option it failed so I tried with the phone booted like normal and it fail as well.
[Moto X Original Android Development] Dark9781:
The phone is going to need to be booted up. After gaining root with RockMyMoto did you install SuperSu and then reboot into recovery to update the su binary?

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
Super auto installed from marketplace..and no I didn't boot into recovery.. So just hold vol down button and power and click recovery after I do clean install and regain root? Then what?
[Moto X Original Android Development] Dark9781:
It will load up with write protection disabled. This is a work around originally used to gain root access to the system. You will now need to update the su binary and then boot back up into normal mode. After that run MotoWPNoMo. Make sure to watch your phone while you are running it. Your phone will ask you to give adb (MotoWPNoMo) root permission. Once it runs through you will now have permanent write protection disabled in normal boot. Then follow Jcase's instructions for SlapMyMoto.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
Ok...so since I've got root..should I just do a clean 4.2.2 install and start again or just continue from where I am since I already rooted..

Edit: I just tried to go into recovery, it just shuts off and does nothing. and if i try again and hit volume up key, it boots like normal.
[Moto X Original Android Development] Dark9781:
Since you are already rooted through Rock you can just continue. Run MotoWPNoMo and then flash 4.2.2 to start the Slap process.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
you said i needed to into recovery to run motowpnomo.. but when i try to go into reovery, i hit power (habbit from droid razr) and it shuts down, if i hit power up key, it boot normally.
[Moto X Original Android Development] Dark9781:
The recovery partition is hijacked. Thus why I said it was a work around. It will appear to be booted normally, but it isn't it will boot your phone up with write protection disabled.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
but every time i've tred to run motowpnomo it says error.. i even just tried it again after i hit volume up key fro recovery...?!
[Moto X Original Android Development] Dark9781:
Did you update the su binary as instructed? Also make sure you have USB debugging mode enabled in developer options.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
I did go to marketplace and saw that SU wasn't installed, so I installed it, and doubled checked that i still had root access, i do.

if that's not the su binary, then what is? (been too long since i've had to f with this)
[Moto X Original Android Development] Dark9781:
As I said before. Boot into recovery. RockMyMoto hijacks the recovery as a work around to disable write protect to the system. It will appear that your phone booted normally, but it hasn't. You can not update the su binary in normal boot due to the system being write protected. To update the su binary open SuperSu. A box will appear asking you which method you want to use to update su. Choose normal. Now su will be updated. Now boot back into normal boot. Make sure you have USB debugging enabled in settings>developer options and then run MotoWPNoMo.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
ok, held vol down button, highlighted recovery and hit vol up on recovery, it booted, opened SU, didn't ask for update.
[Moto X Original Android Development] Dark9781:
In that case it should already be up to date. Just follow the rest of the instructions and make sure USB debugging is enabled.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
still had an error...
[Moto X Original Android Development] Dark9781:
I need some more info then. What OS is the computer you are trying to run this on? Do you have all the moto drivers installed?

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
ok, this is gunna get confusein... I have a mac computer running windows 7 32 bit (NO IOS all windows) I have the newest version of RSD, i should have the newest moto drivers..but i'm also chcking as i type this now, just to make sure. I have the ADB drivers installed as well.

Edit: yes, i have latest Moto drivers.
[Moto X Original Android Development] Dark9781:
Are you able to run ADB commands? Can you open and ADB shell?

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
yes, I can, I am able to open cmd and type any adb shell commands. (I set it up so that any time i type adb it auto searches my pc and finds the file of where the adb is)