Develop Bugs

[Q] ViperOne 4.0.0 Wifi problem; How to go back to stock International HTC M8

Yesterday I upgraded to to the ViperOne Lollipop ROM from the viperOne 3.2.2. kitkat and WiFi keeps getting disconnected after some time. Usually happens after ~45 minutes of inactivity. Turning Wifi on and off doesn't help, on the contrary it doesn't detect any Wifi after I do WiFi Off -> On. After restarting the phone Wifi comes back and I face the same problem all over again after a little while.
Phone info is as follows(took out Serial No. and IMEI):
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any Solutions?
Should I revert back to stock, get the Lollipop OTA and then install ViperOne? If that will help can someone please let me know how to revert back to stock. The backup that I had before I flashed viperOne kitkat got corrupted.
Thanks XDA

http://forum.xda-developers.com/showthread.php?t=2735235

You need firmware 4, look in the op, otherwise its in the op of maximus hd

EddyOS said:
http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
This requires S-OFF. I am still S-ON.

a3adil said:
This requires S-OFF. I am still S-ON.
Click to expand...
Click to collapse
Not all of it. You just need step 3

EddyOS said:
Not all of it. You just need step 3
Click to expand...
Click to collapse
K thanks. Let me try this out.

EddyOS said:
Not all of it. You just need step 3
Click to expand...
Click to collapse
which recovery version should I be using for this? the latest one .401 or the one already on the phone i.e. 3.28.401.6 ? I am confused. I tried both (maybe not a smart thing to do) and this was the result. My Steps so far and yes I am using a macbook.
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot oem lock
ERROR: could not get pipe properties
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.187s
Imraans-MacBook-Prolatform-tools imraanameen$ ./adb shell
error: device not found
error: device not found
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash recovery recovery.img
ERROR: could not get pipe properties
target reported max download size of 1826414592 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.568s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot reboot-bootloader
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Imraans-MacBook-Prolatform-tools imraanameen$ ./adb shell
error: device not found
error: device not found
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot oem rebootRUU
ERROR: could not get pipe properties
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.010s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot devices
ERROR: could not get pipe properties
SH44XWM02716 fastboot
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash zip r
recovery.img ruu.zip
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash zip ruu.zip
ERROR: could not get pipe properties
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 47.189s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 103.571s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot reboot
ERROR: could not get pipe properties
rebooting...
finished. total time: 0.008s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash recovery recovery_4.16.401.10.img
ERROR: could not get pipe properties
target reported max download size of 1826418688 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.670s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.243s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash recovery recovery_3.28.401.6.img
ERROR: could not get pipe properties
target reported max download size of 1826418688 bytes
sending 'recovery' (14556 KB)...
OKAY [ 1.540s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.059s
Imraans-MacBook-Prolatform-tools imraanameen$

Step 3 does not say you need to fastboot flash stock recovery, neither 4.16.401.10 nor 3.28.401.6. And you can't fastboot flash a recovery after bootloader is relocked.
a- relock bootloader - you already did
b- ./fastboot oem rebootRUU
c- ./fastboot flash zip ruu.zip
d- ./fastboot reboot-bootloader

ckpv5 said:
Step 3 does not say you need to fastboot flash stock recovery, neither 4.16.401.10 nor 3.28.401.6. And you can't fastboot flash a recovery after bootloader is relocked.
a- relock bootloader - you already did
b- ./fastboot oem rebootRUU
c- ./fastboot flash zip ruu.zip
d- ./fastboot reboot-bootloader
Click to expand...
Click to collapse
I unlocked the bootloader again and followed the same steps you mentioned. Always came out with Failed message and some error. I should mention again that I am still S-ON. What would you advise?

Because your device is S-On, you need to relock bootloader then follow b, c, d
If you prefer the backup/restore method, get your backup here : http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
Use the 3.28.401.9 instead of 3.28.401.6 and its stock recovery img.
1. Restore backup
2. fastboot flash 3.28.401.9 recovery.img
3. Reboot do OTA
For these, no need to relock bootloader
Good luck.. gotta go now

ckpv5 said:
Because your device is S-On, you need to relock bootloader then follow b, c, d
Click to expand...
Click to collapse
I've honestly tried that twice already. Let me try it again just so I can post the Error that comes up

Read what I update in previous post
If that also cannot work, I'll tell other method when I'm back in next 5 or 6 hours.

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?

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.

Moto z play XT1635-2 blackscreen - only fastboot mode - device manger Fastboot S

HI Guys! Im from brazil, first of all, thank for attention!
I have a Moto z play XT1635-2 which is in blackscreen when I plug the phone on Windows 10 device manager initially only show FASTBOOT S on unknown devices section.
If I press power button + Vol - fo some seconds white light blink for a moment.
only with Android ADB device driver or motorola ADB drivers it is possible to be recognized when I run command fastboot device with Plataform Tools.
The phone is not able to go to the recovery mode.
I also try install qualcomm drivers >> qualcomm hs-usb qdloader 9008 << to make the phone someway be flash.
doest workd
I have tried many blank flash but it does not work anyway because it gets stock on WAITING DEVICE....
I have tried flashing Rom with these commands:
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
The ROM I used was that:
XT1635-02_ADDISON_RETAIL_6.0.1_MPN24.104-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml and
XT1635-02_ADDISON_RETAIL_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
but also, nothing.
Thats the log:
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.290s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.158s]
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: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.589s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.589s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.566s]
Writing 'dsp' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
(bootloader) is-logical:logo: not found
Sending 'logo' (2533 KB) OKAY [ 0.228s]
Writing 'logo' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
(bootloader) is-logical:modem: not found
Sending 'modem' (73570 KB) OKAY [ 1.859s]
Writing 'modem' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
(bootloader) is-logical:fsg: not found
Sending 'fsg' (1996 KB) OKAY [ 0.223s]
Writing 'fsg' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (257311 KB) OKAY [ 6.183s]
Writing 'system' (bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (261378 KB) OKAY [ 6.276s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (251415 KB) OKAY [ 6.140s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (255811 KB) OKAY [ 6.175s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (255574 KB) OKAY [ 6.173s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (257857 KB) OKAY [ 6.215s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (260164 KB) OKAY [ 6.273s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (253309 KB) OKAY [ 6.139s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.8
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (256374 KB) OKAY [ 6.202s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.9
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262140 KB) OKAY [ 6.310s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.10
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (147406 KB) OKAY [ 3.645s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash oem oem.img
(bootloader) has-slotem: not found
(bootloader) is-logicalem: not found
Sending 'oem' (105020 KB) OKAY [ 2.618s]
Writing 'oem' (bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
I run this command and thats the log:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.82 )
(bootloader) product: unknown
(bootloader) board: unknown
(bootloader) secure: yes
(bootloader) hwrev: unknown
(bootloader) radio: e
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serial no: ebf8c285
(bootloader) cid: OxDEAD
(bootloader) channelid: Oxee
(bootloader) uid: 4172C7FB00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei: eeeeeeeeeeeeeee
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: e000e0000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456 (bootloader) current-time:
(bootloader) ro.build. fingerprint:
(bootloader) power off alarm: 0 (bootloader) ro.build.version. full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbli.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg-git
(bootloader) keymaster.git: keymaster.git
DO YOU GUYS BELIEVE SOMEWAY THERE IS SOME POSSIBILITY TO BRING BACK THE PHONE TO LIFE?

Bazileu said:
HI Guys! Im from brazil, first of all, thank for attention!
I have a Moto z play XT1635-2 which is in blackscreen when I plug the phone on Windows 10 device manager initially only show FASTBOOT S on unknown devices section.
If I press power button + Vol - fo some seconds white light blink for a moment.
only with Android ADB device driver or motorola ADB drivers it is possible to be recognized when I run command fastboot device with Plataform Tools.
The phone is not able to go to the recovery mode.
I also try install qualcomm drivers >> qualcomm hs-usb qdloader 9008 << to make the phone someway be flash.
doest workd
I have tried many blank flash but it does not work anyway because it gets stock on WAITING DEVICE....
I have tried flashing Rom with these commands:
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
The ROM I used was that:
XT1635-02_ADDISON_RETAIL_6.0.1_MPN24.104-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml and
XT1635-02_ADDISON_RETAIL_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
but also, nothing.
Thats the log:
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.290s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.158s]
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: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.589s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.589s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.566s]
Writing 'dsp' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
(bootloader) is-logical:logo: not found
Sending 'logo' (2533 KB) OKAY [ 0.228s]
Writing 'logo' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
(bootloader) is-logical:modem: not found
Sending 'modem' (73570 KB) OKAY [ 1.859s]
Writing 'modem' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
(bootloader) is-logical:fsg: not found
Sending 'fsg' (1996 KB) OKAY [ 0.223s]
Writing 'fsg' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (257311 KB) OKAY [ 6.183s]
Writing 'system' (bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (261378 KB) OKAY [ 6.276s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (251415 KB) OKAY [ 6.140s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (255811 KB) OKAY [ 6.175s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (255574 KB) OKAY [ 6.173s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (257857 KB) OKAY [ 6.215s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (260164 KB) OKAY [ 6.273s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (253309 KB) OKAY [ 6.139s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.8
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (256374 KB) OKAY [ 6.202s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.9
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (262140 KB) OKAY [ 6.310s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.10
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (147406 KB) OKAY [ 3.645s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash oem oem.img
(bootloader) has-slotem: not found
(bootloader) is-logicalem: not found
Sending 'oem' (105020 KB) OKAY [ 2.618s]
Writing 'oem' (bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
I run this command and thats the log:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.82 )
(bootloader) product: unknown
(bootloader) board: unknown
(bootloader) secure: yes
(bootloader) hwrev: unknown
(bootloader) radio: e
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serial no: ebf8c285
(bootloader) cid: OxDEAD
(bootloader) channelid: Oxee
(bootloader) uid: 4172C7FB00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei: eeeeeeeeeeeeeee
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: e000e0000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456 (bootloader) current-time:
(bootloader) ro.build. fingerprint:
(bootloader) power off alarm: 0 (bootloader) ro.build.version. full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbli.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg-git
(bootloader) keymaster.git: keymaster.git
DO YOU GUYS BELIEVE SOMEWAY THERE IS SOME POSSIBILITY TO BRING BACK THE PHONE TO LIFE?
Click to expand...
Click to collapse
Try using Lenovo Moto Smart Assistant. It is an official reflash software.

ChlupataKulicka said:
Try using Lenovo Moto Smart Assistant. It is an official reflash software.
Click to expand...
Click to collapse
I have tried but it does not work, Moto Smart Assistant does not recognized the phone, even though it is in fasboot mode with blackscreen

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.