yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] stillthisguy:
The toolkit currently provides SlapMyMoto for ATT and VZW. Future version(s) may include other carriers. Why don't you just unlock your boot loader, install twrp custom recovery, and flash SuperSU.zip from within twrp?
[Moto X Android Development] mschumacher69:
You don't need SlapMyMoto to root the GSM Unlocked (TMO) phone. Just unlock your bootloader, flash twrp and flash supersu, it's as easy as that...

[MENTION=717942]stillthisguy[/MENTION], just a suggestion, I think it would be useful if u add the root method for unlockable bootloaders as well, 1 way of doing it is replacing options 9, 10 and 11 with 1 option called Root, then users would select between Locked Bootloader (ATT, VZW and RW) and Unlockable Bootloader (most if not all others), if they select Locked Bootloader, they would choose between Pwn, Rock and Slap and if they select Unlockable Bootloader, they would get instructions to unlock bootloader, flash twrp and supersu.

What do u think?
[Moto X Android Development] whittikins:
I thought that unlocking it on the non-developer edition would void the warranty. I was under the impression that rooting could be undone and factory reset without unlocking the BL, which would maintain warranty. If this is wrong, please let me know :).
[Moto X Android Development] elliot2112:
if i have the non developer version and root with a locked bootloader am i only able to use safestrap for a recovery and would i get that through the toolkit? also will i only be able to use certain roms with a locked bootloader? thanks.
[Moto X Android Development] stillthisguy:
Just by rooting you will void your warranty, and that is referenced in the OP of every Root thread. You can unroot by flashing back to stock, but there is still a way to detect it if they really wanted to. I am not saying which way you should choose to root, but making sure you have the knowledge about both subjects. SlapMyMoto does require MotoWPNoMo to be run, which is a permanent write protection disable, even if you return to stock. I have read that the 4.4.2 update removes the WP disable, so that would be one less way for the person checking the phone to check. You have to keep in mind that there is also a qe identifier check that you can read more about here. Though, I don't know if what is said about the qe identifier on that page even works the same way on 4.4 or 4.4.2 as it did on 4.2.2 (that page was written when only 4.2.2 was availble). It really comes down to whether or not the person completing the warranty replacement looks for tampering.
[Moto X Android Development] stillthisguy:
I am not sure how safestrap works, but as far as a custom recovery like TWRP or CWM, you cannot install those with a locked bootloader. You can read up on safestrap here.
[Moto X Android Development] stillthisguy:
I have already started to change the root options a bit and that does sound like something that could be changed as well.
[Moto X Android Development] mschumacher69:
Sweet! Thanks for your efforts to produce an improve this tool!
[Moto X Android Development] whittikins:
Thanks very much. I'm attempting to do this manually, but I keep running into a problem with SlapMyMoto. Details here: http://xdaforums.com/moto-x/moto-x-qa/stuck-slapmymoto-followed-steps-exactly-t2662762/post50650922

Any idea what's going on? After rooting with Rockmymoto (while on 4.2.2 camera fix), removing write protection with motowpnomo, then flashing 4.2.2 stock again, then running slapmymoto. It just says I don't have write protection and to do what I just did!
[Moto X Android Development] NWKENT:
Hello.. :) Nice tool..

sent by my 4.2.2_12.15.15

