Database Users

please help

I made a nonsense of wanting to return to jelly bean KitKat with rsd lite and gave me an error and every time I turn on the initial cel fastboot .... as usual do to restart please help

c_v_S said:
I made a nonsense of wanting to return to jelly bean KitKat with rsd lite and gave me an error and every time I turn on the initial cel fastboot .... as usual do to restart please help
Click to expand...
Click to collapse
Are you on an unlocked bootloader? If not, you cannot downgrade.

You can't downgrade even with an unlocked bootloader. Just tried this morning and got a security downgrade error or somesuch.
He's probably getting a flash failed error. Easiest way to fix that is just to successfully flash something simple like the logo.
fastboot flash logo logo.bin

You CAN flash back to JB from KK if you have an unlocked bootloader using RSD, I've done it a few times when I tried KK.
I used VRZ_XT907_9.8.1Q-94-1_CFC.xml and removed these lines.
<step var="max-download-size" operation="getvar"/>
<step var="fb_mode_set" operation="oem"/>
<step operation="flash" MD5="FB3D9083F1B5890BBF2FA8617D31A70A" filename="gpt_main0.bin" partition="partition"/>
<step operation="flash" partition="tz" filename="tz.mbn" MD5="474F31095C8146D1F86D0E5CE72B878F" />
Click to expand...
Click to collapse
Quick Edit: These two posts helped me
http://forum.xda-developers.com/showpost.php?p=52663683&postcount=181
http://forum.xda-developers.com/showpost.php?p=52607724&postcount=222
Goodluck :good:

Seriiez said:
I used VRZ_XT907_9.8.1Q-94-1_CFC.xml and removed these lines.
Click to expand...
Click to collapse
How did you know which lines were safe to omit and which to keep?
I tried just flashing system.img by itself, apparently that alone was not enough for it to boot.

GnatGoSplat said:
How did you know which lines were safe to omit and which to keep?
I tried just flashing system.img by itself, apparently that alone was not enough for it to boot.
Click to expand...
Click to collapse
I updated my post to include where I got the info from.

Help required to unbrick Motorola Electrify M (XT901)

Hi Everyone,
I own Motorola Electrify M (XT901) CDMA handset.
I had unlocked the bootloader, installed recovery-clockwork-touch-6.0.4.4-xt907.img and was running CM11 with jellybean bootloader.
I thought of flashing my mobile with stock rom of XT907. So downloaded "VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip". After extracting the contents. I executed the following commands to flash the mobile.
fastboot flash partition gpt.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
Now the mobile is not booting. Please help me to unbrick my mobile.
Regards,
Ramakrishna.

Dear friend, You cant flash your phone with SBF file of other model number.
you must flash with XT901 sbf. last build is here: Blur_Version.98.22.14.XT901.USC.en.US

mohamadreza1990 said:
Dear friend, You cant flash your phone with SBF file of other model number. you mus flash with XT901 sbf. last build is here: Blur_Version.98.22.14.XT901.USC.en.US
Click to expand...
Click to collapse
Thanks friend for the quick reply. I realized my mistake. But its too late. Now the mobile is not detected by my pc. Neither I'm unable to flash it using RSD lite nor run commands as it not detected by adb also. When I plugin by device to PC I get message drivers not installed and its asking for drivers of "qhsusb_dload". Currently I'm using windows 7 OS.
Please guide me and help me.

v2k100 said:
Thanks friend for the quick reply. I realized my mistake. But its too late. Now the mobile is not detected by my pc. Neither I'm unable to flash it using RSD lite nor run commands as it not detected by adb also. When I plugin by device to PC I get message drivers not installed and its asking for drivers of "qhsusb_dload". Currently I'm using windows 7 OS.
Please guide me and help me.
Click to expand...
Click to collapse
I googled and got the drivers. Downloaded the correct firmware for the mobile. Mobile is getting detected in RSD lite. When I try to flash it, I'm getting "The phone failed to switch to fastboot mode. ".
Please guide me and help me.

v2k100 said:
I googled and got the drivers. Downloaded the correct firmware for the mobile. Mobile is getting detected in RSD lite. When I try to flash it, I'm getting "The phone failed to switch to fastboot mode. ".
Please guide me and help me.
Click to expand...
Click to collapse
Tired fastboot -w / mfastboot -w, I'm getting "< waiting for device >"

