yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] mpetruzz:
I'm rooted with rockmymoto on 4.2 and ran the script to disable write protection.

Not sure what to do now. Do I take the update and then run slapmymoto??
[Moto X Android Development] stillthisguy:
Just use the toolkit and do option 11 for slapmymoto, option 1 to start. When asked about root for first time, say no, then when asked if motowpnomo was successful say yes, then follow the rest of the prompts.
[Moto X Android Development] mpetruzz:
So that will work and update to 4.4 even though I'm on 4.2??
[Moto X Android Development] stillthisguy:
It will continue to get you through the process. You still need to have 4.2.2 reflashed, then the first part of slapmymoto then update to 4.4 ota, then the 2nd part of slapmymoto. But like I said, just follow what the toolkit says and it will get you there.
[Moto X Android Development] mpetruzz:
OK cool. I'll go through the next steps tomorrow and report back. Thx
[Moto X Android Development] ijeenyus:
I have same situation, but when I use option 11; I get the following screen and toolkit crashes. I've also downloaded the correct files into its perspective folders, do you have any suggestions?

Edit: same issue when I'm on 4.2.2
[Moto X Android Development] stillthisguy:
Uninstall the toolkit, and then download it again and install it.
[Moto X Android Development] ijeenyus:
Thanks!! Can confirm this method gives root on 4.4 for Verizon Moto X. It's not much, but donation confirmation 3E76598286911064N
[Moto X Android Development] mpetruzz:
Finished up this am and am happy to report that I'm on 4.4 and rooted!!! Thanks so much for this tool. I was a bit nervous to go through the steps prior to the toolkit.

The only hiccup I had was that I needed to manually copy the RockMyMoto files to my phone, the toolkit wasn't pushing them. Not a big deal at all, it just took me a bit to figure out why it wasn't working.
[Moto X Android Development] stillthisguy:
Glad that it worked for you.
[Moto X Android Development] mskks64:
I went through the entire process yesterday, and it worked I accepted the update to 4.4 but then forgot what I was supposed to do after that. What do I do? Thanks! I thought I was supposed to install SU from the playstore, but I don't think that worked.
[Moto X Android Development] jtseals:
im not completely understanding this I have rooted successfully on 4.2.2 I ran thru as administrator for the motowpnomo successful with that i go back into the tool kit to use slapmymoto but i get an error saying dont have necessary files in the motowpnomo folder you will need to download motowpnomo zip file and place it in the motowpnomo folder I guess im a little lost cause i already downloaded that program any help thanks

---------- Post added at 11:22 PM ---------- Previous post was at 11:16 PM ----------

or do i not even need to use slapmymoto and just go ahead and take the 4.4 ota update
[Moto X Android Development] bolo808:
I also have this problem when I tried option 11. Everything was going well and then after it booted my device into fastboot mode, it went to writing 'system' and it was stuck there. I left it for about 30 minutes before stopping the toolkit. Does the writing system process take longer than that?
[Moto X Android Development] mpetruzz:
During a few of the steps the script wasn't pushing the files to my phone so I had to transfer them manually. And make sure you type the command exactly as written.

Once I manually transferred them I had 0 problems.
[Moto X Android Development] jtseals:
i have typed every command exactly as written when i go back into slapmymoto which is option 11 then i hit option 1 to start the process does a couple of things really quick then pops up with that error i said in the previous message im a little confused on how im suppose to do what that error message says that error does not really make sense

---------- Post added at 08:43 AM ---------- Previous post was at 08:37 AM ----------

it wants me to put the motowpnomo zip file in the motowpnomo folder where is this folder located
[Moto X Android Development] stillthisguy:
After taking the 4.4 update, there was still part of the slapmymoto process left. If you finished that as well, then after the reboot you would install SuperSU and you would be good to go.
[Moto X Android Development] stillthisguy:
The toolkit checks to make sure you have all needed files in their respective folders, in case you have run them before. So just move the motowpnomo .zip to that folder and it should run fine. If you have already successfully used motowpnomo, when you start the process, and it asks if this is the first time, say no, then when it asks if you have successfully run motowpnomo say yes, and it will guide you through the rest of the process.
[Moto X Android Development] jtseals:
I understand that but I dont understand where that folder is located or should be located
[Moto X Android Development] stillthisguy:
As seen in the screenshot, it took about 50 seconds to send the first part of system, and then just over 62 seconds to write then it sends the second part which only took about 5 seconds, and it shouldn't take much longer than that to write it. Not sure why it would stop working when trying to write. I would use option 8 to Return to Stock, then start the process over.
[Moto X Android Development] stillthisguy:
Depends on what OS you have, but it will be either of these two places.

