yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] Dark9781:
I want to test if you already have write protect disabled. Try typing the following command

adb shell getprop ro.boot.write_protect

If it comes back 0 then write protect is already disabled.

If it comes back 1 then make sure you have your firewall and antivirus disabled when you run MotoWPNoMo. If that still doesn't work then you may want to try a different computer.

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
Already did...says 1

I'll disable my AV..I use eset..and its done it b4..

Edit: disabled my AV and firewall... still failed. I'll try to use my wife's file.. I'll have to transfer the files, the site where motowpnomo for download is down right now.

Edit, again: didn't work... any other ideas?
[Moto X Original Android Development] Xenther:
Hey, all. So I've been going through this over the last few days, and I've hit a few snags, but dray_jr has been helping me through a lot of the process. I don't want to keep bugging them, so I'm going to post this up here, because I'm having an issue with this last step of rooting.

I've done everything from downgrading to the 4.2.2 camera update, doing rockmymoto to gain root access, running motowpnomo, and am now working my way through the steps here for slapmymoto. I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.

USB Debugging is on, adb devices shows my phone as being connected correctly

This is a screen cap of what my command prompt shows after I input that command from step 4

http://i.imgur.com/WeekMAf.png

Any suggestions?
[Moto X Original Android Development] xpsychox:
This may be a dumb question..but what's ur AV?
[Moto X Original Android Development] Xenther:
Windows Defender (On Win8.1)
[Moto X Original Android Development] xpsychox:
OK...first get a better AV.. Secondly have u tried to disable it?
[Moto X Original Android Development] Xenther:
Didn't do anything, still same thing. I never disabled my av because while going through to kill write protection, I was able to do it without disabling anything.
[Moto X Original Android Development] xpsychox:
U still may want to try and disable it..I've been having problems completing it too and ppl keep asking me if I've disabled it.. I guess that's the main reason for a lot of ppl for it not working.
[Moto X Original Android Development] Xenther:
I did disable it; it didn't do anything different, as I said. Thanks, though
[Moto X Original Android Development] xpsychox:
Okay, so I just RSD'd back to 4.2.2 again, and regot root, used adb shell getprop ro.boot.write_protect and it did say "0" I installed SU and restarted, and checked it again, it says "1" ...tried to re-run motowpnomo and it errored out again... any ideas?!

Edit: I also put XP virtual mode on my windows 7 pc, same issues... keeps saying error.
[Moto X Original Android Development] Xenther:
Realized a mistake I made, but another issue...

Hey again, all

I realized a little error I was making earlier, that I wasn't running each command from step four as separate commands.

The first two commands run fine, then I get a Permission Denied error when trying to run the echo "/data...." command. I've done everything up until this point, write protect command still shows a 0. Any ideas?

EDIT: Nevermind, got it! Looked through the thread and saw someone suggest going back to 4.2.2 and redo everything. It worked, I'm finally rooted after three days of trying!
[Moto X Original Android Development] syntrix:
VZW:

On the sbf page, there's a"53" version.

Linked in here on the first page, I think I got it as a "57" version.

SBF:

Android 4.2.2

Blur_Version.139.10.53.ghost_verizon.Verizon.en.US

Here:

Yup, it's the 57.

Maybe that's a difference that people aren't noticing, and maybe it makes a difference, maybe not. I was about to flash the "53" version since it matches on the version in the first post here.
[Moto X Original Android Development] Dark9781:
I am out of ideas. The only other thing I can think of is when you flashed 4.2.2 did you let it erase your data?

Sent from my Moto X on KitKat
[Moto X Original Android Development] xpsychox:
yes, i'm going to try something... I saw someone put a post that they used .57 insted of .53 and it worked.. i did the same i got .57 so i'm gunna try .53...
[Moto X Original Android Development] drpencilcase:
i'm stuck on Step 4. It doesn't give me any error message but it doesn't reboot either. I've tried to turn bluetooth on but nothing happens. Did anybody experience similar problem?

Everything went well until then

1.went bavk to OTA(57)

2. installed rockmymoto

3. MotoWPNoMo (adb shell getprop ro.boot.write_protect gives me 0)

4. went back to OTA(57)

5.followed the steps, until it told me to install 4.4

