[GUIDE] [XT1575] Return to stock and relock bootloader

[acejavelin]

I corrupted the eMMC on my MOTO E4 Plus (X1775) last year, but I managed to restore the bootloader by booting off the SD card. Unfortunately, the bootloader is now locked and I can't successfully boot it into the system partition so that I can flip the OEM Unlocking setting to unlock it again.

In theory, I should be able to flash the latest stock ROM though, right? However, I was getting "Preflash validation failed" on the boot, recovery and system partitions. Knowing what I read in the OP, I figured this was a rollback "feature" and have been waiting over a year to get a newer stock ROM release.

Well, I've definitely found at least two newer OEM ROM releases on mirrors.lolinet.com since then, and I'm still receiving the "Preflash validation failed" when flashing those three partitions. In fact, I know that this OEM firmware has a newer bootloader, since the "version-bootloader" definitely increased.

Are there other workarounds for this "Preflash validation failed" error? Perhaps there are flashing modes in RSD Lite that I can use? Should I be using blankflash?

You can't flash without the bootloader unlocked generally. Some people have had luck if it is the exact same version, but my experience was always it didn't work at all. In theory, it should work if it's the exact same or newer version, but it must also be the same variant and region.

Did you try doing a factory reset in recovery first?

You cant use blankflash unless it's hard-bricked and in Qloader mode.

 

[Magendanz]

Did you try doing a factory reset in recovery first?

Unfortunately, the recovery partition is also corrupted. It's frustrating that the Motorola bootloader isn't allowing us to flash a known-good OEM stock firmware release. Other brands like Huawei and Xiaomi allow you to do that when the bootloader is locked as long as it's properly signed.

 

[acejavelin]

Unfortunately, the recovery partition is also corrupted. It's frustrating that the Motorola bootloader isn't allowing us to flash a known-good OEM stock firmware release. Other brands like Huawei and Xiaomi allow you to do that when the bootloader is locked as long as it's properly signed.