x32 - C:\Program Files\stillthisguy\Moto X Toolkit

x64 - C:\Program Files (x86)\stillthisguy\Moto X Toolkit
[Moto X Android Development] jtseals:
oh yeah should of known that anyway thanks and all report back
[Moto X Android Development] jtseals:
well that did get it to do some more stuff but now im having other issues im going to start all over and then see what happens
[Moto X Android Development] jtseals:
Once your phone has booted and you have skipped through the setup

you will need to enable developer options, and then enable usb

debugging.

Once usb debugging is enabled, press enter to continue.

This could take a moment. Please be patient.

List of devices attached

T062804KOS device

'CHOICE' is not recognized as an internal or external command,

operable program or batch file.

You need to get usb debugging fixed before proceeding. Try

unplugging then plugging your phone back into the usb cord.

Press enter in the toolkit after unplugging and plugging in

your phone.

this is whats happening now this is right after im in slapmymoto and it asks me to enter 1 for verizon then shows build number and has me enter the build number twice then enter 1 again for verizon then does a bunch of stuff when booted into bootloader that finishes and phone reboots then says press enter once usb debugging is enabled this has happened twice now sorry for such a long post but want to be on point with the issue help would be great thanks
[Moto X Android Development] stillthisguy:
Thanks, I will take a look at the script and see what I can find.
[Moto X Android Development] nevrozel:
Hi guys,

I have this problem:

- ATT 4.4 Moto X stock

- all files are in correct places

- I start rooting, confirm ATT and first time and 4.4

- I think it installs 4.2.2 and then reboots

- Then it tells me to wait for boot, enable developer options, debugging, and then press enter

The problem is its stuck at the Motorola logo at boot. Whatever I do (reboot in recovery, restart, etc) it always gets stuck here. So it never booted after the first step.

What should I do?

Thanks.
[Moto X Android Development] stillthisguy:
How did you answer the questions at the beginning of the process?
[Moto X Android Development] jtseals:
i never saw the questions that i think your talking about
[Moto X Android Development] stillthisguy:
pm sent
[Moto X Android Development] stillthisguy:
I would suggest booting to bootloader, then running option 8 to return to stock. You can choose to go back to 4.2.2 and then it should boot. Skip through setup and then enable usb debugging and try again.
[Moto X Android Development] nevrozel:
OK just did that and I am back on 4.2.2 camera update. Now what should I select for root process? Option 9,10 or 11?
[Moto X Android Development] TheBurgh:
What steps are recommended if I am on 4.2.2 rooted and want 4.4 rooted?
[Moto X Android Development] nevrozel:
+1
[Moto X Android Development] stillthisguy:
Option 11 again. Just answer yes to first time root 4.4.
[Moto X Android Development] stillthisguy:
If you are 4.2.2 rooted, it will depend on if you have ever run MotoWPNoMo before. If you are on 4.2.2 rooted and have successfully run MotoWPNoMo then you use Option 11 for SlapMyMoto, then answer the first question No and the 2nd question Yes. This will take you to the part of the script that will re-flash 4.2.2 then run you through the slapmymoto parts of root. If you are 4.2.2 rooted but haven't run MotoWPNoMo then you would answer the first question No and the 2nd question No. This will take you to the part of the script that will have you try and run MotoWPNoMo again before continuing.
[Moto X Android Development] bolo808:
Thanks for getting back to me and great job on the toolkit! I noticed that too for the time it took for the first system write which is why I knew after 30 minutes it was way too long. I also did what you said to return to stock and start over but unfortunately it still gets stuck at that same point. I actually got stuck in multiple bootloops since I had to stop the process but for some reason by restoring to stock and stopping the process at the writing 'system' point, it seems to fix the bootloop and I can get back into my phone as if nothing ever happened. I'll try to see if I can figure out what's going on and post back.

