XT1053 invalid CID - Moto X Q&A

My wife recently got a fitbit, and we were trying to connect it to her 2013 Moto X. After repeated failures, and attempts to connect the phone to other devices, other devices to the phone, and other phones to the fitbit, I concluded that there was a Bluetooth issue with the Moto X - it can't see other devices, and other devices can't see it either. A factory reset didn't help. The phone was using the stock ROM, never unlocked, never rooted. This was her first Bluetooth device, so we don't really know if Bluetooth ever worked.
With the phone long out of warranty, I decided to unlock the boot loader and flash the stock firmware. After successfully flashing the 'ghost' firmware (downloadable in another thread here, since the official firmware from Motorola's site fails with the stagefright update), Bluetooth still didn't work. At some point, the phone offered to install the stagefright update, which I allowed. After the update the phone rebooted into the boot loader, with a message "fastboot reason: invalid cid". The screen also indicates that the bootloader is now locked.
At this point, I can't get it to boot to any other screen. Fastboot devices can see the phone, though the device ID is now different than it was before flashing (is this normal?), but I can't do anything with it because it's locked. Fastboot oem get_unlock_data fails, as does fastboot oem unlock .
Am I screwed?
Sent from my SM-T713 using Tapatalk

UncleMike said:
My wife recently got a fitbit, and we were trying to connect it to her 2013 Moto X. After repeated failures, and attempts to connect the phone to other devices, other devices to the phone, and other phones to the fitbit, I concluded that there was a Bluetooth issue with the Moto X - it can't see other devices, and other devices can't see it either. A factory reset didn't help. The phone was using the stock ROM, never unlocked, never rooted. This was her first Bluetooth device, so we don't really know if Bluetooth ever worked.
With the phone long out of warranty, I decided to unlock the boot loader and flash the stock firmware. After successfully flashing the 'ghost' firmware (downloadable in another thread here, since the official firmware from Motorola's site fails with the stagefright update), Bluetooth still didn't work. At some point, the phone offered to install the stagefright update, which I allowed. After the update the phone rebooted into the boot loader, with a message "fastboot reason: invalid cid". The screen also indicates that the bootloader is now locked.
At this point, I can't get it to boot to any other screen. Fastboot devices can see the phone, though the device ID is now different than it was before flashing (is this normal?), but I can't do anything with it because it's locked. Fastboot oem get_unlock_data fails, as does fastboot oem unlock .
Am I screwed?
Sent from my SM-T713 using Tapatalk
Click to expand...
Click to collapse
Paste the results please..
fastboot getvar all

Here's the output from 'fastboot getvar all':
Code:
(bootloader) version-bootloader: 30BE(*)
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x6
(bootloader) secure: yes
(bootloader) mid: 026b
(bootloader) serialno: 47cc93b8
(bootloader) qe:
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: F9D920040C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Invalid CID
(bootloader) ro.build.date:
(bootloader) ro.build.id:
(bootloader) ro.build.tags:
(bootloader) ro.build.type:
(bootloader) ro.build.user:
(bootloader) ro.build.version.codename:
(bootloader) ro.build.version.incremental:
(bootloader) ro.build.version.release:
(bootloader) ro.mot.build.customerid:
(bootloader) ro.product.name:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) kernel.version:

Related

[Q] "Your device does not qualify for bootloader unlocking"

I've got a retail EU XT1068 Dual-SIM Moto G 2nd gen but can't get a bootloader unlock code via the Motorola website. The message I get is
Code:
Your device does not qualify for bootloader unlocking
I thought that a retail device would suffice! Does anyone know what the requirements are for eligibility?
Model: XT1068
Version: 21.11.14.titan_retaildsds.retaildsdsall.en.03 reteu
Buildnr: KXB21.85-14
The Motorola website is also confusing, redirecting back-and-forth between
motorola-global-portal.custhelp.com
motorola-global-en-uk.custhelp.com
motorola-global-en-roe.custhelp.com
I've used this [GUIDE]Unlock Bootloader - Moto G (2nd Gen) guide and tried the unlock pages both on the global custhelp portal as well as on the Global UK custhelp portal, used developer mode, USB debug, fastboot, mfastboot (returning the same device guid) but the result is always the same JS-alert/popup/error.
Thanks!
You probably entered the code wrong. Try removing the spaces in the code you entered if you copied it from cmd, worked for me.
123mucho said:
You probably entered the code wrong. Try removing the spaces in the code you entered if you copied it from cmd, worked for me.
Click to expand...
Click to collapse
Hi 123mucho. I did remove spaces and the (bootloader) headers. Checked to see that it was exactly 132 characters before submitting...
Exact samething happened to me, its so frustrating to see companies do something so simple, in a convuluted way.....why couldnt they simply have designed it in such a way where you download an app or program, and it simply unlocks it, without having to give personal identifiable information as the key to getting the unlock code.......warrenty doesnt trump right
Anyways, like i said, had the same issue, theres a motorola forum thread talking about it, giving a guide to adb, version numbers to find out if your particular phone is unlockable......mine was...........anyways long story short, went to sleep tried/re-pasted again the next day, and it worked, keep trying................although i did bring the matter up with requested details on that motorola thread, i didnt recieve any info from moto, but they very well could have done something server side, so if it goes to long without working, you might have to contact them, assuming your device is on the list
Heres the forum thread
https://forums.motorola.com/posts/132580d3df
You can find out if you should be eligible for the bootloader unlock by using the command
Code:
fastboot getvar all
The output will be something like
Code:
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4807(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: XX1X22XXXX
(bootloader) [B][COLOR="Red"]cid: 0x0007[/COLOR][/B]
(bootloader) channelid: 0x40
(bootloader) uid: FFF8F0060F000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359296055208640
(bootloader) meid:
(bootloader) date: 10-10-2014
(bootloader) sku: XT1068
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Nov 22 16:29:45 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.4/KXB21.85-14/9:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.14.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(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: MSM8626BP_1032.394.88.00R, EMEA_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g6c9aef2-00110-gd54
(bootloader) kernel.version[1]: 3d01 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .7 (GCC) ) #1 SMP PREEMPT Thu Jul 17 00:
(bootloader) kernel.version[3]: 47:37 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.07-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.07-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V48.07-0-g71b1aae-dirty
(bootloader) tz.git: git=MBM-NG-V48.07-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V48.07-0-ge875a20
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: XX1X22XXXX
(bootloader) sutinfo:
all: listed above
finished. total time: 0.052s
The cid is the important bit. The following CID values are eligible for a bootloader unlock, all other CIDs are not.
Code:
0x0000
0x0003
0x0007
0x0009
0x000B
0x000C
0x000D
0x000E
0x0014
0x00DE
As found on Motorola Forums post f2061da875. You can request assistance there as well if you can't unlock.
Will update post with success/failure.
In my case I needed to make sure I accessed the validator from the UK site (my phone was bought from the UK).
I can't post links on this forum as I'm still a new user, but on the Motorola Support Portal go to /a_id/87215/.
that troubles me too! Mine: xt1068 dual India version. Did you find the
way?
Not sure what brought about the change, but today it works on the UK support portal.
No clue which of these solved it for me
Message on Motorola forums
support request via custhelp portal
Registered device yesterday, daily batch-job?
Back-end restart at Motorola
edit: Message from Motorola forum moderators "@All users reporting receiving "does not qualify" since last night, the back-end has to be restarted. Please try now,"
Bergerac87 said:
In my case I needed to make sure I accessed the validator from the UK site (my phone was bought from the UK).
I can't post links on this forum as I'm still a new user, but on the Motorola Support Portal go to /a_id/87215/.
Click to expand...
Click to collapse
Thats interesting.........i wonder if a vpn would affect success's
I had the same problem and could only unlock by doing this: go to settings, moto id, sign in using your google account, go to motorola's website, sign in with the same account that you used on your phone, and then put the code for unlocking. After that i could unlock, good luck.
spiloss said:
I've got a retail EU XT1068 Dual-SIM Moto G 2nd gen but can't get a bootloader unlock code via the Motorola website. The message I get is
Code:
Your device does not qualify for bootloader unlocking
I thought that a retail device would suffice! Does anyone know what the requirements are for eligibility?
Model: XT1068
Version: 21.11.14.titan_retaildsds.retaildsdsall.en.03 reteu
Buildnr: KXB21.85-14
The Motorola website is also confusing, redirecting back-and-forth between
motorola-global-portal.custhelp.com
motorola-global-en-uk.custhelp.com
motorola-global-en-roe.custhelp.com
I've used this [GUIDE]Unlock Bootloader - Moto G (2nd Gen) guide and tried the unlock pages both on the global custhelp portal as well as on the Global UK custhelp portal, used developer mode, USB debug, fastboot, mfastboot (returning the same device guid) but the result is always the same JS-alert/popup/error.
Thanks!
Click to expand...
Click to collapse
Have you genrated the string????

[Q] issue unlocking bootloader

I have non-booting xt890 from South America (bought used in Europe, I think originally Argentina).
The phone stopped booting past the M logo (no idea why, it just started one day) so I tried to flash a stock Rom using RSD lite. It now boots to fastboot mode with "Fastboot Mode: Flash Failure"
I can access the phone using fastboot with "Minimal ADB and Fastboot". I want to unlock the bootloader so I can install a recovery and then flash Cynagonmod or another ROM or something to see if I can fix the phone.
I used the tool on the Motorola site and I get an error "Your device does not qualify for bootloader unlocking". I emailed the support but got no response.
Is this correct? If I run "fastboot getvar all" I get:
(bootloader) version-bootloader: 0x2025
(bootloader) product: smi
(bootloader) secure: yes
(bootloader) rom-key: motorola-key
(bootloader) model-id: 0268
(bootloader) cid: c
(bootloader) version: 0.5
(bootloader) uid: [redacted]
(bootloader) max-download-size: 104857600
(bootloader) emmc-size: 8GB
(bootloader) qe: qe 0/0
(bootloader) unlocked: no
(bootloader) is-warranty-void: no
(bootloader) ifwi: 42.26
(bootloader) cpu: Intel(R) Atom(TM) CPU Z2480 @ 2.00GHz
(bootloader) kernel: droidboot
(bootloader) battery: capacity: 62, voltage: 3884375, temperature: 310
(bootloader) modem-status: secure
all:
finished. total time: 0.371s
try to flash the ORIGINAL STOCK ROM of your Ri (the one that came's with the phone) with RDS Lite 6.1.5 and them unlock the bootloader to flash any other rom
chers

(bootloader) Could not get unlock data! on 2014 XT1095/TMo RMA Replacement

After a month Motorola finally admitted that my replacement 2013 Moto X was NOT ready for shipping, but that they had none to give me, and sent me a 2014 Moto X XT1095 TMoSIM unlocked model. However, this model gives me the following error:
fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.043s]
finished. total time: 0.047s
Is OEM Unlocking turned on in Developer Options? Yep. Am I sure it's an XT1095? (bootloader) sku: XT1095 Yep. What's my CID? (bootloader) cid: 0x0000.
I asked in the Motorola forums and was told that I have to send it back to get them to replace it. Clearly this thrills me to no end, but I figure I'd ask here before attempting that much fun. Is there anything I can do to get this pig to allow me to unlock the bootloader?
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(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: TA9890CTPK
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 3CB30D100B000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) date: 05-28-2015
(bootloader) sku: XT1095
First, turn on debugging mode. And then type 'fastboot oem unlock' from fastboot mode.
Sent from my XT1095 using Tapatalk
I had debugging mode on, and tha tcommand is what you enter with the unlock code, but I went in and did it all just not anyway.
(bootloader) fastboot oem unlock [ unlock code ]
Then the get_unlock_data command, still no dice.

Unlock and Root Moto E5 Play

Hi there everyone. This post of a question is going to be long. So, bear with me. A week ago I decided I wanted to unlock and root my Motorola E5 Play that I have been using with Consumer Cellular as the carrier for nearly a year. I have done this once before with my previous Android phone, so, naturally, I follow instructions to be found on websites, including those to be found on xda forums. The process did not go as expected. I installed the right Moto drivers on my laptop, installed adb utilities, got the Motorola unlock code via a portal to be found here on xda, and proceeded with the typical process. I can't remember all of the frustrations I had, but, basically, I ended up flashing the stock ROM for my phone just to get it usable again, and then discovered I had lost radio transceiver capabilities. I could not connect to Consumer Cellular's network to make or receive calls. The little icon for your cell signal strength was gone. I did a little reading on flashing necessary firmware for your phone's radio transceiver, but since I could find nothing about Consumer Cellular and the idea of going by specifications for my model phone and figuring it out without specific instructions seemed too much, I ultimately decided to buy a carrier unlocked model of my phone, take out the sim-card from my old phone and put it into the new phone. The new phone (or renewed should I say) was the exact same model of Moto E5 Play I had, it worked on the GSM networks, and so I have a working phone again. The only little problem was that, originally, the phone I just bought was an AT&T phone. So, I see the AT&T logo when I turn the phone on, and there are a couple of other quirks here and there, but once I backed up Android data to this phone from Google's Cloud everything was back. However, I still would like the benefits of a rooted smartphone, whether it be programs like SDMaid Pro having more access to clean your phone deeper, or being able to uninstall bloatware, customize boot up animations, etc.
So, after having screwed up as I did, I thought it might be best to pay a professional to unlock and root this newly bought renewed phone of mine. I tried making use of oneclickroot.com, but the operator there told me my phone is not eligible for OEM unlocking. This leads me to two requests of you guys here at xda. One of which may get this thread removed, and the other of which hopefully will be satisfied if this thread is not taken down due to the first request.
Request #1:
-------------------------
I know these phones are made with the capability of being unlocked. If it is not eligible for unlocking then it has something to do with the carrier. I know this because my previous phone (a Verizon Prepaid) was not eligible for unlocking when I got it years ago, but a nice and entrepreneurial Motorola employee looking to make a little money on the side over in China was gracious enough to email me the unlock code once I sent him $45 dollars via Paypal. So, if any of you know how to get my Consumer Cellular Moto E5 Play XT-1921-2 unlock code, be it this way, that way, or the other way, then, please, do tell.
Request #2:
--------------------------
I need some good instructions for unlocking and rooting this phone without screwing it up like I did the last one. If this involves extra steps like flashing needed firmware for the chipset the radio transceiver uses that is OK (I believe this model phone uses QualComm). I just need those steps spelled out and listed.
So, the grand goal here is an unlocked and rooted Motorola Android phone of mine. Relevant device information is below.
Model: Motorola E5 Play XT-1921-2
OS: Android 8.0.0 Oreo
Network: GSM
Carrier: Consumer Cellular
Radio Transceiver Chipset: Some version of QualComm
Baseband version: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
Build Number: OCPS27.91-157-15
Any help would be greatly appreciated.
***This question was originally posted by me in the general discussion area of xda forums for unlocking and not here like I was told should have been by a guy that replied to the question. I have reposted it here, and below I am including what he requested of me when the executing of the command "fastboot getvar all". The information returned by that command should be of help to whomever can assist me.***
>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: ZY323GTQV8
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 854514E600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359542090844190
(bootloader) meid:
(bootloader) date: 11-23-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: 6798BB
(bootloader) battid:
(bootloader) iccid: 89014103271819071604
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-157-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.16.james_a.a.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb838762-0007
(bootloader) kernel.version[1]: 1-g3aa9cf9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 12 02:30:49 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=083cf5f-dirty
(bootloader) devcfg.git: git=083cf5f-dirty
(bootloader) keymaster.git: git=083cf5f
(bootloader) cmnlib.git: git=083cf5f
(bootloader) cmnlib64.git: git=083cf5f
(bootloader) prov.git: git=083cf5f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: att
(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.396s
vindy1099 said:
Hi there everyone. This post of a question is going to be long. So, bear with me. A week ago I decided I wanted to unlock and root my Motorola E5 Play that I have been using with Consumer Cellular as the carrier for nearly a year. I have done this once before with my previous Android phone, so, naturally, I follow instructions to be found on websites, including those to be found on xda forums. The process did not go as expected. I installed the right Moto drivers on my laptop, installed adb utilities, got the Motorola unlock code via a portal to be found here on xda, and proceeded with the typical process. I can't remember all of the frustrations I had, but, basically, I ended up flashing the stock ROM for my phone just to get it usable again, and then discovered I had lost radio transceiver capabilities. I could not connect to Consumer Cellular's network to make or receive calls. The little icon for your cell signal strength was gone. I did a little reading on flashing necessary firmware for your phone's radio transceiver, but since I could find nothing about Consumer Cellular and the idea of going by specifications for my model phone and figuring it out without specific instructions seemed too much, I ultimately decided to buy a carrier unlocked model of my phone, take out the sim-card from my old phone and put it into the new phone. The new phone (or renewed should I say) was the exact same model of Moto E5 Play I had, it worked on the GSM networks, and so I have a working phone again. The only little problem was that, originally, the phone I just bought was an AT&T phone. So, I see the AT&T logo when I turn the phone on, and there are a couple of other quirks here and there, but once I backed up Android data to this phone from Google's Cloud everything was back. However, I still would like the benefits of a rooted smartphone, whether it be programs like SDMaid Pro having more access to clean your phone deeper, or being able to uninstall bloatware, customize boot up animations, etc.
So, after having screwed up as I did, I thought it might be best to pay a professional to unlock and root this newly bought renewed phone of mine. I tried making use of oneclickroot.com, but the operator there told me my phone is not eligible for OEM unlocking. This leads me to two requests of you guys here at xda. One of which may get this thread removed, and the other of which hopefully will be satisfied if this thread is not taken down due to the first request.
Request #1:
-------------------------
I know these phones are made with the capability of being unlocked. If it is not eligible for unlocking then it has something to do with the carrier. I know this because my previous phone (a Verizon Prepaid) was not eligible for unlocking when I got it years ago, but a nice and entrepreneurial Motorola employee looking to make a little money on the side over in China was gracious enough to email me the unlock code once I sent him $45 dollars via Paypal. So, if any of you know how to get my Consumer Cellular Moto E5 Play XT-1921-2 unlock code, be it this way, that way, or the other way, then, please, do tell.
Request #2:
--------------------------
I need some good instructions for unlocking and rooting this phone without screwing it up like I did the last one. If this involves extra steps like flashing needed firmware for the chipset the radio transceiver uses that is OK (I believe this model phone uses QualComm). I just need those steps spelled out and listed.
So, the grand goal here is an unlocked and rooted Motorola Android phone of mine. Relevant device information is below.
Model: Motorola E5 Play XT-1921-2
OS: Android 8.0.0 Oreo
Network: GSM
Carrier: Consumer Cellular
Radio Transceiver Chipset: Some version of QualComm
Baseband version: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
Build Number: OCPS27.91-157-15
Any help would be greatly appreciated.
***This question was originally posted by me in the general discussion area of xda forums for unlocking and not here like I was told should have been by a guy that replied to the question. I have reposted it here, and below I am including what he requested of me when the executing of the command "fastboot getvar all". The information returned by that command should be of help to whomever can assist me.***
>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: ZY323GTQV8
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 854514E600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359542090844190
(bootloader) meid:
(bootloader) date: 11-23-2018
(bootloader) sku: XT1921-2
(bootloader) carrier_sku: 6798BB
(bootloader) battid:
(bootloader) iccid: 89014103271819071604
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_a/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-157-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.16.james_a.a.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8920_21.11.11.63.02R JAMES_NA_ATT_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb838762-0007
(bootloader) kernel.version[1]: 1-g3aa9cf9 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 12 02:30:49 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=083cf5f-dirty
(bootloader) devcfg.git: git=083cf5f-dirty
(bootloader) keymaster.git: git=083cf5f
(bootloader) cmnlib.git: git=083cf5f
(bootloader) cmnlib64.git: git=083cf5f
(bootloader) prov.git: git=083cf5f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: att
(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.396s
Click to expand...
Click to collapse
First I would try LMSA's Flash Rescue option with device in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

Moto G2 XT1072 can't boot

Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
But all fail with "failed validation";
Unlock fails, but I cannot boot in Android to change mentioned option:
Code:
mfastboot-v2> .\mfastboot oem unlock XSVDURWNGOWYDFMGU5ZT
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.057s
RSD Lite to flash stock ROM doesn't see my device.
Rescue and Smart Assistant cannot proceed due to "missing version-baseband:" (see empty var listed below).
Code:
mfastboot-v2> .\mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4821
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2272TX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C96B590915000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 2
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from mot-charger boot mode
(bootloader) imei: 353310061467870
(bootloader) meid:
(bootloader) date: 04-28-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Sep 16 3: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.thea_reteu.
(bootloader) ro.build.version.full[1]: 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:
(bootloader) kernel.version[0]: Linux version 3.4.42-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Sat Sep 10 01:48:29 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.21-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.21-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.21-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.21-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.21-0-gd8d8d9e
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C2272TX
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.105s
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks
enricocava said:
Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
Click to expand...
Click to collapse
Sometimes the bootloader will relock, when using a custom recovery is used.
I'm not sure why usually when trying to install a rom.
It's very common, but it happens on many Moto devices.
enricocava said:
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
Click to expand...
Click to collapse
That will have made it worse.
enricocava said:
But all fail with "failed validation";
Unlocking fails with "Please allow OEM unlock from developer options", but Android is not booting so I cannot change it.
RSD Lite to flash stock ROM doesn't see my device.
Click to expand...
Click to collapse
RSD Lite doesn't work with Windows 9/10/11
Use XP/7
enricocava said:
Rescue and Smart Assistant cannot proceed due to "missing base version" (string is not correct, I'll chek it later).
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Thank you for your quick reply.
sd_shadow said:
RSD Lite doesn't work with Windows 9/10/11
Use XP/7
Click to expand...
Click to collapse
Colud it work on a Win7 on a Virtual machine or does it need direct access to USB ports? At the moment I have not an old Windows available.
sd_shadow said:
What does getvar all say?
Click to expand...
Click to collapse
I updated the original post.
sd_shadow said:
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
I missed this post, I'll take a look.
enricocava said:
Hi all,
I had a XT1072 with Android 6 and wanted to go back to 5 due to problems with GPS.
I unlocked the boot loader, flashed stock ROM with Android 6 and all was fine.
I next tried to flash stock ROM with Android 5 and was stuck in fast boot with errors like "invalid system image signature" or similar.
Next I messed around with TWRP, stock again, lock, unlock... a mess.
Now it's stuck in fastboot with status "LOCKED, status code 2" (0 is LOCKED, 3 UNLOCKED, 2 what is it?)
I tried flashing stock ROM both 5 and 6 in different versions:
RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETESALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
RETGBALL_XT1072_5.0.2_LXB22.99-24_cid7_subsidy-DEFAULT_CFC.xml
Motorola_Moto_G2_XT1072_MPB24.65-34_CID12_6.0
But all fail with "failed validation";
Unlock fails, but I cannot boot in Android to change mentioned option:
Code:
mfastboot-v2> .\mfastboot oem unlock XSVDURWNGOWYDFMGU5ZT
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.057s
RSD Lite to flash stock ROM doesn't see my device.
Rescue and Smart Assistant cannot proceed due to "missing version-baseband:" (see empty var listed below).
Code:
mfastboot-v2> .\mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4821
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2272TX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C96B590915000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 2
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from mot-charger boot mode
(bootloader) imei: 353310061467870
(bootloader) meid:
(bootloader) date: 04-28-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Sep 16 3: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.thea_reteu.
(bootloader) ro.build.version.full[1]: 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:
(bootloader) kernel.version[0]: Linux version 3.4.42-g495dfd8 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Sat Sep 10 01:48:29 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V48.21-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.21-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.21-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.21-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.21-0-gd8d8d9e
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C2272TX
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.105s
Do you have any suggestions to restore it?
Let me know if I can give you more information.
Thanks
Click to expand...
Click to collapse
Code:
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
This should be the correct firmware
https://mirrors-obs-2.lolinet.com/firmware/motorola/2015/thea/official/RETEU/
XT1072_THEA_RETEU_6.0_MPBS24.65-34-5_cid7_subsidy-DEFAULT_CFC.xml.zip
Try flashing
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then flash the firmware using the flash_file.xml as reference.
sd_shadow said:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/thea_reteu/thea:6.0/MPBS2
(bootloader) ro.build.fingerprint[1]: 4.65-34-5/6:user/release-keys
This should be the correct firmware
https://mirrors-obs-2.lolinet.com/firmware/motorola/2015/thea/official/RETEU/
XT1072_THEA_RETEU_6.0_MPBS24.65-34-5_cid7_subsidy-DEFAULT_CFC.xml.zip
Try flashing
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then flash the firmware using the flash_file.xml as reference.
Click to expand...
Click to collapse
Thank you, it worked! So the problem was the wrong fw version and messing up gpt with random commands, right?
For a downgrade I can follow this one, right? https://forum.xda-developers.com/t/guide-flashing-motorola-firmware.4042039/post-84863341
enricocava said:
Thank you, it worked! So the problem was the wrong fw version and messing up gpt with random commands, right?
Click to expand...
Click to collapse
I believe so
enricocava said:
For a downgrade I can follow this one, right? https://forum.xda-developers.com/t/guide-flashing-motorola-firmware.4042039/post-84863341
Click to expand...
Click to collapse
Do not downgrade unless the bootloader says unlocked again.
If the bootloader is reported as unlocked again,
sure you should be able to downgrade the firmware.

Categories

Resources