Database Develop

How to return xt1806 to official software status?

I flashed the stock firmware from the guide thats available, but it's on the june security patch. When I check for an update, it says my device is up to date when that's not the case since the november patch was released. When I try to relock the bootloader in attempt to change the status to official instead of modified, it says this:
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.031s
for any file I attempt to flash after "fastboot oem lock"
Any ideas?
guide I used: https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018

Which version of firmware u had last

clcseungyeon said:
I flashed the stock firmware from the guide thats available, but it's on the june security patch. When I check for an update, it says my device is up to date when that's not the case since the november patch was released. When I try to relock the bootloader in attempt to change the status to official instead of modified, it says this:
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.031s
for any file I attempt to flash after "fastboot oem lock"
Any ideas?
guide I used: https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
Click to expand...
Click to collapse
You must flash newest version of firmware
Sent from my Moto G5S Plus using XDA Labs

clcseungyeon said:
I flashed the stock firmware from the guide thats available, but it's on the june security patch. When I check for an update, it says my device is up to date when that's not the case since the november patch was released. When I try to relock the bootloader in attempt to change the status to official instead of modified, it says this:
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.031s
for any file I attempt to flash after "fastboot oem lock"
Any ideas?
guide I used: https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
Click to expand...
Click to collapse
Don't relock your bootloader, i have experienced this issue on Moto G4 plus.
Relocking will not give you official status back.
According to my experience on G4 plus,
Official status becomes Modified, when you attempt to make modification in stock ROM and stock partitions (/boot, /system, /oem, etc.)
You will get 'Offficial' status back, but not right now.
To get it, you need to take OTA update, updating your device through OTA will make it 'official' again. (I am not sure, every update does not contain update for bootloader, so every update can work or not.)
Moto gives update every 3 month, wait for March/april.
At present, flash December's update. And wait for next update.. next will make it official back..
WARNING: for taking OTA purpose, don't downgrade your firmware, taking OTA from downgraded firmware results in Hard Brickk.

Adi5 said:
You must flash newest version of firmware
Sent from my Moto G5S Plus using XDA Labs
Click to expand...
Click to collapse
I would, but where do I even find it? All I can find is the june update.

____Mdd said:
Don't relock your bootloader, i have experienced this issue on Moto G4 plus.
Relocking will not give you official status back.
According to my experience on G4 plus,
Official status becomes Modified, when you attempt to make modification in stock ROM and stock partitions (/boot, /system, /oem, etc.)
You will get 'Offficial' status back, but not right now.
To get it, you need to take OTA update, updating your device through OTA will make it 'official' again. (I am not sure, every update does not contain update for bootloader, so every update can work or not.)
Moto gives update every 3 month, wait for March/april.
At present, flash December's update. And wait for next update.. next will make it official back..
WARNING: for taking OTA purpose, don't downgrade your firmware, taking OTA from downgraded firmware results in Hard Brickk.
Click to expand...
Click to collapse
My phone hasn't given me the notification for an update, and whenever it checks for an update it says my phone is up to date so I can't do anything. It seems to not take ota's or receive them I guess. I can't even find the December update anywhere also.

yograjfire18 said:
Which version of firmware u had last
Click to expand...
Click to collapse
I was using the pixel experience rom on 8.1 but I had to flash 7.1.1. Maybe I could flash a nougat rom and then try and relock it? Either way, the only update available to manually flash is the June update and not Decembers.

clcseungyeon said:
My phone hasn't given me the notification for an update, and whenever it checks for an update it says my phone is up to date so I can't do anything. It seems to not take ota's or receive them I guess. I can't even find the December update anywhere also.
Click to expand...
Click to collapse
This is December's update :https://androidfilehost.com/?fid=889964283620776326
Again, flashing this will not give you official status back. Already said you that you have to wait for next update after this December's firmware. (March/april 2018)
If there is no update available, then you have latest firmware, check in "about'..

