Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

Motorola Community

Unlockable PhonesMOTOROLA Android Developer Community
All Forum Topics
Options

28352 Posts

02-02-2016

United States of America

5842 Signins

132780 Page Views

  • Posts: 28352
  • Registered: ‎02-02-2016
  • Location: United States of America
  • Views: 132780
  • Message 6621 of 7044

Re: Bootloader Unlock Problems?

2020-02-10, 14:33 PM

 wrote:
Hi, I thought that my CID indicated a device that can be unlocked?

```
(bootloader) CID: 0x0032
```

See page 1 of this thread. 


* Search box is your friend * I don't respond to PM if question belongs in forum
Reply
Options

0 Posts

02-08-2020

United States of America

1 Signins

0 Page Views

  • Posts: 0
  • Registered: ‎02-08-2020
  • Location: United States of America
  • Views: 0
  • Message 6622 of 7044

Re: Bootloader Unlock Problems?

2020-02-10, 15:02 PM

First off, thank you Motorola / Lenovo staff for tending to this thread all these years and continuing to help users. I have two 2014 Motorola Moto X XT1096 phones that need their bootloaders unlocked to finally upgrade beyond Android 5.1.

I am confused by the information in the root post in this thread, as it appears to be contradictory in my case.

  1. First, the post states "VERIZON WIRELESS, ATT WIRELESS, AND REPUBLIC WIRELESS DEVICES ARE NOT ELIGIBLE FOR THE UNLOCKABLE BOOTLOADER PROGRAM." That's pretty clear, and tells me I'm S.O.L.
  2. Then, it lists  "Verizon 2014 Moto X XT1096" under exceptions.
  3. Then, on the page "What devices are supported by the Bootloader Unlock program?", this model is not listed. However, I don't take this to be gospel, because my XT1056 is definitely supported, but not on the list either.
  4. Finally, both of these phones list cid: 0x0002 in the bootloader variable dump.

So, are these phones eligible for unlocking? If so, then what does it take to get it done? Here's the complete dump from each of the phones:

XT1096 #1

[calvin(pts/5)@calvin-w500]$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6020
(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: TA99215ZF8
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: B67ED00B0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 990005080554919
(bootloader) meid:
(bootloader) date: 09-15-2014
(bootloader) sku: XT1096
(bootloader) iccid: 89148000001289148891
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Sep 14  5: 8:29 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_verizon/victara:5
(bootloader) ro.build.fingerprint[1]: .1/LPES23.32-25-5-5/3:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.221.5.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[0]: MSM8974BP_4235210.110.09.13R VICTARA_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gdd04463-00032-g1dc
(bootloader) kernel.version[1]: 8d38 (hudsoncm@ilclbld87) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Wed Sep 14 05:
(bootloader) kernel.version[3]: 05:37 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V60.20-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.20-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V60.20-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.20-0-gc8cfdbe
(bootloader) aboot.git: git=MBM-NG-V60.20-0-g78a2c4f
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: vzw
all: listed above
finished. total time: 0.055s

[calvin(pts/5)@calvin-w500]$ fastboot oem get_unlock_data
...
(bootloader) 9900050805549190#54413939323135
(bootloader) 5A463800585431303936000000#8BCD
(bootloader) 3C4E981032351D191896C954054E5F9
(bootloader) 0C087#B67ED00B0B000000000000000
(bootloader) 0000000
OKAY [  0.045s]
finished. total time: 0.045s

XT1096 #2

[calvin(pts/5)@calvin-w500]$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6020
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA9921DRH4
(bootloader) cid: 0x0002
(bootloader) channelid: 0x83
(bootloader) uid: 802E330D0B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 990005082416380
(bootloader) meid:
(bootloader) date: 01-21-2015
(bootloader) sku: XT1096
(bootloader) iccid: 89148000001486927626
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar  7  5:55:45 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/victara_verizon/victara:5
(bootloader) ro.build.fingerprint[1]: .1/LPES23.32-25-5-5/3:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.221.5.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[0]: MSM8974BP_4235210.110.09.13R VICTARA_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gdd04463-00032-g1dc
(bootloader) kernel.version[1]: 8d38 (hudsoncm@ilclbld87) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Wed Sep 14 05:
(bootloader) kernel.version[3]: 05:37 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V60.20-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.20-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V60.20-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.20-0-gc8cfdbe
(bootloader) aboot.git: git=MBM-NG-V60.20-0-g78a2c4f
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: vzw
all: listed above
finished. total time: 0.056s

[calvin(pts/5)@calvin-w500]$ fastboot oem get_unlock_data
...
(bootloader) 9900050824163800#54413939323144
(bootloader) 52483400585431303936000000#1D22
(bootloader) 28430CB26CF6CC145CB9E41C13BCEB9
(bootloader) 5552A#802E330D0B000000000000000
(bootloader) 0000000
OKAY [  0.046s]
finished. total time: 0.046s


Again, thank you for the many years of assistance in this thread.
Moderators: No, you're not imaginging an echo. This is the second time I tried posting this, after my first post mysteriously disappeared.

Reply
Options

28352 Posts

02-02-2016

United States of America

5842 Signins

132780 Page Views

  • Posts: 28352
  • Registered: ‎02-02-2016
  • Location: United States of America
  • Views: 132780
  • Message 6623 of 7044

Re: Bootloader Unlock Problems?

2020-02-10, 20:28 PM

@CalvinWalden,   

 

See the first sentences in red in post 1 - your phones are no longer supported for unlocking:

 

UPDATED LIST OF UNLOCKABLE PHONES in link right below (If your phone is not listed, there is no support for unlocking it)

 

https://support.motorola.com/us/en/solution/MS87215

 

 


* Search box is your friend * I don't respond to PM if question belongs in forum
Reply
Options

0 Posts

02-08-2020

United States of America

1 Signins

0 Page Views

  • Posts: 0
  • Registered: ‎02-08-2020
  • Location: United States of America
  • Views: 0
  • Message 6624 of 7044

Re: Bootloader Unlock Problems?

2020-02-10, 20:47 PM
Thank you for the reply. If that list is now the final determining factor for bootloader unlocking support, you should remove the extraneous/outdated information regarding XT1096, since it's contradictory and is what led me to post here in the first place.
Reply
Options

0 Posts

02-12-2020

United States of America

0 Signins

0 Page Views

  • Posts: 0
  • Registered: ‎02-12-2020
  • Location: United States of America
  • Views: 0
  • Message 6625 of 7044

Re: Bootloader Unlock Problems?

2020-02-12, 20:36 PM


c:\Windows\System32>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) 3A15880608702779#
(bootloader) 5A593232344658435633005854313731302D0000#
(bootloader) E8746454426E1399B293E388DAB3D2E316FD87F5#
(bootloader) 49270BAC000000000000000000000000
OKAY [  0.020s]
finished. total time: 0.020s

