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" - Moto Z Questions & Answers

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"?

Related

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

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

Close bootloader and returns to stock after LineageOS without losing IMEI

My model is XT1710-09 of Tim Italia with single sim, but it has also been tested in a dual sim model.
This tutorial explains how to get back from LineageOS to stock firmware without losing the IMEI. You should always make a copy of the IMEI in TWPR.
How does it work:
You have to be in a modified rom.
1- You have to download this firmware with the February 2018 patch: https://androidfilehost.com/?fid=962187416754466195
2- Install adb minimal fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3- After installing adb minimal fastboot, go to the location of the ADB installation and paste all the files extracted from the downloaded firmware there.
4- Copy all the commands of this thread in the cmd window, press enter and wait.
Commands:
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 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 oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
These are the results that I have obtained
For US variant XT1710-01 https://forum.xda-developers.com/showpost.php?p=76192627&postcount=18

That way is way i used to return to stockOS on another devices

I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!

julesism said:
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
Click to expand...
Click to collapse
What I'm anxious to know is if the phone will get the OTA´s

julesism said:
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
Click to expand...
Click to collapse
I was going to try this on my XT1710-01 (Canada retail) on the weekend. Thanks for confirming!

While this get me back to the stock Moto ROM, it did not lock my bootloader.
Got the dreaded "Image signed with key bad key" message during various times during using the fastboot commands and my bootloader remains unlocked.
XT1710-01 (Canada Retail)

I think you should try it again I went thru the process posted in another thread by rajatgupta1998 and ended up exactly where you are now. I manually flashed a modified boot.img via adb to get the blue/red splash screen back although some text was still visible including bad key message.
When this topic was created, I decided to give it one more try. I had so may files unzipped from previous zips/flashes etc., I decided to make a clean adb folder with nothing but this zip/files extracted in it. Low and behold, it worked for me. I believe once, maybe twice the process stopped and I had to manually copy/paste the next command. Maybe something was missed.

Here's hoping this fixes my NFC issue

TravellingGuy said:
While this get me back to the stock Moto ROM, it did not lock my bootloader.
Got the dreaded "Image signed with key bad key" message during various times during using the fastboot commands and my bootloader remains unlocked.
XT1710-01 (Canada Retail)
Click to expand...
Click to collapse
This happened to me because I did not install the latest firmware. It is because the bootloader is more recent than the firmware you are trying to install. When putting the firmware of February 2018 I have been able to close the bootloader three times, after returning several times to lineageOS.

julesism said:
I think you should try it again I went thru the process posted in another thread by rajatgupta1998 and ended up exactly where you are now. I manually flashed a modified boot.img via adb to get the blue/red splash screen back although some text was still visible including bad key message.
When this topic was created, I decided to give it one more try. I had so may files unzipped from previous zips/flashes etc., I decided to make a clean adb folder with nothing but this zip/files extracted in it. Low and behold, it worked for me. I believe once, maybe twice the process stopped and I had to manually copy/paste the next command. Maybe something was missed.
Click to expand...
Click to collapse
I actually did try it twice that evening and the same thing happened both times. That was also from a fresh folder.
Kacike27 said:
This happened to me because I did not install the latest firmware. It is because the bootloader is more recent than the firmware you are trying to install. When putting the firmware of February 2018 I have been able to close the bootloader three times, after returning several times to lineageOS.
Click to expand...
Click to collapse
So, I was on LineageOS when I followed your process. Your process includes steps to flash the bootloader and the firmware, which *should* mean the bootloader is the same version as the corresponding firmware (i.e. I didn't skip in any steps in the process that may have allowed a more recent bootloader to remain on my device).
I see from this post (a different, older device, but could very still be relevant), (s)he says
"Make sure you have a fastboot flashable official stock image signed to work with your carrier and region before re-locking the bootloader. Currently running the official firmware is not enough."
Click to expand...
Click to collapse
I wonder if it's also dependent on carrier and/or region. I'm in Canada, maybe there is a slightly modified bootlader for us Canucks or a different bootloader depending on the carrier or purchase location.

Use mfastboot to flash the files instead of fastboot ...check google for difference

I found many ROM for our Albus here:
https://firmware.center/firmware/Motorola/Moto Z2 Play/Stock/
But can't classify them.
My albus is XT 1710-09 in VietNam, so which file is of mine ?

Can you block the bootloader but it did not get Official in the part software status, was Modified got how to make official again?

HeltonMax said:
Can you block the bootloader but it did not get Official in the part software status, was Modified got how to make official again?
Click to expand...
Click to collapse
In my case, software status shows Official with bootloader unlocked.
method in this thread doesn't help me relock bootloader. I think I flash not correct fw for my local. But I cant find anywhere

Working very well in XT710-06 thanks bro.

Working fine on xt-710-07 also (Brazilian unlocked).
The only bug is the NFC is gone. Anyone has a workaround for this?

ogabriel said:
Working fine on xt-710-07 also (Brazilian unlocked).
The only bug is the NFC is gone. Anyone has a workaround for this?
Click to expand...
Click to collapse
I just experienced this after returning to stock from LineageOS, and there was no way I was going to settle for it.
I followed the instructions only omitting the lock and reboot commands.
Flashed TWRP, (twice to be sure), rebooted into recovery, then restored my EFS, Data, and logo. (I think 'Data' is optional, I just didn't want to start over), NFC now works fine again.
I think you always need to restore your EFS.
However, the first time I tried just restoring EFS, after boot/setup, and that didn't work. so I think you have to do it prior to boot.
i imagine you could follow instructions completely, immediately booting into bootloader then use TWRP "Boot" instead of "flash", if your end game is to relock bootloader.

I successfully locked my US variant using following method
Hello,
I can confirm that using following sequence I was able to successfully lock my US variant without loosing IMEI (EFS Partition)
Here is the Stock file I used:
Retail US Stock (ALBUS_C) (ALBUS_NA_CUST) XT1710-01
https://androidfilehost.com/?fid=890129502657596522
Those on Retail channel can perhaps use following stock file
Retail Stock (ALBUS)
https://androidfilehost.com/?fid=890129502657596046
I used mfastbootv2 for my bootloader locking (Google it, easy to find)
Here is the sequence I followed:
Phase-1 (Factory Flashing)
======
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash dsp adspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
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
mfastboot flash oem oem.img
mfastboot erase cache
mfastboot erase userdata
mfastboot erase carrier
mfastboot erase DDR
mfastboot reboot
<<Please note mfastboot erase modemst1 and mfastboot erase modemst2 commands are not being used in the above sequence>>
After reboot I wanted my phone to fully bootup upto "Welcome" screen to ensure I've LTE connectivity with my cellular provider and my IMEI is intact
Once verified, I rebooted the phone into the bootloader,
-While your phone is completely switched off, Hold <Power + Vol Down> button for few seconds to boot phone into the bootloader
Phase-2 (OEM Bootloader Locking)
======
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
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
mfastboot flash system system.img_sparsechunk.7
mfastboot flash boot boot.img
mfastboot oem lock
Following is the final message I got
mfastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.148s]
finished. total time: 0.152s
My phone automatically rebooted once the above sequence was completed
Give it a try at your risk - Best of Luck!!

sevenstar75 said:
Hello,
I can confirm that using following sequence I was able to successfully lock my US variant without loosing IMEI (EFS Partition)
Here is the Stock file I used:
Retail US Stock (ALBUS_C) (ALBUS_NA_CUST) XT1710-01
https://androidfilehost.com/?fid=890129502657596522
Those on Retail channel can perhaps use following stock file
Retail Stock (ALBUS)
https://androidfilehost.com/?fid=890129502657596046
I used mfastbootv2 for my bootloader locking (Google it, easy to find)
<...snip...>
Following is the final message I got
mfastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.148s]
finished. total time: 0.152s
My phone automatically rebooted once the above sequence was completed
Give it a try at your risk - Best of Luck!!
Click to expand...
Click to collapse
I really do appreciate all you guys out there posting your steps to get back to stock and lock the bootloader.
I've literally tried every possible combination of fastboot, mfastboot, mfastbootv2, and all the different variants of ROMs posted. Haha, but it *always* fails for me.
Two things I notice, and I'm not sure if you guys see these or not.
One is that I always "get the (bootloader) Image signed with key bad key" message when I try to flash the boot.img. I'm not sure if that's something you guys get as well?
The other thing is I always see the "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer" message when I run the lock command. @sevenstar75, I notice in your final oem lock command, you don't see this. This makes me think that this is what is different for me. In my developer settings, the OEM Lock toggle is disabled, with a message to the effect of "Bootloader is already unlocked", and I can't change the toggle. This makes sense, as my bootloader IS unlocked, but why don't you see/get that message as well, I wonder?
Here is some sample output of what I'm doing and seeing:
Code:
fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s]
finished. total time: 0.002s
fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.002s
fastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (232923 KB)...
OKAY [ 6.020s]
writing 'oem'...
OKAY [ 3.161s]
finished. total time: 9.181s
fastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262142 KB)...
OKAY [ 6.856s]
writing 'system'...
OKAY [ 4.225s]
sending sparse 'system' (259055 KB)...
OKAY [ 6.732s]
writing 'system'...
OKAY [ 3.632s]
finished. total time: 21.444s
fastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (245604 KB)...
OKAY [ 6.441s]
writing 'system'...
OKAY [ 3.479s]
sending sparse 'system' (240099 KB)...
OKAY [ 6.273s]
writing 'system'...
OKAY [ 3.105s]
sending sparse 'system' (30320 KB)...
OKAY [ 0.800s]
writing 'system'...
OKAY [ 0.414s]
finished. total time: 20.512s
fastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (255375 KB)...
OKAY [ 6.686s]
writing 'system'...
OKAY [ 3.752s]
sending sparse 'system' (258527 KB)...
OKAY [ 6.836s]
writing 'system'...
OKAY [ 4.416s]
finished. total time: 21.690s
fastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 7.145s]
writing 'system'...
OKAY [ 3.449s]
sending sparse 'system' (258973 KB)...
OKAY [ 6.839s]
writing 'system'...
OKAY [ 3.405s]
finished. total time: 20.838s
fastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (261624 KB)...
OKAY [ 6.844s]
writing 'system'...
OKAY [ 3.589s]
sending sparse 'system' (258473 KB)...
OKAY [ 7.094s]
writing 'system'...
OKAY [ 3.587s]
finished. total time: 21.113s
fastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (253898 KB)...
OKAY [ 6.661s]
writing 'system'...
OKAY [ 3.451s]
sending sparse 'system' (262134 KB)...
OKAY [ 6.944s]
writing 'system'...
OKAY [ 4.081s]
sending sparse 'system' (8244 KB)...
OKAY [ 0.231s]
writing 'system'...
OKAY [ 0.160s]
finished. total time: 21.527s
fastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (252681 KB)...
OKAY [ 6.432s]
writing 'system'...
OKAY [ 3.292s]
finished. total time: 9.725s
fastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.448s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.458s]
finished. total time: 0.906s
fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.002s

