Develop Bugs

About to brick my DZ, help! (Solved, backupCID was blank)

So i had custom rom installed by previous owner, but which i did not like, so i wanted to go stock.
After following some guide i managed to flash new rom into my DZ using CWM and all hell broke loose.
My DZ refused to boot, only gives me the white htc screen and vibrates once.
From hboot i tried go back into recovery, which gives me same white screen with htc logo and vibrates once. Same goes for Factory reset option.
After week of browsing xda forums and google, i finally gave up. Thou i managed once to reboot into G2 os after attempted flash trhu PC10IMG method or from recovery as first attempt, not sure. Which i thougt was supposed to be DZ rom, but was not. This rom might have reduced my system partition, i dont know how to confirm this.
Fastboot works, but no adb since i have no OS running atm.
Fastboot getvar all gives me this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>fastboot devices
SH0B5RT09144 fastboot
C:\Documents and Settings\User>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.84.2000
(bootloader) version-baseband: 26.02.01.15_M2
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 1.22.531.8
(bootloader) serialno: SH0B5RT09144
(bootloader) imei: 352212045345548
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: adbd7a75
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
C:\Documents and Settings\User>
At this point i dont want to go solo anymore, so im crying out for help on this one... I want to save this awesome Desire Z
Edit: I am able to flash recovery using fastboot flash recovery recovery.img but recovery option is still useless (does the white screen htc logo vibrating once thingy)

Boot to bootloader and write down all on that screen here
Then in bootloader choose image CRC and write down all that (may take 5min to run)
Then we will go from there
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Boot to bootloader and write down all on that screen here
Then in bootloader choose image CRC and write down all that (may take 5min to run)
Then we will go from there
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 8 2010 , 15:56:38
Then i have Fastboot, recovery,factory reset, simlock, system info and image crc in this order.
In image CRC i have:
hboot : 0x2A125CF4
boot : 0xD28A4324
recovery : 0x26A3CD9C
system : 0x0
Then it promts me to press power key to go back

