Develop Bugs

Verizon HTC one stuck in bootloader with s-off

I used firewater to unlock and s-off my HTC One with 4.3. Everything went well and I installrd TWRP. I did a back up and when I restarted the phone it said No OS. After trying so many things I ended up, only able to boot into bootloader with no recovery or os and anything I try to send to the phone fails.
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.110s
This is what I get when I try to flash a new recovery.
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9744 KB)...
OKAY [ 1.166s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.326s
Thanks for any in put guys.

Make sure you open command prompt in administrator mode. Try renaming your recovery to recovery.img. And make sure you can see file extensions on your computer. If file extensions are hidden and you add that img at the end,it could really be recovery.img.img.

joeymagnus1 said:
Make sure you open command prompt in administrator mode. Try renaming your recovery to recovery.img. And make sure you can see file extensions on your computer. If file extensions are hidden and you add that img at the end,it could really be recovery.img.img.
Click to expand...
Click to collapse
I tried this and it failed....
C:\platform-tools>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 0
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.057s]
finished. total time: 0.057s
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.150s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.185s
C:\platform-tools>

I got the same errors running as adm... Should I try this? Someone had a similar problem but he was S-On.
Here you guys go. Santod added it to his thread. http://goo.gl/JEkyCk 2.10.605.1 RUU Signed

joeyz400 said:
I used firewater to unlock and s-off my HTC One with 4.3. Everything went well and I installrd TWRP. I did a back up and when I restarted the phone it said No OS. After trying so many things I ended up, only able to boot into bootloader with no recovery or os and anything I try to send to the phone fails.
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.110s
This is what I get when I try to flash a new recovery.
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9744 KB)...
OKAY [ 1.166s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.326s
Thanks for any in put guys.
Click to expand...
Click to collapse
This line: (bootloader) product: m7_wlv indicates that you flashed a Sprint bootloader to the phone. It should say m7_vzw. The Sprint model has different mount points, so that could explain the error.

NotATreoFan said:
This line: (bootloader) product: m7_wlv indicates that you flashed a Sprint bootloader to the phone. It should say m7_vzw. The Sprint model has different mount points, so that could explain the error.
Click to expand...
Click to collapse
I must have messed something up when I was still able to get into recovery, I wasn't able to flash anything. I kept getting E: drive errors so I flashed a stock recovery.... that is when I lost Twrp and only bootloops into boot loader with no OS.
I just tried flashing openrecovery-twrp-2.6.3.3-m7.img and got the same errors....
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.152s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.190s
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 4.911s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 5.090s
C:\platform-tools>

joeyz400 said:
I must have messed something up when I was still able to get into recovery, I wasn't able to flash anything. I kept getting E: drive errors so I flashed a stock recovery.... that is when I lost Twrp and only bootloops into boot loader with no OS.
I just tried flashing openrecovery-twrp-2.6.3.3-m7.img and got the same errors....
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.152s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.190s
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 4.911s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 5.090s
C:\platform-tools>
Click to expand...
Click to collapse
If you have stock recovery on the phone now, try using ADB Sideload to push the stock, rooted 4.4.2 ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
If that works for you, then try pushing TWRP 2.6.3.4.

Will that relock my bootloader and make it S-On? I was on stock 4.3 before I started everything.
NotATreoFan said:
If you have stock recovery on the phone now, try using ADB Sideload to push the stock, rooted 4.4.2 ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
If that works for you, then try pushing TWRP 2.6.3.4.
Click to expand...
Click to collapse

joeyz400 said:
Will that relock my bootloader and make it S-On? I was on stock 4.3 before I started everything.
Click to expand...
Click to collapse
No. But you will also need to flash the latest firmware package from that thread. It also does not affect S-Off, so don't worry.

Seems my bootloader is corrupt... Is there anyway to wipe it clean to start over?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\platform-tools
C:\platform-tools>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 0
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.059s]
finished. total time: 0.059s
C:\platform-tools>

I tried flashing the stock recovery and got this error:
C:\platform-tools>fastboot flash recovery 1.10.605.10_recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (16383 KB)...
OKAY [ 1.793s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.953s
C:\platform-tools>

I just tried this...... FAIL
C:\platform-tools>fastboot flash RUU RUU_M7_WL_JB43_SENSE50_VZW_MR_VERIZON_WWE_2
.10.605.1_Radio_1.12.41.1112_2_NV_VZW_3.71_002_release_341019_signed_2.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1232586 KB)...
OKAY [ 41.968s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 42.006s
C:\platform-tools>

joeyz400 said:
I just tried this...... FAIL
C:\platform-tools>fastboot flash RUU RUU_M7_WL_JB43_SENSE50_VZW_MR_VERIZON_WWE_2
.10.605.1_Radio_1.12.41.1112_2_NV_VZW_3.71_002_release_341019_signed_2.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1232586 KB)...
OKAY [ 41.968s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 42.006s
C:\platform-tools>
Click to expand...
Click to collapse
Is this the encrypted RUU? If so, you may need the decrypted one. Or vice versa.
Sent from my HTC6500LVW using Tapatalk

This is my latest attempt... FAIL***** Am I doing something wrong?
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno: 12345678****
(bootloader) imei: 99000428262****
(bootloader) meid: 9900042826****
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4074mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.113s
C:\platform-tools>fastboot flash recovery PN07IMG_M7_WL_JB_50_VZW_1.10.605.10_DE
CRYPT.zip
target reported max download size of 1526722560 bytes
sending 'recovery' (1178304 KB)...
OKAY [ 40.982s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 41.018s
C:\platform-tools>fastboot flash RUU PN07IMG_M7_WL_JB_50_VZW_1.10.605.10_DECRYPT
.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1178304 KB)...
OKAY [107.432s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 107.468s
C:\platform-tools>

you are doing more than I can do right now. how did you get the sdk bundle to work?

I had it working before things went wrong. If you are on windows 8 people have problems so search that if that is your OS. I'm running Windows 7 on my PC. I had Unlocked S-Off and rooted with TWRP 2.6.3.3 installed. Everything was working till I did my first back up. When I restarted my phone it said there was no OS installed and the bootloops started but I still had recovery. But I couldn't restore my backup. Now I can only boot into bootloader with no OS or Recovery. Search how to set up SDK and ADB for your OS and take it from there. I am stumped because I cant run any RUU's, all I get are errors. Good luck.

I don't have my SIM card installed. Does that matter?

joeyz400 said:
I don't have my SIM card installed. Does that matter?[/QUOTE
]that shouldn't matter
Click to expand...
Click to collapse

If I fried something can the part be bought and replaced?
Jamesdbritt said:
joeyz400 said:
I don't have my SIM card installed. Does that matter?[/QUOTE
]that shouldn't matter
Click to expand...
Click to collapse
Click to expand...
Click to collapse

