yashsingh1/xdaforums huggingface dataset:
[Moto X General] r_diaz13:
Thanks [MENTION=1165307]KidJoe[/MENTION]. I'm actually soak testing 5.0.2 straight from Moto. I have the 5.1 ota captured already just can't get it to work
[Moto X General] KidJoe:
IF you were invited by Moto for the MFN testing, and the files they sent you do not work, then I suggest you work with Moto directly to resolve as they know what was pushed to your device, and should be pushing the right files to you.

If what they sent you doesn't work, they need to know so they can make sure it doesn't happen to anyone else.

Another option... would be to attempt to side load the 5.1 they sent you via STock Recovery. It will tell you exactly why it errors... (see the side load instructions at -> http://xdaforums.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079 )
[Moto X General] jmcdonald58:
Thanks

I guess somewhere along the line I flashed a leak build of 4.4.4 could not take 5.1 update without getting and error followed instructions Option 5 here http://mark.cdmaforums.com/MotoX-ReturnToStock.html and update went off without a hitch took me awhile to fine theis thread and firmware till I got here good thread and most useful for me ---Thanks
[Moto X General] guruehsaan:
so guys I've got the at&t XT1058 variant and currently residing in the UK. Unlocked to all networks, rooted but a locked bootloader. I thought I was already on stock ready for the lollipop OTA but then someone on G+ told me this:

"if you've rooted on a locked bootloader, you're either below 4.4.4 or you have flashed a modified system image. In either case, it is recommended to go back to stock before taking the OTA which yes, you will receive regardless of your current location or network.﻿"

Is this guy right? and if he is do I still follow the same procedure as 'whizinc' proposed in the first post in this thread?

and I've attached screenshots of what I'm currently on
[Moto X General] tormin:
Yes he is right. Even with an unlocked bootloader installing SuperSU modifies /system. It's just easier to get root back after the update with the unlocked bootloader. The safest option for installing the OTAs is to flash to stock first. But there's no guarantee you'll be able to get root back.
[Moto X General] KidJoe:
If you have a LOCKED Bootloader, before you take ANY OTA, you need to decide if ROOTING is necessary or not. If you *NEED* Root, then do not take the OTA until after someone has put out a root process for it.

There is a link in my signature to a post which will have some additional information and conditions when preparing for an OTA.

But yes, the steps in the OP are a good way to get back to stock (i.e. flash stock SBF using RSDLite)
[Moto X General] guruehsaan:
Thanks tormin and KidJoe for the swift advice. If I do get back to stock will my phone be back to being locked to one carrier(at&t)? Or will it remain unlocked to all networks?

Just to clarify, my phone is rooted but with a LOCKED bootloader.
[Moto X General] whizinc:
If your phone was network unlocked through a Sim Unlock Code then it will never ever get lock again, AFAIK. Do you know how you unlocked all the networks?
[Moto X General] guruehsaan:
Hey whiznic, I bought the device from ebay, from china and the seller unlocked it and i have no clue how he did it.
[Moto X General] whizinc:
Yeah i think you'll be good to go for flashing probably.. Most of the people do the sim unlock from the unlocking device so the device does the permanent unlock AFAIK. But still take extra precautions. :)
[Moto X General] KidJoe:
As [MENTION=5782800]whizinc[/MENTION] said, if it was SIM Unlocked (aka Carrier Unlocked) by entering the code, you should stay unlocked after flashing.

As for ROOT, that is another matter. To further clarify what I said before, since you have a LOCKED Bootloader, you will lose root when you reflash, or take an OTA. And any updates will likely patch the exploit used to root. Therefore you wont be able to root after you do any updates.

And yes, the only way to root an ATT XT1058 on 4.4.4 without unlocking its bootloader is to flash a customized image, which means you phone will fail the OTA's pre-flash validation check, so you'll have to flash back to 100% stock to take an OTA, again losing root.
[Moto X General] timmytucker718:
I have xt1053 dev edition. Unlocked bootloader, rooted, with xposed installed.

Will I receive the OTA? If not, what do I need to do to get the OTA?

Thanks!
[Moto X General] whizinc:
If you are still on the stock recovery and you haven't changed any thing in the system of your phone you will receive the OTA and it will be installed correctly. If you have messed up the system files still you will receive the OTA but it will get failed to install because the changes of recovery system files etc. But since you have installed Xposed and xposed modules do change the system files, so i guess you have to follow the steps in the OP to get back to stock completely. And also you will lose root. But you can get it back anytime since you have an unlocked BL.
[Moto X General] KidJoe:
see the link in my signature :D
[Moto X General] timmytucker718:
Thanks. I read through that and just need some clarification so I don't brick my phone. As I stated, bootloader unlocked (via motorola), flashed Superuser through twrp, I have xposed installed.

So, to update, I need to flash default recovery and uninstall xposed? What If I wait till a copy of 5.1 is available on the internet? Then what? Can I just flash it using TWRP? Or would I need to use stock recovery for this update method too?
[Moto X General] KidJoe:
Apparently you didn't read (THIS) close enough...

Flash Default recovery (explained in item #8) and disable Xposed (explained in item #7) and uninstall it, since a newer version of Xposed is needed for Lollipop (also Item #7).

Now, if you read those and didn't understand, please suggest a better way for me to word it.

As for waiting and flashing via TWRP, if someone makes a backup, sure you can RESTORE that, but it will likely skip parts like GPT.BIN, parts/all of Motoboot.img, modems, and stuff which has its issues/disadvantages. Its covered in -> http://xdaforums.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 (see item #11 and 13) Further, if its a backup for another model/carrier, there may be things in the build.prop that need to be tweaked.
[Moto X General] zmore:
OTA Failure anecdote

My wife's XT1053 (t-mobile) got the ~600MB 5.1 OTA update last night, but after downloading it and attempting to install, it aborted for some reason, leaving it at 4.4.4. Her phone is bootloader unlocked, rooted with stock recovery and bootloader 30B7, with the only /system change being etc/hosts for adblocking, afaik.

Anyway, I adb shell'd into the phone wanting to find the OTA image, since I couldn't use 'About phone > sys updates' to get the OTA notification to show again, but it seems to have been deleted upon failure.

FWIW here's some relevant snippets from the /cache/recovery/last_log.x during the update.

Starting recovery on Sat Jun 13 01:59:37 2015
...
Parsing the directoryd_name: ..
Command: "/sbin/recovery" "--update_package=/cache/Blur_Version.213.44.1.ghost_row.Retail.en.US.zip" "--locale=en_US"
...
ro.com.google.gmsversion=4.4.3_r1
ro.mot.build.customerid=Retail
ro.boot.radio=0x6
ro.boot.bootloader=0x30B7
ro.boot.write_protect=0
ro.build.fingerprint=motorola/ghost_retail/ghost:4.4.3/KXA21.12-L1.21/23:user/release-keys
ro.product.model=XT1053
ro.product.device=ghost
...
Finding update package...
I:Update location: /cache/Blur_Version.213.44.1.ghost_row.Retail.en.US.zip
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/platform/msm_sdcc.1/by-name/system , file system type :ext4script aborted: Package expects build fingerprint of motorola/ghost_retail/ghost:4.4.4/KXA21.12-L1.29.1/2:user/release-keys or motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys; this device has motorola/ghost_retail/ghost:4.4.3/KXA21.12-L1.21/23:user/release-keys.
Package expects build fingerprint of motorola/ghost_retail/ghost:4.4.4/KXA21.12-L1.29.1/2:user/release-keys or motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys; this device has motorola/ghost_retail/ghost:4.4.3/KXA21.12-L1.21/23:user/relea
E:Error in /cache/Blur_Version.213.44.1.ghost_row.Retail.en.US.zip
(Status 7)
Installation aborted.

Not quite sure why it aborted, but I'll get back to a clean(er) slate, and try again later.
[Moto X General] vandrem:
I received the OTA message on my rooted 4.4.4. I used this thread to revert to the standard image and everything went fine. However, I checked for updates and it is indicating that nothing is available now. Will this eventually show up?
[Moto X General] timmytucker718:
Just a tip for you all. The stock ROMs from Motorola's website (which are hosted on other 3rd party sites) DO NOT COME WITH THE XML FILE. You can't use rsdlite without this. If you have one of these versions, your options are a) create your own XML or b) use the included .bat file to AUTOMATICALLY flash via fastboot.

