[Q] Moto X Device UNLOCKED Status Code 1 - Moto X Q&A

I did buy an moto x from eBay couple of weeks ago and it say Device UNLOCKED Status Code 1 in the Fastboot Mode ...I cannot make any sense of it since all of the Moto X have the status code 3,not 1. Also it has on extra option in Fastboot menu Switch console [NULL: null]. othe thing is when I run Command Fastboot erase all it erases allot of partition on the phone,and not just a few like in the rest of the Moto X ...The only problem that i have is that the IMEI is missing and it cannot be used to make any kind of phone calls Does anybody knows anything about this issue and explain to me what is the deal with it? Any help is much appreciated

DejanPet said:
I did buy an moto x from eBay couple of weeks ago and it say Device UNLOCKED Status Code 1 in the Fastboot Mode ...I cannot make any sense of it since all of the Moto X have the status code 3,not 1. Also it has on extra option in Fastboot menu Switch console [NULL: null]. othe thing is when I run Command Fastboot erase all it erases allot of partition on the phone,and not just a few like in the rest of the Moto X ...The only problem that i have is that the IMEI is missing and it cannot be used to make any kind of phone calls Does anybody knows anything about this issue and explain to me what is the deal with it? Any help is much appreciated
Click to expand...
Click to collapse
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831

KidJoe said:
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831
Click to expand...
Click to collapse
A picture can say a million words.. Thanks a lot KidJoe for the reply

DejanPet said:
A picture can say a million words.. Thanks a lot KidJoe for the reply
Click to expand...
Click to collapse
Exactly what model do you have? What is stamped on the back of the phone in the FINE PRINT?
Based on those shots... 161.44.25 is XT1053 4.4.2. 30.B7 is 4.4.2 bootloader.
BUT as you can see, similar to those other threads, your phone reports...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
And your IMEI and SKU are all zeros...
I'm not sure how phones are getting into this state. And I don't have a fool proof way to fix them.

it is probably one of those "motorola confidential property" tagged phones used by company staff only, it may have been leaked into market, it often has unlocked bootloader like developer edition phones. it is a pre release phone with extra functions (that are not in mass production versions)

KidJoe said:
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831
Click to expand...
Click to collapse
DejanPet said:
A picture can say a million words.. Thanks a lot KidJoe for the reply
Click to expand...
Click to collapse
KidJoe said:
Exactly what model do you have? What is stamped on the back of the phone in the FINE PRINT?
Based on those shots... 161.44.25 is XT1053 4.4.2. 30.B7 is 4.4.2 bootloader.
BUT as you can see, similar to those other threads, your phone reports...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
And your IMEI and SKU are all zeros...
I'm not sure how phones are getting into this state. And I don't have a fool proof way to fix them.
Click to expand...
Click to collapse
tahwer said:
it is probably one of those "motorola confidential property" tagged phones used by company staff only, it may have been leaked into market, it often has unlocked bootloader like developer edition phones. it is a pre release phone with extra functions (that are not in mass production versions)
Click to expand...
Click to collapse
hi dears
well, i've got the same issue (device is unlocked - status code 1)
it seems it has an unlocked bootloader, but for me, the unlocked bootloader warning has never appeared
i've even flashed twrp and cyanogenmod 12.1
my question is, (1) should i unlock it with the code and all that moto.com stuff?
one last question is, (2) why can't i just add supersu from twrp 2.8.7.0?
i turn it on at system, and i swipe to root, but the icon never appears on my apps drawer, is it related to the status code 1?
please help me...

For God sake! I have the same problem here. How can I root this phone? What code 1 means?

Related

Moto X won't update to KitKat

