yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] Dark9781:
You will need to unzip the firmware you downloaded and then you can either flash automatically using RSDLite or manually using fastboot.

You can find RSDLite here:

http://www.4shared.com/rar/HkfWKoC5/RSD_Lite_615__MTK_Patch.html

(Note: If your computer is running USB 3.0 then RSDLite will not register your phone.)

If you use RSDLite you will need to remove the following line from the XML file:

If you choose to use fast boot then use the following post as a guide:

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

You can get fastboot by downloading the Android SDK from here:

http://developer.android.com/sdk/index.html

Fastboot will be located in the platform-tools folder.

Sent from my Moto X on KitKat
[Moto X Original Android Development] fndpena:
When I click "Show Device" RSD isn't displaying any info. That's because of USB 3.0, right?

If I'm running usb 3.0 the only way to do is manually?

I've downloaded RSD lite 6.1.6 from xda thread.
[Moto X Original Android Development] Dark9781:
Did you put your phone into fastboot mode? If you did and it is not finding your device you are probably running USB 3.0. The only other route is to flash manually.

Sent from my Moto X on KitKat
[Moto X Original Android Development] fndpena:
As I'm still on 4.2.2. Can I simply restore recovery using:

fastboot flash recovery recovery.img

?
[Moto X Original Android Development] Dark9781:
I may sound like a douche for saying this, you are really not getting this. If you plan to go to 4.4 and have root no. I'm not going to explain why again since I've already stated it a few times and it is stated clearly in the OP how to root for 4.4.

Sent from my Moto X on KitKat
[Moto X Original Android Development] fndpena:
Sorry, I know I'm being a pain in the ass. I thought the step to flash 4.2.2 was only to restore the recovery in order to install the OTA update.

I'll try to flash 4.2.2 manually via fastboot. Thanks.
[Moto X Original Android Development] fndpena:
Finally got it working. Now I'm running a rooted kitkat on my moto x.

Thank you very much for all your help and patience. I was probably too excited about my new phone and wasn't paying attention on the instructions.

Thanks again, and sorry about anything...
[Moto X Original Android Development] wisenick:
Not trying to single you out, but you seem to have a pretty good idea as to what is going on with rooting the X.

I was running 4.2.2 rooted but then attempted to do the update without a recovery (obviously that was my first mistake) and I was stuck in a boot loop so I reverted back to stock through adb fastboot.

Now every time I try to run RockMyMoto it skips to step 3 and never actually installs superuser binaries (at least that's what I'm assuming step 1 and 2 are for)

If I move on to start the "MotoWpNoMo" process it says it is already rooted, however I do not have root permission, just simply that write protection is off. And when I install supersu it says I'm not rooted.

Not sure what to do seeing as every time I restore back to stock it still says that write protection is off and that's probably why it keeps skipping all the important steps.
[Moto X Original Android Development] Dark9781:
You don't run RockMyMoto again. You only need RockMyMoto to run MotoWPNoMo. That is a one time process.

Sent from my Moto X on KitKat
[Moto X Original Android Development] wisenick:
So to make sure I understand what you're saying, you're saying since I already did RockMyMoto and MotoWPNoMo, I should be able to do the "SlapMyMoto" process and the do the ota and I'll be rooted running 4.4?
[Moto X Original Android Development] mj0528:
I flashed rsd twice before I got out of it. You have to erase user data. That was issue anyway.

Nervous to yet it again.
[Moto X Original Android Development] lowvolt1:
I keep getting permission denied on the echo. Any help would be greatly appreciated.
[Moto X Original Android Development] staveandor:
I flashed back up to 4.4. Obviously, I've lost all of the work I had done on 4.2.2 to try to root 4.4. But having a working phone is the goal, for now.

That's where I got stuck, as well. Not sure what to do about it.

Just don't try to downgrade right now; you'll hit a bootloop.
[Moto X Original Android Development] MaddHatt3r:
I can't imagine why the 4.2.2 would not take. Something must not have flashed properly, reboot into recovery and reflash your FXZ is the best I have for you. I had to dust of a LOT of cobwebs to this so try that and if it doesn't work you'll have to wait for someone more skilled/more fresh than I. Open your FXZ and make sure all your files are where they belong (should be 9 files) and the xml only has the getvar line removed. If you need an unmodified copy of the xml let me know.
[Moto X Original Android Development] lowvolt1:
Anyone??
[Moto X Original Android Development] gitku:
same here