Hope this helps.
[Moto X General] KidJoe:
It failed because....

In other words, you still have a 4.4.3 rom on that phone, and the OTA is looking for 4.4.4.
[Moto X General] zmore:
Yeah, I figured that much out. I was just initially confused because I hadn't touched the phone in almost a year, and 'About > version' reported itself as 4.4.4, even though the ROM version was actually 4.4.3.

I used your older guide's "option 5" -- thanks -- to find and download the 6-month-old 4.4.4 stock ROM from a sloooow source (but faster than waiting on motorola), then used an old mfastboot linux version to update everything non-destructively, and manually updated to the 5.1 OTA in stock recovery using 'update from SD card' using the OTA image someone uploaded to google drive in your thread.

sha256sum of the GSM OTA, FWIW:

f8843c724acff48ece68891d144f56627c87e9bfc030d3c349a763adeb98b32f Blur_Version.213.44.1.ghost_row.Retail.en.US.zip

All good. I haven't bothered to re-root yet, since the wife hasn't complained about ads, but I've got the newer TWRP and SuperSU ready to go.
[Moto X General] vandrem:
Sorry to repeat this question but Its been several days now and Im not sure what to do. I receive the OTA message on my rooted 4.4.4 phone and followed the instructions on this thread to go back to stock. Now I am not receiving the OTA message. Anything I can do?
[Moto X General] whizinc:
Factory Reset your phone one's and log in to play store, update Motorola update services and all motorola apps.. You will receive the OTA eventually.. AFAIK, meanwhile our Moto X god [MENTION=1165307]KidJoe[/MENTION] ;) can put more clear light on this situation.
[Moto X General] whizinc:
and really sorry for the delayed reply, i was really busy setting up my new computer. Sorry again. :)
[Moto X General] KidJoe:
What model is your X and who is your carrier?

