Database Develop

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?

Moto Z3 Play Baseband no fount Imei Unknow

Hello everyone, I have a Moto Z3 Force XT1929-6 Latam Chile I had updated the firmware and after that the phone is working but the baseband is not found and the IMEI is unknow and of course there is no wi-fi and no carrier signal. I try with a lot of roms stock but i cant fix this. Some one can help me please?.. Thank you!!

leodechiloe said:
Hello everyone, I have a Moto Z3 Force XT1929-6 Latam Chile I had updated the firmware and after that the phone is working but the baseband is not found and the IMEI is unknow and of course there is no wi-fi and no carrier signal. I try with a lot of roms stock but i cant fix this. Some one can help me please?.. Thank you!!
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
DOnt work. Failed to connect or Doesn´t apropiate firmware .

I have the same problem "baseband not found"
no signal or wifi ... moto z3 play xt1929-6 beckham at & t MX ..... any solution? I already tried different roms both att and retail and it remains the same ..
I thought about using blankflash but I don't know how to do the procedure. any clues please?

Yayo70136 said:
I have the same problem "baseband not found"
no signal or wifi ... moto z3 play xt1929-6 beckham at & t MX ..... any solution? I already tried different roms both att and retail and it remains the same ..
I thought about using blankflash but I don't know how to do the procedure. any clues please?
Click to expand...
Click to collapse
Rayos! if u find the solution can post here?? i do the same, oka? ... mi zplay 3 is almost a
personal weapon

Yayo70136 said:
I have the same problem "baseband not found"
no signal or wifi ... moto z3 play xt1929-6 beckham at & t MX ..... any solution? I already tried different roms both att and retail and it remains the same ..
I thought about using blankflash but I don't know how to do the procedure. any clues please?
Click to expand...
Click to collapse
Cannot use a blankflash unless device is in emergency download mode (edl)
All a blankflash does is flash a bootloader, if the bootloader is corrupted.
It will not fix radio issues.
Sent from my Moto E (4) using Tapatalk

leodechiloe said:
Rayos! if u find the solution can post here?? i do the same, oka? ... mi zplay 3 is almost a
personal weapon
Click to expand...
Click to collapse
I currently found a solution partially ... Flash havoc os android 9 with twrp flash gaps and it gives me network and internet, everything works. Except motorcycle horn mod, it is a momentary solution in what is a solution since when flashing the stock rom it keeps leaving me without signal....
I was thinking about flashing the stock rom without the commands that eliminate the modem based on this configuration to see if it is possible that this way the problem is fixed, since in havoc os bluetooth did not work for me, so I flashed it directly from the stock rom and it worked It was repaired, so now I'm looking to do something similar with the modem aver if I'm lucky, although I don't know what the exact commands to achieve it would be ... I'll investigate further, I should find a solution !! Let me know if you recovered signal with. havoc os. You have to be persistent since sometimes it does not catch the signal, it tries with a clean installation.
Skip
fastboot flash modem NON-HLOS. bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I hope it works. I'll try as soon as I can.

great! thx 4 compart u approach!!

You can Fastboot flash all the imgs in the stock ROM. I believe it's only boot, and recovery that's needed, but might as well flash em all (3-4) to be safe. Then LMSA will recognize your device and recover it.
Alternatively, you can install one of the custom roms, then using TWRP, back up your EFS Partition to an SD card.
Then after installing Stock ROM, Fastboot twrp, and restore your EFS.