XT1060 Moto XDEV
[Moto X Android Development] Swimboy46163:
[MENTION=717942]stillthisguy[/MENTION] is it possible to flash the system.IMG using your toolkit? If so how is this done?
[Moto X Android Development] stillthisguy:
Just place system.img in the Moto X Toolkit folder and then use option 25 and manually flash it. Nothing automated for just flashing 1 .img file like that.
[Moto X Android Development] Swimboy46163:
When I click option 25 to do it manually. What do I put into the command prompt to flash it (sorry, I'm no good with command prompt). I have "system.img" in the moto toolkit folder
[Moto X Android Development] stillthisguy:
You would need to be in the bootloader on the phone, so if you are booted to android you would type

adb reboot bootloader

then

mfastboot flash system system.img
[Moto X Android Development] James4.0:
I have not used your tool kit yet, is "#7. Recovery" for TWRP or CWM on the DE phones or is it from the stock recovery?
[Moto X Android Development] Mickoou:
Unroot dev back to stock

I just want to unroot verizon dev edition back to stock .Im on 4.4 rooted now

Will this toolkit do this?

Which is the proper Motorola Firmwares for my phone on the motorola site.

Also when I choose Verizon which varent do i use for the Dev edition.

Thanks
[Moto X Android Development] DeathGrind:
Hi. I am attempting to use this toolkit to return to stock. I am on verizon. However, when i go to download and install, both options 1 and 2 say file not found> It appears that they are not online anywhere. However I do have MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip on my pc that i downloaded directly from motorola for my verizon moto x. How would i go about using this file in conjunction with this toolkit. Thanks

Edit....

Nevermind, I ended up just using fastboot to restore system.img and recovery.image without this tool.
[Moto X Android Development] Mickoou:
I'm Still interested in this question.

Also will this toolkit return me to stock & unroot if i was runnning this rom. [ROM] Eclipse Moto X AOSP 4.4.2 - XT1060 VZ?.

Thanks
[Moto X Android Development] dewie68:
So I'm not sure if I missed it, but, what are the conditions for this toolkit? What carrier? What version of software?
[Moto X Android Development] DownTheCross:
Okay, so I went through the entire toolkit, had a little issue where it wouldn't push the slapmymoto files to the sdcard, did that manually, got passed that. Got to the download and install 4.4 part, 4.4 was downloading, probably around 45% and then lightning struck my house.

Can I now, several hours later still install the 4.4 update and can I run the necessary commands in android terminal?

Edit: Well, I guess I could give it hell trying on this netbook, I can always just start again when I get back to the house.
[Moto X Android Development] stillthisguy:
Sorry about not getting to questions sooner. I have been moving from one state to another over the last few days.
[Moto X Android Development] stillthisguy:
It is for any and all recoveries you would like to flash to your phone. Just place the recovery image in the recovery\custom folder and then you can use option 7 to flash it.
[Moto X Android Development] stillthisguy:
I have heard (but cannot confirm) that the verizon SBF file is the same whether you get it from here or the moto site. If you download 4.4 from the SBF site you can use the toolkit to return to stock 4.4. It will erase everything on the device though. I will be adding the ability to flash the one from the moto site, as I now have a Dev Ed to test on.
[Moto X Android Development] stillthisguy:
No conditions, other than you would have to run it on Windows.
[Moto X Android Development] stillthisguy:
You could either start over or if you install 4.4 you would just need to run option 25 and enter the following code:

adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
[Moto X Android Development] DownTheCross:
Thanks man, I'll try this as soon as I can get this little netbook setup and can run the toolkit.

Edit: worked like a charm! Rooted on 4.4, removed most, if not all of the bloat, and got gravitybox set up.
[Moto X Android Development] mschumacher69:
I can confirm that the SBFs on the sbf website and moto website are the same, you can confirm that yourself by comparing the md5s of each file within the zip file and they are exactly the same. The only difference is the XML file which doesn't have the commands to erase cache, userdata, customize and clogo on the moto website.
[Moto X Android Development] nvertigo:
I'm on VZW dev edition. Can I uninstall xposed and gb and use this toolkit to return to stock to accept OTA? I've been pushing off updating.

sorry if this has been asked, didn't find anything.
[Moto X Android Development] NWKENT:
1) Purchase / Install Titanium Backup Pro..one can "Freeze" the update..

2) With the DEV model..Why OTA.? To save your data.? The latest FXZ is available.!

sent by my 4.2.2_139.15.1

Jelly Bean TWRP 2.6.3.1

XT1060 Moto XDEV

Please donate to: jcase & Hashcode (if you can)
[Moto X Android Development] wncoulte:
So now, I used RockMyMoto and I'm rooted on 4.2.2. Since you mentioned that I'm on the post-camera OTA 4.2.2, do I need MotoWPNoMo?
[Moto X Android Development] mschumacher69:
If u have used it already, u don't need to use it again. If u haven't used it yet, u have to use it to disable write protection.
[Moto X Android Development] wncoulte:
No, I don't believe I've used it before. All I've ever done prior to the RockMyMoto, was use download the 4.2.2 firmware, altered a single line of code in the file, and RSD Lite to downgrade from stock 4.4 to 4.2.2.

About the Write Protections: I thought I have Write Permission now, since i'm rooted on 4.2.2 from RockMyMoto, being that at the end of the installation, I got a screen that mentioned I could donate to Jason, but it also said something like 'congrats, you have write privileges.'
[Moto X Android Development] mschumacher69:
If write protection is off on ur phone, this means u probably ran MotoWPNoMo at some stage without knowing it...
[Moto X Android Development] wncoulte:
Ok, I've gone through the SlapMyMoto setup right after successfully running MotoWPNoMo, but now when I'm trying to tack 4.4 OTA my device gets an error in the middle of the installation. I'm still on rooted 4.2.2. Is there anything i'm missing?
[Moto X Android Development] stillthisguy:
If you have run MotoWPNoMo successfully, then you start the root process, answer no to the first question and yes to the second question. This will wipe the device and put it back on 4.2.2, but you will still have R/W enabled, it will run a command, then have you update to 4.4. After updating to 4.4, it will run a couple more commands and you will be done.