I haven't been paying attention lately, so I don't know if the official push of 5.1 has started, or not, so bear with me here...

IF you were invited to take part in the MFN tests or soaks, and factory reset AFTER they pushed it to you, but before you applied it, you likely wont get the OTA again. They warn of this when you accept. Its a one time push. It does not retry. Usually Moto sets up a private area to discuss the tests, you could try asking there if they can re-push it to your phone (usually they wont).

If you are getting notified of a regular OTA, and factory reset before you apply it, it may take some time before you are prompted again. After fully setting up your phone you may be able to hit "check for system updates" to pull it down rather than waiting, but most often you just have to wait, especially if its the early stages of the roll out.
[Moto X General] vandrem:
My model is xt-1053 dev edition. My carrier is Cricket (Owned by ATT). I never installed the OTA update but I know it did download to my phone and then kept prompting me to install it. I've checked System Updates multiple times but no luck. It said nothing about being a test so I believe it was a traditional rollout. If I'm reading your response correctly then I should get it eventually OTA but I might have to wait?
[Moto X General] KidJoe:
Correct. IF they are starting to roll it out to everyone, then they are doing so in waves.. you missed your turn so to speak, so you'll have to wait.
[Moto X General] enjoimadcow:
Hello. XT1053 here. Just flashed back to stock 4.4.4 from CM12.1 using the image directly from motorola. Everything is working as intended except I don't get LTE anymore on att. I am just connected to HSPA. Any ideas of why this is happening?

Edit: nevermind. LTE kinda magically appeared after about an hour. Not sure why.
[Moto X General] whizinc:
Sometimes it gets a little of time to get everything back to normal after a fresh Rsd lite flash.. Glad that you got LTE back..
[Moto X General] ajsonofgod:
Can i do it with my unlocked boot loader?

Sent from my XT1052
[Moto X General] whizinc:
do what?
[Moto X General] ajsonofgod:
Receive ota. I am on 4.4.4 aisa retail version but with custom recovery (twrp).

Sent from my XT1052
[Moto X General] ryzilla23:
Nope. You cannot receive the OTA with a custom recovery. The unlocked bootloader doesn't matter, but you will have to return to a stock recovery.
[Moto X General] ajsonofgod:
If i get stock recovery then will the update also update my bootloader??

Sent from my XT1052
[Moto X General] whizinc:
If you Do An RSD LITE flash as mentioned in the OP. You will be on the way to receive the OTA. As for now, You are on a custom recovery so THERE IS NO way you can perform the OTA. If you put the stock recovery back and perform the OTA, Yes it will update your bootloader to the latest OTA you received.
[Moto X General] ajsonofgod:
So i have to only get back to stock recovery amd sideload the ota then. It will be the best option right.