Alright, you are looking good and most likely this isn't a brick, should be easy to recover
Do these steps
Go to fastboot mode and run
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now you want the most recent recovery, probably latest 4ext (see this thread for recovery links - http://forum.xda-developers.com/showthread.php?t=2348266
In second post along with lots of other good links
Now take this image and
fastboot flash recovery nameofrecovery.img
fastboot reboot-bootloader
Now choose recovery
If this gets you there flash ROM of choice (and gapps if needed) in this new recovery
Reboot
If anything fails or you can't find links let me know
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

C:\Documents and Settings\User>fastboot erase system -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'system'...
OKAY [ 0.344s]
erasing 'userdata'...
OKAY [ 0.266s]
erasing 'cache'...
OKAY [ 0.109s]
finished. total time: 0.719s
C:\Documents and Settings\User>fastboot erase boot
erasing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.125s
C:\Documents and Settings\User>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\Documents and Settings\User>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Documents and Settings\User>cd C:\android-sdk_r11-windows\platform-tools
C:\android-sdk_r11-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (5342 KB)...
OKAY [ 0.891s]
writing 'recovery'...
OKAY [ 0.594s]
finished. total time: 1.484s
C:\android-sdk_r11-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\android-sdk_r11-windows\platform-tools>
Did all that but still cannot access recovery :/ does the white screen thing.
Now im having hard time booting into hboot / fastboot
Edit: Okay, got in after a while Image crc as follows:
hboot 0x2A125CF4
boot 0x0
recovery 0x4C2506F5
system 0x0

http://forum.xda-developers.com/showthread.php?t=2348266
The second post in this thread you will find a section on adb and fastboot, the how to why to link brings you to a guide on fastboot
Flash the dz hboot from there (be sure to check md5sum)
I'm under the impression you have a corrupt partition right now so
fastboot flash hboot hboot.img
fastboot reboot-bootloader
Now start over with the same fast boot erase and flash commands from prior
Sent from my Nexus 7 using XDA Premium 4 mobile app

Still no luck.
I flashed hboot_7230_0.82.0000_100902.nb0, which i got from the PC10IMG.zip mentioned in thread.
Image CRC from hboot did not change after flash, so i guess i had the exact same hboot.
I repeated all the steps you mentioned and it gave me same error messages.
Still willing to help me?

You should have the .84.2000 according to your bootloader
Maybe try flashing the dz pc10img.zip in post 30 of that thread, many have said it fixed similar problems for them
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
You should have the .84.2000 according to your bootloader
Maybe try flashing the dz pc10img.zip in post 30 of that thread, many have said it fixed similar problems for them
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did that and repeated all again. Did not do anything :/ only recovery crc changed, but flashed recovery did not work so i flashed the 4ext again, still no access to recovery
Any ideas? Maybe im stuck with G2 system size since i flashed G2 rom back then, which i got to boot. Should i try that again? If so, any hints to do it properly?

Unzip that pc10img.zip that was linked in post 30 from the fastboot thread, use the dz one and flash just the bootloader with fastboot
There is an issue somewhere and I'm under the impression that if we can successfully flash this bootloader all will be good
Otherwise try this
Boot to bootloader
fastboot rebootRUU
fastboot flash update dzpc10img.zip
Of course replace with whatever the proper name is (forget off hand)
And then note all input/output from cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Unzip that pc10img.zip that was linked in post 30 from the fastboot thread, use the dz one and flash just the bootloader with fastboot
There is an issue somewhere and I'm under the impression that if we can successfully flash this bootloader all will be good
Otherwise try this
Boot to bootloader
fastboot rebootRUU
fastboot flash update dzpc10img.zip
Of course replace with whatever the proper name is (forget off hand)
And then note all input/output from cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashing the hboot from zip changes nothing and for some reason fastboot rebootRUU gives me list of commands
C:\android-sdk_r11-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\android-sdk_r11-windows\platform-tools>fastboot rebootRUU
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\android-sdk_r11-windows\platform-tools>
Should i try to manually format system partition? If so, how and how large?

Sorry, the command is
fastboot oem rebootRUU
Sent from my Nexus 4 using XDA Premium 4 mobile app

Do you mean fastboot update DZPC10IMG.zip since fastboot flash update DZPC10IMG.zip gives unknown partition error.

Sounds right, its been probably at least a year or two since I've worked on this, take a look at my threads and you'll see two comprehensive guides on fastboot which will have all the proper steps
Sent from my Nexus 4 using XDA Premium 4 mobile app

I was able to flash stock rom extracted from RUU.
I used fastboot oem rebootRUU and then fastboot flash zip rom.zip and everything went OK.
However, i still cannot access recovery nor boot my phone.
Atm my hboot is 0.85.0013 SHIP S-OFF
Radio 26.10.04.03_M
Image CRC :
osb1: 0x7EE4ED8C
amss: 0xB7A63815
hboot: 0x887F7ABB
boot : 0x4CB9BC27
recovery 0xCFD60F9D
system 0xC46F8680
Any leads where to go from here?

Um, what RUU did you use? Did you use the one I made from my post? You should have a different bootloader if so
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Um, what RUU did you use? Did you use the one I made from my post? You should have a different bootloader if so
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to flash DZPC10IMG.zip from rebootRUU but that did no good either so i tried to flash this rom from this RUU RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Which i believe is supposed to be latest stock rom from DZ... correct me if im wrong

The problem with flashing a random PC10IMG.zip is that it will change your hboot, recovery, radio, etc
Not all this firmware is 100% compatible and can cause issues depending on your phones current state
Can you link the guide you followed originally by the way? Want to see if I can figure out what happened to your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
The problem with flashing a random PC10IMG.zip is that it will change your hboot, recovery, radio, etc
Not all this firmware is 100% compatible and can cause issues depending on your phones current state
Can you link the guide you followed originally by the way? Want to see if I can figure out what happened to your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have no idea where that guide is now, but if my memory serves me well, i flashed PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from cwm recovery. After that i was able to boot into G2 rom for a while, thou my onscreen buttons didnt work (back and home etc) after that, no idea.
Edit: I do have my old DZ with working CWM v3.0.2.4 recovery. Can i use that in my advantage somehow?

Here is some data if its helpfull. My backup cid seems to be blank. Im under impression it should be like y_13 or so.
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D087B50
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is
(bootloader) setting->cid::
(bootloader) serial number: SH0B5RT09144
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =456
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.13.04.19_M androidboot
(bootloader) .cid= androidboot.batt_poweron=good_battery androidboot.carr
(bootloader) ier=COMMON androidboot.mid=PC1011000 androidboot.keycaps=qwe
(bootloader) rty androidboot.mode=normal androidboot.serialno=SH0B5RT0914
(bootloader) 4 androidboot.bootloader=0.84.2000 no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:657379 msec
FAILED (status read failed (Unknown error))
finished. total time: 222.922s

Pixel XL bricked, bootloader locked and recovery doesn't work.

Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Useful logs:
fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) hw-revision:PVT
(bootloader) mid:G-2PW2100
(bootloader) version-main:0.12.999.1
(bootloader) imei:352693081633543
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:pg2fs:no
(bootloader) has-slot:pg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:a
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4240000
(bootloader) variant:US
(bootloader) secure:yes
(bootloader) unlocked:no
(bootloader) version-baseband:8996-012901-1702171013
(bootloader) version-bootloader:8996-012001-1704121145
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x635400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:HT7370201155
(bootloader) kernel:lk
(bootloader) product:marlin
all:
finished. total time: 2.243s
./flash-all.sh (8.0.0-stock-opr3.170623.007):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32268 KB)...
OKAY [ 1.076s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.175s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.275s
target reported max download size of 536870912 bytes
sending 'radio_a' (57272 KB)...
OKAY [ 1.952s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.050s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.150s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10452): Zip: unable to allocate 818872552 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
W/ziparchive(10452): Zip: unable to allocate 263934088 bytes at offset 0 : No space left on device
failed to extract 'vendor.img': I/O Error
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
error: file_write: write: No space left on device
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
FAILED
Device version-bootloader is '8996-012001-1704121145'.
Update requires '8996-012001-1706221457'.
finished. total time: 0.300s
./flash-all.sh (7.1.2-stock-njh47d):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32380 KB)...
OKAY [ 1.088s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.187s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.247s
target reported max download size of 536870912 bytes
sending 'radio_a' (57240 KB)...
OKAY [ 1.924s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.022s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10714): Zip: unable to allocate 1721085316 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (26001 KB)...
OKAY [ 0.951s]
writing 'boot_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.401s

zades9 said:
Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Click to expand...
Click to collapse
I assume that you have tried fastboot boot with the correct twrp image?

I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".

mikefnz said:
I assume that you have tried fastboot boot with the correct twrp image?
Click to expand...
Click to collapse
I get this log:
Code:
[cristian: PixelXL]$ fastboot boot twrp-3.0.2-0-alpha2-fastboot-marlin.img
downloading 'boot.img'...
OKAY [ 0.901s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.001s

Pain-N-Panic said:
I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".
Click to expand...
Click to collapse
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

I have no idea man... hopefully someone a lot more experienced than me comes around with a valid solution.

zades9 said:
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20

mikefnz said:
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20
Click to expand...
Click to collapse
I can't enable Bootloader Unlocking from the developer settings because the device is bricked.

@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.

Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?

comat0se said:
Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?
Click to expand...
Click to collapse
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

tdct12 said:
@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.
Click to expand...
Click to collapse
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!

Bryanx86 said:
I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!
Click to expand...
Click to collapse
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/

zades9 said:
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
Actually that's not true. You can flash factory ota updates on a locked bootlader from stock recovery, idk about twrp though.

zades9 said:
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/
Click to expand...
Click to collapse
I wasn't referring to flashing that zip file, but looking inside to see if it's an adb shell script, you have a booting phone with a working bootloader, the recovery is compromised. There has to be a way to get your phone fixed. Only when it's totally dead do you give up hope

Well, while we are grasping at straws, make sure your fastboot is the very latest version. The version I use is marked as
~$ fastboot --version
fastboot version -4022467
I would also give the November image a try.

Crap I bricked mine too! Was on rooted Stock with twrp. Did factory reset (to unroot), then relock bootloader (all done with Skipsoft Toolkit). Thought I'd be in the clear, but now it's just bootlooping a half second Google logo and then black. I can get into the bootloader but nothing else works, not recovery, nothing. Can't flash anything since bootloader is locked now. Tried adb commands like fastboot continue but nothing works... Any updates or ideas on this!?? Device is bricked! I bought mine new on Craigslist so may have some trouble with RMA.... Yikes!

Please let this be a lesson to people to stop locking their bootloader's, or know what the heck they are doing before they do. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b

dictionary said:
Please let this be a lesson to people to stick locking their bootloader's, or know what the heck they are doing. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b
Click to expand...
Click to collapse
Code:
C:\Users\cristian>fastboot --set-active=_b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.076s
C:\Users\cristian>fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.292s
I posted my problem on the Pixel User Community, but that thread is dead: https://groups.google.com/a/googlep...forums.com?utm_medium=email&utm_source=footer

XT1710-09 Bricked

Hello guys,
I need a help. I was trying to update my moto using this thread: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153
Everything seemed to be fine until the restart. Phones starts imidately in Fastboot mode with ERROR: Failed to pass validation, backup to fastboot. Now I can't do anything. I've tried to flash other roms, using also that thread: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479 but during the installation it gives many error about downgrading to older security version. Any Ideas? I was trying to find blanckflash but qboot doesn't see the phone. What can I do with that?
with command getvar all I get this. Maybe it will be helpfull.
HTML:
D:\moto recover\>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.CD
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(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: ZY2249PJMN
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: EDCCE8F000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 351888080876090
(bootloader) meid:
(bootloader) date: 07-24-2017
(bootloader) sku: XT1710-09
(bootloader) carrier_sku:
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jan 25 4:33:24 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/albus_playpl/albus:7.1.1/
(bootloader) ro.build.fingerprint[1]: NPSS26.118-33-9/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.301.12.albus_play
(bootloader) ro.build.version.full[1]: pl.playpl.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953P_23.33.07.34R ALBUS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g2371d89-0010
(bootloader) kernel.version[1]: 2-g249f1d8 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Sat Feb 3 11:22:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.CD-0-g4650d8f
(bootloader) rpm.git: git=MBM-NG-VC1.82-0-gbd19194
(bootloader) tz.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) devcfg.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) keymaster.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) prov.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.CD-0-g361b83a
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(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.047s

Do you unlock bootloader before?

Mark2014 said:
Do you unlock bootloader before?
Click to expand...
Click to collapse
Actually not... I assumed it was unlocked...

rembick said:
Actually not... I assumed it was unlocked...
Click to expand...
Click to collapse
You flash rom without unlock bootloader !!!
sorry, I cant help.

Mark2014 said:
You flash rom without unlock bootloader !!!
sorry, I cant help.
Click to expand...
Click to collapse
Thanks anyway, cheers.

How did you flash the Oreo stock ROM in the first place, did you use the script or did you manually flash the commands? Do you still have the flashing log to upload (i.e. the output from the ADB terminal)?
If that's your getvar output after the flash, then it looks like the Oreo update did not work (you're still on 7.1.1). Is your device on the Play.pl carrier btw? It looks like you're receiving some Play.pl specific firmware?
Code:
Blur_Version.26.301.12.albus_playpl.playpl.en.US
Your bootloader is locked, which is why it's falling back to fastboot mode
Code:
(bootloader) securestate: oem_locked
- OEM_locked represents a locked bootloader.
EDIT - Having downloaded and looked at the albus Oreo update, it looks like your bootloader got updated to the Oreo bootloader (version C0.CD), but the rest of your device was not updated. Hence, your device bootloader performed the integrity checks expecting Oreo firmware and failed to boot as you still have 7.1.1 firmware on your device.
Are you able to re-flash the Oreo stock firmware, and if so, can you provide us with a flash log please? If another flash does not work in getting your device working, you may have to consult your carrier or retailer for assistance.
Here's the info for the Oreo stock ROM:
Code:
BUILD REQUEST INFO:
SW Version: albus-user 8.0.0 OPS27.76-12-25 26 release-keysM8953P_41.50.07.63R
MBM Version: C0.CD
Modem Version: M8953P_41.50.07.63R
FSG Version: FSG-8953-08.120
Build Fingerprint: motorola/albus/albus:8.0.0/OPS27.76-12-25/26:user/release-keys
CQATest App Version: 6.0.3
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 27.21.26.albus.retail.en.US
Model Number: Moto Z2 Play
Android Version: 8.0.0
Baseband Version: M8953P_41.50.07.63R
Build Id: OPS27.76-12-25
SW Display Build ID: OPS27.76-12-25
Build Date: Wed Apr 4 07:17:22 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.27.21.26.albus.retail.en.US
Version when read from CPV: albus-user 8.0.0 OPS27.76-12-25 26 release-keys
AB Update Enabled: False
Full Treble Enabled: False