v2k100 said:
I googled and got the drivers. Downloaded the correct firmware for the mobile. Mobile is getting detected in RSD lite. When I try to flash it, I'm getting "The phone failed to switch to fastboot mode. ".
Please guide me and help me.
Click to expand...
Click to collapse
You need to boot into fastboot, before plugging the phone into the computer.
Sent from my HTC6525LVW using Tapatalk

The sentences "fastboot flash partition gpt.bin" and "fastboot flash tz tz.mbn" has set off the alarm. You have now hardbricked it because of the bootloader signature NOT belonging to the XT901. Bootloader signatures on both gpt.bin and tz.mbn are different for each models. You might get away with flashing the unofficial XT907 kernel on XT901, although I doubt it due to bootloader differences.
But you may get pretty lucky enough to flash back to the XT901 bootloader. Hope you have enough juice in the battery, otherwise you will have to either make or buy a Motorola factory jig USB cable to force the phone to boot without the battery if s*** hits the fan.

Root..
Hey guys this has nothing to do with the post! But I have the same phone and can someone PLEASE tell me how to root it please it running android version 4.4.2.. Thanks

slgdad said:
Hey guys this has nothing to do with the post! But I have the same phone and can someone PLEASE tell me how to root it please it running android version 4.4.2.. Thanks
Click to expand...
Click to collapse
System version? Not android version
Full kernel version?
Sent from my XT907 using Tapatalk

The KitKat update was released last month, so most likely the kernel is "rather new".
It that's the case, Towelroot might be locked out, but it's still possible to unlock the bootloader via Motorola (to install a custom recovery etc.).

system version
its a motorola xt901.. system version 182.44.3.XT901.USC.en.US.... and kernel version 3.4.42-g7f16ba8-00003-gc488536... [email protected] #1.... towelroot will not work.. i tried motochopper but it will not work for the 4.4.2.. kingo will not work or framaroot also will not work..

slgdad said:
its a motorola xt901.. system version 182.44.3.XT901.USC.en.US.... and kernel version 3.4.42-g7f16ba8-00003-gc488536... [email protected] #1.... towelroot will not work.. i tried motochopper but it will not work for the 4.4.2.. kingo will not work or framaroot also will not work..
Click to expand...
Click to collapse
the kernel date is the important part of the kernel name...
---------- Post added at 02:04 PM ---------- Previous post was at 01:44 PM ----------
slgdad said:
its a motorola xt901.. system version 182.44.3.XT901.USC.en.US.... and kernel version 3.4.42-g7f16ba8-00003-gc488536... [email protected] #1.... towelroot will not work.. i tried motochopper but it will not work for the 4.4.2.. kingo will not work or framaroot also will not work..
Click to expand...
Click to collapse
does this match?
System Version - 182.44.3.XT901.USC.en.US
Android Version - 4.4.2
Baseband Version - SOLSTICE_BP_105070.150.43.00R
Kernel Version - 3.4.42-g7f16ba8 - [email protected] #1 - Fri Jul 11 15:14:22 CDT 2014
Build Number - KDA20.92-3
Build Date - Fri Jul 11 14:59:57 CDT 2014

Yes that's exactly what i have! ..

slgdad said:
Yes that's exactly what i have! ..
Click to expand...
Click to collapse
Hi slgdad,
I have successfully rooted my updated XT901 with 4.4.2 stock rom.
Pre-requisites
1. XT901 bootloader should be unlocked.
The steps I followed
1. Kept the mobile in fastboot mode.
2. Flashed recovery with "ClockWorkMod Recovery v6.0.4.9 for DROID RAZR HD/M" [Link to download]
fastboot flash recovery CWM6049-RAZR-HD_M-KITKAT.img
3. Loaded to recovery, install "update supersu v2.46.zip" by chainfire. I'm not sure if I can provide the link for external sites. Better search on google for the zip file.
And XT901 is rooted. I hope this helps you. Feel free to ask questions.
Note: I have not made any changes to img file or zip file. I have used as is. They are works of their respective owners. I'm just a pointer, indicating the files I used to root XT901. Please do share this post if required.
Regards,
v2k100

Thanks! I will try it! But i still have a locked boot loader. I can't find away to get it unlocked.?