Edit: I restarted and did everything over again and it took .. Thanks jcase!!
[Moto X Original Android Development] stonesaber:
I also got the permission denied on the echo command. I went back to 4.2.2 and started over. 2nd time was the charm as I now have root on 4.4 on my VZW Moto X. Thanks jcase!
[Moto X Original Android Development] staveandor:
I'm attempting a downgrade now, since I had an unmodified 4.4 installed.

EDIT:

Did you both have to wipe Data to downgrade?
[Moto X Original Android Development] lowvolt1:
I went back to 4.2.2 as well. 2nd time was not a charm for me.

---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------

Going back to 4.2.2 again. will try it from the top.

Here's to hoping.
[Moto X Original Android Development] staveandor:
Lowvolt, according to users in the IRC, if you've retained data, it will most likely fail.

I'm RSDing to 4.2.2 and wiping everything to start fresh.
[Moto X Original Android Development] MaddHatt3r:
All you need to do to resolve the permission denied is go back to the beginning of step 6. Do an adb reboot, the start with the adb push su...... It went smooth as butter after I went back to the beginning of Step 6.
[Moto X Original Android Development] lowvolt1:
I am not retaining data. Full wipe both times.

Here I go!
[Moto X Original Android Development] staveandor:
I got rid of SLM and redownloaded 0.5c in the hopes that I just had a bad download.
[Moto X Original Android Development] stillthisguy:
For the sake of running into the issue again. Make sure you are using the files from slapmymoto 0.5c and not from 0.5. I would just remove them and then extract again to be sure.
[Moto X Original Android Development] lowvolt1:
Success!!!!!!!!!!!!!!!!
[Moto X Original Android Development] staveandor:
I also had success! I had to run Step 6 a second time, but after I did that, it worked well.

Thank you, Jcase, for this!
[Moto X Original Android Development] MaddHatt3r:
Glad you guys got it working. Congrats
[Moto X Original Android Development] lowvolt1:
Heres a weird thing though.

Root checker shows that I am rooted. However supersu fails to install.

Thoughts?
[Moto X Original Android Development] eyc:
I'm about to show you guys how noobish I am: I can't get into the stock recovery.

1. From off position, I press power+volume down for 3 seconds.

2. Click down to recovery, then press volume up to select it.

3. Green guy with red exclamation point pops up and says "No Command."

4. I tried pressing power, then quickly press volume up for a few seconds. Nothing. If I hold it for any longer, it just restarts.

5. I tried pressing power and volume down, nothing.

What am I doing wrong?

*** Got it. I pressed power and volume up at the same time for 1 second, and it entered.
[Moto X Original Android Development] ericizzy1:
im still getting permission denied after running this: echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper

tried step 6 for 5 times, still no go
[Moto X Original Android Development] Dark9781:
Read and follow the instructions in the OP. The entire process is laid out in black and white. I cannot help someone that can't take the time to read and follow instructions. If you run into errors running SlapMyMoto post and I'll be more than happy to help otherwise the rest is up to you.

Sent from my Moto X on KitKat
[Moto X Original Android Development] wisenick:
I understand your frustration, but I'm not saying I don't understand the instructions. What I am saying is I don't understand how SlapMyMoto seems to work until after I take the OTA. When I try to do the final steps in adb shell, it seems to work, however the device never reboots no matter how many times I toggle bluetooth. And of course, root never sticks.

and what's weird is i can see that the files were pushed to the phone in all the right places, but root still doesn't work, and like I said, it never reboots on it's own.
[Moto X Original Android Development] Dark9781:
You never once said you were stuck on the end part where you toggle Bluetooth. You keep going on asking same questions and then talk about running RockMyMoto again and getting stuck because write protection is disabled. Never once did you say you ran through the SlapMyMoto process and are stuck at the end. Now that you have established that you followed the directions here's what you need to do. Your device may not reboot. If it doesn't reboot in a fee minutes reboot it manually and then install supersu from the play store, run it and update the binary if prompted.

Sent from my Moto X on KitKat
[Moto X Original Android Development] wisenick:
Thanks for the sanity check, I kept forgetting to update the stupid binaries!!!!!
[Moto X Original Android Development] Dark9781:
Sorry wisenick. Reading this half asleep on my mobile. Thought you were someone else asking me the same questions over and over again.

