[Q] Device locked and system image reflash required - a deadlock situation - E 2015 Q&A, Help & Troubleshooting

I got the key and used "fastboot oem unlock <key>" to unlock the device. Replace the logo.bin so that the warning messages goes off. After that I locked the phone. Following is the screenshot.
# fastboot oem lock
...
(bootloader) Phone is locked successfully!
(bootloader) Please reflash system image before reboot the phone!
OKAY [ 1.595s]
finished. total time: 1.595s
Now the phone remains in fastboot mode because it cannot boot (system image issue.). While unlocking it says,
# fastboot oem unlock W3YRQHWOSLI2V7OVUI4L
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.007s
It is a deadlock situation now, I cannot change the option because the phone does not boot to access Developer options and cannot flash because it is locked. (The display says Device is LOCKED. Status Code: 2, Software staus modified.)

I think this is the answer of your question : http://forum.xda-developers.com/showthread.php?p=59564073

dulce.ai.angel said:
I think this is the answer of your question : http://forum.xda-developers.com/showthread.php?p=59564073
Click to expand...
Click to collapse
Thanks a lot for the quick response. Looks better now. At least not flagging Check 'Allow OEM Unlock' in Developer Options'. but transformed to 'Preflash validation failed' , not sure if it means the same as before. The response is as below.
# mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (32768 KB)...
OKAY [ 1.038s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.664s
When flashing system images it gives:
# mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.231s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.638s
Gives Invalid signed image. As from fastboot screen, the product variant is "sunria XT1521 8GB P3" of Moto E 2015 4g LTE, country - India. Used the same image as refereed above "XT1527_SURNIA_RETUS_5.0.2_LXI22.50-24.1_cid9_subsidy-DEFAULT_CFC.xml.zip"
Still hopeful to bring it back. Any more clues ..

[Q][CLOSED] Device locked and system image reflash required - a deadlock situation
rakeshv62 said:
Thanks a lot for the quick response. Looks better now. At least not flagging Check 'Allow OEM Unlock' in Developer Options'. but transformed to 'Preflash validation failed' , not sure if it means the same as before. The response is as below.
# mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (32768 KB)...
OKAY [ 1.038s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.664s
When flashing system images it gives:
# mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.231s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.638s
Gives Invalid signed image. As from fastboot screen, the product variant is "sunria XT1521 8GB P3" of Moto E 2015 4g LTE, country - India. Used the same image as refereed above "XT1527_SURNIA_RETUS_5.0.2_LXI22.50-24.1_cid9_subsidy-DEFAULT_CFC.xml.zip"
Still hopeful to bring it back. Any more clues ..
Click to expand...
Click to collapse
Yayy !!!! I could bring the phone back to life after a day of coma. 
 @dulce.ai.angel - thanks for referring to squid2 link, must read for all fiddling with the device.
My 2 cents on it.
The problem was region. The build referred above refers to US ( .._RETUS_5.0.2...). I could get the image for the build for ASIA, pl search. I am too young on this group to put a external link (please drop a PM if needed for this).
With the Product name appearing on the initial fastboot string, Region, version of android, you will be able to makeout the right firmware. As for me the it was XT1521_SURNIA_RETASIA_DS_5.0.2_LXI22.50-53.1_cid7_subsidy-DEFAULT_CFC.xml.zip
Enjoy!!!!

Related

In need of Cricket XT1021 stock Recovery.IMG

i messed up my device trying to flash a different carrier's firmware and now my recovery doesn't work. Every other xt1021 recovery image i try to flash it says preflash verification failed. All i need is the Cricket Moto E recovery.img and i should be fine. If anybody could get this file for me i would be very greatful. (i can't install OTA updates or ADB sideload updates without this file)
xt1021 stock recovery
Try this: https://drive.google.com/folderview?id=0BwilK79Wld2CcGpMaUdiTWtYM0k&usp=sharing
mrgadgetuk said:
Try this: https://drive.google.com/folderview?id=0BwilK79Wld2CcGpMaUdiTWtYM0k&usp=sharing
Click to expand...
Click to collapse
validation failed
C:\Program Files\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.375s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
pinging all IP addresses for any signs of life.

Moto E 2nd Gen 4G LTE model (XT1521) not booting up

Hello folks,
On a fine day when I was disabling the airport mode, I realised the phone is hung as both the home screens - Aviate and Google were not responding. So I forced switched off the phone by holding down the power key for 15-20 seconds. The phone booted in fast boot mode and since then its not starting up.
Note - I never enabled USB debugging (developer mode) in this phone, so ADB will not work and I did not select "Allow OEM Unlock" - obviously I was not hoping this kind of unprovoked crash/bricking.
I am on Mac OS X with USB drivers installed for the device. I have access to a Windows Machine also, in case any of the suggested solutions work with windows tools.
Here is what I have tried so far after reading various threads in xdaDevelopers. Please note I have tried mfastboot on windows as well and have the same output -
(1.) Tried unlocking the phone as mentioned in the Motorola website and elsewhere in the forum. I get an error
Code:
$ ./fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.105s
The phone is unlockable with a cid of 0x007
Code:
$ fastboot getvar all
......
(bootloader) cid: 0x0007
......
(2.) Downloaded the MotoE stock firmware from here and followed the "How to flash Stock Firmware". All the commands are failing, below is the output.
Code:
$ fastboot devices -l
TA38500WHO fastboot usb:1D110000
$ fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.023s
$ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.098s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.548s
$ fastboot flash bootloader bootloader.imgtarget reported max download size of 268435456 bytes
sending 'bootloader' (2410 KB)...
OKAY [ 0.155s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.391s
$ fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (679 KB)...
OKAY [ 0.137s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.245s
$ fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (679 KB)...
OKAY [ 0.175s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.282s
$ fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32752 KB)...
OKAY [ 1.108s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.803s
$ fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32752 KB)...
OKAY [ 1.251s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.947s
$ fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 8.315s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.847s
$ fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.331s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.427s
$ fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.335s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.453s
$ fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (256116 KB)...
OKAY [ 8.120s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.229s
$ fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (240640 KB)...
OKAY [ 7.653s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.764s
$ fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (124212 KB)...
OKAY [ 3.977s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.064s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (54616 KB)...
OKAY [ 1.789s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.908s
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (54616 KB)...
OKAY [ 1.846s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.925s
$ fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.126s
$ fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.173s
$ fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1518 KB)...
OKAY [ 0.143s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.247s
$ fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (1518 KB)...
OKAY [ 0.189s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.293s
$ fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.167s
$ fastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.146s
$ fastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.049s
$ fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.023s
Any help in recovering the phone will be appreciated.
If you can get in to recovery from bootloader maybe try factory reset
When I select factory reset or recovery I got thrown to the fast boot prompt back. I checked the Bootloader logs in the fastboot mode which says - "failed to validate boot image. Boot up failed"
The same problem on 1528 after flashing stock rom!!? somebody can help us??
the firmware xt1528 have 6 files system.img_sparsechunk, and in the instruction -5, thats why phone cant start.....may be 1521 ? Look in unzipped folder with firmware how much files youve got?
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Romik80 said:
the firmware xt1528 have 6 files system.img_sparsechunk, and in the instruction -5, thats why phone cant start.....may be 1521 ? Look in unzipped folder with firmware how much files youve got?
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
It has 6 with me. There are errors / failures at every stage of flashing. That's what I am not able to understand.
ajitabhpandey said:
It has 6 with me. There are errors / failures at every stage of flashing. That's what I am not able to understand.
Click to expand...
Click to collapse
does it being flashed successfully?
sounds like it isn't therefor not booting up
according to the "log" you're not unlocked, therefore it fails
Tools to unbrick the device!
ajitabhpandey said:
Any help in recovering the phone will be appreciated.
Click to expand...
Click to collapse
Do take a look at this link:http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
I have the same problem even though my bootloader is unlocked. My phone decided to reboot one fine day and subsequently have been stuck at the bootloader. All the commands are accompanied in the log by "failed to validate abc image" where abc=boot,system,recovery etc.
Since my moto e is unlocked, I can't even RMA to Motorola for warranty :/
what were you running ?
what were you flashing ?
bootloader was locked when the problem occurred ?
Hey,
In the fastboot mode navigate to factory mode and then keep pressing the power button fast about 20-30 times till it boots into the os. Now u can access developer options and unlock the boot loader. Once the boot loader is unlocked u can flash the same rom again.......
I installed unofficial cm13 on my xt1521 everything good as of now .. i dont like the boot animation really worse.... so if any solution ?? pls do.... btw how to flash that i tried via twrp but no changes ...
kumaranwade said:
I installed unofficial cm13 on my xt1521 everything good as of now .. i dont like the boot animation really worse.... so if any solution ?? pls do.... btw how to flash that i tried via twrp but no changes ...
Click to expand...
Click to collapse
Install a theme with an alternate boot animation.
Sent from my SAMSUNG-SM-G920A using Tapatalk

[SOLVED][ISSUE] Bootloop after restoring stock firmware

My device is an XT1524. I was on CAF 6.0.1 rom and i wanted to come back stock, waiting for official Mashmallow. So i flashed this firmware https://mega.nz/#!ecUiUDDC!OG_MssktVAjTu4l7OGeqxKOFRIpBiml1Gro0VnfX0Tk following the guide step by step.
Now i am stuck at a bootloop. I can only boot to bootloader and in recovery mode there's only and android with red warning triangle.
I looked at the log and i notices these two failures:
Code:
D:\Downloads\XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.360s
Code:
D:\Downloads\XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml>mfastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.007s
What i have to do now?
Thanks
[SOLVED]
OK, i am a stupid.
5.1.1 firmwares have 6 sparsechunk files and i flashed only 5.

Unrooted and Locked Moto E XT1022 Suddenly stuck on boot logo

Yesterday, I was using my phone (Moto E XT1022) and suddenly it got turned off automatically..
When I tried Switching it on,it got stuck on boot logo...
Tried resetting cache/data from recovery mode but it gives the following error
E:Can't mount / cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Can't open /dev/block/platform/msm_sdcc.1/y-name/misc
(No such file or directory)
Click to expand...
Click to collapse
Also tried flashing 4.4.4 Kitkat stock firmware but it doesn't let me flash..Error:
Code:
C:\androide>mfastboot.exe oem lock begin
...
(bootloader) Device is already locked!
OKAY [ 0.023s]
finished. total time: 0.024s
C:\androide>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.488s
C:\androide>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.119s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 6.740s
C:\androide>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.075s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 5.085s
C:\androide>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.537s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 6.182s
C:\androide>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.556s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.208s
C:\androide>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (254408 KB)...
OKAY [ 11.958s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 26.784s
C:\androide>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (245298 KB)...
OKAY [ 11.531s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 19.975s
C:\androide>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (193465 KB)...
OKAY [ 9.065s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 26.199s
C:\androide>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 2.197s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 7.217s
C:\androide>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.017s
C:\androide>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.020s
C:\androide>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (857 KB)...
OKAY [ 0.120s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 5.139s
C:\androide>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.016s
C:\androide>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.016s
C:\androide>
Tried unlocking bootloader....
Output:
Code:
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure! FAILED
(remote failure) finished.
total time: 10.440s
Please help me..If I need to flash any other stock firmware,please help me with a link with complete steps...
Thanks in Advance
What OS version were you running before?
The 4.4.4 error suggests you were trying to downgrade.
Tapped from My Moto X
neo.ank said:
What OS version were you running before?
The 4.4.4 error suggests you were trying to downgrade.
Tapped from My Moto X
Click to expand...
Click to collapse
I was running 5.0.2 but the phone turned off automatically...Didn't find any firmware other than 4.4.4 online..
Same thing happn into my moto e, my is xt 1025 and was running 5.02 too.
The only diference is, even with the "error failed" message unlocking bootloader, now the device starts warning that the bootloader is unlocked.
But nothing that I try to downgrade works
Did you get any help?
thakkardeep18 said:
I was running 5.0.2 but the phone turned off automatically...Didn't find any firmware other than 4.4.4 online..
Click to expand...
Click to collapse
You can't downgrade. Best bet right now is flash TWRP and flash a custom ROM if you can't find stock 5.0.2
Tapped from My Moto X
neo.ank said:
You can't downgrade. Best bet right now is flash TWRP and flash a custom ROM if you can't find stock 5.0.2
Tapped from My Moto X
Click to expand...
Click to collapse
Can't.. The bootloader is locked and it gives me error while unlocking bootloader...
How am I supposed to flash TWRP before unlocking bootloader?

moto G3 2015 custom ROM to Stock ROM flashing issue

i installed all the drivers in PC and after trying commands one after another it stucks at command "fastboot flash partition gpt.bin" and showing the following error :
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.142s
after that other commands also not working and getting error: FAILED (remote failure)....now I am stuck at bootloader.......how to get rid of this issue....and works my handset well....... i searched all the questions in XDA and no command helped me out.......... cold u please help me out....thank you in advance

Categories

Resources