Database Develop

[XT1097 AT&T] Last Time Flashing Failed Bootloop

Well.. I may have messed up beyond belief.
I accidentally ordered the AT&T variant instead of going with XT1095, and instead of returning it, I figured I'd unlock it and convert.
To my error, I tried CF-Auto-Root-victara-victararetbr-xt1097 with a locked bootloader and I was put into a bootloop with the error "Fastboot Reason: Last time flashing failed"
Am I screwed? Are there ways to fix this new $325 brick?
I just remembered, I have my old XT1095 IMEI and bootloader code. Is there anyway to flash my XT1097 with those numbers so my phone can pretend to be my old 'Pure' edition and be able to unlocked?

Have you check unlocking the bootloader from motorola site? I heared xt1097 is also unlocking now via motorola website, you can also try these lines hope it will help you reboot in fastboot first then type these:
Fastboot reboot-bootloader
Fastboot oem fb_mode_set
Fastboot erase cache
Fastboot oem fb_mode_clear
Fastboot reboot
Hope you will get the device back running.. If these didnt help kindly get back here.. And dont try any imei tweak etc you will hard brick that

Salik Iqbal said:
Have you check unlocking the bootloader from motorola site? I heared xt1097 is also unlocking now via motorola website, you can also try these lines hope it will help you reboot in fastboot first then type these:
Fastboot reboot-bootloader
Fastboot oem fb_mode_set
Fastboot erase cache
Fastboot oem fb_mode_clear
Fastboot reboot
Hope you will get the device back running.. If these didnt help kindly get back here.. And dont try any imei tweak etc you will hard brick that
Click to expand...
Click to collapse
I've tried what you posted to no avail.
I've been trying to download VICTARA_ATT_XT1097_5.1_LPE23.32-21.9_cid1_CFC.xml.zip or VICTARA_ATT_XT1097_5.1_LPE23.32-21.2_cid1_CFC.xml.zip from FileFactory, but because i'm using the "Slow Speed" download(50Kb/s), it keeps failing, so I haven't even been able to try flashing the official ATT Victara firmware.
I'm almost positive it's because the partition was flashed over... so I'm hoping if I can get one of these files downloaded, I can try flashing the original gpt.bin and it boot fine..
Any other ideas would be extremely helpful.
If this helps, this is all the info from my bootloader
AP Fastboot Flash Mode (S)
60.16 (sha-496ce05,c2015-04-02 18:55:00)
CPU: MSM8974AC ES1.1
eMMC: 32GB Samsung RV=07 PV=0B TY=57
DRAM: 2048MB Elpida S8 SDRAM DIE=4GB
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official

Fastboot getvar all
Paste the output pls

