Database Develop

MOTO G 2nd gen XT1072 Thea, error "Preflash validation failed".

Hello, Thank you for assist !!
I got a MOTO G 2nd Generation, with bootloader unlocked, it starts only in Fastboot mode.
Do not enter the recovery, I tried many times, only displayed for several seconds on the screen "Warning Bootloader Unlocked" and returns to fastboot mode.
Equipment details:
C:\Minimal ADB and Fastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4821
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: editado
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: Editado
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: editado
(bootloader) meid:
(bootloader) date: 04-01-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat May 9 0:36:35 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:5.0.2/LXB
(bootloader) ro.build.fingerprint[1]: 22.99-24.12/11:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.46.12.thea_reteu.
(bootloader) ro.build.version.full[1]: reteuall.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: M8926_309101.02.03.17R THEA_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gf18cb80 ([email protected]
(bootloader) kernel.version[1]: ilclbld52) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 18 18:25:55 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V48.21-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.21-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.21-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.21-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.21-0-gd8d8d9e
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C226PVH
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.066s
Flash with stock ROM:
RETEU_XT1072_5.0.2_LXB22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
Also with this:
RETEUALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.zip
I did it with fastboot and mfastboot and got the following errors:
fastboot flash partition gpt.bin
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash motoboot motoboot.img OK
fastboot flash logo logo.bin OK
fastboot flash boot boot.img OK
fastboot flash recovery recovery.img OK
fastboot flash system system.img_sparsechunk.0
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.1
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.2
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.3
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.4
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.5
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash modem NON-HLOS.bin OK
fastboot erase modemst1 OK
fastboot erase modemst2 OK
fastboot flash fsg fsg.mbn OK
fastboot erase cache OK
fastboot erase userdata OK
fastboot reboot OK
Appreciate much any suggestions.

figaro972 said:
Hello, Thank you for assist !!
I got a MOTO G 2nd Generation, with bootloader unlocked, it starts only in Fastboot mode.
Do not enter the recovery, I tried many times, only displayed for several seconds on the screen "Warning Bootloader Unlocked" and returns to fastboot mode.
Equipment details:
C:\Minimal ADB and Fastboot>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4821
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: editado
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: Editado
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: editado
(bootloader) meid:
(bootloader) date: 04-01-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat May 9 0:36:35 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:5.0.2/LXB
(bootloader) ro.build.fingerprint[1]: 22.99-24.12/11:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.46.12.thea_reteu.
(bootloader) ro.build.version.full[1]: reteuall.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: M8926_309101.02.03.17R THEA_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gf18cb80 ([email protected]
(bootloader) kernel.version[1]: ilclbld52) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 18 18:25:55 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V48.21-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.21-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.21-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.21-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.21-0-gd8d8d9e
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C226PVH
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.066s
Flash with stock ROM:
RETEU_XT1072_5.0.2_LXB22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
Also with this:
RETEUALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.zip
I did it with fastboot and mfastboot and got the following errors:
fastboot flash partition gpt.bin
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash motoboot motoboot.img OK
fastboot flash logo logo.bin OK
fastboot flash boot boot.img OK
fastboot flash recovery recovery.img OK
fastboot flash system system.img_sparsechunk.0
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.1
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.2
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.3
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.4
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.5
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash modem NON-HLOS.bin OK
fastboot erase modemst1 OK
fastboot erase modemst2 OK
fastboot flash fsg fsg.mbn OK
fastboot erase cache OK
fastboot erase userdata OK
fastboot reboot OK
Appreciate much any suggestions.
Click to expand...
Click to collapse
Try to flash TWRP for Thea from fastboot and restart to recovery. Flash a CyanogenMod firmware once you get there. >If it didn't work, tell me every detail. I have CM13 20160404 nightly, Pico OpenGapps and TWRP 3.0.2-0 if you want my base. Edit: Avoid touching "motoboot.img" unless really necessary. It contains the device's bootloader, and a bad flash will result in a hard brick.
Use:
fastboot flash recovery twrp-3.0.2-0-thea.img
fastboot reboot recovery
While trying to reboot to recovery, remember to use the volume keys or TWRP will be overwritten. I also see you have problems with GPT.bin, and that's a possibility of hardware damage...

