Database Develop

Moto X 2014, IMEI and Baseband unknown

Hi Guys,
I used the QPSC utility with my MOTO X through a COM port, and I have a correct IMEI! I followed this guide:
forum.xda-developers.com/showthread.php?t=1960918&page=16
If I execute:
fastboot getvar all (baseband empty!)
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA46600C1G
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: 5AF7AC0E0B000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359283050814168
(bootloader) meid:
(bootloader) date: 11-14-2014
(bootloader) sku: XT1092
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 5 23:56:35 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retde/victara:5.1
(bootloader) ro.build.fingerprint[1]: /LPE23.32-25.1/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.16.1.victara_retd
(bootloader) ro.build.version.full[1]: e.retdeall.en.DE
(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:
(bootloader) kernel.version[0]: Linux version 3.4.42-gac28f45 ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 8 15:03:58 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 1/1
Click to expand...
Click to collapse
I see that the correct IMEI is configured... so I don't understand why if I cannot see these info in the Settings -> about window and especially I cannot use any SIM!!
My actual rom is the original one: VICTARA_RETDE_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml
Do you have any idea please??

mrfabio80 said:
Hi Guys,
I used the QPSC utility with my MOTO X through a COM port, and I have a correct IMEI! I followed this guide:
forum.xda-developers.com/showthread.php?t=1960918&page=16
If I execute:
fastboot getvar all (baseband empty!)
C:\platform-tools>fastboot getvar all
I see that the correct IMEI is configured... so I don't understand why if I cannot see these info in the Settings -> about window and especially I cannot use any SIM!!
My actual rom is the original one: VICTARA_RETDE_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml
Do you have any idea please??
Click to expand...
Click to collapse
This section is for the MOTO X 2013 Ghost. You'll have better luck posting in the 2014 MOTO X section.
Sent from my Moto X using Tapatalk

Losing baseband after updating cyanogenmod

So, I recently aquired XT1092, rooted & flashed official CM13 succesfully via TWRP.
Then I tried to upgrade it in to latest nightly (20160311 -> 20160313) and I lost my baseband.
Same thing happened few days back, when I only booted into recovery and I had again missing baseband, after flashing stock I got it.
Restorign EFS-backup and/or flashing modem(s) didn't help, so I'm now running stock while figuring this out.
Any help?

Tatoro said:
So, I recently aquired XT1092, rooted & flashed official CM13 succesfully via TWRP.
Then I tried to upgrade it in to latest nightly (20160311 -> 20160313) and I lost my baseband.
Same thing happened few days back, when I only booted into recovery and I had again missing baseband, after flashing stock I got it.
Restorign EFS-backup and/or flashing modem(s) didn't help, so I'm now running stock while figuring this out.
Any help?
Click to expand...
Click to collapse
Could you post the results of the command:
fastboot getvars all
Please remove imei info from the results before you post them.
Sent from my XT1095 using Tapatalk

AGISCI said:
Could you post the results of the command:
fastboot getvars all
Please remove imei info from the results before you post them.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hi, output here:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: SERIAL
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: 38E138100B000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: IMEI
(bootloader) meid:
(bootloader) date: 05-11-2015
(bootloader) sku: XT1092
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Mar 13 22:31:39 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_reteu/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPE24.49-18/19:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.11.18.victara_ret
(bootloader) ro.build.version.full[1]: eu.reteuall.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_E
(bootloader) version-baseband[1]: MEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-ga9982b3-00002-g389
(bootloader) kernel.version[1]: e46b ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Tue Nov 3 16:0
(bootloader) kernel.version[3]: 0:01 CST 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: reteu

xt1096 moto x 2nd gen bricked

moto x 2nd gen
was trying to upgrade to marshmallow and the person i bought from gave me the xt1092 link. went on with it and now i have a paperweight stuck in fastboot mode.. tried restoring back to xt1096 via fastboot, mfastboot and rsdlite
while doing it i am getting version downgraded for primary gpt, hab error, invalid piv image
any guru who can provide any help would be appreciated
get var all data below
C:\Phone\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA99218ZUS
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: 2EEA0E0D0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 990005080698989
(bootloader) meid:
(bootloader) date: 10-18-2014
(bootloader) sku: XT1096
(bootloader) iccid: 89148000001390856408
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Nov 19 18:48:29 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/victara_verizon/victara:5
(bootloader) ro.build.fingerprint[1]: .0/LXE22.46-11/11:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.11.victara_ver
(bootloader) ro.build.version.full[1]: izon.verizon.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-ga88ac50 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Nov 20 04:01:54 CST 2014
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: vzw
all: listed above

Try unlocking your bootloader from motorola site, last o heared Verizon started too unlock bootloader of x2 from mototola site. If you can unlock bootloader do it and after that flash xt1092 rom it will pass through.
astalavistadear said:
moto x 2nd gen
was trying to upgrade to marshmallow and the person i bought from gave me the xt1092 link. went on with it and now i have a paperweight stuck in fastboot mode.. tried restoring back to xt1096 via fastboot, mfastboot and rsdlite
while doing it i am getting version downgraded for primary gpt, hab error, invalid piv image
any guru who can provide any help would be appreciated
get var all data below
C:\Phone\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA99218ZUS
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: 2EEA0E0D0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 990005080698989
(bootloader) meid:
(bootloader) date: 10-18-2014
(bootloader) sku: XT1096
(bootloader) iccid: 89148000001390856408
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Nov 19 18:48:29 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/victara_verizon/victara:5
(bootloader) ro.build.fingerprint[1]: .0/LXE22.46-11/11:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.11.victara_ver
(bootloader) ro.build.version.full[1]: izon.verizon.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-ga88ac50 ([email protected]
(bootloader) kernel.version[1]: ilclbld73) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Nov 20 04:01:54 CST 2014
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: vzw
all: listed above
Click to expand...
Click to collapse

Salik Iqbal said:
Try unlocking your bootloader from motorola site, last o heared Verizon started too unlock bootloader of x2 from mototola site. If you can unlock bootloader do it and after that flash xt1092 rom it will pass through.
Click to expand...
Click to collapse
its giving an error
"enable oem unlock from developer options"

bump

Did you go into developer options in settings and check oem unlock?
astalavistadear said:
bump
Click to expand...
Click to collapse

Archangel said:
Did you go into developer options in settings and check oem unlock?
Click to expand...
Click to collapse
Since he is stuck in fastboot, I assume not.
Just reflash stock whatever firmware you were on before you tried upgrading. You can do this with all fastboot commands. Your phone is far from a "paper weight" if you can still get into fastboot, most classify this as a "soft brick."
Instructions on flashing the stock firmware can be found on the Moto X FAQ. https://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769
Alternatively, I'm a huge fan of House of Moto: http://www.droidrzr.com/topic/61124-house-of-moto-43/ - automates a lot of the flashing process for you. I like to always have an install of House of Moto ready to roll incase of soft bricking.

xKroniK13x said:
Since he is stuck in fastboot, I assume not.
Just reflash stock whatever firmware you were on before you tried upgrading. You can do this with all fastboot commands. Your phone is far from a "paper weight" if you can still get into fastboot, most classify this as a "soft brick."
Instructions on flashing the stock firmware can be found on the Moto X FAQ. https://forum.xda-developers.com/moto-x-2014/help/wip-frequently-questions-moto-x-2014-t2876769
Alternatively, I'm a huge fan of House of Moto: http://www.droidrzr.com/topic/61124-house-of-moto-43/ - automates a lot of the flashing process for you. I like to always have an install of House of Moto ready to roll incase of soft bricking.
Click to expand...
Click to collapse
hi.. sorry for such a late and random reply... had been stuck in a family emergency
i am getting the same error by your methods..
failed- version downgraded for boot

astalavistadear said:
hi.. sorry for such a late and random reply... had been stuck in a family emergency
i am getting the same error by your methods..
failed- version downgraded for boot
Click to expand...
Click to collapse
Sounds like you probably aren't using the correct firmware version.

mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256352 KB)...
OKAY [ 9.646s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.762s

astalavistadear said:
hi.. sorry for such a late and random reply... had been stuck in a family emergency
i am getting the same error by your methods..
failed- version downgraded for boot
Click to expand...
Click to collapse
i flashed a wrong version earlier as the guy i bought from said it was ok to flash xt1092 on xt1096.. 1096 wasnt getting updates post lollipop... and was stuck... now when m trying to get 1096 to flash back... m stuck with these errors

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.

[SOLVED] Now no OEM Unlock for 7 days???

Two days ago I got my hands on a "mint" XT1925-6, and I'm still waiting for OEM Unlock to be un-grayed (available) in Dev Options.
I've nearly lost count of the number of Moto phones I've owned, rooted, bootloader-unlocked in the past 5-6 years. I've never had to wait more than one quick little WiFi connection before tapping OEM unlock.
I know this phone is unlockable because I've already got its unlock code, emailed to me straight from Motorola. So that question has been asked and answered. But I'm still waiting to be able to tap and enable OEM Unlock.
I found the verbage below in the Lenovo G6/Plus/Play support forum -- https://forums.lenovo.com/t5/Moto-G...lay-software-image/m-p/5077477?page=1#5317655
This question was asked concerning a G6 Play (XT1922), but I've also found this same answer for the XT1925 in other pages that I've since lost track of . . . to wit, how does one get the phone unlocked if the OEM bootloader unlock switch is greyed out.
Answer by 'Agent Rich' in the 2nd post (MY emphasis/caps/etc): "I've seen it before, it looks like the phone needs to have an active data connection for a WEEK for the OEM option [to] become available."
And then in the 4th post (the last one): "The phone needs to have an active data [connection] to help mitigate the risk of device being stolen and re-flashed."
". . . . . . to help mitigate the risk of device being stolen and re-flashed" . . . . . What kind of B.S. answer is that?
Does anybody have any kind of meaningful response to this horse****?
In the meantime I've disabled all the google junk and other useless stuff while keeping the phone on an "active data connection" (WiFi), in the (probably vain) hope that it won't be anywhere near a week before OEM gets enabled . . . . . . . . . . . . . .
Firmware version is PPS29.118-15-11-16; 'getvar all' shows CID 0x0032. Just to be sure, and despite the 'advice' from 'Agent Rich', is there anything else I can look at that might show the phone I have is not a genuine, official, carrier-unlocked/bootloader-unlockable XT1925-6?

NINE days and still waiting for OEM Unlocking to enable.
The phone IS unlockable according to Motorola. I've got the unlock code. XT1925-6, RetUS, CID 0x0032, everything says it's unlockable. Methinks something is fishy with this phone but I have no idea what. No clue at all.
--- fastboot getvar all (from "day 1" after an FDR) ---
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: [**********]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: AC94058600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [***************]
(bootloader) meid:
(bootloader) date: 05-03-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jul 25 14:56: 2 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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

I might try reflashing the firmware I downloaded through the Rescue program. Or maybe run an actual rescue through that software.

Moondroid said:
I might try reflashing the firmware I downloaded through the Rescue program. Or maybe run an actual rescue through that software.
Click to expand...
Click to collapse
The invalid slots are concerning.
I would reflash the firmware, then reconnect to the internet.

sd_shadow said:
The invalid slots are concerning.
I would reflash the firmware, then reconnect to the internet.
Click to expand...
Click to collapse
I see what you mean. I reflashed last night but didn't think to run getvar and compare. I just did that, again after reflashing FW downloaded through Lenovo Rescue and Smart Assistant, and those slots still show invalid . . .
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: [**********]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: AC94058600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [***************]
(bootloader) meid:
(bootloader) date: 05-03-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 4 17:30: 0 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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
Another thing: On this phone OEM Unlocking shows completely grayed out. But on another G6 (XT1925-6) that I picked up cheap in an eBay auction, the OEM Unlocking verbage is not grayed out. Just the button.
Edit/Add: Identical phones, exact same firmware. The second phone also shows those slots as Invalid.

getvar all from the second phone (the one that shows only the button disabled). I'm still looking for any differences . . .
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: ********DJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: FA6FB84D00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: *************19
(bootloader) meid:
(bootloader) date: 10-28-2018
(bootloader) sku: XT1925-6
(bootloader) carrier_sku: XT1925-6
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Sep 13 12: 0:16 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:9/PPS29.118-15-11
(bootloader) ro.build.fingerprint[1]: -16/3afd9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.4.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M450_23.31.10.89R ALI_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g19723945513
(bootloader) kernel.version[1]: 7-04290-gfb8faa3398e9 ([email protected]
(bootloader) kernel.version[2]: 71) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[3]: ase) (GCC) ) #1 SMP PREEMPT Thu Apr 23 1
(bootloader) kernel.version[4]: 1:51:22 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ali_retail-5e077487fa-200423
(bootloader) rpm.git: MBM-2.1-ali_retail-218e5afd-200423
(bootloader) tz.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) devcfg.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) keymaster.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) prov.git: MBM-2.1-ali_retail-f9b266cd30-200423
(bootloader) aboot.git: MBM-2.1-ali_retail-a49aaf13a93-200423
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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
PS: This getvar all is before I corrected the time to current.