Sent from my XT1052
[Moto X General] whizinc:
Yes precisely!
[Moto X General] ajsonofgod:
Then i will wait for asia retail ota and then try to sideload it with stock recovery.

Sent from my XT1052
[Moto X General] MaRz0o:
I successfully flashed back to stock with the XT1053_TMO_RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip using RSDLite. Now after the reboot process, my phone doesn't recognize that their is a 5.1 OTA update anymore. Should I try to reflash back to stock again?

SOLVED: Had to log into my Google account and update Motorola Update Services.
[Moto X General] s3ars:
On my device I'm in Fastboot and it says "USB Connected." On RSD the Device Properties is empty. I'm guessing I shouldn't start the flash, right?

My computer is recognizing the phone and I Ran As Administrator.

I was caught in a boot loop because I was rooted with TWRP and ran the OTA upgrade this morning. The one thing I shouldn't have done..
[Moto X General] elamorc:
Thanks!

Hi,

I wanted to thank you for this tutorial/guide. It helped me to unroot my Moto X and get the Android Lollipop update.

Thanks a ton mate especially for the step-by-step instructions.
[Moto X General] ttrublu:
How long does the process usually take? Mine has been stuck at '7/16 flash system "system.img"' for a long time.
[Moto X General] whizinc:
Glad that you solved the problem.. I already mentioned above to update the motorola services... Unfortunately I Didn't add it to the OP. I will add it when i have spare time. (Y)
[Moto X General] whizinc:
Install Motorola drivers properly Uninstall any other drivers that you installed before, Use CCleaner to clean the bad files of old drivers and download the drivers mentioned in the OP, Surely your phone will show up as "Connected" on the RSD LITE. Yes if the phone is not getting detected on RSD LITE dont proceed on the guide untill or unless it shows up. Also make sure USB DEBUGGIN IS ON and Your pc is Allowed to debug your phone.
[Moto X General] whizinc:
Really glad that this thread is helping people get on the right path! My pleasure sir! To show your appreciation please hit the thanks button on the OP always ;)
[Moto X General] whizinc:
Usually it takes about a maximum time of 35Mins... How long have you been on the System.img process? If 35 mins has been exceeded then make sure that your usb cable is fine or try another port of usb.. Check that your drivers are fine. If these doesn't work then post a complete and brief explanation that what happened and will help you get this thing successful. :)
[Moto X General] ttrublu:
Thanks, I will try this and let you know how it went.
[Moto X General] s3ars:
What drivers other than the Motorola drivers should I be uninstalling? I used CCleaner to uninstall all of the Motorola software and got the same result. Shouldn't the Motorola Device Manager pop up when I plug the phone in? Maybe this is content for a different thread. I feel like I'm there, just can't do something really basic that I've done before.

I'm in USB Debugging mode.

I have Windows 8.1 which seems to be an issue with some people but this is how the computer came. I am also using the USB cable that came with the phone. Others don't do any different. Neither does shifting USB ports.
[Moto X General] whizinc:
you don't need to uninstall any drivers other than Motorola drivers... And i said use ccleaner to clean the temp files and fix the unused .reg entries in windows. As far as i know Windows 8 is not a big problem... it has the same Cmd like windows 7.. Does your bootloader says "Connected" while in fastboot mode? Also make sure that ADB.EXE is running in background and Adb is recognizing your Mobile's serial number..
[Moto X General] heroisnotdead:
Warning!!! This will erase EVERYTHING on your phone!!!

OP - please put a clear warning in red at the top of your post that this process will wipe out everything on the phone - user data, everything. I have titanium backups, but not of everything. I figured I could just restore from my twrp back-up, nope, that was erased too. I have backups of that so no worries. This RSD software is a fantastic time saving device to restore the phone to stock. But I don't want anybody to suffer the same "WTF?!?!" shock. For those of you know fastboot, just continue to do that instead of RSD if you want your user data to retain.
[Moto X General] s3ars:
I want to thank you for all the time you've spent helping me. Maybe somewhere out there someone as stupid as me will be able to use this.

This is what I've done.

01. Uninstalled Motorola Device Manager using ccleaner

02. Cleaned registry using ccleaner

03. rebooted

04. reinstalled Motorola Device Manager

05. rebooted

06. connected phone which is in Fastboot mode.

07. Computer makes its tone and says momentarily, "Installing Ghost Fastboot" or something to that effect.