I purchased a Moto X today. It is currently on 4.2.2. Whenever I update it, it says that device is fully updated. I tried searching on Xda but couldn't find a relevant thread. I don't want to root it or flash a Rom, I want to avoid all that. Also I am new to Xda, if this is not the right place to post this then please let me know.
Best way would be to go to the return to stock thread and flash your carriers sbf for 4.4.4
You can flash it via mfastboot or with rsd. There is also a toolkit in the development section. Good luck and ask if you have questions.
There is no way of updating through OTA?
Being on 4.2.2, invest in Sunshine to unlock the bootloader. Why worry about OTAs when you have the option to update manually?
nhizzat said:
Being on 4.2.2, invest in Sunshine to unlock the bootloader. Why worry about OTAs when you have the option to update manually?
Click to expand...
Click to collapse
Why do I need to unlock the bootloader? I am new to this so sorry for the noob questions
mateen1994 said:
Why do I need to unlock the bootloader? I am new to this so sorry for the noob questions
Click to expand...
Click to collapse
Once you update to 4.4.4, you will not be able to unlock your bootloader, or root. If that doesn't matter to you, then no worries.
But if you ever want to Root, unlocking your bootloader now is the best option. With Sunshine, for $25.
Sunshine won't work on 4.4.4, and you'll be stuck, with no chance to Root as of now. ?
mateen1994 said:
I purchased a Moto X today. It is currently on 4.2.2. Whenever I update it, it says that device is fully updated. I tried searching on Xda but couldn't find a relevant thread. I don't want to root it or flash a Rom, I want to avoid all that. Also I am new to Xda, if this is not the right place to post this then please let me know.
Click to expand...
Click to collapse
A few questions...
Did you buy it new or used?
Can you boot into Fastboot/Bootloader mode what is listed on the 2nd line of the phone's screen?
Your screen shots indicate this is an ATT Branded XT1058. Is that correct? do you have the ATT logo on its back? do you see XT1058 in the very small fine print on the back of the phone?
That being said, IF you ever want to root, and your phone is fully on the 4.2.2 rom (including the correct bootloader version), then you will want to use Sunshine to unlock the bootloader NOW before you worry about updates. Once your phone has been updated to 4.4.4 you wont be able to bootloader unlock it.
Once you are ready to upgrade, the best option is to figure out what Android version you want, grab the correct SBF for your carrier/model/android version, and flash it. Taking OTA's are incremental. You need to install one after the other to get to the version you want to be on. SBF files are FULL/All-Inclusive roms, so you just flash the latest you want to be on, so its quicker and Easier.
One final thing.. since I've seen something like this before... IF you have the latest android sdk/platform tools installed on your PC, and USB Debugging turned on (on your phone), then while still in Fastboot/Bootloader mode, connect the phone to your PC, and do a fastboot getvar all what does your phone say for the following...
(bootloader) unlocked:
(bootloader) iswarrantyvoid:
(bootloader) cid:
and does it show the proper IMEI?
KidJoe said:
A few questions...
Did you buy it new or used?
Can you boot into Fastboot/Bootloader mode what is listed on the 2nd line of the phone's screen?
Your screen shots indicate this is an ATT Branded XT1058. Is that correct? do you have the ATT logo on its back? do you see XT1058 in the very small fine print on the back of the phone?
Click to expand...
Click to collapse
1- Used. Also, don't know if it's important to mention or not, I live in Pakistan.
2- I just copy pasted the whole thing for you
AP Fastboot Flash Mode (NS)
30.70 (sha-88483d6, 2013-07-02 15:32:03)
eMMC: 16GB Toshiba RV=06 PV=00 TY=17
DRAM: 2048MB Elpida S4 SDRAM DIE=4Gb
Up Time: 5 minutes
Device is UNLOCKED. Status Code: 1
Battery OK
Connect USB Data Cable
Boot Mode Selection Menu
Vol Up Selects, Vol Down Scrolls
Normal Powerup
Recovery
Factory
Switch console (NULL: null)
Barcodes
BP Tools
Fastboot Reason: Key pressed.
3- Yes it is an AT&T branded XT1058. It doesnt have a logo on its back but when I plug in the phone it says XT1058.
Device is UNLOCKED. Status Code: 1 <--- Does this mean my bootloader is unlocked?
KidJoe said:
(bootloader) unlocked:
(bootloader) iswarrantyvoid:
(bootloader) cid:
and does it show the proper IMEI?
Click to expand...
Click to collapse
(bootloader) unlocked: Not Supported
(bootloader) iswarrantyvoid: Not Supported
(bootloader) cid: 0xdead
And no it doesnt, showing a bunch of zeroes
mateen1994 said:
(bootloader) unlocked: Not Supported
(bootloader) iswarrantyvoid: Not Supported
(bootloader) cid: 0xdead
And no it doesn't, showing a bunch of zeroes
Click to expand...
Click to collapse
UGH... Not another one!!
see -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150 and the tale end of... http://forum.xda-developers.com/moto-x/moto-x-qa/xt1058-sim-lock-mystery-t2755476/page3
I don't know where these devices are coming from, or what is being done to them... but.. yikes..
Where did you buy yours??
My suggestion... if you are SURE its an ATT XT1058, use mfastbooot to flash the 4.4.2 ATT SBF, make sure the phone works, if it does, try sunshine to get the Unlocked status to 3. Then you can try flashing 4.4.4 SBF
*IF* that works, without bricking, count your self lucky.
KidJoe said:
Where did you buy yours??
My suggestion... if you are SURE its an ATT XT1058, use mfastbooot to flash the 4.4.2 ATT SBF, make sure the phone works, if it does, try sunshine to get the Unlocked status to 3. Then you can try flashing 4.4.4 SBF
*IF* that works, without bricking, count your self lucky.
Click to expand...
Click to collapse
Bought it from a shop that sells used phones. Asked the guy to give me another piece, he says he will in a couple of days when the phone is in stock again.
It is printed on the bottom backside of the phone XT1058 Designed and Assembled in the USA. So it is probably a case of improper flashing.
Also, what is SBF? And after unlocking the bootloader, do I need to root the phone to flash the 4.4.4 SBF?
mateen1994 said:
Bought it from a shop that sells used phones. Asked the guy to give me another piece, he says he will in a couple of days when the phone is in stock again.
Click to expand...
Click to collapse
That is the best thing to do. Get a replacement.
mateen1994 said:
It is printed on the bottom backside of the phone XT1058 Designed and Assembled in the USA. So it is probably a case of improper flashing.
Also, what is SBF? And after unlocking the bootloader, do I need to root the phone to flash the 4.4.4 SBF?
Click to expand...
Click to collapse
SBF = full Stock Motorola signed rom.
Root isn't needed to flash a ROM.
You don't NEED to unlock the bootloader, unless you feel you want to root at some point. Because you are on XDA, its usually expected you are looking to hack and customize your phone. Most of that needs rooting. The best way to root, and ensure you can root later, is unlock the bootloader. Hence the mention of it.
If you are going to get a replacement, I wouldn't mess with this phone. I wouldn't try sunshine (as its tied to the phone, so replace your phone and you'd have to pay for sunshine again). If you try and reflash it, you could screw it up, then the seller might not take it back.
"improper flashing" has been the cause of many bricks, either immediately or down the road. So if that is truly the case (that improper flashing is the cause, or even suspected cause), I would advise you to not mess with it if you are able to return/exchange it.
mateen1994 said:
1- Used. Also, don't know if it's important to mention or not, I live in Pakistan.
2- I just copy pasted the whole thing for you
AP Fastboot Flash Mode (NS)
30.70 (sha-88483d6, 2013-07-02 15:32:03)
eMMC: 16GB Toshiba RV=06 PV=00 TY=17
DRAM: 2048MB Elpida S4 SDRAM DIE=4Gb
Up Time: 5 minutes
Device is UNLOCKED. Status Code: 1
Battery OK
Connect USB Data Cable
Boot Mode Selection Menu
Vol Up Selects, Vol Down Scrolls
Normal Powerup
Recovery
Factory
Switch console (NULL: null)
Barcodes
BP Tools
Fastboot Reason: Key pressed.
3- Yes it is an AT&T branded XT1058. It doesnt have a logo on its back but when I plug in the phone it says XT1058.
Device is UNLOCKED. Status Code: 1 <--- Does this mean my bootloader is unlocked?
Click to expand...
Click to collapse
Yes , your device bootloader has been unlocked.
Whats interesting is that both @RafaySid and @mateen1994 bought the phones from the same country; probably even from the same seller.
I guess the seller bought used ATT phones from USA and tried to unlock them via flashing some different custom ROM and ended up messing it up.
I've found quite a few devices in the market with this problem.
usmanshahid said:
Whats interesting is that both @RafaySid and @mateen1994 bought the phones from the same country; probably even from the same seller.
I guess the seller bought used ATT phones from USA and tried to unlock them via flashing some different custom ROM and ended up messing it up.
I've found quite a few devices in the market with this problem.
Click to expand...
Click to collapse
I bought mine from a guy in Karachi
No, not from the same seller I'm pretty sure. I guess these phones are imported from abroad which have been improperly flashed or something. I sorted out my problem though.

Can't get unlock data on a XT1053

My original Moto-X 1st Gen Developer Edition was a piece of cake to do the whole unlock bootloader procedure. Unfortunately my original phone died and I received a replacement from Motorola which is supposedly a Developer Edition version (however does not say Developer Edition anywhere, nor does it have the white woven back cover).
I have tried from two different PC's both which contain the Android SDK and Motorola USB Drivers. My PC's recognize the phone when it is in fastboot mode and the phone recognizes USB Connected. So when I issue the command "fastboot oem get_unlock_data" it responds back with "Could not get unlock data!" and that's as far as I get! Fastboot getvar all works fine.
Anyone have any ideas? My original phone also had Android 4.x.x whereas the replacement has Android 5.1 so I don't know if that makes a difference..
Thinkster said:
My original Moto-X 1st Gen Developer Edition was a piece of cake to do the whole unlock bootloader procedure. Unfortunately my original phone died and I received a replacement from Motorola which is supposedly a Developer Edition version (however does not say Developer Edition anywhere, nor does it have the white woven back cover).
I have tried from two different PC's both which contain the Android SDK and Motorola USB Drivers. My PC's recognize the phone when it is in fastboot mode and the phone recognizes USB Connected. So when I issue the command "fastboot oem get_unlock_data" it responds back with "Could not get unlock data!" and that's as far as I get! Fastboot getvar all works fine.
Anyone have any ideas? My original phone also had Android 4.x.x whereas the replacement has Android 5.1 so I don't know if that makes a difference..
Click to expand...
Click to collapse
I haven't been able to successfully unlock the regular Moto X bootloader, so my best guess is they sent you a non-Developer Edition phone. Let them know and they should be able to send out a replacement.
That's my guess too, even though they claim they go by the IMEI number of the original phone and send out a replacement that is the same based on that. But maybe they loaded the updated OS with the unlockable bootloader & Rom. I'm sending it back for replacement. hopefully the next one is correct!
Thinkster said:
My original Moto-X 1st Gen Developer Edition was a piece of cake to do the whole unlock bootloader procedure. Unfortunately my original phone died and I received a replacement from Motorola which is supposedly a Developer Edition version (however does not say Developer Edition anywhere, nor does it have the white woven back cover).
I have tried from two different PC's both which contain the Android SDK and Motorola USB Drivers. My PC's recognize the phone when it is in fastboot mode and the phone recognizes USB Connected. So when I issue the command "fastboot oem get_unlock_data" it responds back with "Could not get unlock data!" and that's as far as I get! Fastboot getvar all works fine.
Anyone have any ideas? My original phone also had Android 4.x.x whereas the replacement has Android 5.1 so I don't know if that makes a difference..
Click to expand...
Click to collapse
I've got the same problem right now with a replacement XT1053DE. Did the second one you receive unlock properly? I'd love to be able to solve this rather than wait for another exchange. Especially considering this already the second one I had to wait for.
Sent from my XT1053 using Tapatalk
Moto x xt1060 on 5.1 unlock bootloader
Hi,
I am trying to unlock the bootloader and root my 1st gen moto x running 5.1. I have followed the steps found online to get the unlock code from the motorola site but after I enter the string of code it says "your phone cannot be unlocked."
I cannot find any other site with instructions onwhat to do next. Please help.
Thanks
Bdough said:
Hi,
I am trying to unlock the bootloader and root my 1st gen moto x running 5.1. I have followed the steps found online to get the unlock code from the motorola site but after I enter the string of code it says "your phone cannot be unlocked."
Thanks
Click to expand...
Click to collapse
You probably have the non-DE XT1060 - There is no way to unlock the bootloader for it. Also: Next time post this question as a separate thread.
check your string of data u pulled I had the same issue but missed spaces and kept trying
Thinkster said:
My original Moto-X 1st Gen Developer Edition was a piece of cake to do the whole unlock bootloader procedure. Unfortunately my original phone died and I received a replacement from Motorola which is supposedly a Developer Edition version (however does not say Developer Edition anywhere, nor does it have the white woven back cover).
I have tried from two different PC's both which contain the Android SDK and Motorola USB Drivers. My PC's recognize the phone when it is in fastboot mode and the phone recognizes USB Connected. So when I issue the command "fastboot oem get_unlock_data" it responds back with "Could not get unlock data!" and that's as far as I get! Fastboot getvar all works fine.
Anyone have any ideas? My original phone also had Android 4.x.x whereas the replacement has Android 5.1 so I don't know if that makes a difference..
Click to expand...
Click to collapse
perfoliate said:
I've got the same problem right now with a replacement XT1053DE. Did the second one you receive unlock properly? I'd love to be able to solve this rather than wait for another exchange. Especially considering this already the second one I had to wait for.
Click to expand...
Click to collapse
Yep, same problem here. I've got 5.1 on an XT1053 that isn't marked as a developer edition, but the CID: is 0x00, which is unlockable. And like the OP, all I can get from "oem get_unlock_data" is "Could not get unlock data!" Extremely frustrating. Every other fastboot command seems to work fine.

Relocked Bootloader... Bricked :(

Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
what happens if you do a factory reset from the bootloader? Also can you flash a factory image?
returns to the fastboot , and I can not flash factory image
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
miketoasty said:
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
Click to expand...
Click to collapse
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
TheSt33v said:
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
Interesting, I didn't think that RSD would be able to modify the recovery partition on a locked device. Nonetheless if anything is going to work I believe what you have outlined is it St33v, best of luck to you OP.
miketoasty said:
Interesting, I didn't think that RSD would be able to modify the recovery partition on a locked device. Nonetheless if anything is going to work I believe what you have outlined is it St33v, best of luck to you OP.
Click to expand...
Click to collapse
Yep. As long as it passes the signature check, it flashes.
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
Let's be clear -- it was the Droid Turbo. Leave off the Moto Maxx part, OK?
You can lock/unlock a Moto Maxx (XT1225/XT1250) or even Moto Turbo (XT1225) all you want. In fact, the U.S. Moto Maxx XT1250 is IDENTICAL in every way to the Droid Turbo XT1254 -- radio bands, even the same FCC ID. Of all the Quarks, only Verizon's "Droid Turbo" has a carrier-locked down bootloader. All the others can be unlocked via the Motorola website. Whereas, the Droid Turbo bootloader unlock is a hack (Sunshine) that relies upon a vulnerability present in devices with Snapdragon 805.
miketoasty said:
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
Click to expand...
Click to collapse
Yes, WHY would you do that? Devs went through all the trouble to find a vulnerability to UNlock the Droid Turbo, and you lock it back? Been posted MANY, MANY times with the Droid Turob it's a one-time unlock only, through Sunshine.
TheSt33v said:
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
While you can flash stock again with a locked bootloader and it can work, over in the Moto Maxx section many people did brick their phones because they refused to unlock their bootloaders first. They were more worried about their silly "warranty" than having a functioning device. We kept stressing, FIRST unlock your bootloader. If you mess up, it's an easy fix if a flash goes wrong. With a locked bootloader, a bad flash is a recipe for disaster.
Over in the Moto Maxx/Moto Turbo section was a write up about flashing images, similar to your write up:
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724
Usually people wanting to downgrade back to KitKat or flash a Quark image from another region (India Moto Turbo XT1225) got Lollipop first before Latin American Moto Maxx XT1225).
And people were able to do it with a locked bootloader -- but you have to do everything just right. In my case, first time I flashed from Moto Maxx image to Moto Turbo image, I messed up. I was looking at the example picture more than reading the instructions. But, since I had an unlocked bootloader, so what? Just did it again the correct way, the second time.
In the case of Moto Maxx brick people trying to flash to Moto Turbo, those people had to wait until Lollipop was released for their phones then try to re-flash an image made for their phones -- and HOPE it worked.
Re Unlock
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
I tried what you said and I could not, Recovery does not work
A failure occurred when the step system.img_sparsechunk
How did you re-lock your bootloader? What did you do?
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
tvlovers said:
How did you re-lock your bootloader? What did you do?
Click to expand...
Click to collapse
Before I answer this question, I have to make one thing clear: DON'T EVER DO THIS!
Verizon will still replace your phone under warranty with an unlocked bootloader as long as there is no physical damage. Motorola will do the same. Even if they do decide to get picky about bootloaders, re-locking your bootloader does not erase all traces of it ever being unlocked. Your bootloader will show status code 2, which indicates that it has been unlocked and re-locked again. If you lock it before you sell it to someone else, and they try to unlock it again, the phone will be ruined. There is absolutely no reason to do this.
With that out of the way, the command is "fastboot oem lock"
Don't ever use it.
Thank youfor the warning. I should make it clear before. The reason I was asking was to make sure that no one would accidentally do it as I see no reason to lock it again once unlocked.
Besides that fastboot command is there any other way to accidentally lock it? New VZW OTA software or OEM unlocking under developer options in settings?
Please advise.
TheSt33v said:
Before I answer this question, I have to make one thing clear: DON'T EVER DO THIS!
Verizon will still replace your phone under warranty with an unlocked bootloader as long as there is no physical damage. Motorola will do the same. Even if they do decide to get picky about bootloaders, re-locking your bootloader does not erase all traces of it ever being unlocked. Your bootloader will show status code 2, which indicates that it has been unlocked and re-locked again. If you lock it before you sell it to someone else, and they try to unlock it again, the phone will be ruined. There is absolutely no reason to do this.
With that out of the way, the command is "fastboot oem lock"
Don't ever use it.
Click to expand...
Click to collapse
tvlovers said:
Thank youfor the warning. I should make it clear before. The reason I was asking was to make sure that no one would accidentally do it as I see no reason to lock it again once unlocked.
Besides that fastboot command is there any other way to accidentally lock it? New VZW OTA software or OEM unlocking under developer options in settings?
Please advise.
Click to expand...
Click to collapse
A verizon OTA probably will not, but it's best to wait until someone here confirms that. In the past, they have not, but you never know what they'll try next. The OEM unlock setting in developer options does nothing on a Turbo. It's intended for true dev phones (or phones designed for carriers less tyrannical than Verizon) that can be unlocked and re-locked easily. It disables the "fastboot oem unlock" command that someone with a dev phone would normally use to easily unlock the bootloader. There are no other ways to lock the bootloader that I know of.
bubblesd306 said:
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
Click to expand...
Click to collapse
Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?
Sent from my XT1254 using Tapatalk
richii0207 said:
Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
This isn't unlocking for a first time. This is unlocking for a second time.
Typically when you unlock a bootloader you can relock and unlock easily in adb.
For our device this is not the case and it should never be relocked.
A few have and have always succeeded with those commands.
Again this is only for a previously unlocked boot loader.
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
This isn't unlocking for a first time. This is unlocking for a second time.
Typically when you unlock a bootloader you can relock and unlock easily in adb.
For our device this is not the case and it should never be relocked.
A few have and have always succeeded with those commands.
Again this is only for a previously unlocked boot loader.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
Ya. I did unlock, relock, then unlock again. I am able to install TWRP, and use CF ROM with no issues but if I install CM, I get data but NO voice which is very odd.
Reflashing radios and messing with the network configurations did not help.
I've seen people that have unlocked twice and are able to run CM without any issues.
I've tried reflashing firmware, Reflashing SU38 and OTAing to 44 to no avail. I used to run CM before I relocked without a problem.
Although I do get errors flashing GPT partition, it says that it flashes backup GPT instead of primary.
Sent from my XT1254 using Tapatalk
richii0207 said:
Ya. I did unlock, relock, then unlock again. I am able to install TWRP, and use CF ROM with no issues but if I install CM, I get data but NO voice which is very odd.
Reflashing radios and messing with the network configurations did not help.
I've seen people that have unlocked twice and are able to run CM without any issues.
I've tried reflashing firmware, Reflashing SU38 and OTAing to 44 to no avail. I used to run CM before I relocked without a problem.
Although I do get errors flashing GPT partition, it says that it flashes backup GPT instead of primary.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Is it possible you're not doing a full wipe? What version of twrp are you flashing with?
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
Is it possible you're not doing a full wipe? What version of twrp are you flashing with?
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
I realized that I can only make calls when VoLTE is enabled on stock. If I turn it off, I cannot make any phone calls but can access data still. I went into diagnostic mode and it showed " Phone ICCID compare with sim CCID error" with "UNKNOWN" under Phone ICCID. Hmmm..

STILL cant get rid of N/A or bad key message!!! grrr

Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Right, Lets begin....
Originally i followed a guide to root my g6 play,that was by booting a patched twrp, and dm verity and another file beginning with Q, then flash the twrp........... all that was working except dm verity which gave a error (cant remember which one)
i have tried a different number of firmwares (motorola themselves said try jeter and alijeter - as some alijeter firmware are for my model xt1922-2)
now there was a OTA, as far as I can remember, there was 2 ota updates, they went smoothly, but still the BAD KEY message (brought on by the patched dm verity file i think)
after doing this ota, the oem unlocking button was no longer greyed out, so i tried fastboot oem lock but it gives errors about bootloader bad key and more, or invalid android image
whatever happens, i cannot relock the bootloader to remove the message, i cant flash any firmware for my model without one or two errors.......
the only thing that works, to show the bootloader is locked, is fastboot flashing_lock (as my bootloader screen shows flashing_unlocked) this shows, by doing fastboot getvar all and all that, that the bootloader is relocked....but I still have bad key error, and then have to oem unlock again to do anything.....help
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
biggary said:
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
Click to expand...
Click to collapse
Ok so let's put this out there first. I am helping you for free because I generally enjoy being a helping hand! I asked for screenshots, which we still have not gotten. I asked if bootloader was unlocked still to be sure, because I wasn't sure if you had tried to relock it. I think you did try to relock based on your post, but I had to ask twice to get that information out of you. If you truly want help, help those who want to help you help yourself.
That said, I asked for screenshots because I have never heard of a "bad key" error. The way I understood it you were seeing this error in TWRP. After a quick google search I found this image:
https://forums.lenovo.com/lnv/attachments/lnv/230/6043/1/IMG-20170528-WA0015.jpg
I assume this is the same error you see? If so, you can actually ignore it. If you don't want to ignore it, you can try going to bootloader and type this: fastboot oem fb_mode_clear
Also, you can try to see if there is a modified logo.bin for your device and flash it. You could try the G6+ logo.bin possibly:
https://forum.xda-developers.com/moto-g6/themes/bootlogo-remove-message-unlocked-t3789155
PS: I found this info with a quick google search, so I assume you didn't even bother to search?
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
I am having the same issue as you, i am trying so much that i forget about doing root and just want to lock my bootloader again ;-;
The XT1922-2 is an annoying little ****.
biggary said:
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
Click to expand...
Click to collapse
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
w4r3zgod said:
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
Click to expand...
Click to collapse
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
madbat99 said:
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
Click to expand...
Click to collapse
Yea warranty void.
biggary said:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
Click to expand...
Click to collapse
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
Click to expand...
Click to collapse
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
Click to expand...
Click to collapse
I found this for another g6. Use the firmware for your model and it may work.
https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292/post78432631

Unlocking Bootloader in 2020

Hi all, I got my hands on my brother's old Moto G 2nd Gen (XT1068) last week and wanted to flash a custom ROM. To my disappointment I found that Motorola/Lenovo has discontinued support for the G2 last year and will no longer provide bootloader unlock keys for this model.
Does anyone know of an unofficial way to obtain a bootloader unlock key or of an exploit which can unlock the bootloader without unlock key? Any help would be appreciated!
Unlocking Possible for Moto G 2nd Gen (XT1068)
santa41116 said:
Hi all, I got my hands on my brother's old Moto G 2nd Gen (XT1068) last week and wanted to flash a custom ROM. To my disappointment I found that Motorola/Lenovo has discontinued support for the G2 last year and will no longer provide bootloader unlock keys for this model.
Does anyone know of an unofficial way to obtain a bootloader unlock key or of an exploit which can unlock the bootloader without unlock key? Any help would be appreciated!
Click to expand...
Click to collapse
Hey there, I literally just unlocked a (old & dead) Moto G 2nd Gen (XT1068) a day ago... I did it the official way!
This might help you if you're doing it for the first time > https://wiki.lineageos.org/devices/titan/install
Or fell free to reply here if you're stuck or need any assistance... The only hurdle I faced is getting the Fastboot driver to install on my system!
Good luck :good:
blackmonk19 said:
I did it the official way!
Click to expand...
Click to collapse
Hi @blackmonk19, thanks a lot for your reply and congrats for your successful unlock! I also struggled a bit with the USB drivers but got it working and retrieved the unlock data from fastboot. However, the Motorola support website "motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a" won't give me the bootloader unlock code and claims that my device is not eligible for unlocking. I have tried it several times for the past few days. My Moto G2 is neither branded nor SIM-locked. Customer ID is 7: (bootloader) cid: 0x0007 which means that it's unlockable.
I contacted the Motorola customer support and they referred me to their list of supported devices which does not include the Moto G2 any longer: support.motorola.com/us/en/solution/MS87215
Can you confirm that you received your bootloader unlock key this week from motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a ?
Your link to lineage OS refers to an alternative way to unlock the bootloader via theroot.ninja which got my hopes up but the phone has to be on Android 4.4.3 or lower for this to work and my Moto is on Android 6. :crying:
Any more help would be appreciated
santa41116 said:
Won't give me the bootloader unlock code and claims that my device is not eligible for unlocking. I have tried it several times for the past few days. My Moto G2 is neither branded nor SIM-locked. Customer ID is 7: (bootloader) cid: 0x0007 which means that it's unlockable.
Click to expand...
Click to collapse
Hi there, thats strange... seems like its carrier locked, even though you say it isnt! Did you get the Customer ID is 7: (bootloader) cid: 0x0007 by inputting the command -
C:\platform-tools>fastboot getvar all...
You should get a line saying (bootloader) ro.build.fingerprint[0]: motorola/(CARRIER NAME, IF LOCKED)
santa41116 said:
I contacted the Motorola customer support and they referred me to their list of supported devices which does not include the Moto G2 any longer: support.motorola.com/us/en/solution/MS87215
Can you confirm that you received your bootloader unlock key this week from motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a ?
Click to expand...
Click to collapse
Yeah Moto G2 is not on the list... But I can confirm i received the Unlock Code on June 18!
Let me know accordingly ... :good:
blackmonk19 said:
Did you get the Customer ID is 7: (bootloader) cid: 0x0007 by inputting the command -
C:\platform-tools>fastboot getvar all...
Click to expand...
Click to collapse
Yes, that is what I did.
blackmonk19 said:
You should get a line saying (bootloader) ro.build.fingerprint[0]: motorola/(CARRIER NAME, IF LOCKED)
Click to expand...
Click to collapse
No carrier name here:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 6.0/MPB24.65-34-3/3:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
blackmonk19 said:
Yeah Moto G2 is not on the list... But I can confirm i received the Unlock Code on June 18!
Click to expand...
Click to collapse
Have you by any chance had your bootloader unlocked before?
Hi, I have a Moto G 2014 (titan) and I would like to installa on it a custom recovery.
In order to do it I need to unlock the bootloader.
Unluckly SunShine failed the procedure.
Any ideas?
Thanks.
EDIT:
the standard procedure worked.
Unfortunately I have the very same problem. I found this phone hidden in one of my boxes during a move. I wanted to try and see how it would work with Lineage OS but if I try to use the Motorola web site but no way to find the unlock code. Also, SunShine app doesn't work with it.
I'm out of ideas
---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------
tattare1987 said:
[...]
EDIT:
the standard procedure worked.
Click to expand...
Click to collapse
You mean using the Motorola website?

Categories

Resources