shell@ghost:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
cp /sdcard/install.sh /data/local/tmp/install.sh
shell@ghost:/ $ chmod 755 /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
shell@ghost:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
[Moto X Original Android Development] lowvolt1:
Adb reboot or manually reboot
[Moto X Original Android Development] drpencilcase:
it worked...thanks..I had tried rebooting earlier and it hadn't worked. Anyway, thanks.
[Moto X Original Android Development] phlyphish:
Just to be perfectly clear about this (please bear with me)...

I have a new Moto X and just received the camera patch update, so I'm now on 4.2.2, build number 13.9.0Q2.X-116-MX-17-57-X-1.

So my question is: Since I'm already on the 4.2.2 camera update, can I just start with Step 1 (SlapMyMoto) or do I need to do RockMyMoto and MotoWPNoMo and restore to 4.2.2 first?

Sorry, but I'm just a bit confused because at the beginning of this thread it says,

"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 makes it sound like the very first thing I need to do is use MotoWPNoMo, then use RockMyMoto, then use MotoWPNoMo again and then restore back to the exact same 4.2.2 version that I'm already on. After that, the rest of the instructions (starting with Step 1) seem fairly straightforward.

Sorry if I'm being dense, but that first part hasn't really been made clear yet and I've been going over this thread for the past three hours. I know it's been said that we need to be on a clean 4.2.2 with "write protection" disabled in order to use SlapMyMoto, but is "write protection" different than root? Or are those terms being used interchangeably? Or do I need root, but with "write protection" disabled?

Thanks for your patience and especially all the effort that been put into this rooting process.
[Moto X Original Android Development] dimasp6:
I for the life of me cannot get past the telnet issue.. I've enabled it in win8.1 programs. Turned off the verify usb and apps options with debugg enabled. I start impactor and run the 2222 option, get a quick pop up that disappears on the phone, impactor seems to complete but when I use command: telnet myIP 2222 i get the 'telnet' is not recognized as an internal or external... Somebody please help me understand this.

Edit: Looks like i finally got it.
[Moto X Original Android Development] Dark9781:
If you are on 4.2.2 already you are going to need to run RockMyMoto. This will give you root access. You need root access in order to run MotoWPNoMo. MotoWPNoMo is required if you wish to have root on 4.4 since it will disabled write protection to the system on normal boot. In 4.4 the work around of replacing the recovery with the boot image to disable write protect was patched. After running MotoWPNoMo you will need to flash 4.2.2 in order to have a clean non-rooted device so that the stock recovery is installed and no remnants of root access is left. Once that is done you can start the root process through SlapMyMoto.

Sent from my Moto X on KitKat
[Moto X Original Android Development] phlyphish:
K, thanks for that. Guess I need to do the whole process, but still not sure why it says, "First you must use MotoWPNoMo".

Also, the first paragraph in the instructions creates some of the confusion because it says, "It requires you downgrading to 4.2.2

or

already be on 4.2.2 before updating to 4.4.

I'm "already be on 4.2.2 before updating to 4.4", but I guess it's implied that you must already be on 4.2.2 AND have already rooted AND have already run MotoWPNoMO to disable write protection. At least, I think that's what I'm getting from all of this.

I can see now, where that's pretty much what is implied in the instructions, but those couple of things I mentioned can be confusing to us non-experts coming into this without a lot of rooting experience.

So, to recap: even though I'm already on 4.2.2, but never rooted, I need to:

1. Run RockMyMoto to get rooted.

2. Run MotoWPNoMo to disable write protection so SlapMyMoto can be run later.

3. Flash 4.2.2, which will remove root, but keep write protection disabled.

4. Run SlapMyMoto process beginning at Step1) as defined in the instructions.

Perhaps this was painfully obvious to most, but if that's all correct, then I think I finally understand not only the process, but the why, which, as a programmer myself, is important to me.

Thanks again for your patience and hopefully this will be helpful to a few others as well. I'll update later as to how it goes. :fingers-crossed:

BTW, I got my Moto X directly from Verizon and didn't go through MotoMaker, which is probably why it came with 4.2.2, but without the camera patch update.
[Moto X Original Android Development] gmmurphy:
I believe I have put enough time reading to ask 2 quick questions. I am rooted, WP off, about to flash back to 4.2.2. #1. Whilst editing the XML(VZ) file to flash back to 4.2.2 when the line is deleted it leaves a space, must I delete the space or does it matter? #2. Now, I have the 4.4 update nagging me now, once I flash back to 4.2.2 will that be the update nagging if so is this the OTA I take? Just want to be sure. Thanks for any input.
[Moto X Original Android Development] lowvolt1:
Answer to question #1 is no.