Since Google sold Motorola to Lenovo, the brand has been going downhill... Lenovo doesn't want to support device more than a year old, they want you to buy a new one. In my opinion, this is just more of their planned obsolescence. In fact, they don't release any firmware images at all anymore, and all the firmware we have gotten since about 2015 for Moto devices has been leaked by employees or service houses, and that has dwindled as well. I have lost all faith in Moto, and I was a HUGE fan and advocate of their products, even into the middle of last year. Now we are a mostly a Pixel and Nokia home, with an HTC and a Samsung straggler (that will likely get Pixel 3a's in the next few months), and I doubt that will change, at least for the next few years.

And I know nothing about Xiaomi, other than they really don't work well in the US due to LTE band support, but Huawei has changed there tune a LOT in the last year or two... There is no more bootloader unlocking at all, no kernel source releases, and support for the custom ROM/mod community went from pretty decent to nothing.

 

[Magendanz]

In my opinion, this is just more of their planned obsolescence. In fact, they don't release any firmware images at all anymore, and all the firmware we have gotten since about 2015 for Moto devices has been leaked by employees or service houses, and that has dwindled as well.

It's a disturbing industry-wide trend, representing a massive shift of power away from consumers and denying us any right to modify or repair the products we purchase. Can you imagine if the auto industry worked that way? Would we tolerate having the engine compartments of our cars and trucks locked up tight so that only the dealers could maintain, repair or make modifications?

 

[acejavelin]

It's a disturbing industry-wide trend, representing a massive shift of power away from consumers and denying us any right to modify or repair the products we purchase. Can you imagine if the auto industry worked that way? Would we tolerate having the engine compartments of our cars and trucks locked up tight so that only the dealers could maintain, repair or make modifications?

Actually, your correlation here isn't that different... Yes, hoods are not locked up tights, but what can most people really do? Normal maintenance, maybe replace a few things here and there. Auto makers are locking down many of the things in vehicles. Can you upgrade the indash entertainment system yourself? Can you change the setup of the ECM on most cars? Heck, in some cars it is even impossible to replace the indash radio system at all. You laugh, but it is headed that way... Compare this to a 60's or 70's vehicle, you could literally change or do anything to that, a new 2019 vehicle not so much, except for an elite few people and vehicles.

 

[Magendanz]

Just to really emphasize how broken Motorola's firmware upgrade system is, today I went to upgrade a Cricket Moto G6 Play (XT1922-9) to Android Pie, which is available for the XT1922-9 but only for the RETUS channel. I ran the batch file in fastboot and received the same "Preflash validation failed" on the boot, recovery and system partitions. Now the device only boots to the bootloader because it fails to validate the boot image. Likewise, recovery mode is inaccessible because it can't validate the recovery image. (Interestingly enough, neither of these images were actually flashed.)

Now, the locked device is completely bricked. Motorola wouldn't allow me to unlock the bootloader, and trying to flash the original Oreo ROM for the Cricket channel also fails validation. I'm stuck again on the bootloader with the inability to flash known-good (and properly signed) OEM firmware. How could they not leave a way to flash their own ROMs on unlocked devices?

 

[pt917]

Dear Teacher you are Great

 

[Jman47]

This 7.0 NPHS25.200-23 file fixed it

https://xdaforums.com/moto-x-style/...on-factory-t3704142/post77054647#post77054647

I was able to locate both stock ROMs and didn't see them posted here at all in any thread anywhere so, I tossed them both up on Mega if anyone finds themselves in a situation where they could prove useful. As I understand it, NPHS25.200-22-1 was the minimum build for any carrier usage either CDMA or GSM, but NPHS25.200-23-1 was more for GSM use. I cannot verify that, it's just something I saw mentioned on another forum that one user pointed out. What I can say for sure is that there are differences in the checksums of the system.img_sparsechunk files and some others as well included in these ROMs so there are differences in there somewhere.

Regardless, here are NPHS25.200-22-1 and NPHS25.200-23-1 stock ROMs if anyone happens to need them so you won't have to deal with or wait for any OTA updates to patch things along the way - considering they still leave the MXPE with the October 1 2017 security patch, I think it's fairly safe to say Lenovo will never release another update for this device and if they do it'll be a small miracle at this point.

NOTE: THESE ARE FOR THE XT1575 ONLY AS I UNDERSTAND IT, I have no way of verifying if they'd be functional on the XT1572 model (Style), so be aware of this fact. I own an XT1575 and I cannot say if these will work on the XT1572 - it's sufficiently say to say "Nope, they are for the XT1575 only..." and be done with it

CLARK_RETUS_7.0_NPHS25.200-23-1_cid9_subsidy-DEFAULT_CFC.xml.zip
1.39 GB (1,498,747,731 bytes)
SHA1: feccf2c71bb5d55cb5405e5698053f6c7332eb13
flashfile.xml = <software_version version="clark_retus-user 7.0 NPHS25.200-23-1 1 release-keysM8992_1255331.29.01.88.09R"/>

https://mega.nz/#!xUsiXI6C!cAyj2HZgoyxUIcnhNtso7nw6lo-0qKeJnmGoNaHQrec

THIS SAVED ME.
Locked Bootloader (had 'Allow OEM Unlock' in Developer Options. error)
firmware on 200-23. was bootlooping without an OS.

was able to fastboot and ADB soI tried everything on the forums but everyone only had 200-22 available.
i downloaded this file and everything flashed perfectly. was able to boot and "allow oem unlocking " used my code and unlocked the bootloader

mirror for download: https://drive.google.com/open?id=16LD16SS9hNqIAD6DHTgi8PVsghe-s_bd

 

[tswrench]

Halp!

Got a NOS Moto X Pure Edition xt1575 and experienced some kind of rooting glitch after having unlocked the bootloader and installing TWRP. Long story short, after a frantic bout of wiping and swiping, the OS is gone, I can't select the micro SD in TWRP, and fastboot only sees the phone in recovery. I found this thread, which seemed promising, but it appears to be a no-go without access to the bootloader. I've flashed so many custom ROMS to a tablet I have, that I thought this phone would be a cakewalk, but it seems to have rolled right over me. So, is it time to slather some mortar on this thing and add it to the wall (bricked), or is there a Hail Mary play, or Jiu Jitsu move out there somewhere? Anything...ANY-THING would be welcome and much appreciated. Thank you.

 

[bhati2710]

Help XT1925 Motorola G6

Hi @acejavelin ,
I know this is not the correct thread to discuss it but I have found that you know well about the fasboot and flashing moto devices. Therefore, I couldn't stop myself to put a question here. I am using XT1925-2 device which shows CID: 0xdead at this moment due to which I couldn't flash firmware and phone was stuck into boot loops. Whenever I run command bootloader.img and GPT.bin, they are successfully but boot.img, recovery.img, system, vendor doesn't flash at this moment and gives an error "Preflash Validation failed". I thought, it could be happening due to locked bootloader so I get an unlock key from Motorola and when I try to unlock my XT1925-2 motorola G6, it gives an error "premission failed" as unable to unlock.

Also, I don't boot into TWRP using "fastboot boot twrp.img". Please help me if there is an option to restore my phone. Thanks in advance.

 

[pshadoww]

Thank you, this works!

• I tried to relock my phone, which is running version NPHS25.200-22-1
• I downloaded NPHS25.200-22-1 image
• I failed due to "Preflash Validation failed"
• I downloaded this 25.200-23-1 version
• relocked successfully!

https://xdaforums.com/moto-x-style/...on-factory-t3704142/post77054647#post77054647



THIS SAVED ME.
Locked Bootloader (had 'Allow OEM Unlock' in Developer Options. error)
firmware on 200-23. was bootlooping without an OS.

was able to fastboot and ADB soI tried everything on the forums but everyone only had 200-22 available.
i downloaded this file and everything flashed perfectly. was able to boot and "allow oem unlocking " used my code and unlocked the bootloader

mirror for download: https://drive.google.com/open?id=16LD16SS9hNqIAD6DHTgi8PVsghe-s_bd