#3
Thanks for answering: :laugh:
I have already tried the procedure described:
Flash only:
fastboot flash recovery twrp-3.0.2-0-thea.img
fastboot reboot recovery
Upon restart, I hold down the volume- key.
Immediately enters the fastboot mode.
Loose Volume- button.
With the key volume-, i positioned itself in the recovery option.
select with Volume+.
Upon restart, only it displayed for several seconds in the "Warning bootloader unlocked" screen and returns to fastboot mode.
And in fact I have tried with at least six versions of gpt.bin file, And with all:
(bootloader) Preflash validation failed
FAILED (remote failure)
:crying:
Thanks again.

Hi guys, this happen to me exactly in the same way.
evererything start with a problem with Android then a flash it.
but give me the same problem:
"(bootloader) Preflash validation failed
FAILED (remote failure)"
after that start only in fastboot and say "UTAG 'bootmode' configured as fastboot."
in fact, i was flash twrp-3.0.2-0-peregrine.img
and when i want to enter to the recovery send me back to fastboot and
say "[Red="Red"]Boot up failed[/COLOR]"
Some idea about what can i do? :crying:
in any case thank you.

try to unlock another time the bootloader

Are you sure your bootloader is properly unlocked?
---------- Post added at 05:28 PM ---------- Previous post was at 05:05 PM ----------
Pattox said:
Hi guys, this happen to me exactly in the same way.
everything starts with a problem with Android then a flash it.
but it gives me the same problem:
"(bootloader) Preflash validation failed
FAILED (remote failure)"
after that the device starts only in fastboot and says "UTAG 'bootmode' configured as fastboot."
in fact, i was flash twrp-3.0.2-0-peregrine.img
and when i want to enter to the recovery send me back to fastboot and
say "[Red="Red"]Boot up failed[/COLOR]"
Some idea about what can i do? :crying:
in any case thank you.
Click to expand...
Click to collapse
Are you rooted?
Did you unlock your bootloader?
If the bootloader is not unlocked try to flash a common firmware (I used to have 5.0.2 retLA before unlock and CyanogenMod).

Fastboot flashing_locked, but system modified?

Hi friends,
I have a new Moto X4 1900-1 that I picked up several weeks ago (standard unlocked version, not Amazon), been working beautifully. Stock aside from magisk flashed/bootloader unlocked, still on stock ROM w/stock recovery.
Been having unrelated hardware trouble with it lately, and was trying to restore it to factory settings prior to sending it in for warranty work...but I fear I've bricked it somehow.
Steps taken:
USB debugging disabled in dev settings
OEM unlock disabled in dev settings
Developer options switched off in dev settings
Magisk completely uninstalled within app
Device rebooted via magisk uninstall
On device reboot, I've got the dreaded "Your device is corrupt. It can't be trusted and will not boot." screen, as if the system is still somehow modified. So, I'm now in a state where the bootloader is locked, but the phone won't boot, not even to recovery.
On trying to boot it to TWRP from fastboot, I get the same "Device is corrupt" screen, and if I try to flash partitions (boot, recovery), I get a "(bootloader) flash permission denied" message. I'm unable to unlock the bootloader again via fastboot oem unlock (unlock code) or fastboot flashing unlock, both of which give me this message: "(bootloader) Check 'OEM unlocking' in Android Settings > Developer Options".
I really did like this phone when it was working, which was for all of a couple weeks. I backed up what I needed before starting all of this, so I don't care about data loss, just want to restore it to factory fresh.

