yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] syntrix:
One of the files is too big for fastboot. mfastboot is required (on a pc, but guessing same issues on linux).

edit, it's system.img, noted in the restore thread here:

http://xdaforums.com/showthread.php?t=2446515
[Moto X Original Android Development] AdhvanIt:
I'm using mfastboot already. It breaks the system image and send it in chunks. Without that, it would give errors about buffer size limits. As I mentioned in my post, everything flashes correctly.
[Moto X Original Android Development] stillthisguy:
Did you skip fastboot erase userdata?
[Moto X Original Android Development] AdhvanIt:
I skipped it on the first attempt, but included it on each subsequent attempt. Corrupt or bad data will typically still allow it to get past boot splash. It'll just loop at the bootani in most cases.
[Moto X Original Android Development] hackercity:
I am getting my MotoX tomorrow. From Big Red...

Will this method work on Verizon with a locked BL?
[Moto X Original Android Development] AdhvanIt:
Yes.
[Moto X Original Android Development] hackercity:
Thank!!
[Moto X Original Android Development] lowvolt1:
What XML are you flashing?

Slapped the sh*t out of my X
[Moto X Original Android Development] AdhvanIt:
The one in the OP for VZW.
[Moto X Original Android Development] lowvolt1:
Have you tried removing the get-var line? If it isn't already.

Slapped the sh*t out of my X

---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------

.57? That should be the one you use.

Slapped the sh*t out of my X
[Moto X Original Android Development] AdhvanIt:
The XML itself doesn't matter as I'm not flashing with a tool that reads it (RSDLite, scripts that read it, etc). I'm using fastboot. The premise behind fastboot is that you flash each file individually. If there was an issue with it writing improperly or failing due to a main version issue/bad file, it would tell me.

I'm not at home, so idk exactly which version it is without looking. I assure you, I'm flashing the 4.2.2 camera update for Verizon. I've downloaded it several times as well. There's got to be something I'm missing and I'm certain it's something very small..

I just have no idea what it is.
[Moto X Original Android Development] lowvolt1:
Well then, good luck.

Slapped the sh*t out of my X
[Moto X Original Android Development] AdhvanIt:
Okay, so I got it mostly fixed.

adb shell getprop ro.boot.write_protect

Returns 0 on 4.4 now. Though running the final shell command returns:

adhvanit@Lisa ~/Downloads/slapmymoto $ adb shell
shell@ghost:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
shell@ghost:/ $ chmod 755 /data/local/tmp/install.sh
shell@ghost:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
shell@ghost:/ $

Any ideas?
[Moto X Original Android Development] 640k:
did you push 4.4 using fastboot? i ran in to the same problem and tried it again with the 4.4 OTA (went back to 4.2.2, ran slapmymoto, took ota) instead and it worked fine.
[Moto X Original Android Development] schwieb:
Wow, that was a laborious process! In any case, jcase deserves props. Root is working well on my brand new Moto X!
[Moto X Original Android Development] AdhvanIt:
Sure did. I'll give it a shot waiting for the OTA to download. Thanks!
[Moto X Original Android Development] a1exus:
I followed this method, I got root, thanks! What about my recovery? Is there a way to get that back too? When I try go to recovery my phone just reboots into Android, can I get TWRP?
[Moto X Original Android Development] sydewayz:
On a vzw motox here (14 hours old...love it). So I followed the steps and ran the commands in adb shell...when I entered the commands it simply repeated what I typed as a response...so errors...no funny comments like usual. Nothing happened. Toggling Bluetooth didn't trigger anything and rebooting never happened. Looks like I don't have root either.... Any ideas what went wrong? WP is off and I def had root in 4.2.2.
[Moto X Original Android Development] Khanusma:
Hey Team Awesome :),

Anyone having trouble flashing to the 4.2.2 Camera update? I am using HouseOfMoto and getting an error when it tries to write the system update.

The phone tells me in the Flashboot screen "Invalid PIV image: system"

The HoM tool tells me "sending 'system' (262144 KB)... OKAY [ 22.653s] writing 'system'... INFOPreflash validation failed FAILED (remote failure)"