I gave up... I'm sending the phone to MobileTechVideos.COM they say they can repair it for $60. Thanks for all your help. Has anyone heard of their service to repair bricked phones using Riff Jtag tools?

Moto g5 cedric xt1676 blankflash needed urgently

Please i am in urgent need of moto g5 cedric blankflash to revive my hardbricked device. Thank you

Can you tell me what happened at first so that me and others avoid what you did?

ap4ss3rby said:
Can you tell me what happened at first so that me and others avoid what you did?
Click to expand...
Click to collapse
I flashed a wrong rom

Which rom? How did u make this ?

Hi! I'm in a similar situation here! I wanted to flash a retail firmware of the XT1676 for my little brother's phone, he just forgot to tell me he had just updated it and so the firmware/rom I flashed was an old update (dating back to February if I'm correct) and it bricked, I managed to access TWRP (I have unlocked the bootloader yesterday and I booted the file) and to push a custom rom (ViperOS) but it cannot access any network outside of Wifi.
I can access the bootloader, but since pushing the custom rom to the phone, I cannot flash or boot TWRP.
When I try to flash via flashboot the lastest firmware I have found, it just says "
fastboot flash partition gpt.bin
target max-sparse-size: 256MB
error: cannot load 'gpt.bin': No error
fastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
error: cannot load 'bootloader.img': No error" and on and on with every file.
I also messed up by trying in a last resort to repair the partition data, system and cache in TWRP and it changed data & cache from f2fs to ext4 and I don't know if that's a part of the same issue here.
My brother is currently freaking out since he has had the phone for only 2 months but all the apps that bloated the phone made him ask me to do this.
If anyone can create or find the blankflash or just help me or OP, that would be neat.
Sincerely and desperately, Thibziboy

slowflamez said:
I flashed a wrong rom
Click to expand...
Click to collapse
How did you flash it? (Zip through recovery or using fastboot)
If you did it using the recovery you should still be able to acces recovery (or flash one with fastboot) ...

Someone should help urgently! its very important cos virtually all users who tried to update or downgrade their devices got a hard bricked device as the end result. Please don't let this devices useless in our hands. Thanks

tyty48 said:
Hi! I'm in a similar situation here! I wanted to flash a retail firmware of the XT1676 for my little brother's phone, he just forgot to tell me he had just updated it and so the firmware/rom I flashed was an old update (dating back to February if I'm correct) and it bricked, I managed to access TWRP (I have unlocked the bootloader yesterday and I booted the file) and to push a custom rom (ViperOS) but it cannot access any network outside of Wifi.
I can access the bootloader, but since pushing the custom rom to the phone, I cannot flash or boot TWRP.
When I try to flash via flashboot the lastest firmware I have found, it just says "
fastboot flash partition gpt.bin
target max-sparse-size: 256MB
error: cannot load 'gpt.bin': No error
fastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
error: cannot load 'bootloader.img': No error" and on and on with every file.
I also messed up by trying in a last resort to repair the partition data, system and cache in TWRP and it changed data & cache from f2fs to ext4 and I don't know if that's a part of the same issue here.
My brother is currently freaking out since he has had the phone for only 2 months but all the apps that bloated the phone made him ask me to do this.
If anyone can create or find the blankflash or just help me or OP, that would be neat.
Sincerely and desperately, Thibziboy
Click to expand...
Click to collapse
Just flash without GPT and Bootloader. Tried it.
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
slowflamez said:
Someone should help urgently! its very important cos virtually all users who tried to update or downgrade their devices got a hard bricked device as the end result. Please don't let this devices useless in our hands. Thanks
Click to expand...
Click to collapse
Contact Moto using the livechat. Just tell the truth

Hey! I just tried it, it failed... here's the log it gave me:
C:\WINDOWS\system32>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
error: cannot load 'logo.bin': No error
C:\WINDOWS\system32>mfastboot flash boot boot.img
target max-sparse-size: 256MB
error: cannot load 'boot.img': No error
C:\WINDOWS\system32>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
error: cannot load 'recovery.img': No error
C:\WINDOWS\system32>mfastboot flash dsp adspso.bin
target max-sparse-size: 256MB
error: cannot load 'adspso.bin': No error
C:\WINDOWS\system32>mfastboot flash oem oem.img
target max-sparse-size: 256MB
error: cannot load 'oem.img': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.1': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.2': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.3': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.4': No error
C:\WINDOWS\system32>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
error: cannot load 'NON-HLOS.bin': No error
C:\WINDOWS\system32>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.037s]
finished. total time: 0.039s
C:\WINDOWS\system32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.037s]
finished. total time: 0.039s
C:\WINDOWS\system32>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
error: cannot load 'fsg.mbn': No error
C:\WINDOWS\system32>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
C:\WINDOWS\system32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.074s
C:\WINDOWS\system32>mfastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
C:\WINDOWS\system32>mfastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
Click to expand...
Click to collapse
I don't know if it can help, but I sent a getvar all to the phone and this came out:
C:\WINDOWS\system32>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.23
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3224V2KT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: E7437CF900000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: eio
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351865087161254
(bootloader) meid:
(bootloader) date: 06-08-2017
(bootloader) sku: XT1676
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0:17:20 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPP25.1
(bootloader) ro.build.fingerprint[1]: 37-33/31:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.31.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g7d1eb92 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Mon Feb 6 19:00:09 CST
(bootloader) kernel.version[3]: 2017
(bootloader) sbl1.git: git=MBM-NG-VB8.23-0-g2cafa24
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) devcfg.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) keymaster.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) cmnlib.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) prov.git: git=MBM-NG-VB8.09-0-g1a41aff
(bootloader) aboot.git: git=MBM-NG-VB8.23-0-g8fcce1f
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
Click to expand...
Click to collapse