Answer to question #2 is yes

slapped the sh*t out of my X
[Moto X Original Android Development] syntrix:
Nobody really seems to answer the question, so I'll just have to break it down.

I'm on a VZW 4.4, came that way from Moto.

So according to this:

It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.

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.

It's a "root path upgrade", so this assumes that I start on the camera update 4.2.2, right? Ok, if so, then we start on version "57", linked in here:

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

Then we use WPN, then we use Rock, but need Imactor to use Rock.

Here's where nobody really gets it.... at this point we need to flash back to the camera update, which I'm assuming we lose all the WPN/Rock/Impactor work. Yes or no? What is left if there's no CWM?

Assume we have to flash again... 100% flash this:

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

Then go into the slap steps, right? Wrong?
[Moto X Original Android Development] lowvolt1:
Okay. Breaking it down.

1) downgrade to 4.2.2 camera update. .57

2) root using rockmymoto

3) use motowpnomo

4) use rsdlite to downgrade to 4.2.2 camera update .57 again. ( yes you will lose root, but not wp disabled. That is permanent)

5) root using slapmymoto

In the slap process you will be prompted to take 4.4 OTA.

Hope this helps.

slapped the sh*t out of my X
[Moto X Original Android Development] syntrix:
Bam, that's the missing part, thank you thank you thank you!!!! I understand now! I'll give this a try a little later in the evening!
[Moto X Original Android Development] phlyphish:
Not having much luck here. Keep getting an error while running wpbegone. I right click and select Run as administrator and answer the prompts, but when it gets to "Checking for updates", then it says ERROR:Cannot check for updates. Then Press ENTER to exit.

Everything before this went well. I restored 4.2.2 via rsd lite. Then ran RockMyMoto at the end of which, after installing SuperSu, I ran adb shell su -c "id" and got id=0<root> gid=0<root>. It even prompted me on my phone to be allowed in SuperSu. I did grant authority. So I got rooted successfully, but can't get any further.

Before all this I disabled my AV (Avira) and turned off the Windows firewall. USB Debugging is checked on my phone.

Really lost now. Have no idea where to go from here. I already started over and reflashed the 4.2.2 update twice and redownloaded RockMyMoto and MotoWpNoMo and tried them all again with the same results. Running on Windows 7 Ultimate.

I downloaded and flashed http://sbf.droid-developers.org/download.php?device=0&file=55 for Verizon. I also edited the XML to remove the getvar line before flashing.
[Moto X Original Android Development] lowvolt1:
There was another user pretty much having this same issue. he changed computers and toggled MTP to camera and back to MTP and motowpnomo finally took. worth a try. Also make sure the latest drivers are installed.
[Moto X Original Android Development] phlyphish:
Thanks again. Have re-installed drivers a couple of times. I'll try the MTP switch. I freakin hate MTP!

Update:

Still no luck. Guess I'll just be happy with root on 4.2.2 and keep refusing the 4.4 update unless someone has an idea of why I'm getting the Cannot check for updates error, or until something else gets figured out to root 4.4.

.
[Moto X Original Android Development] douglasrac:
I hope this is not an stupid question but: WHY NOT just use the Motorola Bootloader Unlock program?
[Moto X Original Android Development] lowvolt1:
You can only unlock on sprint and T-Mobile.

slapped the sh*t out of my X
[Moto X Original Android Development] holyevilcow:
Sarcastic reply.
[Moto X Original Android Development] douglasrac:
My Moto X is free from carriers. But I still need to root cause I tried Xposed and didn't work.
[Moto X Original Android Development] lowvolt1:
Are you boot loader unlocked?

slapped the sh*t out of my X
[Moto X Original Android Development] douglasrac:
No not yet. I wonder if I do this official motorola thing then all I need is install SU from Play Store?
[Moto X Original Android Development] lowvolt1:
Well, if you can unlock your boot loader, you can flash TWRP then flash SuperSu.

