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

Jan 9, 2013
24
3
0
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:
  1. unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
  2. 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
 
Last edited:

doree

Senior Member
Jan 3, 2010
134
51
0
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:
  1. unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
  2. 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
Had the same issue and figured it out:

https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
 

doree

Senior Member
Jan 3, 2010
134
51
0
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?
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.
 

nighteeeeeY

Member
Jun 24, 2013
28
0
0
Sydney/Bielefeld
Last edited:
Jan 9, 2013
24
3
0
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

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.
 
Last edited:

nighteeeeeY

Member
Jun 24, 2013
28
0
0
Sydney/Bielefeld
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
 

doree

Senior Member
Jan 3, 2010
134
51
0
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/)
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.

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

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
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.
 
Last edited:

benzinerwin

Senior Member
May 1, 2008
50
54
0
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
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:
  1. backup everything you can via TWRP...
  2. boot into bootloader (fastboot)
  3. 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
  4. directly boot into (stock) recovery, do not try to boot the system
  5. press and hold down power, then press volume-up, release volume-up, then power.
  6. select 'Apply update from ADB'
  7. 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
 

doree

Senior Member
Jan 3, 2010
134
51
0
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.
 
Last edited:

nighteeeeeY

Member
Jun 24, 2013
28
0
0
Sydney/Bielefeld
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://mega.nz/fm/hqplTQJS
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
 

doree

Senior Member
Jan 3, 2010
134
51
0
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
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.
 
  • Like
Reactions: hackepeterbroetchen
Jan 9, 2013
24
3
0
You didn't account for the line break...;) It should read something like "Blur_Version.25.221.12.griffin.retail.en.US".
I really didn't see that :D

You may want to try this:
  1. backup everything you can via TWRP...
  2. boot into bootloader (fastboot)
  3. 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..)
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
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.
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
 
Last edited:

benzinerwin

Senior Member
May 1, 2008
50
54
0
I really didn't see that :D
I'm getting errors with it (@benzinerwin method):(
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+…
Maybe that worked in the old days :confused: With current bootloader versions only VOL- & power works. But that only gets you into the fastboot mode, from which you can launch recovery...
 
  • Like
Reactions: hackepeterbroetchen

doree

Senior Member
Jan 3, 2010
134
51
0
I really didn't see that :D



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+…
Sorry, I meant VOL-. Typed it in a hurry! :)
 
  • Like
Reactions: hackepeterbroetchen
Jan 9, 2013
24
3
0
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.
 
Last edited:

doree

Senior Member
Jan 3, 2010
134
51
0
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.
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
 
Jan 9, 2013
24
3
0
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
Oh boy! I guess this happened because I skipped coffee today :eek:
@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! :D
Can you recommend any root system for using it with the stock rom?
 
Last edited:

doree

Senior Member
Jan 3, 2010
134
51
0
Oh boy! I guess this happened because I skipped coffee today :eek:
@doree the mobile is booting again. I guess owe you a beer. Thank you so much!
Glad I could help

I guess it isn't possible to go back to the EU rom again for now?
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! :D
Can you recommend any root system for using it with the stock rom?
What do you exactly mean with "root system"?
 
  • Like
Reactions: hackepeterbroetchen