____Mdd said:
This is December's update :https://androidfilehost.com/?fid=889964283620776326
Again, flashing this will not give you official status back. Already said you that you have to wait for next update after this December's firmware. (March/april 2018)
If there is no update available, then you have latest firmware, check in "about'..
Click to expand...
Click to collapse
The description says it's for variant xt1805, so I'm afraid I can't use it :/ thank you though.

Needing latest up to date stock firmware

Im looking for the most latest up to date stock firmware for the 1806 US model G5S plus
Looking at
https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/
Which one(s) are for the US model and would work with it, I dont know the difference between each of the build numbers, nor do I know which would be for the various models
This bring me to another question,
If all the various global variants, aka US, GB, EU, etc were running the july security patch, for example we will say its model number is 52, where the latest January one that some got is 65.
Would all have the exact same build numbers regardless of which model of the G5S plus it is, or are some build designed for specific global variants?

xSpartacusx said:
Im looking for the most latest up to date stock firmware for the 1806 US model G5S plus
Looking at
https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/
Which one(s) are for the US model and would work with it, I dont know the difference between each of the build numbers, nor do I know which would be for the various models
This bring me to another question,
If all the various global variants, aka US, GB, EU, etc were running the july security patch, for example we will say its model number is 52, where the latest January one that some got is 65.
Would all have the exact same build numbers regardless of which model of the G5S plus it is, or are some build designed for specific global variants?
Click to expand...
Click to collapse
Flash 26.116-61-2 https://androidfilehost.com/?w=files&flid=214680
January patch,newest one

okay, thank you!

Adi5 said:
Flash 26.116-61-2 https://androidfilehost.com/?w=files&flid=214680
January patch,newest one
Click to expand...
Click to collapse
I tried, now its stuck in a boot loop :/

xSpartacusx said:
I tried, now its stuck in a boot loop :/
Click to expand...
Click to collapse
U used commands from flashfile.xml?

Actually no. i didnt know that was there... I used a guide that was on here for returning to early stock..

so how do I go about flashing this? do I just do it through twrp?

GOT IT! Now how do I go about locking the bootloader in this case? I dont think the guides here are going to help

xSpartacusx said:
GOT IT! Now how do I go about locking the bootloader in this case? I dont think the guides here are going to help
Click to expand...
Click to collapse
Ctrl C and Ctrl V this commands:
fastboot oem fb_mode_set
fastboot

I can't copy commands,write this from ss

xSpartacusx said:
so how do I go about flashing this? do I just do it through twrp?
Click to expand...
Click to collapse
How did you flash it?

(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.488s
what to do in this kind of scenerios? I updated my phone to april security update now its showing this everytime I am trying to return to stock?
any helps?

navnit75 said:
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.488s
what to do in this kind of scenerios? I updated my phone to april security update now its showing this everytime I am trying to return to stock?
any helps?
Click to expand...
Click to collapse
That's because you are flashing old firmware (compared to currently installed),
For april patch, get this one : https://androidfilehost.com/?fid=746163614322262641

____Mdd said:
That's because you are flashing old firmware (compared to currently installed),
For april patch, get this one : https://androidfilehost.com/?fid=746163614322262641
Click to expand...
Click to collapse
commands would be same right?

navnit75 said:
commands would be same right?
Click to expand...
Click to collapse
Yes,
Just a reminder: skip lock commands, if you don't want to relock bootloader..

What is OPWS27.113-45-4 (notice the S after OPW)

I am owner of Moto G6 Plus but I have noticed the images others are uploading are "OPW" releases for Moto G6 Plus. I tried flashing one but I got error. Why my stupid phone have different builds, and what's the difference in "OPW" and "OPWS" builds. I guess I cannot use firmwares uploaded here? Any hope for me?

VarunAgw said:
I am owner of Moto G6 Plus but I have noticed the images others are uploading are "OPW" releases for Moto G6 Plus. I tried flashing one but I got error. Why my stupid phone have different builds, and what's the difference in "OPW" and "OPWS" builds. I guess I cannot use firmwares uploaded here? Any hope for me?
Click to expand...
Click to collapse
I have too "S" version and I flashed successfully OPW version from this thread https://forum.xda-developers.com/moto-g6/development/firmware-moto-g6-g6plus-t3789274 (after flashing OPW version it's still showing OPWS)
What error you are getting?

Mr. Nerd_ said:
I have too "S" version and I flashed successfully OPW version from this thread https://forum.xda-developers.com/moto-g6/development/firmware-moto-g6-g6plus-t3789274 (after flashing OPW version it's still showing OPWS)
What error you are getting?
Click to expand...
Click to collapse
I didn't flash the whole firmware. I tried patched boot.img with magisk. I got error something like "partition boot-1 doesn't exist".

VarunAgw said:
I didn't flash the whole firmware. I tried patched boot.img with magisk. I got error something like "partition boot-1 doesn't exist".
Click to expand...
Click to collapse
You probably need to use "mfastboot" instead of "fastboot" command. Download this: https://androidfilehost.com/?fid=962187416754477464
Unpack it and place the boot.img in same directory. Open Command Prompt in that directory. Correct command is: mfastboot flash boot bootimagename.img
Here you can also find the correct patched boot.img: https://forum.xda-developers.com/moto-g6/how-to/guide-magisk-patched-boot-image-opw27-t3794977

Got the S too
Hi,
I bought my new Motorola G6+ Evert last week here in Mexico. (where I live)
It's fully unblocked
Version PVT1, SKU XT1926-6
Running Oreo 8.0
But I wondered me about that Build Number.
While every tutorial is saying that I can just flash TWRP with that Build-Number : OPW27.113-45-4
Because I have: " OPWS27.113-25-4 "
I've upgradet OTA and it still says, that I have the latest security patch (1. June 2018) and so on....
So I wonder if I can unlock the bootloader, flash OPW27.113-45-4 or OPWS27.113-45-4 to be able to install TWRP Recovery from
https://forum.xda-developers.com/showpost.php?p=76501832&postcount=3
Purpose:
I can't wait to get my new babe rooted to install the real hot Stuff on it.
But it's still confusing why I got that different Build Number.... Maybe it's because of my location.
But i'am not shure if it is safe to root it and to flash SuperSU and TWRP. With my B-Number.
So may some one got the right Firmware for me ?
Sunny Greetings
B2DR

OPW27.113-45 is normal firmware.
OPWS27.113-45-4 is same firmware but with new security patch.
S for Security and 4 for revision version.
You can't install a previous version of the current on the device without unlocking the bootlader.

Junior Passos said:
OPW27.113-45 is normal firmware.
OPWS27.113-45-4 is same firmware but with new security patch.
S for Security and 4 for revision version.
You can't install a previous version of the current on the device without unlocking the bootlader.
Click to expand...
Click to collapse
And what about the "-25" vs "-45"? I have the same firmware here (Argentina): OPW27.113-25
Thanks!

Also what about this version OPW27.113-89 with security patch level 1 July 2018 for Australia.

What is difference between A1 and Retail versions?

So I bought the A1 version a couple of days ago and thought it was considered the Retail, not the Google Fi one, so I flashed the stock rom for Retail. The phone worked perfectly fine, although seemed more bloated with software than it was originally. I found out it is actually the Fi version, so I went and flashed that stock rom.
Comparing the files, I noticed that the NON-HOS.bin (modem) files were not the same. They were the same size, but had different md5sums. Do they not support the same networks? I was under the assumption they both supported all US carriers, nothing was special from one version to the other.
The Android One NON-HLOS.bin was from
PAYTON_FI_8.1.0_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And the Retail NON-HLOS.bin was from
XT1900-1_PAYTON_RETAIL_8.1.0_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Any ideas why these were different? When I flashed Android One version, I had latest version. When I flashed stock, I had one ~80mb update.
The Android One baseband version is
M660_7042.27.01.74R PAYTON_NA_CUST
I did not check the Retail when I had that installed, wish I did.

Knuxyl said:
The Android One NON-HLOS.bin was from
PAYTON_FI_8.1.0_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And the Retail NON-HLOS.bin was from
XT1900-1_PAYTON_RETAIL_8.1.0_OPWS28.46-21-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Any ideas why these were different? When I flashed Android One version, I had latest version. When I flashed stock, I had one ~80mb update.
Click to expand...
Click to collapse
A1 FW contains september 2018 security patch.
Retail FW contains august 2018 security patch, ~80mb update is retail OTA with september 2018 security patch.

Comby_sk said:
A1 FW contains september 2018 security patch.
Retail FW contains august 2018 security patch, ~80mb update is retail OTA with september 2018 security patch.
Click to expand...
Click to collapse
I know the versions are different, but I don't think security patches have anything to do with the modem firmware. Security patches typically address kernel issues. I could be wrong though. Im just curious if anyone knows if there is a difference between the 2 variants of the phone's modem firmware, if there is one (assuming the security patch did not update the firmware). I would know for sure if I knew if OTA was compressed when downloaded because if not, then they definitely are different modem firmwares because the modem is 90+mb and I can get that compressed to ~45mb.

Knuxyl said:
I know the versions are different, but I don't think security patches have anything to do with the modem firmware. Security patches typically address kernel issues. I could be wrong though. Im just curious if anyone knows if there is a difference between the 2 variants of the phone's modem firmware, if there is one (assuming the security patch did not update the firmware). I would know for sure if I knew if OTA was compressed when downloaded because if not, then they definitely are different modem firmwares because the modem is 90+mb and I can get that compressed to ~45mb.
Click to expand...
Click to collapse
The OTA may or may not be compressed, but it is a block level patch. It's not the new files, but just the atomic blocks that are different between the old and new images. If only a few files change in the modem, then the patch is just the blocks that are different for those files. The ROM does a block level hash to make sure it is bit-wise identical to the image, otherwise, it will throw errors or not boot at all, depending on what level of dm-verity is enforced. The modem files could be exactly the same, but only difference could be that the version string could be October instead of September, and the OS will have a different hash and consider the two different.
It's certainly not line in the good ol' days
---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------
You could blow up the modem images and compare the individual files to see what is different. You can certainly detect the differences at the file level, but you may not be able to know what the differences does.

Imei and baseband unknown

Hey, I am in trouble my imei and baseband is unknown after reverting back to stock rom from pixel experience.
Please help.
My phone dead from around 10 days.

R.Rishik said:
Hey, I am in trouble my imei and baseband is unknown after reverting back to stock rom from pixel experience.
Please help.
My phone dead from around 10 days.
Click to expand...
Click to collapse
Flash stock Oreo firmware and you will get your IMEI and baseband of you're device.

R.Rishik said:
Hey, I am in trouble my imei and baseband is unknown after reverting back to stock rom from pixel experience.
Please help.
My phone dead from around 10 days.
Click to expand...
Click to collapse
Flash Stock oreo (latest available for RETIN is april), if you previously updated your stock to June security patch and now flashed April Full stock you loose your IMEI,
To get IMEI back you need to update to latest JUNE through OTA using WIFI.

pradeeppk said:
Flash Stock oreo (latest available for RETIN is april), if you previously updated your stock to June security patch and now flashed April Full stock you loose your IMEI,
To get IMEI back you need to update to latest JUNE through OTA using WIFI.
Click to expand...
Click to collapse
What to do if my moto on Android 7.1.1 installed with fastboot images from here doesn't see updates?

br3w0r said:
What to do if my moto on Android 7.1.1 installed with fastboot images from here doesn't see updates?
Click to expand...
Click to collapse
Flash this (for Indian Varrient)
https://mirrors.lolinet.com/firmware/moto/sanders/official/RETIN/
It is April 2019 patch for india, and after that you need to update to latest june patch through wifi (if your imei is zero you cant use mobile network)

pradeeppk said:
Flash this (for Indian Varrient)
https://mirrors.lolinet.com/firmware/moto/sanders/official/RETIN/
It is April 2019 patch for india, and after that you need to update to latest june patch through wifi (if your imei is zero you cant use mobile network)
Click to expand...
Click to collapse
Yeah, I already used a 8.1 fastboot rom, updated it to june patch and got my cellular back.