hello. i try with almost all rom for beckham, one for every variant from this site ( https://mirrors.lolinet.com/firmware/moto/beckham/official ), one for android 8.1 and the other for android 9, without lucky.. no simm , 4g and no wifi. I find that the base band exactly for my version is "Modem Version: M636_30.77.01.101R2 beckham latam custom" not present in lolinet, but present in a pay site (for tecnical people).my question is.. if i buy that rom because is the same version, the problem should fix'??. thankyou

Okey.. FIXED! In my case, Is just the band base version compatibility. I buy de oficial, oficial rom (exactly like say in the box.. in my case xt1929-6 P/N PA9T0016CL <--- this is the serial that u need find in the web). And voila! all oki doki.. Looking in this web, i a web for technik people (electric manual, especific roms stock, etc). 1.- http://www.ligtelgsm.com.br/downloads/class/index.php?p=file&idprog=9356 2.- https://www.firmwaredown.com.br/ ... in the sit 1.- i buy a little account. If u wee u exactly base band (i ask to people with the same phone and company phone-- they send me a screen impr) y can donwnload and up 4you. But, looking good, i have few megas more. GLuck

leodechiloe said:
Okey.. FIXED! In my case, Is just the band base version compatibility. I buy de oficial, oficial rom (exactly like say in the box.. in my case xt1929-6 P/N PA9T0016CL <--- this is the serial that u need find in the web). And voila! all oki doki.. Looking in this web, i a web for technik people (electric manual, especific roms stock, etc). 1.- http://www.ligtelgsm.com.br/downloads/class/index.php?p=file&idprog=9356 2.- https://www.firmwaredown.com.br/ ... in the sit 1.- i buy a little account. If u wee u exactly base band (i ask to people with the same phone and company phone-- they send me a screen impr) y can donwnload and up 4you. But, looking good, i have few megas more. GLuck
Click to expand...
Click to collapse
Hello, so you could solve it ??? I can't find the version for my cell phone !!! PA9T0000MX. Doesn't appear on the pages you mention ...

Yayo70136 said:
Hello, so you could solve it ??? I can't find the version for my cell phone !!! PA9T0000MX. Doesn't appear on the pages you mention ...
Click to expand...
Click to collapse
option 2. ask in face or somtehing what version they have.. I ask in facebook market. 128/6g Z3p - same company sailes. They send me one imprscreen, so, with the information aboud band base, looking for the roms.... Every rom in the description, have de band base number exact...
En español: pidele, pregunta a la gente de facebook market u otro medio que este vendiendo un telefono como el tuyo, x e modelo exacto, y en la compañia que podia funcionar (que sim acepta.. aqui en chile estan todos liberados para todas las compañias). Pidele que te envie un pantallazo de la banda de base, que version exacta es.. y ese numero, con punto y coma, lo buscas en las descripciones de las roms.. (que tienen.. con punto y coma.. exactamente el numero de la banda base detallado... y en base a eso buscas las rooms candidatas...) MI cellular es un xt1929-6 de banda de base M636_30.77.01.101R (modem version M636_30.77.01.101R), y la que baje e instale fue la rom para una xt1929-5 que tiene la misma version del modem.. o sea banda de base M636_30.77.01.101R.. Captas?
MI phone is a XT1929-6 SINGLE SIM but i fix with a xt1929-5 DUAL SIM room --> http://www.ligtelgsm.com.br/downloads/class/index.php?p=file&idprog=9356 because have the same band base.

leodechiloe said:
option 2. ask in face or somtehing what version they have.. I ask in facebook market. 128/6g Z3p - same company sailes. They send me one imprscreen, so, with the information aboud band base, looking for the roms.... Every rom in the description, have de band base number exact...
En español: pidele, pregunta a la gente de facebook market u otro medio que este vendiendo un telefono como el tuyo, x e modelo exacto, y en la compañia que podia funcionar (que sim acepta.. aqui en chile estan todos liberados para todas las compañias). Pidele que te envie un pantallazo de la banda de base, que version exacta es.. y ese numero, con punto y coma, lo buscas en las descripciones de las roms.. (que tienen.. con punto y coma.. exactamente el numero de la banda base detallado... y en base a eso buscas las rooms candidatas...) MI cellular es un xt1929-6 de banda de base M636_30.77.01.101R (modem version M636_30.77.01.101R), y la que baje e instale fue la rom para una xt1929-5 que tiene la misma version del modem.. o sea banda de base M636_30.77.01.101R.. Captas?
MI phone is a XT1929-6 SINGLE SIM but i fix with a xt1929-5 DUAL SIM room --> http://www.ligtelgsm.com.br/downloads/class/index.php?p=file&idprog=9356 because have the same band base.
Click to expand...
Click to collapse
Would you be so kind as to provide me with the commands I use to flash your device? thanks and greetings!

Yayo70136 said:
Would you be so kind as to provide me with the commands I use to flash your device? thanks and greetings!
Click to expand...
Click to collapse
Make a new text document. Paste:
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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot reboot
Rename you file.txt to file.bat. Cut in u room folder and click. Good Luck

exactly that problem is the one that occurred to me the bootloader is corrupt and does not allow me to update it with any rom so I cannot repair the radio signal of my phone so I thought I would use the blankflash file to repair the boot loader and be able to update with stock rom but I don't know how a hard brick could be caused in my moto z3 play currently, I can enter fastboot mode and flash any rom beckham and the cell phone works but without signal and without wifi: / any ideas ??? Any help is appreciated !!!! I've been like this for almost a month!:crying:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(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: SDM636 1.0 (1)
(bootloader) serialno: ZY2...........
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 1FB614B6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ..................
(bootloader) meid:
(bootloader) date: 09-14-2018
(bootloader) sku: XT1929-6
(bootloader) carrier_sku: XT1929-6
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 3890
(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-22/d2da2:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.271.29.beckham.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gebfe3c50a253
(bootloader) kernel.version[1]: -02598-g4bfe89b274ac ([email protected]
(bootloader) kernel.version[2]: 2) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Thu Mar 12 22
(bootloader) kernel.version[4]: :35:14 CDT 2020
(bootloader) git:abl: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) git:xbl: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) gitmic: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) git:rpm: MBM-3.0-beckham_sprint-33b79ec-190708
(bootloader) git:tz: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:hyp: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:devcfg: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib64: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:keymaster: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) gitrov: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:storsec: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: attmx
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.146s
sd_shadow said:
Cannot use a blankflash unless device is in emergency download mode (edl)
All a blankflash does is flash a bootloader, if the bootloader is corrupted.
It will not fix radio issues.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse

Yayo70136 said:
exactly that problem is the one that occurred to me the bootloader is corrupt and does not allow me to update it with any rom so I cannot repair the radio signal of my phone so I thought I would use the blankflash file to repair the boot loader and be able to update with stock rom but I don't know how a hard brick could be caused in my moto z3 play currently, I can enter fastboot mode and flash any rom beckham and the cell phone works but without signal and without wifi: / any ideas ??? Any help is appreciated !!!! I've been like this for almost a month!:crying:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(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: SDM636 1.0 (1)
(bootloader) serialno: ZY2...........
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 1FB614B6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ..................
(bootloader) meid:
(bootloader) date: 09-14-2018
(bootloader) sku: XT1929-6
(bootloader) carrier_sku: XT1929-6
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 3890
(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-22/d2da2:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.271.29.beckham.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gebfe3c50a253
(bootloader) kernel.version[1]: -02598-g4bfe89b274ac ([email protected]
(bootloader) kernel.version[2]: 2) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Thu Mar 12 22
(bootloader) kernel.version[4]: :35:14 CDT 2020
(bootloader) git:abl: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) git:xbl: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) gitmic: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) git:rpm: MBM-3.0-beckham_sprint-33b79ec-190708
(bootloader) git:tz: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:hyp: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:devcfg: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib64: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:keymaster: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) gitrov: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:storsec: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: attmx
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.146s
Click to expand...
Click to collapse
Doesn't sound like a corrupted bootloader.
Sounds like mismatched modem firmware.
Bit if you want to flash the blankflash, flash twrp,
Look for reboot to edl or use
Code:
adb reboot edl

I appreciate your prompt response but it doesn't seem to work! I think that if the bootloader was damaged because before it flashed other roms and they started! now they do not go beyond the motorola logo. (havoc os, RR, etc all install without errors but when rebooting it does not go beyond the logo and goes into infinite loop rebooting. I thought that the version of the bootloader is the last one to update and I cannot return the command fastboot flash bootloader bootloader. img always fails with each and every one of the roms that I have tried to flash ... for this reason I was thinking of starting from 0 with blankflash ... but in reality I don't know if it works ..... you seem to know more than I do. idea ?? motorola smart assistant does not recognize the cell phone !!! It is worth mentioning that I am from Mexico operator att version PA9T0000MX .... greetings from a distance!
C:\adb>fastboot reboot edl
fastboot: usage: unknown reboot target edl
C:\adb>adb fastboot reboot edl
adb.exe: unknown command fastboot
C:\adb>adb reboot edl
error: no devices/emulators found
sd_shadow said:
Doesn't sound like a corrupted bootloader.
Sounds like mismatched modem firmware.
Bit if you want to flash the blankflash, flash twrp,
Look for reboot to edl or use
Code:
adb reboot edl
Click to expand...
Click to collapse