Reply
Options

0 Posts

02-16-2020

United States of America

0 Signins

0 Page Views

  • Posts: 0
  • Registered: ‎02-16-2020
  • Location: United States of America
  • Views: 0
  • Message 6626 of 7044

Re: Bootloader Unlock Problems?

2020-02-16, 2:03 AM

Hi there,

 

I'm having an issue getting the unlock info.

 

I've enabled developer options > OEM unlocking and USB debugging.

 

Output of getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2245MDDD
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: F6AA9E0200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354123070213758
(bootloader) meid:
(bootloader) date: 10-11-2017
(bootloader) sku: XT1622-DS
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Dec 22 9:32:40 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-23.4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.24.4.athene.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband[0]: M8952_70004.04.03.32R ATHENE_EMEA_DSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gcf01273 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld30) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Sat May 14 20:58:01 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.178s

 

So since to the CID value is 0x0000 it should be eligable for an unlock, however when i try "fastboot oem get_unlock_data" I only get this output:
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.110s]
finished. total time: 0.111s

 

I have tried to run this multiple times - disabling debugging and unlocking > restarting > turing those back but that also doesn't seem to work so I'm kinda at a loss here.

 

 

 

Also I apologize if this problem has showed up before but I didn't really see it come by (though I admit I haven't carefully read every post, just looked for anything that said unavailable).

Reply
Options

28352 Posts

02-02-2016

United States of America

5842 Signins

132780 Page Views

  • Posts: 28352
  • Registered: ‎02-02-2016
  • Location: United States of America
  • Views: 132780
  • Message 6627 of 7044

Re: Bootloader Unlock Problems?

2020-02-16, 15:35 PM

@REVERSEDSKIES

 

If the output of fastboot oem get_unlock_data shows unavailable/failed then service is needed. There is no way to provide an unlock code if that command fails.


* Search box is your friend * I don't respond to PM if question belongs in forum
Reply
Options

0 Posts

02-16-2020

United States of America

0 Signins

0 Page Views

  • Posts: 0
  • Registered: ‎02-16-2020
  • Location: United States of America
  • Views: 0
  • Message 6628 of 7044

Re: Bootloader Unlock Problems?

2020-02-16, 19:15 PM

Huh, interesting XD

what kind of service is necessary? I mean I don't think I still have warranty on this device but it seems a little weird that it needs service sine it's working fine 

Reply
Options

0 Posts

02-12-2020

United States of America

0 Signins

0 Page Views

  • Posts: 0
  • Registered: ‎02-12-2020
  • Location: United States of America
  • Views: 0
  • Message 6629 of 7044

Re: Bootloader Unlock Problems?

2020-02-17, 2:19 AM
hi,thanks for your reply.
my mobile z2play,when i add device to my stuff.the result is "you don't have any devices"
Reply
Options

28352 Posts

02-02-2016

United States of America

5842 Signins

132780 Page Views

  • Posts: 28352
  • Registered: ‎02-02-2016
  • Location: United States of America
  • Views: 132780
  • Message 6630 of 7044

Re: Bootloader Unlock Problems?

2020-02-17, 4:42 AM

 wrote:

Huh, interesting XD

what kind of service is necessary? I mean I don't think I still have warranty on this device but it seems a little weird that it needs service sine it's working fine 


Unsure as I have never needed it, but this is the official response. 


* Search box is your friend * I don't respond to PM if question belongs in forum
Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms