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.
Related
Trying to fix my daughter's phone, that I had previously flashed before using the XT1049_GHOST_REPW_5.1_LPA23.12-39-R-15_cid6_CFC.xml.zip file. Unfortunately it is now bricked and sitting at LPA23.12-39-R-19, and it fails the flash with the "security version downgraded" and "preflash validation failed" messages.
Is there (A) any way to get the full file for the updated R-19, or (B) get the 35MB OTA update and splice it into the R-15 update to make it work?
AndrewNKeller said:
Trying to fix my daughter's phone, that I had previously flashed before using the XT1049_GHOST_REPW_5.1_LPA23.12-39-R-15_cid6_CFC.xml.zip file. Unfortunately it is now bricked and sitting at LPA23.12-39-R-19, and it fails the flash with the "security version downgraded" and "preflash validation failed" messages.
Is there (A) any way to get the full file for the updated R-19, or (B) get the 35MB OTA update and splice it into the R-15 update to make it work?
Click to expand...
Click to collapse
Not following you exactly... So. U flashed xt1049 ghost.... Then took an ota then bricked?
I have this exact problem. Basically we need the latest stock firmware from Republic Wireless which is from 2016, and has the build LPA23.12-39-R-19. Apparently once you upgrade, flashing doesn't work for older versions because the verification doesn't check out. If anyone could help out and post the SBF for this that would be greatly appreciated
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..
My phone was previously rooted with magisk. I did a complete uninstall of magisk and then fully wiped my phone and installed the stock image. I've tried this multiple times now. After my phone gets set up, I try to download the OTA updates, and it will just say the update failed. Is there something else I am missing here? What is causing me to be unable to update?
Back when the 8.1 update was offered OTA I had a similar problem. For whatever reason OPW28.1 (OPW28.46-13) failed every time. I had to wait for the flashable firmware to become available and then flash it. After that I took all OTAs just fine up to the current version (Jun 2018). If you are willing to wipe your phone you can try to flash the latest firmware instead of trying OTAs.
Latest one is OPW28.3 (OPW28.46-21) 8.1.0 w/ June 2018 security patch:
Moto X4 Retail https://androidfilehost.com/?fid=5862345805528054494
Moto X4 Amazon edition https://androidfilehost.com/?fid=5862345805528062525
Moto X4 Android One https://androidfilehost.com/?fid=5862345805528054493
Knowledge of ADB and fastboot is required.
xt1900-1 payton_fi retus
Thanks, I was actually trying something similar when you posted.
I had previously been flashing OPWS27.57-25-6-10 which is 8.0, and it would fail to update every time.
I decided to try a different stock image, and I found an 8.1 image linked from this thread.
I flashed it, and tried ota update again. I initially got an error that the update failed, but I tried again, and it actually worked! So I am up to date on the July patch now!
Could some one please point me to a full stock image for the with the Oreo rom for the reteu release channel?
I have a moto 5gs plus here that does not want to do the OTA update to oreo 8.1 the phone has an unlocked bootloader but unmodifyed system/boot.
So I thought i just wil go with installing a full stock 8.1 image.
but the images i can fund does not say if they are for my release channel which is reteu,
does that even matter or can i just install the file from here: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
any advice would be greatly appreciated
You can use the one you mentioned. I did, on an XT1805. System info still shows reteu as software channel after flashing.
Did you run all the commands from the thread including erasing the data partition?
Or what was your update procedure?
I followed the commands, except erasing the data partition (the OTA for Oreo also didn't do that). I also skipped flashing logo and bootloader. I have the bootloader unlocked, and the logo was replaced to remove the unlocked bootloader warning.
(I flashed the ROM to see if that would solve an issue I had after the OTA upgrade to Oreo.)
I have the XT1900-1 android one version. Before unlocking my bootloader, I had the December 2018 security update. I unlocked my bootloader to get lineageOS, but decided to go back to stock using muchy_cool's guide. But now the security patches are going up to November 2018, and then it says its up to date.
Is there a difference between the stock firmware from the guide and the stock firmware upon buying the phone? I would assume so because if I relock the bootloader again, the warning message on boot changes to "device has loaded a different operating system". But then this is still stock firmware. Why don't the updates get detected?
Paximonium said:
I have the XT1900-1 android one version. Before unlocking my bootloader, I had the December 2018 security update. I unlocked my bootloader to get lineageOS, but decided to go back to stock using muchy_cool's guide. But now the security patches are going up to November 2018, and then it says its up to date.
Is there a difference between the stock firmware from the guide and the stock firmware upon buying the phone? I would assume so because if I relock the bootloader again, the warning message on boot changes to "device has loaded a different operating system". But then this is still stock firmware. Why don't the updates get detected?
Click to expand...
Click to collapse
Well it sounds like the OTAs ARE working if you're still on the November update. (My non-Pie phone is still on October update and Android 8.0)
It sounds like you just haven't gotten the December update yet. So did you first get September, October, and November?
As I am aware, even if you got the update it will fail at the moment of installation. There is no official stock recovery available so far that's why even if you lock the bootloader you are using the modified system warning shows at the time of booting.