If MotoWPNoMo didn't complete successfully, then you would answer no to the first question and no to the second question. Then follow the process in the toolkit.
[Moto X Android Development] wncoulte:
After running through the SlapMyMoto root tookskit succesfully, yes, I was back at 4.2.2 and yes I still have R/W enabled. The problem is this: when my device ask me to install OTA 4.4 after it finishes downloading it, of course the phone reboots and starts to install 4.4, but during the process I get the green android on his back with an error, meaning that my Update Failed.

Okay, i'll run through the toolskit one more time. FYI: MotoWPNoMo did run successfully last night and I checked to see if I have write access to my phone and yes, I still do, so i'll tell the toolskit yes again when I get there.
[Moto X Android Development] dmonleo:
I'm on latest android. Sprint motoX. Will this method work?
[Moto X Android Development] wncoulte:
Alright! GREAT!! I'm finally rooted on 4.4. Last question: how do I disable 4.4.2 Update Notifications and Prompts to install? I'm only asking because having this notification hang around is dangerous, because in the past I've accidentally hit the install button and caused my device to lose root.

---------- Post added at 05:38 AM ---------- Previous post was at 05:34 AM ----------

Alright! GREAT!! I'm finally rooted on 4.4. Last question: how do I disable 4.4.2 Update Notifications and Prompts to install? I'm only asking because having this notification hang around is dangerous, because in the past I've accidentally hit the install button and caused my device to lose root.
[Moto X Android Development] NWKENT:
Titanium BackUp Pro.."Freeze" the ( MotorolaOTA 1.0 ) and (Updater 1.0)..now your safe..

:)

sent by my 4.2.2_12.15.15

XT1080MDEV (aka) Droid Maxx DE

Please donate to: jcase & Hashcode (if you can)

---------- Post added at 11:51 PM ---------- Previous post was at 11:43 PM ----------

One must start out on 4.2.2 Rooted..(RockMyMoto) then "Write Protect Off" as our friend mentions here..then to 4.4 and then (SlapMyMoto)..

If your on 4.4.2 then I'm pretty sure its to late for Root..Someone correct me if I'm wrong..one cannot maintain Root over onto 4.4.2 UNLESS you have a DEV model..

sent by my 4.2.2_12.15.15

XT1080MDEV (aka) Droid Maxx DE

Please donate to: jcase & Hashcode (if you can)
[Moto X Android Development] spyderkoz:
I hope you guys can help I had a pc and will it found its way to the floor, had the tool kit on there now I am on a pc thats linus how do I install the tool kit to there... please and thank you
[Moto X Android Development] stillthisguy:
Sprint Moto X can be bootloader unlocked, that would be the best way to gain root. Unlock the bootloader, install TWRP, Install SuperSU.
[Moto X Android Development] stillthisguy:
The toolkit is currently only supports Windows systems.
[Moto X Android Development] stillthisguy:
I need some help, can someone on sprint and tmoblie with 4.2.2 post camera and 4.4 run the following adb command and post the output.

adb shell getprop ro.build.id
[Moto X Android Development] JGoN86:
I selected option 11 for slapmymoto

When i get to

List of devices attached (be patient this may take a moment)

I have been waiting for a 20 minutes and nothing. Any idea? or should i wait longer?
[Moto X Android Development] Mickoou:
Can I use option 8 to flash 4.4 which is on my computer rather than 4.2.2 which my Moto x came with?.

Can i use option 7 to flash a 4.4 recovery (non custom) to recieve the 4.4.2 update
[Moto X Android Development] stillthisguy:
I would try unplugging the phone, waiting a minute, and then plugging it in again.
[Moto X Android Development] stillthisguy:
Answers are within your quote.
[Moto X Android Development] spyderkoz:
Major brain fart here.. I finally got a pc with windows, installed what I need trying to bring my sprint moto x back to stock to do update but all looks good but it is not taking any ideas. thanks again guys and gals
[Moto X Android Development] stillthisguy:
Going to need a little bit more information about what is happening when you say it isn't working.
[Moto X Android Development] spyderkoz:
I installed the kit, drivers and everything else need ran through program I think it was opt 8 then 3 then 3 it ran through booted to boot loader restarted bit root was still there... Kinda want to get the moto up and running getting bored of the note 2
[Moto X Android Development] stillthisguy:
That sounds like the system.img file didn't flash. Did you notice anything fail during the flash process? Run the flash back again, just do opt 8, 3, 6 then watch the process. If one or more fail, report back the error.
[Moto X Android Development] Toxicoblivion:
Does this still work for rooting ATT 4.4?
[Moto X Android Development] NoNotReally:
I got to the point in the slapmymoto walkthrough where it says