slgdad said:
Thanks! I will try it! But i still have a locked boot loader. I can't find away to get it unlocked.?
Click to expand...
Click to collapse
I'm not sure about unlocking bootloader of 4.4.2. Since I had unlocked my bootloader when it had 4.1.2. Try motopocalypse to unlock the bootloader. Else visit motorola site for unlocking procedure.

require stock kit kat sbf for xt901 can anyone upload
thnks

please guide me i have same xt901 and wanna install custom rom... my mail is [email protected]

pls post me stock xt901 firmware indian version pls fast ...thanks in advanced

rohitddd1 said:
pls post me stock xt901 firmware indian version pls fast ...thanks in advanced
Click to expand...
Click to collapse
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my XT1060 using XDA Labs

Official Moto X xt 1053 stagefreight fix rolling out NOW

Personally I couldn't careless about stage freight but rather in the bug fixes and enhancements mentioned.
Alsi, will Motorola update the OS as 5.1 + stage freight vs 5.1 alone like they did with jellybean + camera update vs jellybean

What's the easiest way I can go about flashing stock in order to install the OTA. I usually use Nexus toolkit to do it with my Nexus 7, not sure the Moto equivalent though I do have RSD Lite but I don't want to erase my data when flashing stock recovery and such. I'm rooted on 5.1 tmo/unlocked with custom recovery and unlocked bootloader.
edit: I unrooted and uninstalled xposed, flashed stock recovery, boot and system img files but the OTA still failed.

A proper changelog?

Can someone create a flashable zip? I can grab the ota if needed from my XT1053.
I think I've made one myself but it's been so long I'm leary.
---------- Post added at 01:29 PM ---------- Previous post was at 01:24 PM ----------
ohmimpotence said:
What's the easiest way I can go about flashing stock in order to install the OTA. I usually use Nexus toolkit to do it with my Nexus 7, not sure the Moto equivalent though I do have RSD Lite but I don't want to erase my data when flashing stock recovery and such. I'm rooted on 5.1 tmo/unlocked with custom recovery and unlocked bootloader.
edit: I unrooted and uninstalled xposed, flashed stock recovery, boot and system img files but the OTA still failed.
Click to expand...
Click to collapse
Easiest way is to backup data via custom recovery, offload it to your pc. Flash stock using stock script, wiping it clean. Once fully up to date, custom recovery, copy backup and restore it.
USB mode in TWRP makes this relatively painless. Even if encrypted it works perfectly.

ohmimpotence said:
What's the easiest way I can go about flashing stock in order to install the OTA. I usually use Nexus toolkit to do it with my Nexus 7, not sure the Moto equivalent though I do have RSD Lite but I don't want to erase my data when flashing stock recovery and such. I'm rooted on 5.1 tmo/unlocked with custom recovery and unlocked bootloader.
edit: I unrooted and uninstalled xposed, flashed stock recovery, boot and system img files but the OTA still failed.
Click to expand...
Click to collapse
are u getting ""/system/app/3c_main.apk" has unexpected contents."?

ohmimpotence said:
What's the easiest way I can go about flashing stock in order to install the OTA. I usually use Nexus toolkit to do it with my Nexus 7, not sure the Moto equivalent though I do have RSD Lite but I don't want to erase my data when flashing stock recovery and such. I'm rooted on 5.1 tmo/unlocked with custom recovery and unlocked bootloader.
edit: I unrooted and uninstalled xposed, flashed stock recovery, boot and system img files but the OTA still failed.
Click to expand...
Click to collapse
Same thing here. It just fails with no error message.

