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.

Warning: Update to LRX21Q fails when rooted.

Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.

Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.

Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.

I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.

Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.

Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.

StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...

Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot

mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?

zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them

mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .

pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.

mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .

Where can i find the images for download. Thx

Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app

Update failed on me too. Completely stock

UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really

Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.

maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google

Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L

Unable to update OTA since repair - alternatives?

Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil

clarkey586 said:
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
Click to expand...
Click to collapse
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
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 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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal

DaMadOne said:
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
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 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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
Click to expand...
Click to collapse
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:

clarkey586 said:
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
Click to expand...
Click to collapse
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* Here is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...

DaMadOne said:
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* .... is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
Click to expand...
Click to collapse
Haha suppose you're right! Sure I'll probably just wipe my device in the end, be nice to have a clean go at MM haha.
The bootloader status was indeed locked so I don't know what's causing the issue?
Anyway, thanks a million for the help I'll update if/when all goes well :good:

Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated

clarkey586 said:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
Click to expand...
Click to collapse
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.

DaMadOne said:
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
Click to expand...
Click to collapse
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!

clarkey586 said:
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
Click to expand...
Click to collapse
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.

DaMadOne said:
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
Click to expand...
Click to collapse
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again

clarkey586 said:
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
Click to expand...
Click to collapse
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?

DaMadOne said:
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
Click to expand...
Click to collapse
Had to use the 2nd OTA.zip but I didn't really try any of the remove sim card stuff or waiting long. No unlockable bootloader either but I'm satisfied for the moment haha.

Can't get December 2016 security OTA.

Hey guys, a while ago I tried going back to stock with the official Motorola Factory image. I wasn't getting any security OTAs, so I tried again with this image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip by Motorola-Firmware-Team It was an update behind despite being uploaded on 1/26/17. I totally reset my phone and now I'm getting the latest update notification, but it won't update because of this error: [IMG="Sorry for the BLUR (see what I did there?)"]
I get that this error happens a lot and yes, I know I went back to stock correctly and I'm pretty sure I flashed my modem correctly. Anyone know what I'm doing wrong?

pswiifanwmi said:
Hey guys, a while ago I tried going back to stock with the official Motorola Factory image. I wasn't getting any security OTAs, so I tried again with this image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip by Motorola-Firmware-Team It was an update behind despite being uploaded on 1/26/17. I totally reset my phone and now I'm getting the latest update notification, but it won't update because of this error: [IMG="Sorry for the BLUR (see what I did there?)"]
I get that this error happens a lot and yes, I know I went back to stock correctly and I'm pretty sure I flashed my modem correctly. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
We can't see your image of your error. Can you link a screen shot on imgur or something?

acejavelin said:
We can't see your image of your error. Can you link a screen shot on imgur or something?
Click to expand...
Click to collapse
Whoops! Sorry 'bout that! Okay, XDA won't let me post pictures since I haven't posted enough so let me try this. imgur . com / a / wYX1F
Does that work?

pswiifanwmi said:
Whoops! Sorry 'bout that! Okay, XDA won't let me post pictures since I haven't posted enough so let me try this. imgur . com / a / wYX1F
Does that work?
Click to expand...
Click to collapse
Yeah, I got it... You have a incomplete flash on 18-8 or you used a ROM not for your device. You need to reflash the modem stack from 18-8 image and try the update again.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY after each step, if you don't get one, do it again.
Then if it still fails to update, can you post output of `fastboot getvar all` and mask out your IMEI number?

acejavelin said:
Yeah, I got it... You have a incomplete flash on 18-8 or you used a ROM not for your device. You need to reflash the modem stack from 18-8 image and try the update again.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY after each step, if you don't get one, do it again.
Then if it still fails to update, can you post output of `fastboot getvar all` and mask out your IMEI number?
Click to expand...
Click to collapse
How did you know that would work?! The script I've been running had those steps in them and they said okay each time, so what made this attempt any different? Was it the cache clearing that happened right afterward that messed everything up or the lack of a reboot after flashing system, recovery, logo and boot?
I used the same files I'd been using, but I copied them again for good measure. Guess they got corrupted the first time huh?
Thanks so much for your help!