You will now need to install the 4.4 update.

Press enter to continue once 4.4 is installed.

Does this mean I just install the OTA on the phone? Won't that result in a bootloop?

Edit: Nevermind. I went ahead and installed the OTA. No bootloop this time.
[Moto X Android Development] stillthisguy:
Yes
[Moto X Android Development] princedwi:
VZW Non DE at 4.2.2 OTA Keeping Root on 4.4

Just as a friendly note for those uncertain:

When using the Moto X toolkit with a non-DE VZW Moto X, the last step where the toolkit now prompts the following:

"You will now need to install the 4.4. update. Please enter to continue once 4.4 is installed"

Just take note of the OTA when it downloads on your Moto X - it should reflect OTA update 140.45.5 (4.4). This is safe, and not the 4.4.2 update. As such, continue as normal and you should be good for 4.4 root.
[Moto X Android Development] mschumacher69:
When taking the OTA from the post-camera 4.2.2, the OTA would always be 4.4, it can never be 4.4.2. You can only take the 4.4.2 OTA once on 4.4.

OTA's are incremental, which means you cannot jump directly to 4.4.2 from 4.2.2 because there's a 4.4 OTA in between...
[Moto X Android Development] Teidullie:
confirmation

so just to confirm the rooting method in the tool kit is no longer working on the ATT variant if you take the 4.4.2 update OTA?
[Moto X Android Development] Danzoman:
OK I am having a big problem. I cannot get my computer to recognize my phone in fast boot at all. adb devices shows numbers and I can reboot to boot loader but nothing happens after that. When I am in boot loader and check the driver it shows the wrong driver but even if I restore any generic fast boot driver or the Moto driver sill nothing. The boot loader screen says every time I unplug the cable though. I have no issues with fast boot with my Nexus 7 or 5. A little more info, Windows 8 and I previously rooted two Moto X's with Jcase method and disabled write protection. Am I missing something here or ant ideas? Thanks for any help.

btw no instances of using fast boot work including this utility. Oh and I am on stock rooted Verizon 4.4.
[Moto X Android Development] stillthisguy:
There is currently no root method for 4.4.2 other than an unlocked bootloader. You cannot use this toolkit to root 4.4.2.
[Moto X Android Development] stillthisguy:
Try changing from MTP to PTP and see if fastboot starts working. Then just switch back to MTP.
[Moto X Android Development] Danzoman:
I'll try that but how would I do that while in boot loader?
[Moto X Android Development] stillthisguy:
Wow, I have not had enough caffeine this morning. That will not work when you are in bootloader, when you are in bootloader, and you bring up device manager, what does it list your phone as?
[Moto X Android Development] Danzoman:
OK now I'm lost lol! When I am booted into the system when I type adb devices I get the serial # or whatever and adb reboot boot loader takes it to the boot loader. Then I'm dead. Absolutely nothing works. No rsd no manual fastboot commands nothing.

Does rockmymoto or pwnmymoto replace something that's hindering this?
[Moto X Android Development] stillthisguy:
When your phone is plugged in and in bootloader, what is showing in device manager in Windows? I have attached a sample of what mine shows.
[Moto X Android Development] Danzoman:
I got it sorted out. I'm not sure what windows 8 update did it but for some reason when I'm in boot loader I have to delete the driver and change it to boot loader interface. I have to do it with my nexus devices as well but the same driver that makes them work didn't make my moto x work.
[Moto X Android Development] dmonleo:
I'm rooting today!!!
[Moto X Android Development] shaopeng9:
root for 4.4.2

so will there ever be a root method for 4.4.2? if not can i somehow disable the OTA update prompt? it's getting really annoying.
[Moto X Android Development] gerodive:
Finally decided to root my Verizon Moto X! Just installed the toolkit, installed the drivers, and then.... It won't recognize my phone. "Error: no device found." What could be the issue? =(
[Moto X Android Development] stillthisguy:
I wouldn't hold your breath on a root method for 4.4.2, but you never know. To disable the OTA update prompt you would need to use Titanium Backup and freeze Motorola OTA. To delete the OTA that has already been downloaded, you would need to reboot to bootloader and run command - fastboot erase cache
[Moto X Android Development] stillthisguy:
Did you turn on USB Debugging in the Developer options?
[Moto X Android Development] KidJoe:
If you want usable root on the X you need two parts 1. Root Exploit, and 2. An Exploit that allows for disabling Write Protection.