EDIT: So I know I've seen this before but I didn't think it was affecting me but I was able to successfully complete writing 'system' by switching to a USB 2.0 port. I was using a 3.0 port, stupid me. But after hours of trying, things have finally been working and I'm just about to finish by gaining root on 4.4. Fantastic job on this toolkit and thank you so much!
[Moto X Android Development] TheBurgh:
Truly appreciate your quick response and help. I plan on updating and using your advice later
[Moto X Android Development] nevrozel:
OK so this is exactly what happened to me twice:

- I am on 4.2.2 camera update rooted

- I then start option 11 and answer NO and NO and proceed with MotoWPNoMo

- MotoWPNoMo is succesfull and write protection is off

- then it reflashes 4.2.2 camera update (I think there is a problem here? see below**)

- then it tells me to run Cydia Impactor and puttytel 2 times.

- I run Cydia Impactor first time

- I run puttytel first time -> HERE COMES THE PROBLEM: it tells me "SlapMyMoto 1.o does not support write protected devices. Please root using RockMyMoto, then remove write protection with MotoWpNoMo and restore to stock before continuing with SlapMyMoto".

OK but this is EXACTLY what I have done, twice, and everytime i get this error.I think that the script deletes root and re-enables write protection when flashing firmware 2nd time**.

So I don't know how to preserve root and write protection off after the script flashes 4.2.2 the second time.
[Moto X Android Development] stillthisguy:
That makes it sound like you don't have WP off and that MotoWPNoMo did not complete successfully. You need flash back to stock, then run option 11, it will take you through RockMM, then MotoWPNoMo, then flash you back to 4.2.2 again, then it will take you through SlapMM. That is the process of getting root on 4.4.
[Moto X Android Development] nevrozel:
Is MotoWPNoMo's effect permanent? After I run MotoWPNoMo I get this "Enter to exit" message which I believe it means everything is done correctly. Then in your script main window R/W Protection is 0. Does this mean protection is off and is permanent?

Because after this, I continue the process, reflash 4.2.2 the second time and them R/W Protection is 1 and no root - I get in the same place as before, stuck at puttytel window. :)))
[Moto X Android Development] lowvolt1:
Yes. After you run motowpnomo, it is permanent. Sounds like it is not taking.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Android Development] jtseals:
man im so confused i thought i had finally went thru all the steps i have the root write protection at 0 and its not going back to 1 at all which is good but im confused about how to go to 4.4 and keep or get root
[Moto X Android Development] mskks64:
I'm not sure i did the last part, is there a way to redo just that part?
[Moto X Android Development] stillthisguy:
If you have run MotoWPNoMo successful, then when you start option 11 answer no and yes. That will take you through the rest of the process.
[Moto X Android Development] stillthisguy:
You can manually complete that part, just go look at the slapmymoto OP for the commands. Or you can run option 11 of the toolkit and answer no then yes. This will flash you back to 4.2.2 and erase everything on the phone. Then it will take you through the first part of slapmymoto, then install 4.4 ota, then it will complete the last part of slapmymoto.
[Moto X Android Development] Eighthourblink:
Fresh install of 4.2.2 camera update. Trying to run option 11. All the files are in the correct folder. Chose option 1, it its giving me errors?

Help?
[Moto X Android Development] kwyrt:
What errors are you getting? I'm having issues as well. Keeps telling me to fix usb debugging. I have usb debugging enables so I'm unsure what's wrong.
[Moto X Android Development] jtseals:
same problem for me tells me to fix usb debugging when i clearly have it enabled
[Moto X Android Development] ccoulterjg1:
Can't flash stock 4.2.2.

Hey, I keep getting errors when trying to flash to 4.2.2 from stock 4.4. Everything extracts fine and then the phone reboots to bootloader. Then as it's running the operations, it throws errors which I believe all say something about failing to extract. So I decided to try to just root using the SlapMyMoto option, and when I do this it shows all of the direction and requirements, then I select option 1 to start the root process and it instantly starts throwing errors so quickly I can't even read them.

Just wondering if anyone knows what the issue is with all of this. Any help is appreciated! Looks like an amazing tool if I can get it to work! Thanks!
[Moto X Android Development] Mont:
Very useful thanks you :good:
[Moto X Android Development] jakeo423:
help