Sent from my Moto X on KitKat
[Moto X Original Android Development] lowvolt1:
Reading through some of these posts, I can't help but notice that some of the folks that come here for help are being treated with what would seem to me to be a bit of a condescending attitude. these people come here for help from us who have already achieved what they want. I for one became a member, so I could learn and teach

No matter how frustrating it can be.

slapped the sh*t out of my X
[Moto X Original Android Development] SYNSYNACKACK:
I believe most of us here are willing to help out those with legit errors or issues.

Those of us rooted are probably a little more experienced.

We take our time, think about what we're doing and realize where we screwed up.

Steps in the OP aren't exactly a step by step. I admit I made a couple stupid mistakes.

However, there are times I get disgusted reading, just seems like the same stupid questions.

Some people don't read OP or give up too quickly.

I am rooted using Win8.1 running Sophos A/V and didn't have to modify my OS for any steps.

Just my two cents.
[Moto X Original Android Development] lowvolt1:
While I would agree that a lot of users don't read the OP. There are still those that don't comprehend fully what they're reading. People learn in different ways. A lot of people need the hands on teaching of others, or just need the comfort of knowing someone is there that they can turn to when and if they get stuck. These forums were put into place as a teaching tool as much as a learning one. People don't want to intentionally pester or frustrate others. Unfortunately that sometimes happens. I remember my first android device and I remember even more clearly bricking it by flashing the wrong ROM. I turned to a forum and received great help from a user there. The least I can do is pay it forward when the opportunities arise. None of us were born knowing how to do this. It takes patience and the willingness to learn. There will always be those that just want the quick " do it for me" method. That doesn't make me any less willing to help them. The ones that show true gratitude make it all worth it.

slapped the sh*t out of my X
[Moto X Original Android Development] dmonleo:
OK......so without PM you.. The OP list the file for AT&T/ VZW. Is there a file for Sprint or T-Mobile? I'm looking for the Sprint one....
[Moto X Original Android Development] lowvolt1:
Are you wanting to root?

If so, and your on sprint. Just unlock the boot loader , flash TWRP, and flash supersu.

slapped the sh*t out of my X
[Moto X Original Android Development] Zeklandia:
Is there any work being done on an exploit that does not require downgrading?
[Moto X Original Android Development] chrisbass:
May I ask why? Just to make it easier? I'm not questioning your mindset about the matter...just curious as to why
[Moto X Original Android Development] Zeklandia:
So

a) less likely to brick

b) no loss of data

and

c) to make it easier to root future updates.
[Moto X Original Android Development] lowvolt1:
http://xdaforums.com/showthread.php?t=2603051

There is a script for root. I haven't used it. Not sure if its easier or not. Also not sure if you have to still downgrade.

slapped the sh*t out of my X
[Moto X Original Android Development] Dark9781:
Yeah. Go to the following site. It has the firmware for multiple carriers.

http://sbf.droid-developers.org/phone.php?device=0

Sent from my Moto X on KitKat
[Moto X Original Android Development] Hammerdroid:
So this method will work to sprint users if we just use our firmware from the link you listed?

Has anyone from sprint confirmed this?

Also, where do I find the method to unlock the boot loader for sprint users?

Sent from my Moto X

-B
[Moto X Original Android Development] Dark9781:
It will work on all versions of the Moto X. If you want to go the route of unlocking the bootloader go to the following website.

https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
[Moto X Original Android Development] clevertrevor777:
Donated!!!

Only hangups I ran into:

1. Activate telnet in Windows: Control Panel -> Programs and Features -> Add or Remove Windows Features -> Scroll down and click the telnet client box.

2. I was trying to run "telnet {ip} 2222" from within Impactor. Stupid mistake - run it in the command prompt

3. Didn't pay attention to the phone during MotoWpNoMo and missed the adb SuperSU request.

Thank you!
[Moto X Original Android Development] mrpopgun:
PwnMyMoto upgrade

My searches are turning up answers I'm sure enough in, so I'm just going to break down and ask.

I haven't looked at XDA for months while swamped at work with Christmas rush preparations. I'm running 4.2.2 that was rooted with PwnMyMoto and I have never installed the camera update i.e. I'm running System Version 139.9.51.ghost_att.ATT.en.US. I now want to get up to KitKat.