When Write Protection is enabled (the phone's default state with locked bootloader, or the state you are in after you take the 4.4.2 OTA), any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on.

For 4.4 and lower, MotoWpNoMo process disabled write protection on locked bootloader phones. With 4.4.2 this loophole was closed, and you can't flash back to 4.4 or lower.

While Jcase said he has a root method for 4.4.2 but he wont release it until fall, I have seen no mention of a Write Protection Disable for 4.4.2 being worked on or anything.

So right now, if you have 4.4.2 on your phone, the only way to root and disable write protection is if your phone is eligible to have its bootloader unlocked via Motorola's web page (there was a 3rd party "from China" way to get an unlock code if your phone isn't eligible via Moto's web site, but that seems to have ended.)

Oh, and you can NOT disable the OTA prompts unless you are rooted.
[Moto X Android Development] gerodive:
Yes indeed! And then reinstalled drivers. Still nothing.
[Moto X Android Development] stillthisguy:
Change MTP to PTP, then if it works change it back. Also, make sure you are using a USB 2.0 port and not USB 3.0.
[Moto X Android Development] gerodive:
It recognized it via PTP! Unfortunately, when I switched back to MTP it wouldn't recognize it anymore. Is it possible to do the SlapMyMoto root via a PTP connection?
[Moto X Android Development] gerodive:
Bump? =/
[Moto X Android Development] doitinthedirt:
Don't know why but when I rooted my razr M a couple years ago and had trouble getting the pc to see the razr m I checked the moto site and it said to download the latest windows media player, it worked.
[Moto X Android Development] gerodive:
Already on the latest unfortunately. So I take it I can't root on a PTP connection?
[Moto X Android Development] Czechnolog:
Guys,

do you have any RELIABLE script for going back to STOCK ROM - with re-locking bootloader as well?

I created this, but it does NOT work on my Moto X (XT1052 - GB RETAIL)

Thanks.

===

::Set our default parameters
[MENTION=279333]ECHO[/MENTION] off

SET fastboot=fastboot.exe

%fastboot% devices

%fastboot% oem lock begin

%fastboot% flash partition gpt.bin

%fastboot% flash motoboot motoboot.img

%fastboot% flash logo Moto-logo.bin

%fastboot% flash boot boot.img

%fastboot% flash recovery recovery.img

%fastboot% flash system system.img

%fastboot% flash modem NON-HLOS.bin

%fastboot% erase modemst1

%fastboot% erase modemst2

%fastboot% flash fsg fsg.mbn

%fastboot% erase cache

%fastboot% erase userdata

%fastboot% oem lock

pause
[Moto X Android Development] gerodive:
That PTP root guys... Can it happen, or am I forever doomed to have a stock phone?
[Moto X Android Development] stillthisguy:
I have never tried. If your phone works on PTP it should work with MTP. Maybe try finding the universal USB driver.
[Moto X Android Development] clavin78:
Sqqqqqqqqqqqqqqqent qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq my Nexus 7 using xda app-developers app

---------- Post added 20th April 2014 at 12:00 AM ---------- Previous post was 19th April 2014 at 11:59 PM ----------

Qqqqqqqqqqqqqqqqqqqqqqqqqq

---------- Post added at 12:00 AM ---------- Previous post was at 12:00 AM ----------

Qqqqqqqqqqqqqqqqqqqqqqqqqq frqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqom my Nexus 7 using xda app-developers appqq
[Moto X Android Development] doitinthedirt:
if I am on 4.4 do i run flash back to 4.2.2 and rockmymoto and wipemymoto and flash 4.2.2 and than slapmymoto all seperately or do i just run slapmymoto?

Thanks
[Moto X Android Development] stillthisguy:
Just use option 11. Root with SlapMyMoto
[Moto X Android Development] ambient711:
JaroslavHruska, this worked for me, pretty fast and painless. My Moto X was not factory resetting or updating so I just flashed 4.4 onto it. Hope this helps.

http://wccftech.com/steps-to-restor...lite-att-sprint-t-mobile-us-cellular-verizon/

Austin
[Moto X Android Development] BADDINOROX99:
will this root 4.4.2?
[Moto X Android Development] stillthisguy:
It will not.