I've got an ATT Moto X on Att. I open the toolkit, follow all the instructions to root, click start root process, and it just keeps saying the same thing over and over again. It never actually reverts it back to the 4.2.2 camera update, never roots or does anything. Am I doing something wrong? Idk what to do at this point, any help would be appreciated. Thanks.
[Moto X Android Development] kwyrt:
I think you need to do this:

"Toolkit won't open on Windows 7/8

Right click the icon>Properties>Compatibility>Check mark Run this program in compatibility mode for: Windows XP (Service Pack 3) and Check mark Run this program as an administrator."

That's from the FAQ in post #3.
[Moto X Android Development] stillthisguy:
Going to need more information than that. What errors are you seeing?
[Moto X Android Development] stillthisguy:
If it is saying you need to fix usb debugging, it means that your phone isn't listed when running the command adb devices. Sometimes unplugging and then plugging the phone back in will fix it, or sometime you have to switch from MTP to PTP and back to MTP again. That can be done under Settings>Storage>Settings button in top right>USB computer connection or clicking on the Connected as a media device notification. If you are having the issue after updating to 4.4, there is a popup on the phone that you have to authorize the computer to use adb debugging.
[Moto X Android Development] stillthisguy:
What is the last thing that comes up on the screen? When you start the slapmymoto process, the toolkit checks for everything to see if it is in right place, and it also extracts the zip files, so that is probably what you are seeing at the beginning.
[Moto X Android Development] stillthisguy:
So, I figured out what the issue with USB debugging was, and have fixed the script. I am running a final test now, and will be putting an updated version to download in the 2nd post shortly.
[Moto X Android Development] ehasley:
I am having a few issues with this Toolkit and Rooting. I was on stock 4.4 before I started all this. I chose option 11 and followed the prompts. The issue is that it doesn't seem to error out but it kicks me out to the main menu saying I must attempt again. I have the write protection removed and it flashed me back to 4.2.2 but no I am stuck.

***EDIT*** Waiting to try the new version
[Moto X Android Development] jakeo423:
Error

I run Slapmymoto and have downloaded everything and put it in the correct folder. I keep getting an error that says error: cannot find archive. how can I fix this?
[Moto X Android Development] ehasley:
Patiently hitting F5 haha

I see the change log posted but no link yet.
[Moto X Android Development] stillthisguy:
V1.3.3 is up in the 2nd post! Sorry it took so long, had this, real work, and bought a house! Was a big day!
[Moto X Android Development] kwyrt:
Congrats! Looking forward to trying the new version. Thanks [MENTION=717942]stillthisguy[/MENTION]!
[Moto X Android Development] ehasley:
Congrats!

Thanks for the hard work too.
[Moto X Android Development] ehasley:
Okay here is where I am at...

I reflashed to stock 4.4 to start over. Did step 11 and it successfully downgraded me to 4.2.2 I ran the Impactor the first time successfully, it launched Puttytel the first time and it is saying "System is not write protected... Executing step 3..." and its just sitting there at that point.

What is next
[Moto X Android Development] stillthisguy:
Sounds to me like you have already ran MotoWPNoMo successfully in the past. If that is true, answer the first question as No and the 2nd question yes.
[Moto X Android Development] kwyrt:
It worked! Thank you so much for this. Really appreciate the work you put in on this tool.
[Moto X Android Development] rantoca:
step by step using moto x toolkit

hello everyone

I'm new on this one and for make it a go , if someone can help me step by step on this , iI'm on the update 4.4 unroot and i wish to root access .

thanks
[Moto X Android Development] mschumacher69:
This is what the tool is there for, to help u step by step on this...
[Moto X Android Development] kwyrt:
I would suggest just giving it a shot. The tool actually walks you through everything step-by-step. Tells you when to do this, what to type where, etc. [MENTION=717942]stillthisguy[/MENTION] really did a great job making it almost fool proof. Just follow the on screen instructions and I think you'll be fine. If you get stuck then make a post about that and I or someone else try will help you out. Good luck!
[Moto X Android Development] rantoca:
when they ask me if you are on boot loader or android ? ,,the phone is on ,which will be the correct awnser
[Moto X Android Development] mschumacher69:
If the phone is on and you're on your homescreen, this means you're in Android.

