yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] dobbs3x:
I think so. I went from 4.2.2 w/ OTA and reverted with toolkit to 4.2.2 pre OTA and then did the 4.2.2 OTA (the phone dloaded it through motorola software update in settings) and I am bricked. So I dont know. I am downloading the 4.2.2 camera OTA to see if it will flash and unbrick me. If it were me I would not attempt a downgrade to stock in any form to be safe unless someone with more knowledge can come in and help clarify what might be going on and how to prevent this.
[Moto X Android Development] Blitzpwnage:
Which one is the camera?
[Moto X Android Development] dobbs3x:
Okay I am back online. Booted into the rom. Used the ghost_sprint-user-4.2.2-13.9.0Q2.X-116-MX-17-57-1-1-release-keys-cid9.xml.zip file from http://sbf.droid-developers.org/phone.php?device=0 in the moto x toolkit, it was giving lots of erros during the flash but I had it reboot to bootloader when it asked and it showed unlocked bootloader status 2, decided to try to boot the rom and it booted :)

*update, looks like its hanign on hands free activation, so its not all good yet....

---------- Post added at 05:25 PM ---------- Previous post was at 05:22 PM ----------

Android 4.2.2

Blur_Version.139.14.1.ghost_sprint.Sprint.en.US pretty sure it was that one, just be carefull cause my radio is not working i dont think.

---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------

ok I was getting no bars on cell so I connected to my wifi, did a profile update, it rebooted and now I have signal and activation went through. So I think all is good so far...
[Moto X Android Development] AbstractXart:
Let us know if you get your radio to come back on or not!
[Moto X Android Development] dobbs3x:
Its back on. I am writing this from my moto x now over 4g and have sent a SMS and made a call.
[Moto X Android Development] MichaelMcEntire:
Just got home from work, anyone still need it?
[Moto X Android Development] Blitzpwnage:
Looks like it's back up on the site so we are all good thanks though!!!

Are you able to update to 4.4 after the rsdl back to the camera update? Don't really want to brick lol
[Moto X Android Development] dobbs3x:
To sum all this mess up...

Using Moto X Toolkit you can use the Android 4.2.2 Blur_Version.139.14.1.ghost_sprint.Sprint.en.US file located @ http://sbf.droid-developers.org/phone.php?device=0 to revert to stock 4.2.2 with the OTA camera update. The above file will actually be named ghost_sprint-user-4.2.2-13.9.0Q2.X-116-MX-17-57-1-1-release-keys-cid9.xml.zip once downloaded. The big thing to watch is that it is 17-57-1-1 in the file, this is the once with the camera 4.2.2 firmware that will work.

I am also putting this file in my google drive in-case of another nuclear meltdown like we had earlier... Happy Flashing! And Meery X-mas. Oh and after I got this reverted I just put the 4.4 ota zip from this thread OP in /sdcard and it flashed successfully. I am now on kitkat 4.4 on my moto x.

