MOTO E (1st GEN) FIRMWARES NEEDED INDIAN RETAIL (immediately) - Moto E Q&A, Help & Troubleshooting

Hi devs and helpers!!
this is only for indians but if you wish you can help
ok this is a long story let me explain
so first lollipop soak test released and i updated it via keeping the file in sd and phone memory and then i updated it till 22.27.1 then i found that i am stuck on that version i cant do anything so i flashed 5.1 firmware images and then on the bootloader says that hab check failed for system and failed to validate system image so i need the indian retail from flipkart stock 4.4.4 images only if they are 4.4.4 ! AND I CANT UNLOCK THE BOOTLOADER AS THAT IS ANOTHER LONG STORY SO NOW IF ANYONE HAS WHAT I WANT THEN PLZ GIVE AND DONT TELL TO UNLOCK THE BOOTLOADER AND I HAVE TRIED EVERY FIRMWARE EXCEPT (http://forum.xda-developers.com/showthread.php?t=2759495) , the link isnt working and i have also posted on that thread that the link isnt working , So can anyone help me plz???
THANKS!!

Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.

Droidriven said:
Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.
Click to expand...
Click to collapse
Thankyou very much for responding !! i will try it and tell u tommorow!!:laugh::good::good::good:

Droidriven said:
Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.
Click to expand...
Click to collapse
sorry doesnt work:crying:
i need Blur_Version.21.41.20.condor_retaildsds.retaildsdsall.en.03 something like that the xx.xx.xx is not correct:crying:

snehil_dps_6l said:
hi devs and helpers!!
This is only for indians but if you wish you can help
ok this is a long story let me explain
so first lollipop soak test released and i updated it via keeping the file in sd and phone memory and then i updated it till 22.27.1 then i found that i am stuck on that version i cant do anything so i flashed 5.1 firmware images and then on the bootloader says that hab check failed for system and failed to validate system image so i need the indian retail from flipkart stock 4.4.4 images only if they are 4.4.4 ! And i cant unlock the bootloader as that is another long story so now if anyone has what i want then plz give and dont tell to unlock the bootloader and i have tried every firmware except (http://forum.xda-developers.com/showthread.php?t=2759495) , the link isnt working and i have also posted on that thread that the link isnt working , so can anyone help me plz???
thanks!!
Click to expand...
Click to collapse
plzzz someone send firwares plzzzz

You cannot flash any 4.4.4 Firmware Image without Unlocking Bootloader. Follow Bootloader locking Tutorial: http://forum.xda-developers.com/showpost.php?p=52693419&postcount=2
Alternatively, forget about KitKat and flash latest XT1022 Lollipop 5.1 Firmware Image from here: http://forum.xda-developers.com/showthread.php?t=2755857
XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.

You have to unlock the bootloader

MaddySayaji said:
You have to unlock the bootloader
Click to expand...
Click to collapse
if there is a corrupt firmware how can i unlock the bootloader

lost101 said:
You cannot flash any 4.4.4 Firmware Image without Unlocking Bootloader. Follow Bootloader locking Tutorial: http://forum.xda-developers.com/showpost.php?p=52693419&postcount=2
Alternatively, forget about KitKat and flash latest XT1022 Lollipop 5.1 Firmware Image from here: http://forum.xda-developers.com/showthread.php?t=2755857
XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Hi sir,
im very happy that someone is trying to help me out
all the commands were successful but i have a error "failed to validate system image" in purple color and plus ur older version of 5.1 firmware isnt working its saying (preflash validation failed) (XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.2_cid7_CFC.xml)
here are all the commands as asked (output from command prompt):
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.024s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.712s]
finished. total time: 0.741s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.088s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 2.071s]
finished. total time: 2.170s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (527 KB)...
OKAY [ 0.067s]
writing 'logo'...
OKAY [ 0.132s]
finished. total time: 0.205s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.396s]
writing 'boot'...
OKAY [ 1.573s]
finished. total time: 1.976s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.409s]
writing 'recovery'...
OKAY [ 1.575s]
finished. total time: 1.998s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (242987 KB)...
OKAY [ 8.533s]
writing 'system'...
OKAY [ 27.242s]
finished. total time: 38.026s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256539 KB)...
OKAY [ 9.150s]
writing 'system'...
OKAY [ 25.751s]
finished. total time: 34.909s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257126 KB)...
OKAY [ 9.087s]
writing 'system'...
OKAY [ 25.306s]
finished. total time: 34.406s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46232 KB)...
OKAY [ 1.667s]
writing 'modem'...
OKAY [ 3.940s]
finished. total time: 5.614s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.016s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (648 KB)...
OKAY [ 0.066s]
writing 'fsg'...
OKAY [ 0.130s]
finished. total time: 0.201s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.079s]
finished. total time: 0.082s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.271s]
finished. total time: 0.274s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>