pswiifanwmi said:
How did you know that would work?! The script I've been running had those steps in them and they said okay each time, so what made this attempt any different? Was it the cache clearing that happened right afterward that messed everything up or the lack of a reboot after flashing system, recovery, logo and boot?
I used the same files I'd been using, but I copied them again for good measure. Guess they got corrupted the first time huh?
Thanks so much for your help!
Click to expand...
Click to collapse
Lucky guess, and I figured it was a radio issue from the error message. And I know the modem stack messes up a lot, especially when flashed too fast... There is a reason we recommend doing it manually and not with a script. ?

[Help] Moto x style ota update "error" in stock recovery

I was at 24.49-18-16 with unlocked bootloader and twrp and wanted to go back to stock, so i followed the guide at https://forum.xda-developers.com/mo...urn-to-stock-relock-bootloader-t3489110/page1 to do so because in it it says that having an unlocked bootloader wont prevent you applying ota updates, and there is no image or stock recovery for 18-16, so instead i downgraded to 18-8 via fastboot without unlocking the bootloader hoping i can just ota update back to 18-16, however when i try and do so in the stock recovery it just says "error"
i tried using the moto device manager on pc with all the correct drivers but it keeps saying under maintenance, so is there anyway to upgrade my device via ota back to 18-16?
Thanks

If you had TWRP your bootloader is unlocked already, shouldn't be an issue.
You can see what the error in stock recovery is when it is, when that screen is displayed hold POWER and tap VOL UP for he log and post the error message.

acejavelin said:
If you had TWRP your bootloader is unlocked already, shouldn't be an issue.
You can see what the error in stock recovery is when it is, when that screen is displayed hold POWER and tap VOL UP for he log and post the error message.
Click to expand...
Click to collapse
I did so and this came up:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: motorola/clark_reteu/clark:6.0/MPHS24.49-18-8/4:user/release-keys
Target: motorola/clark_reteu/clark:6.0/MPHS24.49-18-16/12:user/release-keys
Verifying current system...
"/modem/image/adsp.b01" has unexpected contents.
E:Error in /cache/Blur_Version.24.221.8.clerk_reteu.reteu.en.EU.zip
(Status7)
Installation aborted.

XxperexX said:
I did so and this came up:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: motorola/clark_reteu/clark:6.0/MPHS24.49-18-8/4:user/release-keys
Target: motorola/clark_reteu/clark:6.0/MPHS24.49-18-16/12:user/release-keys
Verifying current system...
"/modem/image/adsp.b01" has unexpected contents.
E:Error in /cache/Blur_Version.24.221.8.clerk_reteu.reteu.en.EU.zip
(Status7)
Installation aborted.
Click to expand...
Click to collapse
Your modem flash didn't take properly when going back to 18-8... Reflash the modem stack from 18-8
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify you get an OKAY after each step, if you don't, then repeat the command (sometimes twice) until you do, then apply the update again.

acejavelin said:
Your modem flash didn't take properly when going back to 18-8... Reflash the modem stack from 18-8
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify you get an OKAY after each step, if you don't, then repeat the command (sometimes twice) until you do, then apply the update again.
Click to expand...
Click to collapse
Ah, ur a life saver, it worked
So when the nougat update comes for my device i can upgrade without problems?

XxperexX said:
Ah, ur a life saver, it worked
So when the nougat update comes for my device i can upgrade without problems?
Click to expand...
Click to collapse
Should be able to, as long as you stay stock...
Remember, that once on Nougat you will NOT pass SafetyNet checks with an unlocked bootloader (no Android Pay, Pokemon Go, Netflix, etc) but there is no way to go back to a locked bootloader at this time so this is more of a heads up than a recommendation to do anything. Once on Nougat you can root with Magisk and do a bypass or wait for the official firmware image to be able to relock.