taloras said:
Hi friends,
I have a new Moto X4 1900-1 that I picked up several weeks ago (standard unlocked version, not Amazon), been working beautifully. Stock aside from magisk flashed/bootloader unlocked, still on stock ROM w/stock recovery.
Been having unrelated hardware trouble with it lately, and was trying to restore it to factory settings prior to sending it in for warranty work...but I fear I've bricked it somehow.
Steps taken:
USB debugging disabled in dev settings
OEM unlock disabled in dev settings
Developer options switched off in dev settings
Magisk completely uninstalled within app
Device rebooted via magisk uninstall
On device reboot, I've got the dreaded "Your device is corrupt. It can't be trusted and will not boot." screen, as if the system is still somehow modified. So, I'm now in a state where the bootloader is locked, but the phone won't boot, not even to recovery.
On trying to boot it to TWRP from fastboot, I get the same "Device is corrupt" screen, and if I try to flash partitions (boot, recovery), I get a "(bootloader) flash permission denied" message. I'm unable to unlock the bootloader again via fastboot oem unlock (unlock code) or fastboot flashing unlock, both of which give me this message: "(bootloader) Check 'OEM unlocking' in Android Settings > Developer Options".
I really did like this phone when it was working, which was for all of a couple weeks. I backed up what I needed before starting all of this, so I don't care about data loss, just want to restore it to factory fresh.
Click to expand...
Click to collapse
fastboot flash your factory FW

bcrichster said:
fastboot flash your factory FW
Click to expand...
Click to collapse
That's a negative, ghost rider.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 on following this guide, downloading/extracting the stock image and using the included batch file to flash all, every partition tried returns the following error in Fastboot:
sending 'x'
writing (x)
(bootloader) flash permission denied
FAILED (remote failure)

taloras said:
That's a negative, ghost rider.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 on following this guide, downloading/extracting the stock image and using the included batch file to flash all, every partition tried returns the following error in Fastboot:
sending 'x'
writing (x)
(bootloader) flash permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
Try without Window's batch file thing..?? The new FW may have files of a different name that the cmds may need adjusting for..
Sent from my Moto E (4) Plus using Tapatalk

bcrichster said:
Try without Window's batch file thing..?? The new FW may have files of a different name that the cmds may need adjusting for..
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
No joy. The batch file starts with "fastboot flash partition gpt.bin" (which works), but the next one, "fastboot flash bootloader bootloader.img" fails thusly:
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.218s]
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.272s

taloras said:
No joy. The batch file starts with "fastboot flash partition gpt.bin" (which works), but the next one, "fastboot flash bootloader bootloader.img" fails thusly:
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.218s]
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.272s
Click to expand...
Click to collapse
Can you post a screenshot of the file listing of extracted FW? I'd like to do a file-name comparison, maybe helpful
Sent from my Moto E (4) Plus using Tapatalk

bcrichster said:
Can you post a screenshot of the file listing of extracted FW? I'd like to do a file-name comparison, maybe helpful
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
Firmware download: PAYTON_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Files:
boot.img
bootloader.img
BTFM.bin
dspso.bin
flashfile.xml
fsg.mbn
gpt.bin
logo.bin
NON-HLOS.bin
oem.img
PAYTON_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt
regulatory_info_default.png
servicefile.xml
slcf_rev_d_default_v1.0.nvm
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
system.img_sparsechunk.5
system.img_sparsechunk.6
system.img_sparsechunk.7
system_other.img

Strange.. I usually just use Linux & add "sudo" to the beginning of flash cmd for perms issues. They may have changed something else, somewhere
Sent from my Moto E (4) Plus using Tapatalk

bcrichster said:
Strange.. I usually just use Linux & add "sudo" to the beginning of flash cmd for perms issues. They may have changed something else, somewhere
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
Let me try this from Linux, then. Though, this does seem to be a permissions issue being squawked back at me from Fastboot and not from Windows...

Definitely not a Windows problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

taloras said:
Definitely not a Windows problem.
Click to expand...
Click to collapse
Any possibility there isn't a bootloader partition or maybe it has different name..??
Sent from my Moto E (4) Plus using Tapatalk

Do you remember your latest installed rom? The bootloader you want to flash has to be newer or at least the same, furthermore you can try it on a older machine with USB 2.0 ports, I had the same problem with "permission denied" on USB 3.0/3.1 ports and new mainboards

bcrichster said:
Any possibility there isn't a bootloader partition or maybe it has different name..??
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
How can I check for partitions from Fastboot? As I can't even boot to recovery, I'm limited in what I can do to fastboot commands, which unfortunately doesn't include any adb shell use.