Yayo70136 said:
I appreciate your prompt response but it doesn't seem to work! I think that if the bootloader was damaged because before it flashed other roms and they started! now they do not go beyond the motorola logo. (havoc os, RR, etc all install without errors but when rebooting it does not go beyond the logo and goes into infinite loop rebooting. I thought that the version of the bootloader is the last one to update and I cannot return the command fastboot flash bootloader bootloader. img always fails with each and every one of the roms that I have tried to flash ... for this reason I was thinking of starting from 0 with blankflash ... but in reality I don't know if it works ..... you seem to know more than I do. idea ?? motorola smart assistant does not recognize the cell phone !!! It is worth mentioning that I am from Mexico operator att version PA9T0000MX .... greetings from a distance!
C:\adb>fastboot reboot edl
fastboot: usage: unknown reboot target edl
C:\adb>adb fastboot reboot edl
adb.exe: unknown command fastboot
C:\adb>adb reboot edl
error: no devices/emulators found
Doesn't sound like a corrupted bootloader.
Sounds like mismatched modem firmware.
Bit if you want to flash the blankflash, flash twrp,
Look for reboot to edl or use
Click to expand...
Click to collapse
While twrp is booted?
Sent from my ali using XDA Labs

I am using platform tools I use "fastboot reboot edl" and nothing happens. I don't understand what you mean by "while twrp starts" ??
or maybe you mean write command in twrp terminal ???
sd_shadow said:
While twrp is booted?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse

Baseband not found on Moto X4 Lineage Os 17.1

Good Day! After an unsuccessful attempt to install the Moto X4 rom stock, Now my smartphone does not work the SIM2, only SIM1 and when I start bootloader mod show the message "Baseband <not found>. I know I screwed up using a command at the wrong time, but any command I try to run on fastboot doesn't work. It just says "sending" without finishing the procedure. Several times I execute the commands to try to repair modem1 or modem2 but only an error message appears. The same messages that appeared when I tried to return with the rom stock. can anybody help me? I also tried to install twrp, but I also can't, this device only works with lineage recovery?

wmazoni said:
Good Day! After an unsuccessful attempt to install the Moto X4 rom stock, Now my smartphone does not work the SIM2, only SIM1 and when I start bootloader mod show the message "Baseband <not found>. I know I screwed up using a command at the wrong time, but any command I try to run on fastboot doesn't work. It just says "sending" without finishing the procedure. Several times I execute the commands to try to repair modem1 or modem2 but only an error message appears. The same messages that appeared when I tried to return with the rom stock. can anybody help me? I also tried to install twrp, but I also can't, this device only works with lineage recovery?
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

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
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-a5ca046-190905
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0043770743
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: E2812B5D
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 359552086827919
(bootloader) meid:
(bootloader) date: 02-02-2018
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4347
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (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]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-a5ca046-190905
(bootloader) git:xbl: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:pmic: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190905
(bootloader) git:tz: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:hyp: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:devcfg: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:keymaster: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:prov: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:storsec: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.092s
Hi!!This is the message after you type the command

wmazoni said:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-a5ca046-190905
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0043770743
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: E2812B5D
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 359552086827919
(bootloader) meid:
(bootloader) date: 02-02-2018
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4347
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (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]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-a5ca046-190905
(bootloader) git:xbl: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:pmic: MBM-3.0-payton_retail-d45d20b-190905
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190905
(bootloader) git:tz: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:hyp: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:devcfg: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:keymaster: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:prov: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) git:storsec: MBM-3.0-payton_retail-e7821e0-190905
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.092s
Hi!!This is the message after you type the command
Click to expand...
Click to collapse
You are using this firmware?
https://mirrors.lolinet.com/firmware/moto/payton/official/RETBR/
XT1900-6_PAYTON_RETBR_9.0_PPWS29.69-26-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

I am using Lineage OS 17.1. I can t install stock rom on my device. Do you think its work if i try install this firmware?
Enviado de meu Moto X4 usando o Tapatalk

wmazoni said:
I am using Lineage OS 17.1. I can t install stock rom on my device. Do you think its work if i try install this firmware?
Enviado de meu Moto X4 usando o Tapatalk
Click to expand...
Click to collapse
Try just theses from stock version you were using.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my jerry_cheets using XDA Labs

sd_shadow said:
Try just theses from stock version you were using.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my jerry_cheets using XDA Labs
Click to expand...
Click to collapse
In the first command I already get an error message:
https://www.dropbox.com/s/om4mz3us0ers85q/Anotação 2020-09-08 191819.jpg?dl=0

wmazoni said:
Try just theses from stock version you were using.
In the first command I already get an error message:
https://www.dropbox.com/s/om4mz3us0ers85q/Anotação 2020-09-08 191819.jpg?dl=0
Click to expand...
Click to collapse
You may need to change active slot.
Flash
Then change back
Try this to see if slot changes.
Code:
fastboot getvar current-slot
fastboot set_active other
fastboot getvar current-slot
Sent from my ocean using XDA Labs