> I have tried all flashing methods available in HoM (RSD Flash and OMAP)

> I have tried both Full and Keep Data in HoM

> I have successfully done RMM (I have root) and MWMN (I have '0' which means write protection is off).

> I have successfully used HoM before to get to the 15.15 4.2.2 update

> I just went back to the 15.15 using HoM and system writes fine

> I feel I understand the correct steps and understand the goal of each step

Thanks in advance for any help!
[Moto X Original Android Development] timmay54:
I have this problem too, and i have done dang near everything to try and get it to work... its so frustrating, can anyone help... Is it because im on a hotel wifi connection? this is the most discouraging thing ever, i hope one of smart miinded people can help me!!!
[Moto X Original Android Development] Khanusma:
To perform that step the computer and phone need to be able to communicate to each other through the wifi. I doubt that the Hotel wifi setup will allow two computers to talk to each other on their guest wifi network so I wouldn't be surprised if that's the issue.

If you can't wait, you could try setting up an ad-hoc network where your laptop acts as a wifi access point and your phone can then connect to it and they could then talk to each other. I think this would be more trouble than its worth. But again, if you need it, see if you can google ad-hoc wifi laptop private network or something like that.
[Moto X Original Android Development] 640k:
this. set up an ad-hoc wifi connection. you may be able to map usb to an IP address and fake it but this is an untested method and I don't know enough right now to help with the configuration.
[Moto X Original Android Development] Blade765:
Stuck at the actual update to 4.4

I followed all of the steps to a T. However, when I go to accept the 4.4 update, everything goes smoothly until about halfway through the actual update. The phone then says "Update Failed" and reboots me back into 4.2.2. Ive tried reading through the thread, but 100+ pages is a lot of info to read.

Any ideas on what to try next? This is on a VZW Maxx.

TIA
[Moto X Original Android Development] lowvolt1:
Just putting it out there. When you flash 4.2.2 are you deleting any lines in the XML?

Also have you already rooted with rock and ran the motowpnomo? Then flashing back to a clean 4.2.2?

Slapped the sh*t out of my X
[Moto X Original Android Development] Blade765:
No, I used House of Moto to flash back to "clean" 4.2.2 (meaning I kept my user data). I'd really like to keep my data, if it's possible.
[Moto X Original Android Development] 640k:
you can't degrade OS versions without wiping your device. I can't imagine the repercussions involved.
[Moto X Original Android Development] lowvolt1:
Like 640k said, you have to wipe data. Just back up your stuff to your PC.

Slapped the sh*t out of my X
[Moto X Original Android Development] Blade765:
But I never left 4.2.2. I haven't gone to 4.4 yet because the update fails halfway through. I'm about to try the 4.4 OTA again, since write protect is still off. (I still get a 0 when I run adb shell getprop ro.boot.write_protect). It was just failing when I tried to do the 4.4 OTA update. I'm thinking maybe a corrupted update file? So, in theory, everything else should still be ready to go.
[Moto X Original Android Development] lowvolt1:
After running motowpnomo you have to flash a clean version of 4.2.2. So your not rooted anymore.

Slapped the sh*t out of my X
[Moto X Original Android Development] Blade765:
No, I haven't deleted any lines from the XML. I just tried again, following all of the steps, and, once again, it failed at the 4.4 update. Then, when the phone reboots (into 4.2.2), a popup tells me that the installation of the update failed. What the hell am I doing wrong? Should I just use fastboot to install the 4.4 update?

Here is where I stand right now. SlapMyMoto has been run through telnet, everything has been done so the phone is ready to install the 4.4 update. It reboots into recovery, and begins installing the 4.4 update. Halfway through, it fails. EVERYTIME! I'm not a noob by any means, but I sure as hell feel like a complete idiot right now! Can someone please help me figure this out????

Thanks in advance for the assistance!

:confused::mad::confused:

---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------

I did that. I used HouseOfMoto to flash 4.2.2 again, which gets rid of an root access I may have had in the past.
[Moto X Original Android Development] lowvolt1:
Use rsdlite to flash back to 4.2.2 camera update. You have to delete data.

