Related
The files were posted today. Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
You noticed this too I see. Glad you posted this as a new thread. I was just randomly posting that link in threads where stock images may have helped.
I'm not home to try it yet but I'm guessing that's a US image?
Ahhhhh finally.
i just followed this process, everything worked on the xoom wifi (US), im back to stock and everything is ok so far.
but im an idiot and pressed vol up instead of down on the last step (oem lock) which aborted the oem lock step. before i did this i was rooted, so i think technically im still rooted.
can i simply go back into fastboot oem lock and try again and press the rightbutton this time to re lock the xoom or would that brick it?
ok thanks guys!
vista64 said:
i just followed this process, everything worked on the xoom wifi (US), im back to stock and everything is ok so far.
but im an idiot and pressed vol up instead of down on the last step (oem lock) which aborted the oem lock step. before i did this i was rooted, so i think technically im still rooted.
can i simply go back into fastboot oem lock and try again and press the rightbutton this time to re lock the xoom or would that brick it?
ok thanks guys!
Click to expand...
Click to collapse
If you want to be extra safe, start over from the beginning. You're probably still unlocked (but not rooted) if you managed to flash boot and system.
i have error failed to boot lnx 0x0004 - starting rsd mode 2
can i use this file ??
DinarQ8 said:
i have error failed to boot lnx 0x0004 - starting rsd mode 2
can i use this file ??
Click to expand...
Click to collapse
Only if you can get into fastboot mode AND your computer can see it. But if I recall, neither ADB, Fastboot nor RSD Lite will see your Xoom?
maybe solution i wait SBF file
Hi Scourge1024,
Are you going to try and flash the images to your Canadian Xoom AND then see if you can OEM re-lock it again??
I haven't been able to find out if all the WiFi images ie US, Canadian or European are all interchangeable on a Wifi only xoom??
I guess what I'd like to know is, if I ever wanted to re-lock my UK xoom, could I simply flash the Motorola MZ604_HWI69 files, then oem re-lock OR would have to wait for European Motorola backup files?
Cheers
Ody
what he said ^
Just tried downloading the Wi-fi files... On both my Mac and PC, it's saying it can't extract the ZIP. Crap crap crap crap crap...
If i remember correctly, scourge said that both devices are exactly the same hardware. Therefore flashing either version's set of images is irrelevant as long as you do WIFI for that model and 3G for that one.
odyseus said:
Hi Scourge1024,
Are you going to try and flash the images to your Canadian Xoom AND then see if you can OEM re-lock it again??
I haven't been able to find out if all the WiFi images ie US, Canadian or European are all interchangeable on a Wifi only xoom??
I guess what I'd like to know is, if I ever wanted to re-lock my UK xoom, could I simply flash the Motorola MZ604_HWI69 files, then oem re-lock OR would have to wait for European Motorola backup files?
Cheers
Ody
Click to expand...
Click to collapse
Nope. I'm done being the guinea pig (with the OEM locking). I bricked my first Xoom trying to OEM lock it. I managed to lock it a few times. Then I tried a different boot.img and bricked...
Personally, I have no issues flashing the US image on. It's just the re-locking. There's really no point to relock it. The Americans with the 3G/4G Verizon ones had to be able to relock for a hardware upgrade. I have managed to flash US images onto my Xoom but they were extracted by BeagleBoy here. I posted a comparison here: http://forum.xda-developers.com/showthread.php?p=13070124
The software is interchangable between the MZ604 Xoom models (Wi-fi only). There are a bunch of other Brits using the Canadian images I extracted from me and my friend's XOOMs. I've used the US ones. You just need to do a "fastboot -w" after flashing both the system and boot images because going between versions sometimes requires userdata to be wiped.
Scourge1024 said:
Just tried downloading the Wi-fi files... On both my Mac and PC, it's saying it can't extract the ZIP. Crap crap crap crap crap...
Click to expand...
Click to collapse
FYI,
$ md5sum MZ604_HWI69.zip
ae9b9f5693c4b49c745cb017afe1a4b5 MZ604_HWI69.zip
$ unzip -t MZ604_HWI69.zip
Archive: MZ604_HWI69.zip
warning [MZ604_HWI69.zip]: 36325409 extra bytes at beginning or within zipfile
(attempting to process anyway)
testing: MZ604_HWI69/boot.img OK
testing: MZ604_HWI69/recovery.img OK
testing: MZ604_HWI69/system.img OK
testing: MZ604_HWI69/userdata.img OK
No errors detected in compressed data of MZ604_HWI69.zip
You might be OK if you can get something that'll handle errors better.
In Windows, WinRar worked. On my Mac, I did what you posted and well, it seemed to work. I also did a compare against BeagleBoy's ripped images and boot was perfect. System was 1 byte off. Maybe a counter for the file system being mounted?
Code:
mac-mini:mz604_img Howard$ md5 MZ604_HWI69.zip
MD5 (MZ604_HWI69.zip) = ae9b9f5693c4b49c745cb017afe1a4b5
mac-mini:mz604_img Howard$ unzip -t MZ604_HWI69.zip
Archive: MZ604_HWI69.zip
warning [MZ604_HWI69.zip]: 36325409 extra bytes at beginning or within zipfile
(attempting to process anyway)
testing: MZ604_HWI69/boot.img OK
testing: MZ604_HWI69/recovery.img OK
testing: MZ604_HWI69/system.img OK
testing: MZ604_HWI69/userdata.img OK
No errors detected in compressed data of MZ604_HWI69.zip.
mac-mini:mz604_img Howard$
Scourge1024 said:
In Windows, WinRar worked. On my Mac, I did what you posted and well, it seemed to work. I also did a compare against BeagleBoy's ripped images and boot was perfect. System was 1 byte off. Maybe a counter for the file system being mounted?
Click to expand...
Click to collapse
Yep, IIRC, ext maintains a mount count. One'd need some file system tools to properly verify.
Can someone post a walk through on how to do this?
pricej636 said:
Can someone post a walk through on how to do this?
Click to expand...
Click to collapse
from the op:
Instructions to return it to stock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Scourge1024 said:
Nope. I'm done being the guinea pig (with the OEM locking). I bricked my first Xoom trying to OEM lock it. I managed to lock it a few times. Then I tried a different boot.img and bricked...
Personally, I have no issues flashing the US image on. It's just the re-locking. There's really no point to relock it. The Americans with the 3G/4G Verizon ones had to be able to relock for a hardware upgrade. I have managed to flash US images onto my Xoom but they were extracted by BeagleBoy here. I posted a comparison here: http://forum.xda-developers.com/showthread.php?p=13070124
The software is interchangable between the MZ604 Xoom models (Wi-fi only). There are a bunch of other Brits using the Canadian images I extracted from me and my friend's XOOMs. I've used the US ones. You just need to do a "fastboot -w" after flashing both the system and boot images because going between versions sometimes requires userdata to be wiped.
Click to expand...
Click to collapse
Fair do's - I don't blame you! You've done enough As you say why re-lock on WiFi?
What I would really like to do is flash all the images to my UK WiFi Xoom and then try to install Bignadad's BigDX Xoom|Zoom Theme..
Previously flashing this theme soft-bricked my UK xoom - got loads of Force Closures. Installing the extracted images from you, still caused the same problem. Maybe it only works on the US WiFi Xoom, but I might re-flash with 'stock' ROM to see if that makes any difference? (I do have CWM nandroid backups in case of another soft brick!)
Cheers
Ody
Is there a risk with using these cause of zip extra bytes warning?
Seeing as bwcorvus has been missing in action, I've decided to pick up the slack.
These images are to be used to return to stock.
DO NOT USE THESE TO RELOCK YOUR DEVICE. YOU WILL END UP SOFT BRICKING YOUR DEVICE
These images only contain a boot image and a system image. Ever since Android 3.1, the recovery image is flashed on boot from the boot image.
To flash:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w
fastboot reboot
MZ600 (US 4g Only)
3.2.2 HLK75C MD5Sum: a2e2ac8378b951bf6fd87b0cd75ec72a (Thanks AceXMachine)
MZ600 (US 3g Only)
MZ604 (US Wifi Only)
3.2.2 HTK55D
3.2.2 HTK75D
Pulling your own images
1. Flash a custom recovery
2. Boot straight into recovery.
adb shell
mount /data
mkdir -p /data/media/Images
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/media/Images/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/data/media/Images/system.img
syncThen reboot back into android and pull them off of your device.
You're more than welcome to upload them, and I will add them to the list
Any chance of getting the bootloader (/dev/block/platform/sdhci-tegra.3/by-name/ebb) included in a dump somewhere? I'm suspecting that's why my LTE modem isn't working since it got overwritten when I flashed back to an older version and I'll need a dump from a working setup to confirm. Thanks!
zarkuu said:
Any chance of getting the bootloader (/dev/block/platform/sdhci-tegra.3/by-name/ebb) included in a dump somewhere? I'm suspecting that's why my LTE modem isn't working since it got overwritten when I flashed back to an older version and I'll need a dump from a working setup to confirm. Thanks!
Click to expand...
Click to collapse
Wouldn't mind getting the bootloader dump also
Bootloader dump will not help. I'm working on it, though there seems to be no possible way to do it without an SBF from motorola.
Hello all,
So I originally had unlocked my bootloader and installed a ROM but determined that I would rather have stock so I reverted to the stock ROM and re-locked my bootloader. However, I attempted to update my OS as prompted in the OS and I received a failure while trying to install the 1MB update and now I have no bootable OS so I know now that I have to restore again. I was wondering how I can prevent this again or if this was just a bad case?
I downloaded and used the stock image files from this post: http://forum.xda-developers.com/showthread.php?t=1998802
Could it be that the stock image doesn't check properly when installing the update? Any help is appreciated, thanks!
I could be wrong, but it's possible the factory images listed on that link are older, and there was a known issue with the older factory image for the N10 that caused the 4.2.1 update to fail.
I would recommend trying the factory image on Google's actual site: https://developers.google.com/android/nexus/images#mantaray
espionage724 said:
I could be wrong, but it's possible the factory images listed on that link are older, and there was a known issue with the older factory image for the N10 that caused the 4.2.1 update to fail.
I would recommend trying the factory image on Google's actual site: https://developers.google.com/android/nexus/images#mantaray
Click to expand...
Click to collapse
Thanks for the reply. I did previously download that factory image but then the fastboot commands to restore would be different no? I would have to update each partition manually?
fastboot flash boot
fastboot flash recovery
etc.
vs.
fastboot -w update image xxxxxx
Do you know if there is a guide available to update the OS using the factory image zip instead of the one listed on the post in my first post?
TheEmpyre said:
Thanks for the reply. I did previously download that factory image but then the fastboot commands to restore would be different no? I would have to update each partition manually?
Click to expand...
Click to collapse
Did you try just running the batch file included with the factory image? I believe the image off Google's site has additional commands that erase and/or format partitions first, flash the bootloader, restart back into bootloader, and then flash the image.
Edit: Here's the entire batch file:
Code:
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-mantaray-jop40c.zip
echo Press any key to exit...
pause >nul
exit
TheEmpyre said:
Thanks for the reply. I did previously download that factory image but then the fastboot commands to restore would be different no? I would have to update each partition manually?
fastboot flash boot
fastboot flash recovery
etc.
vs.
fastboot -w update image xxxxxx
Do you know if there is a guide available to update the OS using the factory image zip instead of the one listed on the post in my first post?
Click to expand...
Click to collapse
I found this on google website:
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
Do I have to execute the ./fastboot command first (running Mac OS X)?
./fastboot flash-all.sh OR ./flash-all.sh ?
So strange thing, I just plugged it into my computer and it went through with the update and is functioning normally....insteresting. Nonetheless I guess I now know to just run the script if I need to flash stock
TheEmpyre said:
I found this on google website:
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
Do I have to execute the ./fastboot command first (running Mac OS X)?
./fastboot flash-all.sh OR ./flash-all.sh ?
Click to expand...
Click to collapse
in order to run the script, you just run ./flash-all.sh and it should work; the "fastboot" command on its own probably wouldn't do anything unless you have fastboot in PATH or whatever, but I'm not too familiar with the process on OS X (you might even have to have Android SDK installed)
Well, there's been a lot of confusion about over in the 5.0 OTA thread about how to get onto the latest build of Lollipop.
**********UPDATE********
Sorry guys, I no longer have a Moto X and as such have to discontinue support for the downloads in this thread; I can no longer keep up with a device I don't have
If you can get the files I mention elsewhere, most of these instructions should remain applicable.
Thanks
*****************************
So how does one get onto the latest OFFICIAL build of Android 5.0 on their Moto X 2014 Pure Edition (XT1095)? Here's how (and it most likely involves a data wipe)
Have an XT1092 or XT1097? Well fear not! It's easy to convert.
Follow this guide later in the thread (thanks to@steff999 for this!):
http://forum.xda-developers.com/showthread.php?p=56700701
And if you have cellular problems on your 1092 or 1097, follow this post by @sbtm1337:
http://forum.xda-developers.com/showthread.php?p=56778275
****If you damage anything in the process, it's no one's fault but yours (it's hard to mess this up, though )****
Step 0:
Make sure you have basic fastboot and adb knowledge; have Motorola drivers on your computer.
Enable USB debugging on your phone if you haven't yet.
Then, go to the home screen. Plug in the USB cable into your computer, and then into your phone.
If you haven't done anything like this before, it should prompt you for RSA authorization. Check always allow, and then yes.
Step 1:
Determine where you are in the process.
You can be in one of 5 places:
A: On 4.4.4 KitKat, un-tampered
B: On 4.4.4 KitKat, tampered (root, /system mods, etc.)
C: On 5.0 Lollipop LXE22.39-6 un-tampered
D: On 5.0 Lollipop LXE22.39-6 tampered
E: On ANY other version
If option A, go to step 4 (no wipe!)
If option C, go to step Q (keep your data )
If option B, D, or E, go to step 2 (gonna have to wipe...)
******Unless you're on option A or C, you NEED an unlocked bootloader!******
Step 2:
Download the stock 4.4.4 firmware.
It's on Motorola's site, but you have to request access and wait a while. I've mirrored it in .zip form for easy access:
https://onedrive.live.com/redir?resid=227F163CB35629DA!20267&authkey=!AMWPTB3ICDtezYs&ithint=folder,
Extract the .zip on your PC. On OneDrive, open the Moto Fastboot folder and download the fastboot corresponding to your OS (Windows or Linux, no Moto Fastboot exists for Mac unfortunately).
***Take the fastboot file here and replace the one in whatever directory you have your current one***
***Move the files from the 4.4.4 Firmware to the same place you have the new fastboot.***
***There may be a file called fastboot in the 4.4.4 Firmware folder. Delete that, you only need the one from OneDrive***
Step 3:
Reboot your device to fastboot.
Enter these commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
Don't sign into any accounts, and skip all the setup.
Step 4:
Now, download the 4.4.4 to 5.0 OTA zip from here:
https://onedrive.live.com/redir?resid=227F163CB35629DA!20267&authkey=!AMWPTB3ICDtezYs&ithint=folder,
Put it in the download folder of your Moto X.
Step 5:
Reboot to stock recovery. Once you see the Android and a red triangle above it, press volume up for 3 sec and then lock right afterwards. Then let go immediately.
Select "apply update from sdcard".
Navigate to your download directory, and select the update zip.
Let it flash.
Reboot.
Step 6 **IMPORTANT**:
Now you've got L! But... Not so fast.
Skip through the setup, and go to factory reset in settings (enjoying the beauty along the way).
Here's why: Android L has 256-bit encryption (up from 128-bit on KitKat), however it only takes effect if you factory reset within L.
It's ultimately up to you whether you reset or not, but coming from a clean KitKat install like most this is a great benefit for little effort.
If you've made it this far without a wipe and don't want to re-set up your phone, it will work without it, but to ensure smooth operation and for security purposes I'd highly recommend the reset (many who haven't done this reset have reported numerous FCs and other issues as well).
Step Q:
All you have to do now is download the 5.0-6 to 5.0-11 OTA from my OneDrive and flash it in stock recovery. Not much to it!
*If you have an alternate modem, you'll be ineligible for this .6-.11 OTA. It's likely that you'll have to wipe, flash 4.4.4, and redo the steps it took to get you to -6 but with the -11 OTA file.*
And...
BAM!
LOLLIPOP!
YEAHHH BUDDY
Enjoy
Hope this helps some folks! Hit the thanks button if it does!
Sent from my Moto X Pure Edition using Tapatalk
SolarTrans said:
Well, there's been a lot of confusion about over in the 5.0 OTA thread about how to get onto the latest build of Lollipop.
In case you haven't followed it all, here's the story:
On the 8th or 9th of November 2014, Motorola started a very limited soak test with L build LXE22.39-5. That OTA got leaked, and many of us tried to get back to stock 4.4.4 to take the OTA. On 11/11/14, they started another, more widespread soak test. The build in that one is LXE22.39-6. In order to get from the first soak test build to the next, a "delta" OTA was required, and it was only sent to those officially enrolled in the first wave. That was never leaked, so in order to get onto the -6 firmware, a downgrade to stock 4.4.4 was necessary.
So how does one get onto the latest (as of now) build of Android 5.0 on their Moto X 2014 Pure Edition (XT1095)? Here's how (and it most likely involves a data wipe):
****If you damage anything in the process, it's no one's fault but yours****
Step 0:
Make sure you have basic fastboot and adb knowledge; have Motorola drivers on your computer.
Step 1:
Determine where you are in the process.
You can be in one of 5 places:
A: On 4.4.4 KitKat, boot loader locked, untampered whatsoever
B: On 4.4.4 KitKat, boot loader unlocked, tampered
C: On 4.4.4 KitKat, boot loader unlocked, untampered whatsoever (not even root) (extremely unlikely)
D: On 5.0 Lollipop build LXE22.39-5 boot loader unlocked
E: On 5.0 Lollipop build LXE22.39-5 boot loader locked
If option A or C, skip to step 4 (phew, no data wipe needed )
If option B or D, go to step 2 (you're getting wiped, sorry)
If option E, unlock your bootloader through Motorola's website (yup. Wipe too) and go to step 2
Step 2:
Download the stock 4.4.4 firmware.
It's on Motorola's site, but you have to request access and wait a while. I've mirrored it in .zip form for easy access:
https://onedrive.live.com/redir?res...0263&authkey=!AM8xPNkiWBzJ3iY&ithint=file,zip
Extract the .zip, and open the folder corresponding to your OS (Windows, Linux, etc).
Take the fastboot file here and replace the one in whatever directory you have your current one.
Move the rest of the files not in the OS folders to the same place you have the new fastboot.
Reboot your device to fastboot.
Enter these commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
Don't sign into any accounts, and skip all the setup.
Step 4:
Now, download the OTA zip from here:
https://onedrive.live.com/redir?res...0264&authkey=!APWqFt6yzNh4mSU&ithint=file,zip
And put it in the download folder of your Moto X.
Step 5:
Reboot to stock recovery. Once you see the Android and a red triangle above it, press the volume up and lock buttons simultaneously for 3 seconds and let go.
Select "apply update from sdcard".
Navigate to your download directory, and select 5.0OTA.zip.
Let it flash.
Reboot.
Step 6 **IMPORTANT**:
Now you've got L! But... Not so fast.
Skip through the setup, and go to factory reset in settings (enjoying the beauty along the way).
Here's why: Android L has 256-bit encryption (up from 128-bit on KitKat), however it only takes effect if you factory reset within L. It's ultimately up to you whether you reset or not, but if you're coming from a clean KitKat install like most this is a great benefit for little effort.
If you've made it this far without a wipe and don't want to re-set up your phone, it will work without it, but to ensure smooth operation and for security purposes I'd highly recommend the reset (many who haven't done this reset have reported numerous FCs and other issues as well).
And...
BAM!
LOLLIPOP!
YEAHHH BUDDY
Enjoy
Hope this helps some folks! Hit the like button if it does!
Sent from my Moto X Pure Edition using Tapatalk
Click to expand...
Click to collapse
A lot of people including myself have had troubles with the motoboot command. It comes up with a downgrade from TZ ( or something like that)
Have you had any problems?
Currently I'm on 4.4.4
I was on the first soak and tried to get back to 4.4.4 but my phone bootloops and then goes to recovery when I try to update to the newest L.
I have to flash the system from 4.4.4 And the boot to get my phone back.
matt99017d said:
A lot of people including myself have had troubles with the motoboot command. It comes up with a downgrade from TZ ( or something like that)
Have you had any problems?
Currently I'm on 4.4.4
I was on the first soak and tried to get back to 4.4.4 but my phone bootloops and then goes to recovery when I try to update to the newest L.
I have to flash the system from 4.4.4 And the boot to get my phone back.
Click to expand...
Click to collapse
No, I haven't had any problems. I've heard of some people saying that you don't have to flash motoboot (it's the boot loader) to successfully downgrade.
Have you tried flashing everything else from this firmware?
Sent from my Moto X Pure Edition using Tapatalk
I've tried to flash the system, but it tells me something about needing to use a new fastboot. Multi....+++++? Not used anymore.
I've tried to flash the gpt but it won't work either. I've done boot, fsg, modem, that is it.
System, gpt, motoboot are all a no go.
Kinda lost.
I'm at work now, so I can't do much for about 7 more hours.
Thanks for this - so this is the official 5.0 OTA? Not the Soak test?
SolarTrans said:
Extract the .zip, and open the folder corresponding to your OS (Windows, Linux, etc). Take the fastboot file here and replace the one in whatever directory you have your current one.
Click to expand...
Click to collapse
There are no folders in the archive with stock 4.4.4 firmware and there is no fastboot.exe for Windows inside. Where I can get fasboot for Windows to flash so big system.img ?
It's in the os folders - that fastboot did not work for me however. I just used sdk fastboot.
Quick question
Sorry for a noob question, but am I correct in assuming this will function fine on a Mac using the Linux fastboot? And does it need to be placed in the same directory as the files associated with the Android SDK? Or can it be in its own folder?
Thanks for any help!
Sdobron said:
It's in the os folders - that fastboot did not work for me however. I just used sdk fastboot.
Click to expand...
Click to collapse
I have downloaded both archives (1st link in OP, 2nd in another tread) and both do not have any folders inside. There is "fastboot" file in the archives and looks like it is for Mac and not for Windows.
So does it means that sdk fastboot flashed sustem.img successfully ?
Thanks to @SolarTrans and everyone else, both here and on MFN, I was able to reflash back to 4.4.4, update OTA to the Lollipop soak test, and restore the logo file to get rid of the ugly bootloader unlocked warning screen
This has been a great resource, and first time doing all of this. Definitely a little confusing at first, but I figured it out. Thanks everyone.
matt99017d said:
I've tried to flash the system, but it tells me something about needing to use a new fastboot. Multi....+++++? Not used anymore.
I've tried to flash the gpt but it won't work either. I've done boot, fsg, modem, that is it.
System, gpt, motoboot are all a no go.
Kinda lost.
I'm at work now, so I can't do much for about 7 more hours.
Click to expand...
Click to collapse
That's because you need the motorola fastboot file in the 4.4.4 zip
Sent from my Moto X Pure Edition using Tapatalk
Sdobron said:
Thanks for this - so this is the official 5.0 OTA? Not the Soak test?
Click to expand...
Click to collapse
It's the 2nd soak test, which some believe is the final OTA.
If it isn't, however, I'm registered as part of that soak test so I'll be able to post the update
Sent from my Moto X Pure Edition using Tapatalk
greggov said:
Thanks to @SolarTrans and everyone else, both here and on MFN, I was able to reflash back to 4.4.4, update OTA to the Lollipop soak test, and restore the logo file to get rid of the ugly bootloader unlocked warning screen
This has been a great resource, and first time doing all of this. Definitely a little confusing at first, but I figured it out. Thanks everyone.
Click to expand...
Click to collapse
How did you restore the logo? Just fastboot flash the logo.bin from the factory image?
paul_jones said:
Sorry for a noob question, but am I correct in assuming this will function fine on a Mac using the Linux fastboot? And does it need to be placed in the same directory as the files associated with the Android SDK? Or can it be in its own folder?
Thanks for any help!
Click to expand...
Click to collapse
As I said in the guide, it needs to replace your current fastboot file in your Android SDK (it works for other manufacturers too, it just has some added functionality for Motorola so it's safe to do this).
But yeah you should be fine with the Linux one, although I don't have a Mac so I can't test it
Sent from my Moto X Pure Edition using Tapatalk
Moto Fastboot files are back up guys! They're in my OneDrive, just follow the folders from either link up there
Sent from my Moto X Pure Edition using Tapatalk
Sdobron said:
How did you restore the logo? Just fastboot flash the logo.bin from the factory image?
Click to expand...
Click to collapse
I actually googled around trying to replace it, and it linked me back to a thread here. Downloaded the logo.bin file and flashed it. It's the stock M logo with "powered by Android" or whatever that says
greggov said:
I actually googled around trying to replace it, and it linked me back to a thread here. Downloaded the logo.bin file and flashed it. It's the stock M logo with "powered by Android" or whatever that says
Click to expand...
Click to collapse
Care to link that thread? Thanks
Sdobron said:
Care to link that thread? Thanks
Click to expand...
Click to collapse
here you go!
Anyone did try on XT1097 (Brazilian model)?
Updated OP with Moto Fastboot files! There should be no problems now
Sent from my Moto X Pure Edition using Tapatalk
It seems like there needed to be a thread dedicated to the issues that users have been seeing with this recent OTA, as it seems like there has been a few problems with updating if you ever used Motorola's Stock 5.1 Image, I'll begin by listing the steps necessary to successfully apply the OTA update regardless of what software version you are currently running, there is also a TWRP System Image for those of you who don't want to go through the fastboot process or return to stock
Official OTA Update Procedure
1) Use TWRP and make a full backup, then connect your phone to your computer and transfer the backup files to your computer
2) Reboot your phone into the bootloader, either by doing adb reboot-bootloader or the physical key combination (power off then press and hold the power and volume down key for ~4 seconds)
3) Download the Stock 5.1.0-LPA23.12-15.0 Image from here, do NOT use Motorola's Recovery Image to do this procedure, it will fail, as the hashes are not what the OTA is expecting for the system.img, and extract the contents to a folder on your computer
4) Download the OS relevant attached mfastboot zip and unzip the contents to the same folder on your computer (if you are having issues with mfastboot try reefuge's version and see if it helps!)
5) Open up a command prompt in the directory and use the following commands to flash the 5.1 Stock Image, erasing the userdata partition is not required but it is highly recommended, as you can easily restore the TWRP data partition after doing these steps if you want your personal data back
Code:
[B]not required, but recommended![/B]
mfastboot erase userdata
[B]required[/B]
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot -P flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
6) Reboot your phone and do your initial 5.1 phone setup, and then immediately check for System Updates
7) Download the OTA and select to install the OTA
8) Rejoice in your completed OTA update, if the update fails to install, upload the recovery logs (or tell us the problem) and we will try to help!
9) You can now install TWRP and root if desired, and restore your TWRP data backup if you erased it beforehand
TWRP System Image
The TWRP System Image can be used instead of trying to apply the OTA update, this is a backup of my own phone's system partition after doing the OTA update, so it's already on 222.27.5...
Alright, after quite a bit of time uploading...
Here is the TWRP System Image
1) Download the Stagefright System 222.27.5 TWRP backup from the above link
2) Unzip the Stagefright System 222.27.5 folder to your computer
3) Copy the Stagefright System 222.27.5 folder to your phones internal storage, to the TWRP/BACKUPS/TA0000008VJ/ directory
4) Reboot your phone into recovery (TWRP)
5) Click Restore and select the Stagefright System 222.27.5 folder
6) Verify that the System partition is selected and then Swipe to Restore
7) Clear your cache
8) Boot into system and enjoy the new patch
_
Obligatory initial post
If this guide helped you at all, please show your support by either donating or telling people about how they can fix their device, pay it forward!
Please forgive me for being paranoid and not immediately running out and flashing some random OS image off the internet without first asking: what's the provenance of this OS image?
vtluu said:
Please forgive me for being paranoid and not immediately running out and flashing some random OS image off the internet without first asking: what's the provenance of this OS image?
Click to expand...
Click to collapse
The image is a Motorola signed Image, it's just not the same one that they have listed on the Recovery page, here is the details from the factory version info file inside the zip
Code:
BUILD REQUEST INFO:
SW Version: ghost_retail-user 5.1 LPA23.12-15 15 release-keysMSM8960PRO_BP_23255.138.89.00R
MBM Version: 30.BE
Modem Version: MSM8960PRO_BP_23255.138.89.00R
FSG Version: ONEBIN_BP_FSG_2.3.03_v127
Build Fingerprint: motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 222.21.15.ghost_row.Retail.en.US
Model number: Moto X
Android Version: 5.1
Baseband Version: MSM8960PRO_BP_23255.138.89.00R
Build Number: LPA23.12-15
Build Date: Sat May 9 01:44:45 PDT 2015
OTHER MISC VERSION INFO:
Subsidy Lock Config: None
Blur Version: Blur_Version.222.21.15.ghost_row.Retail.en.US
Version when read from CPV: ghost_retail-user 5.1 LPA23.12-15 15 release-keys
I can confirm that the stock image linked in the original post actually allows the update to succeed. I originally tried flashing the "official" firmware (TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz) from Motorola's site , since I had used firmware from Motorola's page to go back to stock for previous OTAs successfully, but the Stagefright OTA failed to install over that "stock" version. After flashing over to the image from motofirmware.center (GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip), the OTA installed smoothly. Looks like someone at Motorola made a mistake with the Lollipop 5.1 firmware they uploaded to their official page.
mastarifla said:
The image is a Motorola signed Image, it's just not the same one that they have listed on the Recovery page, here is the details from the factory version info file inside the zip
Click to expand...
Click to collapse
Thanks for the clarification. :good:
EDIT: false alarm about LTE functionality deleted, my bad. Happy flashing!
Sorry for posting again, but would it be possible to create a zip file for this OTA that will flash in TWRP?
vtluu said:
Thanks for the clarification. :good:
Warning: it looks like I might have lost LTE support on T-Mobile US after applying the above flash (it shows me using HSPA+). Could be a false alarm or me being clueless. Will edit this post once I've verified one way or the other.
EDIT: confirmed, after putting back the image I got from the official Motorola page, I see "LTE" once again under "Cellular network type" in "SIM status", whereas with the above image it said "HSPA+". There might be a way of mixing and matching the radio firmware to fix that, but I haven't tried. At this point I think I'll just sit tight and wait for an update to the update from Moto.
Click to expand...
Click to collapse
T-Mobile default's data to HSPA+, then once you start using data it "revs up" to LTE, this is a network topology thing
You could also use the dialer code (*#*#4636#*#*) to verify that your preferred network type is set correctly, mine is set to LTE/GSM auto (PRL)
Thanks. Will try again. (The most painful part being having to wait 15-20 minutes for ART to recompile my 109 apps after each reflash.)
UPDATE: all good. And the OTA update worked as well.
AaronCompNetSys said:
Sorry for posting again, but would it be possible to create a zip file for this OTA that will flash in TWRP?
Click to expand...
Click to collapse
I think all that has to be done for that is to remove the fingerprints from the flash script right?
If so, here you can try this version in TWRP... I didn't remove the patch hash checks, so if you used the Motorola Image you will still fail when flashing
mastarifla said:
I think all that has to be done for that is to remove the fingerprints from the flash script right?
If so, here you can try this version in TWRP... I didn't remove the patch hash checks, but theoretically they could be removed, but that seems quite risky...
Click to expand...
Click to collapse
I just tried it and it failed to install with TWRP. Bummer! Thanks for trying.
Being on Motorola Stock 5.1 image I flashed stock image linked in OP using RSD Lite. I did not erased Userdata during flash. Afer that OTA installed just fine.
sisterchick said:
I just tried it and it failed to install with TWRP. Bummer! Thanks for trying.
Click to expand...
Click to collapse
When did it fail? Was it due to the sha-1 mismatch? Or was it not even able to begin?
If it was the mismatch, then you would have gotten the same error with the stock recovery, which is resolved by flashing the 5.1 stock image that I linked to in the OP, you could also try removing the hash checks in the build-script, but that would be somewhat risky-ier
Al936 said:
Being on Motorola Stock 5.1 image I flashed stock image linked in OP using RSD Lite. I did not erased Userdata during flash. Afer that OTA installed just fine.
Click to expand...
Click to collapse
Awesome, I added to the OP that you don't need to wipe your data partition but it's still highly recommended
Do I need to unzip the pack I downloaded? For some reason system.img won't unzip. I keep getting an error that says "CRC failed in 'system.img". File is broken." I'm using 7zip to try to extract the files.
Shemlon said:
Do I need to unzip the pack I downloaded? For some reason system.img won't unzip. I keep getting an error that says "CRC failed in 'system.img". File is broken." I'm using 7zip to try to extract the files.
Click to expand...
Click to collapse
You should unzip the .zip, but you should not "unzip" the .img. The .img is a binary file that should stay as is (don't try to open it).
Alright I made a version of the update.zip without the patch checks
Edit: Unfortunately no luck as the patching cant be forced on the Motorola Image, as the places where they patch seem to be different than the other zip's system image
Will I need to reinstall TWRP and reroot my phone when I'm done? I apologize for the really basic questions guys.
Shemlon said:
Will I need to reinstall TWRP and reroot my phone when I'm done? I apologize for the really basic questions guys.
Click to expand...
Click to collapse
No problem, yes, you will need to re-install TWRP and re-root your phone if you are doing the full procedure
Thank you dude!
Looks like all problems cuz of missmatching hashes in prev firmware and OTA. I just flashed from your link following things and OTA installed fine:
mfastboot flash motoboot motoboot.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Click to expand...
Click to collapse
Success!
Thanks! You saved me a bunch of time fixing my wife's phone that failed-to-update correctly like so many others.
FWIW:
1) Do NOT use the regular android sdk 'fastboot'; use the motorola-tweaked mfastboot version attached above. I've gotten away with using the regular fastboot util for most things, but the device failed to boot past the unlocked bootloader warning screen until I reflashed system using mfastboot instead.
2) I got an error updating the gpt partition (something about downgrading security versions), but it didn't seem to matter.
3) I didn't wipe the userdata partition either, and all was fine. Had a TWRP backup just in case, though.
5.1 -> 5.1.1 == done. Secure... for now. (according to this Stagefright Detector app)
Doubt this original MotoX will get Marshmallow 6.0, so I might be switching it to CyanogenMod 13 in a couple months.