slapped the sh*t out of my X
[Moto X Original Android Development] douglasrac:
What would be the use of TWRP? I need a concept explanation here, as I already know what TWRP do, but I don't have very clear in my mind the point of it. The boot unlocked will allow third part apps to be loaded, so Super SU will be there after installed and rebooted no?
[Moto X Original Android Development] lowvolt1:
To my knowledge you would need custom recovery to flash to flash supersu to system. And if you want to flash Roms. Unlocking the boot loader allows for custom recovery to be installed. So you can flash these things.

slapped the sh*t out of my X
[Moto X Original Android Development] emmanueldmc:
So...what firmware to downgrade my moto x? (for start the tutorial) im actually on 4.4 official tmo.​
[Moto X Original Android Development] dray_jr:
from what i have read you can unlock the bootloader if you like. or follow the guide in the OP

and here is a link to the 4.2.2 camera update for Tmobile

http://www.androidfilehost.com/?fid=23269279319196167

it came from this post

http://xdaforums.com/showthread.php?t=2568334
[Moto X Original Android Development] Tel9000:
Hello, this process worked well for me, but three weeks later, my device is slow and buggy. I would like to do a hard reset, but the normal procedure through settings won't work. How do I do a hard reset?
[Moto X Original Android Development] lowvolt1:
It maybe possible to un-root through supersu. Then do your reset.

Likewise, flashing the stock XML file will surely do it.

slapped the sh*t out of my X
[Moto X Original Android Development] juancaperez2000:
i just try to run it but when the phone is supposed to reboot after take the 4.4 OTA it was stuck on android with red triangle, and show me some times like i have a bad recovery, can somebody help me please
[Moto X Original Android Development] lowvolt1:
What phone?

What carrier?

Were you on 4.2.2 to begin with?

Did you run motowpnomo?

slapped the sh*t out of my X
[Moto X Original Android Development] juancaperez2000:
MotoX

Verizon

From 4.4 rsd lite 4.2 RockMyMoto, MotoWpnomo, Rsd Lite then start SlapMyMoto
[Moto X Original Android Development] lowvolt1:
When you rsd from 4.4 to 4.2.2 did you do a full install? Meaning did you remove the delete data line or any other lines from the XML before flashing? Other than the get-var line.

Did you verify wp is disabled?

slapped the sh*t out of my X
[Moto X Original Android Development] Tel9000:
I flashed the XML file from 4.4 I seemed to have lost root now. Do I have to go through the whole root process again?
[Moto X Original Android Development] dray_jr:
If you don't have a nadroid back up you might
[Moto X Original Android Development] lowvolt1:
Did you run motowpnomo? If you did you only have to run slap.

slapped the sh*t out of my X
[Moto X Original Android Development] juancaperez2000:
I just delete the regular line i guess get-var and yes, i check wp and show me 0
[Moto X Original Android Development] lowvolt1:
Flash back to 4.2.2 and re-do slap. Follow the instructions and run your dalvikvm command three times.

slapped the sh*t out of my X
[Moto X Original Android Development] enkryptik:
Well, sadly I cannot get my Asus G75VW laptop to work with RSD Lite.

I assume the problem is only with RSD Lite because device manager shows it as Mot Composite ADB Interface even in fastboot.

Also, in VMWare with a Windows 7 VM, when i go to connect usb device to VM, it says Motorola PCS XT1060 and Motorola PCS fastboot ghost s when in bootloader. Moto X Toolkit also shows my device in fastboot mode.

I've never had RSD Lite problems before but then again, I was on a Windows 7 and maybe Windows 8 at one point but only USB 2.0 ports.

Guess I'm wondering if I can attain root without RSD Lite...? Already being on 4.4 OTA that is.

I love this phone but this is wearing on me quite a bit.
[Moto X Original Android Development] lowvolt1:
Can't you push the files manually through fastboot adb?

slapped the sh*t out of my X
[Moto X Original Android Development] fndpena:
Looks like I lost motorola recovery after doing RockmyMoto to root the device. Is that a known issue?

I realized that the recovery wasn't there after the phone ended up on a reboot lopp after trying to install OTA update (4.4).

My phone is back to normal after erasing userdata and cache. But the recovery is still lost. Anybody knows how to solve this?
[Moto X Original Android Development] Dark9781:
RSDLite doesn't like USB 3.0. All the newer laptops are coming with USB 3.0. You shouldn't have any issues flashing manually through fastboot.