@Snehil_DPS_6l - The solution is to unlock your Bootloader and try fastboot flashing again.

Related

HELP.. Unable to Re-Lock bootloader..!

I have condor 4.4.2 stock firmware... I am able to flash firmware but while relocking bootlader I am getting some error...
<Bootlader> sst lock failure..!
I am using MOTO E with stock firmware but I want to relock my bootloader to claim warranty..! Please help me out.!
The whole Command and their replies:
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.068s]
finished. total time: 0.070s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.585s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.107s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.581s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.087s]
writing 'logo'...
OKAY [ 0.146s]
finished. total time: 0.237s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.413s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.129s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.418s]
writing 'recovery'...
OKAY [ 1.613s]
finished. total time: 2.035s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (243147 KB)...
OKAY [ 8.385s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.062s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257549 KB)...
OKAY [ 8.775s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.865s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (204273 KB)...
OKAY [ 6.958s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.019s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 1.582s]
writing 'modem'...
OKAY [ 3.953s]
finished. total time: 5.540s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.019s]
finished. total time: 0.021s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.018s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (648 KB)...
OKAY [ 0.104s]
writing 'fsg'...
OKAY [ 0.152s]
finished. total time: 0.261s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.109s]
finished. total time: 0.113s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.635s]
finished. total time: 0.637s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.041s]
finished. total time: 0.042s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe oem lock
...
(bootloader) sst lock failure!
Click to expand...
Click to collapse
OKAY [ 0.021s]
finished. total time: 0.022s
D:\MOTO E\RETAIL-DSDS_CONDOR_KXC20.82-14_cid7_CFC_1FF.xml\RETAIL-DSDS_CONDOR_KXC
20.82-14_cid7_CFC_1FF.xml>mfastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Same Problem with Moto G
Am also facing the same problem with moto G. No one has the solution for this.
Need it too
I,m too facing the same problem:crying:
Flash
Flash Updated 4.4.4 Original Stok Firmware....
not Zip file full Stok Firmware then try to RE lock Bootloder....
Thanks .......:good:
Do you have link to download 4.4.4 stock rom if so please provide us the link
thank you
I came to know that the bootloader has been updated in 4.4.4 update so it doesn't allow to downgrade your phone
heare u go
http://www.filefactory.com/file/260ktu25bxrv/RETUGLB_XT1021_4.4.4_KXC21.5-53_cid9_CFC.xml.zip
Thanks for the link. But it is XT1021 I need for XT1022 (Indian dual sim version).
Can you please provide that link
GO TO This Thread
Find Ur self
http://forum.xda-developers.com/showthread.php?t=2755857
shivakiran456 said:
Thanks for the link. But it is XT1021 I need for XT1022 (Indian dual sim version).
Can you please provide that link
Click to expand...
Click to collapse
Here you go : http://forum.xda-developers.com/showpost.php?p=54872420&postcount=73
First Link.
Abhishek_Rawal said:
Here you go : http://forum.xda-developers.com/showpost.php?p=54872420&postcount=73
First Link.
Click to expand...
Click to collapse
Thanks a lot
Relock bootloader
Even if you relock Bootloader you cannot claim warrenty ,coz u have officially unlocked bootloader and your device will be registered to motorola
dharsayantan said:
Flash Updated 4.4.4 Original Stok Firmware....
not Zip file full Stok Firmware then try to RE lock Bootloder....
Thanks .......:good:
Click to expand...
Click to collapse
Then how to flash stock firmware????
Its simple.I too faced the same issue.try stock firmwares from different website.it works!
Why do u need to claim warranty ?
guys , i am having moto e condor ,when relocking Moto e it says sst lock failure and i have original stock firmware file.

Moto e LTE 2015 XT1527 Brick Help