Hi there,
Sorry for hijacking this thread, but I've got a similar problem with the OTA update. Any help would be appreciated.
The error message I get is as follows:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: motorola/clark_reteu/clark:6.0/MPHS24.49-18-16/12:user/release-keys
Target: motorola/clark_reteu/clark:7.0/NPHS25.200-15/14:user/release-keys
Verifying current system...
E3005: "/bt_firmware/image/btfw30.tlv" has unexpected contents.
E:unknown command [log]
E:Error in @/cache/recovery/block.map
(Status7)
Installation aborted.

Stupendous said:
Hi there,
Sorry for hijacking this thread, but I've got a similar problem with the OTA update. Any help would be appreciated.
The error message I get is as follows:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: motorola/clark_reteu/clark:6.0/MPHS24.49-18-16/12:user/release-keys
Target: motorola/clark_reteu/clark:7.0/NPHS25.200-15/14:user/release-keys
Verifying current system...
E3005: "/bt_firmware/image/btfw30.tlv" has unexpected contents.
E:unknown command [log]
E:Error in @/cache/recovery/block.map
(Status7)
Installation aborted.
Click to expand...
Click to collapse
Your Bluetooth firmware is incorrect... Since you are on 18-16 already it's a little trickier, but luckily the BT firmware hasn't changed in awhile.
Find MPHS24.49-18-8 reteu and
Code:
fastboot flash bluetooth BTFM.bin
And try again... If that fails you might have to start over and go completely back to 18-8, then OTA to 18-16, then to Nougat. ?

acejavelin said:
Your Bluetooth firmware is incorrect... Since you are on 18-16 already it's a little trickier, but luckily the BT firmware hasn't changed in awhile.
Find MPHS24.49-18-8 reteu and
Code:
fastboot flash bluetooth BTFM.bin
And try again... If that fails you might have to start over and go completely back to 18-8, then OTA to 18-16, then to Nougat.
Click to expand...
Click to collapse
Thank you.
That worked like a charm on the first try. *tips hat*

acejavelin said:
Your Bluetooth firmware is incorrect... Since you are on 18-16 already it's a little trickier, but luckily the BT firmware hasn't changed in awhile.
Find MPHS24.49-18-8 reteu and
Code:
fastboot flash bluetooth BTFM.bin
And try again... If that fails you might have to start over and go completely back to 18-8, then OTA to 18-16, then to Nougat.
Click to expand...
Click to collapse
Man, Can you help me? I was on lineageOs 14.1 and flash stock ROM 29.49-18-8 and then OTA update to 18-16. But for OTA Nougat this error apear...
verifying current system...
E3005: "/system/vendor/lib/libllvm-qcom.so" has unexpected contentes.
E:unknow command [log]
thanks

acejavelin said:
Your modem flash didn't take properly when going back to 18-8... Reflash the modem stack from 18-8
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify you get an OKAY after each step, if you don't, then repeat the command (sometimes twice) until you do, then apply the update again.
Click to expand...
Click to collapse
THANK YOU!
now i can cancel my appointment at Hair Club for Men!
---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------
THANK YOU!
now i can cancel my appointment at Hair Club for Men!
acejavelin said:
Your modem flash didn't take properly when going back to 18-8... Reflash the modem stack from 18-8
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify you get an OKAY after each step, if you don't, then repeat the command (sometimes twice) until you do, then apply the update again.
Click to expand...
Click to collapse
THANK YOU!
now i can cancel my appointment at Hair Club for Men!
---------- Post added at 08:05 AM ---------- Previous post was at 08:04 AM ----------
THANK YOU!
now i can cancel my appointment at Hair Club for Men!
acejavelin said:
Your modem flash didn't take properly when going back to 18-8... Reflash the modem stack from 18-8
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify you get an OKAY after each step, if you don't, then repeat the command (sometimes twice) until you do, then apply the update again.
Click to expand...
Click to collapse
THANK YOU!
now i can cancel my appointment at Hair Club for Men!
---------- Post added at 08:09 AM ---------- Previous post was at 08:05 AM ----------
sorry for the multi post...