Zokhii said:
Do you remember your latest installed rom? The bootloader you want to flash has to be newer or at least the same, furthermore you can try it on a older machine with USB 2.0 ports, I had the same problem with "permission denied" on USB 3.0/3.1 ports and new mainboards
Click to expand...
Click to collapse
I've never touched the ROMS on the device beyond what it came with out of the box, it's using whatever the latest October OTA version is (there was an 11/1 OTA update which I saw a notification for but didn't apply).
fastboot getvar all gives me the following:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-2d29a27-181010
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2257LBZP
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 662200ED
(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: xxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 09-19-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4284
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.1.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 8.46-21-15/ec37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.261.23.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-06900-8x98.0
(bootloader) version-baseband: M660_7042.27.01.74.02R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gf993b65 (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]: Wed Oct 10 02:52:24 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-2d29a27-181010
(bootloader) git:xbl: MBM-3.0-uefi-455afa3-181010
(bootloader) git:pmic: MBM-3.0-uefi-455afa3-181010
(bootloader) git:rpm: MBM-3.0-uefi-f14962c-181010
(bootloader) git:tz: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:hyp: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:devcfg: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:cmnlib: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:cmnlib64: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:keymaster: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:prov: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:storsec: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(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: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
28.261.23 and 8.46-21-15 look sort of like build numbers; that plus a pretty recent Oct 10th kernel build date leads me to think I'm looking for a 28.46-21-15 or later firmware download, which I'll try to track down. Know of anywhere I could find firmwares that recent?
I have an older desktop with a bunch of usb 2.0 ports on it, I'll give that a whirl too.

taloras said:
I've never touched the ROMS on the device beyond what it came with out of the box, it's using whatever the latest October OTA version is (there was an 11/1 OTA update which I saw a notification for but didn't apply).
fastboot getvar all gives me the following:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-2d29a27-181010
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2257LBZP
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 662200ED
(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: xxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 09-19-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4284
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.1.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 8.46-21-15/ec37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.261.23.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-06900-8x98.0
(bootloader) version-baseband: M660_7042.27.01.74.02R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gf993b65 (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]: Wed Oct 10 02:52:24 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-2d29a27-181010
(bootloader) git:xbl: MBM-3.0-uefi-455afa3-181010
(bootloader) git:pmic: MBM-3.0-uefi-455afa3-181010
(bootloader) git:rpm: MBM-3.0-uefi-f14962c-181010
(bootloader) git:tz: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:hyp: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:devcfg: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:cmnlib: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:cmnlib64: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:keymaster: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:prov: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:storsec: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(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: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
28.261.23 and 8.46-21-15 look sort of like build numbers; that plus a pretty recent Oct 10th kernel build date leads me to think I'm looking for a 28.46-21-15 or later firmware download, which I'll try to track down. Know of anywhere I could find firmwares that recent?
I have an older desktop with a bunch of usb 2.0 ports on it, I'll give that a whirl too.
Click to expand...
Click to collapse
Firmwares can be found here (but unfortunately I can't find a 28.46-21-15 build):
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
https://androidfilehost.com/?w=files&flid=229118&sort_by=date&sort_dir=DESC (official motorola account)
Use these commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
If you get an error with something like "partition not found", change the "fastboot flash modem NON-HLOS.bin" command to "fastboot flash modem_a NON-HLOS.bin" for all commands where you get this error.

Zokhii said:
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
https://androidfilehost.com/?w=files&flid=229118&sort_by=date&sort_dir=DESC (official motorola account)
Hmm but unfortunately I can't find a 28.46-21-15 build...
Click to expand...
Click to collapse
Yeah, the most recent I see is 21-12, with a 10-09 upload date on androidfilehost (earlier than the kernel build date of whatever firmware I'm currently running). Might have to wait a few days until some kind soul uploads something more recent. I'll try this one on that other PC, just to dot my Is and cross my Ts.

taloras said:
Yeah, the most recent I see is 21-12, with a 10-09 upload date on androidfilehost (earlier than the kernel build date of whatever firmware I'm currently running). Might have to wait a few days until some kind soul uploads something more recent. I'll try this one on that other PC, just to dot my Is and cross my Ts.
Click to expand...
Click to collapse
Good luck man, I hope it works

Zokhii said:
Good luck man, I hope it works
Click to expand...
Click to collapse
No luck. flash partition gpt.bin works, but flashing anything after that fails with either "invalid partition name" or "permission denied".
Code:
C:\Users\Paul\Desktop\Peyton>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.000s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.141s]
Finished. Total time: 0.281s
C:\Users\Paul\Desktop\Peyton>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.687s]
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: '')
Finished. Total time: 0.766s
C:\Users\Paul\Desktop\Peyton>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (94843 KB) OKAY [ 4.970s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 5.157s
C:\Users\Paul\Desktop\Peyton>fastboot flash modem_a NON-HLOS.bin
Sending 'modem_a' (94843 KB) OKAY [ 2.612s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 2.643s

taloras said:
No luck. flash partition gpt.bin works, but flashing anything after that fails with either "invalid partition name" or "permission denied".
Code:
C:\Users\Paul\Desktop\Peyton>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.000s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.141s]
Finished. Total time: 0.281s
C:\Users\Paul\Desktop\Peyton>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.687s]
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: '')
Finished. Total time: 0.766s
C:\Users\Paul\Desktop\Peyton>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (94843 KB) OKAY [ 4.970s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 5.157s
C:\Users\Paul\Desktop\Peyton>fastboot flash modem_a NON-HLOS.bin
Sending 'modem_a' (94843 KB) OKAY [ 2.612s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 2.643s
Click to expand...
Click to collapse
Damn.. well then let's wait till someone uploads a newer fw and hope that it will work, I am running out of ideas for now..

Are you using the latest version of fastboot?
https://developer.android.com/studio/releases/platform-tools
latest build PAYTON_OPWS28.46-21-16:
https://moto.netlib.re/payton/

i softbricked moto g6 :(

so here i am, after 2 days of scrutinizing every corner of the internet, looking for solution. i had my moto g6 on pie but out of curiosity i wanted try out different roms and here is what happened:
- after ive successfully unlocked the oem lock, installed twrp and tried to install different roms just to run into error 255 and such i gave up and thought **** it lets go back to original rom, so i fired up fastboot and put back oreo that i downloaded from here, the splashscreen however was still bearing the 'device has been unlocked and cant be trusted' message, so i thought i would put back the oem lock and then formatted the device... ooops and thats when i started having these problems.
- since then i cant install any rom - stock or mod (i was however successful in flashing twrp back on the phone)
- fastboot says FLASHING_LOCKED and having tried maybe 6 different stock roms i noticed that i can flash these two lines without problems:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
but anything after that is giving me (bootloader) flash permission denied FAILED (remote failure) in powershell
so to sum it up: i can boot into fastboot or twrp but i cant do much anything else
ive seemed to exhaust every remote advice out there and really dont know what to do anymore
any of you guys could point me in the right direction? or is the phone done and done?
here is the fastboot var list
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) meid:
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 26 14: 4:32 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
thx
Peter

You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"

najjannajS650 said:
You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"
Click to expand...
Click to collapse
thanks, i think ive already tried that already before,
here is a recap of what happens when i type in fastboot flashing unlock
- (bootloader) WARNING: This command erases all user data. (bootloader) Please re-run this command to continue.
- (bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer (bootloader) Options.
i dont have any rom installed so i cant get into developers options and allow OEM unlock
edited: and if i try ./fastboot oem unlock
i get
... (bootloader) invalid boot state
:crying:

nobody has solution to this? really????

delosanto said:
nobody has solution to this? really????
Click to expand...
Click to collapse
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.

Spaceminer said:
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.
Click to expand...
Click to collapse
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:

delosanto said:
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:
Click to expand...
Click to collapse
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.

Spaceminer said:
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.
Click to expand...
Click to collapse
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above

delosanto said:
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: son[email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Click to expand...
Click to collapse
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.

Spaceminer said:
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.
Click to expand...
Click to collapse
im in the uk, please dont say there is still hope

delosanto said:
im in the uk, please dont say there is still hope
Click to expand...
Click to collapse
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.

Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
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.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
i tried to flashed the files exactly in the order they appear in .info file
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash modem NON-HLOS.bin
./fastboot flash fsg fsg.mbn
./fastboot flash dsp adspso.bin
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery recovery.img
./fastboot flash system system.img_sparsechunk.0
./fastboot flash system system.img_sparsechunk.1
./fastboot flash system system.img_sparsechunk.2
./fastboot flash system system.img_sparsechunk.3
./fastboot flash system system.img_sparsechunk.4
./fastboot flash system system.img_sparsechunk.5
./fastboot flash system system.img_sparsechunk.6
./fastboot flash system system.img_sparsechunk.7
./fastboot flash system system.img_sparsechunk.8
./fastboot flash system system.img_sparsechunk.9
./fastboot flash vendor vendor.img_sparsechunk.0
./fastboot flash vendor vendor.img_sparsechunk.1
./fastboot flash oem oem.img
./fastboot erase cache
./fastboot erase userdata
./fastboot erase ddr
./fastboot oem fb_mode_clear
./fastboot reboot

delosanto said:
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
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.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
Click to expand...
Click to collapse
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
---------- Post added at 07:09 PM ---------- Previous post was at 06:57 PM ----------
@delosanto
Are you able to boot or flash twrp?

Spaceminer said:
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
Click to expand...
Click to collapse
thank you! i think i must have read and tried everything there is out there trying to bring the poor little fella back to life.. ive tried different ports, methods, ROMs, different cables, tomorrow im gonna try what youre suggesting - the older cmd but i doubt it will make any difference, since i was able to flash and re-flash this phone just fine before i somehow managed to **** up the oem lock with no possibility to unlock it since there is no OS.
yes, im able to totally erase twrp (pic of android with red triangle and NO COMMAND) and then bring it back by booting twrp and consequently flashing twrp so it's there back under recovery mode

Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.

Ragarianok said:
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.
Click to expand...
Click to collapse
the last OS that was successfully flashed was Oreo

delosanto said:
the last OS that was successfully flashed was Oreo
Click to expand...
Click to collapse
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)

Spaceminer said:
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)
Click to expand...
Click to collapse
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms

delosanto said:
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms
Click to expand...
Click to collapse
Try flashing this boot.img in fastboot. If it fails, try using TWRP.

Spaceminer said:
Try flashing this boot.img in fastboot. If it fails, try using TWRP.
Click to expand...
Click to collapse
but when i try to flash the stock rom, again i get past the first two files gpt.bin and bootloader.bit but the rest is giving me the same error
(bootloader) flash permission denied
FAILED (remote failure)
but then it crashes back to fastboot
and i even did a clean windows installation today

Stuck in fastboot mode, with OEM blocked, fastboot not accepting commands.

In short I can't flash on any official device rom, and the bootloader is blocked, which I actually need to enable and the OEM at the developer's option.
But I can't turn on the device because the phone says it has a different operating system, and goes back to fastboot. (Then after this message, it goes to the normal Motorola logo, but get stuck there)
Can anyone help me with this? I cant even flash the latest Android version for my phone (Android 10 for XT1965-2), fastboot and mfasboot is not accepting my commands.
GETVAR ALL
After some tries only this command seems to be working.
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-su: not found
getvar:all FAILED (remote failure)
finished. total time: 0.003s
C:\Minimal ADB and Fastboot>fastboot getvar all
getvar:all FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200410
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0054997355
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 7FB0DF4F
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355577095140552
(bootloader) meid:
(bootloader) date: 03-11-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C44559
(bootloader) battery-voltage: 3813
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPWS30.6
(bootloader) ro.build.fingerprint[1]: 1-21-9/664a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.192-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 10 06:08:41 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200410
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200410
(bootloader) gitmic: MBM-3.0-lake_retail-efaf0cccb-200410
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200410
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) gitrov: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200410
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retbr
(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: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.170s
ps: I'm using the translator because I don't speak English.
I tried everything possible, wiping data/cache,adb sideload rom.zip, flashing using mfasboot and fasboot, RSD LITE (This one does not shows me device).
The ONLY thing i didnt tried yet, was another cable, im using a paralel cable of a good quality.
When it doesn't show errors or it doesn't recognize commands, it just gets stuck.
(bootloader) max-sparse: not found
getvar:max-sparse-size FAILED (remote failure)
finished. total time: 0.005s
...
FAILED (remote: unknown command)
finished. total time: 0.002s
(bootloader) has: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
(bootloader) Failed to get the number of bytes to download
FAILED (remote failure)
finished. total time: 0.006s
(bootloader) max: not found
target didn't report max-download-size
sending 'bootloader' (9520 KB)...
please any help ?

it looks like all my partitions are missing, is there anyway to create them ? when i trie 'adb shell' i get 'errror closed'.
can someone point me the direction ?

Mine only goes to Fastboot, he can't even start Android.

MOTO G7 PLUS - HELP UnLock Bootloader

Please help unlock MOTO G7 PLUS and change Bootloader to TWRP or other variant
THANKS
===========================================
First think what I do. Go to MOTO unlock site
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) 3xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) 5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) 2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) Cxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) xxxxxxxxx
OKAY [ 0.018s]
Finished. Total time: 0.019s
Click to expand...
Click to collapse
And gave UnLock Code to Mail
Unlock Code: GSMxxxxxxxxxxxxxxxS
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
!!!I can not unlock bootloader with this instruction!!!​
Motorola Moto G7 Plus
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
!!!I can not unlock bootloader with this instruction!!!​============================================
# adb reboot bootloader
# fastboot devices
Zxxxxxxxx9 fastboot
Click to expand...
Click to collapse
# fastboot oem unlock
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
Finished. Total time: 0.012s
Click to expand...
Click to collapse
# fastboot oem unlock GSMxxxxxxxxxxxxxxxxS
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.006s]
Finished. Total time: 0.006s
Click to expand...
Click to collapse
# fastboot flash boot_a recovery-e-0.19-q-20211027142973-dev-lake.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (21629 KB) OKAY [ 0.583s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
# fastboot oem unlock GSMxxxxxxxxxxxxxxxxS
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.013s]
Finished. Total time: 0.013s
Click to expand...
Click to collapse
# fastboot flash boot_a recovery-e-0.19-q-20211027142973-dev-lake.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (21629 KB) OKAY [ 0.482s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
# fastboot flash boot_b recovery-e-0.19-q-20211027142973-dev-lake.img
(bootloader) is-logical:boot_b: not found
Sending 'boot_b' (21629 KB) OKAY [ 0.488s]
Writing 'boot_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
# fastboot flash boot_b twrp-3.5.2_9-0-lake.img
(bootloader) is-logical:boot_b: not found
Sending 'boot_b' (31612 KB) OKAY [ 0.875s]
Writing 'boot_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
# fastboot oem unlock GSMxxxxxxxxxxxxxxxxS
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.037s]
Finished. Total time: 0.037s
Click to expand...
Click to collapse
# fastboot flash boot_b twrp-3.5.2_9-0-lake.img
(bootloader) is-logical:boot_b: not found
Sending 'boot_b' (31612 KB) OKAY [ 0.714s]
Writing 'boot_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
# fastboot flash boot_a twrp-3.5.2_9-0-lake.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (31612 KB) OKAY [ 0.720s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
==========================================================
# fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-a985cf7-191129
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: Zxxxxxxxxx9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x06
(bootloader) uid: FE8C5F34
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 3xxxxxxxxxxxxxxx8
(bootloader) meid:
(bootloader) date: 03-06-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 4246
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_amx_n/lake_n:9/PPWS2
(bootloader) ro.build.fingerprint[1]: 9.98-111-9/d601:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.271.13.lake_amx.a
(bootloader) ro.build.version.full[1]: mx.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05200-sdm660.0
(bootloader) version-baseband: M636_09.25.02.49R LAKE_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3860674 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Fri Nov 29 00:21:30 CST 2019
(bootloader) git:abl: MBM-3.0-lake_retail-a985cf7-191129
(bootloader) git:xbl: MBM-3.0-lake_retail-41fb118-191129
(bootloader) gitmic: MBM-3.0-lake_retail-41fb118-191129
(bootloader) git:rpm: MBM-3.0-lake_retail-f920ba6-191129
(bootloader) git:tz: MBM-3.0-lake_retail-a34fba5-dirty-191129
(bootloader) git:hyp: MBM-3.0-lake_retail-a34fba5-dirty-191129
(bootloader) git:devcfg: MBM-3.0-lake_retail-a34fba5-dirty-191129
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a34fba5-dirty-191129
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a34fba5-dirty-191129
(bootloader) git:keymaster: MBM-3.0-lake_retail-a34fba5-dirty-191129
(bootloader) gitrov: MBM-3.0-lake_retail-a34fba5-dirty-191129
(bootloader) git:storsec: MBM-3.0-lake_retail-a34fba5-dirty-191129
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxla
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.192s
Click to expand...
Click to collapse
And this instruction doesnt help me
System and Kernel Downloads | Glass Explorer Edition | Google for Developers
developers.google.com
To gain root shell access on Glass, run the following commands using the rooted bootloader:
$ adb reboot bootloader # enter fastboot mode, takes 10-15 seconds
$ fastboot devices # verify device is in fastboot, should see its serial #
$ fastboot oem unlock # unlocking erases all data, you are prompted to run this command twice to be sure
$ fastboot flash boot boot.img # gain root shell access with the rooted bootloader
$ fastboot reboot # reboot the device
$ adb root # start adb as root
$ adb shell # access the shell as root
Click to expand...
Click to collapse