Hi,
1) What is your variant? I mean XT1710-?? Is that RetUS software channel?
2) Did you toggle Allow OEM Unlocking to "ON" before unlocking your phone?
3) While that toggle currently grayed out, is the toggle - ON or OFF?

Unlocked bootloader but still getting "Partition flashing not allowed"

Phone: Oneplus 3T
Recovery: TWRP 3.3.0-1
OS: LOS 16.0
Flashed a bad emmc_appsboot.mbn and now my phone loops as soon as it gets to the 1+ logo.
Cannot get into recovery.
Can get into fastboot.
Bootloader has been unlocked for years. After getting the "not allowed" error, I did a "fastboot oem unlock" again, successfully.
Code:
$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
$ fastboot flashing unlock
(bootloader) Device already : unlocked!
$ fastboot flashing unlock_critical
(bootloader) Device already : unlocked!
$ fastboot flash recovery twrp-3.3.0-1-oneplus3.img
target reported max download size of 440401920 bytes
erasing 'recovery'...
OKAY [ 0.010s]
sending 'recovery' (27405 KB)...
OKAY [ 0.721s]
writing 'recovery'...
OKAY [ 0.199s]
finished. total time: 0.930s
$ fastboot flash aboot firmware-update/emmc_appsboot.mbn
target reported max download size of 440401920 bytes
sending 'aboot' (1584 KB)...
OKAY [ 0.062s]
writing 'aboot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.082s
$ fastboot flash devcfg firmware-update/devcfg.mbn
target reported max download size of 440401920 bytes
sending 'devcfg' (50 KB)...
OKAY [ 0.038s]
writing 'devcfg'...
FAILED (remote: Partition flashing is not allowed)
Every partition other than recovery gives the "not allowed" error. And flashing the recovery doesn't help.
I'm stumped. I haven't been able to find any other reports online of the same problem, only people with locked bootloaders getting that error.
I know about EDL and I've been working on that angle, but getting fastboot flashing working would be easier.
Ideas? Suggestions?

Can't install TWRP, blocked in fastboot

I tried to install TWRP
fastboot flash a twrp.img
Sending 'a' (39892 KB) OKAY [ 0.929s]
Writing 'a' FAILED (remote: '(a_a) No such partition')
fastboot: error: Command failed
astboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 1.057s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 1.063s
The phone is stuck in fastboot.

I tried this:
c:\TWRP>fastboot flash boot_b twrp.img
target reported max download size of 804261888 bytes
sending 'boot_b' (39892 KB)...
OKAY [ 0.931s]
writing 'boot_b'...
OKAY [ 0.215s]
finished. total time: 1.148s

fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory

fastboot erase userdata
fastboot getvar all
fastboot erase boot
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img
fastboot reboot
I press power Volume Up but the phone boot in Fastboot

you have flashed a bad boot image. if you are on a11 stock i dont think twrp work 100% safe. los recovery is recommended and work without problems

Better Mobile App

welcome