hi, I need help.
I have flashed a ROM 5.1.1 XT1527 XT1524 in but did not have the bootloader unlocked, and apparently pedia have now unlocked bootloader and flash a rom whenever I get this:
Flashing GPT and bootloaders ...
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.351s
error: cannot load 'motoboot.img'
Flashing Modem SW ...
sending 'modem' (54616 KB)...
OKAY [ 1.716s]
writing 'modem'...
OKAY [ 3.549s]
finished. total time: 5.265s
Flash AP images ...
sending 'logo' (679 KB)...
OKAY [ 0.020s]
writing 'logo'...
OKAY [ 0.100s]
finished. total time: 0.120s
sending 'boot' (32768 KB)...
OKAY [ 1.040s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.639s
sending 'recovery' (32752 KB)...
OKAY [ 1.031s]
writing 'recovery'...
OKAY [ 2.065s]
finished. total time: 3.096s
sending 'system' (262143 KB)...
OKAY [ 8.220s]
writing 'system'...
Invalid signed image
Preflash validation failed
FAILED (remote failure)
finished. total time: 8.620s
sending 'system' (262141 KB)...
OKAY [ 8.230s]
writing 'system'...
Invalid signed image
Preflash validation failed
FAILED (remote failure)
finished. total time: 8.255s
sending 'system' (262141 KB)...
OKAY [ 8.222s]
writing 'system'...
Invalid signed image
Preflash validation failed
FAILED (remote failure)
finished. total time: 8.271s
Wipe Cache and Data ...
erasing 'userdata'...
OKAY [ 0.521s]
finished. total time: 0.522s
erasing 'cache'...
OKAY [ 0.042s]
finished. total time: 0.042s
What I understand and what I am doing is going back to an earlier or better version Downgrade but I will not let that do not have the bootloader unlocked, and can not unlock it since it does not activate the option in developers "Allow OEM Unlock" that copion not active, and now I'm stuck in fastboot mode and I can not do anything .
This is what I get when trying to unlock the bootloader :
D:\moto e 5.1.1\FlashFirmware 5.0.2 AMXLA>mfastboot devices
TA0930ILHQ fastboot
D:\moto e 5.1.1\FlashFirmware 5.0.2 AMXLA>fastboot oem unlock EOW2SHFPQ5XESUDR5YNX
...
Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Now I 've read post on the internet and I have to flash a rom the same cid and this is my cid and so I understand the cid12 is for Latin America and yet does not leave me any flash rom I always generates the same problem
D:\moto e 5.1.1\FlashFirmware 5.0.2 AMXLA>fastboot getvar cid
cid: 0x000C
finished. total time: 0.008s
You can unlock the bootloader without marking the option "Allow OEM Unlock" ?
is that all you can flash rom stock without having the bootloader unlocked, but that leaves no flash ?
what am I doing wrong?
someone could help me revive my cell
hello, me exactly the same way someone could help me please, thank you very much

Moto E bricked...

Hi everyone! I have a problem with my Moto E XT1021. Some time ago I updated my device to Lollipop. Everything was ok but after a while it stopped working... Meantime I changed my device, so i put my Moto E in a drawer! Now I wanna use it again, but I have a lot of problem with fastboot (that's the only stage that works on my phone).
I tried to repeat the process for install the original firmware (http://forum.xda-developers.com/showthread.php?t=2755857) but i had always the same errors:
Code:
[email protected]:# fastboot flash partition gpt.bin
target reported max download size of 299892736 bytes
sending 'partition' (32 KB)...
OKAY [ 0.072s]
writing 'partition'...
(bootloader) Preflash validation failed
[COLOR="Red"]FAILED[/COLOR] (remote failure)
finished. total time: 0.650s
[email protected]:# fastboot flash motoboot motoboot.img
target reported max download size of 299892736 bytes
sending 'motoboot' (1669 KB)...
OKAY [ 0.149s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 3.263s]
finished. total time: 3.412s
[email protected]:# fastboot flash logo logo.bin
target reported max download size of 299892736 bytes
sending 'logo' (527 KB)...
OKAY [ 0.113s]
writing 'logo'...
OKAY [ 0.155s]
finished. total time: 0.268s
[email protected]:# fastboot flash boot boot.img
target reported max download size of 299892736 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.411s]
writing 'boot'...
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 1.121s
[email protected]:# fastboot flash recovery recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.412s]
writing 'recovery'...
OKAY [ 1.785s]
finished. total time: 2.197s
[email protected]:# fastboot flash system system.img_sparsechunk.0
target reported max download size of 299892736 bytes
sending 'system' (242987 KB)...
OKAY [ 7.674s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 8.332s
[email protected]:# fastboot flash system system.img_sparsechunk.1
target reported max download size of 299892736 bytes
sending 'system' (256535 KB)...
OKAY [ 8.104s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 8.188s
[email protected]:# fastboot flash system system.img_sparsechunk.2
target reported max download size of 299892736 bytes
sending 'system' (257126 KB)...
OKAY [ 8.121s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 8.183s
[email protected]:# fastboot flash system system.img_sparsechunk.3
target reported max download size of 299892736 bytes
sending 'system' (45848 KB)...
OKAY [ 1.515s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
[COLOR="red"]FAILED[/COLOR] (remote failure)
finished. total time: 1.570s
[email protected]:# fastboot flash modem NON-HLOS.bin
target reported max download size of 299892736 bytes
sending 'modem' (46232 KB)...
OKAY [ 1.531s]
writing 'modem'...
OKAY [ 4.763s]
finished. total time: 6.294s
[email protected]:# fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.055s]
finished. total time: 0.055s
[email protected]:# fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.054s]
finished. total time: 0.054s
[email protected]:# fastboot flash fsg fsg.mbn
target reported max download size of 299892736 bytes
sending 'fsg' (648 KB)...
OKAY [ 0.110s]
writing 'fsg'...
OKAY [ 0.165s]
finished. total time: 0.275s
[email protected]:# fastboot erase cache
erasing 'cache'...
OKAY [ 0.369s]
finished. total time: 0.369s
After few try i unlocked bootloader, and the process was done ok (also if i read "Device is locked. Status code:0" is it normal?).
I tried to flash CWM or TWRP but without success. Always the same error: failed to validate system image.
Someone can help me?
Sorry for my english...
superazo said:
Hi everyone! I have a problem with my Moto E XT1021. Some time ago I updated my device to Lollipop. Everything was ok but after a while it stopped working... Meantime I changed my device, so i put my Moto E in a drawer! Now I wanna use it again, but I have a lot of problem with fastboot (that's the only stage that works on my phone).
I tried to repeat the process for install the original firmware (http://forum.xda-developers.com/showthread.php?t=2755857) but i had always the same errors:
After few try i unlocked bootloader, and the process was done ok (also if i read "Device is locked. Status code:0" is it normal?).
I tried to flash CWM or TWRP but without success. Always the same error: failed to validate system image.
Someone can help me?
Sorry for my english...
Click to expand...
Click to collapse
First unlock bootloader then flash twrp
What steps u r using to flash TWRP??
Ujwal Agrawal said:
What steps u r using to flash TWRP??
Click to expand...
Click to collapse
If you already unlocked boot loader
Then flash twrp in fastboot command
Fastboot flash recovery twrp.3.x.x.img
Rajendran Rasa said:
First unlock bootloader then flash twrp
Click to expand...
Click to collapse
I unlocked bootloader (with this guide: http://forum.xda-developers.com/showthread.php?t=2753110) then i tried flash recovery with this guide: http://forum.xda-developers.com/moto-e/general/root-moto-e-rooting-flashing-recovery-t2802971.
I tried with CWM and TWRP too!
superazo said:
I unlocked bootloader (with this guide: http://forum.xda-developers.com/showthread.php?t=2753110) then i tried flash recovery with this guide: http://forum.xda-developers.com/moto-e/general/root-moto-e-rooting-flashing-recovery-t2802971.
I tried with CWM and TWRP too!
Click to expand...
Click to collapse
https://dl.twrp.me/condor/
Try the latest TWRP
Ujwal Agrawal said:
Try the latest TWRP
Click to expand...
Click to collapse
Tried...
Code:
fastboot flash recovery twrp-3.0.2-0-condor.img
target reported max download size of 299892736 bytes
sending 'recovery' (6808 KB)...
OKAY [ 0.244s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.295s
If I reboot and go to "Recovery" voice:
Code:
failed to validate system image
Boot up failed

fastboot: FAILED (remote: cannot flash this partition in unlocked state)

Hi,
Can someone clarify what this message means and why fastboot is failing?
Thanks
Code:
# fastboot flash aboot aboot_300032.bin
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.036s]
writing 'aboot'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 0.038s
Probably because your phone has unlocked bootloader and needs to be locked .
Instruction how to do that .
https://www.google.rs/amp/s/www.theandroidsoul.com/relock-bootloader-fastboot-android/amp/
Good luck : )
Any ideas how to solve this catch 22? I mean other than using the LG Flash Tool or LG UP. I didn't much success with them.
Thanks
Code:
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.749s]
writing 'modem'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 2.750s
# fastboot oem lock
...
(bootloader) Erasing userdata and cache
OKAY [ 1.881s]
finished. total time: 1.882s
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.775s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.776s
greerdd said:
Any ideas how to solve this catch 22? I mean other than using the LG Flash Tool or LG UP. I didn't much success with them.
Thanks
Code:
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.749s]
writing 'modem'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 2.750s
# fastboot oem lock
...
(bootloader) Erasing userdata and cache
OKAY [ 1.881s]
finished. total time: 1.882s
# fastboot flash modem modem_16384.bin
target reported max download size of 536870912 bytes
sending 'modem' (86016 KB)...
OKAY [ 2.775s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.776s
Click to expand...
Click to collapse
I have the same problem. Did u solve this ?
exact same problem, is there any solution exist?

[DOWNGRADING] [QUICK GUIDE] Solved: Directly Rebooting to Recovery and not to System!

**************THE PROBLEM***************
Boot into recovery (twrp) - and flash Los 15.1 after formatting internal- then comes the *error 255* .
So I tried it with twrp treble and it flashed without any problems.
After flashing I clicked reboot and it rebooted into twrp again.
No matter how many times I try rebooting from system or twrp it boots into twrp itself. *Tried with many twrps*
But it boots into bootloader and from there I could click start to boot to system!
So I thought I would flash stock ROM (Oreo August) and I did. On rebooting, it went straight to stock recovery and I selected reboot to system and it didn't! It rebooted back to the recovery!
So I rebooted into the bootloader and clicked start and then it boots! And it shows encrypting and reboots to the setup area.
After setting up I rebooted the device ( normal way ) and again I found myself in the stock recovery!!
**************** THE SOLUTION **************
FLASH STOCK NOUGAT ROM (I FLASHED THE NOVEMBER BUILD)
Link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Since I was on Oreo downgrading was not directly applicable.. I flashed TWRP and formatted the phone then booted to bootloader and flashed the stock ROM!
Fastboot commands didn't work exactly ! So I followed this guide to get the servicefile.xml in the ROM zip to create a new .bat file that flashed the phone!
Link: https://youtu.be/njXQYn53SPc
OR
I've made an attachment of the .bat file that you can download and extract.
Bootloader was left unlocked!
OTAs were successful! No issues so far! Flashed November 2017 Fastboot ROM and updated to August 2018 Oreo via OTA!
Cheers People!! Happy Flashing!!
Oh! And as always! No one will take responsibility for your actions! You alone are responsible!! ? #standardprocedure
Hi, u wipe data and factory data in the recovery before installing stock? i had the same problem yesterday and I solved it flashing stock 7.1.1 (NPSS26.118-19-14 - November 2017)
SteveO-RG said:
Hi, u wipe data and factory data in the recovery before installing stock? i had the same problem yesterday and I solved it flashing stock 7.1.1 (NPSS26.118-19-14 - November 2017)
Click to expand...
Click to collapse
Thanks mate! It Worked Well! ??
Cheers!!
I have the same problem. I've tried TWRP 3.2.1_r12 and 3.2.3-0, in both cases the phone reboots to recovery and I have to reboot again to bootloader and from there to the OS. Any way to fix this without going back to stock ROM? It's no big deal, I reboot rarely, but still slightly annoying.
indrekh said:
I have the same problem. I've tried TWRP 3.2.1_r12 and 3.2.3-0, in both cases the phone reboots to recovery and I have to reboot again to bootloader and from there to the OS. Any way to fix this without going back to stock ROM? It's no big deal, I reboot rarely, but still slightly annoying.
Click to expand...
Click to collapse
I honestly tried many times to get it working normally without going back to stock ROM but couldn't!
Sorry bruv! I guess this is the only way! :angel:
the_phantom_97 said:
I honestly tried many times to get it working normally without going back to stock ROM but couldn't!
Sorry bruv! I guess this is the only way! :angel:
Click to expand...
Click to collapse
Bummer. Thanks anyway
DUDE!!!
I had an Issue yesterday while trying to downgrade and i ended having a custom ROM with the fingerprint sensor disabled i dont know why!
But today i followed this thread an solved the problem!!
A lot of thanks my friend! My eternal gratitude!!!
Thanks for this solution, but I still get BAD KEY message and I can't relock bootloader. Any advice to solve this problem? Thx
the_phantom_97 said:
**************THE PROBLEM***************
Boot into recovery (twrp) - and flash Los 15.1 after formatting internal- then comes the *error 255* .
So I tried it with twrp treble and it flashed without any problems.
After flashing I clicked reboot and it rebooted into twrp again.
No matter how many times I try rebooting from system or twrp it boots into twrp itself. *Tried with many twrps*
But it boots into bootloader and from there I could click start to boot to system!
So I thought I would flash stock ROM (Oreo August) and I did. On rebooting, it went straight to stock recovery and I selected reboot to system and it didn't! It rebooted back to the recovery!
So I rebooted into the bootloader and clicked start and then it boots! And it shows encrypting and reboots to the setup area.
After setting up I rebooted the device ( normal way ) and again I found myself in the stock recovery!!
**************** THE SOLUTION **************
FLASH STOCK NOUGAT ROM (I FLASHED THE NOVEMBER BUILD)
Link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Since I was on Oreo downgrading was not directly applicable.. I flashed TWRP and formatted the phone then booted to bootloader and flashed the stock ROM!
Fastboot commands didn't work exactly ! So I followed this guide to get the servicefile.xml in the ROM zip to create a new .bat file that flashed the phone!
Link:
OR
I've made an attachment of the .bat file that you can download and extract.
Bootloader was left unlocked!
OTAs were successful! No issues so far! Flashed November 2017 Fastboot ROM and updated to August 2018 Oreo via OTA!
Cheers People!! Happy Flashing!!
Oh! And as always! No one will take responsibility for your actions! You alone are responsible!! ? #standardprocedure
Click to expand...
Click to collapse
JRapsky said:
Thanks for this solution, but I still get BAD KEY message and I can't relock bootloader. Any advice to solve this problem? Thx
Click to expand...
Click to collapse
That is most probably because you're trying to flash an old firmware wherein your bootloader is already on the newer one! We'll try flashing with this December 2018 firmware linked below but don't use the zip in the thread... It is only for Nougat Firmware!
2018 December Firmware:-
https://androidfilehost.com/?fid=11410963190603890525
Fastboot command zip by @brunorochaa00 :- https://androidfilehost.com/?fid=13356325061477270130
this zip has the fastboot and the commands... Just extract the firmware to the folder where you extract the zip and flash any of the .bat files!!
i ran through all these commands but it still says no OS is installed in TWRP
trying to install custom rom give 255 ERROR'
do these logs look normal?
PS C:\adb> .\2-Instalador-Completo.bat
*************************************************
* Instalador Firmware *
* Moto Z2 Play Albus XT1710 *
* Script by Junior Passos *
*************************************************
"Desligue seu Moto Z2 Play e conecte-o no computador em Modo Fastboot."
"Aviso: Os arquivos no armazenamento interno serao totalmente deletados!"
Press any key to continue . . .
< waiting for device >
max-sparse-size: 268435456
finished. total time: 0.001s
...
OKAY [ 0.002s]
finished. total time: 0.002s
sending 'partition' (45 KB)...
OKAY [ 0.002s]
writing 'partition'...
Validating 'gpt.default.xml'
Security version downgrade
Image primary_gpt failed validation
Preflash validation failed
Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.076s
sending 'bootloader' (5115 KB)...
OKAY [ 0.116s]
writing 'bootloader'...
Validating 'bootloader.default.xml'
Committing 'bootloader.default.xml'
- flashing 'emmc_appsboot.mbn' to 'aboot'
- flashing 'rpm.mbn' to 'rpm'
- flashing 'tz.mbn' to 'tz'
- flashing 'devcfg.mbn' to 'devcfg'
- flashing 'cmnlib.mbn' to 'cmnlib'
- flashing 'cmnlib64.mbn' to 'cmnlib64'
- flashing 'keymaster.mbn' to 'keymaster'
- flashing 'prov.mbn' to 'prov'
- flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.526s]
finished. total time: 0.644s
sending 'modem' (71573 KB)...
OKAY [ 1.612s]
writing 'modem'...
OKAY [ 1.126s]
finished. total time: 2.761s
sending 'fsg' (4020 KB)...
OKAY [ 0.081s]
writing 'fsg'...
OKAY [ 0.126s]
finished. total time: 0.233s
erasing 'modemst1'...
OKAY [ 0.032s]
finished. total time: 0.032s
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.032s
sending 'dsp' (16384 KB)...
OKAY [ 0.370s]
writing 'dsp'...
OKAY [ 0.295s]
finished. total time: 0.668s
sending 'logo' (2192 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.098s]
finished. total time: 0.164s
sending 'boot' (16384 KB)...
OKAY [ 0.432s]
writing 'boot'...
Image signed with key bad key
OKAY [ 0.392s]
finished. total time: 0.840s
sending 'recovery' (20580 KB)...
OKAY [ 0.522s]
writing 'recovery'...
Image size exeeded partition limits
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.536s
sending 'system' (262141 KB)...
OKAY [ 6.039s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 6.058s
sending 'system' (255657 KB)...
OKAY [ 5.741s]
writing 'system'...
OKAY [ 3.393s]
finished. total time: 9.142s
sending 'system' (243061 KB)...
OKAY [ 5.673s]
writing 'system'...
OKAY [ 3.380s]
finished. total time: 9.058s
sending 'system' (260374 KB)...
OKAY [ 6.039s]
writing 'system'...
OKAY [ 3.955s]
finished. total time: 10.002s
sending 'system' (260395 KB)...
OKAY [ 6.005s]
writing 'system'...
OKAY [ 3.608s]
finished. total time: 9.629s
sending 'system' (242845 KB)...
OKAY [ 5.567s]
writing 'system'...
OKAY [ 3.173s]
finished. total time: 8.753s
sending 'system' (262140 KB)...
OKAY [ 5.994s]
writing 'system'...
OKAY [ 3.402s]
finished. total time: 9.402s
sending 'system' (262141 KB)...
OKAY [ 6.108s]
writing 'system'...
OKAY [ 3.620s]
finished. total time: 9.742s
sending 'system' (262142 KB)...
OKAY [ 5.885s]
writing 'system'...
OKAY [ 3.633s]
finished. total time: 9.531s
sending 'system' (262141 KB)...
OKAY [ 6.044s]
writing 'system'...
OKAY [ 3.412s]
finished. total time: 9.465s
sending 'system' (239056 KB)...
OKAY [ 5.488s]
writing 'system'...
Invalid sparse image data
Failed to flash sparse image
FAILED (remote failure)
finished. total time: 7.494s
sending 'system' (45248 KB)...
OKAY [ 1.018s]
writing 'system'...
Invalid sparse image data
Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.044s
sending 'oem' (155105 KB)...
OKAY [ 3.549s]
writing 'oem'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 3.562s
erasing 'carrier'...
OKAY [ 0.135s]
finished. total time: 0.150s
erasing 'cache'...
OKAY [ 0.008s]
finished. total time: 0.008s
erasing 'userdata'...
OKAY [ 0.128s]
finished. total time: 0.140s
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.002s
...
OKAY [ 0.002s]
finished. total time: 0.002s
"Arquivos instalados com sucesso!"
rebooting...
finished. total time: 0.001s
I tried installing custom ROM (viper OS) on my moto z2 play and it showed the same error. Updater process error 255 and after trying two more ROMs my phone is stuck in twrp mode. Why the error: 255 and how to fix it, is it that i can never install a custom ROM or what? and about downgrading it to NOUGAT i'm trying it now. I'll let you know if it works. but can you help me with the error 255!
FIX
Use this command on PC:
fastboot oem fb_mode_clear
https://forum.xda-developers.com/showthread.php?t=2774709&page=5
Works! But i lost my imei...

Categories

Resources