zyldragoon said:
are u getting ""/system/app/3c_main.apk" has unexpected contents."?
Click to expand...
Click to collapse
Yes, I see this in the error log. After it first failed I unrooted and reflashed a stock factory L-5.1-LPA23.12-15 (Retail) LMR1, just to be absolutely sure I was stock.
I tried to get the OTA again and it failed again.
Here's the relevant bit from last_error_log:
Finding update package...
I:Update location: /cache/Blur_Version.222.21.15.ghost_row.Retail.en.US.zip
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified against RSA key 0
I:verify_file returned 0
Installing update...
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/platform/msm_sdcc.1/by-name/system , file system type :ext4Verifying current system...
file "/system/app/3c_main/3c_main.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
file size of "/system/app/3c_main/3c_main.apk" is 9638
sha1 of "/system/app/3c_main/3c_main.apk" is 5c1d9df1c32e8cc2f0750aec478941e5d7abe817
expected sha1 is: f9aafd2ebf8aa92804c45206f81e2b3b0904d209
cb28a4acc187de6c016ca7ba4ff9b7a5518520a2
1022009344 bytes free on /cache (9638 needed)
dumping bad file /system/app/3c_main/3c_main.apk to /cache/recovery/last_badfile
script aborted: "/system/app/3c_main/3c_main.apk" has unexpected contents.
"/system/app/3c_main/3c_main.apk" has unexpected contents.
E:Error in /cache/Blur_Version.222.21.15.ghost_row.Retail.en.US.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Also, TWRP shows the following error:
Package expects build fingerprint of motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys or motorola/ghost_retail/ghost:5.1/LPA23.12-15.5/4:user/release-keys; this device has motorola/ghost_retail/ghost:4.4/13.11.1Q2.X-69-3/51:user/release-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/cache/Blur_Version.222.21.15.ghost_row.Retail.en.US.zip'
E:Error installing zip file '/cache/Blur_Version.222.21.15.ghost_row.Retail.en.US.zip'
Click to expand...
Click to collapse
It's surprising to me that my device would have 4.4 release keys. WTF?
I've attached a couple of log files (one from the installer, one from TWRP) if anyone wants to poke around.

The other thing I noticed was that TWRP leaves the OTA zipfile in /cache, which causes the device to reboot and re-attempt the update automatically ad infinitum. So I used TWRP's file manager to move the zipfile out of /cache (and into /sdcard/Downloads so I could snag it).

vtluu said:
Yes, I see this in the error log. After it first failed I unrooted and reflashed a stock factory L-5.1-LPA23.12-15 (Retail) LMR1, just to be absolutely sure I was stock.
I tried to get the OTA again and it failed again.
Here's the relevant bit from last_error_log:
Also, TWRP shows the following error:
It's surprising to me that my device would have 4.4 release keys. WTF?
I've attached a couple of log files (one from the installer, one from TWRP) if anyone wants to poke around.
Click to expand...
Click to collapse
It seems that the sha1 in the ota does not match the sha1 in stock factory L-5.1-LPA23.12-15 (Retail) LMR1, i saw the same problem in moto's forum.
some people think that is because of unlocked bootloader, but when u try to relock your boot loader, but, it seems the Lollipop images on the factory restore page are even signed correctly, so we cannot even relock the bl now.
so i think we have to wait moto to give us another version of OTA file

This is the OTA file: https://mega.nz/#!NcsDQISa!Q1KWQJpRE-iey897T8JdiVNlNscscS4WXOvsxAratIY

i tried use system update, update from sd card, update from ads
no one works
the sha1 in update-script does not match

vtluu said:
The other thing I noticed was that TWRP leaves the OTA zipfile in /cache, which causes the device to reboot and re-attempt the update automatically ad infinitum. So I used TWRP's file manager to move the zipfile out of /cache (and into /sdcard/Downloads so I could snag it).
Click to expand...
Click to collapse
Um, usually you need STOCK recovery to flash an OTA. TWRP doesn't work.

KidJoe said:
Um, usually you need STOCK recovery to flash an OTA. TWRP doesn't work.
Click to expand...
Click to collapse
I did try the stock recovery first (I reflashed every factory partition image including recovery), and that didn't work.
I only installed TWRP after the stock recovery failed so I could get more information about how the update was failing. (And also so I could reinstall SuperSU.)
TWRP has worked for me with previous OTAs I think. I mean from the looks of it, it's opening and executing the update script like the stock recovery would; why would it necessarily not work (other than possible compatibility issues)?

The ota file is bad, it needs to be fixed.

Glad I'm not the only one with this same issue

The solution to apply the OTA is to use a firmware from here as well as to either use RSD lite or the following commands to flash it:
Code:
./mfastboot erase cache
./mfastboot erase userdata
./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 customize
./mfastboot erase clogo
./mfastboot oem fb_mode_clear
It was working for me on a XT1053 DE.