08. ADB.EXE is not running in the background. adb devices in command line gives me no devices.

09. No Motorola Device Manager appears in the tray.

10. Phone, in fastboot, says "USB Connected."

11. RSD shows no connection.

So, it's like the computer and the phone recognize that a USB device is in there and maybe some sort of phone but the Motorola Device Manager remains without a clue. If I run the Motorola Device Manager it just checks for new software forever.

Maybe there's a clue in there somewhere. If I unbrick this thing I promise never to root it again, even though I thought it was great fun with Tasker.
[Moto X General] whizinc:
I will put that warning as im going to update some other things also.. But always keep in mind The Word "Flash" means erasing everything completely so its a common thing almost everyone knows that when the term flash comes in something it means to erase everything properly and the word flash is used several times in the OP... But thank you for reminding me mate i appreciate it!! :)
[Moto X General] whizinc:
Im working on your problem and trying different things on my computer to come to your point and tell which thing is causing the problem... As soon as i find something on your problem i will post.. In the meanwhile i suggest you to borrow a Windows 7 pc from someone and try it on that pc.. Good luck.
[Moto X General] heroisnotdead:
Ya, I know. I was just shocked it formatted my storage. Not the end of the world. It's my fault too for not being diligent with my back-ups as usual.
[Moto X General] s3ars:
I was trying on my Win 7 machine and getting the same results.

Then I went into Android Settings on my phone and turned USB Debugging Off with the intention of turning it back "on" and I noticed the Software Update notification. After I clicked it, it told me that the new Android was available and I said No Thanks. Which is what I should have said yesterday.

That seems to have reset the switch. It seems the boot loop is no longer looping. I can use my phone on 4.4.4 and figure it out without freaking out.

I will continue to subscribe and participate and get it to work!
[Moto X General] whatsitsnamenow:
I have 3 laptop running Windows 8.1. Only one of them works right with RSD detecting the phone.

On my other 2 Laptop, my phone cannot be detected by RSD no matter what. My system device manager list the phone and the Android Device ADB interface. I have tried to uninstall/reinstall Motorola Device Manager, Motorola Drivers, adb drivers. Nothing works. Pulling my hair out.

I'll keep an eye on this thread for any update
[Moto X General] Aman Aurora:
getting md5 missing error

any ideas how to do it..? i am getting missing md5 error
[Moto X General] sudhanshupatil:
I was having CM 12.1 on my phone. Before flashing CM i made a backup of my stock system using twrp. To get back to stock I restored the backup and then flashed recovery.img which i got from retail firmware zip file using fastboot. Is it enough for me to get the 5.1 OTA?
[Moto X General] whizinc:
Yes im going to update on that, As the installation of Windows 8.1 has been completed on my Pc, I will be working on it to the find the solution. Untill then just wait. It will take some time because im busy at something else also...
[Moto X General] whizinc:
if you are getting an md5 error then either the zip file is corrupted or broken. Redownload the zip and try again.
[Moto X General] whizinc:
I guess its enough to get the OTA. But if it doesn't works then follow the OP, if it works then post it here for other people also.
[Moto X General] Aman Aurora:
Did that

i downloaded the file two times.. same result:confused::confused:
[Moto X General] whizinc:
Ah i see then the file is broken/corrupted form the source. Try the SBF link that I've mentioned in the OP and find your SBF, files from FileFactory are never broken.
[Moto X General] Aman Aurora:
Downloaded from 2 different sources

Once i did it frm the link mentiond in this post.. and the other from google drive mentioned in a comment...

Both gave the same result.. Can you plese provide the link Xt1052 Asia Retail XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml

Useing twrp
[Moto X General] whizinc:
WAIT WHAT?! you are using TWRP to flash stock sbf of on your MOTO? Mention the whole process that you are trying to do??? And For your information TWRP is not intended to use when flashing stock firmware. Either you have to flash it through RSD LITE or mFastboot. These are the only two options for flashing stock firmware.

Here is the 100% OK link of XT1052 Asia Retail. http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
[Moto X General] Aman Aurora:
SORRY

I just read the whole post... I am still getting your system is up to date... No update available... Hasent the update reached everybody
[Moto X General] KidJoe:
No, the update is rolling out in phases. And if its your turn, your not stock and have to reset the phone, reflash it, etc to get back to stock, you will likely lose your place, and have to wait a little longer for the update to come to your phone again.