tyty48 said:
Hey! I just tried it, it failed... here's the log it gave me:
I don't know if it can help, but I sent a getvar all to the phone and this came out:
Click to expand...
Click to collapse
What is a getvar please and how can I get it?

slowflamez said:
What is a getvar please and how can I get it?
Click to expand...
Click to collapse
It's a fastboot command
Look at how he typed it in on the command prompt with the resulting output in his post
Requires you to have fastboot setup - in his case he was using mfastboot from Motorola although the standard fastboot will probably have the same result

TheFixItMan said:
It's a fastboot command
Look at how he typed it in on the command prompt with the resulting output in his post
Requires you to have fastboot setup - in his case he was using mfastboot from Motorola although the standard fastboot will probably have the same result
Click to expand...
Click to collapse
Kindly send the commands..Please

slowflamez said:
Kindly send the commands..Please
Click to expand...
Click to collapse
Like I said - the commands are in the post that he wrote! Have you read that post and looked at what commands were typed to generate that output?
It was
mfastboot getvar all

Still no solution?

[Q] How do I reinstall or re-flash partitions on my XT1922-3

Hi there,
My XT1922-3 had a problem on stock ROM whereby the cell radio wasn't working, (no signal, so couldn't make calls or send SMS texts) so I unlocked the bootloader and installed TWRP and installed a custom firmware (unfortunately I'm not sure which one now) and it all worked fine (I wish I'd left it like that) but I wanted it back to stock ROM to sell on. So I followed a YouTube guide called 'Moto G6/G6+/G6 Play Unroot | Unbrick |Flash Stock Firmware' which got the stock ROM back, but the no signal issues also returned.
I have since flashed another custom ROM but now I seem to have lost the partitions, as I get "(bootloader) is-logical:bootloader: not found" and the same for other partitions when flashing via fastboot.
I've managed to get TWRP back into the recovery partition, so presumably that is still there but it seems to be missing some options and is not able to mount partitions.
If anyone has a link to the correct and latest stock firmware ROM or a way of re-creating the partitions I would grateful, or if there is a custom kernel or ROM that I can use to get it working again. I am in the United Kingdom and I think some of the ROMs don't seem to be for the UK.
Here is my phone's current info from fatboot getvar all:-
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-e4c1135-190328
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZL62223QNV
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 02DD3E7E00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351844090727492
(bootloader) meid:
(bootloader) date: 05-06-2018
(bootloader) sku: XT1922-3
(bootloader) carrier_sku: XT1922-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 26 15:19: 6 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:8.0.0/OPP
(bootloader) ro.build.fingerprint[1]: 27.61-14-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.4.aljeter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8937_13.423.05.35R JETER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g74a113b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed Feb 28 03:33:30 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-0d2031d-190328
(bootloader) rpm.git: MBM-2.1-aljeter_retail-af31f6a-190328
(bootloader) tz.git: MBM-2.1-aljeter_retail-4636043-190328
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-4636043-190328
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-4636043-190328
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-4636043-190328
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-4636043-190328
(bootloader) prov.git: MBM-2.1-aljeter_retail-4636043-190328
(bootloader) aboot.git: MBM-2.1-aljeter_retail-e4c1135-190328
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown

If it's Aljeter retail, use Aljeter retail firmware. It's easiest to flash with RSDlite. You can use fastboot if you like. Just open the flashfile XML and copy the commands from it for fastboot.
https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/