---------- Post added at 08:03 AM ---------- Previous post was at 07:55 AM ----------
Benoe said:
The solution to apply the OTA is to use a firmware from here as well as to either use RSD lite or the following commands to flash it:
Code:
./mfastboot erase cache
./mfastboot erase userdata
./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 customize
./mfastboot erase clogo
./mfastboot oem fb_mode_clear
It was working for me on a XT1053 DE.
Click to expand...
Click to collapse
I've downloaded the official firmware from Motorola and the update it's not working. What's the difference between this files? I mean the Motorola official firmware and the one you have shared?
What I have seen from this thread, Motorola stock firmware already users those steps when flashing. http://forum.xda-developers.com/showpost.php?p=55516176&postcount=8
Will that make a difference if reflashing stock firmware and using your flash instructions than official stock flash instructions?

Luescoff said:
---------- Post added at 08:03 AM ---------- Previous post was at 07:55 AM ----------
I've downloaded the official firmware from Motorola and the update it's not working. What's the difference between this files? I mean the Motorola official firmware and the one you have shared?
What I have seen from this thread, Motorola stock firmware already users those steps when flashing. http://forum.xda-developers.com/showpost.php?p=55516176&postcount=8
Will that make a difference if reflashing stock firmware and using your flash instructions than official stock flash instructions?
Click to expand...
Click to collapse
The method is not working with stock firmware directly from motorola, I tried that. The phone gets stock, but the ota upgrade fails.
I suppose the other firmware is also original, that's why the OTA works with it. I don't know why there is any difference, why there are more 5.1 firmwares

Yeah, I brought my XT1053 back to stock 5.1 using the Motorola official firmware download (TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz) from their site, but the OTA update for Stagefright still fails. It's odd, because flashing to stock worked for all the prior OTAs; something seems to be different about this one that's causing it to fail even on a phone that's been rolled back to stock in some circumstances.
Is the 5.1 firmware from Motorola firmware center link from above actually different in some significant way such that it would allow the OTA update to succeed where it fails with the "official" download?
EDIT: I just downloaded the firmware from the link above, and all of the components have different file hashes than the official firmware does, so it isn't just a repackaged version of the main firmware. Given all the issues surrounding the gpt/motoboot files, I don't know if it's particularly safe to flash the files from that motofirmware.center link or not.
EDIT 2: Flashed the motofirmware.center firmware (GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip) and re-ran the OTA update; everything went smoothly. It looks like there's some sort of issue with the "official" firmware from Moto's site.

I took it. I am unrooted. Boot unlocked .
Strangest thing is that after the app optimization which took around 15 min, the phone is faster and cooler. And get this, I do NOT see cell stand by drain in the battery stats. Will give it a couple of cycles and confirm back.

XT1053 222.27.5 Stagefright OTA Update Guide

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.

htc u ultra - sideload OTA flash file

Hello Guys,
I have a U Ultra with a boot problem.
Failure: It starts, show up the logo for a short time, than it shut down.
In fastboot mode the lock status is relocked. Flashing in fastboot there is no chance. Because the OEM Unlock flag in the rom is off. The recovery does nothing, same behavior as on startup...
The only way to get the phone back to life is the sideload via OTA flash zip file on a sdcard.
Problem: I don't have such a file with os 2.21.410.1, I have only a 1.64.401.10 file.
If I try this file it shows me a Version Androis-Info Error.
Where can I get such a flash file with the version 2.21.401.1 with oreo (european version)?
On the other side I try to patch the info.bin file but , the version is easy to patch but it seems so that this file has a byte in front, that changed in a unknown way and 8 bytes in the middle of the file with the same problem, this could be a file size or checksum I don't know what it is and how it will be generated. The rest of the file is filled with zeroes.
Does somebody have information about the file structure of the info.bin in the flash file?
I heared about LeeDrOiD, that he worked a long time for HTC, maybe he could help to get this phone back to life????
Phone Info:
C:\ADB>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: ************
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: ***************
(bootloader) version-main: 2.21.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__034
Hope someone can help me...
davii

