yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] kernozlov:
I think the Powers That Be just dont want me to root today....

http://imgur.com/u6rod3j
[Moto X Android Development] stillthisguy:
Extract the files somewhere else, like the Downloads folder, then move them to the slapmymoto folder. Make sure you are running the toolkit as admin, as from the 2nd screenshot it looks like it is not running as admin.
[Moto X Android Development] kernozlov:
Well I tried running as admin and now im getting the same error for MotoWPNoMo.....

So all the files should or should not be zips in the folders? Was I supposed to unzip all the packages into those folders?

Unzipping MotoWPNoMo gives me the same error as SlapMyMoto...
[Moto X Android Development] stillthisguy:
It should work with the zips only, or with all files out of the zip. I must have missed something in the script. I will take a look and get another version up for you to try.
[Moto X Android Development] kernozlov:
**sigh**

http://imgur.com/B7Iyc0i
[Moto X Android Development] stillthisguy:
Give this new V1.4.2 a try. .zip files only. Make sure you are running the toolkit as admin.
[Moto X Android Development] kernozlov:
Welp. I tried the new version. Still not working. But I noticed if I run with admin it says I dont have MotoWPNoMo but when I run w/o admin it says I dont have SlapMyMoto...
[Moto X Android Development] stillthisguy:
That is rather odd, have you tried to run it in compatibility mode Windows XP SP3?
[Moto X Android Development] kernozlov:
I noticed I had 4 different installations of the toolkit in my programs so IM reinstalling it. I just installed 8.1 4 days ago so its still a little new to me.

EDIT: XP SP3 and Admin rights and still the same MotoWPNoMO problem.
[Moto X Android Development] baker5792:
I have been having the same issue as kernozlov. I am operating windows 7 SP1. I have tried uninstalling and reinstalling. I have update JDK and JRE, I have no other conflicting software. My drivers are up to date. I have also tried 1.4.2 instead of 1.4.1. I am running in compatibly mode Windows XP SP3 and as Administrator. I have no clue what I am missing. Any thoughts?
[Moto X Android Development] stillthisguy:
I really am at a loss, as I don't have any issues on 1.4.1 or 1.4.2 on either my Win 8.1 or Win 7 machines. Try downloading the .zip files again, if that doesn't work, try extracting from each .zip and moving the files to right folders then run.
[Moto X Android Development] straylight:
Stock recovery

I love these toolkits. The one for my moto M was priceless.

Will this allow me to flash to stock recovery to accept the update (uninstall twrp)? or do i have to completely flash my phone back to factory default just to reinstall that recovery?

I'm having a hard time finding were i can do this. Any info would be appreceated.
[Moto X Android Development] stillthisguy:
If you have the stock recovery.img you can place it in the Recovery\Custom folder and then choose option 8 to Flash Recovery. Then use option 2 to choose your own, and it will come up with a list of recoveries you have in the recovery\custom folder. TWRP 2.7.1.1 does come in the toolkit, in case you want to flash that back later as well.
[Moto X Android Development] straylight:
This is my problem. I don't have the recovery img.
[Moto X Android Development] stillthisguy:
All of the firmware downloads are here. Just make sure you download the firmware for what you are currently on. Otherwise if you are looking for the stock recovery for Verizon 4.4.2 -VZW 4.4.2 Recovery.img
[Moto X Android Development] straylight:
That was exactly what I needed, Thanks Stillthisguy!
[Moto X Android Development] tdiman:
Excellent! Thank you.
[Moto X Android Development] tluley51:
It appears as though I have lost recovery, both stock and twrp...any idea on how to get it back?

And yes, I tried downloading a flashing the stock recovery.img file, it shows errors on both the phone and in the toolkit.

Any help would be MUCH appreciated.
[Moto X Android Development] rahulcuthber91:
Hi,

I am Also running stock moto x unlcoked twrp installed XT1052,and i have seen my friends getting ota but i guess i need to have stock recovery in order to install ota but i dont have the same ,Can you plz help me with it?

Also what is that link of blur based rom,I am always confused with those firmwares?
[Moto X Android Development] KidJoe:
On your Phone... App Drawer -> Settings -> About... Make note of the System Version and Android Version. Visit -> http://sbf.droid-developers.org/phone.php?device=0 Look for your phone's System Version number in the FIRMWARE VERSION column on the web site, and your carrier in the Carrier column. Download that file. Unzip it. It will contain the RECOVERY.IMG that you can flash with the ToolKit.