madbat99 said:
If it's Aljeter retail, use Aljeter retail firmware. It's easiest to flash with RSDlite. You can use fastboot if you like. Just open the flashfile XML and copy the commands from it for fastboot.
https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/
Click to expand...
Click to collapse
Thanks madbat99, unfortunately RSDlite 6.2.4 won't show my device, so I've tried the following in fastboot:-
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.165s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.100s]
Finished. Total time: 0.345s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (7483 KB) OKAY [ 0.404s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.697s]
Finished. Total time: 2.590s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (59660 KB) OKAY [ 2.117s]
Writing 'modem' OKAY [ 0.740s]
Finished. Total time: 3.692s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (5984 KB) OKAY [ 0.376s]
Writing 'fsg' OKAY [ 0.140s]
Finished. Total time: 0.829s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
fastboot: error: cannot load 'dspso.bin': No such file or directory
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.684s]
Writing 'dsp' OKAY [ 0.274s]
Finished. Total time: 1.305s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.651s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.359s]
Finished. Total time: 1.471s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (523263 KB) OKAY [ 19.751s]
Writing 'system' OKAY [ 6.352s]
Finished. Total time: 36.205s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (522607 KB) OKAY [ 17.476s]
Writing 'system' OKAY [ 6.597s]
Finished. Total time: 31.190s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (461122 KB) OKAY [ 15.294s]
Writing 'system' OKAY [ 5.255s]
Finished. Total time: 26.227s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (515436 KB) OKAY [ 17.054s]
Writing 'system' OKAY [ 5.785s]
Finished. Total time: 28.917s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (173989 KB) OKAY [ 5.872s]
Writing 'system' OKAY [ 2.526s]
Finished. Total time: 10.873s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (108561 KB) OKAY [ 3.720s]
Writing 'oem' OKAY [ 1.303s]
Finished. Total time: 6.731s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
(bootloader) is-logical:vendor: not found
Sending 'vendor' (252387 KB) OKAY [ 8.479s]
Writing 'vendor' OKAY [ 3.160s]
Finished. Total time: 15.483s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot erase carrier
Erasing 'carrier' OKAY [ 0.068s]
Finished. Total time: 0.080s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.100s]
Finished. Total time: 0.112s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot erase DDR
Erasing 'DDR' OKAY [ 0.004s]
Finished. Total time: 0.016s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (1423 KB) OKAY [ 0.209s]
Writing 'logo' OKAY [ 0.084s]
Finished. Total time: 0.461s
C:\Users\angie\Desktop\Moto\Minimal ADB and Fastboot>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.008s
Which just boots into bootloader mode, however clicked 'start' and it has booted up properly now and I have signal again. Thanks so much.
Now, is there a way I unroot it and relock the oem bootloader so I don't get the "bad key" warning screen before the Moto screen, so I can sell it on?

@Motorocker
If you flashed the boot.img and recovery.img from the stock firmware, you shouldn't be rooted anymore. I wouldn't lock the bootloader. It's not a big deal and can cause problems if a flash goes bad.

Help
my bike g6 play was without a partition could also help me?
C:\9>fastboot flash partition gpt.bin
< waiting for device >
sending 'partition' (45 KB)... OKAY [ 0.005s]
writing 'partition'... INFOValidating 'gpt.default.xml'
INFOImage primary_gpt failed validation
INFOPreflash validation failed
INFOCancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.044s
C:\9>fastboot flash partition gpt.bin
sending 'partition' (45 KB)... OKAY [ 0.006s]
writing 'partition'... INFOValidating 'gpt.default.xml'
INFOImage primary_gpt failed validation
INFOPreflash validation failed
INFOCancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.043s
C:\9>fastboot flash bootloader bootloader.img
sending 'bootloader' (7483 KB)... OKAY [ 0.627s]
writing 'bootloader'... INFOValidating 'bootloader.default.xml'
INFOInvalid partition name aboot
INFOInvalid partition name rpm
INFOInvalid partition name tz
INFOInvalid partition name devcfg
INFOInvalid partition name cmnlib
INFOInvalid partition name cmnlib64
INFOInvalid partition name keymaster
INFOInvalid partition name prov
INFOInvalid partition name sbl1
INFOCancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.715s
C:\9>fastboot flash modem NON-HLOS.bin
sending 'modem' (59664 KB)... OKAY [ 4.499s]
writing 'modem'... INFOInvalid partition name modem
FAILED (remote failure)
finished. total time: 4.501s
C:\9>fastboot flash fsg fsg.mbn
sending 'fsg' (5984 KB)... OKAY [ 0.416s]
writing 'fsg'... INFOInvalid partition name fsg
FAILED (remote failure)
finished. total time: 0.418s
C:\9>fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin'
C:\9>fastboot flash dsp adspso.bin
sending 'dsp' (16384 KB)... OKAY [ 1.318s]
writing 'dsp'... INFOInvalid partition name dsp
FAILED (remote failure)
finished. total time: 1.321s
C:\9>fastboot flash boot boot.img
sending 'boot' (16384 KB)... OKAY [ 1.345s]
writing 'boot'... INFOInvalid partition name boot
FAILED (remote failure)
finished. total time: 1.348s
C:\9>fastboot flash system system.img_sparsechunk.0
sending 'system' (475777 KB)... OKAY [ 34.828s]
writing 'system'... INFOInvalid partition name system
FAILED (remote failure)
finished. total time: 34.830s
C:\9>fastboot flash system system.img_sparsechunk.1
sending 'system' (499282 KB)... OKAY [ 38.910s]
writing 'system'... INFOInvalid partition name system
FAILED (remote failure)
finished. total time: 38.914s
C:\9>fastboot flash system system.img_sparsechunk.2
sending 'system' (474682 KB)... OKAY [ 33.479s]
writing 'system'... INFOInvalid partition name system
FAILED (remote failure)
finished. total time: 33.482s
C:\9>fastboot flash system system.img_sparsechunk.3
sending 'system' (476300 KB)... OKAY [ 37.698s]
writing 'system'... INFOInvalid partition name system
FAILED (remote failure)
finished. total time: 37.701s
C:\9>fastboot flash system system.img_sparsechunk.4
sending 'system' (270349 KB)... OKAY [ 21.270s]
writing 'system'... INFOInvalid partition name system
FAILED (remote failure)
finished. total time: 21.272s
C:\9>fastboot flash oem oem.img
sending 'oem' (188470 KB)... OKAY [ 14.180s]
writing 'oem'... INFOInvalid partition name oem
FAILED (remote failure)
finished. total time: 14.182s
C:\9>fastboot flash vendor vendor.img
sending 'vendor' (252387 KB)... OKAY [ 19.033s]
writing 'vendor'... INFOInvalid partition name vendor
FAILED (remote failure)
finished. total time: 19.035s
C:\9>fastboot erase carrier
erasing 'carrier'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.004s
C:\9>fastboot erase userdata
erasing 'userdata'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.002s
C:\9>fastboot erase DDR
erasing 'DDR'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.003s
C:\9>fastboot flash logo logo.bin
sending 'logo' (1423 KB)... OKAY [ 0.092s]
writing 'logo'... INFOInvalid partition name logo
FAILED (remote failure)
finished. total time: 0.095s
C:\9>fastboot reboot
rebooting...
finished. total time: 0.002s