Slapped the sh*t out of my X
[Moto X Original Android Development] Blade765:
I'm on my macbook right now, so would fastboot suffice?
[Moto X Original Android Development] lowvolt1:
You can try it. Just remember, you have to have a fresh 4.2.2 os in order to take the OTA

Slapped the sh*t out of my X
[Moto X Original Android Development] Blade765:
OK, I am going to use HOM to do a FULL wipe/restore.... are there any changes I need to make in the xml file?

---------- Post added at 10:16 PM ---------- Previous post was at 10:14 PM ----------

This **** we do for root.... oh well, I guess it was time for spring cleaning anyway....
[Moto X Original Android Development] lowvolt1:
I know if you use rsdlite you have to remove the get var line.

Slapped the sh*t out of my X
[Moto X Original Android Development] timmay54:
SOMEONE PLEASE HELP im bricked and i dont know how, i ran the update and at the end it said error and now it doesnt boot, just boot logo, im going to try house of moto.... nothing i have done for this root has worked correctly....
[Moto X Original Android Development] lowvolt1:
Did you get it fixed?

Slapped the sh*t out of my X
[Moto X Original Android Development] timmay54:
im such a noob, i cant get house of moto to work... it says file not found and its in the C:/ directory and evrything... i was hoping to keep my data but i wont probably keep my phone, idk why the update bricked me
[Moto X Original Android Development] lowvolt1:
Can you get into fastboot?

Slapped the sh*t out of my X

---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------

If so use rsdlite and flash back to 4.2.2

Slapped the sh*t out of my X
[Moto X Original Android Development] momentman10176:
Well been trying to reroot after downgrading from 4.4, made it back to 4.2.2. Had root, ran MotoWPNoMo, have successfully achieved write protection off, took update, lost root, and now can't get it back, always says SU binaries are not installed. Downgraded multiple times, and done everything according to the guides, and tools here on XDA. Anyone have any ideas?
[Moto X Original Android Development] Khanusma:
Did you run SlapMyMoto when you were in the 4.2.2 Camera Update before you took the 4.4 OTA?
[Moto X Original Android Development] momentman10176:
Yes I did, I've lost count of how many times...I've ran it so many
[Moto X Original Android Development] timmay54:
Thank you for the offer for assistance, i just went ahead and typed the fastboot commands in my command prompt, and skipped the data wipe and installation and im back to where i was (12.15.15) with the data i needed found. Now if anyone would like to help a noob out, is there anyway i can do this without losing data? Im assuming no.

What version do i need to be running? i thought 12.15.15 was the camera update that i need to be on?

any help wpuld be fantastic, other than that i want to start by runnin the Mwtpwnmoto thing then rockmymoto and then mwtpenmoto thing a 2nd time (like the directions say)
[Moto X Original Android Development] lowvolt1:
After running motowpnomo you have to flash back to 4.2.2 then run slap. Don't take OTA until directed to do so.

Slapped the sh*t out of my X

---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------

In order to root successfully on 4.4 you will lose data.

Start on 4.2.2 camera update, root using rockmymoto, then run motowpnomo, then flash back to 4.2.2 camera update, then run slapmymoto. You only have to do rock once and motowpnomo once and slap once.

Slapped the sh*t out of my X
[Moto X Original Android Development] timmay54:
so i need to start on the version before the camera update first??? then do the following:

1.motopwnomo

2.and rock my moto

3.and motopwnomo

4.flash forward to the camera update

5.run slapmymoto (and in those directions it says when to update)

I know you super guys hate when noobs like this flood the forums and ask questions that are already answered but i like having a confirmed confirmation on what im doing is right, and i really appreciate the help, honestly!
[Moto X Original Android Development] lowvolt1:
Start on 4.2.2 camera update

Then do the following

1) rock my moto, you have to root first.

2) motowpnomo, now you disable write protection. This is permanent

3) flash back to 4.2.2 camera update. Wipe data.

4) slapmymoto, you will be prompted to take 4.4 OTA in this process.