Clarification on the images: The first image is from the second phone. The second image is from phone #1, the one I've had for 10 days and reflashed yesterday. I just double-checked on the phones themselves.

Phone #1 (100% gray):
emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5
Phone #2 (button only gray):
emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01

After taking a relaxing 4-day vacation I remembered a possible solution, which worked on the #2 phone (haven't tried it on #1):
-- FDR
-- Setup as new with Wireless enabled. I did this with Wifi turned on but without an actual working Internet connection. Apparently it just wants WiFi enabled.
-- Setting the date may or may not matter. I just went through the setup using "Skip" and "Next" liberally.
-- Enabled Developer Options and Presto, OEM Unlock was enabled. My previously requested Unlock Code then worked to unlock the bootloader.

I'm experiencing this exact same issue. The phone is a Motorola Edge 30 Neo XT2245-1. I just opened the product package, turned it on, used the Motorola website to request the bootloader unlock code (which I received via email, no problem), and then I found out that the "OEM unlock" checkbox in Android Settings > Developer options is shown but it's grayed out. It is completely grayed out, meaning both the text and the checkbox are grayed out. What I did afterwards was search XDA and found a couple of threads, most of them suggesting to do a factory reset (via the Android settings), which I did, but that didn't help.
I'm hoping now that it's simply a timer, and that I have to wait a few days before the checkbox starts working. The CID value is 50 (or hex 0x32), and I already received the bootloader unlock code, so I'm pretty sure it should be possible to liberate this phone without having to resort to (or waiting for new) privilege escalation exploits.
Will post in a few days whether it (the "OEM unlock" setting) becomes toggle-able. Feel free to nudge me if I forget to do so.

