Database Users

Bootlooping XT1622 with locked bootloader

As above, my XT1622, running the December security update, is bootlooping, and has been since installing that update. It doesn't boot into recovery either. I recently bought it second hand and hadn't got around to enabling USB debugging, so am limited in terms of what I can do with it. I've flashed the December 2017 Fastboot stock on it, but no change (and of course downgrading to a previous version of the bootloader wouldn't work as things stand).
Any suggestions would be gratefully received! I don't want to give up on the thing because there's obviously life left in it somewhere.

Ok, did you flash the update.zip with stock recovery or twrp?

It was the stock firmware flashable through Fastboot, so just followed that method manually - Fastboot is the only thing I can reach. I can't boot into recovery mode at all, it just loops.

How are you flashing the fastboot stock ROM, are you using a script or flashing each command manually? Can you verify each command is reporting [OKAY] after flashing?
Also, are you performing a full flash on the device (including fastboot erase userdata)?
If you can, it would be good to see a getvar all data, so we have an idea of the state of this device, given it was second hand:
1)Boot your device to the bootloader, attach to your computer via USB cable.
2)Open ADB on your computer, and type 'fastboot getvar all' without quotes into the ADB terminal. Press Enter.
3)Paste the output in a new post here - you may wish to omit the IMEI. The output should contain a list of your device variables.

https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Try this, this is for flash bootloader and Qualcomm drivers by 0