Slapped the sh*t out of my X
[Moto X Original Android Development] timmay54:
Ohhhhh okay, (Thank you again you clarified so much there, thank you thank you) So when I fxz and wipe the camera update (12.15.15) i will still be rooted and disabled write protection? then the data will be gone and i will use TiBu for that and i can finally breath?? YES THANK YOU
[Moto X Original Android Development] lowvolt1:
When you fxz back to 4.2.2 after motowpnomo. You will not have root.

Only after you run slapmymoto.

Slapped the sh*t out of my X
[Moto X Original Android Development] timmay54:
Alright well maybe i dont see why i need motopwnomo but its not my liberty to ask why, so ill give this a try, now knowing i can get back haha thanks again!!!
[Moto X Original Android Development] lowvolt1:
Slap my moto 1.0 works only after you have disabled write protection. If you don't disable write protection you would have to reboot "recovery" to write to system. Motowpnomo makes it so you can always write to system.

Slapped the sh*t out of my X
[Moto X Original Android Development] timmay54:
I know that ive been really annoying latley, but i need more help... So i used house of moto to wipe everything, back to the camera update. I tried rooting using rock my moto but it wont work saying "system is not write protected " ( i disabled write protections before i flashed back to the camera update) and motowpnomo wont work either because i dont have root. What in the world do i do now?
[Moto X Original Android Development] lowvolt1:
You already ran motowpnomo once right? Because your not write protected. You don't need to run it again. You can just run slapmymoto.

Slapped the sh*t out of my X
[Moto X Original Android Development] Blanko6:
I am finally on step 4 but it keeps telling me "device offline " ........ !!!
[Moto X Original Android Development] Khanusma:
This could be your solution.

Make sure you are on ADB 1.0.1.31 (I think you can type adb version at the command prompt). Then you have to accept the security prompt on your phone when trying to connect with ADB.

http://www.wugfresh.com/faqs/how-to-fix-adb-device-is-listed-as-offline/
[Moto X Original Android Development] Blanko6:
No luck ! I seems to be starting at "port 5037 " not sure if it has something to do with that .

Weird thing is before I took the 4.4 update it was working just fine .

Been rooting for 8 hours now ......help !

Thanks
[Moto X Original Android Development] 640k:
did you enable usb debugging?
[Moto X Original Android Development] Blanko6:
Yes, yes , and toggled it on and off . also used a different port . nothing , still says "device offline "

I also ran the Cyndia impactor " # start telnet as system on port 2222" just to test And it gives mW and error " signature bug unavailable"

Thanks

---------- Post added at 06:05 PM ---------- Previous post was at 05:50 PM ----------

After a while on google it seems I do need to update to adb 1.0.31. Now I just can't find answers on how to do that !!

Thanks for any help - advice
[Moto X Original Android Development] 640k:
if you're on step 4, you're not running cydia/telnet. you're installing a script and setting the uevent to run it at startup.
[Moto X Original Android Development] Blanko6:
Yes, I understand on step 4 there is no need to start Cyndia but I did it to see if it would connect .

But still ,

Adb shell

Error: device offline
[Moto X Original Android Development] 640k:
cydia won't work on 4.4 because the exploit doesn't exist. you won't get a connection anyway.

if you're having ADB problems, make sure you're using a USB 2.0 port, instead of USB 3.0. my script has adb 1.0.31 bundled with it. you can run step 4 automagically from the advanced menu.
[Moto X Original Android Development] Blanko6:
OK so cydia makes sense .

Not sure what to do then because if I

Adb version

Android debug bridge version 1.0.26

I have tried every port in my PC .

Is there any test I can do to see if I did something wrong.

my bad, realize im talking to 640k, ok so on the script option 8 then option 6 or 9?

thanks

Thanks again
[Moto X Original Android Development] Blade765:
I finally got it to work without any further issue. I overlooked the fact that that libe had to be removed from the .xml file. All is well now. I officially have root with android 4.4 installed on my Droid Maxx!!!!!!!

I've said it many times before, and I am sure I shall say it again, but YOU ARE THE MAN!!!!!!