If the phone is on and you're on a black screen with text (if u rebooted into fastboot mode using the hardware keys or adb command), this means you're in bootloader...
[Moto X Android Development] rantoca:
thanks mschumacher69 , the best way to go will be work the on boot load mode cuz i put like 10 min ago , i choose android and the message came as the phone will reboot to boot load , pree any key ,i press it and nothing comes

sorry for ask
[Moto X Android Development] stillthisguy:
Most of the steps would need to be performed in android, so you would want it booted to start. It sounds like it isn't rebooting because it is not detecting your device is connected and has usb debugging enabled. When you first start the toolkit with your phone plugged in, make sure your device is listed at the top of the toolkit under ADB Mode. If it is not, you would need to make sure you have the right drivers installed, and that usb debugging is enabled on your device. Also, make sure you are plugged into a USB 2.0 port and not USB 3.0. I wouldn't try running root until you verify that your device is recognized by the computer and toolkit.
[Moto X Android Development] rantoca:
thanks to all

besides i had other devices rooted with kitkat and other great stuff under the hood ,this look a little hard to failed process i will leave for the moment like this my i little error was i buy it from RS (make it happen !) and was on 4.2.2 before camara update and put the fun on wifi leave it to charge and he took all the update

thanks for your help may me i will try it again

---------- Post added at 09:43 AM ---------- Previous post was at 09:41 AM ----------

i will give try try later ,thanks
[Moto X Android Development] ehasley:
This did it! Thank you so much!
[Moto X Android Development] kzoak82:
not working

Ok, I'm lost after trying to get option 11 to work (slapmymoto). Followed all instructions, downloaded firmware and zips to the correct folders, phone is recognized etc. However, when I press #1 start rooting process, the script just runs on and on & nothing happens. Screenshot attached (this repeats over and over again). I'd would be much appreciated if someone could let me know what I'm missing. thanks!
[Moto X Android Development] stillthisguy:
It looks like 7zip is missing from the 1.3.3 version. Not sure how it didn't get included, but I will have to rebuild the package. This won't take long.
[Moto X Android Development] kzoak82:
Thanks! I'm sitting here thinking how is it that I rooted phones with more complicated methods but cannot figure out how to use a toolkit lol
[Moto X Android Development] stillthisguy:
V1.3.4 is up in the 2nd post. If you have installed 1.3.3 at some point, please download and install 1.3.4 before looking for support.
[Moto X Android Development] stillthisguy:
Sorry jakeo423, somehow I missed your question. Did you rename any of the .zip files before putting them in their folders? The name of the firmware zip is the most important one to have correct.
[Moto X Android Development] jakeo423:
No, I didn't rename anything. I just downloaded the zip and put it in the specified file.
[Moto X Android Development] stillthisguy:
Can you give V1.3.4 a try and see if you still get the same error? Are you on VZW or ATT?
[Moto X Android Development] jakeo423:
I'm on ATT. I tried 1.3.4 and I'm getting the same error.
[Moto X Android Development] stillthisguy:
Can you grab a screenshot?
[Moto X Android Development] NWKENT:
Sorry..posted to wrong thread..deleted..
[Moto X Android Development] jakeo423:
Screenshot
[Moto X Android Development] stillthisguy:
When it asks if you are in bootloader or android, you need to type either

bootloader

or

android

Bootloader is the fastboot screen and android would be if you are at your home screen.
[Moto X Android Development] koocheese:
I tried toolkit v1.3.4.

Initially on Rogers 4.2.2 rooted with jcase's method. I wanted to start fresh to update to 4.4.2.

Trying to revert to Firmware version - Rogers post camera.

Chose revert to stock, all the fastboot flash commands failed, at the end of the script there were a couple of erase commands.

Not wanting to try my luck, I selected the unroot option, which worked no problem.

An FYI, I noticed while playing with the toolkit, flash recovery option is missing text as to where to place the recovery.img. It's easy to figure out, but for those who aren't too literate with this stuff, you may want to complete that sentence.

Keep up the good work!
[Moto X Android Development] reno55:
I keep getting device not found when starting the kit. I am on 4.4 and I have not yet put my sim in..usb debugging mode on
[Moto X Android Development] stillthisguy:
Did you install the drivers?
[Moto X Android Development] nevrozel:
I previously tried to go through the MotoWPNoMo process (while on 1.3.2) but il always failed after it booted back to Android, saying waiting for ADB and never showing anything on my phone. Could 1.3.4 solve this issue?