Thanks for the help, all.
I flashed each command manually on Fastboot (couldn't get script to run, for whatever reason), each was reported OKAY. I included 'erase userdata' in there.
getvar all results:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223FFP8R
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: 13E8080100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (redacted!)
(bootloader) meid:
(bootloader) date: 08-09-2016
(bootloader) sku: XT1622
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 24 21:50:49 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:7.0/NPJS25.
(bootloader) ro.build.fingerprint[1]: 93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband: M8952_70030.25.03.62.01R ATHENE_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g498cc0c (hudsoncm
(bootloader) kernel.version[1]: @ilclbld34) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Nov 23 09:34:10 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
all: listed above

How to re lock my bootloader

hi. little help?
i am tried to relock my bootloader but... still require signed boot.img
motorola g5 plus XT1685
C:\Users\lassitter\Desktop\Moto G5 Plus\minimal_adb_fastboot_1.4.3_portable>fast
boot devices
ZY224FQL9G fastboot
C:\Users\lassitter\Desktop\Moto G5 Plus\minimal_adb_fastboot_1.4.3_portable>fast
boot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8C
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(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: MSM8953
(bootloader) serialno: ZY********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 4C8D884C00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 3**************
(bootloader) meid:
(bootloader) date: 08-28-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat May 23 15:19:14 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-93-10/12:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.321.12.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47R POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g8599239 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT F
(bootloader) kernel.version[3]: ri Mar 30 01:29:10 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.8C-0-g22013cf
(bootloader) rpm.git: git=202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8C-0-gcba6d5d
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.284s
I have solved my problem myself.Android 8 is installed with the Moto G5 Toolkit.Оnce and start and adjust,again the same software.Тhen the commands are written in ADB
fastboot oem lock
fastboot oem lock
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash oem oem.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 boot boot.img
fastboot oem lock

Moto G7 (Soft brick?)

Hi Guys, i have a moto g7 1962-4.
After flashed the lineage os rom, and installed wrong modules, i decided to install the Havoc Os, after that, my cellphone's restarted on the fastboot(secure) screen.
The oem_turns to lock, says oem_lock
and, i can't flash roms.
The error on start: failed to initialize partition table.
No Bootable A/B Slot, and failed to boot Linux, falling back to the fastboot.
here is my bootloader informations:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
i can't flash nothing, Its giving me, ex:
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.037s
Remote Failure.
Can someone help me? please angelllllllllllllss

Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.

WoKoschekk said:
Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.
Click to expand...
Click to collapse
and the fastboot details? its like, corrupted?

WoKoschekk said:
Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.
Click to expand...
Click to collapse
Dont Work, Remove Error

Are you able to boot into TWRP via "fastboot boot twrp.img" ? Is there any fastboot command executable on your device?
Can you enter the stock recovery?

WoKoschekk said:
Are you able to boot into TWRP via "fastboot boot twrp.img" ? Is there any fastboot command executable on your device?
Can you enter the stock recovery?
Click to expand...
Click to collapse
Nope, i cant go to the Stock Recovery, and the fastboot boot twrp.img dont work.

if you can't run the following commands then maybe you will need a blankflash...
Just use the gpt.bin and bootloader.img files from your stock rom:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader

Or try RSDlite or any Motorola repair software...

WoKoschekk said:
if you can't run the following commands then maybe you will need a blankflash...
Just use the gpt.bin and bootloader.img files from your stock rom:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Gpt and bootloader don't installs, the remote error its back.

WoKoschekk said:
Or try RSDlite or any Motorola repair software...
Click to expand...
Click to collapse
i tried, the RSD, and not recognize the phone.

So, you can't do anything... I guess the only chance to fix your phone is a blank flash.
I'm sorry but I don't know how to do that.
It would be better for you to use the search function.
Good luck!!

GordinhoBr said:
Hi Guys, i have a moto g7 1962-4.
After flashed the lineage os rom, and installed wrong modules, i decided to install the Havoc Os, after that, my cellphone's restarted on the fastboot(secure) screen.
The oem_turns to lock, says oem_lock
and, i can't flash roms.
The error on start: failed to initialize partition table.
No Bootable A/B Slot, and failed to boot Linux, falling back to the fastboot.
here is my bootloader informations:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
i can't flash nothing, Its giving me, ex:
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.037s
Remote Failure.
Can someone help me? please angelllllllllllllss
Click to expand...
Click to collapse
Got the same here brow. I've tried everything without success. I took the cell phone in the authorized service and they charged me incredible 840 reais to fix (the phone already costs 899 new in the store). In the G7 plus forum there is a topic talking about Blank Flash. I tried to do it but I need the singleimage.bin file for the G7 model, since there the file is for G7 plus and it doesn't fit. I didn't find this file anywhere on the internet so I tried to build mine. apparently needs to extract the booloader.img file and create from the extracted files the singleimage.bin file with a program called star. For now, assists cannot recover. I already put mue G7 in the drawer and bought an a50, because I believe that in a few months this blank flash file will appear on the internet and solve our case. anyway, good luck! and any news please let me know here! I will do the same.

diegovmsouza said:
Got the same here brow. I've tried everything without success. I took the cell phone in the authorized service and they charged me incredible 840 reais to fix (the phone already costs 899 new in the store). In the G7 plus forum there is a topic talking about Blank Flash. I tried to do it but I need the singleimage.bin file for the G7 model, since there the file is for G7 plus and it doesn't fit. I didn't find this file anywhere on the internet so I tried to build mine. apparently needs to extract the booloader.img file and create from the extracted files the singleimage.bin file with a program called star. For now, assists cannot recover. I already put mue G7 in the drawer and bought an a50, because I believe that in a few months this blank flash file will appear on the internet and solve our case. anyway, good luck! and any news please let me know here! I will do the same.
Click to expand...
Click to collapse
send me you phone number.

Do you have access to Fastboot mode, right?

River blankflash is available on Tel$gram

HueyT said:
River blankflash is available on Tel$gram
Click to expand...
Click to collapse
On what now?

iamcubeman said:
On what now?
Click to expand...
Click to collapse
Telegram

IMEI and Baseband unknown

I installed the ROM LineageOS 17.1 on my xt1962-4(Moto G7) and now my phone is without IMEI and without Baseband
And I'm not able to activate the SIM slot
TWRP:twrp-3.3.1-2-river
Rom used:lineage-17.1-20200423-nightly-river-signed
https://textsaver.flap.tv/lists/3d82

GamingHero said:
I installed the ROM LineageOS 17.1 on my xt1962-4(Moto G7) and now my phone is without IMEI and without Baseband
And I'm not able to activate the SIM slot
TWRP:twrp-3.3.1-2-river
Rom used:lineage-17.1-20200423-nightly-river-signed
https://textsaver.flap.tv/lists/3d82
Click to expand...
Click to collapse
Download the stock firmware
And flash
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Run
Code:
fastboot getvar all
To find codename ad software channel
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Find firmware @ https://mirrors.lolinet.com/firmware/moto
Sent from my Moto E (4) using Tapatalk

So did you ever figure it out? Having the same problem here, have tried many variations on the instructions above. Nothing I flash for either "RETAIL" or "RETUS" gives me my IMEI back. I've tried several full roms and also firmware only and then lineage.
What even constitutes the "stock firmware" for this device? XT1962-1 is supposed to be RETAIL, but it also says RETUS in several places. RETUS is supposed to be for XT1962-4 is it not? What is the true "stock firmware" for "Model: XT1962-1 Type: M0314"? That's what's inscribed on the back of the phone, but I've been doing
fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff2029-200211
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY2272SL7W
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: CCFC076500000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [redacted but present]
(bootloader) meid:
(bootloader) date: 11-29-2019
(bootloader) sku: XT1962-1
(bootloader) carrier_sku: XT1962-1
(bootloader) battid: SB18C34004
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 16 13:29:47 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/river/river:9/PPO29.114-1
(bootloader) ro.build.fingerprint[1]: 6/35c0:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.20.river.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld87) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #1 SMP PREEMPT Wed Jan
(bootloader) kernel.version[3]: 16 07:47:50 CST 2019
(bootloader) sbl1.git: MBM-2.1-river_retail-516ad1c-200211
(bootloader) rpm.git: MBM-2.1-river_retail-22daab3-200211
(bootloader) tz.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) devcfg.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) keymaster.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) cmnlib.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) cmnlib64.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) prov.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) aboot.git: MBM-2.1-river_retail-0ff2029-200211
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.011s
Click to expand...
Click to collapse
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Till I'm blue in the face and it does nothing. I also tried the Lenovo recovery thing on Windows, and it said the device isn't supported (?!)