The OP starts from a RockMyMoto base, then applies MotoWPNoMo, then restores the camera update then applys SlapMyMoto. Since I'm further back from this, what do I need to do to install SlapMyMoto?

I'm guessing I can apply MotoWPNoMo on my current install, install the camera update then apply SlapMyMoto. Is this safe and workable?
[Moto X Original Android Development] syntrix:
Sounds legit, I was confused on the reflashing, and it's to get you back to the camera update with the read only system disabled, which is sustained after the reflash.

Regardless, you will get through it if you follow the OP's instructions, but you will kick a few things along the way thinking you are stuck, but it will eventually work itself out where it's not really documented.
[Moto X Original Android Development] tgmtzmx:
Any one running into the problem of impactor "signature bugs unavailable" and not being able to get past it to telnet?
[Moto X Original Android Development] syntrix:
I had to disable AV on my PC to get it to work properly, can't remember if that was the error message. disable AV is in the first post, as there are exploits in the packages (obviously)
[Moto X Original Android Development] tgmtzmx:
AV has been disabled so that isn't the problem.

Turned off verify apps in settings as some had suggested when doing RockMyMoto and keeping the screen on to see if any requests popped up and nothing.

Still keep getting the same "signature bugs unavailable" in Impactor.
[Moto X Original Android Development] gunnyman:
Are you selecting telnet from impactors menu or just running it? You have to select telnet
[Moto X Original Android Development] tgmtzmx:
Yup selecting telnet 2222. It gets to testing and then I get the pop up
[Moto X Original Android Development] Dark9781:
Are you on 4.4 or 4.2.2? If you are on 4.4 then that is your problem. The signature bugs were completely patch upon the release of 4.4 on the Moto X. One of the bugs still exist on 4.2.2 camera update.
[Moto X Original Android Development] tgmtzmx:
Still on 4.2.2.
[Moto X Original Android Development] Chronzy:
I had the same error, but I forgot what I did to get impactor working. Don't know if you have already, but make sure to install the telnet service. Provided you are using win7, it's not automatically turned on. I think that might have been the fix for me.

Control Panel->Programs and Features-> Turn Windows features on or off (left side of window). I turned on both client and server.
[Moto X Original Android Development] trrubicon06:
A quick question. I rooted using 1.0 a few weeks ago and everything works fine. I was following the instructions to install safestrap. It said reboot into recovery mode to install. Scrolled down and selected recovery. Upon clicking, it displayed an android on his back saying "no command". Is this because I have no WP now and have no need or is something wrong. Thanks
[Moto X Original Android Development] dicarli:
I'm trying to flash a .zip file but it's only possible with a custom recovery. Is there a way to flash a custom recovery with a locked bootloader? I'm already on 4.4 with SlapMyMoto and MotoWPNoMo
[Moto X Original Android Development] fndpena:
That's true. Mine a had to manually reboot and install super su.

And it worked.

---------- Post added at 08:06 AM ---------- Previous post was at 07:51 AM ----------

I guess you can do this using fastboot.
[Moto X Original Android Development] grifforama:
Hi all. Slapped my Moto some time ago, and have started having battery issues. I decided to do a factory reset, but every time I try from the main menu, it just reboots. It will not reset everything. Can anyone help?
[Moto X Original Android Development] tgmtzmx:
Yup I've got both up and running client and server running already.

This is driving me nuts.
[Moto X Original Android Development] grifforama:
I can also add that I'm unsure I even have a recovery on my phone. If I it recovery, it just reboots. I don't see a recovery screen.
[Moto X Original Android Development] fndpena:
Simply rooting your phone shouldn't give you battery issues.

---------- Post added at 05:33 PM ---------- Previous post was at 05:30 PM ----------

It's because when you run "RockMyMoto" it removes the stock recovery in order to perform root.

To restore the recovery you have to flash 4.2.2 rom using fastboot or RSD Lite.
[Moto X Original Android Development] lowvolt1:
Deleted

---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------

No need to reboot recovery. You have no wp. Just install the .apk as normal.

Slapped the sh*t out of my X

---------- Post added at 08:41 AM ---------- Previous post was at 08:41 AM ----------

Unfortunately, no.

