Moto E 2nd Gen 4G LTE model (XT1521) not booting up - E 2015 Q&A, Help & Troubleshooting

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

Related

[Q] Device locked and system image reflash required - a deadlock situation

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!!!!

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 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 G5NPFP026657RFA

Hi,
I am trying to revive my Asus and running into following problem. I read multiple threads and forums and have executed multiple commands in cmd fastboot. Getting following errors:
First I was running into error that "vrl needs to be flashed" which I found a correct (I hope) file and flashed the vrl, and then flashed CM13 or stock ROM from Asus website. Which fastboot returns with "OKAY flashed partition system. Time 28 seconds" Still wont boot and stuck on boot logo.
C:\adb>fastboot devices
G5NPFP026657RFA fastboot
C:\adb>fastboot flash system UL-P023-CN-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
erasing 'system'...
(bootloader) Erasing partition: system
OKAY [ 0.031s]
sending 'system' (907352 KB)...
(bootloader) Ready to receive: 0x376162fc size of data
OKAY [ 28.448s]
writing 'system'...
(bootloader) Flashing partition: system
FAILED (remote: VRL need to be flashed!)
finished. total time: 28.511s
C:\adb>fastboot flash vrl vrl2.bin
(bootloader) vrl partition type: raw
target reported max download size of 1019215872 bytes
sending 'vrl' (128 KB)...
(bootloader) Ready to receive: 0x00020000 size of data
OKAY [ 0.016s]
writing 'vrl'...
(bootloader) Flashing partition: vrl
OKAY [ 0.078s]
finished. total time: 0.094s
C:\adb>fastboot flash system UL-P023-CN-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
erasing 'system'...
(bootloader) Erasing partition: system
OKAY [ 0.047s]
sending 'system' (907352 KB)...
(bootloader) Ready to receive: 0x376162fc size of data
OKAY [ 28.424s]
writing 'system'...
(bootloader) Flashing partition: system
OKAY [ 0.031s]
finished. total time: 28.518s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Any of the senior members or other who have more knowledge, please shade some light here and tell me what am I doing wrong??
I also get below error at times, and my computer gets stuck every time I execute below command and it takes forever for it to get back to working by itself unless I try to close the application.
C:\adb>fastboot update system "C:\adb\UL-P023-WW-4.7.3.0-user.zip"
W/ ( 448): Unable to open 'system': No such file or directory
error: failed to open zip file 'system': I/O Error
C:\adb>fastboot flash system UL-P023-WW-4.7.3.0-user.zip
(bootloader) system partition type: ext4
target reported max download size of 1019215872 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 175719111 is not a multiple of t
he block size 4096
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 1.102s
Very much keen to read some good replies. Thanks in advance guys.

Stuck in "Your device has been unlocked and can't be trusted. […] ID: bad key"