dotignore said:
Please help unlock MOTO G7 PLUS and change Bootloader to TWRP or other variant
THANKS
===========================================
First think what I do. Go to MOTO unlock site
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
fastboot oem get_unlock_data
And gave UnLock Code to Mail
View attachment 5464563
!!!I can not unlock bootloader with this instruction!!!​
Motorola Moto G7 Plus
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
View attachment 5464593
!!!I can not unlock bootloader with this instruction!!!​============================================
# adb reboot bootloader
View attachment 5464559
# fastboot devices
# fastboot oem unlock
View attachment 5464571
# fastboot oem unlock GSMxxxxxxxxxxxxxxxxS
View attachment 5464573
# fastboot flash boot_a recovery-e-0.19-q-20211027142973-dev-lake.img
View attachment 5464577
# fastboot oem unlock GSMxxxxxxxxxxxxxxxxS
View attachment 5464579
# fastboot flash boot_a recovery-e-0.19-q-20211027142973-dev-lake.img
# fastboot flash boot_b recovery-e-0.19-q-20211027142973-dev-lake.img
View attachment 5464581
# fastboot flash boot_b twrp-3.5.2_9-0-lake.img
# fastboot oem unlock GSMxxxxxxxxxxxxxxxxS
# fastboot flash boot_b twrp-3.5.2_9-0-lake.img
# fastboot flash boot_a twrp-3.5.2_9-0-lake.img
View attachment 5464583
==========================================================
View attachment 5464585
View attachment 5464587
View attachment 5464589
# fastboot getvar all
And this instruction doesnt help me
System and Kernel Downloads | Glass Explorer Edition | Google for Developers
developers.google.com
To gain root shell access on Glass, run the following commands using the rooted bootloader:
Click to expand...
Click to collapse
There is a forum for your device
Moto G7 Plus Questions & Answers
Ask your questions about the Moto G7 Plus and get answers from the community! Please be as specific as possible when posting.
forum.xda-developers.com
If you have a Windows machine
Try reflashing the firmware with LSMA and start over
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
If you don't have a Windows machine you may be stuck.
Try reflashing the correct firmware with fastboot
Device Model #, Codename, build #, and Software Channel.
Online FlashFile Converter

I resolve problen
1 need load Android
2 connect to internet
3 developer mode
4 ON OEM mode on Android
5 adb reboot bootloader
and
# fastboot oem unlock GSxxxxxxxxxxxxxxSS
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) WARNING: This command voids warranty!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.011s]
Finished. Total time: 0.011s
# fastboot oem unlock GSxxxxxxxxxxxxxxSS
(bootloader) Bootloader is unlocked!
OKAY [ 0.390s]
Finished. Total time: 0.390s
Click to expand...
Click to collapse