Related
Greetings all. I've tried contacting moto support, and I'm not having any luck getting into tier 2 support. So far, my post on the forum hasn't been addressed. So, I'm turning to the good 'ole xda community
I'm trying to unlock the bootloader on my new GSM Dev edition moto x. It's not working and I'm certain I'm following the directions on their site. I've even tried (as per their web site) to manually flash the latest 4.2.2 or the 4.4 images. No joy. When I issue the command "fastboot oem get_unlock_data" I get "could not get unlock data!" See attached screen shot. I dunno what to do.
Any ideas? Please?
heroisnotdead said:
Greetings all. I've tried contacting moto support, and I'm not having any luck getting into tier 2 support. So far, my post on the forum hasn't been addressed. So, I'm turning to the good 'ole xda community
I'm trying to unlock the bootloader on my new GSM Dev edition moto x. It's not working and I'm certain I'm following the directions on their site. I've even tried (as per their web site) to manually flash the latest 4.2.2 or the 4.4 images. No joy. When I issue the command "fastboot oem get_unlock_data" I get "could not get unlock data!" See attached screen shot. I dunno what to do.
Any ideas? Please?
Click to expand...
Click to collapse
If you haven't updated your sdk in a while, the old fastboot executable doesn't work. Either update your sdk or use the mfastboot provided by moto.
edit: I'm not seeing mfastboot listed anywhere anymore from motorola so I would suggest trying to update your sdk if all else fails, here's link to the mfastboot I downloaded from moto. https://drive.google.com/file/d/0B8NUe_bfBHZ7SGpDMWt3MUM2Vm8/edit?usp=sharing
P!X3L said:
If you haven't updated your sdk in a while, the old fastboot executable doesn't work. Either update your sdk or use the mfastboot provided by moto.
edit: I'm not seeing mfastboot listed anywhere anymore from motorola so I would suggest trying to update your sdk if all else fails, here's link to the mfastboot I downloaded from moto. https://drive.google.com/file/d/0B8NUe_bfBHZ7SGpDMWt3MUM2Vm8/edit?usp=sharing
Click to expand...
Click to collapse
Thanks for the suggestion. mfastboot and the latest platform-tools from the most recent SDK yielded the same error. I also tried the fastboot included in the stock 4.4 image from the moto support site. Could there be something wrong with the bootloader? It's simply not returning the data even though the command seems to be recognized. Give me my data, I command you bootloader!
heroisnotdead said:
Thanks for the suggestion. mfastboot and the latest platform-tools from the most recent SDK yielded the same error. I also tried the fastboot included in the stock 4.4 image from the moto support site. Could there be something wrong with the bootloader? It's simply not returning the data even though the command seems to be recognized. Give me my data, I command you bootloader!
Click to expand...
Click to collapse
Odd. I don't have a mfastboot in the package I downloaded from moto. (MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip) Can you get any of the other fastboot commands to work? Maybe try to reflash the stock package, or at least reflash/reboot the bootloader.
P!X3L said:
Odd. I don't have a mfastboot in the package I downloaded from moto. (MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip) Can you get any of the other fastboot commands to work? Maybe try to reflash the stock package, or at least reflash/reboot the bootloader.
Click to expand...
Click to collapse
I'm gonna try reflashing using the files from this the TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF download link from the moto site. It's suppose to be for GSM dev and has a fastboot and the supporting .dll files in the windows folder (see attached). That doesn't match what you have. I wonder if they are giving me the wrong image files. The phone seems to work perfectly fine on 4.4 or 4.2.2; it's just this damn bootloader won't give me my data.
I had tried the 4.2.2 images, including the bootloader. I'll try again using 4.4. Is there a difference between the reflashing the bootloader and rebooting it? The other fastboot commands work fine.
heroisnotdead said:
I'm gonna try reflashing using the files from this the TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF download link from the moto site. It's suppose to be for GSM dev and has a fastboot and the supporting .dll files in the windows folder (see attached).
I had tried the 4.2.2 images, including the bootloader. I'll try again using 4.4. Is there a difference between the reflashing the bootloader and rebooting it? The other fastboot commands work fine.
Click to expand...
Click to collapse
I updated to 4.4 OTA before unlocking, but if I was you, I'd reflash the complete 4.4 factory image. I wouldn't put anything from any other package on it.
Reflashing the bootloader actually flashes the bootloader partition, while rebooting it, well, just reboots it. If you do flash a new bootloader using fastboot, you'll need to reboot the bootloader for the "new" bootloader take effect. I'd flash the whole 4.4 system image and then try the unlock command again. For what it's worth, I had no problem using the latest sdk's regular fastboot and I'm also using koush's Superuser instead of SuperSU.
P!X3L said:
I updated to 4.4 OTA before unlocking, but if I was you, I'd reflash the complete 4.4 factory image for the XT1060. I wouldn't put anything from any other package on it.
Reflashing the bootloader actually flashes the bootloader partition, while rebooting it, well, just reboots it. If you do flash a new bootloader using fastboot, you'll need to reboot the bootloader for the "new" bootloader take effect. I'd flash the whole 4.4 system image and then try the unlock command again. For what it's worth, I had no problem using the latest sdk's regular fastboot and I'm also using koush's Superuser instead of SuperSU.
Click to expand...
Click to collapse
understood, thanks. Do you have the GSM dev version as well? I also updated to 4.4 before trying to unlock. I'm just wondering if I'm flashing the wrong images now because of the differences in file names. I used the download links moto gave me. Seemed pretty straight forward to me. I'll go through their instructions again using the 4.4 images this time.
heroisnotdead said:
understood, thanks. Do you have the GSM dev version as well? I also updated to 4.4 before trying to unlock. I'm just wondering if I'm flashing the wrong images now because of the differences in file names. I used the download links moto gave me. Seemed pretty straight forward to me. I'll go through their instructions again using the 4.4 images this time.
Click to expand...
Click to collapse
I have the XT1060 VZW DE. Definitely flash the gsm 4.4 package and give the unlock another try
P!X3L said:
I have the XT1060 VZW DE. Definitely flash the gsm 4.4 package and give the unlock another try
Click to expand...
Click to collapse
Manually flashed the 4.4 package using the latest fastboot and dlls from the 4.4 SDK. I also tried with the fastboot and dlls included in the 4.4 moto factory package. I used the instructions from the moto site (see attached) as a general guide, but followed the sequence in the attached XML file. Everything flashed fine, I ran reboot-bootloader and it loaded just fine.
Still no unlock data from the bootloader. I did the same thing using the 4.2.2 GSM dev factory package with the same result. WTF. I have no idea what could be wrong. I mean, we're talking about two different bootloader images here, right?
FYI: Moto support sent me a response saying that can't help. Best I can do is return the phone for a refund or ask for a replacement.
I used the guide here( http://www.elementalxdesigns.com/ec...-Edition-install-TWRP-and-how-to-flash-images) to unlock and gain root. Thanks @Nitroglycerin! This is for the VZW Dev Ed but dont think it matters. Hope this helps....
Sent from my XT1060 using Tapatalk
heroisnotdead said:
Manually flashed the 4.4 package using the latest fastboot and dlls from the 4.4 SDK. I also tried with the fastboot and dlls included in the 4.4 moto factory package. I used the instructions from the moto site (see attached) as a general guide, but followed the sequence in the attached XML file. Everything flashed fine, I ran reboot-bootloader and it loaded just fine.
Still no unlock data from the bootloader. I did the same thing using the 4.2.2 GSM dev factory package with the same result. WTF. I have no idea what could be wrong. I mean, we're talking about two different bootloader images here, right?
FYI: Moto support sent me a response saying that can't help. Best I can do is return the phone for a refund or ask for a replacement.
Click to expand...
Click to collapse
I'd ask for a replacement and hope the turnaround is as fast as a carrier. If all the images flashed fine there's no reason you shouldn't be getting that unlock data. Especially on two different factory versions. As a last resort, I'd verify the various factory image files MD5's and then repeat the process using mfastboot exclusively and make sure to include the include the erase commands. That should put your phone back to stock for you to return anyways if it doesn't work.
P!X3L said:
I'd ask for a replacement and hope the turnaround is as fast as a carrier. If all the images flashed fine there's no reason you shouldn't be getting that unlock data. Especially on two different factory versions. As a last resort, I'd verify the various factory image files MD5's and then repeat the process using mfastboot exclusively and make sure to include the include the erase commands. That should put your phone back to stock for you to return anyways if it doesn't work.
Click to expand...
Click to collapse
Did that. Everything flashed fine. I have a pending request into moto for replacement. They sold me an unlockable phone, clearly this one isn't, therefore it's defective. I really appreciate the time you took to help me P!X3L!
Hey. Do you get anything with fastboot getvar all
Sent from my XT1058 using XDA Premium 4 mobile app
planktoid said:
Hey. Do you get anything with fastboot getvar all
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup. Attached a screenie for ya. Something catch your eye?
Yes. Thanks. I am sending you a private message.
Sent from my XT1058 using XDA Premium 4 mobile app
planktoid said:
Yes. Thanks. I am sending you a private message.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm encountering the same problem as op. Any chance I could get a pm as well?
Sent from my Nexus 7 using xda app-developers app
Get a moto X if you don't care about unlocking the bootloader.
Motorola (much like HTC and their bull**** unlocking steps) is ****ing absurd. I finally got my replacement moto x and I was able to get the unlock data from this device. Of course, now the web site says my device isn't eligible to be unlocked. I haven't tried contacting T1 support because those guys are worthless.
My experience with motorola has been completely awful. The only reason I'm not using an N5 is due to the audio issues. Maybe that's been fixed now that the phone has had 2 updates and one hardware revision. There is no ****ing reason in the world why any company that advertises a "developer friendly" devices makes it this freaking hard to unlock the bootloader. Damn it! I guess I'm going to try their "tech support" and see what happens.
If you're on the fence about an N5 or Moto X and want to unlock the BL; just get an N5 and save yourself a lot of trouble.
so i tried to update to the new sprint update that fixes the 4.4 battery issues. i was on twrp recovery and i flashed back to stock recovery and tried to dirty flash the update on top. i had xposed framework installed so was pretty sure that wasn't going to work. and it didn't. now i decided to use the moto x toolkit to flash back to stock. it booted up just fine then i downloaded the update from 4.2.2 to 4.4 and the update failed. now i'm stuck with basically nothing on my phone at all. i can get to fastboot mode but thats it. cant power up cant enter recovery can't do anything.. also i had a unlocked bootloader and now its reading locked again. here is the error i'm getting.
failed to hab check for gpt_nain: 0x35
failed to hab check for gpt_gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. contact Dealer: 0xdead
No SP partition found
Fastboot Reason: Invalid CID
I've been working on this for about 7 hours and have looked up everything i could think of to try and get this fixed. i may just be missing something.. does anyone know how i could fix this?
What version is your bootloader, you can see it in the fastboot screen.
30.71(*) (sha-913941e, 2013-07-31 10:46:37)
is that was your looking for?
OK, that is the 4.2.2 bootloader. Your bootloader is locked in that screen shot - so how did you install twrp recovery?
Also your avatar shows AT&T but you mention you tried using the Sprint update, can you confirm the phone you have is a Sprint model?
Steve-x said:
OK, that is the 4.2.2 bootloader, so you should be fine to try flashing the phone again. I'd download the Sprint 4.4 package and try a full flash using rsdlite if possible. Everything on the phone will be wiped/erased of course. Then take the update to 4.4.2. Once that is done you can reinstall the latest version of twrp and root the phone again.
Click to expand...
Click to collapse
thanks for the reply! well i already tried that and i can't get rsd to flash. are there some special drivers i'm supposed to install? i got the motorola drivers from their web-sight. and it won't flash. it sees that there is a phone but all catagories read n/a and it just comes up with flash fails..
i'm not sure how the bootloader got locked again.. it wasn't locked before i'm pretty sure the moto x toolkit i used to flash back to stock relocked it?.. or maybe not. but i do know it was unlocked and now its locked. and when i try to get the unlock code like last time it doesn't work.
yes this is a sprint phone.
Edit: thank you for pointing that out, never changed it from years ago
If you were able to relock the bootloader and have the phone report status code 0 then you'd be the first to have done it. You can relock the bootloader but it requires a specific procedure to be followed and the phone will never indicate status code 0 again.
Review this guide - the first flashing option you should work for you, remember to remove the getvar line
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
i'm a idiot. i must have looked at that guide 15 times today and never read through all of it. just needed to deleate that one file and it all worked. thanks everyone for you help!
the status code 0 must have been incorrect. its back to status code 3 and unlocked. thank you all for your help!
Hello everyone,
I bought an HTC one off ebay, having in mind I would flash custom rom on the device which I prefer for obvious reasons. But each time I open Hasson2000 Tool to get ID token I get this error in command prompt below:
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
'error: device offline
I have tried searching for solutions but I cant get one to actually fix my own issue, I do know the HTC bootloader has been unlocked and rooted because I can boot to bootloader menu, boot to recovery mode and on top on the screen it says *****TAMPERED***** just below it says ***UNLOCKED*** I figured the previous owner tried locking bootloader before selling it off.
I noticed other commands dont work like reboot device on the tool probably because of that error or my htc is not recognised am not sure. am running Windows 8.1 Pro on my laptop.
What I have done so far
Rebooted phone several times
Rebooted my laptop several times
Unplugged and plugged in usb cable
Used different usb ports it recognises my htc because I can view my SD card or transfer files between laptop and phone.
Please guys I neeed your help with this, thanks.
WOW over 52 views and not a single reply thanks heart breaking
Infoseye said:
WOW over 52 views and not a single reply thanks heart breaking
Click to expand...
Click to collapse
try this
first relock the bootloader
"fastboot oem lock"
and then go to htcdev.com/bootloader and follow the steps to unlock it again
Boachti said:
try this
first relock the bootloader
"fastboot oem lock"
and then go to htcdev.com/bootloader and follow the steps to unlock it again
Click to expand...
Click to collapse
Okay I will give it a try and tell you the out come.
Infoseye said:
Okay I will give it a try and tell you the out come.
Click to expand...
Click to collapse
ok
Boachti said:
ok
Click to expand...
Click to collapse
Okay I have locked and relocked Bootloader, installed custom recovery. So what do I do now?
I got an OTA update from HTC for WIFI fix, I could not update via recovery it gave an error is it because the bootloader is locked?
Am on Kitkat 4.4.2, S-ON,TWRP,4.19.401.9, HTC_001 please how do I just restore it to original HTC stock not custom ROM?
Infoseye said:
I got an OTA update from HTC for WIFI fix, I could not update via recovery it gave an error is it because the bootloader is locked?
Click to expand...
Click to collapse
now unlock it again
go to htcdev.com/bootloader
Boachti said:
now unlock it again
go to htcdev.com/bootloader
Click to expand...
Click to collapse
I have unlocked it again its now unlocked, right now I just want to go back to original stock so that I can get updates official updates from HTC but unfortunately I dont have a copy of stock rom since I bought it off ebay already rooted.
Infoseye said:
I have unlocked it again its now unlocked, right now I just want to go back to original stock so that I can get updates official updates from HTC but unfortunately I dont have a copy of stock rom since I bought it off ebay already rooted.
Click to expand...
Click to collapse
Depending on the carrier the device was made for and the one you use, OTA updates may not be an option. If it is a carrier device then updates will be pushed OTA from the OG carrier. IF you use a different carrier then you wont get OTA. And to be honest they are over rated and cause more issues then anything else.
zelendel said:
Depending on the carrier the device was made for and the one you use, OTA updates may not be an option. If it is a carrier device then updates will be pushed OTA from the OG carrier. IF you use a different carrier then you wont get OTA. And to be honest they are over rated and cause more issues then anything else.
Click to expand...
Click to collapse
Its unbranded HTC One unlocked its not locked to any carrier, so are you saying I cant go back to a stock or use a nand backup from this forum. I have found alot of topics but the procedures are abit confusing can you direct me a link or thread that can directing on how to flash a custom rom on my HTC?
Infoseye said:
Hello everyone,
I bought an HTC one off ebay, having in mind I would flash custom rom on the device which I prefer for obvious reasons. But each time I open Hasson2000 Tool to get ID token I get this error in command prompt below:
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
'error: device offline
I have tried searching for solutions but I cant get one to actually fix my own issue, I do know the HTC bootloader has been unlocked and rooted because I can boot to bootloader menu, boot to recovery mode and on top on the screen it says *****TAMPERED***** just below it says ***UNLOCKED*** I figured the previous owner tried locking bootloader before selling it off.
I noticed other commands dont work like reboot device on the tool probably because of that error or my htc is not recognised am not sure. am running Windows 8.1 Pro on my laptop.
What I have done so far
Rebooted phone several times
Rebooted my laptop several times
Unplugged and plugged in usb cable
Used different usb ports it recognises my htc because I can view my SD card or transfer files between laptop and phone.
Please guys I neeed your help with this, thanks.
Click to expand...
Click to collapse
What about using the command prompt instead of a toolkit? No disrespect to Hasson2000, but toolkits aren't ideal imo
In most cases, ''device offline'' is caused by an outdated version of the android sdk or a bad usb cable/usb port (btw use usb 2.0 ports).
Also in windows devices manager, your phone must be listed as Android usb device ---> My HTC. If not, you have drivers issue.
If your phone still boot normally, just copy the rom inside the sdcard, reboot in recovery and install it. I will highly suggest you make sure adb and fastboot works correctly before as they will be required if something goes wrong when installing the custom rom. Also make a nandroid backup of your current config before flashing the rom and make a copy of that backup on your computer.
alray said:
What about using the command prompt instead of a toolkit? No disrespect to Hasson2000, but toolkits aren't ideal imo
In most cases, ''device offline'' is caused by an outdated version of the android sdk or a bad usb cable/usb port (btw use usb 2.0 ports).
Also in windows devices manager, your phone must be listed as Android usb device ---> My HTC. If not, you have drivers issue.
If your phone still boot normally, just copy the rom inside the sdcard, reboot in recovery and install it. I will highly suggest you make sure adb and fastboot works correctly before as they will be required if something goes wrong when installing the custom rom. Also make a nandroid backup of your current config before flashing the rom and make a copy of that backup on your computer.
Click to expand...
Click to collapse
Well actually I used command prompt since the Hasson2000 tool did not work, Yes my HTC displays under device manager when plugged in. I think its my adb that is out of date.
How do I update my adb?
Infoseye said:
Well actually I used command prompt since the Hasson2000 tool did not work, Yes my HTC displays under device manager when plugged in. I think its my adb that is out of date.
How do I update my adb?
Click to expand...
Click to collapse
what is the output of
Code:
adb version
?
alray said:
what is the output of
Code:
adb version
?
Click to expand...
Click to collapse
I dont undertsand what you mean by adb version, how do find out the version am a newbie to all this stuff
Infoseye said:
I dont undertsand what you mean by adb version, how do find out the version am a newbie to all this stuff
Click to expand...
Click to collapse
open a cmd prompt from your adb/fastboot folder and type ''adb version'' and hit enter.
alray said:
what is the output of
Code:
adb version
?
Click to expand...
Click to collapse
C:\adb>adb version
Android Debug Bridge version 1.0.26 what do I do next?
Infoseye said:
C:\adb>adb version
Android Debug Bridge version 1.0.26 what do I do next?
Click to expand...
Click to collapse
1.0.26 is outdated.
Go here and download the sdk.
alray said:
1.0.26 is outdated.
Go here and download the sdk.
Click to expand...
Click to collapse
I downloaded another Android Debug Bridge version 1.0.31
Hey I was following this guide and got to Part 2 A, flashing TWRP. I believe i followed every step but am unable to access recovery, when i try to from fastboot it simply turns off the phone, when i try to from ADB it says "no command" with a picture of the broken android . I tried a newer TWRP img but it did not change anything.
I am using Android 6.0 and the Moto G2 Dual sim. I have unlocked the bootloader, updated drivers and there is no errors. Please help.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.0.0-1-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (8264 KB)...
OKAY [ 0.286s]
writing 'recovery'...
OKAY [ 0.290s]
finished. total time: 0.578s
Apologies if i have made a mistake in this post or have not provided enough detail, i'm new to rooting and using forums. Thanks for any help!
Moto G2 Dual-SIM is not enough info.
You probably don't have a Moto Titan, but a Moto Thea.
Do you know the exact code name of your phone? XT106x or XT107x?
If you're not sure, download and flash TWRP for Thea. If your phone is a LTE (Thea), you should be able to continue the steps in that tutorial, BUT you will have to choose a ROM for Thea, not Titan.
FCorvin said:
Moto G2 Dual-SIM is not enough info.
You probably don't have a Moto Titan, but a Moto Thea.
Do you know the exact code name of your phone? XT106x or XT107x?
If you're not sure, download and flash TWRP for Thea. If your phone is a LTE (Thea), you should be able to continue the steps in that tutorial, BUT you will have to choose a ROM for Thea, not Titan.
Click to expand...
Click to collapse
Ah, i downloaded the titan version, i've just checked my model number and it is XT1068
RavingSmurf said:
Ah, i downloaded the titan version, i've just checked my model number and it is XT1068
Click to expand...
Click to collapse
I tried a download for the thea but it still didnt work, ill try find some more downloads.
No, XT1068 is indeed Titan. You got it right from the start.
Try the latest version from their site.
Did you succesfully unlock your phone? Check if your bootloader is unlocked in fastboot mode it must say "Device is UNLOCKED. Status code: 3". If it doesn't say that your bootloader is still locked.
FCorvin said:
No, XT1068 is indeed Titan. You got it right from the start.
Try the latest version from their site.
Click to expand...
Click to collapse
Ah ok ill try it again, thanks!
felipe_hdez said:
Did you succesfully unlock your phone? Check if your bootloader is unlocked in fastboot mode it must say "Device is UNLOCKED. Status code: 3". If it doesn't say that your bootloader is still locked.
Click to expand...
Click to collapse
Yeah i checked it thanks
Hey again, sorry for the delay. i tried it again, along with alot of other files but it hasnt worked. Maybe something is wrong with the phone?
The guide you mentioned does not show you how to actually unlock your phone; it gives you links to another guide and a YouTube video.
You checked those out, right?
FCorvin said:
The guide you mentioned does not show you how to actually unlock your phone; it gives you links to another guide and a YouTube video.
You checked those out, right?
Click to expand...
Click to collapse
Ive unlocked the phone but i didnt follow those guides, i have been using this.
Yes, that's the one you mentioned.
But look closely: it doesn't show you how to unlock anything - it gives you a link to another tutorial for unlocking and then skips to rooting.
So... how exactly did you unlock it?
FCorvin said:
Yes, that's the one you mentioned.
But look closely: it doesn't show you how to unlock anything - it gives you a link to another tutorial for unlocking and then skips to rooting.
So... how exactly did you unlock it?
Click to expand...
Click to collapse
Ah I see what you mean, i followed the Motorola guide. You have to make an account to see it though.
http://forum.xda-developers.com/attachment.php?attachmentid=3821476&stc=1&d=1469278472
Well, if you did paste the code correctly and hit enter, then your phone must be unlocked.
Although I'm not so sure. With updated drivers, USB debugging enabled in Developer options and Minimal ADB installed, you should have been able to perform miracles.
Type in a CMD window from within the ADB folder:
Code:
fastboot devices
What happens? If you do get the device, type further:
Code:
fastboot oem device-info
What does it say?
FCorvin said:
Well, if you did paste the code correctly and hit enter, then your phone must be unlocked.
Although I'm not so sure. With updated drivers, USB debugging enabled in Developer options and Minimal ADB installed, you should have been able to perform miracles.
Type in a CMD window from within the ADB folder:
Code:
fastboot devices
What happens? If you do get the device, type further:
Code:
fastboot oem device-info
What does it say?
Click to expand...
Click to collapse
Hey, it gave me an error message.
It doesn't look good
Unfortunately, I am out of suggestions for you.
Good luck.
Ok, Thanks anyway. I might contact motorola support but i doubt they would help
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Still stucked?
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Salik Iqbal said:
Still stucked?
Click to expand...
Click to collapse
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Cesarisg said:
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Click to expand...
Click to collapse
Salik Iqbal said:
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Click to expand...
Click to collapse
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
I am ARSH and Iive in india if some one is having brazzers membership p lzz give me for one day p lzz share with me my e-mail [email protected] plzzzzzz
No problem..
Cesarisg said:
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
Click to expand...
Click to collapse
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
mwaterbu said:
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
Click to expand...
Click to collapse
There was 2 main reasons why I had to go back to stock, the main one was that the OS would not let me uninstall any app, I tried everything I read online to try to fix it, even flashing the rom again, nothing work and the other reason was the phone app would not let me hear from the earpiece, it got fixed after getting back to 5.1 and many other bugs and sudden restarts, some of them might be cause by my phone or not, but since 5.1 everything is a lot more stable.