Stuck in "Your device has been unlocked and can't be trusted. […] ID: bad key"
I wanted to root the device but I now I have a device that doesn't boot anymore.
What I've done so far wasn't this much:
unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
flashed TWRP (fastboot flash recovery twrp-3.0.2-0-griffin.img)
I bootet into the system, downloaded Magisk because I was going to root the device. I bootet into Recovery / TWRP and saw that I wasn't able to find the download folder where I downloaded Magisk. I rebootet and since then I can't boot into the system again.
Fastboot and recovery are possible tough. When I'm trying to boot regulary the device is stuck in:
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
It looks pretty much like this except the ID ('N/A' in the image but 'bad key' on my mobile).
But it never boots. Before TWRP the screen appears as well but at least it is booting into TWRP.
Clearing cache didn't help neither.
Any idea what could help?
PS: I changed the clock in TWRP to 24h format but I guess this should brake anything — right?
PPS: I also tried to flash some official image (XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA) I found here somewhere but it failed with an error message that it won't downgrade security and therefore not flash. Perhaps because I upgraded to Android 7 when I got the mobile?
PPPS: I found a thread on another board with the same problem but no solution
hackepeterbroetchen said:
I wanted to root the device but I now I have a device that doesn't boot anymore.
What I've done so far wasn't this much:
unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
flashed TWRP (fastboot flash recovery twrp-3.0.2-0-griffin.img)
I bootet into the system, downloaded Magisk because I was going to root the device. I bootet into Recovery / TWRP and saw that I wasn't able to find the download folder where I downloaded Magisk. I rebootet and since then I can't boot into the system again.
Fastboot and recovery are possible tough. When I'm trying to boot regulary the device is stuck in:
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
It looks pretty much like this except the ID ('N/A' in the image but 'bad key' on my mobile).
But it never boots. Before TWRP the screen appears as well but at least it is booting into TWRP.
Clearing cache didn't help neither.
Any idea what could help?
PS: I changed the clock in TWRP to 24h format but I guess this should brake anything — right?
PPS: I also tried to flash some official image (XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA) I found here somewhere but it failed with an error message that it won't downgrade security and therefore not flash. Perhaps because I upgraded to Android 7 when I got the mobile?
PPPS: I found a thread on another board with the same problem but no solution
Click to expand...
Click to collapse
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
doree said:
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
Click to expand...
Click to collapse
But I didn't flash another rom yet at all. I just flashed TWRP recovery image so far. Are you sure that you had the same issue?
hackepeterbroetchen said:
But I didn't flash another rom yet at all. I just flashed TWRP recovery image so far. Are you sure that you had the same issue?
Click to expand...
Click to collapse
I wouldn't reply if I wasn't.
You should have rebooted the device after unlocking the device, because it gets wiped after the process. Since you flashed TWRP right after unlocking it, you left the device wiped, therefore there's no system to gain access to. That's the reason you're stuck.
Hm Im stuck at the same screen. My question is just, how can I flash the Rom if the phones not booting and I dont get the Zip on the phone? Recovery and Bootloader works, but no system start. And unfortunately your link only shows 404: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Thanks for you help!
(Found this link tho: https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/)
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
doree said:
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
Click to expand...
Click to collapse
doree said:
I wouldn't reply if I wasn't.
You should have rebooted the device after unlocking the device, because it gets wiped after the process. Since you flashed TWRP right after unlocking it, you left the device wiped, therefore there's no system to gain access to. That's the reason you're stuck.
Click to expand...
Click to collapse
And if I want to sideload it says Invaild zip file Format in recovery and
Code:
C:\adb>adb sideload xt1635.zip
loading: 'xt1635.zip'
error: device '(null)' not found
C:\adb>adb sideload xt1635.zip
Total xfer: 0.00x
in cmd. :S
nighteeeeeY said:
Hm Im stuck at the same screen. My question is just, how can I flash the Rom if the phones not booting and I dont get the Zip on the phone? Recovery and Bootloader works, but no system start. And unfortunately your link only shows 404: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Thanks for you help!
(Found this link tho: https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/)
Click to expand...
Click to collapse
It shows 404 because the Site ran out of Traffic. The Info is on the frontpage. Do NOT flash the stuff you posted, because it's for a different model.
hackepeterbroetchen said:
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
Click to expand...
Click to collapse
Yep, you can't flash the Image, because you already updated your Bootloader to 7.0 Nougat. Therefore a flash attempt of the Image you mentioned will fail. It only works with a 6.0 Bootloader, since it's an 6.0 Stock Image.
nighteeeeeY said:
And if I want to sideload it says Invaild zip file Format in recovery and
Code:
C:\adb>adb sideload xt1635.zip
loading: 'xt1635.zip'
error: device '(null)' not found
C:\adb>adb sideload xt1635.zip
Total xfer: 0.00x
in cmd. :S
Click to expand...
Click to collapse
You need to Install ADB, boot into the Bootloader, unpack the Image I mentioned and execute the fastboot command I mentioned in the othet Post.
// Wait a sec. I will repack the stock image and will add the needed Stuff for you all.
hackepeterbroetchen said:
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
Click to expand...
Click to collapse
You didn't account for the line break... It should read something like "Blur_Version.25.221.12.griffin.retail.en.US". However, you have to submit the version that currently runs on your phone - and the server will give you the next update! For the version you provided, there is no update.
You may want to try this:
backup everything you can via TWRP...
boot into bootloader (fastboot)
restore 6.0.1 image [a] via fastboot, see batch file below (the nougat bootloader doesn't let you boot it, but fastboot hopefully doesn't prevent flashing it..)
The nougat bootloader prevents downgrading itself and will cause that fastboot line to fail. Leave it in anyway. If the script breaks or anything, remove the line from the script and retry.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
directly boot into (stock) recovery, do not try to boot the system
press and hold down power, then press volume-up, release volume-up, then power.
select 'Apply update from ADB'
sideload nougat update from PC console: "fastboot sideload Blur_Version.25.11.14.griffin.retail.en.US.zip"
[*] Wipe data/factory reset, Wipe cache partition, Power off
[*] reboot
Please report back how it all worked out for you...
[a] XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip
OTA: Blur_Version.(24.21.46 --> 25.11.14).griffin.retail.en.US
Okay guys, do the following:
1) Download the Stock Image here and extract the archive to a folder of your choice: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://www.sendspace.com/file/1rm4cj
3) Shutdown your phone and then push the VOL- and Power-Button at the same time. You should now enter the Bootloader.
4) Connect your phone to the computer (USB)
5) Open up the command prompt and go the folder where you extracted the Stock Image and Fastboot files to
6) Type _FLASH.bat and ignore all error messages you will possibly see
7) Wait till the phone boots up with the Motorola Splashscreen
That's how I revived my device.
doree said:
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://mega.nz/fm/hqplTQJS
Click to expand...
Click to collapse
It says "No Data". Do I do something wrong? Just created an account.
I have created this batch from your previous post on the other thread:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is this correct? Or the one @benzinerwin just posted?
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
nighteeeeeY said:
It says "No Data". Do I do something wrong? Just created an account.
I have created this batch from your previous post on the other thread:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is this correct? Or the one @benzinerwin just posted?
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Use this link instead: https://www.sendspace.com/file/1rm4cj
My method is a different approach than benzinerwin's. Use the method you feel comfortable with.
Phew! Thanks. Worked out perfectly.
benzinerwin said:
You didn't account for the line break... It should read something like "Blur_Version.25.221.12.griffin.retail.en.US".
Click to expand...
Click to collapse
I really didn't see that
benzinerwin said:
You may want to try this:
backup everything you can via TWRP...
boot into bootloader (fastboot)
restore 6.0.1 image [a] via fastboot, see batch file below (the nougat bootloader doesn't let you boot it, but fastboot hopefully doesn't prevent flashing it..)
Click to expand...
Click to collapse
I'm getting errors with it (@benzinerwin method)
Code:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.142s
target reported max download size of 536870912 bytes
sending 'bootloader' (7076 KB)...
OKAY [ 0.030s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.202s
doree said:
Okay guys, do the following:
3) Shutdown your phone and then push the VOL+ and Power-Button at the same time. You should now enter the Bootloader.
Click to expand...
Click to collapse
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
hackepeterbroetchen said:
I really didn't see that
I'm getting errors with it (@benzinerwin method)
Click to expand...
Click to collapse
When rolling back the bootloader is not allowed, then also writing an older GPT will be prevented. Sorry, I missed that.
However, writing a retail image for a different country seems to work - the phone keepts its 'reteu' setting (I just tried it for a different reason).
That makes things a lot easier: just flash the RETxx nougat image as @doree discribed and you should be fine!
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
Click to expand...
Click to collapse
Maybe that worked in the old days With current bootloader versions only VOL- & power works. But that only gets you into the fastboot mode, from which you can launch recovery...
hackepeterbroetchen said:
I really didn't see that
I'm getting errors with it (@benzinerwin method)
Code:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.142s
target reported max download size of 536870912 bytes
sending 'bootloader' (7076 KB)...
OKAY [ 0.030s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.202s
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
Click to expand...
Click to collapse
Sorry, I meant VOL-. Typed it in a hurry!
So I tried XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC now and it fails on different files:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.048s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.061s
target reported max download size of 536870912 bytes
sending 'modem' (73570 KB)...
OKAY [ 0.269s]
writing 'modem'...
OKAY [ 1.035s]
finished. total time: 1.304s
target reported max download size of 536870912 bytes
sending 'fsg' (1976 KB)...
OKAY [ 0.051s]
writing 'fsg'...
OKAY [ 0.369s]
finished. total time: 0.420s
erasing 'modemst1'...
OKAY [ 0.193s]
finished. total time: 0.193s
erasing 'modemst2'...
OKAY [ 0.188s]
finished. total time: 0.188s
error: cannot load 'BTFM.bin'
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.075s]
writing 'dsp'...
OKAY [ 0.467s]
finished. total time: 0.542s
target reported max download size of 536870912 bytes
sending 'logo' (2533 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.377s]
finished. total time: 0.432s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.094s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.467s]
finished. total time: 0.561s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.083s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.468s]
finished. total time: 0.552s
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 2.764s]
finished. total time: 3.730s
target reported max download size of 536870912 bytes
sending 'system' (261378 KB)...
OKAY [ 1.035s]
writing 'system'...
OKAY [ 1.873s]
finished. total time: 2.908s
target reported max download size of 536870912 bytes
sending 'system' (251415 KB)...
OKAY [ 0.986s]
writing 'system'...
OKAY [ 1.867s]
finished. total time: 2.853s
target reported max download size of 536870912 bytes
sending 'system' (255815 KB)...
OKAY [ 0.959s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 2.895s
target reported max download size of 536870912 bytes
sending 'system' (255582 KB)...
OKAY [ 0.935s]
writing 'system'...
OKAY [ 1.938s]
finished. total time: 2.873s
target reported max download size of 536870912 bytes
sending 'system' (257857 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 1.775s]
finished. total time: 2.741s
target reported max download size of 536870912 bytes
sending 'system' (260164 KB)...
OKAY [ 1.016s]
writing 'system'...
OKAY [ 1.750s]
finished. total time: 2.766s
target reported max download size of 536870912 bytes
sending 'system' (253309 KB)...
OKAY [ 0.992s]
writing 'system'...
OKAY [ 1.919s]
finished. total time: 2.911s
target reported max download size of 536870912 bytes
sending 'system' (256398 KB)...
OKAY [ 1.061s]
writing 'system'...
OKAY [ 1.805s]
finished. total time: 2.866s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 1.066s]
writing 'system'...
OKAY [ 1.779s]
finished. total time: 2.845s
target reported max download size of 536870912 bytes
sending 'system' (147418 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 1.079s]
finished. total time: 1.706s
error: cannot load 'system.img_sparsechunk.11'
error: cannot load 'system.img_sparsechunk.12'
error: cannot load 'system.img_sparsechunk.13'
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 0.454s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.477s
erasing 'cache'...
OKAY [ 0.379s]
finished. total time: 0.379s
erasing 'userdata'...
OKAY [ 1.957s]
finished. total time: 1.957s
erasing 'customize'...
OKAY [ 0.365s]
finished. total time: 0.365s
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
erasing 'ddr'...
OKAY [ 0.312s]
finished. total time: 0.312s
rebooting...
finished. total time: 0.903s
These were the commands I ran (these are the ones @doree linked)
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is it because the image is XT1635-02 instead XT1650-03?
EDIT:
I did flash it this way now anyway (I probably shouldn't have done this, sorry) but reboot failed now and moves directly to fastboot with the following error message:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
EDIT 2:
I tried ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC with Android 7 now with the same effect. I guess I am missing something here?
PS: I absolutely appreciate your help and it's impressive how fast you answer. Thank you very much for this.
hackepeterbroetchen said:
So I tried XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC now and it fails on different files:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.048s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.061s
target reported max download size of 536870912 bytes
sending 'modem' (73570 KB)...
OKAY [ 0.269s]
writing 'modem'...
OKAY [ 1.035s]
finished. total time: 1.304s
target reported max download size of 536870912 bytes
sending 'fsg' (1976 KB)...
OKAY [ 0.051s]
writing 'fsg'...
OKAY [ 0.369s]
finished. total time: 0.420s
erasing 'modemst1'...
OKAY [ 0.193s]
finished. total time: 0.193s
erasing 'modemst2'...
OKAY [ 0.188s]
finished. total time: 0.188s
error: cannot load 'BTFM.bin'
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.075s]
writing 'dsp'...
OKAY [ 0.467s]
finished. total time: 0.542s
target reported max download size of 536870912 bytes
sending 'logo' (2533 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.377s]
finished. total time: 0.432s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.094s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.467s]
finished. total time: 0.561s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.083s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.468s]
finished. total time: 0.552s
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 2.764s]
finished. total time: 3.730s
target reported max download size of 536870912 bytes
sending 'system' (261378 KB)...
OKAY [ 1.035s]
writing 'system'...
OKAY [ 1.873s]
finished. total time: 2.908s
target reported max download size of 536870912 bytes
sending 'system' (251415 KB)...
OKAY [ 0.986s]
writing 'system'...
OKAY [ 1.867s]
finished. total time: 2.853s
target reported max download size of 536870912 bytes
sending 'system' (255815 KB)...
OKAY [ 0.959s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 2.895s
target reported max download size of 536870912 bytes
sending 'system' (255582 KB)...
OKAY [ 0.935s]
writing 'system'...
OKAY [ 1.938s]
finished. total time: 2.873s
target reported max download size of 536870912 bytes
sending 'system' (257857 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 1.775s]
finished. total time: 2.741s
target reported max download size of 536870912 bytes
sending 'system' (260164 KB)...
OKAY [ 1.016s]
writing 'system'...
OKAY [ 1.750s]
finished. total time: 2.766s
target reported max download size of 536870912 bytes
sending 'system' (253309 KB)...
OKAY [ 0.992s]
writing 'system'...
OKAY [ 1.919s]
finished. total time: 2.911s
target reported max download size of 536870912 bytes
sending 'system' (256398 KB)...
OKAY [ 1.061s]
writing 'system'...
OKAY [ 1.805s]
finished. total time: 2.866s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 1.066s]
writing 'system'...
OKAY [ 1.779s]
finished. total time: 2.845s
target reported max download size of 536870912 bytes
sending 'system' (147418 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 1.079s]
finished. total time: 1.706s
error: cannot load 'system.img_sparsechunk.11'
error: cannot load 'system.img_sparsechunk.12'
error: cannot load 'system.img_sparsechunk.13'
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 0.454s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.477s
erasing 'cache'...
OKAY [ 0.379s]
finished. total time: 0.379s
erasing 'userdata'...
OKAY [ 1.957s]
finished. total time: 1.957s
erasing 'customize'...
OKAY [ 0.365s]
finished. total time: 0.365s
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
erasing 'ddr'...
OKAY [ 0.312s]
finished. total time: 0.312s
rebooting...
finished. total time: 0.903s
These were the commands I ran (these are the ones @doree linked)
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is it because the image is XT1635-02 instead XT1650-03?
EDIT:
I did flash it this way now anyway (I probably shouldn't have done this, sorry) but reboot failed now and moves directly to fastboot with the following error message:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
EDIT 2:
I tried ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC with Android 7 now with the same effect. I guess I am missing something here?
PS: I absolutely appreciate your help and it's impressive how fast you answer. Thank you very much for this.
Click to expand...
Click to collapse
Where are you getting this links from? My post cleary leads to:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You are trying to flash an Image for a whole different Device (Moto Z Play).
Moto Z Play = XT-1635 Addison
Moto Z = XT-1650 Griffin
doree said:
Where are you getting this links from? My post cleary leads to:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You are trying to flash an Image for a whole different Device (Moto Z Play).
Moto Z Play = XT-1635 Addison
Moto Z = XT-1650 Griffin
Click to expand...
Click to collapse
Oh boy! I guess this happened because I skipped coffee today
@doree the mobile is booting again. I guess I owe you a beer. Thank you so much!
I guess it isn't possible to go back to the EU rom again for now?
However, now TWRP and root!
Can you recommend any root system for using it with the stock rom?
hackepeterbroetchen said:
Oh boy! I guess this happened because I skipped coffee today
@doree the mobile is booting again. I guess owe you a beer. Thank you so much!
Click to expand...
Click to collapse
Glad I could help
I guess it isn't possible to go back to the EU rom again for now?
Click to expand...
Click to collapse
RETBR is pretty much the same as the "regular" RETEU Rom, since it uses the same Softwarechannel (Settings/About/Softwarechannel). You'll get the same Updates as everyone else in Germany/Europe.
However, now TWRP and root!
Can you recommend any root system for using it with the stock rom?
Click to expand...
Click to collapse
What do you exactly mean with "root system"?

Categories

Resources