here is my drive share with the ghost_sprint-user-4.2.2-13.9.0Q2.X-116-MX-17-57-1-1-release-keys-cid9.xml.zip[/B https://drive.google.com/file/d/0Bzxa9OQnvkcbY1otQWhhY0EzM00/edit?usp=sharing
[Moto X Android Development] angelriathica:
Exactly which file and how u flashed..I get security error when flashing

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

Do u need to unzip

---------- Post added at 03:08 AM ---------- Previous post was at 03:03 AM ----------

I'm getting access denied when using toolkit..flash back to stock option
[Moto X Android Development] CaliMark1:
Weird why didn't the update go this smooth this morning at 5am causing me to almost brick my phone and freak me out! I am now upgraded to 4.4 KitKat as well!

No more phone for today!

CaliMark

MarkReed
[Moto X Android Development] dobbs3x:
No leave it a zip place it in the toolkit return to stock folder and run the toolkit. If I think that's what you need.

---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------

4.4 seems smooth butter. The new camera is nice. Cab stay the circle around to set exposure. And diaper now finds congrats when you spell their name.
[Moto X Android Development] angelriathica:
Man...thanks work out good..good
[Moto X Android Development] tjeeeeee:
Do you still have unlocked bootloader as well as root?
[Moto X Android Development] dobbs3x:
I still have unlocked boot loader. I haven't done the root for kitkat yet. Don't think I will though. There is a kitkat root in the original android Dev forum FYI
[Moto X Android Development] AbstractXart:
So I rooted 4.4 and installed xposed framework and gravitybox. I then realized that ART running system wouldn't work anymore after I installed it. So now I'm trying to figure out how to unroot and remove all of xposed so I can get ART to work again.

Does anyone have a flashable ROM of 4.4 unrooted that actually works instead of the one in the OP?
[Moto X Android Development] dobbs3x:
No 4.4 Roms for sprint yet that I know of. The only option I think you have is to revert to stock firmware like we all just did or stay with what you have and use dalvik until xposed supports art. Which may never happen as he needs the source.
[Moto X Android Development] gokart2:
file "/system/etc/install-recovery.sh" doesn't have any of expected sha1 sums; checking cache

That's the problem. TWRP put a different file in this place. Usually it just copies the original and names it as a backup. If you remove the .bak and put it where it belongs, when you reboot the phone it will revert back to stock recovery. More or less, Android put this file there, if you flashed a custom recovery and didn't delete this file, or add the .bak to it, it would install the stock recovery on the boot up. TWRP started automagically doing it, but I didn't realize the put a different file it's place.

I'm glad you guys are getting somewhere. I'd have one done but I can't download it. And, I'm betting the firmware will be required to run the rom, so I don't know if it'll work or what will happen if you flash it while running 4.2.2. I WISH you could update the firmware via a way similar to HTC. I have tomorrow off, so I'll try to find a PC that I can DL from.
[Moto X Android Development] AbstractXart:
So what would be the necessary steps I would need to take to get back to stock firmware? I just followed the entire debacle that happened today and don't want that happening to me. I just want to be running ART. It would be greatly appreciated if you provided a quick guide on how I could get back to pure stock 4.4.

Thanks
[Moto X Android Development] magui43212:
Alright I've been running KitKat for a few hours now and it was great. Then it froze and it won't boot up now. It does the boot animation then shuts off. great.
[Moto X Android Development] dobbs3x:
Did you install xposed or root the device?

Maybe try wiping cache in recovery.
[Moto X Android Development] magui43212:
No, it isn't rooted, but I did have ART enabled. I did get TWRP installed and wiped the cache. That worked (so far).
[Moto X Android Development] tjeeeeee:
thanks [MENTION=3380378]dobbs3x[/MENTION] and everyone else, successfully on 4.4 now still with unlocked bootloader, no issues along the way either!

---------- Post added at 06:54 AM ---------- Previous post was at 06:54 AM ----------

thanks [MENTION=3380378]dobbs3x[/MENTION] and everyone else, successfully on 4.4 now still with unlocked bootloader, no issues along the way either!
[Moto X Android Development] gokart2:
Has anyone tried flashing back to 4.2.2 via backup, or the stock Sprint ROM yet? If so, does it work, any issues?
[Moto X Android Development] joda08:
OK thought I'd lay out how I did the update.

First I used the this tool to flash back to stock. (Including stock recover)

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

After that I did the ota update(the previous one with some small fixes on 4.2) then I downloaded this on my PC(pretty sure if you download it from your phone it won't be named correctly) and copied it over to the base of my SD card. When you click the "check for updates" button you'll get the message in the picture I attached. click copy and then when it's file click install.

Hope this is helpful to someone

Edit: if you download it from your phone and manually move it to your SD card rename it to this

Blur_Version.143.44.8.ghost_sprint.Sprint.en.US.zip

And it'll work.
[Moto X Android Development] JasonK75:
So from what I have read it seems that if you have a stock Moto X (not rooted and bootloader locked) you can put the file from the OP on the /SD and flash through the "check for update" but if you have ever rooted or unlocked bootloader you'll get major errors - soft and hard brick - sound about right?
[Moto X Android Development] tjeeeeee:
Well you just have to make sure you use the toolkit to flash the right firmware, bootloader doesn't matter and once you're on 4.4 you can flash twrp and get root, it worked fine for me. For stock just I load the zip to the root of the phone amen check for update
[Moto X Android Development] Kanomy's Ball:
I seemed to have followed the process but had still got hard brick... Anyone have any suggestions on what to do with a hard brick with this device in this situation or any situation for that matter?
[Moto X Android Development] dobbs3x:
If the phone can't turn on and \or you can't get into recovery I don't know what to do. Make sure the phone is charged if it won't turn on. If it turns on then there may be hope. And by turn on I mean any sign of life like at least so blinking lights or the boot loader screen.
[Moto X Android Development] tsalate:
I have never seen so many have this much trouble flashing anything since the early G1 days. Here is what I did. Downloaded the update zip. Put on root of sd. Went to settings search for update. It copied and failed. Was stuck on unlocked bootloader screen. Held down volume down and power. Got back to bootloader. Went to tool kit. Returned to stock. Then the ota. Both in the tool kit. Fastboot flashed Blur.Version.143.44.8 zip from OP. Fastboot reboot. 4.4 with no problems. Hope this helps

Also I was completely stock when doing this. Unlocked bootloader right before I tried to update.
[Moto X Android Development] dobbs3x:
Most of our problems was do to not having access to the 4.2.2 ota firmware because the host server crashed and it took a couple days for it to come online. After getting that firmware everything is easy peazy
[Moto X Android Development] tsalate:
Cool. I never really saw much of a need to root the x. It was one if not the only device I ever had that I didnt root or unlock. 4.4 might make it a little better. Going to test it for next week.
[Moto X Android Development] shaqqq:
This is the real official KitKat update right? The one that's being pushed out
[Moto X Android Development] abiezer:
That is correct.
[Moto X Android Development] abiezer:
I updated the OP explaining that this method works only with stock firmware. If you have rooted or unlocked bootloader, you must reflash the previous update.
[Moto X Android Development] gokart2:
All this firmware this firmware that make no sense to me. Firmware is generally drivers or hardware code changes like touch screen, modem, radio, Bluetooth, or changes to device sensors. More or less it would be easier to say you need to be fully stock, no root, or system changes. According to Motorola, unlocked boot will still allow update.

Edit: After rereading this I realize I sound like a ****. Thats not what I meant. I mean there is something goofy and I can almost guarantee there's an easier way to do an update.
[Moto X Android Development] webby_s:
Right, there has to be an easier way. we on Sprint though must be losing developers or just never had any to begin with cuz personally if someone made a flash zip for this update I'd defiantly buy them a beer two.

I follow peoples instructions but for some stupid reason I can't get the toolkit to work on either of my Windows machines
[Moto X Android Development] abiezer:
I'm at a training today but I'll figure this out.
[Moto X Android Development] gokart2:
I'm at is as well. I'm pretty good with this crap, it's just I don't have internet through a wire and my work PC won't allow much.

I found that I cannot update PRL, I get an INTERNAL error. Then tried updating profile, got an ACTIVATE_OTA_APN

Thought I could do this and did do it while rooted.

Since then I've had "modem" (radio) issues, turns on and off constantly.

Edit: Dalvik and cache wipe fixed PRL and Profile issue.

What files are in the OTA update you posted, anything close to this or including these files?

Are there files simular to this in the FIRMWARE download file?

VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV

bootloader-#####-####.img
flash-all.sh
flash-base.sh
flash-all.bat
image-########.zip
*radio-#####-###_####_####.img

---------- Post added at 03:46 PM ---------- Previous post was at 03:37 PM ----------

And I'm a tard. This is an incorrect statement ^^^^. TWRP saves the factory/stock recovery in system/recovery-from-boot.bak. If you just remove the .bak, it SHOULD restore stock recovery on a reboot. The /system/etc/install-recovery.sh issue I believe to be SuperSU related as it refers to SuperSU in the file and how it should be launched/ran.

---------- Post added at 04:21 PM ---------- Previous post was at 03:46 PM ----------

THIS may help.

Even though they don't have a factory image for Sprint devices, it should work the same if we can dump these files and fastboot flash. Data will likely be gone.
[Moto X Android Development] tsalate:
Try running it in compatibility mode for XP service pack 3. Im assuming you're running Win7 or 8.
[Moto X Android Development] gokart2:
So.....It seems like it's been a week that I've tried to DL the dump. Kept failing, or I would have to leave the WiFi place do to work or kids or wife and it would fail, etc. Found I could "star" AL's download, and it would save to my Google Drive. Halfway through my wife calls. And I get yet another failure screen. Almost lost it. Thank the lord when I hit retry it continued from where it failed! At first, the MB counter made it seem like it was downloading to the device. Finally ~690MB later I find it was just the transfer from AL's drive to mine. Started tearing (LOL.....almost). Found the "pin" for offline use and have it downloading to the phone now. I did a test run earlier real fast to find where it saves and it was right where I thought. HOPEFULLY this will work and I can start the TWRP flashy tonight and have it up tomorrow. I also have presents to wrap, but that shouldn't get in the way. Next time it may be quicker if someone buys a 1MB card, puts the dump on it (LOL), and sends it to me. Not sure if I should pre-root it or leave it stock?
[Moto X Android Development] Kittiesoncrack:
pre-root would be great
[Moto X Android Development] webby_s:
I don't want to 'hi-jack' the thread and turn it into a toolkit questionnaire but ya I've done that and followed instructions on youtube to no avail so far. Do I want to make it work for my flashing addictions? Yes, so I will keep at keeping at it. (windows7 btw)
[Moto X Android Development] dobbs3x:
What I'd not working exactly. Does it open up? Should be a command prompt with options to enter.
[Moto X Android Development] webby_s:
I think this was more directed to me... I (just to cover my a $$) try taking a screenshot to see if I get results and it always says something about wrong path or no file found or something ... I then tried backing up all apps, data, sdcard and it seems to be doing that... So I feel better and more confident that it's connecting to it now... Like I said I just originally tried that screenshot and maybe it busted and I didn't know it but the back up is going now so I will try what others have said... back to complete stock then go from there.
[Moto X Android Development] CaliMark1:
Just curious it still sounds like the OTA update is slowly rolling out from sprint? I updated my phone with instructions here! But, I am still waiting for the update to show up on my mom's phone. Any comments on who as seen it yet?

Thanks,

CaliMark

Mark Reed
[Moto X Android Development] webby_s:
K I've gotten to here.... then in stock recovery the blur_Version errors out then reboots to 4.2.2 (it's doing it all it self)

Someone else said to fastboot flash the blur_version in the op. do tell how... I thought you could only fastboot .img are you talking about fastboot flash the boot.img?

So to edit cuz I was tired last night doing this, I am at work all day and the only way I can do anything today is from the phone so any help would be appriciated.

I am on OTA w/camera update, stock recovery. The OP's flashable zip is on my SD card that I downloaded to a computer then transfered to phone. Update is seen by phone, asks to update, I say copy.. then install... boots into recovery starts the update then errors out and boots back into 4.2.2
[Moto X Android Development] gokart2:
I need abiezer or someone to please verify the md5 checksums of these two files in the 4.4 dump. After all the issues I've had downloading, I want to make sure its not bad before building.

System.img.ext4: 441d3014473df6bd2373457b50661975a

Boot.img: 647008085224a56c0d19478d6c6a78ac
[Moto X Android Development] roguejam:
Boot, yes. System, you have an extra 4 at the beginning. Typo?

My checksums are

41d3014473df6bd2373457b50661975a System.img.ext4

647008085224a56c0d19478d6c6a78ac Boot.img
[Moto X Android Development] Willieumm:
I did get the update to flash with my bootloader unlocked. You need to run the toolkit in compatibility mode of you're on Windows 8. Also make sure you extract the firmware files into the folder you're trying to use whether it be the toolkit or one of the other .bat kits. They will not flash if left in the .zip.
[Moto X Android Development] gokart2:
So I managed to corrupt my data partition somehow. I cooked the rom from the dump. Made it just like the last one, same updater-script, SU, etc.... Loaded it to sdcard, went to fastboot and flashed the updated TWRP recovery for 4.4, rebooted to bootloader, booted to recovery, wiped system/data/dalvik/cache, and flashed. Got an error as I expected, usually the first couple tries require some fixes. Since I wiped everything I had to revert to my backup I made just before doing all this (I should have tried flashing without wiping for this reason). Tried restoring and TWRP froze, then auto rebooted, then went bootloopy on the unlocked boot screen. Got back to recovery and tried wiping individual partitions, and flashing individual partitions multiple times and data made it get loopy every time. Tried fastboot formatting and erasing data partition and it returned an error (bootloader something remote failure)? Nothing "I" did would have touched the data partition. Recovery had something to do with that. I think one of our main issues is recovery not really being updated or tested with our devices by a recovery guru. ATM I think we're best to revert to stock and put the OTA on the SD card, etc. I'm still working on things but it'll be awhile.
[Moto X Android Development] gokart2:
:good::highfive: Thanks, didn't see this till now. If it's only off by the first digit (4) it's likely a typo, I did it via phone and remembered having an issue with pasting the checksum. Likely part of the "ext4" got included and I thought I pasted ON the 4, erasing it. Usually if the files bad it's more then one off.
[Moto X Android Development] btaylor545:
So if I'm rooted right now and I unroot and go back to stock and update and what not to 4.4 is there a way to root 4.4 yet?
[Moto X Android Development] gokart2:
I'd assume its just like anything else, fastboot flash custom recovery, then install superuser via play or recovery.

---------- Post added at 01:32 AM ---------- Previous post was at 01:00 AM ----------

Also.... I hate to say it but I think this update may be enough of a change that it'll be next to impossible to flash from 4.2 to 4.4. All over I've been seeing stuff like

THIS

. Thats from one of the guys who is our firmware saviors. Not sure if it will be or even can be fixed, but in their current state, custom recoveries can't handle both, its one or the other. Plus by not taking the ota your missing out on radio/modem updates, as well as other hardware coding updates. IDK, that's my opinion.

I'm reluctant to update as I have kk on another device and am more fond of holo blue and JB. Has anyone who actually got on kk tried RSD/scripting back to 4.2?
[Moto X Android Development] ziggysmalls:
I called Sprint customer service yesterday and the agent had documentation that said the Android 4.4 update would go out to 1,000 users on 12/12 and then the greater rollout would go out to the rest of the users on 12/18. It looks like those who have been waiting will get theirs today.
[Moto X Android Development] JasonK75:
Still waiting. :(

And now I have it! :)
[Moto X Android Development] Kanomy's Ball:
So I got my new Moto X today(finally). From completely stock out of the box with the OTA installed, have we figure out if it is safe to just put the 4.4 update on the SD, check for up and then install?

-I am pretty ballsy
[Moto X Android Development] webby_s:
Yep, do it... you'll be fine!

Got mine back to stock everything then put update on SD card and it found it and installed..... 4.4 glory
[Moto X Android Development] AbstractXart:
I dont know if this helps at all, but I was on 4.4 and reverted back to the 4.2 OTA via the toolkit. I was skeptical I'd get into a bootloop but it actually worked just fine. I than upgraded back to 4.4 because a noticeable difference in the smoothness. I did this by putting the zip in the OP back into my SD card and then rebooting and "check for system update".
[Moto X Android Development] Kanomy's Ball:
This might seem like a silly question but I am taking every precaution to not brick this new X like I did last week... I download with computer to ensure correct file name, copy to sdcard, check for update, then it asks to copy the package in order to install(or you the option "later" or "no thanks") when copying is done choose "install now". Correct?
[Moto X Android Development] webby_s:
Yep, sounds about right! That's what I did. You should be fine.
[Moto X Android Development] Kanomy's Ball:
Success!!

The beautiful world of 4.4 has been installed successfully with absolutely no hassle... Why my new stock Moto X worked with out a hick-up and my previous stock Moto X wanted to hit ever hurdle in the way I will never know but this definitely works... Oh the age of tiny computers
[Moto X Android Development] gokart2:
It helps! So u were on 4.4, then did a firmware restore to stock with the 4.2 firmware and it took? Afraid to try anything too crazy without the 4.4 firmware. I thought you could only RSD/firmware flash script the firmware of the current got.bin/motoboot.....?

---------- Post added at 04:45 PM ---------- Previous post was at 03:46 PM ----------

I put the OTA zip on the root of my sdcard and when I checked for updates it found the OTA and began downloading, so I think you called it.:good:
[Moto X Android Development] ziggysmalls:
Mine is downloading now too.
[Moto X Android Development] btaylor545:
Is anyone rooted with kk installed If so can you share your process? I want to update but need for four wifi tether for work
[Moto X Android Development] tjeeeeee:
Yes rooted with kit kat, is your bootloader unlocked?
[Moto X Android Development] gokart2:
Put SuperSU on your sdcard. Enter bootloader and fastboot flash recovery. Fastboot reboot-bootloader. Then manually choose recovery. Get to recovery and flash SuperSU. Reboot and enjoy.
[Moto X Android Development] abiezer:
I have a stock deodexed zipaligned rooted and busybox ROM almost ready to share with you guys. Let me know if you guys have any request. This is my first ROM EVER, so take it easy on me.
[Moto X Android Development] gokart2:
Good job! Was planning on going another round tonight, guess now all I need to do is a stock odex. Would you mind if I used your build/link/info in my thread?