good/bad news
hi guys,
I run thru the infos from an other post here in the forum and that I have done successfully.
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
The behaviour is now a bit different, it runs now in a boot loop, the logo has change to the normal htc logo without red text. The recovery shows a red exclamation mark, and run in the bootloop...
The main problem remains, I need a 2.21.401.1 firmware file to flash on the phone... what a m....
I can't find such a file in the internet, the exe firmaware files end up on version 1.64... and I think, this are only us version files. I need HTC__034.
Any ideas?
Is it possible to patch a lower version of a firmware rom just to get the phone running, to open the OEM unlock, and than to flash whatever? I have an twrp backup of my mobile.
The firmware.zip file from @minhnewpro in OTA, where does it come from? The OTA looks like a twrp or titanium backup file. But I can't get it in my mobile without twrp...
Were it possible to integrate the twrp.img in the firmware.zip file as recovery partion? Would it help at all without the open bootloader, can twrp write things with a locked bootloader? I'm not so firm in that matter... In my understanding of this matter it can???
davii

davi133 said:
hi guys,
I run thru the infos from an other post here in the forum and that I have done successfully.
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
The behaviour is now a bit different, it runs now in a boot loop, the logo has change to the normal htc logo without red text. The recovery shows a red exclamation mark, and run in the bootloop...
The main problem remains, I need a 2.21.401.1 firmware file to flash on the phone... what a m....
I can't find such a file in the internet, the exe firmaware files end up on version 1.64... and I think, this are only us version files. I need HTC__034.
Any ideas?
Is it possible to patch a lower version of a firmware rom just to get the phone running, to open the OEM unlock, and than to flash whatever? I have an twrp backup of my mobile.
The firmware.zip file from @minhnewpro in OTA, where does it come from? The OTA looks like a twrp or titanium backup file. But I can't get it in my mobile without twrp...
Were it possible to integrate the twrp.img in the firmware.zip file as recovery partion? Would it help at all without the open bootloader, can twrp write things with a locked bootloader? I'm not so firm in that matter... In my understanding of this matter it can???
davii
Click to expand...
Click to collapse
Well, i used to have U Ultra and now it is dead =] and i can not do anything (Hardware problem), even i tried flash RUU by CMD or SD Card.
Back to your question. Maybe you only can try to boot into DOWNLOAD MODE => Bootloader => recovery => apply ota update.zip

minhnewpro said:
Well, i used to have U Ultra and now it is dead =] and i can not do anything (Hardware problem), even i tried flash RUU by CMD or SD Card.
Back to your question. Maybe you only can try to boot into DOWNLOAD MODE => Bootloader => recovery => apply ota update.zip
Click to expand...
Click to collapse
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:

davi133 said:
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
Click to expand...
Click to collapse
hey guys, I have another idea...
my wifes mobile is the same..., and that mobile is on 1.64...,
were it possible to initiate the update on 2.21..., and then it downloads the update file. Where resides this update file? Can I get this file from my wifes mobile, to flash it on my mobile?
Does anybodey know this?
In my opinion this process is the same as the RUU flash, the file must be on a special partition, I think, then the mobile goes into RUU flash mode, and the command are fired to flash this rom, thats what I think...
davii

davi133 said:
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
Click to expand...
Click to collapse
Try to reflash OTA.zip by using stock recovery, maybe it will works.

minhnewpro said:
Try to reflash OTA.zip by using stock recovery, maybe it will works.
Click to expand...
Click to collapse
the recovery don't comes up, it also hangs in a bootloop. Or do you mean something different?
I can go to the fastboot mode, or in the bootmode for recovery, that dosen't help, I have no OTA with 2.21.401.1, that I could flash, just a lower version (1.64.401.10), that will be rejected by the RUU flash in because of the wrong version. To change the version in the bootloader I need a open bootload and a running os with adb, all that isn't the case.
I need OTA flashable rom with the 2.21.401.1 version to run it with RUU flash, and if this works is will work, that is the next question..., I think and hope it will work...
Why does the recovery didn't comes up, maybe that is the same problem as in the boot situation, the dead boot.img or a corrupted os, I don't know the reason, my last flash was a LeDrOiD, the boot.img maybe does no fit the original boot process. On the other hand, LeDrOiD was also an Oreo rom, as I had a problem with my magisk update I put back my original boot.img from my mobile backup, and my mobile boots up normaly, then I flashed back the LeDrOiD system things and it boots up normaly and magisk was fine.
I don't know whats wrong, why the recovery was gone, why the boot.img dosen't work and so on...
where resides the recovery.img? In the same partition as the boot partition or on its own partition?
Any other ideas?