Salik Iqbal said:
Fastboot getvar all
Paste the output pls
Click to expand...
Click to collapse
I just need VICTARA_ATT_XT1097_5.1_LPE_23.32-21.9 gpt.bin if I do belive so myself. Teach me if i'm wrong, I truly am interested in learning this stuff!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA449074CQ
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 6FD5BD0D0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***************
(bootloader) meid:
(bootloader) date: 02-11-2016
(bootloader) sku: XT1097
(bootloader) iccid:********************
(bootloader) cust_md5: ********************************
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jun 28 20:20:35 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/victara_att/victara:5.1/L
(bootloader) ro.build.fingerprint[1]: PE23.32-21.9/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.16.9.victara_att.
(bootloader) ro.build.version.full[1]: att.en.US
(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[0]: MSM8974BP_4235210.110.09.11R VICTARA_A
(bootloader) version-baseband[1]: TT_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gff6f5d9 ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Sep 29 04:22:36 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: att
all: listed above
finished. total time: 0.101s

you need full flash, not just gpt.bin.. if you did flashing this gpt only, you will have dead bricked device.. check the pvt msg i gave you fast download link there.. download rsd lite, unzip that and flash the full stock rom.. good luck!

Salik Iqbal said:
you need full flash, not just gpt.bin.. if you did flashing this gpt only, you will have dead bricked device.. check the pvt msg i gave you fast download link there.. download rsd lite, unzip that and flash the full stock rom.. good luck!
Click to expand...
Click to collapse
THANK YOU! I really appreciate it, you have no idea how happy I am.
RSD Lite and fastboot, gives me the error: version downgraded for primary_gpt.

ibphantom said:
THANK YOU! I really appreciate it, you have no idea how happy I am.
RSD Lite and fastboot, gives me the error: version downgraded for primary_gpt.
Click to expand...
Click to collapse
It was latest that i gave you..

Salik Iqbal said:
It was latest that i gave you..
Click to expand...
Click to collapse
Uhh... so what could the problem be? lol.

ibphantom said:
THANK YOU! I really appreciate it, you have no idea how happy I am.
RSD Lite and fastboot, gives me the error: version downgraded for primary_gpt.
Click to expand...
Click to collapse
There are other att files on that folder, download and check if they work for you.. Also edit the xml abd remove two lines gpt.bin and motoboot.img start it with boot.img

Salik Iqbal said:
There are other att files on that folder, download and check if they work for you.. Also edit the xml abd remove two lines gpt.bin and motoboot.img start it with boot.img
Click to expand...
Click to collapse
I removed
<step MD5="72167323145a532c1158c13f8543e6d3" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="a942904bb71a2ba69c27a440e1f9801e" filename="motoboot.img" operation="flash" partition="motoboot"/>
and it flashed up to the boot.img
I got another 'Version Downgraded' error for boot
Does it matter that my bootloader CPU is MSM8974AC ES1.1 and the release keys are for MSM8974BP_4235210.110.09.11R?

I have same problem please somehow help me too
I can't flash boot.img
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA98901CI9
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: F9FED40C0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 359279050697553
(bootloader) meid:
(bootloader) date: 09-16-2014
(bootloader) sku: XT1097
(bootloader) iccid: 89014103286416801740
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 22 11:45:36 UTC 2016"
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gff6f5d9 ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Sep 29 04:22:36 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: att
all: listed above
finished. total time: 0.092s
Click to expand...
Click to collapse

MrSaba said:
I have same problem please somehow help me too
I can't flash boot.img
Click to expand...
Click to collapse
Does anybody know how to erase the gpt.bin so that I can flash stock?
I flashed from XT1095 gpt.bin and now I get the "Version Downgraded for primary_gpt" error.

ibphantom said:
Does anybody know how to erase the gpt.bin so that I can flash stock?
I flashed from XT1095 gpt.bin and now I get the "Version Downgraded for primary_gpt" error.
Click to expand...
Click to collapse
Is your bootloader locked? It must be unlocked to flash firmware from other models as well as to downgrade.
Sent from my XT1095 using Tapatalk

AGISCI said:
Is your bootloader locked? It must be unlocked to flash firmware from other models as well as to downgrade.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Yeah, it's locked. I was just asking in hope that someone had a work around.
I guess I'll try to ship it back to Motorola(since it's within 14 days) and pretend I never even turned it on and ask for the PURE as a replacement.

ibphantom said:
Yeah, it's locked. I was just asking in hope that someone had a work around.
I guess I'll try to ship it back to Motorola(since it's within 14 days) and pretend I never even turned it on and ask for the PURE as a replacement.
Click to expand...
Click to collapse
Yeah, there is nothing you can do. Never flash anything with a locked bootloader, it's a recipe for disaster.
Sent from my XT1095 using Tapatalk