Sent from my Moto X on KitKat

---------- Post added at 09:06 PM ---------- Previous post was at 08:56 PM ----------

This is a normal part of RockMyMoto. Prior to MotoWPNoMo we had to use this workaround of replacing the recovery partition with a copy of the boot partition in order to boot up with write protection disabled. This workaround was patched in 4.4. If you plan on going to 4.4 with root you should run SlapMyMoto. If you plan to stay on 4.2.2 or just want recovery back go to the following site, download the firmware for your version of the Moto X, and flash the recovery.IMG to the recovery partition.

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

Sent from my Moto X on KitKat
[Moto X Original Android Development] fndpena:
So, if I don't run SlapMyMoto before trying to install 4.4 I will end up on a reboot loop because of the missing recovery. Right?

Is that completely normal? To fix I only need to run SlapMyMoto and try to update again?
[Moto X Original Android Development] Dark9781:
RockMyMoto was designed for root on 4.2.2 and replaces the stock recovery as a workaround since MotoWPNoMo didn't exist at the time. SlapMyMoto was designed to place a backdoor on 4.2.2 that will carry over to 4.4 so you can root your phone since there is no known exploit for 4.4. Just follow the instructions in the OP for SlapMyMoto.

Sent from my Moto X on KitKat
[Moto X Original Android Development] fndpena:
I'm running MotoWpNoMo now and the screen keeps turning on and off after display the message "hmm, hold please".

The last line on the CMD is [******************************************]. How much this takes to finish?
[Moto X Original Android Development] Dark9781:
It takes awhile. Make sure to watch your phone. It will ask for root permission. Also, some had issues if they didn't disable their firewall and antivirus. Some had issues if they let their phone's screen turn off.

Sent from my Moto X on KitKat
[Moto X Original Android Development] fndpena:
Yes. That was the problem. ADB Shell was asking root permission and I didn't knew it was. Now it worked :)

Thanks for all! Im just finishing the MotoWpNoMo and will run SlapMyMoto after that.

---------- Post added at 03:56 AM ---------- Previous post was at 03:49 AM ----------

One last question:

So, SlapMyMoto restores stock recovery in order to OTA update the phone?

[MENTION=1722087]Dark9781[/MENTION]
[Moto X Original Android Development] Dark9781:
Once you run MotoWPNoMo it is required that you flash 4.2.2 in order to start with a fresh, non-rooted phone. When you flash 4.2.2 it will restore stock recovery. After that you can start the SlapMyMoto process.

Sent from my Moto X on KitKat
[Moto X Original Android Development] mercado79:
Don't know why people don't recommend the Moto X toolkit more often.

http://xdaforums.com/showthread.php?t=2477132

You can use that to flash back to stock. Super straight forward. No RSD Lite required.

Sent from my Moto X
[Moto X Original Android Development] enkryptik:
Thanks for all the help and suggestions. I will try these methods as soon as I get some free time. Perhaps Friday night I'll have some time.
[Moto X Original Android Development] fndpena:
But I'm already on 4.2.2, rooted. I did the following:

1) RockMyMoto

2) Tried to install OTA update (without running MotoWpNoMo and SlapMyMoto)

3) Ended up on a reboot loop.

4) Erased cache and userdata to fix the reboot loop

7) Ran the MotoWpNoMo to remove write protection

Now I really need to flash 4.2.2?

I thought I would only need to flash it if I were on 4.4. At least that's what I read in the thread.
[Moto X Original Android Development] Dark9781:
Yes, you need to flash 4.2.2. Root will not survive the OTA update. There is no known exploit for 4.4 therefore SlapMyMoto installs a backdoor on 4.2.2 which carries over to 4.4 allowing you to root. Because you needed to root to run MotoWPNoMo you needed to run RockMyMoto first. Part of the rooting process for SlapMyMoto needs to be done while on 4.2.2. If you try to run SlapMyMoto while rooted it will give you an error that you are already rooted and won't install the backdoor. This is why you need to flash 4.2.2. As I said previously, follow the OP instructions.

Sent from my Moto X on KitKat
[Moto X Original Android Development] fndpena:
Hmmm. I see.

You're right, Jcase mentions that in the OP.

I got a tar.gz for the 4.2.2 update. How do I flash it?

Sorry for all these questions. I'm new on Motorola.