Hi. I have a same version - 09. Just bought on days and manually updated to Oreo.
Just use easily this commands set from post you mentioned:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash 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 oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear

Thanks for reply guys, I was away couple of days. I will try your solutions today and give feedback.
EDIT:
Hi. I have a same version - 09. Just bought on days and manually updated to Oreo.
Just use easily this commands set from post you mentioned:
Click to expand...
Click to collapse
Thank you man! You've saved me! your solution works and also I got rid of carrier software from my phone. Thank you one more time.

rembick said:
Thanks for reply guys, I was away couple of days. I will try your solutions today and give feedback.
EDIT:
Thank you man! You've saved me! your solution works and also I got rid of carrier software from my phone. Thank you one more time.
Click to expand...
Click to collapse
May I know If you flash through fastboot with locked bootloader or not ?
Thanks.

kuro_neko said:
May I know If you flash through fastboot with locked bootloader or not ?
Thanks.
Click to expand...
Click to collapse
I didn't unlock bootloader. Just flashed through Fastboot using the commands one by one not using any .bat file.

You problem (bootloader) cid: 0x0032

Hey, I also got a problem with XT1710-09, but it's a little bit different one.
I rooted it with Magisk and wanted to install an OTA, so I unrooted it.
Then all my problems started to come to light.
Somehow I managed to modify content of /system partition, so OTA installation was unsuccessful.
Then I remembered that before rooting I made a backup with TWRP, so I tried to restore only system partition from that backup.
Unfortunately, my phone couldn't boot. Then I made a decision to flash just system partition from some other image (well, this one in particular: ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
Ok, my phone started working again, but then I noticed that no OTA were available for my phone.
Today I investigated a bit, found OTAs and tried to sideload them.
This time error was: build fingerprint error.
Well, yeah, at first I tried to install http://erfanoabdi.000webhostapp.com...on.26.241.16.albus.retail.en.US&carrier=reteu which was meant for "albus", but my phone is branded for Play.
Then I tried to install http://erfanoabdi.000webhostapp.com...51.29.albus_playpl.playpl.en.US&carrier=reteu. This time I got the version for "albus_playpl", but build version was not right, due to flashing system partition which I described above.
And here is my question: what I should do now?
I really don't want to lose any data, nor do I want to install my apps all again.
Is there any solution for me to get it right?