ibphantom said:
Does anybody know how to erase the gpt.bin so that I can flash stock?
I flashed from XT1095 gpt.bin and now I get the "Version Downgraded for primary_gpt" error.
Click to expand...
Click to collapse
Dont play with gpt.bin mate.. You will brick your phone, just wait a little bit more Marshmallow is comming soon, you will have your device working soon, dont try other variant gpt partitions you will brick your phone..
---------- Post added at 11:02 PM ---------- Previous post was at 10:51 PM ----------
Salik Iqbal said:
Dont play with gpt.bin mate.. You will brick your phone, just wait a little bit more Marshmallow is comming soon, you will have your device working soon, dont try other variant gpt partitions you will brick your phone..
Click to expand...
Click to collapse
Umm i found something stupid in your fastboot getvar :/ can you please try this:
Fastboot reboot-bootloader
Fastboot oem fb_mode_clear
Fastboot reboot

softbrick?

I have the same problem, i have XT1097 AT&T and i flashed other provider XT1097 Rom and i cant power on my device i only show fastboot mode and the error to downgrade bootloader , i do not know how can i return to stock , can anyone tell me what can i do ?

XT1926-6 Your device is corrupt

Hi, I have a Motorola g6 xt1926-6, with a leyend “your device is corrupt” I try to upload so many softwares but it show me only error, the device have lock the bootloader
I need help me please

yxmikx said:
Hi, I have a Motorola g6 xt1926-6, with a leyend “your device is corrupt” I try to upload so many softwares but it show me only error, the device have lock the bootloader
I need help me please
Click to expand...
Click to collapse
Unlock the bootloader on the Motorola website, take the steps, and once unlocked when you flash the factory firmware you will be installed
Enviado desde mi moto g(6) mediante Tapatalk

stifmaster81 said:
Unlock the bootloader on the Motorola website, take the steps, and once unlocked when you flash the factory firmware you will be installed
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
I can not enter the system to activate the oem option, that's why I have not unlocked

yxmikx said:
I can not enter the system to activate the oem option, that's why I have not unlocked
Click to expand...
Click to collapse
your Motorola goes into recovery?
Power More volume less?
Enviado desde mi moto g(6) mediante Tapatalk

yxmikx said:
I can not enter the system to activate the oem option, that's why I have not unlocked
Click to expand...
Click to collapse
Hmm, can you remember what firmware you had? Have you tried booting to recovery and tried a cache wipe or factory reset?
If your bootloader is still locked and you did not request an unlock key from Motorola, it might be worth considering visiting a service centre and getting your device looked at. You've still got the warranty, hopefully - might as well use it...

yxmikx said:
I can not enter the system to activate the oem option, that's why I have not unlocked
Click to expand...
Click to collapse
You don't need to enter the system. Hold Volume Down and the power button then follow the steps to flash your stock firmware. You need fastboot.exe on your pc. Plug in a USB cable to the pc and phone then flash the stock firmware. Make sure when you power on the device using power + Vol Down to unlock your bootloader. The option you refer to in system does nothing on its own.
Also tell us how you ended up in this situation. I'm guessing you did something to cause the problem?
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
You don't need to enter the system. Hold Volume Down and the power button then follow the steps to flash your stock firmware. You need fastboot.exe on your pc. Plug in a USB cable to the pc and phone then flash the stock firmware. Make sure when you power on the device using power + Vol Down to unlock your bootloader. The option you refer to in system does nothing on its own.
Also tell us how you ended up in this situation. I'm guessing you did something to cause the problem?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
I believe you need the bootloader unlocked in order to flash anything. I have a 1926-7 and I'm stuck in bootloader, since I can't access the operating system to allow Developer Options, I can't unlock bootloader, and my os is corrupt.
What can I do? Thanks

DavCan said:
I believe you need the bootloader unlocked in order to flash anything. I have a 1926-7 and I'm stuck in bootloader, since I can't access the operating system to allow Developer Options, I can't unlock bootloader, and my os is corrupt.
What can I do? Thanks
Click to expand...
Click to collapse
You should be able to flash official Moto firmware whether your bootloader is unlocked or not.
Look here:
https://mirrors.lolinet.com/firmware/moto/evert/official/
Download the correct firmware for your device and flash.