Diego Davi said:
my bike g6 play was without a partition could also help me?
Click to expand...
Click to collapse
I just downloaded the following RETAIL ROM from mirrors . lolinet . com /firmware/moto/aljeter/official/ (remove the spaces, as I can't post links yet)
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
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 boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.

please give me offiicial rom
(bootloader) version: 0 . 5
(bootloader) version-bootloader: MBM-2 . 1-aljeter_retail-b1f322d-191127
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZL522265N2
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 5FC3428700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 35552709152xxxx
(bootloader) meid:
(bootloader) date: 06-08-2018
(bootloader) sku: XT1922-10
(bootloader) carrier_sku: XT1922-10
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Mar 5 10: 2:54 UTC 2020"
(bootloader) ro . build . fingerprint[0]: motorola/aljeter/aljeter:9/PPP29 . 5
(bootloader) ro . build . fingerprint[1]: 5-35-18/f7946:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro . build . version . full[0]: Blur_Version . 29 . 301 . 33 . aljeter . re
(bootloader) ro . build . version . full[1]: tail . en . US
(bootloader) ro . build . version . qcom: LA . UM . 7 . 6 . r1-03700-89xx . 0
(bootloader) version-baseband: M8937_34 . 42 . 05 . 97Z JETER_INDIADSDS_CUST
(bootloader) kernel . version[0]: Linux version 3 . 18 . 120-perf-g3e480e1-042
(bootloader) kernel . version[1]: 56-gd43db30 ([email protected]) (gcc v
(bootloader) kernel . version[2]: ersion 4 . 9 . x 20150123 (prerelease) (GCC)
(bootloader) kernel . version[3]: ) #1 SMP PREEMPT Wed Nov 27 09:41:39 CS
(bootloader) kernel . version[4]: T 2019
(bootloader) sbl1 . git: MBM-2 . 1-aljeter_retail-0d2031d-191127
(bootloader) rpm . git: MBM-2 . 1-aljeter_retail-af31f6a-191127
(bootloader) tz . git: MBM-2 . 1-aljeter_retail-5bf0857-191127
(bootloader) devcfg . git: MBM-2 . 1-aljeter_retail-5bf0857-191127
(bootloader) keymaster . git: MBM-2 . 1-aljeter_retail-5bf0857-191127
(bootloader) cmnlib . git: MBM-2 . 1-aljeter_retail-5bf0857-191127
(bootloader) cmnlib64 . git: MBM-2 . 1-aljeter_retail-5bf0857-191127
(bootloader) prov . git: MBM-2 . 1-aljeter_retail-5bf0857-191127
(bootloader) aboot . git: MBM-2 . 1-aljeter_retail-b1f322d-191127
(bootloader) frp-state: protected (77)
(bootloader) ro . carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished . total time: 0 . 215s
i need official stock rom please sugest me

De-Bricking Support and Questions for my XT1789-06

Hi,
I am stuck, and figured I need to ask you guys some questions.
As I have done previously with other phones, I bought a used Moto Z2 Force to fix up. I bought a bricked phone with no hardware problems. The previous user said he updated it in Stock to Android Pie, and after the update the phone wouldnt boot anymore, so he sold it. I figured I would just debrick it and use it with LineageOS.
But I didnt succeed, and dont know what else to try, so Im asking you.
It is a XT-1789-06 bought in Germany.
So: When I start the phone up, it says: "Your device is corrupt. it cant be trusted and will not boot." and that I should turn to the official Motorola unlocking portal.
I did that, followed the instructions, was able to boot into fastboot mode, and got the Code, and with that the one from motorola, but when I try the
Code:
fastboot oem unlock XXXXXXXXXXXXXX
I get the following:
Code:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.008s]
finished. total time: 0.008s
Obviously I cant do that, because the phone wont boot up. But event though it says OKAY, there is no change to the variable: securestate: flashing_locked, and i still cant flash anything, and the startup error remains the same. When I try "fastboot flashing unlock" I get the same message.
So, the next thing I tried was the LMSA software. It did the Flash-> rescue-> choose model XT1789-06 -> and flash, and it downloaded the NASH_PPX29.159_23_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip ROM, and apparently did something to the phone, but it didnt change the outcome, still the phone shows the same error on bootup.
Then I did a fastboot -w, after which the phone didnt show anything anymore on bootup, just blank screen, and the tried both steps described above again, stil no change.
Then I tried to boot into the newest Twrp image with "fastboot boot twrp.....img" but it fails with the error: too many links.
Then I tried all of the above in Ubuntu, then on windows with the fastboot files given in the guide in this forum, and then with the mfastboot, that I found somewhere else. Same outcome.
Then I tried just flashing the Stockrom that LMSA downloaded with the flashall method from the same guide, but flashing fails with: Permission denied.
So, do you have any ideas what more I can try to unbrick this phone? I will be happy to give you any further information. I will append fastboot getvar all as soon as I reboot my PC in 2 min.
Edit:
Code:
F:\motoz2force>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4120
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NE
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2
(bootloader) kernel.version[1]: [email protected]) (gcc version 4
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:prov: MBM-3.0-nash_retail-22c9393-190327
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 1
all: listed above
finished. total time: 0.177s
Edit 2: While I can boot into fastboot mode, when I try to start recovery mode from there, I get the same "Your device is corrupt", so no adb for me.
Edit3:
"fastboot -w" results in:
Code:
F:\motoz2force>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.012s

It's odd that it says 'a' is unbootable, most updates and roms usually go to 'b' so if there was trouble I'd expect it to be on 'b' slot.. Anyways, it's possible that the chain of trust is corrupt and you can try to blankflash to remedy that and hopefully be able to flash (even with a locked bootloader). You can follow this guide to try and blankflash, if successful then you can try to flash your firmware again. *Note - with a locked bootloader you can only flash the same firmware or newer, that means you should try the one that was downloaded by lmsa. Also, look by your charger port to verify that it is indeed an -06 variant and not just saying -06 because that was what was flashed.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
If no success all around, you can try switching slots and making 'a' the active slot. Once it is active, try to boot it and see if it will, if not, try flashing the firmware you have on that slot.

Thank you for your help. Unfortunatley it didnt get me very far. I installed the drivers on my Vista-PC. When I executed the blank-flash.bat It just said <waiting for device>. Then I removed Motorola and te qualcomm drivers, rebooted, installed the qualcomm-drivers again, rebooted, but then in the device manager the phone just showed up as "Fastboot nash S" without proper drivers. I couldnt get the qualcomm drivers to recognize the device. blank-flash.bat still showed the same thing.
Other ports, same behaviour.
Then I reinstalled moto drivers to test the other commands.
When I tried "fastboot oem blankflash" I got:
Code:
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.005s
Then I tried
Code:
F:\motoz2force>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.008s
I checked next to the charging port, it is really a XT1789-06.
Stuck again. Any other pointers? that would be so great. thanks in advance. I am still learning a lot here, even without progress.

I'm in the same situation, but with an xt1789-05, but it turns on normal, but I don't have Wi-Fi and no data network, and I've tried everything to remove the OEM lock, but without success, and whenever I try a ROM new, it gives me bootloader failure or error.

I'm sure your command to set the other slot is wrong fastboot --set-active=a
As for the blankflash, you need to be in edl mode which isn't always the easiest to get into manually and it's even harder when your system is jumbled. (You think it would be easier since that's when you need it). Either way, that's why blankflash isn't running.

When I wanted to get into edl mode I was holding volume up+power while connecting USB to PC.

OK, thanks for your further tips.
So my goal is to get the phone into edl/blankflash mode, correct?
I would consider myself successful if theres a device showing up in the windows device manager thats called "Qualcomm HS-USB QDLoader 9008" or something similar, correct? Alternatively if the QFIL-Tools recognizes a port.
What I tried:
"fastboot oem blankflash" in fastboot mode, unsuccessful, results shown in a previous post.
Pressing Volume up + power while plugging the phone in, nothing happens.
And I even tried this: https://www.youtube.com/watch?v=DexLELi04XY, but nothing happens, neither the phone showing anything, nor the PC recognizing any device.
... to bad.
I tried to follow this Guide: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/ , but when I try to set the variables in the admin terminal for the first step, it says (translated) "The storage for the startup-configuration files could not be opened. The system could not find the files."
I am close to giving up here. A shame, I really had my hopes up, but I am kind of out of my league here.

You should try running the lmsa tool again. Were you ever successful in switching slots? If you're unsure of the syntax, type fastboot --help that should show you the proper way. Blankflash should be your last option.

wolzotan said:
OK, thanks for your further tips.
So my goal is to get the phone into edl/blankflash mode, correct?
I would consider myself successful if theres a device showing up in the windows device manager thats called "Qualcomm HS-USB QDLoader 9008" or something similar, correct? Alternatively if the QFIL-Tools recognizes a port.
What I tried:
"fastboot oem blankflash" in fastboot mode, unsuccessful, results shown in a previous post.
Pressing Volume up + power while plugging the phone in, nothing happens.
And I even tried this: https://www.youtube.com/watch?v=DexLELi04XY, but nothing happens, neither the phone showing anything, nor the PC recognizing any device.
... to bad.
I tried to follow this Guide: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/ , but when I try to set the variables in the admin terminal for the first step, it says (translated) "The storage for the startup-configuration files could not be opened. The system could not find the files."
I am close to giving up here. A shame, I really had my hopes up, but I am kind of out of my league here.
Click to expand...
Click to collapse
Hi There I have same situation as you, did you fix your phone?
and how you fixed your phone?
I have XT1789-05, please help me, thanks a lot

hi AHMN48, i saw your posts around and figured you have the same problem. I have not yet found a solution unfortunately.
I have tried some more suggestions made here:
Code:
F:\motoz2force>fastboot --set_active=_a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
Code:
F:\motoz2force>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
Code:
F:\motoz2force>fastboot reboot emergency
rebooting into emergency download (EDL) mode...
OKAY [ 0.000s]
finished. total time: 0.000s
I got really excited when that happened, but it just came up in fastboot mode again.
this is my screen, if it helps anything
and I tried those commands on all of my usb ports, and most of the ports on my docking station. Its a Lenovo W520, and I have windows 7 and Ubuntu 18.04 available.

Anyways, the only thing I can do to the phone that apparently does something ist the rescue-flash with LMSA. When I do that, It shows the whole "Your device is corrupt"-Thing, and the yellow line from the fastboot screen linked above that says "Software status: modified" vanished. This line reappears as soon as I try to send any of the above fastboot commands, be it the slo-switching-thing or "fastboot -w", doesnt matter. As soon as this happens, the phone also doesnt show the "Your device is corrupt"-alert anymore too, just a black screen. then I rescue flash with LMSA again, and so on.
I tried RSD lite, and it recognizes a device called "fastboot nash S" and status "connected...", but when I try to flash anything, it tells me: "The phone failed to switch to fastboot mode" even though it still is in fastboot mode from the beginning. But Im also not sure if Im doing it right, because i dont know which of the decompressed files from the stock-rom Im supposed to choose for a flashfile

wolzotan said:
Anyways, the only thing I can do to the phone that apparently does something ist the rescue-flash with LMSA. When I do that, It shows the whole "Your device is corrupt"-Thing, and the yellow line from the fastboot screen linked above that says "Software status: modified" vanished. This line reappears as soon as I try to send any of the above fastboot commands, be it the slo-switching-thing or "fastboot -w", doesnt matter. As soon as this happens, the phone also doesnt show the "Your device is corrupt"-alert anymore too, just a black screen. then I rescue flash with LMSA again, and so on.
I tried RSD lite, and it recognizes a device called "fastboot nash S" and status "connected...", but when I try to flash anything, it tells me: "The phone failed to switch to fastboot mode" even though it still is in fastboot mode from the beginning. But Im also not sure if Im doing it right, because i dont know which of the decompressed files from the stock-rom Im supposed to choose for a flashfile
Click to expand...
Click to collapse
RSD is a bit antiquated and we use a flashall.bat in the command prompt to do the same thing. In your OP you posted your getvar output and it looks like it still has oreo on it. Whether lmsa has actually done anything and flashed pie, it would appear not according to you. Run fastboot getvar all again and look at your build fingerprint, if it is still oreo 8.0 then lets try flashing the last oreo version instead of trying to jump to pie.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

ok. Thanks so much 41rw4lk, for walking me through this. Still no luck unfortunately.
I ran the following commands on a new laptop, new windows 10, that I hadnt tried before. However the outcome was identical, as far as i see.
I did download the firmware you linked. I ran the preparation.bat, and then the flashfile.bat. this is the log. It shows the same error messages, that I got with the Pie firmware.
Code:
max-sparse-size: 268435456
finished. total time: 0.000s
...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.234s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.656s
target reported max download size of 536870912 bytes
sending 'modem_a' (97411 KB)...
OKAY [ 6.896s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.896s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.297s]
writing 'fsg_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.312s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.219s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.234s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.828s]
writing 'dsp_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.844s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.172s]
writing 'logo_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.187s
target reported max download size of 536870912 bytes
sending 'boot_a' (23353 KB)...
OKAY [ 1.172s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.172s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 30.593s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 30.608s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 26.218s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 26.233s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 25.927s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 25.927s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 126.811s
target didn't report max-download-size
sending 'system' (523200 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'system' (413555 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target didn't report max-download-size
sending 'system_b' (515182 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target didn't report max-download-size
sending 'system_b' (319593 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'oem' (163061 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.000s
erasing 'carrier'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.000s
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'ddr'...
FAILED (command write failed (No error))
finished. total time: 0.000s
target didn't report max-download-size
sending 'fsg' (5600 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.270s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.290s
...
OKAY [ -0.000s]
finished. total time: -0.000s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
And then a current flashboot getvar all:
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3922
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.147s
It seems at some point some command was successful in switching the slots. Strange... I am really fishing in the dark here.
Still the Phone says: Device corrupted, and to unlock the bootloader, and when I try t unlock the bootloader in fastboot, it still tells me to check "OEM Unlocking" in the developer options.

You won't be able to unlock the bootloader until you're able to boot, sign in, and enable oem unlocking in dev options. Since it changed a few things around, try running the lmsa tool again.

NOthing new here. Ran LMSA again, it says "flash successful", but on reboot: "Device corrupt, wont boot, unlock bootloader". Then I tried "fastboot -w", but it showed the same results again as above. Then again LMSA, same behaviour again.
I think Ill just try to sell this thing again.
What kind of stupid error message is this? I shall unlock the bootloader because its bricked, but I have to boot it into OEM to unlock the bootloader?

wolzotan said:
NOthing new here. Ran LMSA again, it says "flash successful", but on reboot: "Device corrupt, wont boot, unlock bootloader". Then I tried "fastboot -w", but it showed the same results again as above. Then again LMSA, same behaviour again.
I think Ill just try to sell this thing again.
What kind of stupid error message is this? I shall unlock the bootloader because its bricked, but I have to boot it into OEM to unlock the bootloader?
Click to expand...
Click to collapse
Make sure you're running lmsa and such as an admin, some users depending on their pc have had to pay attention to this, while most don't.

Yeah I did that.

XT1710 Z² Play Dual Chip CID: 0xDEAD after system update

Greetings!
I have a Moto Z² Play Dual Chip (XT1710) which has been recently updated to Pie and right after it, it started presenting several issues (restarts, freezes, etc.) and then, 3 days ago, it simply didn't enter the system anymore. It loops on fastboot and it presents a huge number of errors whatever I try to do - and I've tried a lot.
On AP Fastboot Flash Mode (Secure) screen, it shows the following information:
BL: MBM-2.1-albus_retail-b625135-190911
Baseband:
Product/Variant: albus 000000000000000 64GB P4
Serial number: a8d9e088
CPU: MSM8953
eMMC: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=000000000000007
DRAM: 4GM SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
oem_locked
Transfer Mode: USB Connected
If I select any option from the fastboot menu (Recovery, Start, BP tools, Qcom, Factory), I get a "Start Up Failed" and the following message:
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.
and
AP Fastboot Flash Mode (Secure)
Fastboot reason: Last time flashing failed
USB connected
failed to validate boot (or recovery) image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
I can switch tools mode on and if I select barcodes, it shows only zeros for IMEI and SKU.
Based on the message displayed on the startup failure, I downloaded Lenovo Moto Smart Assistant and selected Rescue. When I select the device's model it shows a message saying: "Information you input does not match connected device. Your device is [000000000000000]. Want to use it?" and the only option offered is to Apply delected info, which leads to a "Doesn't match the appropriate firmware. You can try to select a firmware by yourself manually.", but there's no box to select firmware manually. If I ask it to read current device it says it's "Unable to match the appropriate firmware. Some key information cannot be read from the device".
After some digging, I came across RSD Lite 6.2.4 and have also downloaded the following STOCK ROM:
ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.
I've also tried different stock roms (RETBR, RETCA) and different android versions (Nougat and Oreo) but the message was always the one on this screen:
https://imgur.com/Xdq36E8
Finally, I tried flashing it manually with system wide Platform Tools. Just to check, I tried unlocking the bootloader. When I typed 'fastboot oem get_unlock_data', this was the outcome:
>fastboot devices
a8d9e088 fastboot
>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.004s]
Finished. Total time: 0.082s
Then, I typed the getvar command and got the cid: 0xDEAD:
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-albus_retail-b625135-190911
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: a8d9e088
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 5FA607D400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-albus_retail-b625135-190911
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.078s
Even though I knew I'd hardly achieve anything after that, I tried flashing it manually, inputting line by line, but didn't get very far (I tried both fastboot and mfastboot). These are the steps I followed:
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 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 oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
The outcomes for each command are the following:
>getvar max-sparse-size returns:
max-sparse-size: 268435456
Finished. Total time: 0.002s
>oem fb_mode_set returns:
FAILED (remote: '')
fastboot: error: Command failed
>flash partition gpt.bin:
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.167s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
>flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.417s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote: '')
fastboot: error: Command failed
>flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (62728 KB) OKAY [ 2.951s]
Writing 'modem' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
>flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (4124 KB) OKAY [ 0.364s]
Writing 'fsg' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote: '')
fastboot: error: Command failed
>flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.904s]
Writing 'dsp' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote: '')
fastboot: error: Command failed
>flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.249s]
Writing 'logo' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote: '')
fastboot: error: Command failed
>flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.748s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
>flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 1.087s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
>flash system system.img_sparsechunk.0 (it was the same from 0 to 12)
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 12.211s]
Writing 'system' (bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
>flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (135836 KB) OKAY [ 6.299s]
Writing 'oem' (bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
>erase carrier
Erasing 'carrier' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
>erase cache
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
>erase DDR
Erasing 'DDR' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
>oem fb_mode_clear
FAILED (remote: '')
fastboot: error: Command failed
>reboot (reboot works lol)
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
So, is it dead after all? Or am I doing something wrong? There was a video on YouTube in which the guy managed to solve the 0xDEAD cid by using a UMT dongle, but it's a rather expensive equipment.
Any suggestion will be highly appreciated.

Bad news
Same happened to my moto z2 play dual sim Indian unit in 2019, when I updated to Oreo January patch. Literally all errors are same. I just have the dead phone rn. Company itself said it was dead and nothing could be done. It's great if anyone could help here. Otherwise get ready to buy another device.

cmpunk624 said:
Same happened to my moto z2 play dual sim Indian unit in 2019, when I updated to Oreo January patch. Literally all errors are same. I just have the dead phone rn. Company itself said it was dead and nothing could be done. It's great if anyone could help here. Otherwise get ready to buy another device.
Click to expand...
Click to collapse
You can try to flash blankflash

marcost22 said:
You can try to flash blankflash
Click to expand...
Click to collapse
I would appreciate a lot if you could link a guide since, I don't have much experience with flashing. Note : Bootloader of my device is not unlocked.

cmpunk624 said:
I would appreciate a lot if you could link a guide since, I don't have much experience with flashing. Note : Bootloader of my device is not unlocked.
Click to expand...
Click to collapse
https://phonlabtech.com/how-to-fix-motorola-hard-bricked-devices-in-qualcomm-bulk-mode/
Here's a guide that should guide you through it
https://mirrors.lolinet.com/firmware/moto/albus/blankflash/
And here are the blankflash files for our device, choose the one that corresponds to the version of stock you were running(or had running before going into customs roms)

Thank you very much. I'll try this out. I'll update the thread soon.

The driver install lesson on the link provided is not working. Can you provide an alternate link? Thanks.