Database Users

[Q] OTA Relocked Bootloader, Bricked Device

Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e94557, 2013-05-24 14:49:34)
eMC Info: Size 8GB
Device is LOCKED, Status Code 0
Battery OK
Transfer Mode:
USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
Click to expand...
Click to collapse
Anyone got any ideas what might have caused this, and what can be done to fix it?

Leraeniesh said:
Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
Anyone got any ideas what might have caused this, and what can be done to fix it?
Click to expand...
Click to collapse
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn

ATTACK said:
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
When flashing anything via fastboot (or mfastboot)
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32KB)...
OKAY [ 0.074s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.383s
Click to expand...
Click to collapse

Leraeniesh said:
When flashing anything via fastboot (or mfastboot)
Click to expand...
Click to collapse
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.

ATTACK said:
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.
Click to expand...
Click to collapse
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
EDIT: Was able to get it to flash using HouseofMoto's RSD XML.
All good

Leraeniesh said:
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
Click to expand...
Click to collapse
And you tried to restore 98.30.1? I know with the leak, it is a two part flashing process. It will reboot after part 1, then you need to reboot into recovery to start part 2. You may need to wait until there's a FXZ to fix it.

This is scary. Ive just RSD'd back to stock and am about to update my phone with all the OTA's. Perhaps ill stop for now.
EDIT: And the OTA process just failed from Stock update. FML.

Maybe try this? This is sourced from Moto's website
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91999/p/1449,8620

If anyone else experiences something similar, you can follow jimyv's post regarding setting up RSD to flash (despite something going wonk with the partition table)

I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated

techfellow said:
I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated
Click to expand...
Click to collapse
How did "everything fail?" Just need more details.

xKroniK13x said:
How did "everything fail?" Just need more details.
Click to expand...
Click to collapse
I've been trying this for the past 2 days. I just tried it again so I can give you details, and it worked without any issues, so I'm good.
Thanks to all the previous posters, and the house of moto maker.

[GUIDE][NOOB FRIENDLY] Explaining Boot loader Locking [ERROR][FIX]

Hi , guys after been long time i jumped from my old Galaxy Ace to these MOTO G2 , the concept of rooting and flashing on the Ace was very different from these new devices , we used to have one click flash got ROOT and again with one flash we got UNROOT , tada !
But in these devices for rooting we need to first unlock the boot loader and then we are free to root it or flash or any modding , but what if have to unroot and lock the boot loader ? , though unrooting is a quite a just one click we got unrooted phone but at the time of locking Bootloader we face errors .But why to lock it again ? though every one has different thinking but these is for those who want to lock . But at the time of locking ERRORS What are they ? how to solve them ? searching over the whole Internet but didn't found a proper solution ! So these type of situation is very critical for new users who are new to these like me ( jokes apart) . So below i have explained a little bit & a fail safe process , I am not taking about tools and download links for them just a process .
Click to expand...
Click to collapse
Various ERRORS which we face like
Code:
(bootloader) sst lock failure!
OKAY [ 0.011s]
finished. total time: 0.012s
Code:
failed to validate system image
Code:
Executing ".\Windows\fastboot.exe flash boot boot.img"
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.505s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.090s
Click to expand...
Click to collapse
These type of error we face while locking boot loader , now do note these things first of check out the build number of your phone & download the same build number firmware , or if there is updated version then you can download that . Because OEM doesn't allow you to downgrade the system it will give you error like system downgrade started & then failed to validate system image so flash the same build version firmware or higher one . By doing these follow the same steps as stated here @archies20 in his thread
Click to expand...
Click to collapse
Code:
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
Click to expand...
Click to collapse
Now by following the above procedure in the between watch out in your phone the screen will be black , and you will get to see the Locked status will be written after that the last error will be like
Code:
C:\MOTOROLA\mfastboot-v2>mfastboot.exe oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 20.117s
But don't get panic the boot loader will be locked still the Unlock warning logo will be there so just flash the logo.bin .
Click to expand...
Click to collapse
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
Code:
(bootloader) sst lock failure!
OKAY [ 0.011s]
finished. total time: 0.012s
so follow the above procedure only , if you checked out the whole thing then there will be 0% chances of failing .
I hope you will found these thread very helpful ,
Thankyou
Click to expand...
Click to collapse
.
EDIT : You can downgrade via Fastboot not mFastboot.

Bootloader warning
I followed the steps exactly , and the only error occurred was the one you mentioned ,
but the "bootloader unlocked warning " still remains after i flashed the logo
what is the soulution ?
thankyou,

Good job hitesh :good:

If i relock the bootloader will miss the root?

Sebastian94 said:
If i relock the bootloader will miss the root?
Click to expand...
Click to collapse
Yes.

archies20 said:
Good job hitesh :good:
Click to expand...
Click to collapse
Thanks buddy , just i cleared all doubt's and errors .

ghostcoder said:
I followed the steps exactly , and the only error occurred was the one you mentioned ,
but the "bootloader unlocked warning " still remains after i flashed the logo
what is the soulution ?
thankyou,
Click to expand...
Click to collapse
First just check the Bootloader status in bootloader menu , if it is locked then just flash the logo.bin that's it .

OK, first you are giving instructions to flash the firmware and then to send command "lock oem" (the last line).
Later in your post:
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
sst lock failed.
This is exact error everyone gets, even following your steps (lock begin -> flash firmware -> oem lock).
This guide is misleading.

linasmit said:
OK, first you are giving instructions to flash the firmware and then to send command "lock oem" (the last line).
Later in your post:
Note : Don't try to lock the boot loader after flashing the firmware it will give you error like
sst lock failed.
This is exact error everyone gets, even following your steps (lock begin -> flash firmware -> oem lock).
This guide is misleading.
Click to expand...
Click to collapse
You are not getting properly , i told that after flashing firmware and after booting it , then taking back into boot loader now in these state if you will give command then it wont work !!
That's the point i have explained in that Note .
And above what ever i have written it is 100% working not only tested by but also some other users .

Cannot relock bootloader
Hitesh2626 said:
.
Click to expand...
Click to collapse
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
Click to expand...
Click to collapse
my mobile version info is attached

Anonymous 360 said:
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
my mobile version info is attached
Click to expand...
Click to collapse
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:

pradeepmaddy said:
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:
Click to expand...
Click to collapse
You can try this, for the first time with US version, as far as i can remember, it worked for me. But now, after downgrading and changing back to the global version, it is not working.....
Fastboot oem lock begin
Fastboot flash partition gpt.bin
Fastboot flash motoboot motoboot.img
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot erase cache
Fastboot erase userdata
Fastboot oem lock
Fastboot reboot
Click to expand...
Click to collapse
please, inform me, if it works

Anonymous 360 said:
You can try this, for the first time with US version, as far as i can remember, it worked for me. But now, after downgrading and changing back to the global version, it is not working.....
please, inform me, if it works
Click to expand...
Click to collapse
The user u have quoted is trying to lock the bootloader for Global version retaildsds.en03
If it works then its well & good..

Solved! Solved! Solved!
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps

Anonymous 360 said:
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps
Click to expand...
Click to collapse
Do you still have your device rooted after lollipop update?

Anonymous 360 said:
I have Global version. then flashed US version and upgrade to lollipop. Later decided to go back to Global version for using CF-autoroot. SO I downgraded to KitKaT US first. I again then changed to global version.
The problem is, now, I cannot relock bootloader. I can chage to us and also in us version i cannot relock.
While I flash Fastboot flash boot boot.img it says downgrading; same for Fastboot flash system system.img_sparsechunk.0; downgrading error as well as invalid piv signed system image error.
Thus after mfastboot.exe oem lock command, it gives SST lock failure ! failed to validate system image in device display.
Applied flash according to :
my mobile version info is attached
Click to expand...
Click to collapse
Anonymous 360 said:
YEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!
After lots of flashing, at last ::fingers-crossed:
followed these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da.... explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
Hit thanks if it helps
Click to expand...
Click to collapse
bro am in kitkat now... i dont want to go with us variants again but i want to lock boot loader in kitkat itself please give me the solution for tht

I afraid I do not have a solution......
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
You still have SU app, but you will not have the binary, so you have to appy CF auto root : http://forum.xda-developers.com/moto-g-2014/help/solved-cf-chainfire-autoroot-problem-t2942154

Help please
pradeepmaddy said:
+1 i cant flash the stock rom with mfastboot.exe oem lock begin if i use tht command .. am facing failed to validate system image plz help me to get out of here plz:crying:
Click to expand...
Click to collapse
I've got an XT1068 bought in UK.......and stuck with the same problem after upgrading to lollipop (xt1063 way) and downgrade.
I cant' lock the bootloader and if I install a stock firmware trying to locking it i receive a lot of FAILED messaged (in partition,motoboot,boot, system system.img_sparsechunk1-2-3....) And can't lock with "SST lock failure ! failed to validate system image" error.
What I have to do? T_T Can someone help me please? I want to bring back everything as before...clean!
If I try to install a stock rom and i don't try to lock the bootloader i receive FAILED error only in the first 2 strings
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
and this never happen. What I have to do for locking the bootloader again? :\ I try with fastboot instead of mfastboot commands too..but...same results.
Thanks.... :crying:

After reading numerous threads about relocking the bootloader, I came to the conclusion that after a downgrade it's simply impossible to relock the bootloader.
So, if you have, for instrance, an XT1068 and you have flashed the US build of Lollipop on it, the only way to make it 'stock' is to downgrade to KitKat, since there is no official Lollipop build for the XT1068 yet. This means that you will be unable to lock the bootloader. You'll have to wait for an official Lollipop build, install that manually, and then relock the bootloader.
So in short: after a downgrade (as from Lollipop to Kitkat) it's impossible to lock the bootloader!
Please correct me if I'm wrong!

smitharro said:
After reading numerous threads about relocking the bootloader, I came to the conclusion that after a downgrade it's simply impossible to relock the bootloader.
So, if you have an XT1068 and you have flashed the US build of Lollipop on it, the only way to make it 'stock' is to downgrade to KitKat, since there is no official Lollipop build for the XT1068 yet. This means that you will be unable to lock the bootloader. You'll have to wait for an official Lollipop build, install that manually, and then relock the bootloader.
Please correct me if I'm wrong!
Click to expand...
Click to collapse
According Motorola downgrading from lolipop to kitkat is not possible
Moto G (2nd Generation) - Android™ 5.0 Lollipop - Release Notes
INTRODUCTION
We are excited to announce a new software update for Moto G (2nd Generation) by Motorola. This update brings Android™ 5.0 Lollipop to your phone along with other improvements.
For more information on Motorola updates and repairs, visit us at www.motorola.com/mymotog.
NOTE: You cannot downgrade to a previous software version after installing this update.

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.

Moto G4 retus XT1625, fail at install OTA NPJ25.93-14

Hello everyone
2 days ago I received the message that finally the update for my device was available, specifically NPJ25.93-14, the download was made and proceeded to install, the installer only advanced very little and failed the installation, I check the recovery log And so I could understand the installation script failed because I did not find the expected base version:
Verifying Current System
script aborted: Error E3002:
Packaged expects build thumbprint of 7.0/NPJ25.93-14/16:user/release-keys or
6.0.1/MPJ24.139-48/48:user/release-key; this device has 6.0.1/MPJ24.139-64/65:user/release-key
E:Error in @/cache/recovery/block.map
I would appreciate your help in analyzing the cause of failure in the installer and how I can solve it to perform the installation of the update successfully.
Thank you

what the.., i don't know why the log says " 6.0.1/MPJ24.139-64/65" if you really have 48. So.. maybe you can reinstall your rom

lerg96 said:
what the.., i don't know why the log says " 6.0.1/MPJ24.139-64/65" if you really have 48. So.. maybe you can reinstall your rom
Click to expand...
Click to collapse
In fact I did, reinstall the firmware using the official provided by motorola.

suarezj said:
In fact I did, reinstall the firmware using the official provided by motorola.
Click to expand...
Click to collapse
did you install in the past a -64 rom?
Maybe if you had 64 previously and you tried to install 48 it really was not installed correctly because it was a downgrade
There is not a ota for -64 that you can use for nougat around the forum?

like many of us, I have a rooted, bootloader unlocked retus xt1625 with TWRP installed. Has anyone been able to get the nougat update to install? My version is MPJ24,139-49
I tried to run the update and it booted into my twrp recovery. But I got the same message as above
Does some sort of downgrade need to happen allow it to accept the update?

lerg96 said:
did you install in the past a -64 rom?
Maybe if you had 64 previously and you tried to install 48 it really was not installed correctly because it was a downgrade
There is not a ota for -64 that you can use for nougat around the forum?
Click to expand...
Click to collapse
honestly I can't ensure if the phone had a firmware version 64 or not, i've changed firmware 2 times, both firmware were stock Motorola.
I'm going to check my computer, I sure leave a copy of the firmware that I installed at that moment and I'll be able to check the version
*******************************************************************************************************
Following the recommendation, perform a firmware download provided by motorola again, I did a clean installation again and the result is exactly the same again, the motorola website indicates that the version is 64, but the phone still indicates is The installed version is 48. Assuming I could have done a dowgrade from 64 to 48, the question is, is there a way to correct this?

well buddy, really i can't tell you. Maybe you can try forcing a update downloading the ota and changing the line that verify your rom in the zip file. If you're in the correct build version for the update maybe you can have a success update
For all this process you need TWRP, because the stock recovery verify if the zip file is signed. (Motorola and i are not responsible for any damage)

Finally solved
suarezj said:
Hello everyone
2 days ago I received the message that finally the update for my device was available, specifically NPJ25.93-14, the download was made and proceeded to install, the installer only advanced very little and failed the installation, I check the recovery log And so I could understand the installation script failed because I did not find the expected base version:
Verifying Current System
script aborted: Error E3002:
Packaged expects build thumbprint of 7.0/NPJ25.93-14/16:user/release-keys or
6.0.1/MPJ24.139-48/48:user/release-key; this device has 6.0.1/MPJ24.139-64/65:user/release-key
E:Error in @/cache/recovery/block.map
I would appreciate your help in analyzing the cause of failure in the installer and how I can solve it to perform the installation of the update successfully.
Thank you
Click to expand...
Click to collapse
Well, I've finally been able to resolve the problem with the firmware update, how? simple ..
1.- Download a firmware for the version of my phone, I decided on the 64 version due to the inconsistency that my phone had between what the updater detected and the build that the phone reported as installed. My objective was not to downgrade
I did not want to make firmware downgrade
https://firmware.center/firmware/Motorola/Moto%20G4%20%28Plus%29/Stock/XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.- I did the installation using the fastboot method
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
3.- When the phone reboot after the installation check the compilation version and the inconsistency had disappeared. Check if there were pending updates and yes, had one. Download and install without problems.
Thank you all for your time and collaboration. :good:

Installing updates after flashing back to stock

So I just flashed back to stock using this method, https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 and I was wondering if I can install updates that are pushed to me? After rebooting following the back to stock method I got a notification but it failed when I tried to install the update, I read that it doesn't matter if your bootloader is unlocked as long as your running stock updates should install, and I read that here https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 but it still failed.

MrKite4 said:
So I just flashed back to stock using this method, https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 and I was wondering if I can install updates that are pushed to me? After rebooting following the back to stock method I got a notification but it failed when I tried to install the update, I read that it doesn't matter if your bootloader is unlocked as long as your running stock updates should install, and I read that here https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 but it still failed.
Click to expand...
Click to collapse
What was the exact error? The recovery logs will tell you before you before it reboots...
Because OTA's do work after returning to stock, it has been tried and tested hundreds, probably thousands, of times.

acejavelin said:
What was the exact error? The recovery logs will tell you before you before it reboots...
Because OTA's do work after returning to stock, it has been tried and tested hundreds, probably thousands, of times.
Click to expand...
Click to collapse
I only get the little android guy on his back with the exclamation point and under it it says Error, then I'm forced to hold down the power button to reboot at which point I get the message popping up on my phone after the reboot saying "Software Update Unsuccessful. Sorry there was a problem updating your Moto X Pure Edition. No changes were made"

MrKite4 said:
I only get the little android guy on his back with the exclamation point and under it it says Error, then I'm forced to hold down the power button to reboot at which point I get the message popping up on my phone after the reboot saying "Software Update Unsuccessful. Sorry there was a problem updating your Moto X Pure Edition. No changes were made"
Click to expand...
Click to collapse
At that point, press Power and tap Vol Up and select Recovery Logs from the menu to see the full error message.

acejavelin said:
At that point, press Power and tap Vol Up and select Recovery Logs from the menu to see the full error message.
Click to expand...
Click to collapse
Alright, let me try that and see what happens.

acejavelin said:
At that point, press Power and tap Vol Up and select Recovery Logs from the menu to see the full error message.
Click to expand...
Click to collapse
This is what I'm getting,
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: motorola/clark_retus/clark:6.0M
PHS24.49-18-4/5:user/release-keys
Target: motorola/clark_retus/clark:6.0M
PHS24.49-18-8/4:user/release-keys
Verifying current system...
"/modem/image/adsp.b01" has unexpected contents.
E:Error in /cache/Blur_Version.24.221.4.clark_retus.retus.en.US.zip
(Status 7)
Installation aborted.

As I expected... it's a modem issue. You need to reflash the modem stack from MPHS24.49-18-4 firmware image with fastboot, then it should apply properly.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY response after each step... you might have to do a step more than once., then do the update and it will work.

acejavelin said:
As I expected... it's a modem issue. You need to reflash the modem stack from MPHS24.49-18-4 firmware image with fastboot, then it should apply properly.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY response after each step... you might have to do a step more than once., then do the update and it will work.
Click to expand...
Click to collapse
Worked perfectly, you're the sh*t, thank you.

MrKite4 said:
Worked perfectly, you're the sh*t, thank you.
Click to expand...
Click to collapse
Since you found the solution, it would be good if you edit the OP and add a solution section below it. That will help people who might face this error in future.

AsquareX said:
Since you found the solution, it would be good if you edit the OP and add a solution section below it. That will help people who might face this error in future.
Click to expand...
Click to collapse
I was actually trying to add "SOLVED" to my main title but I cannot edit it, only the body of my OP.