Ragarianok said:
You should be able to flash official Moto firmware whether your bootloader is unlocked or not.
Look here: URL
Download the correct firmware for your device and flash.
Click to expand...
Click to collapse
Thanks for your reply. I've tried many firmwares already, no luck. Here's the thing:
I'm stuck in Fastboot, it says "flashing_locked" , so I'm not allowed to flash. If you try the command "flashing unlock" it sends you to enable USB debugging and OEM unluck but I DO NOT have access to the operating system anymore.
I hope there's something I can do. Very costly paperweight I have now haha :crying:

help!
I keep trying things with no luck, it seems like I fogot my car keys inside, no spare keys, and the car is bulletproof
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-bf761ac-180305
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY323366HL
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 473E091F
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 351853092729596
(bootloader) meid:
(bootloader) date: 08-22-2018
(bootloader) sku: XT1926-7
(bootloader) carrier_sku: XT1926-7
(bootloader) battid: SB18C20873
(bootloader) battery-voltage: 4150
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-2/00cb:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.2.evert.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: M660_23.40.01.85R EVERT_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gba3f1d6 (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]: Wed Feb 6 01:31:11 CST 2019
(bootloader) git:abl: MBM-3.0-uefi-bf761ac-180305
(bootloader) git:xbl: MBM-3.0-uefi-976f2e6-180305
(bootloader) git:pmic: MBM-3.0-uefi-976f2e6-180305
(bootloader) git:rpm: MBM-3.0-uefi-80b016f-180305
(bootloader) git:tz: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:hyp: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:devcfg: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:cmnlib: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:cmnlib64: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:keymaster: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:prov: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:storsec: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(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: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.297s

No luck
No love? Can't believe there's anything I can do with this. What I was thinking I know, but... still...
I've tried the method downloading the Qualcomm drivers, putting the PC in test mode, etc. but I only get the "<Waiting for device>" and nothing else happens.
Hope you can shed some light here. Thanks

Moto Z3 Play with wrong SKU number

Good Afternoon community, I have a small question about my Moto Z3 Play beckham Brazilian model XT 1929-5. but checking bootloader and settings found that it is showing the incorrect SKU with the number TX1601, if I am not mistaken this number and the Moto G4 plus, there is a way to repair this, and the phone works perfectly running Android 9 Whoever can help will be grateful.

l.rochas said:
Good Afternoon community, I have a small question about my Moto Z3 Play beckham Brazilian model XT 1929-5. but checking bootloader and settings found that it is showing the incorrect SKU with the number TX1601, if I am not mistaken this number and the Moto G4 plus, there is a way to repair this, and the phone works perfectly running Android 9 Whoever can help will be grateful.
Click to expand...
Click to collapse
Do you use Magisk, root or any other kind of "device spoofing"???

Nothing, bootloader locked factory. When I checked the incorrect SKU, the bootloader was the first thing I checked and to my surprise it was blocked.

Can you take a picture of the bootloader screen, usually there's information about the SKU in there...
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
Also, try flashing this ROM, it already contains the May 1st patches:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
you can get more informations on how to flash here:
https://forum.xda-developers.com/z3-play/how-to/firmware-oficial-9-0-0-pie-instalacion-t3911995

Thanks for replying, as requested I will have a photo of the bootloader screen in this mode the sku is incorrect, and also the function barcodes in this, the sku is correct.
Another photo I took was from rsd lite shows an error of (the phone could not switch to fastboot mode) so I can just update the phone in Minimal ADB and Fastboot.
I'm sticking down the getvar all I did on adb walks fastboot
C:\Minimal ADB and Fastboot>mfastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0049643811
(bootloader) cid: 0x0000
(bootloader) channelid: 0x1b
(bootloader) uid: A93A2333
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: I hid
(bootloader) meid:
(bootloader) date: 03-16-2019
(bootloader) sku: XT1601
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4202
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-2/7699:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.3.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: M636_25.43.01.89R BECKHAM_BRAZILDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gcc5f412 (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]: Wed Mar 27 12:33:10 CDT 2019
(bootloader) git:abl: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) git:xbl: MBM-3.0-beckham_retail-d286d94-190327
(bootloader) git:rpm: MBM-3.0-beckham_retail-4696e9e-190327
(bootloader) git:tz: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:hyp: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:devcfg: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib64: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:keymaster: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:storsec: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(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.159s

l.rochas said:
Good Afternoon community, I have a small question about my Moto Z3 Play beckham Brazilian model XT 1929-5. but checking bootloader and settings found that it is showing the incorrect SKU with the number TX1601, if I am not mistaken this number and the Moto G4 plus, there is a way to repair this, and the phone works perfectly running Android 9 Whoever can help will be grateful.
Click to expand...
Click to collapse
Me pasa lo mismo solo que estoy con Android 8.1 Parche de seguridad 1 de Setiembre de 2018 Compilacion OPWS28.70-31-2
Alguna solucion para poder actualizar?

l.rochas said:
Thanks for replying, as requested I will have a photo of the bootloader screen in this mode the sku is incorrect, and also the function barcodes in this, the sku is correct.
Another photo I took was from rsd lite shows an error of (the phone could not switch to fastboot mode) so I can just update the phone in Minimal ADB and Fastboot.
I'm sticking down the getvar all I did on adb walks fastboot
Click to expand...
Click to collapse
Did you tried to flash the ROMs i've posted here???

tb110188 said:
Did you tried to flash the ROMs i've posted here???
Click to expand...
Click to collapse
yes, I updated the rom as you mentioned it, and after restart it shows update of May 2019, but continues with the incorrect sku.

yes, the same as you posted with the May 2019 update.

Did you manage to solve the problem?

fashing_locked Moto G7 Plus

EN-US:
In short I can't flash on any official device rom, and the bootloader is unlocked, 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. (I can't go to any other screen besides fastboot)
Can anyone help me with this?
ps: I'm using the translator because I don't speak English.
PT-BR:
Resumidamente eu não consigo da flash em nenhuma rom oficial do dispositivo, e o bootloader esta desbloqueado, o que na verdade preciso habilitar e o OEM na opção do desenvolvedor.
Mais não consigo ligar o aparelho pois o celular diz está com um sistema operacional diferente, e volta para o fastboot. (Não consigo ir para nenhuma outra tela fora o fastboot)
Alguém pode me ajudar com isso?
ps: Eu tou usando o Tradutor pois não falo inglês.