heisenbug#3141 said:
I'm experiencing this exact same issue. The phone is a Motorola Edge 30 Neo XT2245-1. . . .
Click to expand...
Click to collapse
2-3 weeks ago I went through this again with a Motorola One 5G Ace. I waited 8 days with nothing changing, finally tried a factory reset and voila. Unlock enabled.
There no longer seems to be any predictable method to this madness. Good luck, you'll get there eventually.

Moondroid said:
2-3 weeks ago I went through this again with a Motorola One 5G Ace. I waited 8 days with nothing changing, finally tried a factory reset and voila. Unlock enabled.
There no longer seems to be any predictable method to this madness. Good luck, you'll get there eventually.
Click to expand...
Click to collapse
That's wicked. Based on that, I guess it might be that, whether or not the "OEM unlock" will be toggle-able is decided at the time of the reset, or soon after the first successful internet connection has been established, and that this result is saved. In other words, the option perhaps won't become toggle-able afterwards. If that's true, it might even work to just simply try a factory reset every single day until it's toggle-able, because one of those days the (server-side) timer has elapsed. Or, if that theory proves to be false, then perhaps you need to wait at least N days and do a factory reset after having waited long enough. Time will tell. Anyhow, thanks for shining light on this! Really hoping for the best here.

It's unlocked now. The "OEM unlock" option became toggle-able today. It seems waiting is all you have to do after requesting the bootloader unlock code via the Motorola website.
For future reference, and for anyone stumbling upon this here:
I did the last factory reset about 4 days ago and from that moment on I just waited and checked every day whether the "OEM unlock" option was toggle-able or not. And when it was, I toggled it, heeded the well-known warnings, and used 'fastboot' to unlock it. I had the device a few days longer, so in total I waited about a week before being able to unlock it.
Also, in case anyone wonders, whether or not a SIM card is inserted should not matter if one's phone is an international (global) model, as those aren't carrier locked. My phone is an international model and the SIM card was not inserted while waiting for the "OEM unlock".
Whispering digits of pi to the phone also apparently doesn't matter.