Hey Strongst! Thanks for replying.
One more doubt....when i open the main file of blank-flash that is known as singleimage.bin it's contains mainly 5-6 ( most of the single-image.bin) like
1. aboot.img
2. DDR.bin
3. rpm.img
4. sbl1.img
5. tz.img
(I attached a pics for support)
and above files we have managed from dump rom of working device.
Could you please explain it for us?
Your reply will be really appreciating to us
Thanks!!
Those files are bootloader images if I recall, packaged into a singleimage.bin along with other files such as the programmer.mbn. As I understand it, the programmer.mbn is what gets sent to a device after the blankflash communicates with your device, to check whether the blankflash meets or exceeds the bootloader version.
If so, then the programmer begins flashing the bootloader files to repair your bootloader. If your bootloader is too new (and corrupted from a OTA update after downgrading), then the programmer would likely block the flash for security reasons. Thus, it seems it's not just having the up to date files, you also would need a newer programmer file for access and verification.
As strongst has already mentioned, we only get these leaked, as they have to be signed by Motorola for the bootloader to accept them. Unless you can find a Motorola engineer (or a member with such a contact) willing to let you have Moto X force blankflashes, or up to date factory firmware is available/leaked, I'm afraid the only resolution is a motherboard replacement. There's been limited success with using blankflashes from other Motorola devices, but typically those devices have very similar/same CPUs (e.g g5 plus, z play etc), and I don't know of other Motorola devices with the SD810 chip inside.