davi133 said:
the recovery don't comes up, it also hangs in a bootloop. Or do you mean something different?
I can go to the fastboot mode, or in the bootmode for recovery, that dosen't help, I have no OTA with 2.21.401.1, that I could flash, just a lower version (1.64.401.10), that will be rejected by the RUU flash in because of the wrong version. To change the version in the bootloader I need a open bootload and a running os with adb, all that isn't the case.
I need OTA flashable rom with the 2.21.401.1 version to run it with RUU flash, and if this works is will work, that is the next question..., I think and hope it will work...
Why does the recovery didn't comes up, maybe that is the same problem as in the boot situation, the dead boot.img or a corrupted os, I don't know the reason, my last flash was a LeDrOiD, the boot.img maybe does no fit the original boot process. On the other hand, LeDrOiD was also an Oreo rom, as I had a problem with my magisk update I put back my original boot.img from my mobile backup, and my mobile boots up normaly, then I flashed back the LeDrOiD system things and it boots up normaly and magisk was fine.
I don't know whats wrong, why the recovery was gone, why the boot.img dosen't work and so on...
where resides the recovery.img? In the same partition as the boot partition or on its own partition?
Any other ideas?
Click to expand...
Click to collapse
Try extract recovery from ota.zip file and flash in download mode.

minhnewpro said:
Try to reflash OTA.zip by using stock recovery, maybe it will works.
Click to expand...
Click to collapse
hey dude,
please don't be serious but have you read my starting thread?
The bootloader is locked, you can't flash anything with fastboot! The only way to flash something is over RUU flash, so I'm a bit confused about your proposals :angel:
I hope I don't missunderstand things, because you are a senior member, and I do not want to upset anyone.
There is no OTA on the mobile so that the recovery can do it's job.
Wich OTA you mean? The real OTA from HTC look like:
OZA.zip
info.bin
zip_0.zip
zip_1.zip
etc...
Your and the other OTA's look like this:
OTA.zip
[dir] META-INF
[dir] preload
contexts.bin
etc....
Your OTA's are flashable from twrp, made with (I don't know, titanium backup)
A RUU flash want me to pass a real HTC OTA with a version higher or equal to that version that is installed before...
I know, there is a possibility to extract your OTA's but what is it good for? fastboot can't flash the recovery.img because the bootloader is locked.
That's my actual understanding of this matter and that's the behavior of the mobile.
If I'm wrong with something, please let me know.
davi133

new information on my side
The recovery comes up with these special key's (wait for the red exclamation, press power + VolUp).
Ok, but the information from htc support "WIPE DATA/FACTORY RESET" leads also to no success. Everything was made fine but after reboot is the bootloop.
The new menu in the recovery offers me to flash a real OTA from a ADB process or a SDcard, hmm, ok there is controled way now for doing this but I tryed all may real OTA's without success, because of the lower version or false cid's.
I asked the support for an actual OTA update file, but I dont think that they will give me that file.
The ADB process is a very restricted version of ADB, that mean's you can't get a shell or something like that, just the sideload and print some variables...
Is it possible to extract the real OTA, change something, and repack it?
davi133

davi133 said:
The recovery comes up with these special key's (wait for the red exclamation, press power + VolUp).
Ok, but the information from htc support "WIPE DATA/FACTORY RESET" leads also to no success. Everything was made fine but after reboot is the bootloop.
The new menu in the recovery offers me to flash a real OTA from a ADB process or a SDcard, hmm, ok there is controled way now for doing this but I tryed all may real OTA's without success, because of the lower version or false cid's.
I asked the support for an actual OTA update file, but I dont think that they will give me that file.
The ADB process is a very restricted version of ADB, that mean's you can't get a shell or something like that, just the sideload and print some variables...
Is it possible to extract the real OTA, change something, and repack it?
davi133
Click to expand...
Click to collapse
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button

thank you
Siluxsept said:
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
Click to expand...
Click to collapse
been waiting for this firmware also..i will try this hope everything works

update
the flashing was succesfull on my htc ultra and its works..hope this can help also the op..

Siluxsept said:
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
Click to expand...
Click to collapse
Thanks for this