Database Users

[TUTORIAL] Going back to KK from Soak Lollipop

Hello, I'm trying to help people who installed the soak test of Lollipop but is not enjoying the ROM with lots of bugs and want to go back to KK.
THIS IS ONLY FOR XT1225, BRAZILIAN FIRMWARE RETAIL UPDATED VIA OTA
YOU NEED TO HAVE YOUR BOOTLOADER UNLOCKED
It will work even if you have root on lollipop
Do it at your own risk!
So, this is the procedure:
DOWNLOADS
1 - Download the Stock ROM from here:
RETBR_XT1225_4.4.4_KXG21.50-9
2 - Download Motorola Drivers from HERE
3 - Download Moto Fastboot from HERE
* IT NEED TO BE MOTO FASTBOOT, known as "mfastboot" . Android Fastboot wont handle the system flash.
INSTRUCTIONS
1 - Backup your phone, otherwise you will lose everything on it
2 - Extract ROM files to a folder (I did on " C:\MAXX\ " )
3 - Extract Moto Fastboot files on same folder you extracted the ROM
4 - Shutdown your phone and put it on fastboot mode (when off, press Power Button + Volume down)
5 - Plug your phone on your PC
6 - Install Motorola Drivers NOW. (For me it only install the driver at this time. If you have the proper driver installed already, skip this step)
7 - Open a command prompt and go to the folder that you extracted the ROM and Moto fastboot
8 - Now, you need to type every line, pressing enter when is a new line and waiting the process to be sucessfully
Code:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
For me it worked, now your phone will reboot and boot right again on KK
I had tried to do with RSD Lite but it always fail on flash the partition.
So, this procedure above is tested by me and it works.

Well all i just did was to restore my twrp backup and then flash my radio.img and that's it didn't lose anything and my cell works like charm just like before flashing lollipop

These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!

Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
remember that this tutorial is ONLY FOR WHO UPDATES WITH OTA.
if u updated the phone with official OTA ,u can t downgrade to 4.4.4
or if the firmware img of 5.0.2 will go out and u will flash it U CAN T GO BACK TO 4.4.4 either.
always make a nandroid backup in twrp of 4.4.4 .it will be useful.

I've received a OTA without TWRP.... so, I did not could make a nandroid

Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
This was the case with the 2013 Moto X, there is no such problem with the 2014 model. It is unlikely to be a problem with the XT1225. Motorola learned from that mistake.

do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?

arcaneck said:
do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?
Click to expand...
Click to collapse
Did you install the lollipop via OTA after flashing brazilian firmware ?

yes i did

It's the same procedure but with the mx firmware

works fine thanks

Works for me too

do you have the mx ota?

Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!

I've installed the zip file of the soak test (I didn't receive it through OTA), will this procedure work for me? Really tired of the instability of 5.0.2

I have the same problem
megadu said:
Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!
Click to expand...
Click to collapse
I have the same problem.
After the command "mfastboot flash boot boot.img ". Do not process more.
Can anyone help me? Please!

Have you unlocked the bootloader?

boot.img can never been be downgraded. If you downgrade from version 5.x to 4.4.4 you have to skip that file.

I update my motorola using this guide http://forum.xda-developers.com/droid-turbo/general/guideinstall-lollipop-ota-root-ur-moto-t3029690 , can i do the downgrade ?
Thanks!

im have the same question, im using now cm12 with twrp, bootloader unlocked. can i go back to stock 4.4.4 using this tutorial? its safe?

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.

Yet Another Bootloop Thread

Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!

Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.

jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?

bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps

Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.

bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
fastboot oem lock begin
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 system system.img_sparsechunk.9
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
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that

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:

[Guide]relock your bl

This guide will help you re lock the bootloader and fix the bootloader is damaged error download a stock rom for the cedric extract it into adb and fast boot . (Not into its own folder just all the files in adb ) link to stock roms :
Now copy these commands
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
If it worked there shouldn't be a bl warning and in fastboot it should say flashing-locked
Note any problems caused are not my fault I have tested on my device and on g5+ both are fine !

Thank you so much, my Bootloader is locked again.
̶C̶a̶n̶ ̶y̶o̶u̶ ̶p̶l̶e̶a̶s̶e̶ ̶g̶i̶v̶e̶ ̶u̶s̶ ̶f̶i̶r̶m̶w̶a̶r̶e̶ ̶f̶i̶l̶e̶ ̶t̶h̶a̶t̶ ̶y̶o̶u̶ ̶u̶s̶e̶d̶?̶

First its the command to relock de BL?
before the commands to flash system?

AlmapekeDj said:
First its the command to relock de BL?
before the commands to flash system?
Click to expand...
Click to collapse
You need to reflash system

With me didn't worked. It says "Not signed rom"

CypherPotato said:
With me didn't worked. It says "Not signed rom"
Click to expand...
Click to collapse
Redownload stock

CypherPotato said:
With me didn't worked. It says "Not signed rom"
Click to expand...
Click to collapse
Did you get it already? Still need it?
Anyway, if anyone else needs it https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
This is the only one that worked signed for me, XT1672

my imei is 0 already tried everything but I did not have any results help me please it's an xt1672

jonathars said:
my imei is 0 already tried everything but I did not have any results help me please it's an xt1672
Click to expand...
Click to collapse
Reflash stock rom

CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
I already did this and it did not work
---------- Post added at 02:36 AM ---------- Previous post was at 02:30 AM ----------
CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
I already did this and it did not work

infixremix said:
This guide will help you re lock the bootloader and fix the bootloader is damaged error download a stock rom for the cedric extract it into adb and fast boot . (Not into its own folder just all the files in adb ) link to stock roms :
Now copy these commands
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
If it worked there shouldn't be a bl warning and in fastboot it should say flashing-locked
Note any problems caused are not my fault I have tested on my device and on g5+ both are fine !
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------
You are amazing !!

Hi,
doesn't work for me. Tried from here:
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
Moto G5 - Jan 2017 firmware NPP25.137-15 and
Moto G5 - Nov 2017 firmware NPP25.137-93 (Moto G5 - Aug 2017 firmware NPP25.137-33/NPP25.137.33-10 not tested yet).
Error when flashing boot.img:
C:\g5\010117\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.583s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 1.035s
anyone an idea what's going wrong?
D.

CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)

carlapazin said:
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
Click to expand...
Click to collapse
Yes - via fastboot
I don't know why you would want to change though
You risk either not getting ota updates or potentially hard bricking your device if you flash a future ota update if you have flashed firmware that was not designed for your phones specific varient
Unless you have physically moved locations & the firmware you are using is not compatible with the countries mobile networks I see no benefits in changing firmware versions

TheFixItMan said:
Yes - via fastboot
I don't know why you would want to change though
You risk either not getting ota updates or potentially hard bricking your device if you flash a future ota update if you have flashed firmware that was not designed for your phones specific varient
Unless you have physically moved locations & the firmware you are using is not compatible with the countries mobile networks I see no benefits in changing firmware versions
Click to expand...
Click to collapse
thanx!!!

carlapazin said:
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
Click to expand...
Click to collapse
RSD Lite only emulates Fastboot inside the application.
Idk if you can flash the stock rom with an locked bootloader, if it is signed, you can, otherwise, no.