Many Thanks!
[Moto X Original Android Development] lowvolt1:
Thank you for your appreciation.

Glad you got it working.

Slapped the sh*t out of my X
[Moto X Original Android Development] Pr0f_Farnsw0rth:
I'm encountering the same issue. I took the OTA and then tried to run the shell commands and I get the "Permission Denied" response. Any ideas? WP is off/0.
[Moto X Original Android Development] lowvolt1:
After OTA did you re enable USB debugging?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] timmay54:
find sdk manager in your computer and update the 4.4 api, it will give yiu the correct adb. Thats what i had to d

BTW THANK YOU TO ALL THAT HELPED ME STRUGGLE OMG love the kitkat that is now rooted :)
[Moto X Original Android Development] lowvolt1:
Got him dialed in last night. :D

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] nevrozel:
Glad it worked for you in the end, but could you please tell us how exactly did you do it? Because I think am I in the same exact situation:

- I am on 4.2.2 camera update rooted

- MotoWPNoMo is succesfull and write protection is off

- I reflash 4.2.2 camera update second time (I think there is a problem here? see below**)

- I run Cydia Impactor first run

- I run puttytel first run -> 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

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 Original Android Development] lowvolt1:
Obviously write protection is not disabled

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] lowvolt1:
Instead of using the toolkit just run the programs

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] elesatz:
Bootloader No Longer Allowing Downgrade to 4.2.2?

I took the OTA a week ago. I am really annoyed with the lack of KitKat text wrap and tried to downgrade back to 4.2.2. It looks like the bootloader is no longer allowing the downgrade. Anyone else seeing the same issues?

writing 'boot'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 2.070s

sending 'recovery' (10240 KB)...

OKAY [ 0.920s]

writing 'recovery'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 2.090s

sending 'system' (786432 KB)...

OKAY [ 49.449s]

writing 'system'...

(bootloader) Preflash validation failed
[Moto X Original Android Development] lowvolt1:
Did you remove the get var line from the xml?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] hanifaz:
Please Post a Youtube Video for Root 4.4

I have spent hours and hours trying to follow all the instructions, but i am getting an error when using the impactor that the bug is not available.

I am very good with computers and rooting.

thanks
[Moto X Original Android Development] lowvolt1:
If you still need help in the am, I will help.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Dark9781:
If you are on 4.4 the bug will not be available. You need to be on 4.2.2.

Sent from my Moto X on KitKat
[Moto X Original Android Development] hanifaz:
root 4.4 bug unavailable

Is it not the purpose of the thread to root 4.4 not 4.2.2?!

It should be part of the instructions how to downgrade.

---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------

I need help badly my friend, thanks

I am on 4.4 now and I don't know how to downgrade to 4.2.2 and what to do after that
[Moto X Original Android Development] lowvolt1:
Okay. Download rsdlite. What phone and carrier are You on?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] syntrix:
http://xdaforums.com/showthread.php?t=2446515

But use the download in the first post here, not the return to stock guide.

Yes, some stuff isn't perfectly clear, but it works. You flash to 4.2.2 the second time as the write protection is gone and the last portion will fail if you have root. Just follow the instructions (like I should have weeks before) :) :)
[Moto X Original Android Development] Eighthourblink:
Having trouble with the command at the end --- echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper. Its not auto rebooting?

Im in shell on the command Prompt . Turned on bluetooth. and my device is online ( accepted to RSA request)

Any Suggestions?
[Moto X Original Android Development] lowvolt1:
You don't need to worry about auto reboot. Just reboot manually either with adb reboot or by pressing power button.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Eighthourblink:
i manually rebooted my phone, run the other echo command, but still dont have root access
[Moto X Original Android Development] lowvolt1:
Did you install supersu from chainfire?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.

---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------

Run all the shell commands one at a time. Then reboot.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Eighthourblink:
Yes i did. cant use it because i dont have root access
[Moto X Original Android Development] lowvolt1:
Have you already rooted with rockmymoto and ran motowpnomo?

I hate to say it but if it were me I would flash back to clean 4.2.2 and re run slapmymoto. Provided your write protection is off

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.