Related
Hey everyone,
The 2013 N7 factory images have been updated on Google's site to new versions of KRT16O. I've run a compare on the system images and they're definitely different. If you downloaded the original KRT16O factory images, you should probably download the new ones and re-flash. This applies to both the WIFi-only (razor) and LTE (razorg) variants.
Just figured you all would like to know.
downloaded filenames are different too but the last part of the filename is the first past of the sha-1 hash, so that's expected to be different
oldblue910 said:
Hey everyone,
The 2013 N7 factory images have been updated on Google's site to new versions of KRT16O. I've run a compare on the system images and they're definitely different. If you downloaded the original KRT16O factory images, you should probably download the new ones and re-flash. This applies to both the WIFi-only (razor) and LTE (razorg) variants.
Just figured you all would like to know.
Click to expand...
Click to collapse
This may be why the rollout to the N7 LTE has been stalled so long... *fingers crossed*
What is different between new image and old image?
oldblue910 said:
The 2013 N7 factory images have been updated on Google's site to new versions of KRT16O. I've run a compare on the system images and they're definitely different. If you downloaded the original KRT16O factory images, you should probably download the new ones and re-flash. This applies to both the WIFi-only (razor) and LTE (razorg) variants.
Click to expand...
Click to collapse
Reflashing would not yield different results though one might prefer to redownload for their archives.
The bootloader and image files are EXACTLY the same.
The only change is the bootloader got renamed and the associated lines in the install scripts were changed to reflect that.
Code:
\razor-krt16o-old>fsum *
[B][COLOR="Red"]d8b3145274d90d7c90d959fae7eac1de[/COLOR][/B] *bootloader-flo-flo-03.14.img
eea74e92a7fe2e43cae0a36d0ec67381 *flash-all.bat
5b9d8a09cca582968a2a2d4bfd18d183 *flash-all.sh
b859ca97c0f7326bb3e05f411f43a74a *flash-base.sh
[B][COLOR="Red"]3976dad7190e2dbd358e5f02a18ccbf1[/COLOR][/B] *image-razor-krt16o.zip
Code:
\razor-krt16o>fsum *
[B][COLOR="Red"]d8b3145274d90d7c90d959fae7eac1de[/COLOR][/B] *bootloader-flo-flo-04.01.img
ba55aa5e20ff4a8b2b088b6215cb413d *flash-all.bat
3256c5ec010f9ad48b519cfe5bb0533e *flash-all.sh
b34cf35cc3617be09b35bf671771f20b *flash-base.sh
[B][COLOR="Red"]3976dad7190e2dbd358e5f02a18ccbf1[/COLOR][/B] *image-razor-krt16o.zip
Code:
diff flash-all.bat-old flash-all.bat
17c17
< fastboot flash bootloader bootloader-flo-flo-03.14.img
---
> fastboot flash bootloader bootloader-flo-flo-04.01.img
Code:
diff flash-all.sh-old flash-all.sh
17c17
< fastboot flash bootloader bootloader-flo-flo-03.14.img
---
> fastboot flash bootloader bootloader-flo-flo-04.01.img
Code:
diff flash-base.sh-old flash-base.sh
17c17
< fastboot flash bootloader bootloader-flo-flo-03.14.img
---
> fastboot flash bootloader bootloader-flo-flo-04.01.img
Code:
\razorg-krt16o-old>fsum *
[B][COLOR="Red"]d8b3145274d90d7c90d959fae7eac1de[/COLOR][/B] *bootloader-deb-flo-03.14.img
9ec444a4824bf67279c68293638d7b38 *flash-all.bat
8ce9769e5435c70a7ec36c16d3bc2fc1 *flash-all.sh
e00e5bc5ab45f6196dd335d58990d397 *flash-base.sh
[B][COLOR="Red"]606362caca21cbce30cf05e5cd824157[/COLOR][/B] *image-razorg-krt16o.zip
[B][COLOR="Red"]51ddeb28edb513930a797cc122604d14[/COLOR][/B] *radio-deb-deb-g00_1.23.0_0720.img
Code:
\razorg-krt16o>fsum *
[B][COLOR="Red"]d8b3145274d90d7c90d959fae7eac1de[/COLOR][/B] *bootloader-deb-flo-04.01.img
ddea0e096681d7fc374210f1c6d13500 *flash-all.bat
28b6e996916020e00d53fb35e56aab40 *flash-all.sh
128414fe18b07aa5e57b0a8cdd7bed2e *flash-base.sh
[B][COLOR="Red"]606362caca21cbce30cf05e5cd824157[/COLOR][/B] *image-razorg-krt16o.zip
[B][COLOR="Red"]51ddeb28edb513930a797cc122604d14[/COLOR][/B] *radio-deb-deb-G00_2.37.0_1024.img
Code:
diff flash-all.bat-old flash-all.bat
17c17
< fastboot flash bootloader bootloader-deb-flo-03.14.img
---
> fastboot flash bootloader bootloader-deb-flo-04.01.img
20c20
< fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
---
> fastboot flash radio radio-deb-deb-G00_2.37.0_1024.img
Code:
diff flash-all.sh-old flash-all.sh
17c17
< fastboot flash bootloader bootloader-deb-flo-03.14.img
---
> fastboot flash bootloader bootloader-deb-flo-04.01.img
20c20
< fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
---
> fastboot flash radio radio-deb-deb-G00_2.37.0_1024.img
Code:
diff flash-base.sh-old flash-base.sh
17c17
< fastboot flash bootloader bootloader-deb-flo-03.14.img
---
> fastboot flash bootloader bootloader-deb-flo-04.01.img
20c20
< fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
---
> fastboot flash radio radio-deb-deb-G00_2.37.0_1024.img
I analyze the DEB variant and it seems there are no changes between the old and new archive. Changed are file names of images (version number in file name) but content is absolutely same. For validation I use sha1sum. So the DEB images no need to flash again.
sfhub said:
Reflashing would not yield different results though one might prefer to redownload for their archives.
The bootloader and image files are EXACTLY the same.
The only change is the bootloader got renamed and the associated lines in the install scripts were changed to reflect that.
Click to expand...
Click to collapse
Thank god sfhub has an N7. Else we'd all be lost.
I fondly recall: "there are zips and there are zips"
Sent from my Nexus 7 using Tapatalk 4
oldblue910 said:
Hey everyone,
The 2013 N7 factory images have been updated on Google's site to new versions of KRT16O. I've run a compare on the system images and they're definitely different. If you downloaded the original KRT16O factory images, you should probably download the new ones and re-flash. This applies to both the WIFi-only (razor) and LTE (razorg) variants.
Just figured you all would like to know.
Click to expand...
Click to collapse
Maybe thats why its been slow rolling out if they can avoid two updates due to revisions?
Upon further inspection it looks like the only differences between the old and new KRT16O images is the names of the radio and bootloader files. In the old package, they were named wrong but we're still the right actual versions of the files. In the new package, the names have been corrected. So if you flashed before yesterday, you should be fine.
Sent from my GT-I9505G using Tapatalk
Pre-requisites:
a) Download and install Motorola Drivers:
http://forum.xda-developers.com/showthread.php?t=2550635
b) Download and extract the stock firmware of your choosing from:
Looks like this link is now broken :'-( http://sbf.droid-developers.org/phone.php?device=14
The firmwares with '_umtsds' in the file name are for the 'dual-sim' versions of the Moto G, it's probably not a good idea to flash these onto single sim phones, or vice-versa.
Edit: More firmwares for international retail and carrier devices can be found here:
http://www.filefactory.com/folder/c6cdedc45a775d27
Edit: The firmware files have been updated most of the firmware archives are now in .tar.gz archives which include Motorola fastboot and flashing scripts for OSX, Linux and Windows.
On windows the .tar.gz archives need to be opened and extracted using a 3rd party archive manager. e.g. 7-zip, or PeaZip, Windows cannot extract these files natively, Linux and OSX can.
I used the retail British firmware (fastboot_falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB.tar.gz), extracted to c:\
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot View attachment mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
d) Get ADB (if you don't already have this, I suggest downloading and installing Minimal ADB and Fastboot by shimp208:
https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE
Disclaimer:
Follow these instructions at your own risk. If something goes wrong don't blame me!
I have only tested this on a UK Retail Moto G with an unlocked bootloader, however as these are the original stock signed image files from Motorola it should work on all devices.
See notes at the bottom of this post for downgrading from 4.4.2 to 4.3.
Edit: tkm89 reports that he was able to use this guide to restore Stock Retail British firmware on a bootloader locked Tesco-mobile Moto G
Steps to restore stock firmware:
1) Reboot the phone into bootloader mode. There are 2 ways to do this.
I) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
II) The 'software' way.
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open "Minimal ADB and Fastboot". Type:
Code:
adb reboot-bootloader
You should see the Moto G bootloader screen with the following options:
Code:
Normal Powerup
Recovery
Factory
Switch Console [NULL: null]
Barcodes
BP Tools
2) Open a command prompt / terminal (Start -> cmd.exe in Win7) and browse to the folder with the extracted firmware.
In my case:
Code:
cd c:\falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB
3a) If you downloaded and extracted a firmware in .tar.gz format
In windows, run the 'flashall.bat' script Type:
Code:
flashall.bat /eu
The "/eu" switch forces userdata to be erased from the device, this is the same as a factory reset or wipe this is recommended when restoring stock firmware.
In Linux/OSX run the flashall.sh script. Type:
Code:
chmod +x flashall.sh
./flashall.sh
Downgrading:
The scripts will fail with an error on downgrading from 4.4.2 to 4.3. Open the script in a text editor (notepad) and delete (or comment) the following:
Lines 89-90 in the flashall.bat file:
Code:
CALL :fastboot_flash partition gpt.bin
IF %errorlevel% NEQ 0 EXIT /b 1
Lines 120-121 in the flashall.sh file:
Code:
run $fastboot -s "$serial_number" flash partition gpt.bin
if [ $? -ne 0 ]; then echo "ERROR: fastboot failed."; exit -1; fi
3b) If you downloaded and extracted a firmware in .xml.zip format.
Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Downgrading:
The 1st command "mfastboot flash partition gpt.bin" will fail on 4.4.2 to 4.3 downgrade. Skip this command if you are downgrading and continue with the other commands, which should work.
4) Wait, you should now be rebooted into a fully stock Moto G firmware.
t-bon3 said:
[...]
Click to expand...
Click to collapse
added to FAQ
matmutant said:
added to FAQ
Click to expand...
Click to collapse
Can you please remove it temporarily, it's not working at the moment! Sorry about that.
t-bon3 said:
Can you please remove it temporarily, it's not working at the moment! Sorry about that.
Click to expand...
Click to collapse
ok
any news? rsd lite still not see Moto G on windows 8.
Bart123 said:
any news? rsd lite still not see Moto G on windows 8.
Click to expand...
Click to collapse
Guide is updated and working now. :fingers-crossed:
At the moment the flashing needs to be done one partition at a time using a specific motorola version of fastboot. Hopefully a new version of RSD lite will be released that simplifies the whole process.
I was having problems with RSD Lite, when trying to flash the retail British ROM (mine came with the Tesco ROM pre-installed). This worked perfectly on my Moto G with a locked bootloader!
thanks for the guide, ive also just flashed stock firmware over preinstalled tesco firmware with a locked bootloader.
Worked flawlessly on my Tesco Mobile Moto G. Many thanks for the guide fella
Is the bootloader warning Logo also removed?
Gesendet von meinem XT1032 mit Tapatalk
Wich of these stock rooms are the Brazilian XT1033 for the 16gb dual chip???
fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
alex1301 said:
Is the bootloader warning Logo also removed?
Click to expand...
Click to collapse
If you just follow the guide above then no, your unlocked bootloader and warning will remain after flashing.
The procedure for relocking the bootloader is to issue the following command in fastboot before flashing:
Code:
mfastboot oem lock begin
then after flashing but before rebooting enter the following:
Code:
mfastboot oem lock
This should lock the bootloader BUT I have seen reports that even after re-locking there is still a warning screen saying that the bootloader has been previously unlocked!
Allewar said:
Wich of these stock rooms are the Brazilian XT1033 for the 16gb dual chip???
fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
Click to expand...
Click to collapse
first one with ds 'dual-sim' in the name
C:\Motorola\falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-
Brasil_BR>mfastboot flash system system.img_sparsechunk.0
error: cannot load 'system.img_sparsechunk.0'
I had this message when I try, the previous commands worked right!
Daniel
moto g 16gb dual chip
djmgermanos said:
C:\Motorola\falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-
Brasil_BR>mfastboot flash system system.img_sparsechunk.0
error: cannot load 'system.img_sparsechunk.0'
I had this message when I try, the previous commands worked right!
Daniel
moto g 16gb dual chip
Click to expand...
Click to collapse
The south american firmwares do not have multi-part /system images. In that case use this command instead:
Code:
mfastboot flash system system.img
t-bon3 said:
The south american firmwares do not have multi-part /system images. In that case use this command instead:
Code:
mfastboot flash system system.img
Click to expand...
Click to collapse
Tanks
djmgermanos said:
Tanks
Click to expand...
Click to collapse
Now I have this message
C:\Motorola\falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-
Brasil_BR>mfastboot flash system system.img
sending 'system' (524288 KB)...
OKAY [ 18.111s]
writing 'system'...
Multi-Flash is not supported any more!
Please download latest fastboot from: xxxxxx
the link don´t work
Daniel
some of the lines show errors for me:
Sparsechunk2: Failed to validate sparse image
Sparsechunk0: Invalid signed image
other wise, it seems to work fine
thanks,
djmgermanos said:
Now I have this message
C:\Motorola\falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-
Brasil_BR>mfastboot flash system system.img
sending 'system' (524288 KB)...
OKAY [ 18.111s]
writing 'system'...
Multi-Flash is not supported any more!
Please download latest fastboot from: xxxxxx
the link don´t work
Click to expand...
Click to collapse
Can you try mfastboot.exe from the attached zip. This is taken from the south american firmware release.
Now it works
Thanks
Daniel
Moto G 16gb dual chip Brazil
XT1033
---------- Post added at 12:25 PM ---------- Previous post was at 12:13 PM ----------
Allewar said:
Wich of these stock rooms are the Brazilian XT1033 for the 16gb dual chip???
fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
Click to expand...
Click to collapse
Esta
fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
I have a defective device and in preparing to return it, I locked the bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
I was afraid that the N9 was like the N5 & 7 with the "tamper" flag, but after some digging (and advice from others out here), I decided to restore the factory image to see if that would overwrite the image. Yes! No more big fat red "I unlocked my bootloader and may have voided my warranty" message.
I can't take credit for this, but I thought I would consolidate everything I was finding in the Q&A threads into one spot, so I put this little tutorial together. Thank you @Pilz, @jd1639 & @PhilDX for your various posts.
Step 1 - Prepare your system
[Windows]
Since your bootloader is unlocked, you probably already have ADB and fastboot, but if not, grab the SDK from here, unzip and add the "platform-tools" directory to your PATH statement
If your drivers are set up properly and your device has Android debugging enabled, connect USB and execute `adb devices` from a command prompt you should see your device listed
Download the factory image for "volantis" here
The image is double zipped, so unzip, untar, then unzip the image-volantis-lrx21q.zip file into the same directory that contains the bootloader*.img file
Step 2 - Unlock bootloader
If you locked your bootloader, unlock again:
Code:
adb reboot bootloader
fastboot oem unlock
Step 3 - Flash stock image
The flash-all.bat script is broken, so you have to do it by hand:
Open a command prompt
cd into the directory where you unzipped the factory image files
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Before rebooting, relock the bootloader:
Code:
fastboot oem lock
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Typo: fastboot oem unlock
hirndurst said:
Typo: fastboot oem unlock
Click to expand...
Click to collapse
Hahaha! Thanks.
always good to know! thanks!
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
DarthSudo said:
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
Click to expand...
Click to collapse
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Thanks for this thread. Great guide.
jd1639 said:
You could also use fastboot -w instead of the erases
Click to expand...
Click to collapse
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Thanks for this. I RMA'd my Nexus 9 and sending it back tomorrow
DarthSudo said:
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Click to expand...
Click to collapse
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
jd1639 said:
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You guys are all right. I looked back at some of my notes and I've flashed plenty of devices w/o formatting the other partitions first. Just userdata and cache. Thanks!
Hey guys, just wanted to thank you for the fixed "script". This is now my flash-stock.sh script I use whenever I need to flash a nexus device as the one delivered by google just doesn't work (reboot loop due to crashing apps on startup or "missing system.img").
Works perfect and I always like to not dirty but rather make a clean flash as it just reduces the number of possible faults .
Cheers
Creamy
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
bruce7373 said:
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
DarthSudo said:
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
Click to expand...
Click to collapse
Thx, that seems simple enough. But I made the initial system (stock) backup before I rooted. That's why I was thinking restoring that would work. I just wasn't sure about the recovery, whether the restore would put the stock recovery back or not.
Sent from my Nexus 6 using Tapatalk
DarthSudo said:
I have a defective device and in preparing to return it, I locked to bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Click to expand...
Click to collapse
Hi,
is there a way to get rid of that red message if your bootloader is locked and you cannot boot into OS?
Thanks!
EDIT* Nevermind
Hey. Sorry for reviving this thread.
I installed Remix OS on my N9 and (after discovering that performance is horrible, with ~80% RAM usage on idle) after a reboot, Remix OS won't get past it's boot splash. I am attempting to flash my device back to stock.
I never touched the bootloader (never did any 'fastboot flash bootloader ...' or anything), so it it still necessary to flash the bootloader image, or can I just flash the system.img, boot.img, vendor.img etc.?
The bootloader had never changed so there is no reason to flash it.
Sent from my Nexus 9 using XDA Free mobile app
This is a reserection of -> http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735 and -> http://mark.cdmaforums.com/MotoX-OTA.html
With Verizon pushing a maintenance release for their Stock 4.4.4 (which doesn't change the Android version number), I wanted to post this sooner rather than later because questions are coming up....
Whenever a new OTA comes up, there are always questions like "what do I need to do to take the OTA?" or "I got prompted to take the OTA, but xxx is happening." This thread is intended to provide that information in once place.
This information is based on the past OTA updates for the Verizon, T-Mobile, and ATT Moto X phones, and threads on various forums. It should apply to all OTA updates.
Please note: If you have tried downgrading by flashing only parts of a rom, or have mismatched files on your phone for any reason, DO NOT TAKE AN OTA or you will likely brick your phone!! First flash your phone with a full SBF of the latest ROM for your carrier before attempting to take future OTA's. For more on Downgrading and the risks associated with it, see -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
These are the most common Questions and Issues we've seen in the past...
If you could NOT get your bootloader unlock code directly from Motorola and rooted by some other process, you should *WAIT* on taking an OTA update as it may patch any vulnerability being exploited to root your phone. And you may not be able to ROOT on this new version!!
If you used Sunshine, or got your Bootloader Unlock code from the China Seller or Middleman... You should BE CAUTIOUS and *WAIT* on upgrading past 4.4.4. Please see -> [LOLLIPOP WARNING]Those Who Unlocked Via Sunshine or Purchasing a Code from China
You should expect to lose root when you take an OTA.
For the Motorola X, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... To take the 4.4.4 OTA, your phone needs to be on 4.4.2 (or 4.4.3 depending on your model/carrier). To take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
Inside the OTA is a "Pre-flash Validation Check" to ensure your phone is on the correct version BEFORE it will flash. It includes a manifest file that contains a list of files and their check sums the OTA expects to be on your phone. If the files are missing from your phone, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. NOTE: The more files patched by the update, the more strict the pre-flash validation will be. So an update from 4.4.4 -> 5.1 will be more strict than the recent Verizon 4.4.4 maintenance patch.
Because of #5, you must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, may need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update. NOTE: Back in the "early days" of the 2013 X, all apps frozen with TiBu had to be unfrozen. Later updates that hasn't been much of a problem. I don't use it, so I can't say for sure.
If you have XPosed installed on your phone, it often does make changes that will cause the Pre-Flash Validation to fail. You may be able to just disable it, rather than fully removing it, and then take the OTA. (To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) NOTE: There is a newer version of Xposed needed for Lollipop!!
The OTA Updates will only install via Stock Recovery. If your Root method has replaced stock recovery with something else, you will need to use mfastboot to flash stock recovery on your phone BEFORE you attempt to take the update. Not having Stock Recovery on your phone when you take the OTA can result in your phone doing a boot loop. NOTE: You can use fastboot erase cache to delete the update zip file from your phone which will stop the boot loop.
There are several options to get back to "stock" without loosing your data. (I will add them to Post #2 of this thread at a later date), some are more technical, some are more noob friendly. The one you use, depends on how much, or how little, you have modified your phone away from stock.
In some cases, using mfastboot to reflash stock Recovery.IMG and System.IMG can be enough to get you back to "Stock" and take the OTA update.
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 Please be sure to use the latest TWRP fastboot IMG file (Alternate Link) and Installable ZIP of SuperSU
Any tethering hacks you have done will likely need to be undone in order to take the OTA (see #5 above), and may not work after the OTA is installed.
Some FAQ's...
I've tried taking the OTA, but I'm stuck in a loop. It wants to keep rebooting. - This is usually caused by having a 3rd party recovery, like TWRP/CWM, on the phone. Re-flash the stock recovery to install the OTA update, or use fastboot erase cache to delete the update zip file from your phone which will stop the boot loop. (instructions will be added to Post #2 of this thread in the future)
I've tried putting back my bloat, and taking the OTA, but it fails. - You likely missed something the Pre-flash Validation check is looking for. If you are able to capture the OTA ZIP and use the SIDE LOAD AN OTA instructions (which will be added to post #2 of this thread in the future), you can watch progress of the OTA install. It will tell you the error, and/or what file doesn't match.
In the past we've seen error codes 252 and 410. These have been related to files on the phone not matching the OTA's pre-flash validation checks.
[NOT YET SPELL CHECKED!!!]
How to return to stock & Unrooted... (Windows options only, as I don't have a Mac) Note: Some Windows 8/8.1 users have had issues, so when possible, please use Windows 7.
The following are listed in the order I originally posted them HERE and HERE
Requirements: These are the same no matter which option you use.
To repeat what I said in the OP, Do NOT attempt to downgrade your phone!! Please be aware of the risks -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Know what version ROM is on your phone before you touch anything. Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites that host leaked ROMS until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, and you'll find... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools can NOT flash the SYSTEM.IMG on Moto phones!!
Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The Options...
NOTE: I most often recommend option 5.
Option 1... The "Moto X Tool Kit"
This is the most newbie friendly.. But it can be a little complex to prepare and put your SBF in the right place, etc.
See -> [TOOL] Moto X Toolkit v1.4.4 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
It is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. The only thing it does not appear to include would be Roms for your particular phone, so, you'll likely need to download the ROM for your phone separately. As noted in the ToolKit thread, if they are available, you can get them from here -> http://sbf.droid-developers.org/ghost/list.php your "build number" or part of it, should be in the file name you are downloading.
Again, I haven't used this tool, so for install, setup and usage, I'll have to point you to that thread to ask. Two main options you'll be interested in... UNROOT (which keeps your data and apps) or FLASH BACK TO STOCK (which will likely also completely reset your phone and wipe any/all data, settings, applications, etc).
Option 2... mFastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you have made very few changes to your phone and already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept an OTA without losing data/apps.
NOTE: you may need to disable and/or uninstall Xposed before doing this.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements as listed above, the steps would be as follows...
Start the phone in Fastboot AP/Bootloader mode.
Connect phone to PC via USB cable.
open command prompt file and change to the folder you unzipped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and be back to stock and ready for the update.
NOTE: to combat a 410 ERROR while doing the update, some users have also had to also do the following
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
Option 3... Fully flash your phone using RSDLite while attempting to keep your data and settings
NOTE: this has the potential to erase your data if you don't edit the XML properly before flashing.
Follow this guide -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash) using SBF of the ROM currently on your phone, or newer for your carrier and model. HOWEVER, before doing it, as part of STEP 4 while editing the XML file, also remove the line that says...
<step operation="erase" partition="userdata" />
Failure to remove this line will result in your data/apps/settings being erased from your phone!!
Option 4... Fully flash your phone using RSDLite
Note: this WILL ERASE YOUR USER DATA AND APPS, and put you back to a "fresh" phone.
Follow this guide -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash) using the ROM from your carrier.
Option 5... Using mFastboot to manually flash your phone's firmware (without wiping data).
This is very similar to using option 3, but uses Moto fastboot instead of RSD, however it adds a few steps which aid in flashing when your GPT.BIN and MOTOBOOT.IMG are mismatched from the rest of your rom, and refuse to flash.
As written, these steps will NOT erase your data and apps. Because of this you may need to disable and/or uninstall Xposed before doing performing these steps.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements near the top of this page, the steps would be as follows...
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next... NOTE: yes, there are a few commands being repeated, but this is intentional!!!
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready. (it could take a little longer than a normal reboot)
NOTE: if you wish to erase your data and apps during this process, just before the final reboot command, issue... mfastboot erase userdata
Option 6... Flash only stock recovery.
This option is useful if all you did was unlock your bootloader, flash TWRP recovery, and rooted. It can be used if you've haven't installed Xposed, or modified any stock apps, and only run rooted for apps like BigTinCan's Adaway, Root Explorer, Wifi Tether for Root, etc.
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
The device will start in Stock Recovery display additional menu options (Text will appear in BLUE)
While in Stock Recovery, use the VOL DOWN Key to scroll and the POWER Key to select the option you wish to use.
You may now use the option to reboot the phone.
{reserved}
KidJoe,
Thanks so much for this. Even though I manually returned all changes to stock, the ota still kept quitting with an error.
It was really annoying because after each error, I would have to redownload the entire ota, 696MB, which was downloading rather slowly.
Anyway, I followed option number 2 from the original post to flash boot, recovery and system and it was smooth sailing after that
Thanks again
KidJoe said:
[NOT YET SPELL CHECKED!!!]
Option 2... mFastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you have made very few changes to your phone and already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept an OTA without losing data/apps.
NOTE: you may need to disable and/or uninstall Xposed before doing this.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements as listed above, the steps would be as follows...
Start the phone in Fastboot AP/Bootloader mode.
Connect phone to PC via USB cable.
open command prompt file and change to the folder you unzipped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and be back to stock and ready for the update.
NOTE: to combat a 410 ERROR while doing the update, some users have also had to also do the following
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
[/list]
Click to expand...
Click to collapse
KidJoe, thanks for the help. I have an XT1095. All I am pretty sure I did was root. I've never installed TWRP or even used root apps other than Greenify. In that state I was not able to accept the recent 5.1 OTA. I used the option in Supersu to full unroot (which also uninstalled Supersu). That did not fix the problem. I am now just finding your guide but other searching has led me to your conclusion that Option 2 should be all I need to do plus it won't wipe my phone.
The confusion I have now involves the system.img file. I requested the 5.0 download from Moto, but they never responded. I found the proper zip file elsewhere (TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip). When I unzip it, I see all the files. The recovery.img file is there but the system.img file is broken up into eight different files all named system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, etc.
Do I have the right files? Do I flash all of them individually? I'm not very experienced in this and don't want to screw this up. Any information you could provide would be greatly appreciated. Thanks.
Edit: After posting this, I found this site: http://www.usoftsmartphone.com/t279221.html that showd me how to extract the system file from all the sparse files. Step one creates a system.img file from all of them. Step two seems to unzip them. I am guessing that the file created after step 1 is the file I would need to flash?
Again, thanks for your help here!
summit15 said:
KidJoe, thanks for the help. I have an XT1095. All I am pretty sure I did was root. I've never installed TWRP or even used root apps other than Greenify. In that state I was not able to accept the recent 5.1 OTA. I used the option in Supersu to full unroot (which also uninstalled Supersu). That did not fix the problem. I am now just finding your guide but other searching has led me to your conclusion that Option 2 should be all I need to do plus it won't wipe my phone.
The confusion I have now involves the system.img file. I requested the 5.0 download from Moto, but they never responded. I found the proper zip file elsewhere (TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip). When I unzip it, I see all the files. The recovery.img file is there but the system.img file is broken up into eight different files all named system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, etc.
Do I have the right files? Do I flash all of them individually? I'm not very experienced in this and don't want to screw this up. Any information you could provide would be greatly appreciated. Thanks.
Edit: After posting this, I found this site: http://www.usoftsmartphone.com/t279221.html that showd me how to extract the system file from all the sparse files. Step one creates a system.img file from all of them. Step two seems to unzip them. I am guessing that the file created after step 1 is the file I would need to flash?
Again, thanks for your help here!
Click to expand...
Click to collapse
Keep in mind that the XT1095 is NOT a 2013 X, so its files may be different.
So I'm using a cm12 based rom and I've wanted to return to stock lately, let me see if I got this straight. Using rsd lite and erasing the line:
<step operation="erase" partition="userdata" />
Won't erase internal memory like music, photos, etc?
It's safe? I'm wondering if I'm going to have problems with the apps since they're running on ART on lollipop or if the system settings will have issues when I return to stock KitKat
OTA Accepted
For anyone who finds themselves in my same situation (all I really did to my phone was root it and install Supersu, no custom recovery or big time changes and I wanted to apply the OTA without wiping my device), I got my OTA update applied by doing the following:
Did a "Full Unroot" from within the Supersu app which then uninstalled itself.
I found the proper Moto ZIP file that contained Lollipop 5.0.
I then used mfastboot to flash the boot.img and the recovery.img
I then boot the phone up and told it to check for system updates.
It found the update, downloaded it, and then applied it.
It worked and I can move on with my life now.
NOTE: Most of my confusion in this process centered around my being told I needed to flash the system.img file. My problem was that inside the Moto ZIP file were eight different system_sparse files. I didn't know what to do with all them. I found a site in the previous link that showed me how to essentially combine all them into one system.img file. I followed those directions and it created the file. However, when I tried to flash it, I got an error that seemed to suggest that the file was corrupt.SO, this was after I had already flashed the boot and recovery files. I gave the OTA a shot just hoping it would work. Turned out it did.
Thanks again to KidJoe for this guide.
summit15 said:
For anyone who finds themselves in my same situation (all I really did to my phone was root it and install Supersu, no custom recovery or big time changes and I wanted to apply the OTA without wiping my device), I got my OTA update applied by doing the following:
Did a "Full Unroot" from within the Supersu app which then uninstalled itself.
I found the proper Moto ZIP file that contained Lollipop 5.0.
I then used mfastboot to flash the boot.img and the recovery.img
I then boot the phone up and told it to check for system updates.
It found the update, downloaded it, and then applied it.
It worked and I can move on with my life now.
NOTE: Most of my confusion in this process centered around my being told I needed to flash the system.img file. My problem was that inside the Moto ZIP file were eight different system_sparse files. I didn't know what to do with all them. I found a site in the previous link that showed me how to essentially combine all them into one system.img file. I followed those directions and it created the file. However, when I tried to flash it, I got an error that seemed to suggest that the file was corrupt.SO, this was after I had already flashed the boot and recovery files. I gave the OTA a shot just hoping it would work. Turned out it did.
Thanks again to KidJoe for this guide.
Click to expand...
Click to collapse
Again.. you have an XT1095... which is NOT a 2013 X... this guide is in the 2013 X section, so things can/will be different for a 2014 X...
But thanks for sharing.
Awsome Tutorial!!
I'm really a noob, so I still have some questions...
After that you should get the OTA update by going to setting -> about phone -> update??
because if so, I'm not.
Another thing i may done something wrong. On this step:
4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
I needed to move the ROM/SBF to the phone right? At any folder? Because I didnt do that and I opened the command prompt in the pc folder that the ROM/SBF was unziped. Nothing wrong happened to my phone, apparently.
Should I remake the tutorial moving the unziped file to the sdcard folder of my phone?
sorry for so many doubts.
Malba14 said:
I'm really a noob, so I still have some questions...
After that you should get the OTA update by going to setting -> about phone -> update??
because if so, I'm not.
Click to expand...
Click to collapse
The OTA update hasn't rolled out for all phone models and carrier variants yet. So there is a VERY GOOD chance it wont be available for you yet.
Malba14 said:
Another thing i may done something wrong. On this step:
4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
I needed to move the ROM/SBF to the phone right? At any folder? Because I didnt do that and I opened the command prompt in the pc folder that the ROM/SBF was unziped. Nothing wrong happened to my phone, apparently.
Should I remake the tutorial moving the unziped file to the sdcard folder of my phone?
sorry for so many doubts.
Click to expand...
Click to collapse
No, you do NOT move the SBF, or parts of it, to your phone. Leave it on your PC.
The tools to flash (RSDLite and mFastboot) are tools ON YOUR PC... they need the file to be on your pc.
In the post I talk about figuring out what file to download and use the example of the Rogers XT1058, and the correct file being XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip so sticking with that example.. you visit one of the sites (from your PC), download XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip ... and unzip it on your PC to a folder... If you are following option 2, 5 or 6 and using mFastboot, then you need to open a command prompt and change drive and directories to where you unzipped XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip to BEFORE you start entering the mfastboot commands. NOTE: you could just SHIFT-RightClick on the folder and "open command window here" as that will open a command prompt in that path/folder.
KidJoe said:
The OTA update hasn't rolled out for all phone models and carrier variants yet. So there is a VERY GOOD chance it wont be available for you yet..
Click to expand...
Click to collapse
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button and then every time I turned my phone on, after 30 seconds it rebooted to TeamWin. This kept going until I clicked on recovery or system (I dont remember - under the reboot page) and the cycle went off saying that has been some kind of problem with the update.
KidJoe said:
No, you do NOT move the SBF, or parts of it, to your phone. Leave it on your PC.
The tools to flash (RSDLite and mFastboot) are tools ON YOUR PC... they need the file to be on your pc.
In the post I talk about figuring out what file to download and use the example of the Rogers XT1058, and the correct file being XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip so sticking with that example.. you visit one of the sites (from your PC), download XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip ... and unzip it on your PC to a folder... If you are following option 2, 5 or 6 and using mFastboot, then you need to open a command prompt and change drive and directories to where you unzipped XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip to BEFORE you start entering the mfastboot commands. NOTE: you could just SHIFT-RightClick on the folder and "open command window here" as that will open a command prompt in that path/folder.
Click to expand...
Click to collapse
This part I did it right, i think. I fount the one that describe my phone better.
XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml
Actually I just reallized it is .xml. Is that ok? On my PC it opened with winrar just like any zip.
Malba14 said:
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button and then every time I turned my phone on, after 30 seconds it rebooted to TeamWin. This kept going until I clicked on recovery or system (I dont remember - under the reboot page) and the cycle went off saying that has been some kind of problem with the update.
Click to expand...
Click to collapse
Rebooted to TeamWin and said there was a problem with the update?? Yeah, because you need STOCK recovery on the phone. (as stated in the OP)
Malba14 said:
This part I did it right, i think. I fount the one that describe my phone better.
XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml
Actually I just reallized it is .xml. Is that ok? On my PC it opened with winrar just like any zip.
Click to expand...
Click to collapse
There maybe an XML inside the ZIP... you need to uncompress the entire file (extract all) BEFORE you can flash it, other wise RSDlite or mFastboot wont find the files you are trying to flash.
KidJoe said:
Rebooted to TeamWin and said there was a problem with the update?? Yeah, because you need STOCK recovery on the phone. (as stated in the OP)
There maybe an XML inside the ZIP... you need to uncompress the entire file (extract all) BEFORE you can flash it, other wise RSDlite or mFastboot wont find the files you are trying to flash.
Click to expand...
Click to collapse
Thanks for the help man. I'm sorry for the noob questions.
I actually did the hole tutorial before. I extracted this hole file and opened the command prompt in it and did the tutorial number 5.
Sorry if I wasnt clear before but the problem with the update was just a backgroud history to what I was aiming to know. That is: after I do the tutorial, what I have to do to get the OTA update now?
And how can I know that I did it right?
Your are awsome man!
Malba14 said:
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button....
Click to expand...
Click to collapse
I forgot to mention... for the models IT has started pushing for, they were sending it out in waves... IF you missed your turn (which you eventually did by not installing), you usually need to wait until the end, when the waves are done.. Because of when the BR Xt1058 push was started, I'd say that might be in the next week, or two.
Malba14 said:
Thanks for the help man. I'm sorry for the noob questions.
I actually did the hole tutorial before. I extracted this hole file and opened the command prompt in it and did the tutorial number 5.
Sorry if I wasnt clear before but the problem with the update was just a backgroud history to what I was aiming to know. That is: after I do the tutorial, what I have to do to get the OTA update now?
And how can I know that I did it right?
Your are awsome man!
Click to expand...
Click to collapse
As long as you flashed the latest 4.4.4 rom, your bootloader is consistent with the ROM you flashed, are you 100% completely stock, you just sit and wait until the OTA becomes available to your phone again. You can manually keep checking...
OR you can see if the 5.1 SBF is available for your carrier/model in this thread -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 download and flash it instead, which will take you right to 5.1...
OR you can see if the official OTA zip has been posted, download the zip to the /SDCard of your phone, and follow the SIDE LOAD section of -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
KidJoe said:
I forgot to mention... for the models IT has started pushing for, they were sending it out in waves... IF you missed your turn (which you eventually did by not installing), you usually need to wait until the end, when the waves are done.. Because of when the BR Xt1058 push was started, I'd say that might be in the next week, or two.
As long as you flashed the latest 4.4.4 rom, your bootloader is consistent with the ROM you flashed, are you 100% completely stock, you just sit and wait until the OTA becomes available to your phone again. You can manually keep checking...
OR you can see if the 5.1 SBF is available for your carrier/model in this thread -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 download and flash it instead, which will take you right to 5.1...
OR you can see if the official OTA zip has been posted, download the zip to the /SDCard of your phone, and follow the SIDE LOAD section of -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
Click to expand...
Click to collapse
Thanks a lot!!!
KidJoe said:
Option 5... Using mFastboot to manually flash your phone's firmware (without wiping data).
This is very similar to using option 3, but uses Moto fastboot instead of RSD, however it adds a few steps which aid in flashing when your GPT.BIN and MOTOBOOT.IMG are mismatched from the rest of your rom, and refuse to flash.
As written, these steps will NOT erase your data and apps. Because of this you may need to disable and/or uninstall Xposed before doing performing these steps.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements near the top of this page, the steps would be as follows...
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next... NOTE: yes, there are a few commands being repeated, but this is intentional!!!
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready. (it could take a little longer than a normal reboot)
NOTE: if you wish to erase your data and apps during this process, just before the final reboot command, issue... mfastboot erase userdata
Click to expand...
Click to collapse
Hey.
I wanted to return to stock by flashing the parts manually.
I followed your steps but when i executed the command a message popped out saying 'Variable not supported' and it continued the execution.
I did not find any change in the system when I checked after the whole process was completed.
The message I mentioned earlier was shown for every step.
Example Code:
Code:
mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.280s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.534s]
finished. total time: 0.819s
I also flashed boot, logo, system and the others parts.
But the same message was shown every time.
And after the process was complete I restarted the phone but the 'Bootloader Unlocked Warning' screen appeared.
I hadn't removed this after I rooted the phone.
I thought it would be removed when I flashed motoboot, boot and logo.
Phone Details:
Current Android Version: 4.4.4
System Version: 212.44.26.ghost_row.AsiaRetail.en.03
Build Number: KXA21.12-L1.26
Kernel Version: 3.4.42-g50861a7
I used this image:
Drive Link:
https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?pli=1
File Factory Link:
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
I desperately need your help.
What should I so to flash the stock image properly?
Thanks in advance.
RohanAditya said:
Hey.
I wanted to return to stock by flashing the parts manually.
I followed your steps but when i executed the command a message popped out saying 'Variable not supported' and it continued the execution.
I did not find any change in the system when I checked after the whole process was completed.
The message I mentioned earlier was shown for every step.
Example Code:
Code:
mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.280s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.534s]
finished. total time: 0.819s
I also flashed boot, logo, system and the others parts.
But the same message was shown every time.
And after the process was complete I restarted the phone but the 'Bootloader Unlocked Warning' screen appeared.
I hadn't removed this after I rooted the phone.
I thought it would be removed when I flashed motoboot, boot and logo.
Phone Details:
Current Android Version: 4.4.4
System Version: 212.44.26.ghost_row.AsiaRetail.en.03
Build Number: KXA21.12-L1.26
Kernel Version: 3.4.42-g50861a7
I used this image:
Drive Link:
https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?pli=1
File Factory Link:
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
I desperately need your help.
What should I so to flash the stock image properly?
Thanks in advance.
Click to expand...
Click to collapse
Based on what you posted, I'm not completely sure of your question. I mean if you think you are not stock because you still have the unlocked bootloader warning message after flashing, that is normal if you've ever unlocked your bootloader.
Out of box LOCKED bootloader shows Locked Status 0... After unlocking, it shows Unlocked Status 3. If you attempt to relock it, it will show as Locked Status 2. We don't have a way to get back to Locked Status 0. That being said... If the status is NOT 0, you'll always get the Unlocked Bootloader Warning when using the stock/standard LOGO.BIN.
KidJoe said:
Based on what you posted, I'm not completely sure of your question. I mean if you think you are not stock because you still have the unlocked bootloader warning message after flashing, that is normal if you've ever unlocked your bootloader.
Out of box LOCKED bootloader shows Locked Status 0... After unlocking, it shows Unlocked Status 3. If you attempt to relock it, it will show as Locked Status 2. We don't have a way to get back to Locked Status 0. That being said... If the status is NOT 0, you'll always get the Unlocked Bootloader Warning when using the stock/standard LOGO.BIN.
Click to expand...
Click to collapse
Okay I unlocked it. The code is 3.
Thanks
But how do I know if I'm ready to receive the OTA?
Is there a way to find out if I can receive it without it resulting in a brick?
And is the Variable not supported message normal?
Or have I done something wrong?
Thanks in advance
RohanAditya said:
Okay I unlocked it. The code is 3.
Thanks
But how do I know if I'm ready to receive the OTA?
Is there a way to find out if I can receive it without it resulting in a brick?
And is the Variable not supported message normal?
Or have I done something wrong?
Thanks in advance
Click to expand...
Click to collapse
Variable not supported is normal and nothing to worry about.
Because each OTA is different and looks at different aspects of the phone (based on what it will upgrade, or not), there is no way to tell you exactly what should be checked.
If you returned to stock by flashing the COMPLETE STOCK ROM (all parts of SBF) for your carrier/model with mFastboot, and received no errors (other than variable not supported), and your bootloader version is consistent with the ROM on your phone (i.e. you didn't attempt to downgrade), then you should be ready for the OTA...
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.