PU Kirito LP said:
EN-US:
In short I can't flash on any official device rom, and the bootloader is unlocked, 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. (I can't go to any other screen besides fastboot)
Can anyone help me with this?
ps: I'm using the translator because I don't speak English.
PT-BR:
Resumidamente eu não consigo da flash em nenhuma rom oficial do dispositivo, e o bootloader esta desbloqueado, o que na verdade preciso habilitar e o OEM na opção do desenvolvedor.
Mais não consigo ligar o aparelho pois o celular diz está com um sistema operacional diferente, e volta para o fastboot. (Não consigo ir para nenhuma outra tela fora o fastboot)
Alguém pode me ajudar com isso?
ps: Eu tou usando o Tradutor pois não falo inglês.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
------------------
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-191220
(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: 0055749849
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 0F2A4B3E
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577096137011
(bootloader) meid:
(bootloader) date: 04-05-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C44559
(bootloader) battery-voltage: 4320
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:9/PPW29.98-
(bootloader) ro.build.fingerprint[1]: 28/b7d2f:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.31.31.lake.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g73ca513-0001
(bootloader) kernel.version[1]: 1-g007505b ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Dec 11 09:54:13 CST
(bootloader) kernel.version[4]: 2018
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9-191220
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-191220
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-191220
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-191220
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) frp-state: no protection (0)
(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.312s

PU Kirito LP said:
What does getvar all say?
------------------
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-191220
(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: 0055749849
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 0F2A4B3E
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577096137011
(bootloader) meid:
(bootloader) date: 04-05-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C44559
(bootloader) battery-voltage: 4320
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:9/PPW29.98-
(bootloader) ro.build.fingerprint[1]: 28/b7d2f:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.31.31.lake.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g73ca513-0001
(bootloader) kernel.version[1]: 1-g007505b ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Dec 11 09:54:13 CST
(bootloader) kernel.version[4]: 2018
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9-191220
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-191220
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-191220
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-191220
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) frp-state: no protection (0)
(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.312s
Click to expand...
Click to collapse
Says bootloader is locked.
Code:
securestate: flashing_locked
And baseband is missing
Code:
version-baseband: <not found>
Try using the unlock code again.
Sent from my ocean using XDA Labs
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
If that doesn't work see
https://forum.xda-developers.com/showpost.php?p=81614501&postcount=9
Sent from my ocean using XDA Labs

sd_shadow said:
Says bootloader is locked.
Code:
securestate: flashing_locked
And baseband is missing
Code:
version-baseband: <not found>
Try using the unlock code again.
Sent from my ocean using XDA Labs
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
If that doesn't work see
https://forum.xda-developers.com/showpost.php?p=81614501&postcount=9
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
check 'allow oem unlock' in android settings developer (bootloader) options.
is sending I enable, plus the internet does not pay for lack of the modem.
even if i use bluetooth to use internet, or use the pc to send internet to the cell phone i can't enable the OEM in the developer's option.

PU Kirito LP said:
Says bootloader is locked.
And baseband is missing
------------------
check 'allow oem unlock' in android settings developer (bootloader) options.
is sending I enable, plus the internet does not pay for lack of the modem.
even if i use bluetooth to use internet, or use the pc to send internet to the cell phone i can't enable the OEM in the developer's option.
Click to expand...
Click to collapse
Did you lock the bootloader or did it seem to lock it's self?
Sent from my ocean using XDA Labs

sd_shadow said:
Did you lock the bootloader or did it seem to lock it's self?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
-----------------
in this case I formatted the cell phone and the oem option was disabled. and now I can’t flash the roms anymore.

PU Kirito LP said:
-----------------
in this case I formatted the cell phone and the oem option was disabled. and now I can’t flash the roms anymore.
Click to expand...
Click to collapse
I think the only fix is boot into edl mode
Code:
fastboot oem blankflash
Then flash a blankflash
Sent from my ocean using XDA Labs

sd_shadow said:
I think the only fix is boot into edl mode
Code:
fastboot oem blankflash
Then flash a blankflash
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
But how do I do this? boot into edl mode
I never hear about that command just do I apply?
Code:
fastboot oem blankflash

PU Kirito LP said:
But how do I do this? boot into edl mode
I never hear about that command just do I apply?
Click to expand...
Click to collapse
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs

sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I will try to run tests later.

sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
None of the things on that page worked. I'm still in the same problem.

PU Kirito LP said:
------------------
None of the things on that page worked. I'm still in the same problem.
Click to expand...
Click to collapse
What things?
Sent from my ocean using XDA Labs

sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I tried everything that was here on this link but I was not successful.
I'm trying to activate the 'Unlock OEM from the developer option' by ADB Shell, since the wi-fi and the operator chip won't catch on.
But I haven't had much success yet, I just found some commands to enter developer mode via adb shell. But I found nothing on how to activate the Unlock OEM via ADB Shell.

PU Kirito LP said:
------------------
I tried everything that was here on this link but I was not successful.
I'm trying to activate the 'Unlock OEM from the developer option' by ADB Shell, since the wi-fi and the operator chip won't catch on.
But I haven't had much success yet, I just found some commands to enter developer mode via adb shell. But I found nothing on how to activate the Unlock OEM via ADB Shell.
Click to expand...
Click to collapse
Fastboot oem blankflash failed?
Sent from my ocean using XDA Labs

sd_shadow said:
Fastboot oem blankflash failed?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
Yes, it failed.

PU Kirito LP said:
------------------
Yes, it failed.
Click to expand...
Click to collapse
Dod you try to boot twrp?
Sent from my ocean using XDA Labs

sd_shadow said:
Dod you try to boot twrp?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I can go to Recovery mode, but I can't send TWRP to my cell phone.

i have been in exactly the same problem since last year,
Eu to com o mesmo problema desde o ano passado, e até hoje nao achei uma solução pro Flashing_locked

Coxinha2139 said:
i have been in exactly the same problem since last year,
Eu to com o mesmo problema desde o ano passado, e até hoje nao achei uma solução pro Flashing_locked
Click to expand...
Click to collapse
[PT-BR]
Estou com o mesmo problema, levei na assistência e foi diagnosticado com problema na memoria eMMC
[EN-US]
I have the same problem. Sent to technical assistance, and I was told that it is a hardware problem on eMMC memory.
{
"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"
}

Hard Bricked (EDL) moto g9 play XT2083-1

Help needed
My device is on EDL mode ( showing on device manager as Qualcomm HS-USB QDLoader 9008).
I tried every single blankfash file from lolinet and my device not booted.
Mine is the brazillian version (XT2083-1_GUAMP_RETBR).
Someone have the correct file for Blankflashing my device or other solution for my problem?
Thanks in advance.

Hello friend, I created a Blankflash based on the latest version of android 11 (RPX31.Q2-58-17-7), it worked for me, if you want to try it do it at your own risk, I am not responsible for any possible problems let it happen.

RMS100 said:
Hello friend, I created a Blankflash based on the latest version of android 11 (RPX31.Q2-58-17-7), it worked for me, if you want to try it do it at your own risk, I am not responsible for any possible problems let it happen.
Click to expand...
Click to collapse
Worked fine for me, thank you.

my phone also returned to image, what did you do after that?

vtrxz said:
my phone also returned to image, what did you do after that?
Click to expand...
Click to collapse
You can use this tool from motorola to flash the latest Stock Rom on your device: https://www.motorola.com/us/rescue-and-smart-assistant/p

Thank you very much, my phone is working again thanks to you

RMS100 said:
Olá amigo, criei um Blankflash baseado na última versão do android 11 (RPX31.Q2-58-17-7), funcionou para mim, se você quiser experimentar faça por sua conta e risco, não me responsabilizo por quaisquer problemas possíveis deixe acontecer.
Click to expand...
Click to collapse
God bless you my friend, save me a lot!!!

Hello, I had the same problem and managed to get out of EDL mode, but when trying to install the stock rom via fastboot, an error occurred and, in the failed attempt to solve it, I ended up blocking the bootloader. Now I have my device bricked and the bootloader is locked.
I've already used Rescue and Smart Assistant and it can't finish the process. I can't flash any roms through adb either. It really is a misfortune.
Below is the information about my device:
C:\Users\whoami\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamp_retail-252ee94a78-220503
(bootloader) product: guamp
(bootloader) board: guamp
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DP6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: 0073117509
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: B74625DD
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804464640
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 352234676210270
(bootloader) imei2: 352234676210288
(bootloader) meid:
(bootloader) date: 04-30-2021
(bootloader) sku: XT2083-1
(bootloader) carrier_sku: XT2083-1
(bootloader) battid: SB18C45530
(bootloader) battery-voltage: 3904
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/guamp_retail/guamp:11/RPX
(bootloader) ro.build.fingerprint[1]: 31.Q2-58-17-7/c9ebb:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-02200-KAMORTA.0
(bootloader) version-baseband: HA10_32.40.02.106R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[4]: pr 29 11:24:11 CDT 2022
(bootloader) git:xbl: MBM-3.0-guamp_retail-0ed29cb2f-220503
(bootloader) git:xbl_config: MBM-3.0-guamp_retail-0ed29cb2f-220503
(bootloader) git:abl: MBM-3.0-guamp_retail-252ee94a78-220503
(bootloader) git:rpm: MBM-3.0-guamp_retail-834e250d-220503
(bootloader) git:tz: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:hyp: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:devcfg: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:keymaster: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) git:storsec: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) git:uefisecapp: MBM-3.0-guamp_retail-4b088521-220503
(bootloader) gitrov: MBM-3.0-guamp_retail-2c435ecc4-220503
(bootloader) git:qupfw: MBM-3.0-guamp_retail-2c412ce-220503
(bootloader) frp-state: protected (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D19213
(bootloader) primary-display: hlt_ili9882h_video_display
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.125s

friend, I have the same problem, the motorola updated and the version of the blankflash that I need is the version RPXS31.Q2-58-17-7-2 I looked in several places on the internet and it really doesn't have it. help!

L1p3Droid_BR said:
friend, I have the same problem, the motorola updated and the version of the blankflash that I need is the version RPXS31.Q2-58-17-7-2 I looked in several places on the internet and it really doesn't have it. help!
Click to expand...
Click to collapse
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.

RMS100 said:
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.
Click to expand...
Click to collapse
yes, I tried but without success.

RMS100 said:
Did you try the blankflash that was made available here? maybe it still works as the latest Motorola update was just a security patch.
Click to expand...
Click to collapse
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retbr
{
"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"
}

L1p3Droid_BR said:
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retb
Click to expand...
Click to collapse
L1p3Droid_BR said:
follows the photo, but it does not restart to fastboot. it is version xt2083-3 retbrView attachment 5701121
Click to expand...
Click to collapse
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.

RMS100 said:
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.
Click to expand...
Click to collapse
the device does not turn on. even the cmd command saying that it was completed for fastboot, but it is false, it does not show any signal, it just exits edl mode only and unresponsive and does not recognize on the computer even with drivers and platform tools configured on the computer. It's a brick, it only enters edl at the moment, I believe only with the blankflash of the current version.

RMS100 said:
Ok, try this, download LSMA from motorola and try to run the fastboot commands with the device connected to the PC with the program already open. if the device is recognized, download the stock and install using the program.
Click to expand...
Click to collapse
Worse than I've done it using LMSA, I left it in the background and it's still not recognized.

L1p3Droid_BR said:
Worse than I've done it using LMSA, I left it in the background and it's still not recognized.
Click to expand...
Click to collapse
Hello friend, I didn't find a specific firmware for your model (XT2083-3), apparently the only difference between this model and the XT2083-1 is the NFC, so I made this blankflash based on the latest firmware of the model XT2083-1. If you want to try, do it at your own risk, I am not responsible for any problems.

RMS100 said:
Hello friend, I didn't find a specific firmware for your model (XT2083-3), apparently the only difference between this model and the XT2083-1 is the NFC, so I made this blankflash based on the latest firmware of the model XT2083-1. If you want to try, do it at your own risk, I am not responsible for any problems.
Click to expand...
Click to collapse
I tried, I didn't succeed. I tried, without success. this phone's software is hosted on lolinet. can you flash this software? Follow the link https://mirrors.lolinet.com/firmware/motorola/guamp/official/RETBR/

L1p3Droid_BR said:
Eu tentei, não tive sucesso. Eu tentei, sem sucesso. o software deste telefone está hospedado no lolinet. você pode mostrar este software? Siga o link https://mirrors.lolinet.com/firmware/motorola/guamp/official/RETBR/
Click to expand...
Click to collapse
Hi, I used exactly the firmware available on lolinet, I think unfortunately I can't do anything else for you.

RMS100 said:
Hi, I used exactly the firmware available on lolinet, I think unfortunately I can't do anything else for you.
Click to expand...
Click to collapse
Thank you for making yourself available to help. It went into Hard brick after deleting the vendor by passing a gsi. At least the blankflash created can help another forum member.

hello someones knows where are the edl points in moto g9 play? i putted in contacts a lot of places and i cant know the place