zaq21wsx said:
Then I made a decision to flash just system partition from some other image (well, this one in particular: ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
Click to expand...
Click to collapse
NPSS26.118-19-14 is "November 2017". Did you have that version before? If not, restoring only the System partition will break the OTA upgrade script because it verifies Boot and Oem partitions as well.
My suggestion is to flash the following partitions from the stock image: gpt, bootloader, logo, boot, oem, system
With that the data remains intact then you can try to check for OTA again.

wsemi said:
NPSS26.118-19-14 is "November 2017". Did you have that version before? If not, restoring only the System partition will break the OTA upgrade script because it verifies Boot and Oem partitions as well.
My suggestion is to flash the following partitions from the stock image: gpt, bootloader, logo, boot, oem, system
With that the data remains intact then you can try to check for OTA again.
Click to expand...
Click to collapse
But now I don't really know what version I had before, because of that branded software. It's nowhere to be found on the internet...
Is changing ro.product.name in build.prop any solution for "albus" from "albus_playpl"? Or how does it change when I'll be flashing another image?

zaq21wsx said:
But now I don't really know what version I had before, because of that branded software. It's nowhere to be found on the internet...
Is changing ro.product.name in build.prop any solution for "albus" from "albus_playpl"? Or how does it change when I'll be flashing another image?
Click to expand...
Click to collapse
Don't change build.prop. Product name should not change, albus_playpl version is probably for different device.
Try to flash ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip without "erase userdata".

wsemi said:
Don't change build.prop. Product name should not change, albus_playpl version is probably for different device.
Try to flash ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip without "erase userdata".
Click to expand...
Click to collapse
But now I have "albus_playpl" with system image from NPSS26.118-19-14.
Btw what is the difference between ALBUS_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip? And will it be good for my XT1710-09?

zaq21wsx said:
But now I have "albus_playpl" with system image from NPSS26.118-19-14.
Btw what is the difference between ALBUS_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip? And will it be good for my XT1710-09?
Click to expand...
Click to collapse
Ok, I get it know. At the first reading I didn't catch that "Play" is also the name of your mobile carrier. They sold the device with "albus_playpl" firmware. Probably they just put some bloatware or limitation on top of the retail version.
Currently your partitions are inconsistent and seems there is no way to get a full "playpl" firmware. So to make the partitions consistent again you can flash a full retail (carrier independent) firmware. I believe if you do that (as previously described) you will get the OTA updates as well.

wsemi said:
Ok, I get it know. At the first reading I didn't catch that "Play" is also the name of your mobile carrier. They sold the device with "albus_playpl" firmware. Probably they just put some bloatware or limitation on top of the retail version.
Currently your partitions are inconsistent and seems there is no way to get a full "playpl" firmware. So to make the partitions consistent again you can flash a full retail (carrier independent) firmware. I believe if you do that (as previously described) you will get the OTA updates as well.
Click to expand...
Click to collapse
Yeah, that's a sad coincidence in my case... Well, I'll come back to it, when I have more free time to have fun with flashing new firmware.
You only suggest not to flash data partition, but which one is it?
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata # is it this one? should I just omit it?
fastboot erase DDR
fastboot oem fb_mode_clear

zaq21wsx said:
Code:
fastboot erase userdata # is it this one? should I just omit it?
Click to expand...
Click to collapse
Exactly. Omitting that line should keep the data and internal storage. But to be sure you can make backup to a usb stick.

Moto Z2 Play
My Moto Z2 Play is bricked after system update November 2017.
Bootloader was unlocked.
Now phone is showing on PC as Qualcomm HS-USB QDLoader 9008.
Please help

Locked Bootloader - Bootloop - XT1879-04 - please help

I got to this point after following a guide here to install magisk and MK100 Nash. I lost baseband, probably because I naively flashed XT1789-05 firmware from the guide, to an 04. Idk, anyway, I hadn't read as much at that point and thought I needed to lock the bootloader again *duh duh.* So I'm reading a lot about how this might be impossible to recover from and it's starting to look like it. I've downloaded 10s of GB of firmware to multiple computers, and I for sure can say that the bootloader is rejecting any flashing of firmware from OCX27.109-51 or OCX27.109-36 that I've tried anyway. There may be yet more stock firmwares to try, but I think I'm missing the point with all that because shouldn't any stock firmware be accepted by the bootloader? Anyway, if I could get people to muster up whatever they can on getting out of this trap I laid myself, I would really appreciate it. I was very foolish to attempt this when my food stamps and college application depend on me having a phone number. Plus this phone was sweet I feel like I betrayed it.
I've been trying to fuss with Qualcomm recovery but either EDL is broken too, since some commands I've tried to get it into EDL just resulted in it going to the ol' "can't be trusted," screen but that might be just that it's not going into EDL anyway. Thinking about getting a deepflash cable or something. I lack the patience and dexterity to rig it myself right now. But I don'y want to get my hopes up if it's screwed.
One fun quirk is that if I fastboot boot boot.img it actually does boot to a broken OS where "pixel setup" infinitely crashes but I can get it to let me use a black desktop with limited settings, like I can use the flashlight haha. No adb or ability to change developer settings though. In case it wasn't clear, I can't use TWRP, factory reset, or anything but fastboot essentially.
I'm wondering if someone knows a shell script I could possibly load into fastboot to enable OEM unlock again? AS in, commands to change the OEM unlock to "enable" in dev ops?
I noticed fastboot has a shell option '-c' which I was hoping to leverage with one of those broken boot.imgs maybe change the settings that way?
Btw I also have tried using the LMSA tool and it's a piece of crap, it never seemed like it would work on my other computer, but it had a weird connection. I installed windows on this one and it seemed to work, possibly a USB 2.0 thing, but as soon as LMSA seemed to actually be maybe doing something, I lost the ability to sign in. It just hangs forever and says it was successful then asks again (or it doesn't). I added a new windows user, tried reinstalling like 40 times, it behaved erratically but ultimately the problem persisted and now it remembers my login info between uninstalls and across new users but can't actually log in.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224TL8V5
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 3F57D9A7
(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:<Not zero>
(bootloader) meid:
(bootloader) date: 03-25-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku: XT1789-04
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3748
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g668a0f8 (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]: Thu Jan 10 22:25:12 CST 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0

What -05 firmware did you flash?

41rw4lk said:
What -05 firmware did you flash?
Click to expand...
Click to collapse
I don't even know anymore, it was on a computer that I had to wipe and install windows over in order to try everything I did. The clue in my other computer, which is probably accurate, is NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT. I'd be willing to bet that is the firmware that is currently flashed, before it was modified with Magisk v20.4, MindTheGapps-8.1.0-arm-20180808_153837, and either MK100 or MK81 of Mokee. I'm no longer even sure if this firmware is for 05, that's just what the name of some other archive this all got dumped into. It's also the version that the instructions I was following used, before I even knew there were 6 versions.

NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT is the last firmware available for TMO, hopefully whatever firmware you've flashed wasn't a pie firmware.
With a locked bootloader you can only flash official signed same version or newer firmware. I would try to flash that again, your goal is to get a booting system that you can enable oem unlocking in. That will give you more flexibility to solve other issues if needed. However if you've flashed a oie firmware you might be out of luck.

41rw4lk said:
NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT is the last firmware available for TMO, hopefully whatever firmware you've flashed wasn't a pie firmware.
With a locked bootloader you can only flash official signed same version or newer firmware. I would try to flash that again, your goal is to get a booting system that you can enable oem unlocking in. That will give you more flexibility to solve other issues if needed. However if you've flashed a oie firmware you might be out of luck.
Click to expand...
Click to collapse
Well, I looked up that exact filename and attempted to flash the firmware from it. Am I somehow doing this wrong? (see attached -- fastboot version eac51f2bb6a8-android )
https://postimg dot cc/BPq1sbmS
This matches the firmware from the folder I found everything else in, like magisk and some utilities from the first night of this, so it should be the one that's on there. I don't think I flashed pie firmware, unless I installed a ROM that was Pie I think that I only flashed Oreo stuff. (Were they just unable to think of a desert that starts with Q?)
I'm noticing my build fingerprint and blur version correspond with the firmware OCSX.109-51-7/9, which also tells me this should have worked (that firmware also doesn't work). I lost baseband before this happened though ( that's why I locked it, because I thought that would fix it smh), I don't know what does that besides flashing the wrong firmware or really screwing something else.

urvurm said:
Well, I looked up that exact filename and attempted to flash the firmware from it. Am I somehow doing this wrong? (see attached -- fastboot version eac51f2bb6a8-android )
https://postimg dot cc/BPq1sbmS
This matches the firmware from the folder I found everything else in, like magisk and some utilities from the first night of this, so it should be the one that's on there. I don't think I flashed pie firmware, unless I installed a ROM that was Pie I think that I only flashed Oreo stuff. (Were they just unable to think of a desert that starts with Q?)
I'm noticing my build fingerprint and blur version correspond with the firmware OCSX.109-51-7/9, which also tells me this should have worked (that firmware also doesn't work). I lost baseband before this happened though ( that's why I locked it, because I thought that would fix it smh), I don't know what does that besides flashing the wrong firmware or really screwing something else.
Click to expand...
Click to collapse
I've attached the latest adb/fastboot files and a flashall.bat for TMO. Delete any .bat files in your firmware folder and then extract the attached zip into the same firmware folder. Then try running the flashall and keep track of what flashes and what doesn't. Again the goal is to get a booting system that you can enable oem unlocking on so that you can unlock your bootloader again.

41rw4lk said:
I've attached the latest adb/fastboot files and a flashall.bat for TMO. Delete any .bat files in your firmware folder and then extract the attached zip into the same firmware folder. Then try running the flashall and keep track of what flashes and what doesn't. Again the goal is to get a booting system that you can enable oem unlocking on so that you can unlock your bootloader again.
Click to expand...
Click to collapse
Under way, will update with output from fastboot. Thank you for helping me.
Update, it's acting differently, preliminary results show that it is automatically appending slot names with extra "_". I'm going to edit the bat file and add "--slot all" to the relevant partitions. I am getting flash permission denied for the bootloader though. I want to let it run all the way through with the slot option. Nvm I don't know what "relevant is" Here's the output from the unedited bat so far:
I'm having serious issues with copying from the command line, idk if you've got tricks for that.
Code:
C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot oem fb_mode_set
OKAY [ 0.016s] Finished. Total time: 0.016s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot getvar max-sparse-size
max-sparse-size: 268435456 Finished. Total time: 0.000s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash gpt gpt.bin
(bootloader) is-logical:gpt: not found
Sending 'gpt' (206 KB) OKAY [ 0.000s]
Writing 'gpt'
(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.132s] Finished. Total time: 0.138s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.316s]
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: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash modem NON-HLOS.bin --slot_all
fastboot: unknown option -- slot_all C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97459 KB) OKAY [ 2.949s]
Writing 'modem__a'
(bootloader) Invalid partition name modem__a FAILED (remote: '')
fastboot: error: Command failed
Sending 'fsg__a' (5596 KB)
OKAY [ 0.185s]
Writing 'fsg__a'
(bootloader) Invalid partition name fsg__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Permission denied
FAILED (remote: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Permission denied
FAILED (remote: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash bluetooth BTFM.bin
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.122s] Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.488s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash logo logo.bin
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (3151 KB)
OKAY [ 0.100s]
Writing 'logo__a'
(bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash boot boot.img
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (23361 KB)
OKAY [ 0.717s]
Writing 'boot__a'
(bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516201 KB)
OKAY [ 16.302s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system__a: not found
Sending 'system__a' (495129 KB) OKAY [ 15.174s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system__a: not found
Sending 'system__a' (519381 KB) OKAY [ 16.144s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523787 KB) OKAY [ 16.147s]
Writing 'system__a'
(bootloader) Invalid partition name system__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516413 KB) OKAY [ 16.205s]
Writing 'system__a'
(bootloader) Invalid partition name system__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system__a: not found
Sending 'system__a' (420583 KB) OKAY [ 12.854s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system_b system_b.img_sparsechunk.0
(bootloader) is-logical:system_b: not found
Sending 'system_b' (515183 KB) OKAY [ 15.725s]
Writing 'system_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system_b system_b.img_sparsechunk.1
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.363s]
Writing 'system_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash oem oem.img
(bootloader) is-logical:oem__a: not found

Try copying the the commands in the flashall one at a time and adjust accordingly.
For example say you post the command fastboot flash logo logo.bin and it returns fastboot: error: Command failed logo__a: not found
You know it's trying to flash the _a slot, which is fine so tell it to do so manually fastboot flash logo_a logo.bin
With a locked bootloader you might get some permissions denied, especially since you flashed the -05 firmware, which might have mismatched a few things. Keep going to the end of your flashall. You need a bootable os so you can get the bootloader unlocked and hopefully overwrite more wrongs and get back to good.

41rw4lk said:
Try copying the the commands in the flashall one at a time and adjust accordingly.
For example say you post the command fastboot flash logo logo.bin and it returns fastboot: error: Command failed logo__a: not found
You know it's trying to flash the _a slot, which is fine so tell it to do so manually fastboot flash logo_a logo.bin
With a locked bootloader you might get some permissions denied, especially since you flashed the -05 firmware, which might have mismatched a few things. Keep going to the end of your flashall. You need a bootable os so you can get the bootloader unlocked and hopefully overwrite more wrongs and get back to good.
Click to expand...
Click to collapse
Well, permission was denied for all slots except for gpt.bin (consistently the only one to work), which I attempted to analyze to better understand the partion table but I think the tool I used was not designed for moto z. Anyway, this is just how it's been. From here, all boot options stop me at the "your software is corrupt you evil hacker anathema to corporate purity"
While I haven't tried it after this round of 100% failed commands, I have used fastboot boot boot.img and been able to enter a dysfunctional wreck of an OS that can almost but not quite get past pixel setup and allow me to edit prefs. Is there maybe a way to bypass setup and edit settings from here? ( It's too broken to launch adb, but it does persist to some degree, I was able to set a pin that remains. It's just infinitely crashing and never makes it past the checkpoint where I disagree to all of tmobiles usage stats agreements,

urvurm said:
Well, permission was denied for all slots except for gpt.bin (consistently the only one to work), which I attempted to analyze to better understand the partion table but I think the tool I used was not designed for moto z. Anyway, this is just how it's been. From here, all boot options stop me at the "your software is corrupt you evil hacker anathema to corporate purity"
Click to expand...
Click to collapse
I assume you mean the lenovo rescue and smart assistant tool. With a mismatch system it might not recognize the phone (which is moto z 2nd gen for the record).
I'll attach a both slot flashall, maybe the other slot can be sorted a little better. For what it is worth, you might boot to recovery and do a factory reset 1st. Then try the other flashall. You might just be out of luck, but it's worth trying a few things before you call it. Same deal with this flashall too, if you need to manually go line by line do it. Also, when it's all said and done, try another factory reset from recovery if needed.
If you see the no command dead android in recovery, just hold pwr and press vol up to get to the actual recovery.
I just seen your edit, no way to get past setup that I know of. Another user tried forever to find away, but I don't think they did. Also, I wouldn't set any screen security until you're in a clean state. It will only hinder what you're trying to do.

41rw4lk said:
I assume you mean the lenovo rescue and smart assistant tool. With a mismatch system it might not recognize the phone (which is moto z 2nd gen for the record)
Click to expand...
Click to collapse
I was actually referring to this: https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/
To see if I could get a better Idea of the partition names, since even when I set --slot all, I get the (permission denied) instead of (command fail) or whatever.
And you're right, LMSA wasn't able to do recognize it and I think it's because of mismatched firmware. I'm glad someone else has seen this broken boot ing. thing before. I know setting a pin was a bad idea, I just felt like I was running out of options.
I'll try this modified flashall you sent me.

41rw4lk said:
For what it is worth, you might boot to recovery and do a factory reset 1st. Then try the other flashall. You might just be out of luck, but it's worth trying a few things before you call it. Same deal with this flashall too, if you need to manually go line by line do it. Also, when it's all said and done, try another factory reset from recovery if needed.
Click to expand...
Click to collapse
No dice.. failed uniformly as flash permission denied or permission denied for the erase commands. Tried line by line and got the same result. Only noteworthy things I saw anyway:
Code:
#after any flash attempt, with both invalid and valid partition names, I get this:
(bootloader) is-logical:<Insert whatever partition name I just attempted _a, _b either way>: not found
#it always says flash permission denied, unless I try an invalid partion name, like radio
(bootloader) is-logical:radio: not found Sending 'radio' (97459 KB) OKAY [ 3.039s] Writing 'radio' (bootloader) Invalid partition name radio FAILED (remote: '') fastboot: error: Command failed
C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot --set-active=other
Setting current slot to '`' FAILED (remote: '')
If you see the no command dead android in recovery, just hold pwr and press vol up to get to the actual recovery.
Click to expand...
Click to collapse
I tried booting to recovery from bootloader, holding power+ vol up, and also just booting with power +vol up. I always get to the "corrupted, can't trust" screen. I think it's trying to boot into TWRP but isn't allowed. It's weird though because I remember trying this before and it just restarting the bootloader, but it might have been a dead battery.

Question Preflash validation failed on REVVLRY+ (G7 Plus), XT1965-T

Dear Experts,
Today I was trying to convert a REVVLRY+ (G7 Plus via TMobile)
to Lineage microg 20, but got the error:
Preflash validation failed
...
Phone was sold via TMobile.
On the back is printed the T logo, and at the bottom: REVVL
Phone is OEM unlocked.
...
Downloaded the latest Lineage microg files from:
lake
download.lineage.microg.org
adb reboot bootloader
fastboot flash boot C:\...20.0-20230213-microG-lake-boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (26545 KB) OKAY [ 0.630s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
...
Some data from adb shell:
...
getprop | grep -i "model"
[media.recorder.show_manufacturer_and_model]: [true]
[ro.opa.device_model_id]: [motorola-lake_n]
[ro.product.model]: [REVVLRY+]
[ro.product.odm.model]: [REVVLRY+]
[ro.product.system.model]: [REVVLRY+]
[ro.product.vendor.model]: [REVVLRY+]
...
No instances of G7 in the properties.
getprop | grep -i "g" | grep -i "7"
[dalvik.vm.heaptargetutilization]: [0.75]
[ro.com.google.rlz_ap_whitelist]: [y0,y5,y6,y7,y8,YH]
[ro.gwfcactivation.disabled_carriers]: [1187,576,1962,1895,2020,1403,1404,2021,2008,1492,28,1839]
[ro.mot.build.guid]: [27f8f602936ea71]
[ro.mot.gms.rlz_ap_whitelist]: [y0,y5,y6,y7,y8,YH]
...
XT1965-T
getprop | grep -i "sku"
[ro.boot.hardware.sku]: [XT1965-T]
[ro.boot.product.hardware.sku]: [n]
[ro.vendor.product.hardware.sku.variant]: [n]
...
In the properties, there are variations of "lake"
lake_revvl
lake
lake_n
getprop | grep -i "lake"
[ro.mot.build.oem.product]: [lake_rv]
[ro.mot.hab.product]: [lake]
[ro.opa.device_model_id]: [motorola-lake_n]
[ro.product.device]: [lake_n]
[ro.product.name]: [lake_revvl_n]
[ro.product.odm.device]: [lake]
[ro.product.odm.name]: [lake_revvl]
[ro.product.product.name]: [lake_revvl]
[ro.product.system.device]: [lake]
[ro.product.system.name]: [lake_revvl]
[ro.product.vendor.device]: [lake]
[ro.product.vendor.name]: [lake_revvl]
[ro.vendor.hw.device]: [lake]
[ro.vendor.product.device]: [lake_n]
[ro.vendor.product.name]: [lake_n]
...
I'm suspecting that this phone had a specific build.
It's not the stock lake build for the standard Motorola G7 Plus.
Is that correct?
Is it possible to install Lineage on this phone?
Either stock, or microg?
If so, where can I find the correct binaries?
And, any special instructions if necessary?
Thanks a lot!

Some more info.
The same error is happening with other Lineage versions, and
even another phone.
With the same phone, I tried installing
Stock Lineage, version 20
Same issue.
...
Then, with another phone, a stock G7 Plus,
there was also the same issue.
Lineage 19, microg
Lineage 19, stock
fastboot flash boot C:\Download\LineageOS\lake\lineage-19.1-20221025-recovery-lake.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (24969 KB) OKAY [ 0.598s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
---
More info from the first phone mentioned:
fastboot getvar all
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) date: 05-15-2020
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
----
fastboot oem partition
...
(bootloader) boot_a: offset=376192KB, size=65536KB
(bootloader) boot_b: offset=441728KB, size=65536KB
----
Any ideas?
Is there something I'm missing?
Thanks

Ok, I figured it out the solution:
You have to do the unlock command, not once,
but twice
fastboot oem unlock UNIQUE_KEY
fastboot oem unlock UNIQUE_KEY
fastboot reboot
Then, on reboot, you will now see the unlock warning
Takes a while to reboot.
Reboots to stock Android: 'Hi There'
...
Posted just in case any other poor soul has this error.