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?

Help. I'm way out of my depth. Moto G5s XT1797

Firstly I will apologise for my lack of knowledge. I had no prior knowledge of how android works, and I have been learning as I go.
Here is my situation: I wanted to remove guest mode from my Moto G5s Xt1797 so I decided to root it. I followed the following process:
Test everything on my old Moto G. Succeed and try the same with the Moto G5s
Attempt to use KingRoot. Fail
Unlock Bootloader
Flash TWRP
Install SuperSu
Install Root Check
Rootchecker says "Device is not rooted"
Reinstall SuperSu. Same result
Attempt to install Magisk. Fail because SuperSu is installed
Attempt to uninstall SuperSu. Fail because phone doesn't think it is installed
Give up and try KingoRoot. After two hours it reached 39% and I stopped it and went to bed
Check Root Check. It says "Device is rooted"
Remove guest mode using BuildProp Editor
Success!
Check Root Check. It says "Device is NOT rooted"
At this point I left it because I had accomplished my goal. However, a few day later I noticed a problem
...
Realised my camera doesn't work
Do some research, find that the kernel is the most likely problem
Install this kernel. (I didn't realise it was incorrect)
Now camera and wifi don't work
Try flashing another incorrect kernel. Fail to install
Give up on the whole thing and try to restore to stock rom using this guide. Fail at "mfastboot flash partition gpt.bin"
Accidentally wipe phone. Can't access wifi to reinstall anything
Give up on that
Create backup using TWRP
Install Lineage 14.1. Camera and wifi work, but I have no idea how to transfer personal information across. I can't even call my wife because I haven't memorised her number.
Realise that Lineage has guest mode, the very thing I was trying to remove
Restore Backup
Try to reinstall stock ROM using .bat file as in this guide
Failure. Receive "(bootloader) image size exeeded partition limits" ("exeeded" spelled incorrectly).
Camera and wifi still don't work
Remove SIM to put in old phone, realise SIM card is wrong size, replace in Moto G5s
Now the camera, wifi and SIM don't work
Start losing sleep over it all
Give up
Write this post
In a nutshell:
MotoG5s
Bootloader unlocked
TWRP installed
SuperSu semi-successfully installed
Wrong kernel installed
Camera, wifi and SIM reader not working
I would like to just completely return to stock, albeit with guest mode still disabled. I don't care about removing bloatware at this point, I just need to repair my phone. Please help. I'm sorry that I have nothing to offer in return, except my love.

Hey um sorry if i got your hopes up with this reply as I can't actually help much and am also not very informed on android phones and tech etc but am learning as I go. I just wanted to ask, for my own phone issues I'm trying to resolve: is your phone a motog5s or a mota g5s plus? Where did you fin the download for LineageOS for a motog5s and could I please have a link? If it's only for a g5s plus, can I have your opinion on if you think this would be compatible with the motog5s?

I have the Moto G5s. NOT plus.
I found the LineageOS download on this G5s forum. https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918.
It worked fine for me. The only issue I noted was full screen video tended to glitch non stop

What error are you getting when flashing stock ROM? Did you install Moto drivers?
Replace "mfastboot" with "fastboot" in every command and try again.

ShattrdChain said:
What error are you getting when flashing stock ROM? Did you install Moto drivers?
Replace "mfastboot" with "fastboot" in every command and try again.
Click to expand...
Click to collapse
Yes, Moto drivers are installed
Using the fastboot method I receive the error: "error: cannot load 'gpt.bin': No such file or directory"
gpt.bin is definitely in the folder, but fastboot can't find it
Using the .bat method I get much further before I receive: "(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed"
Here is everything from that process:
C:\Tools\New ROM>echo off
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
max-sparse-size: 268435456
finished. total time: 0.014s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.007s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.010s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(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.108s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (5179 KB)...
OKAY [ 0.198s]
writing 'partition'...
(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.543s]
finished. total time: 0.746s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (66916 KB)...
OKAY [ 3.301s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.329s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (3120 KB)...
OKAY [ 0.199s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.228s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.022s]
finished. total time: 0.024s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.024s]
finished. total time: 0.026s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (16384 KB)...
OKAY [ 0.554s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.583s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (2195 KB)...
OKAY [ 0.095s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.121s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (16384 KB)...
OKAY [ 0.723s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.750s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (16484 KB)...
OKAY [ 0.751s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.776s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (513248 KB)...
OKAY [ 22.090s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 22.119s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (512318 KB)...
OKAY [ 31.832s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 31.860s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (524213 KB)...
OKAY [ 23.103s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 23.127s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (516197 KB)...
OKAY [ 21.656s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 21.685s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (523150 KB)...
OKAY [ 25.129s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 25.155s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (418542 KB)...
OKAY [ 19.140s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.168s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (476509 KB)...
OKAY [ 23.958s]
writing 'partition'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 23.987s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotDR: not found
erasing 'DDR'...
OKAY [ 0.011s]
finished. total time: 0.013s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.006s]
finished. total time: 0.008s
Press any key to continue . . .

Andrew Reeson said:
I have the Moto G5s. NOT plus.
I found the LineageOS download on this G5s forum. https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918.
It worked fine for me. The only issue I noted was full screen video tended to glitch non stop
Click to expand...
Click to collapse
Hmm okay thank you for this. And good luck with your phone!

Take your phone to the nearest service centre. Since your bootloader is unlocked, they might not help you but, I've got my Samsung and Vivo phones reflashed after I unlocked and bricked phones. You might have to request them a little.

ShattrdChain said:
Take your phone to the nearest service centre.
Click to expand...
Click to collapse
Unfortunately, the nearest service centre is 900km away, so that won't be an option unless I get desperate. I have sent an email to Motorola support, so I'll see if they have anything helpful to say

Good news! I installed Resurrection Remix and now everything works. My only gripe is that it has guest mode. Does anyone know if I can remove it using build.prop like on stock Android?

Glad to hear your phone is working again. No idea about the guest mode.

just a question, why do you hate guest mode so much?

Wait for next security patch what was your old security patch is it April patch the gpt.bin doesn't flash because if we flash the old security patch

[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

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.

Question Soft brick on unmodded XT2052-1. "No bootable A/B slot"

Hi all. I'm a complete newb to this, so please excuse any incorrect terminology. I appreciate any help given!
Here's the situation in brief:
This Moto E (XT2052-1) is completely unmodded. Nothing rooted, nothing unlocked, nothing flashed before. About 1.5 years in use.
It goes through a bootloop, and then "falls through to fastboot."
It reports "No bootable A/B slot" and fastboot getvar current slot yields "not found". I can't get it to switch to either slot.
can't find current slot
Code:
C:\platform-tools>fastboot getvar current slot
(bootloader) current: not found
getvar:current FAILED (remote: '')
fastboot: usage: unknown command slot
can't assign a slot
Code:
C:\platform-tools>fastboot set_active a
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
I think flashing stock ROM (specifically the boot image?) will fix the issue, but I'm running into problems
doesn't let me flash boot image, needs vbmeta image
Code:
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
trying boot with boot image without flashing
Code:
C:\platform-tools>fastboot boot boot.img
Sending 'boot.img' (32768 KB) OKAY [ 0.765s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
And then flashing the boot image again after flashing the vbmeta image (... successfully? not sure)
Code:
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.768s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
I'm not sure if I'm missing a step, or if I need to change toggle a setting somewhere, or what.
I don't want to wipe it, but I understand it might prove to be necessary.
Here are the nitty gritty details:
It started bootlooping and then "falling back to fastboot" about 3 days ago. I don't think there was any damage or instigating event. It says to connect to a computer to fix it with "Software Repair Assistant" (which doesn't seem to exist). Here's the "Bootloader logs" text after turning it on and attempting to start it:
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.​you can try to press powerkey in failure interface to fix it [sic]​If you try to fix it, Please try it at least 6 times [sic]​
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux,falling back to fastboot
Fastboot Reason: Fall-through from normal bootmode
No bootable A/B slot
Failed to boot Linux,falling back to fast bootmoode
Boot up failed
Click to expand...
Click to collapse
Many guides say to use LMSA to detect and fix, but I've also seen people warning of it flashing incorrectly, so I'm wary of it.
The problem seems to be with the A/B slot, so I've done research to understand what that means. I found this guide from droidwin.com useful, and have managed to do the following:
Downloaded and unzipped SDK platform tools.
I'm barely familiar with command line, but fastboot has been fine.
Tried fastboot set_active a, as well as b and other
Found appropriate (I think) stock ROM from here. It has the boot image, as well as many other files. I'm not familiar with how ROM is packaged.
Tried to flash the boot image from the stock ROM. It said I needed to flash the vbmeta image first.
Flashed the vbmeta image, onto both vbmeta_a and vbmeta_b (after much trial and error)
This took a while because I actually got ahold of and downloaded... let's say several stock ROM packages. Cycled through until I found one that was actually accepted.
Tried flashing the boot, but now Preflash validation failed
Here are all the relevent outputs from the command line
Code:
C:\platform-tools>fastboot devices
[...omitted...] fastboot
C:\platform-tools>fastboot getvar all
[...Let me know if I omitted something important...]
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [...omitted...]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 101ECD4600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: [...omitted...]
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-10-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66367
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 6 2:44:35 UTC 2021" [idk why it says that time]
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-141-15-2/e9f0a:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.04R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 1 01:56:14 CDT 2022
(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-ginna_retail-b0c61b8e633-220530
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 0.233s
C:\platform-tools>fastboot set_active a
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot set_active other
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot set_active b
Setting current slot to 'b' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot getvar current slot
(bootloader) current: not found
getvar:current FAILED (remote: '')
fastboot: usage: unknown command slot
C:\platform-tools>fastboot getvar product
product: ginna
Finished. Total time: 0.003s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot: error: Failed to identify current slot
C:\platform-tools>fastboot getvar has-slot:vbmeta
has-slot:vbmeta: yes
Finished. Total time: 0.005s
C:\platform-tools>fastboot flash vbmeta vbmeta.img
fastboot: error: Failed to identify current slot
C:\platform-tools>fastboot boot boot.img
Sending 'boot.img' (32768 KB) OKAY [ 0.765s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot boot_a boot.img
fastboot: usage: unknown command boot_a
C:\platform-tools>fastboot boot_b boot.img
fastboot: usage: unknown command boot_b
C:\platform-tools>fastboot flashing unlock
(bootloader) This command requires you to first unlock the bootloader.
(bootloader) A unlock code may be required.
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot getvar iswarrantyvoid
iswarrantyvoid: no
Finished. Total time: 0.004s
[--WITH WRONG ROM--]
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
[--WITH CORRECT ROM--]
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_a' OKAY [ 0.006s]
Finished. Total time: 0.064s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.768s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (32768 KB) OKAY [ 0.759s]
Writing 'boot_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_b vbmeta.img
Sending 'vbmeta_b' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_b' OKAY [ 0.006s]
Finished. Total time: 0.063s
C:\platform-tools>fastboot BE NORMAL PLEASE
fastboot: usage: unknown command BE
That's about what I've got so far. At one point I did fastboot reboot fastboot and got into fastbootd, but I had no idea what I was doing there and promptly left.
I'm almost ready to give in and try factory resetting it, but I feel like I'm just missing a piece of the puzzle. Maybe several. I don't know. I have so many tabs open.
Again, any help you can give is welcome! Please keep in mind, I only started learning about any of this yesterday (brand new words in my repertoire: image, flash, bootloader, fastboot, slot, stock, ROM, RETUS, NFC, and much, much more!). I may not be the most articulate, but I'm certainly trying :^)
[Edit: and let me know about any formatting faux pas I may have committed! With text color or code blocks or whatever it may be. I messed with the options probably a little more than I should have, heh]

Alright, I've done some more reading and tried a couple other things.
This post with a similar problem suggested that it was a faulty partition, and to run:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
This is what I got
Code:
C:\platform-tools>fastboot oem fb_mode_set
OKAY [ 0.002s]
Finished. Total time: 0.004s
C:\platform-tools>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.009s]
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.121s]
Finished. Total time: 0.252s
C:\platform-tools>fastboot oem fb_mode_clear
OKAY [ 0.002s]
Finished. Total time: 0.005s
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
But it just did its normal bootloop after rebooting. [Oh wait, that's different... oh never mind. Just now, as I was writing, it stayed on one of the flashing screens for a significant amount of time, but then continued looping again]
WAIT OKAY, something happened! After the reboot from flashing gpt.bin, I tried flashing the boot image again.
Code:
[...directly after the previous commands...]
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_a' OKAY [ 0.007s]
Finished. Total time: 0.054s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.763s]
Writing 'boot_a' OKAY [ 0.908s]
Finished. Total time: 1.734s
It accepted the boot image! No more "Preflash validation failed"!
I immediately fastboot getvar all, and I really should have done so after flashing gpt.bin, but oh well. There are some changes!
Code:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [...omitted...]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 101ECD4600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [...omitted...]
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-10-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66367
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Apr 5 23:52: 0 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-141-15-2/e9f0a:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.04R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 1 01:56:14 CDT 2022
(bootloader) sbl1.git: MBM-2.1-ginna_retail-054f0bdd8c-220530
(bootloader) rpm.git: MBM-2.1-ginna_retail-20f2cf34-220530
(bootloader) tz.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) devcfg.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) keymaster.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) cmnlib.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) cmnlib64.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) prov.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) aboot.git: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 7
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 0.753s
First I noticed that the slots information had changed. There is now an active slot, and slot b now reads "bootable" (which is odd, because I flashed boot_a ), and a retry count that isn't 0! Then I noticed a bunch of the git variables also changed, to MBM-2.1-ginna_retail-[yaddayadda-yadda]
I have no idea what this means, but I call it progress!
________________________________________________________________​It still bootloops, but I'll keep poking at it.
A change I've notices, however, from even before I flashed gpt.bin, is an inconsistency of how it bootloops.
It either:
immediately falls through from normal bootmode
bootloops for a while and then goes into fastboot
bootloops and turns off
And I haven't really found a pattern why. I've taken to manually starting fastboot (with volume down) when before it would go there by itself. Who knows.

I'm sorry that I cant help with your situation but could you help me to understand these recovery options? My pc wont recognize the phone when connected in fastboot mode but the phone recognizes the pc....
what am I doing wrong? and are there any settings I'm supposed to have activated to facilitate the data transfer?
Here's my Forum post
Phone is completely stock btw

Heruktiang said:
I'm sorry that I cant help with your situation but could you help me to understand these recovery options? My pc wont recognize the phone when connected in fastboot mode but the phone recognizes the pc....
what am I doing wrong? and are there any settings I'm supposed to have activated to facilitate the data transfer?
Here's my Forum post
Phone is completely stock btw
Click to expand...
Click to collapse
Hi! Due to time constraints, I ended up fully flashing the stock ROM (thereby erasing userdata). I plan on updating this thread tonight with what I did, even though it just eventually led to erasing everything.
Hmm, as to your situation... I have to admit I am not familiar with all this (this was first time touching a bootloader, haha), but I took a quick look through your post. I can note a couple differences between our situations:
My recovery mode was inaccessible, as far as I could tell. If I tried to select it in the bootloader, I think it would give the same "No bootable A/B slot" error.
I never used the LMSA on the phone, but I did have it open when the phone was plugged in to the computer, and the bootloader logs indicated that some sort of communication was happening. I didn't record exactly what the commands were, but I think there were three, among them "getvar product" or some such.
Other than that, I have no insight on this. In my research, I found no way to get the userdata off a bootlooping phone that didn't have TWRP or some things (bootloader?) unlocked. Sorry I can't help much
I was wondering if the bootloop was prompted by a recent update, but there doesn't seem to be too many people affected

Thanks for the swift and detailed reply. I'm starting to think I was hacked. My gf admitted to hacking me before. Ill keep trying to get the pc to communicate with the phone.

GewdGrief said:
I plan on updating this thread tonight with what I did, even though it just eventually led to erasing everything.
Click to expand...
Click to collapse
Had you tried flashing with servicefile.xml from the your firmware archive? It flashes everything, but leaves userdata intact, so I think it would have been your best bet.