Slapped the sh*t out of my X
[Moto X Original Android Development] cocchiararo:
Flashify maybe? I haven't tried yet tho

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Original Android Development] dicarli:
I already have MotoWPNoMo working. Isn't there an easier way to apply root from 4.4?

Getting back to 4.2.2 is a pain. Have to backup data, apply root, apply OTA, then backup data again, which takes a long time.

Tried flashing a WhatsApp fix libart and it drove me to a bootloop. Had to flashboot to 4.4 again and lost root. I'll have to do everything agaaaaaaaain, damn it! :silly::silly::silly:
[Moto X Original Android Development] lowvolt1:
You CANNOT flash/install or otherwise obtain a custom recovery with a locked boot loader. You maybe able to use safestrap to flash your .zip file.

Slapped the sh*t out of my X
[Moto X Original Android Development] peters4n6:
Has anyone used this set of instructions to root 4.4 ? (based off and credits this thread and jcase) Just seems like a complete soup-to-nuts set of instructions as compared to instructions from the top of this thread referencing rockmymoto and motowpnnomo in addition to Slapmymoto.

I guess I'm a bit of a newb, but I'm having difficulty even understanding from this thread what to do first. Rockmymoto, then motowpnnomo, then slap? The addictive tips link i reference doesn't even pay more than a passing mention to these and seems to focus solely on slapmymoto. Correct?
[Moto X Original Android Development] dray_jr:
Look in the general section for my post how to root 4.4 guides and links it well give you the order to do everything but the order is

1. If not in 4.2.2 camera update then downgraded to it

2. Root 4.2.2 with rockmymoto

3. Disable write protect

4. Reflash 4.2.2 camera update

5. Start following guide in OP

How this helps
[Moto X Original Android Development] grifforama:
It's not just root. I'm having battery issues and I've done a lot of analysis, but came up with no solution but to try a reset.
[Moto X Original Android Development] Dark9781:
The method over on addictivetips is no longer a valid method. They lay out the method that Jcase used while SlapMyMoto was is beta before MotoWPNoMo existed. SlapMyMoto 1.0 simplified the SlapMyMoto method, but added steps to allow MotoWPNoMo to work.

Sent from my Moto X on KitKat
[Moto X Original Android Development] dicarli:
It still works though. Just use SlapMyMoto 0.5c beta
[Moto X Original Android Development] Dark9781:
Oh yeah. It will work fine. Might not be the best route to go though if there are future updates to the OS.

Sent from my Moto X on KitKat
[Moto X Original Android Development] ozg33k:
SO ill have to downgrade to 4.2.2 first? VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip"

then root it, then disable write protect, and then what do you mean by "reflash" camera update? and what do I use to downgrade with this zip file? can i use the stock recovery to install it? and after i root the phone, i just flash it the same exact way i flashed it to downgrade?

Thank you for your time.
[Moto X Original Android Development] syntrix:
You have to start on 4.2.2

Slap won't run if you don't have WP disabled and root, so that's why you flash the second time. DWP sticks on the second flash.

I know, it took me asking about 3 times before someone was able to explain what was not clear in the first post.
[Moto X Original Android Development] ozg33k:
Ahh thanks I get it now.

So I'm guessing the second flash is a dirty flash? No wiping? Just flashing over.._?
[Moto X Original Android Development] syntrix:
I just flashed over, didn't omit anything in the xml file, didn't wipe anything IIRC. There were a few wonky moments, just can't remember exactly where.... like having to wait a while for one of the steps. But follow the steps, and it works!
[Moto X Original Android Development] AdhvanIt:
Since being on 4.2.2 is a prereq for this root, and I haven't bothered to root since the 4.4 update, I'm just now finding this issue. Hopefully someone can help.

When I flash 4.2.2 (camera update) to downgrade, the device gets stuck at boot splash. Typically with other devices I've owned, this is a sign of a bad kernel flash or an incompatible kernel. Though I've run through multiple times and get the same issue every time.

-VZW locked bootloader.

-Flashing using mfastboot for Linux.

-Bootloader and terminal show successful data transfer and flash on all partitions.

-Boot splash just shows the "M" logo without "a Google company" written underneath.

-Flashing back to 4.4 the same way yields no issues.

Any thoughts? Again, keep in mind that I run Linux. RSDLite will not work.

(This is a double post from one in the general section. It was better applied there, but still applies here and figured it'd get more attention.)