(for example, my Verizon X has System Version 212.55..26.ghost_verizon.Verizon.en.US so from that web site I'd download "firmware version" Android 4.4.4 Blur_Version.212.55.26.ghost_verizon.Verizon.en.US, unzip it, and use the recovery.img that is inside of it)

Not being stock will only prevent you from installing an OTA, it will not prevent you from being notified one is available.

If your phone hasn't said an OTA is available, then it likely isn't being pushed for your carrier/model, or its being pushed out in batches and your phone hasn't been included in the first batches so far.
[Moto X Android Development] stillthisguy:
Going to need some more information, what model and carrier? What Android version are you currently on? What version of the firmware did you download? What errors are you seeing?
[Moto X Android Development] tluley51:
Yes sir, thanks for the reply.

Verizon Moto X non dev non rooted (used to be rooted and rommed with safestrap).

Currently on the 4.4.2 OTA, trying to pull the 4.4.4 OTA but since no recovery is installed, nothing happens.

When trying to flash recovery.img...

The errors on the toolkit are:

writing 'recovery'...

<bootloader> Preflash validation failed

FAILED <remote failure>

finished. total time: 1.842s

recovery.img has been installed successfully.

The errors on the device are:

Failed to hab check for recovery: 0x56

preflash validation failed for recovery
[Moto X Android Development] stillthisguy:
This error sounds like you are trying to flash the incorrect version of recovery.img to the device. Did you download the 4.4.2 vzw image or the 4.4.4 vzw image to get the recovery.img file? Post #639 has the VZW 4.4.2 Recovery.img download link, if you don't want to download the entire firmware again.
[Moto X Android Development] tluley51:
That is exactly the recovery.img file that I downloaded and tried to flash, unfortunately. Tried re-downloading it twice on my desktop and once even on my laptop and flashing it via toolkit with no luck.
[Moto X Android Development] stillthisguy:
What bootloader version is your device on? On the bootloader screen it is at the top, 2nd line down.
[Moto X Android Development] tluley51:
30.71 (sha-913941e, 2013-07-31 10:46:37)

This?
[Moto X Android Development] stillthisguy:
I am pretty sure that is the bootloader of 4.2.2 camera update for Verizon.

Verizon Bootloader Versions

4.2.2 Original Release - 30.70

4.2.2 Camera Update - 30.71

4.4 - 30.B2

4.4.2 - 30.B4

4.4.4 - 30.B7

Which means it would only be able to flash the recovery.img from 4.2.2 camera update firmware - VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF
[Moto X Android Development] tluley51:
I just downloaded the whole firmware folder and just took out the recovery.img and put it in the custom recovery folder, flashed with success but still unable to boot to recovery. I choose recovery from the bootloader screen and my phone just stays black for about 15 seconds, reboots to the blue M startup screen, then goes black again and continues to loop. I can't seem to get it to stop looping either...

Finally got it to stop looping, back into Android. Debating trying to go into recovery again...

Tried going back into stock recovery, no luck. Any other ideas?
[Moto X Android Development] KidJoe:
I gotta ask... how did you get on the 4.4.2 OTA without updating the bootloader?

Something tells me you were using mFastboot and only flashed PARTS of your phone.

Flashing is failing because you are using missmatched versions. And if you manage to take the OTA in this state, you will likely brick.

Consider downloading the full 4.4.2 SBF from -> http://sbf.droid-developers.org/phone.php?device=0 reboot the phone into fastboot/booloader mode, and using mFastboot to flash each part using the following commands... NOTE: since you have a Verizon X, you could just download the 4.4.4 SBF and use it instead, with the same commands.

mfastboot getvar max-download-size

mfastboot flash partition gpt.bin

mfastboot flash motoboot motoboot.img

mfastboot reboot-bootloader

mfastboot flash partition gpt.bin

mfastboot flash motoboot motoboot.img

mfastboot flash logo logo.bin

mfastboot flash boot boot.img

mfastboot flash recovery recovery.img

mfastboot flash system system.img

mfastboot flash modem NON-HLOS.bin

mfastboot erase modemst1

mfastboot erase modemst2

mfastboot flash fsg fsg.mbn

mfastboot erase cache

mfastboot reboot

(yes, repeating some of the first few lines is intentional.)
[Moto X Android Development] tluley51:
Honestly, I have no idea. I was on 4.4 with root and the 4.2.2 bootloader, per JCase method. Somewhere along the process, I unrooted and got on the 4.4.2 OTA while keeping 4.2.2 bootloader/recovery.

I am not in Android again, wiped phone, on 4.2.2.

I will try these steps and report back.

---------- Post added at 08:32 PM ---------- Previous post was at 07:46 PM ----------

Everytime I try to do a command, it starts with "<bootloader> Variable not supported!" then proceeds to try and flash the files anyway...I dont think it is completing right and I dont want to continue with the risk or bricking.
[Moto X Android Development] rahulcuthber91:
Thanks for info. But i have recently flashed T-mobile XT1053 so now i am on XT1053 and not on XT1052.I dont know what this variant means.is it related to hardware or software?

Thats why i havent received any OTA notification. so first i need to flash stock XT1052 indian variant for getting OTA :(
[Moto X Android Development] mschumacher69:
It's related to both hardware and software. It's the model number of the hardware which is set by the software. Running the Retail US (TMO) image on your phone would make ur phone appear as if it's an XT1053 but in fact the hardware would still be XT1052.

If you're currently on the Retail US (TMO) image, you're most likely on 4.4.3 and flashing back to the stock Indian XT1052 image would mean that you would be downgrading (unless you directly flash the full 4.4.4 SBF which is not available yet) which would fail unless you manage to flash parts of the SBF which is highly NOT recommended because you would most likely brick when you take an OTA because of the mismatched versions of the different parts of the image.

It is highly recommended to stay on the Retail US image now and wait for the 4.4.4 OTA when it is released for it, or wait for the full 4.4.4 SBF to be released for your carrier and flash it if you wish to go back to your original stock firmware.
[Moto X Android Development] stillthisguy:
<bootloader> Variable not supported! is caused by using fastboot instead of mfastboot. You can flash everything but system.img with fastboot, but you might as well flash all the commands with mfastboot.
[Moto X Android Development] tluley51:
That's really weird because I have mfastboot setup and I am using those exact commands.

For now, I might have to concede. I think I'm just going to rock 4.2.2 until the new Moto X releases. Although I REALLY want to figure this out...
[Moto X Android Development] rahulcuthber91:
Okay.But i have twrp backup of 4.4.2 XT1052. So i can go back to 4.4.2 anytime and get an OTA for indian version? But after going to 4.4.2 .I will have to uninstall xposed module and install stock recovery right?
[Moto X Android Development] mschumacher69:
You'll be able to take your system partition back to 4.4.2 but not your bootloader and gpt partitions. If you do that, you would have mismatched versions and you would most likely brick when you take the 4.4.3 OTA.
[Moto X Android Development] rahulcuthber91:
U mean to say if i restore my backup to 4.4.2, bootloader version will not be changes and if i install 4.4.4 OTA on that ...i will brick?Have i done anything wrong by flashing T-mobile variant?
[Moto X Android Development] mschumacher69:
That's exactly what I mean. You haven't done anything wrong by flashing the Retail US (TMO) image (as long as it's fully compatible with your phone), actually, I would recommend staying on this image because it is the one that usually gets OTAs first and I expect it to get L first.

The reason it didn't get 4.4.4 first is because 4.4.3 and 4.4.4 are on the same upgrade batch (21X.XX.XX) and we already got it, it happened to be 4.4.3 instead of 4.4.4 because 4.4.4 wasn't available yet when we got it.
[Moto X Android Development] rahulcuthber91:
so there is no harm staying on this image and i will get notified as and when new update is there.Its just that i have to flash stock recovery prior installing any official update?
[Moto X Android Development] mschumacher69:
That's right, as long as you've flashed the full SBF when you flashed Retail US (TMO). Also, when you get the OTA notification, make sure you flash stock recovery from the same image/version that's installed on ur phone (Retail US), not from your original carrier image.
[Moto X Android Development] rahulcuthber91:
Thanks buddy :) What is SBF?
[Moto X Android Development] mschumacher69:
It's the factory image file that you flash. When u flashed Retail US, did u flash all partitions or only some of them? How did u do it exactly?
[Moto X Android Development] rahulcuthber91:
See when i was on stock 4.4.2 XT1052. I used to flash some custom roms such as liquid smooth,dirty unicorm but as it doesnt have stock active display and touchless control, i came back on my stock rom.But then i saw this thread( http://xdaforums.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675 ) and flash this zip file with twrp and rebooted..It was working gr8 so i never mind to change it. But now motorola has rolled out OTA for all indiant variant and i wanted to be on 4.4.4 so i started searching on xda how to get back to stock and flash this OTA.hope this explains.
[Moto X Android Development] mschumacher69:
According to the thread, this is the stock unmodified Retail US 4.4.3 so u should be OK taking the ota when it's released for it.
[Moto X Android Development] rahulcuthber91:
hmm.But i never thought that it would change the bootloader also :(.Nevermind. Hopefully this will get all the latest update :)
[Moto X Android Development] mschumacher69:
Believe me it will, I'm almost sure it will be the 1st one to get Android L...
[Moto X Android Development] akhenax:
I have tried to do the backup several times, and while it seems to be working on the device, the backup files are not located locally on the computer's harddrive, nor on the phones internal storage.

Thanks for the updated Toolkit, but hopefully the next release will fix this, by perhaps having a way to open the backup through Explorer, or showing a path where the backup resides.
[Moto X Android Development] Fadelight:
I am attempting to root 4.4, but every time I select the option I get this message.

EDIT: Also, Root for 4.2.2 seems to be getting hung on the download for Cydia.
[Moto X Android Development] stillthisguy:
Make sure you are running the toolkit in compatibility mode of Windows XP SP3 and as administrator. File location should be C:\Program Files (x86)\stillthisguy\Moto X Toolkit or C:\Program Files\stillthisguy\Moto X Toolkit

[IMG="Compatibility and Admin"]https://lh4.googleusercontent.com/-U_izmKd_hGQ/U-Tcq9HC6rI/AAAAAAAAL8E/z_BIuZePsK8/w378-h517-no/Campatibility.png[/IMG]
[Moto X Android Development] Fadelight:
Thanks! That solved those issues.

Now I am having an issue where telnet is saying "Executing step 3" every time. Even the first time. It isn't going through what it should be. I know this is an issue with RockMyMoto because I tried doing it manually, too. I've RSD'd back to bone stock 4.2.2 about 4 times now, tried redownloading, everything.
[Moto X Android Development] czechm8:
Unlocked XT1060 Dev Ed. on 4.4.4 - Root?

Am I correct that an unlocked Moto X Developer Edition on VZW, running stock 4.4.4 cannot be rooted?

I was unlocked, and rooted on 4.4.2 running stock OS and stock recovery.

i hosed up a system file after I took the 4.4.4 OTA, so I had to flash back to stock 4.4.4 using the toolkit to fix. I lost root after that, so I flashed TWRP and installed Super SU, but I cannot gain root.

Any ideas?

Thanks.
[Moto X Android Development] mschumacher69:
No you're not, root can always be achieved on an unlocked bootloader.

Maybe u flashed a version of SuperSU that is not compatible with 4.4.4.

Did u flash the latest official twrp?
[Moto X Android Development] czechm8:
Yes, I pulled the latest version of twrp. it prompted me to install SU, which I did, but it did not root.

It still says unlocked, status 3 on the bootloader.

I reverted back to the stock recovery and reflashed twrp, but still no go.
[Moto X Android Development] czechm8:
I have SU version 2.01 and used TWRP version 2.7.1

Are these not compatible with 4.4.4?
[Moto X Android Development] stillthisguy:
Flash system.IMG, then TWRP 2.7.1.1, boot to TWRP and choose reboot system. It will ask to install SuperSU, slide to do so. Then when android boots you will get a notification to install SuperSU and have to reboot. Once the reboot has occurred, you will be on 4.4.4 with root.
[Moto X Android Development] czechm8:
How do I flash the system.img using the toolkit? Do I push it or is there another way?
[Moto X Android Development] stillthisguy:
Copy the system.img from C:\Program Files (x86)\stillthisguy\Moto X Toolkit\ReturnToStock\Verizon\VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml folder and paste it into C:\Program Files (x86)\stillthisguy\Moto X Toolkit folder, then use option 27 for manual ADB/Fastboot.

If booted into android

adb devices
adb reboot-bootloader
fastboot devices
mfastboot flash system system.img

If booted into fastboot/bootloader

fastboot devices
mfastboot flash system system.img
[Moto X Android Development] czechm8:
Gotcha. I'll give that a shot.
[Moto X Android Development] czechm8:
Got it all worked out!

Thanks Stillthisguy!!
[Moto X Android Development] droidzer1:
Thanks for this Moto X Toolkit as it made an almost overwhelming root and write protection removal a nearly tolerable task. I've never had this much trouble rooting a phone but it's done and working fine other than the charging LED. I tried the fix for the charging LED but it still doesn't show up. Not a big concern as I'll take root over an LED charge light any day but if it's fixable I'd like to get that done. I'll read more in this thread shortly but wanted to share a couple hickups I found along the way in using the Toolbox. Apologies if these have already been covered.

One is that by default it installs into "Program Files (x86)" which is protected in Windows 7 and 8. That's fine but even if you run Toolbox with Admin rights you will run into a problem if you are on choice 12 and you need to download the camera update ROM. It will start downloading and appear to finish but since it is saving it to a subfolder under "Program Files (x86)" it will disappear into never never land. I started the first download late one night and in the AM found it missing - nothing where it should have been. So I started it again and noted that after the first few seconds the free space on my C: drive was no longer decreasing as one would expect when a download was saving to it. After it reached 14% it had not changed in size since the start at less than 1% so I halted the hour long download. I was able to copy and paste the url seen in the Toolbox into my browser and save it to an unprotected area and later copy it to the correct location in the Toolbox Verizon folder (using a program with Admin rights).

One other hickup was noticed after starting the SlapMyMoto in that it appeared to hang up and after 10 or 15 minutes I was sure it was not going anywhere (I've got a very fast computer and even copying a Gigabyte of data to a phone like this won't take that long) I did Control-C to break the batch file. It asked me if I wanted to continue so I tried 'Yes' and then it continued on then eventually getting root and removing write protection. I'm very grateful for that as my previous attempts using some of the methods individually weren't working right.

I've got the Moto X from Verizon (I believe is the XT1060) and if anyone can suggest a way to get the charge light working again I would appreciate it. Toolbox fix didn't seem to work and I've rebooted a couple times and unplugged / replugged in the charger but no little green light.
[Moto X Android Development] stillthisguy:
Sounds like you weren't running the toolkit as administrator. You will have some funky issues when it doesn't have elevated permissions. Also, LED light works for me using the newest toolkit. If you would like to manually input the commands for the LED they are listed below.

On while charging, off when charged.
adb shell "echo battery-charging > /sys/class/leds/charging/trigger"

On while charging, on when charged.
adb shell "echo battery-charging-or-full > /sys/class/leds/charging/trigger"

Off while charging, on when charged.
adb shell "echo battery-full >/sys/class/leds/charging/trigger"

Heartbeat while plugged in.
adb shell "echo heartbeat > /sys/class/leds/charging/trigger"
[Moto X Android Development] iSplassh:
Hi guys, im new in the forum i just got the moto x (xt1053) t-mobile sim unlocked.

I want to know if can i root the phone safety with the ability to go back to stock for any warranty issues? Im on 4.4.3.

Sorry is this has been already answered.

TIA
[Moto X Android Development] mschumacher69:
Yes you can, you just have to unlock your bootloader and flash the latest official twrp, it would root for you.

It's also easy to go back to stock but this wouldn't get you your warranty back, unlocking your bootloader voids your warranty and there's no way to get it back again (unless you have a Dev Ed).
[Moto X Android Development] iSplassh:
So you are saying i cant lock the bootloader again with this tool kit?

I mean i sow the option on the screenshot in OP "lock bootloader"

Im asking a lot because i want to go safe, in case i want to sell the phone later its better to lock it again and bring it to stock...
[Moto X Android Development] mschumacher69:
You can re-lock it, but this wouldn't change anything and wouldn't restore your warranty, it would say Status 2 (re-locked), there's no way to change it back to "virgin" Status 1 (locked)...
[Moto X Android Development] iSplassh:
Thanks a lot mate ;)

Last question..i hope ...:p

So i will always get the message: Warning your bootloader has been unlocked/relocked?
[Moto X Android Development] mschumacher69:
Yes you will always get the Bootloader Unlocked Warning Message even if you re-lock...

Unless u modify ur boot logo that is...
[Moto X Android Development] iSplassh:
Sorry if i bother you again, how can i modify the bootloader logo?
[Moto X Android Development] mschumacher69:
There's a thread in the forum on that, look for it...
[Moto X Android Development] KidJoe:
See -> http://xdaforums.com/moto-x/themes-apps/moto-x-boot-logos-t2417961

or -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm