Database Users

Downgrade from 6.0 Indian Firmware to 5.1 EU Firmware. Is it possible?

Hi everyone,
I would like to know if is possible to dowgrande to a different country firmware (I'm not interested in the dual sim option). Anyone know if this is possible? I have a locked and non rooted moto x play. I've tried to follow this thread REMINDER HOW TO DOWNGRADE from 6.0 to 5.1.1, but the installation fail with this error:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse

lollo64 said:
Hi everyone,
I would like to know if is possible to dowgrande to a different country firmware (I'm not interested in the dual sim option). Anyone know if this is possible? I have an unlocked and non rooted moto x play. I've tried to follow this thread REMINDER HOW TO DOWNGRADE from 6.0 to 5.1.1, but the installation fail with this error:
Click to expand...
Click to collapse
Yes, downgrading is possible with unlocked bootloader (locked bootloader doesn't allow downgrading). The first 2 commands ("fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img") always fail when downgrading, and can be skipped without any issues, so if the error you got was for one of the first 2 commands just continue with the rest of the commands.

panart said:
Yes, downgrading is possible with unlocked bootloader (locked bootloader doesn't allow downgrading). The first 2 commands ("fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img") always fail when downgrading, and can be skipped without any issues, so if the error you got was for one of the first 2 commands just continue with the rest of the commands.
Click to expand...
Click to collapse
Thanks, I was start to supposing that the locked bootloader was the problem and you just confirmed. Unluckily right now I can't unlock the bootloader so I think I must wait for the release of the complete EU 6.0 Firmware.

lollo64 said:
Thanks, I was start to supposing that the locked bootloader was the problem and you just confirmed. Unluckily right now I can't unlock the bootloader so I think I must wait for the release of the complete EU 6.0 Firmware.
Click to expand...
Click to collapse
In your post you mentioned "unlocked" so i assumed you had unlocked the bootloader already. I'm afraid that downgrading is only possible if you unlock the bootloader, or you can wait for EU 6.0 full stock ROM to become available and try installing that (it might work as you'll be going from 6.0 ROM to 6.0 ROM).

panart said:
In your post you mentioned "unlocked" so i assumed you had unlocked the bootloader already. I'm afraid that downgrading is only possible if you unlock the bootloader, or you can wait for EU 6.0 full stock ROM to become available and try installing that (it might work as you'll be going from 6.0 ROM to 6.0 ROM).
Click to expand...
Click to collapse
Ooops, sorry. It was a typo, I've just fixed it. Yes, right now I'm waiting for the release of EU 6.0 full stock rom and then I'm going to retry to flash it!

lollo64 said:
Ooops, sorry. It was a typo, I've just fixed it. Yes, right now I'm waiting for the release of EU 6.0 full stock rom and then I'm going to retry to flash it!
Click to expand...
Click to collapse
Have you tried what panart said, about skipping the first 2 fastboot commands ?
I also downgraded to 5.1 skipping the first 2 lines and it was working fine.Only I had an unlocked bootloader at that moment ,but maybe it wil also works with a locked bootloader, not sure.

Sickaxis79 said:
Have you tried what panart said, about skipping the first 2 fastboot commands ?
I also downgraded to 5.1 skipping the first 2 lines and it was working fine.Only I had an unlocked bootloader at that moment ,but maybe it wil also works with a locked bootloader, not sure.
Click to expand...
Click to collapse
Yes, I've tried both. With and without the first two commands (fastboot flash partition gpt.bin / fastboot flash bootloader bootloader.img), but it fails in every case. Purposely I get the errors when I launch this commands:
Code:
- fastboot flash boot boot.img
- fastboot flash system system.img_sparsechunk.*
All the other instructions work fine.

http://forum.xda-developers.com/showpost.php?p=65423306&postcount=475
24.65-33 Full EU
You can flash it directly On any XT1562

Downgrade From 6.0.1 to 6.0 or 5.1.1

I accidentally flashed wrong firmware on indian moto x style which is 6.0.1 (24.221.1 clark_reteu), i was on 6.0 asia dual sim rom.
and now i am unable to flash my asia rom, only 6.0.1 rom is flashing and i am not getting any network on both of my sim cards.
Please HELP.

What do you mean by unable to flash?
Why not try retasia version of 6.0.1?

teji007 said:
I accidentally flashed wrong firmware on indian moto x style which is 6.0.1 (24.221.1 clark_reteu), i was on 6.0 asia dual sim rom.
and now i am unable to flash my asia rom, only 6.0.1 rom is flashing and i am not getting any network on both of my sim cards.
Please HELP.
Click to expand...
Click to collapse
( No service/ no sim card fix)
Once you have flashed your phone with 6.0.1, let it boot..
You will not get signals till now...
Open command window in the folder where u extracted ur software 6.0.1 and follow the steps below.
1- fastboot flash modem NON-HLOS.bin
2- fastboot erase modemst1
3- fastboot erase modemst2
4- fastboot erase cache
5- fastboot reboot
And u r done wait for 2-3 minutes once your phone turns on.. you will see your signal bars....

M.Nabeel said:
( No service/ no sim card fix)
Once you have flashed your phone with 6.0.1, let it boot..
You will not get signals till now...
Open command window in the folder where u extracted ur software 6.0.1 and follow the steps below.
1- fastboot flash modem NON-HLOS.bin
2- fastboot erase modemst1
3- fastboot erase modemst2
4- fastboot erase cache
5- fastboot reboot
And u r done wait for 2-3 minutes once your phone turns on.. you will see your signal bars....
Click to expand...
Click to collapse
I tried every thing..
retasia rom 6.0.1 is not avaliable only 6.0 is avaliable.
Even after flashing HLOS its not working.

lafester said:
What do you mean by unable to flash?
Why not try retasia version of 6.0.1?
Click to expand...
Click to collapse
Retasia 6.0.1 version is not avaliable.
(Bootloader) Preflash verification failed.....This error shows when i try to flash 6.0 rom.

teji007 said:
Retasia 6.0.1 version is not avaliable.
(Bootloader) Preflash verification failed.....This error shows when i try to flash 6.0 rom.
Click to expand...
Click to collapse
Yes this tends to happen, but in my case rom just install fine

M.Nabeel said:
Yes this tends to happen, but in my case rom just install fine
Click to expand...
Click to collapse
Can you please send me the link from where you downloaded you rom.
I have XT1572 indian dual sim

teji007 said:
Retasia 6.0.1 version is not avaliable.
(Bootloader) Preflash verification failed.....This error shows when i try to flash 6.0 rom.
Click to expand...
Click to collapse
Sure it is I flashed it weeks ago. Check general forum.

Droid Turbo XT1254 Marshmallow->Lollipop downgrade (unlocking bootloader)COMING SOON?

Droid Turbo XT1254 Marshmallow->Lollipop downgrade (unlocking bootloader)COMING SOON?
*this is new thread because I started last as Q&A by mistake so first 2 pages may look off with posts and answers.
DOWNGRADING EXPERIMENT TOPIC
So as you may know , after upgrading to Marshmallow OTA, on locked bootloader there won't be any option to unlock bootloader (ever as some people say) , sunshine officially doens't support Marshmallow. The only option is to downgrade which again isn't possible on locked BL..
Or is it ?
Introduction - skip to DOWNGRADE
First of all I'm not an programmer , but have some experience with locked down motorola's bl's , firmware's ,downgrades and so on..
I'm sure when somebody says impossible, it doesn't really mean impossible, but rather not worthy to some. So in my case I bought the phone few days ago, wasn't fully up to date with infos on unlocking BL so didn't check FW version when buying , just after I checked and phone was updated on MM 1-2 days before buying it. On not unlockable BL phone will become useless to me very soon, while unlocked I would plan to have it for long period of time. It goes in Verzion's favour for me to ditch the phone and buy a new one except I'm not in USA , there are no Verzion services in my country and if there were I would never ever buy (again) anything from Verzion. Well I lived in Japan , and there is network Softbank which is well.. Imagine Verizon but on steroids when it comes to tying people down, locked bootloaders and software, insane fee's and so on.. Well that Softbank bough Verizon some time ago .. I was avoiding them at all cost, but on to the topic now.
DOWNGRADE - fastboot
I would like to invite everybody who is interested in this and who can help to participate in this. Every programmer that has time and can contribute would be greatly appreciated! In return I'm willing to sacrifice my phone and my time , even paying some reasonable donations.
While experimenting in the end I was able to flash all bootloader files from various different versions including all partitions related to it which gets upgraded. Even managed to flash XT1250 MM bootloader. Bootloader version DOES change in bootloader / fastboot ,But it doesn't mean ANYTHING. While downgrading , something else, possibly other parts of bootloader obviously search for match and there is more to it than simple bootloader , more experienced , chime on in here! SElinux enforcing? Verity?
(see attachments)
SU4TL-49 bootloader.img to motoboot flash - Successfully
SU4TL-49 manually flashing 1 by 1:
tz.mbn -[/B] Successfully
SBL1.mbn (bootloader) - [/B] Successfully
sdi.mbn - [/B] Successfully
fsg.mbn to mdm1m9kefs3 - [/B] Successfully
rpm.mbn - [/B] Successfully
emmc_appsboot.mbn to aboot - [/B] Successfully
gpt.bin to "partition" , it's the partitions info partition, people say it can't be downgraded or flashed cross versions. After some experimenting mfastboot failed but fastboot succeded, on some versions mfastboot worked - [/B] Successfully
What I can't get to downgrade / cross flash no mather which bootloader and combinations of firmware im on :
boot.img
recovery.img
system,img (sparse_chunk files)
I will go deeper, but hope that new full firmware SBF will be released soon in case of brick. Verzion is slow. I'm making my own full 6.0.1 xml.zip based on full flashable zip's , repacked system.img sparsechunks, rewrited the script but can't get to flash system files due to invalid signed image. Any help with that? It would also help already bricked guys because who knows when'll Verzion release it..
Downgrade OTA way , stock Android Recovery
While stock android recovery is pretty much useless, it can do software upgrades OTA on a fully stock system , which we on locked bootloaders and MM have.
In my opinion , the way is to trick stock recovery into thinking it's flashing ota, and that whole envieroment is like recovery is expecting it while it's actually flashing downgraded version full / close to full firmware in combination with you flashing some partitions manually through fastboot. OTA's contain only "patch" and just replaces files which get changed on new SW. Or even maybe reverse OTA downgrade?
I've made my own update.zip and signed it , but so far get footer size is wrong error so can't flash it .. Need more help here too..

That looks promising!
Marshmallow feels slower than lollipop for me and I wish I could downgrade but I just can't!
I am looking forward to see what you can do about this issue
Good luck bro!

sorry for my mistake, I do not intend to comment here
@EjđiSixo
How to remove the "signed" of system image or bypass it? Fastboot or RSD are stuck at flashing system image. Does this "sign" relate to boot, recovery, partition? Or it's simply the "sign" to prevent downgrade???
I've never succeeded with partition downgrade...
---------- Post added at 10:29 PM ---------- Previous post was at 10:19 PM ----------
when I was flashing the only system.img (3GB), it said that "wrong at header magi". But after a bit time, fastboot separated the file and began to flash. But still failed because of signed image.
I've tried to remove the code from updater-script but it could not write files to system

Not out yet!

Thanks! I think if we all try , we can do it ! For now main focus is downgrading anyhow, even to half working Lollipop just in the purpose of unlocking bootloader with sunshine.
@mr_5kool
Feel free to comment and ask / suggest, thats what this topic is for!
Unforutenately thats the part I haven't yet figured out myself. It is a " permissions" to prevent the downgrade , bootloader and possibly something else checks current version / keys / properly signed image and then flashes. With other bootloader I'm still not able to flash it because it's obviously locked. Motorola probably signs their images differently.
You can't flash 3GB image because when flashing, phone recieve's partition first to ram so max download size is set to 255mb per file. You have to repack system.img to sparse chunks. But you don't have to bother with it , I already repacked system.img which I found at fully stock flashable MCG24.251-5 . It again failed due to invalid signed image . If we could figure out what is exactly signed and how , that would open a lot more possibilities. Possibly even flashing prerooted roms on locked bootloader. There are more possibilities , who knows..
Currently the only thing notices downgrade when flashing is recovery. In bootloader log says I tried to downgrade. Even with downgraded bootloader (kind of, there is sbl2 and sbl3 but they don't get upgraded )

Anyway, I tried something just for the "gags" . Flashed all partitions of XT1250 bootloader. Got to Motorola's site, posted "unlock bootloader data". It returned it's not unlockable of course.. The first sequence of numbers in data is your imei , it starts with 99 and it's verzion's specific imei.
My theory is that motorola ties unlock bootloader data to every phone and imei and stores it in database ( please confirm) . So even with moto maxx bootloader I can't unlock because :
1 it reads my verzion imei
2 it doesn't find alltogether data in the database..
I don't know what are other numbers in the data you get from fastboot, possibly some serial numbers and so on, haven't really checked it .. That's why i think this method is not possible at all for now. Manipulating that data in your phone and running it through motorola's site knowing that exact same code works for some device might be possible, but I think there is really way too much impossible messing involved. If somebody can share more about this?

lol
http://forum.xda-developers.com/dro...ficial-marshmallow-build-mcg24-t3512813/page2
I've renamed it like suggested in the post #11
Download link is at 1st page. It's just a OTA.

Yes I just renamed it.
IT DOESN'T WORK WITH ADB AND YOU CAN'T FLASH IT AGAIN THROUGH RECOVERY. ITS OTA.

EDIT: The post that I was responding to has been removed.

The method to downgrade from Lollipop to Kitkat is the same with what I've done. It may be possible. Some said that "impossible to downgrade with locked bootloader on vrz". So the system image may be signed with bootloader (or imei, serial or something else, god know).
The unlock method of Sunshine takes place in Trustzone (sbl2). They cannot get unlock code.

You succesfully downgraded LL to KK on droid? There is partition for trust zone alone "tz.mbn" , downgradable without any problem. I only see sbl1 get's upgraded on droid turbo , never saw in any firmware sbl2 or 3 yet.. So I'm little confused.. I remember I saw some PDF regarding that..

Yes, successfully downgraded 5.1 to 4.4.4 on Droid Turbo but with unlocked bootloader. I helped this guy.
http://forum.xda-developers.com/droid-turbo/help/solved-problem-downgrade-install-ota-t3497791
http://forum.xda-developers.com/droid-turbo/help/how-to-downgrade-lollipop-5-1-to-kitkat-t3494459

Finally managed to *Brick my devices while trying to make latest sbf firmware (what an irony ) because used some of files from that stupid OTA . Tried flashing all possible firmware I have but it doesn't fix it so system got corrupted probably and for now didn't succed flashing any of the available systems. Flashing MM recovery doesn't help. It's a " recovery loop".
Basically phone starts , vibrates , goes into recovery, it says "erasing" , it does the factory reset then restarts and over and over again erasing restarting loop.
I'll continue exploring downgrade options but top priority now is making working marshmallow sbf or waiting for stupid Verzion to release it already. Just checked with SUA and it still doesn't show repair so firmware isn't available still.
Biggest problem is signed system images which are probably signed by RSA and I need help with that..

I have same problem erasing

Can't flash SU4TL gpt.bin anymore , so success was definitely connected to experiment and steps I did so I'll investigate more.

@EjđiSixo
I have never tried before. My Moto X2013 failed to downgrade from LL to KK, too. So, it's the common problem of Verizon Motorola Devices.
If you have problem with "erasing", just enter recovery by "hold power button for a while then fast press volume up button". Phone will enter recovery and do the factory reset. But when rebooting the system, "erasing" appear again.
If partition is dead, flash the higher version, commonly gpt and tz.
PS: still waiting for the official xml firmware

ChazzMatt said:
Yes, successfully downgraded 5.1 to 4.4.4 on Droid Turbo but with unlocked bootloader. I helped this guy.
http://forum.xda-developers.com/droid-turbo/help/solved-problem-downgrade-install-ota-t3497791
http://forum.xda-developers.com/droid-turbo/help/how-to-downgrade-lollipop-5-1-to-kitkat-t3494459
side note, I hate this Q&A format. Not sure why XDA even has it. You can't even format URL links correctly.
Click to expand...
Click to collapse
mr_5kool said:
@EjđiSixo
I have never tried before. My Moto X2013 failed to downgrade from LL to KK, too. So, it's the common problem of Verizon Motorola Devices.
If you have problem with "erasing", just enter recovery by "hold power button for a while then fast press volume up button". Phone will enter recovery and do the factory reset. But when rebooting the system, "erasing" appear again.
If partition is dead, flash the higher version, commonly gpt and tz.
PS: still waiting for the official xml firmware
Click to expand...
Click to collapse
I wonder if there is any way to force Verizon to release firmware. This is really low of the lowest, it says 1 week after OTA , now it's almost 1 month. Until somebody forces them , it can be months as far as they are considered. No help from developers / programmers either on any of 2 subjects so don't see my method of full MM SBF working.

god know
:v

ChazzMatt said:
Yes, successfully downgraded 5.1 to 4.4.4 on Droid Turbo but with unlocked bootloader. I helped this guy.
http://forum.xda-developers.com/droid-turbo/help/solved-problem-downgrade-install-ota-t3497791
http://forum.xda-developers.com/droid-turbo/help/how-to-downgrade-lollipop-5-1-to-kitkat-t3494459
Click to expand...
Click to collapse
Exactly brother .
I solved my problem .
I can downgrade from Marshmallow to lollipop is very easy for my ..
But first step is unlocked bootloader from lollipop..
Sent from my XT1254 using XDA Free mobile app

Yeah people , we all know everything can be done with unlocked bootloader. It's a GOD mode. Nothing strange about downgrading with unlocked BL. This topic is for people stuck on locked BL like myself to try to odowngrade on lollipop only in purpose of UNLOCKING BL. So let's for now focus on locked BL's.

Seeking G4 Plus (XT1642) Marshmallow stock ROM for the UK

I have a G4 Plus which i've flashed with a stock ROM. The phone is running Marshmallow 6.0.1 and the build number is: MPJ24.139-48 - the patch level is 1 May 2016. When I hit 'update' it doesn't update to July 2016 which is the latest available patch in the UK.
Does anyone have a UK marshmallow rom for the G4 Plus which I can load onto the phone and then update to the July 2016 patch??
Any help would be fantastic. Thanks in advance.

https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Select I agree and then moto g from the dropdown menu. The instructions are fairly straightforward. XT1625 works for your device. Bootloader probably does not need to be unlocked if not downgrading**
Then execute the following
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
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 reboot
Edit: Use 7-Zip to extract the tarball from tgz file, and then again extract the files from the tarball.
**I'm not sure though, select allow oem unlocking in developer options just in case

mrinmaydhar - thank you very much. I will try that out now.

Which stock ROM did you flash, btw?
You may like to look at this stock ROM here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Though it's for XT1643, I've previously successfully flashed it onto a UK XT1642, dual SIM G4 Plus and had no issues. It also brings the July security patch and build 139-63/64, and from what I remember, kept the EMEA baseband and IMEI numbers for both SIM ports.

echo92 said:
Which stock ROM did you flash, btw?
You may like to look at this stock ROM here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Though it's for XT1643, I've previously successfully flashed it onto a UK XT1642, dual SIM G4 Plus and had no issues. It also brings the July security patch and build 139-63/64, and from what I remember, kept the EMEA baseband and IMEI numbers for both SIM ports.
Click to expand...
Click to collapse
Thanks i'll try that because it sounds like you've had a good success with it!
I flashed this one: ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
It worked but it was stuck on the 1st May 2016 security patch and kept saying it was up to date and wouldn't upgrade further.

Quick update: I tried echo's rom link because the other one had issues - WiFi wouldn't work.
Echo's xt1643 rom works well. It also includes the July 2016 patch level as mentioned in the posts above.
My next question is: when Nougat arrives, I assume we'll be able to upgrade to it. Will the nougat upgrade install the recovery file? For whatever reason, I don't think my recovery file installed properly when I flashed the rom. Just wondering ifnNougat will overwrite it when it is released?

motogfalcon said:
Quick update: I tried echo's rom link because the other one had issues - WiFi wouldn't work.
Echo's xt1643 rom works well. It also includes the July 2016 patch level as mentioned in the posts above.
My next question is: when Nougat arrives, I assume we'll be able to upgrade to it. Will the nougat upgrade install the recovery file? For whatever reason, I don't think my recovery file installed properly when I flashed the rom. Just wondering ifnNougat will overwrite it when it is released?
Click to expand...
Click to collapse
Nice one, from the sounds of it, everything's working
As for Nougat (whenever it arrives in the UK and Europe!), you should be receiving an OTA update, since you're up to the latest MM 139-63/64 build for our region. It also should flash onto your device provided no modifications have been made to the recovery/system (bootloader lock/unlock doesn't appear to matter).
What did you see that suggested your recovery wasn't properly installed? If it was an error such as 'not signed' or 'bad key', but reported OK after flashing, don't worry about it.

I got the 'not signed' message. Excellent! All seems to be working well. Looking forward to when Motorola release Nougat. It's a shame they haven't kept on top of the security patches because its a great device I think! Thanks again!

motogfalcon said:
Excellent! All seems to be working well.
Click to expand...
Click to collapse
What is your software channel now? Still retgb ?

Yes retgb. Apparently Lenovo are releasing Nougat soon in the UK so hopefully I'll get it on the retgb channel

Need to Re-Lock Bootloader on my friends XT1572

So the only thing that has been done with this phone, is that the bootloader has been unlocked, officially with a code from Motorola. No custom recovery, ROM, or anything were installed on it.
I need to re-lock the bootloader so he can return it to warranty as his screen sometimes goes crazy and starts clicking everywhere. So I just download the latest firmware for Vodafone Australia, which I believe is:
XT1572_CLARK_RETASIA_6.0_MPHS24.49-20-8_cid7_subsidy-DEFAULT_CFC.xml
from:
https://firmware.center/firmware/Motorola/Moto%20X%20Style/Stock/XT1572/
And then follow the commands from this thread in the OP for the XT1575 (*should be the same codes, right?*).
https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110
Also one final note, is the firmware I posted above the latest one for vodafone Australia? Just for confirmation, I am not sure, but according to this guide, it belongs to vodafone Australia:
https://forum.xda-developers.com/moto-x-style/general/australian-xt1572-guide-to-restore-t3292794

Qustion is what firmware on phone do you have?
Relock is possible by flashing the same or upper version only. @Blackfyre

dzidexx said:
Qustion is what firmware on phone do you have?
Relock is possible by flashing the same or upper version only. @Blackfyre
Click to expand...
Click to collapse
In the Bootloader it says:
Baseband: M8992_1255331.29.01.88.07R CLARK_APAC_CUST
Product/Variant: clark XT1572 32GB PC3
In the Phone Settings:
Build Number: NPH25.200-15
Any way to find out exactly if that's the same firmware as in the OP?
EDIT: His phone is running Nougat, I can't find a Nougat ROM for Clark ASIA or APAC (at all) from the link of firmwares above.

Blackfyre said:
In the Bootloader it says:
Baseband: M8992_1255331.29.01.88.07R CLARK_APAC_CUST
Product/Variant: clark XT1572 32GB PC3
In the Phone Settings:
Build Number: NPH25.200-15
Any way to find out exactly if that's the same firmware as in the OP?
EDIT: His phone is running Nougat, I can't find a Nougat ROM for Clark ASIA or APAC (at all) from the link of firmwares above.
Click to expand...
Click to collapse
There is no Nougat factory firmware image available, or even the "latest" Marshmallow version. Sorry, but without those it is no possible to lock the booloader. In order to lock the bootloader, you must flash a complete, signed image that is the same or a newer version than what you have.
Remember that relocking the bootloader will NOT remove the Unlocked Bootloader boot splash screen, nor will it hide the device has ever been unlocked (it is still plainly visibile on the bootloader screen and in a getvar all).
TBH, I have doubts we will ever see more factory firmware images... relocking the bootloader will probably never be possible.

@Blackfyre
This is Nougat, no flashable firmware.
Flash modified logo.bin and try warranty repair.

@acejavelin and @dzidexx
Thank you for the replies. I have a few questions.
If I root the device, can I install an old ROM on it, then update to the latest firmware available that is above, then lock OEM?
Would doing that result in Software = Modified? Because currently it's still Unmodified.
Flashing the modified logo.bin you mentioned above I am guessing will remove that warning that shows up at boot stating that the bootloader has been unlocked. Would flashing this .bin file result in Software = Modified or not?
And if not, then where can I find this modified logo.bin?
Thank you guys again for your help and replies.

https://forum.xda-developers.com/mo...e-unlocked-bootloader-warning-t3201141/page22
fastboot flash logo NameOfFile.bin
If after flashing still will be unmodified you can try relock:
fastboot oem lock begin
fastboot erase userdata
fastboot erase cache
fastboot oem lock @Blackfyre

dzidexx said:
https://forum.xda-developers.com/mo...e-unlocked-bootloader-warning-t3201141/page22
fastboot flash logo NameOfFile.bin
If after flashing still will be unmodified you can try relock:
fastboot oem lock begin
fastboot erase userdata
fastboot erase cache
fastboot oem lock @Blackfyre
Click to expand...
Click to collapse
Does that work though without flashing full firmware images?

quakeaz said:
Does that work though without flashing full firmware images?
Click to expand...
Click to collapse
No, you must flash a full, signed image... In some newer Moto devices you can get by with flashing only the signed system sparce_chunks and wiping data, in 3rd gen and older devices flashing a full signed image, even if already stock, is required.

acejavelin said:
No, you must flash a full, signed image... In some newer Moto devices you can get by with flashing only the signed system sparce_chunks and wiping data, in 3rd gen and older devices flashing a full signed image, even if already stock, is required.
Click to expand...
Click to collapse
Previous post - It was only my hope.
In Europe, Moto/Lenovo can not refuse to repair the components for two years.

dzidexx said:
Previous post - It was only my hope.
In Europe, Moto/Lenovo can not refuse to repair the components for two years.
Click to expand...
Click to collapse
Eh... Yeah, they can and do, often saying that what was done while unlocked is the cause of the problem... And then you have to fight it, by the time it's all said and done many people just give up as the process can take many months.