sd_shadow said:
You may need to change active slot.
Flash
Then change back
Try this to see if slot changes.
Code:
fastboot getvar current-slot
fastboot set_active other
fastboot getvar current-slot
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
The command show active b see the command below pls:
https://www.dropbox.com/s/kebh9oot54o8jqj/Anotação 2020-09-08 224144.jpg?dl=0

wmazoni said:
The command show active b see the command below pls:
https://www.dropbox.com/s/kebh9oot54o8jqj/Anotação 2020-09-08 224144.jpg?dl=0
Click to expand...
Click to collapse
Try changing it to slot a using these commands
https://forum.xda-developers.com/showpost.php?p=71987324&postcount=8
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Try changing it to slot a using these commands
https://forum.xda-developers.com/showpost.php?p=71987324&postcount=8
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi. Now I got to change slot to a.
https://www.dropbox.com/s/2kxb77p5g2...13749.jpg?dl=0
However, I still find an error when I type the following commands, the command does not end:
https://www.dropbox.com/s/e00igqsicq...14453.jpg?dl=0

@sd_shadow, I am running LOS 18.1, without major issue, but my cell signal isn't fantastic. Could just be the chips in the phone, I don't know. I was thinking of flashing the modem from the latest RETUS firmware using your directions from #6. But 1) I think I started off with the stock ROM from a few months earlier and 2) I'd like to not totally screw up my LOS installation. Of course, I can try a backup, but I've never really gotten one restored successfully. Is trying to do this likely to break things?

JimDandy68 said:
@sd_shadow, I am running LOS 18.1, without major issue, but my cell signal isn't fantastic. Could just be the chips in the phone, I don't know. I was thinking of flashing the modem from the latest RETUS firmware using your directions from #6. But 1) I think I started off with the stock ROM from a few months earlier and 2) I'd like to not totally screw up my LOS installation. Of course, I can try a backup, but I've never really gotten one restored successfully. Is trying to do this likely to break things?
Click to expand...
Click to collapse
Just flashing the radio is pretty safe.

sd_shadow said:
Just flashing the radio is pretty safe.
Click to expand...
Click to collapse
Thanks. I suppose I can also reflash from the earlier stock if the most recent causes problems. I'll also be sure to check my slots. Do you flash to both slots or only one?

Moto G7 Plus XT1965-2 NO deja desbloquear el Bootloader

Hola, tengo problemas con Moto G7 Plus XT1965 - 2, No deja desbloquear el bootloader...que puedo hacer?...saludos ( como puedo subir imagenes?)

Makero said:
Hola, tengo problemas con Moto G7 Plus XT1965 - 2, No deja desbloquear el bootloader...que puedo hacer?...saludos ( como puedo subir imagenes?)
Click to expand...
Click to collapse
English only on XDA.
Translation
,
Hi, I have problems with Moto G7 Plus XT1965 - 2, it won't allow the bootloader to unlock ... what can I do?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk

Fastboot getvar all??
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(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: ZY225CGC7R
(bootloader) cid: 0x0032
(bootloader) channelid: 0x04
(bootloader) uid: 0226B216
(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: 355576092458736
(bootloader) meid:
(bootloader) date: 01-31-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C35581
(bootloader) battery-voltage: 3809
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPW30.61
(bootloader) ro.build.fingerprint[1]: -21/cb81e: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 D
(bootloader) kernel.version[3]: ec 20 22:19:05 CST 2019
(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 (0)
(bootloader) ro.carrier: amxcl
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(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: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.178s
,
What does getvar all say?
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk[/QUOTE]

Makero said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(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: ZY225CGC7R
(bootloader) cid: 0x0032
(bootloader) channelid: 0x04
(bootloader) uid: 0226B216
(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: 355576092458736
(bootloader) meid:
(bootloader) date: 01-31-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C35581
(bootloader) battery-voltage: 3809
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPW30.61
(bootloader) ro.build.fingerprint[1]: -21/cb81e: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 D
(bootloader) kernel.version[3]: ec 20 22:19:05 CST 2019
(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 (0)
(bootloader) ro.carrier: amxcl
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(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: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.178s
,
What does getvar all say?
Click to expand...
Click to collapse
You cid looks good
https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809
You enabled OEM unlocking in dev options?
Sent from my payton_sprout using XDA Labs

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