If you made a backup of your persist partition, flash it with twrp. I haven't had to do it with the g7, but it always worked with the g5+.

Yeah I almost made a disclaimer like "and of course if I had a backup I'd flash that" but thank you.
---------- Post added at 03:38 AM ---------- Previous post was at 03:31 AM ----------
For the record, I figured my issue out. Had to flash XT1962-1_RIVER_RETUS_9.0_PPOS29.114-134-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

nothing yet, I even took it for technical assistance and nothing solves
does anyone have a suggestion? in addition to the possible motherboard exchange

Stumbled into a product desc. with some band nfo...dunno if it'll help but here it is....
http://phonedb.net/index.php?m=devi...l_sim_td-lte_in_64gb_xt1962-6__motorola_river

https://forum.xda-developers.com/g5-plus/how-to
We went through this with the G5+, and it boils down to a permissions issue in the persist partition. This guide should help, even though it is a different variant.

Help needed moto G5 plus - stuck in fastboot menu? cant flash?

I have spent the last 12 hours trying to fix this. I am tech savvy but have never flashed a cellphone before, hence I dunno if I am doing something wrong. And apologies if my terms aren't correct. please correct me when I am wrong.
Phone is a moto G5 plus XT1681 (according to imei), one day it powered to fastboot (see image 1) and what ever I try to press, I get an error. (see image 2)
I followed and tried many guides. but especially this one
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
when I try to run the first line of the script I get the following error.
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
If I keep advancing in the code I get the same error than this guy
Bricked MOTO G5(XT1676) stucked at fastboot menu
hELLO.. I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from...
forum.xda-developers.com
the phone is detectable with command "fastboot devices"
Despite running this, the phone still stays "oem_locked" like in the images
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot oem unlock
(bootloader) feature disabled
OKAY [ 0.017s]
Finished. Total time: 0.018s
I tried also installing TWRP and I get this error (because maybe that bypasses a locked bootloader?)
"(bootloader) Preflash validation failed
FAILED (remote failure)¨
And here is the log for what I learned that you always ask for
C:\Users\ADj\Desktop\moto g\Tiny ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ca31f0ad
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 423FF92E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.175s
QUESTIONS
Am I just confusing rom because of firmware or country?
is all of this because my bootloader seems locked?
do I just need to get to recovery mode first?
I just want the phone to work, don't care for the data inside.
Other people that seem to be stuck with the same problem
https://forum.xda-developers.com/t/...-question-noob-friendly.3963645/post-85232253
THANKS IN ADVANCE AND SORRY FOR THE LONG POST I WANTED TO GIVE ALL MY INFORMATION AND RESEARCH

Same problem here.