Moto Z3 Play with wrong SKU number - Moto Z3 Play Questions & Answers

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?

Related

Unlock bootloader moto x 2014 - XT1097

I recently bought this used cell phone, with android 5.1, I upgraded to the 6 stock (original motorola) but I now want to install a custom ROM, and for this I need to unlock the bootloader, but when I try to do this, this message appears in the command prompt "could Not get unlock data! ", I even tried a crazy on the internet some method to solve but what I found said that I should downgrade and go up rom, but I can not install another rom by RSD lite, I would like a method to be able Do the bootloader unlock and do root, exchange rom these things
roneyss93 said:
I recently bought this used cell phone, with android 5.1, I upgraded to the 6 stock (original motorola) but I now want to install a custom ROM, and for this I need to unlock the bootloader, but when I try to do this, this message appears in the command prompt "could Not get unlock data! ", I even tried a crazy on the internet some method to solve but what I found said that I should downgrade and go up rom, but I can not install another rom by RSD lite, I would like a method to be able Do the bootloader unlock and do root, exchange rom these things
Click to expand...
Click to collapse
You must have the unlock.bin from motorola official site to unlock bootloader.
After send the unlock.bin to your mail you move it to adb folder etc.
papsr6 said:
You must have the unlock.bin from motorola official site to unlock bootloader.
After send the unlock.bin to your mail you move it to adb folder etc.
Click to expand...
Click to collapse
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
roneyss93 said:
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
Click to expand...
Click to collapse
Did you enable Developer Options by going to Settings, About, tap Build Number 7 times, then go back, enable allow bootloader unlock and Android Debugging.
roneyss93 said:
The problem is that I do not even receive the code to unlock, before that happens it already appears that "could not get unlock data!" Which makes it impossible for me to unlock
Click to expand...
Click to collapse
Do it again you do something wrong.
I do the same and my fault is the wrong copy of numbers when i copy from commant window.
Gus Ghanem said:
Did you enable Developer Options by going to Settings, About, tap Build Number 7 times, then go back, enable allow bootloader unlock and Android Debugging.
Click to expand...
Click to collapse
I do exactly this, and it continues to give error
papsr6 said:
Do it again you do something wrong.
I do the same and my fault is the wrong copy of numbers when i copy from commant window.
Click to expand...
Click to collapse
I can not even get the numbers that we put on the Motorola site, I have unlocked Motorola before, however this nor give me the codes when I put the command to generate the codes
roneyss93 said:
I do exactly this, and it continues to give error
Click to expand...
Click to collapse
Do this just to get some info, no need to paste it here:
fastboot getvar all
In bootloader mode of course.
EDIT: You can get the latest fastboot and adb from here:
https://developer.android.com/studio/releases/platform-tools.html
Gus Ghanem said:
Do this just to get some info, no need to paste it here:
fastboot getvar all
In bootloader mode of course.
EDIT: You can get the latest fastboot and adb from here:
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Open again the CMD, the most updated according to the link that you sent me. And as a response the commands had this.
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: 6018
(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: 0432146139
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: EC13870C0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 353320060936783
(bootloader) meid:
(bootloader) date: 2014-10-24
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 5 12:11:27 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(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_42352121.25.09.24R VICTARA_S
(bootloader) version-baseband[1]: INGLELA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:44:51 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V60.18-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.18-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V60.18-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.18-0-g4ad5029
(bootloader) aboot.git: git=MBM-NG-V60.18-0-g3b3b501
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.229s
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot devices
0432146139 fastboot
D:\Programas\Celular\MOTO X 2\root\platform-tools>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Could not get unlock data!
OKAY [ 0.036s]
finished. total time: 0.036s
D:\Programas\Celular\MOTO X 2\root\platform-tools>
Remember that yes "OEM unlock" and "USB debugging" was enabled. As shown in the image.
Here is mine
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 1 15:55:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retca/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: ca.retca.en.CA
(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_42352121.25.09.24R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:53:00 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
Looks like your bootloader is older, but it shouldn't matter, I think I unlocked mine before the Android 6.0 update, I then relocked it, and unlocked it again a second time. I'm sure a lot of RETBR phones have been unlocked around here. I just can't see what the problem is. But don't try downgrading, you may brick the phone. I don't know what else to suggest. I'm sure you've installed the Motorola USB drivers, but I don't think that's the issue.
Try the Motorola (Lenovo) forums, you can submit your getvar to them, and they will send you an unlock code in a few days:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
Good Luck!
They have forums in Portugese.
Gus Ghanem said:
Here is mine
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno:
(bootloader) cid: 0x000E
(bootloader) channelid: 0x80
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-12-2015
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 1 15:55:30 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retca/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: ca.retca.en.CA
(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_42352121.25.09.24R VICTARA_R
(bootloader) version-baseband[1]: ETCA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:53:00 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: retca
Looks like your bootloader is older, but it shouldn't matter, I think I unlocked mine before the Android 6.0 update, I then relocked it, and unlocked it again a second time. I'm sure a lot of RETBR phones have been unlocked around here. I just can't see what the problem is. But don't try downgrading, you may brick the phone. I don't know what else to suggest. I'm sure you've installed the Motorola USB drivers, but I don't think that's the issue.
Click to expand...
Click to collapse
I also do not know what the problem, I even tried to do the downgrade but does not accept any other android pq is not unlocked the bootloader.

Is it possible?

I'm very new to this, but I have a Motorola E5 Cruise (Cricket) that's network locked, ...sent my info to several unlocking sites and even tried a few, but so far they haven't been able to help, or tried to help but refunded me.
Other than doing a 6 month contract with Cricket to get them to network unlock, what are my options? I'd like to use this phone, but with straight talk rather than Cricket.
Is firmware for the Play & Cruise compatible? Please advise. Thanks a million!!!
RLBuddi said:
I'm very new to this, but I have a Motorola E5 Cruise (Cricket) that's network locked, ...sent my info to several unlocking sites and even tried a few, but so far they haven't been able to help, or tried to help but refunded me.
Other than doing a 6 month contract with Cricket to get them to network unlock, what are my options? I'd like to use this phone, but with straight talk rather than Cricket.
Is firmware for the Play & Cruise compatible? Please advise. Thanks a million!!!
Click to expand...
Click to collapse
I don't know, but you want to be careful about flash firmware for different model.
I would try to unlock the bootloader first
https://forum.xda-developers.com/showpost.php?p=80035798&postcount=115
Then
Check the getvar info
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
Please post it here after you remove the IMEI line
Then you can compare software channels with the same model number
https://mirrors.lolinet.com/firmware/moto
If you find a retail software channel like RetUS
That is for the same model you might be able to
Either just flash the modem files
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Or the complete firmware
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
But this just a guess
Sent from my ali using XDA Labs
---------- Post added at 01:12 AM ---------- Previous post was at 01:09 AM ----------
If the bootloader cannot be unlocked
You might be able to just flash the modem files
But it would likely be less risky if bootloader is unlocked.
Sent from my ali using XDA Labs
C:\Adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY322XV4G5
(bootloader) cid: 0x0001
(bootloader) channelid: 0x89
(bootloader) uid: DBA1266E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 07-27-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: XT1921-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jan 4 6:42:31 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-157-28/2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.341.2.james_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_34.26.11.76R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-ga94d3a1 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Feb 4 05:47:07 CST
(bootloader) kernel.version[3]: 2020
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=cc1477e
(bootloader) devcfg.git: git=cc1477e
(bootloader) keymaster.git: git=cc1477e
(bootloader) cmnlib.git: git=cc1477e
(bootloader) cmnlib64.git: git=cc1477e
(bootloader) prov.git: git=cc1477e
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: cricket
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.363s
RLBuddi said:
C:\Adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 9
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY322XV4G5
(bootloader) cid: 0x0001
(bootloader) channelid: 0x89
(bootloader) uid: DBA1266E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 07-27-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: XT1921-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jan 4 6:42:31 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-157-28/2:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.341.2.james_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_34.26.11.76R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-ga94d3a1 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Feb 4 05:47:07 CST
(bootloader) kernel.version[3]: 2020
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=cc1477e
(bootloader) devcfg.git: git=cc1477e
(bootloader) keymaster.git: git=cc1477e
(bootloader) cmnlib.git: git=cc1477e
(bootloader) cmnlib64.git: git=cc1477e
(bootloader) prov.git: git=cc1477e
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: cricket
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.363s
Click to expand...
Click to collapse
Does this device still boot normally?
Sent from my ali using XDA Labs
sd_shadow said:
Does this device still boot normally?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Yes, it boots no problem. I tried flashing the retail firmware for the same phone. It realized there was a size difference or something. Got up to step 11 ......11-20 failed
I'd tried to flash the modem files using the posted instructions, flashing was success. Still oem locked
RLBuddi said:
Yes, it boots no problem. I tried flashing the retail firmware for the same phone. It realized there was a size difference or something. Got up to step 11 ......11-20 failed
I'd tried to flash the modem files using the posted instructions, flashing was success. Still oem locked
Click to expand...
Click to collapse
Oem locked is different from carrier locked.
It's still carrier locked?
Sent from my ali using XDA Labs
---------- Post added at 01:47 AM ---------- Previous post was at 01:45 AM ----------
If it's still carrier locked the thing to try is
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my ali using XDA Labs
sd_shadow said:
Oem locked is different from carrier locked.
It's still carrier locked?
Sent from my ali using XDA Labs
---------- Post added at 01:47 AM ---------- Previous post was at 01:45 AM ----------
If it's still carrier locked the thing to try is
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Sorry bout the delay, ....Yes, it's still carrier locked. Thanks for your help!! It is very much appreciated!!! Also, checked out the link you provided.
Motorola global site does not list E5 Cruise (XT1921 2) as one that can be bootloader unlocked. Can the bootloader still be unlocked anyway?
RLBuddi said:
Sorry bout the delay, ....Yes, it's still carrier locked. Thanks for your help!! It is very much appreciated!!! Also, checked out the link you provided.
Motorola global site does not list E5 Cruise (XT1921 2) as one that can be bootloader unlocked. Can the bootloader still be unlocked anyway?
Click to expand...
Click to collapse
Moto has never listed every model that can be unlocked.
The only way to really know is go through the unlock steps.
Sent from my jerry_cheets using XDA Labs
sd_shadow said:
Moto has never listed every model that can be unlocked.
The only way to really know is go through the unlock steps.
Sent from my jerry_cheets using XDA Labs
Click to expand...
Click to collapse
Follow unlocking steps from the Moto site? Or elsewhere?
RLBuddi said:
Follow unlocking steps from the Moto site? Or elsewhere?
Click to expand...
Click to collapse
Yes, Moto site and I have some info here
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Sent from my jerry_cheets using XDA Labs

Moto X4 - Payton XT1900-2 - fastboot working, adb not working - OEM_Locked - Help

Dear Members,
My friend Have Moto X4 (Out of Warranty) this phone popup always says "Close App". So he cannot use the phone.
We tried to repair the phone 2-3 shops. No one able to solve the issue.
I am new to Android, So I thought to watch some youtube videos and downgrade the OS.
So I tried to reduce the Android version to "PAYTON_RETAIL_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
My bad, I watched only some Youtube videos (munchy) and started the procedure from that video.
After those steps My phone Locked. I tried to get help from him but he says the following.
"your bootloader is locked ..nothing i can do to help". sorry.
I have product vairiant : payton XT1900-2 64GB P4.
Power ok, then "oem_locked".
I am using Windows 10.
Some more information
--------
C:\adb>fastboot devices
ZY224GVR4R fastboot
--------
Fastboot recognize the device. adb not working. I have the Unlock Code from Motorola. But I cannot use it.
C:\adb>fastboot oem unlock WDEJJDCG2WPXNSWBGRT7
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
mobile network not detected.
Tried with Wi-fi, the device search progress bar keeps on running. Didn't find the Hotspots/Wifi Router. There is no next button to proceed.
please advise me the next step. Thanks for the reply and your help.
I have the logs while the first attempt fails and erase everything.
Please help to use the phone. Thanks
patrickjjs said:
Dear Members,
My friend Have Moto X4 (Out of Warranty) this phone popup always says "Close App". So he cannot use the phone.
We tried to repair the phone 2-3 shops. No one able to solve the issue.
I am new to Android, So I thought to watch some youtube videos and downgrade the OS.
So I tried to reduce the Android version to "PAYTON_RETAIL_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
My bad, I watched only some Youtube videos (munchy) and started the procedure from that video.
After those steps My phone Locked. I tried to get help from him but he says the following.
"your bootloader is locked ..nothing i can do to help". sorry.
I have product vairiant : payton XT1900-2 64GB P4.
Power ok, then "oem_locked".
I am using Windows 10.
Some more information
--------
C:\adb>fastboot devices
ZY224GVR4R fastboot
--------
Fastboot recognize the device. adb not working. I have the Unlock Code from Motorola. But I cannot use it.
C:\adb>fastboot oem unlock WDEJJDCG2WPXNSWBGRT7
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
mobile network not detected.
Tried with Wi-fi, the device search progress bar keeps on running. Didn't find the Hotspots/Wifi Router. There is no next button to proceed.
please advise me the next step. Thanks for the reply and your help.
I have the logs while the first attempt fails and erase everything.
Please help to use the phone. Thanks
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Please post it here, and remove IMEI line
Sent from my Moto E (4) using Tapatalk
Thanks Shadow
sd_shadow said:
Run
Code:
fastboot getvar all
Please post it here, and remove IMEI line
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(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 (0)
(bootloader) serialno: ZY224GVR4R
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: A1A80AC4
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: ---------------
(bootloader) meid:
(bootloader) date: 12-16-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4270
(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-0e6e7ce-190409
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190409
(bootloader) git:tz: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:hyp: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:devcfg: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:keymaster: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) gitrov: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:storsec: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retin
(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: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.176s
C:\adb>
patrickjjs said:
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190409
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(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 (0)
(bootloader) serialno: ZY224GVR4R
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: A1A80AC4
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: ---------------
(bootloader) meid:
(bootloader) date: 12-16-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4270
(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-0e6e7ce-190409
(bootloader) git:xbl: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) gitmic: MBM-3.0-payton_retail-6b0c3d7-190409
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190409
(bootloader) git:tz: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:hyp: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:devcfg: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:keymaster: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) gitrov: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) git:storsec: MBM-3.0-payton_retail-4adda86-dirty-190409
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retin
(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: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.176s
C:\adb>
Click to expand...
Click to collapse
You cannot unlocked the bootloader unless
Oem unlock is allowed in dev options
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
Help through remote screen
sd_shadow said:
You cannot unlocked the bootloader unless
Oem unlock is allowed in dev options
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
Hi Shadow, Can you help through Team viewer or Anydesk, if possible.
Thanks
Process device information screen
patrickjjs said:
Hi Shadow, Can you help through Team viewer or Anydesk, if possible.
Thanks
Click to expand...
Click to collapse
Hi Shadow,
It pops up "Process device information screen " for more than 10 mins. It never returned anything.
Progress bar going on and going on.....
Tested with two times with Admin mode.
Any ideas.
Thanks
hello, could you solve your problem, for my adb if it works, that's why it returns the serial number in the command window, I think you are only trying to flash the wrong firmware, since it is not necessary to have the bootloader unlocked to flash via adb, you have to download a firmware xt1900-2 retail, regards
Solved?
patrickjjs said:
Hi Shadow,
It pops up "Process device information screen " for more than 10 mins. It never returned anything.
Progress bar going on and going on.....
Tested with two times with Admin mode.
Any ideas.
Thanks
Click to expand...
Click to collapse
Did you ever got it working? i'm probably on the same Scenario, tried a lot of stuff, but no sucess.

No IMEI after flashing the Stock from, Unable to Unlock the Bootloader

I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (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]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s
hamhaingaurav said:
I was happy using Pixel Experience but Some bugs are worrying me so A week back I thought to go back to stock oreo and downloaded the Official Firmware lastest version for my G5s Plus, I flashed it using fastboot commands and now the only issue is that I do not have any IMEI in my phone, No network and No Signal.
Only thing I am getting is my Carrier Name Jio4G also it is able to detect my phone number. IMEI is correctly being shown using this command "$ fastboot getvar imei" but my device is unable to detect it. I have tried several time flashing with fastboot commands and Lenovo Moto Software Assistant, nothing worked for me.
I have also tried to resintall Pixel Experience ROM but no IMEI(Imei 0). I have also tried several other roms like RR and AOSP Ex also Havoc OS, nothing worked for me. I have also tried to flash TWRP backup of my Stock ROM but still IMEI 0. For your information I have also tried Pixel Experience rom with erasing modemst1 and modemst2 method, nothing worked.
Finally I thought to take it to the Moto Service Center, they flashed my devices with their software, but no success of retrieving the IMEI, even worse they gave me one more issue, which is now I am unable to unlock the bootloader with my unlock key. When I try to unlock it it says, "Code validation failure with status 7". When I try to generate new unlock data it says "Unlock data unavailable (bootloader) Failed.
I am really worried for my device because this is my only device and I am a student , I can not afford a new phone right now.
I will really appreciate your help for my entire lifetime, this issue is really making me sick.
I am attaching my "fastboot getvar all" output-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322F8CL2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E320A71E00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: "I AM HIDDING THIS FOR SECURITY PURPOSE, BUT IMEI IS VISIBLE HERE"
(bootloader) meid:
(bootloader) date: 12-11-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 17 9:41:58 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (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]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=82f94af-dirty
(bootloader) devcfg.git: git=82f94af-dirty
(bootloader) keymaster.git: git=82f94af-dirty
(bootloader) cmnlib.git: git=82f94af-dirty
(bootloader) cmnlib64.git: git=82f94af-dirty
(bootloader) prov.git: git=82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g37f20e1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
Finished. Total time: 0.024s
Click to expand...
Click to collapse
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.
riyan65 said:
You just mess your device with locked bootloader, there are not many things that can be done with locked bootloader. But still you can try this method.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post77249207
And try to unlock the bootloader, with unlock bootloader there could be some hope of recovery.
Click to expand...
Click to collapse
Yes, I knwo there is an hope if i can unlock the bootloader, but the service center guy messed my device, I do not know how they flashed my device, they were flashing my device and said it is not turning on, i said okay return my device, i will flash it my self and after taking from them, i was trying to unlock the bootloader and I was getting the error "Code validation failure with status 7". I am also unable to get Unlock data.
What can i do now, is there any solution to it. Do i need to take my device to service center again ???
Try flashing april stock....then do the OTA update till August..
vivek1310yadav said:
Try flashing april stock....then do the OTA update till August..
Click to expand...
Click to collapse
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.
hamhaingaurav said:
Did it already and it have not solved my problem, There is one more issue on my phone, Whenever I flash my device with Retail and Retin verion it always shows my Harddware version as /x/x/x/x instead of PVT.
Go to settings>abount phone>hardware information then look at the version , in my case it is /x/x/x/x, because of which some of my sensors are not working.
My device is really messed up.
Click to expand...
Click to collapse
PM me..

Moto x4 corrupted

Moto X4 shows your device is corrupt it cant be trusted and will not boot. pls help I tried few methods but not worked.
arunyesudas03 said:
Moto X4 shows your device is corrupt it cant be trusted and will not boot. pls help I tried few methods but not worked.
Click to expand...
Click to collapse
Try LMSA's Rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
I tried rescue app first but it doesn't work.
I tried rescue app first but it doesn't work.
sd_shadow said:
Try LMSA's Rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
arunyesudas03 said:
I tried rescue app first but it doesn't work.
Click to expand...
Click to collapse
What error did you get?
What does getvar all say?
Code:
fastboot getvar all
sd_shadow said:
What error did you get?
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
Bro can you check the 3rd image
arunyesudas03 said:
Bro can you check the 3rd image
Click to expand...
Click to collapse
No the error with LMSA
sd_shadow said:
No the error with LMSA
Click to expand...
Click to collapse
sd_shadow said:
What error did you get?
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180328
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(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 (0)
(bootloader) serialno: ZY224FMS7V
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 351899080443617
(bootloader) meid:
(bootloader) date: 10-17-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 3775
(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: M660_7045.36.01.100R PAYTON_APACDSDS_CUST
(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-uefi-641a15b-180328
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180328
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-180328
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180328
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retin
(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.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
arunyesudas03 said:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180328
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(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 (0)
(bootloader) serialno: ZY224FMS7V
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 351899080443617
(bootloader) meid:
(bootloader) date: 10-17-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 3775
(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: M660_7045.36.01.100R PAYTON_APACDSDS_CUST
(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-uefi-641a15b-180328
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180328
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-180328
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180328
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retin
(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.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
Click to expand...
Click to collapse
I believe your only option is booting into EDL Mode and using a blankflash
Is my device in EDL Mode?
How to boot into EDL Mode
You will need to find a blankflash for "payton"
https://forum.xda-developers.com/c/moto-x4.6912/
sd_shadow said:
I believe your only option is booting into EDL Mode and using a blankflash
Is my device in EDL Mode?
How to boot into EDL Mode
You will need to find a blankflash for "payton"
https://forum.xda-developers.com/c/moto-x4.6912/
Click to expand...
Click to collapse
Ok let me check
Hi
While connecting my device it detect as usb controllers as unknown usb device(device descriptor request failed).
Not detecting under port as qd loader
arunyesudas03 said:
Moto X4 shows your device is corrupt it cant be trusted and will not boot. pls help I tried few methods but not worked.
Click to expand...
Click to collapse
Managed to solve?

Categories

Resources