I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
RandyThor said:
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Click to expand...
Click to collapse
Do you install Motorola drivers..?
Salik Iqbal said:
Do you install Motorola drivers..?
Click to expand...
Click to collapse
yes the newest drivers are installed. It shows up in device manager as "MOT Single ADB Interface". I can also detect it in fastboot, though most commands won't work.
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
varunpilankar said:
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
Click to expand...
Click to collapse
when following the second link steps i get stuck at step 8. Im not sure what he means by click on the device. does he mean the 'Mot Single ADB Interface' device? i clicked properties on that then i clicked update and i selected the folder where i kept the signed sys files. there was nothing about QHSUSB_DLOAD as it said in the tutorial though. anyway afterwards there was no port called Qualcomm HS-USB QDLoader 9008 so i couldn't get a portnumber to continue the process.
The other link you gave i assumed id go to Moto X BE\1_Repair_Boot (RSD Lite)\1060 and flash the gpt.bin and the motoboot.img but i got this error:
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.210s
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.420s]
writing 'motoboot'...
Motoboot: Unknown partition name
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.700s
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
OrlandoAlex said:
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
Click to expand...
Click to collapse
For both of you.. @RandyThor and @OrlandoAlex check thread after 12hrs.. i have something for you which may hopefully fix thay issue.
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
PiArc said:
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
Click to expand...
Click to collapse
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Salik Iqbal said:
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Click to expand...
Click to collapse
No worries. Whenever you get the chance.
RandyThor said:
No worries. Whenever you get the chance.
Click to expand...
Click to collapse
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
PiArc said:
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
Click to expand...
Click to collapse
It was from att latest firmware gpt and aboot.
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
you are the GOAT my friend
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
RandyThor said:
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
Click to expand...
Click to collapse
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
RandyThor said:
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
Click to expand...
Click to collapse
So lets close the thread by requesting moderator..
Salik Iqbal said:
So lets close the thread by requesting moderator..
Click to expand...
Click to collapse
do i have to do that lol? im a noob
Related
Hi, I am a professional phone repair guy and I am very familiar with adb, rooting, android OS ect. So I will probably only need to be pointed in the right direction... I have searched 3 days for a solution and I know that I haven't tried EVERY possible recovery solution... But the links on the SBF Droid 3 flash files are "DEAD" and I can't find them...
So I used psouza4's one click and got this...
AP Fastboot Flash Mode (S) (Boot Failure)
0A.53
Battery OK
OK to Program
ConectUSB
Data Cable
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0035 )
Invalid CG OTV (CG: system)
I know I most likely just need an SBF file for whichever STOCK firmware I was on, not sure which so if someone can link me the file or at least point me in the right direction to restore this phone. (Had it 2 days and soft bricked)
Thanks in Advance
If it's an XT862, it seems you have 2 choices (verizon stock roms) here:
http://forum.xda-developers.com/showthread.php?t=1295839
I prefer the method below. Download the 450MB-ish file and then just follow the instructions in the OP. It takes about 5 minutes to get back to box stock. Just used it today actually.
http://forum.xda-developers.com/showthread.php?t=1339816
redsox985 said:
I prefer the method below. Download the 450MB-ish file and then just follow the instructions in the OP. It takes about 5 minutes to get back to box stock. Just used it today actually.
http://forum.xda-developers.com/showthread.php?t=1339816
Click to expand...
Click to collapse
Hey. Im Having the same problem as the last guy ..Unfortunately the links are now bad since the Feds busted megaupload..Any chance you can post a different link to this file? Any help is greatly appreciated!
I may have a copy of the files needed to do the fast/easy unbrick method shown elsewhere in the general forum. Don't know if it will help, but I'll check when I get home tonight and maybe put it on dropbox.
Sent while mobile using Tapatalk.
fxwrangler said:
Hey. Im Having the same problem as the last guy ..Unfortunately the links are now bad since the Feds busted megaupload..Any chance you can post a different link to this file? Any help is greatly appreciated!
Click to expand...
Click to collapse
That link goes to multiupload, it can be downloaded from there use fileserve or another link on multiupload.
I have established all that info actually I have the file Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4.rar But that is what brought me to that state. I pretty well know that I bricked by not properly removing the old bootstrap before flashing the SAFE one for CM9 ICS the feds are taking out multiupload, but all the secondary links are dead. I can Drop box any files I have, they might help some people with different soft bricks but I'm worried about my phone cause I use psouza's many times and always the same result. I also tried flashing his firmware with RSD 5.5 and .5.4 didn't work still it constantly gets failed boot. I ALSO tried this file all those ways, VRZ_XT862_5.5.1_84_D3G-55_1FF_01 which did not work. I haven't attempted any Fast boot methods or linux, (because my linux machine is currently crashed)... I think that last file was the Verizon 5.5.959, and I read somewhere you couldn't go backwards if you were already at, Verizon 5.6.890 So does ANYONE please have that file, or maybe know if I'm doing something wrong?
edit : whenever i use rsd it never completes always failed at random point in the process... But I read somewhere that a guy edited hxml file or something to jump back and try to flash only certain sections of the phone. Can anyone give me any pointers on that? keeps giving size rturned by phone error
Let me just get this straight; you didn't try the fast/easy unbrick method wherein you use fastboot and Windows cmd line tool to flash to stock? If you did, never mind me lol. If you haven't, it's great and I used Windows to get mine back to stock.
I am ready to share those files via PM (dropbox link) if any one needs em.
Sent while mobile using Tapatalk.
protechcertifiedrepair said:
I have established all that info actually I have the file Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4.rar But that is what brought me to that state. I pretty well know that I bricked by not properly removing the old bootstrap before flashing the SAFE one for CM9 ICS the feds are taking out multiupload, but all the secondary links are dead. I can Drop box any files I have, they might help some people with different soft bricks but I'm worried about my phone cause I use psouza's many times and always the same result. I also tried flashing his firmware with RSD 5.5 and .5.4 didn't work still it constantly gets failed boot. I ALSO tried this file all those ways, VRZ_XT862_5.5.1_84_D3G-55_1FF_01 which did not work. I haven't attempted any Fast boot methods or linux, (because my linux machine is currently crashed)... I think that last file was the Verizon 5.5.959, and I read somewhere you couldn't go backwards if you were already at, Verizon 5.6.890 So does ANYONE please have that file, or maybe know if I'm doing something wrong?
edit : whenever i use rsd it never completes always failed at random point in the process... But I read somewhere that a guy edited hxml file or something to jump back and try to flash only certain sections of the phone. Can anyone give me any pointers on that? keeps giving size rturned by phone error
Click to expand...
Click to collapse
There is a moto-fasboot for windows, I would suggest trying it, looking in the xml files will tell you what order to fastboot flash in. Also note, if I'm not mistaken, that the verizon OTAs are named after the system version they are meant to be applied to, as opposed to the system version they upgrade you to.
Sent from my XT860 using xda premium
mmsomekid said:
My buddy made a torrent mirror of the sbf for anyone still looking for it. You can get it here
Click to expand...
Click to collapse
got this off the recovery thread.
I have used quick unbrick over a dozen times for various brick causes. It's never failed me and I'm a huge fan. Especially because it's faster than RSD. Make sure you have the latest drivers installed and stock USB cable as well. This changes a lot.
BenSWoodruff said:
Let me just get this straight; you didn't try the fast/easy unbrick method wherein you use fastboot and Windows cmd line tool to flash to stock? If you did, never mind me lol. If you haven't, it's great and I used Windows to get mine back to stock.
I am ready to share those files via PM (dropbox link) if any one needs em.
Sent while mobile using Tapatalk.
Click to expand...
Click to collapse
NO, I DID use the quick unbrick and the RSD lite methods. But no I did not yet try the Fast boot CMD style I will try tonight or tomorow, and that is only half my problem the other was getting those files for the stock, I only have pouzas version extracted and ran through rsd. So I will download files in the TOrrent mentioned post and try that. Thanks guys for the help I got mad donations for anyone who gives me th right poimter I need to fix my phone.
protechcertifiedrepair said:
NO, I DID use the quick unbrick and the RSD lite methods. But no I did not yet try the Fast boot CMD style I will try tonight or tomorow, and that is only half my problem the other was getting those files for the stock, I only have pouzas version extracted and ran through rsd. So I will download files in the TOrrent mentioned post and try that. Thanks guys for the help I got mad donations for anyone who gives me th right poimter I need to fix my phone.
Click to expand...
Click to collapse
The quick unbrick method (which I believe is mirrored in that torrent) is the CMD style unbricking method. I'm using it for the second time today, actually!
Here's a video I made recently showing how it works and whatnot.
http://www.youtube.com/watch?v=pcne9tFtBxY
protechcertifiedrepair said:
NO, I DID use the quick unbrick and the RSD lite methods. But no I did not yet try the Fast boot CMD style I will try tonight or tomorow, and that is only half my problem the other was getting those files for the stock, I only have pouzas version extracted and ran through rsd. So I will download files in the TOrrent mentioned post and try that. Thanks guys for the help I got mad donations for anyone who gives me th right poimter I need to fix my phone.
Click to expand...
Click to collapse
I believe it's a script you double click on after unzipping the file to your PC. If you have any trouble downloading, I have a copy of the .zip I can share. You connect via usb, power up while holding m button on D3 keyboard and select AP Fastboot mode, then run the script.
Just read the OP carefully and you should be fine ;-)
Good luck.
Just my input on this "One Click " ...it does work..I tried for three days and when I got to the "sending", it wouldnt go any further..So I finally tried it on another computer & Shazaam..It Worked!!..Thanks fot all the help from this forum!!
Sent from my DROID3 using Tapatalk
As far as I know, if the fast/easy unbrick method isn't working, it could very well be a usb/driver issue. The phone, once connected to the PC, should show up in device manager (windows). If it isn't connecting properly, it should say 'waiting for device.' If it is connected but doesn't go all the way through the process, trying a different/newer PC, stock usb cable, or updating drivers may be necessary.
Maybe you can describe what is the exact point that you run into a road block and we can see better the cause of the issue. I'll keep reading around to see if I can understand it better.
Sent while mobile using Tapatalk.
BenSWoodruff said:
As far as I know, if the fast/easy unbrick method isn't working, it could very well be a usb/driver issue. The phone, once connected to the PC, should show up in device manager (windows). If it isn't connecting properly, it should say 'waiting for device.' If it is connected but doesn't go all the way through the process, trying a different/newer PC, stock usb cable, or updating drivers may be necessary.
Maybe you can describe what is the exact point that you run into a road block and we can see better the cause of the issue. I'll keep reading around to see if I can understand it better.
Sent while mobile using Tapatalk.
Click to expand...
Click to collapse
OP, have you checked your drivers to see if they're the most recent? I, too, have been mentioning them for days with no acknowledgement of it. I feel like this is the only thing left other than a very strange device.
I have read over and over again for hours and I cant find a solution. I tried to used RDS Lite with Droid_3_SBF_5.6.890 for my XT860 and got the multiboot issue. I never could pass from 1/18
At that time I was still able to boot to application pressing m and selecting Normal. Then I read this forums and tried the fast/easy unbrick method.
I didnt have any problem to connect but some files were OK and someothers failed then I received a new error:
Invalid CG OTV: Invalid SP Data
Invalid CG HAB: CG: System Status: 0x0035
and cannot longer enter into the application using the m button.
The "easy" methods shows:
**
** Now flashing the Verizon DROID 3 OTA 5.6.890 updated system to your phone...
**
erasing 'userdata'... OKAY [ 0.014s]
erasing 'cache'... OKAY [ 0.039s]
sending 'recovery' (9216 KB)... OKAY [ 1.042s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
sending 'boot' (8192 KB)... OKAY [ 1.183s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
sending 'devtree' (512 KB)... OKAY [ 0.334s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
sending 'logo.bin' (854 KB)... OKAY [ 0.363s]
writing 'logo.bin'... OKAY [ 0.391s]
sending 'preinstall' (262144 KB)... OKAY [ 25.000s]
writing 'preinstall'... OKAY [ 22.900s]
sending 'preinstall' (229376 KB)... OKAY [ 21.985s]
writing 'preinstall'... OKAY [ 20.234s]
sending 'cdrom' (12032 KB)... OKAY [ 1.319s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
sending 'radio' (14368 KB)... OKAY [ 1.689s]
writing 'radio'... OKAY [ 1.447s]
sending 'system' (262144 KB)... OKAY [ 26.719s]
writing 'system'... OKAY [ 23.026s]
sending 'system' (175872 KB)... OKAY [ 17.813s]
writing 'system'... OKAY [ 15.383s]
rebooting...
**
** Done!
**
Press any key to continue . . .
I am getting out of ideas. PLEASE HELP ME!!!!
SOLVED!!! I was using the wrong SBF. Now it is working using RDS Lite 5.5
Here is the list of SBF for many motorola devices. Jus click in Milestone 3 Firmware at the end of the 1st post:
http://forum.xda-developers.com/showthread.php?t=1370721
I am so Happy
protechcertifiedrepair said:
Hi, I am a professional phone repair guy and I am very familiar with adb, rooting, android OS ect. So I will probably only need to be pointed in the right direction... I have searched 3 days for a solution and I know that I haven't tried EVERY possible recovery solution... But the links on the SBF Droid 3 flash files are "DEAD" and I can't find them...
So I used psouza4's one click and got this...
AP Fastboot Flash Mode (S) (Boot Failure)
0A.53
Battery OK
OK to Program
ConectUSB
Data Cable
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0035 )
Invalid CG OTV (CG: system)
I know I most likely just need an SBF file for whichever STOCK firmware I was on, not sure which so if someone can link me the file or at least point me in the right direction to restore this phone. (Had it 2 days and soft bricked)
Thanks in Advance
Click to expand...
Click to collapse
If your a professional phone repair guy y are you asking for help? You may be phone repair guy but not a professional because a professional will have done it with out asking for are help but I do think if you call your self a professional then you must be very good at it is all but not as good as a professional
Sent from my XT862 using XDA
leerpsp said:
If your a professional phone repair guy y are you asking for help? You may be phone repair guy but not a professional because a professional will have done it with out asking for are help but I do think if you call your self a professional then you must be very good at it is all but not as good as a professional
Sent from my XT862 using XDA
Click to expand...
Click to collapse
Not trying to start something, but he could be a phone repair person for a different company (not Motorola), he may usually deal with phones that have unlocked bootloaders, who knows.
In the workplace-and life in general-it is an admiral trait to ask for help rather than just "wing it". Even company heads ask for help. If he made a mistake, he could end up with a few hundred dollar paper weight.
Sent from my DROID3 using xda premium
Shall we have a centralized place for discussion (or better, solutions) related to the bootloop issue happened on HTC One GPe? Apparently I'm not the only one in this situation, and having a single thread will help others to find the solution more easily.
The problems are basically having a soft bricked GPe and only bootloader is accessible. The GPe device is real, S-On, locked or relocked, with stock firmware of OS-3.58.1700.5 and HBOOT 1.54, but without a working rom.
1. flashing the GPe RUU by graffixnyc from this thread won't work because of the signature verification failure, which makes sense since it's not signed by HTC (the firmware.zip flashes through because it's signed by HTC).
2. fastboot oem unlock does not work and shows the following error:
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.543s]
finished. total time: 0.543s
3. fastboot flash unlocktoken Unlock_code.bin fails silently, i.e. the confirmation screen does not show up on device.
4. trying s-off the device is not feasible without a working rom and unlocked bootloader.
5. fastboot boot <custom_recovery>.img fails for both CWM and TWRP:
Code:
downloading 'boot.img'...
OKAY [ 1.123s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.123s
6. fastboot erase cache and factory reset does not help.
Any other options so we could have a try? @nkk71 @SaHiLzZ
Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.
I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.
SaHiLzZ said:
Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.
I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.
Click to expand...
Click to collapse
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.
This seems to be happening more and more. I'm in the same boat. Tried to update a GPe HTC One and got stuck.
I have contacted HTC support as stated in this thread:
http://forum.xda-developers.com/showthread.php?t=2492469&page=5
They we able to help get his up and running. Hopefully they can help me out to with out the need to pay extra charges.
I will update on the progress, but seeing as we are entering the weekend, it will probably only be next week.
I miss my phone
Thanks for the thread and the clear summary. I have exactly the same issue with my stock Gpe and am anxiously waiting for a solution.
Sent from my Nexus 7 using XDA Premium 4 mobile app
joe7wu said:
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.
Click to expand...
Click to collapse
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.
mderksen said:
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.
Click to expand...
Click to collapse
I think he is talking about the method on the device, not from HTC Dev.
On the device, using "fastboot oem unlock" or the HTC Dev method dosent work.
As stated above the first returns an error and the .bin method shows a success message, but nothing actually happens.
This is my situation anyways.
Any one with locked, not relocked bootloader having the same issue. Wonder how Google will fix this..
+1 I'm having the same problem
Edit: They should make this a sticky thread for as long as the problem exist
I am also having the same issue on my google play edition. S-On. I reflashed a stock recovery image so I could update to stock ROM. Now, I am stuck in a bootloop. I cannot reload any kind of custom recovery (I say that I can't. When I do, the phone will not boot into recovery. It just jumps to the Google screen, attempts to load the OS and then restarts). I AM able to unlock and relock using fastboot oem unlock and lock. I've attempted to reload the firmware and it seems to work (via cmd loading), but the loop process begins again. I attempted to flash a 4.3 firmware I found, but received the blue screen of nothingness when I did.
I'm lost. Possibly only solution is sending back in for repair. I just got the phone and this is annoying as heck..
alcaloide_ said:
+1 I'm having the same problem
Edit: They should make this a sticky thread for as long as the problem exist
Click to expand...
Click to collapse
Yeah, a sticky thread will help a lot. Anyway, I'm still waiting for those people who got in touch with HTC and see how it goes. A bit worried about the fact that I'm in Canada and a friend in US bought this phone for me. Not sure how the custom support will be like in my case.
So, a thought just occurred to me - i haven't updated any of my tools for fastboot since i originally unlocked the system a few months ago.
I am not currently at home, so i cannot check on this, but perhaps this will help others....
The current sdk tools version is 22.3 : http://developer.android.com/sdk/index.html
Could perhaps updating these tools help us re-unlock our phones?
If someone checks and tries this, and then the fastboot oem unlock command, let me know if it is simply a windows software thing.
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Hope this helps somebody...
AmirH said:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Hope this helps somebody...
Click to expand...
Click to collapse
Interesting. I chatted with an HTC rep this morning and I am sending the phone to an HTC repair facility in Houston. I wish Google would just do an exchange. DId they give you a hard time? Should I just call them and ask for an exchange?
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
AmirH said:
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
Click to expand...
Click to collapse
Thanks! I assume it is a one year warranty? My issue is that I bought it used. I wonder if they will give me a hard time about that.
---------- Post added at 03:48 PM ---------- Previous post was at 03:34 PM ----------
AmirH said:
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
Click to expand...
Click to collapse
Well, i just got off the phone with them. I'm glad you had more success than I! The lady said she could not identify a troubleshot and, since I did not buy from them under my account, they couldn't help me.
AmirH said:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Click to expand...
Click to collapse
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
elisaw99 said:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
Click to expand...
Click to collapse
I would give it a shot
elisaw99 said:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
Click to expand...
Click to collapse
Let us know how it goes! II will be sending mine to HTC tomorrow
I just got off of the phone with Google. Rep indicated that many have been going through this problem. They are sending out a new phone right away and I will send mine back upon receiving the new one. Bought the phone in July from Google Play Store. Great customer service!
Hello!
This is my first post... then sorry if i mest something,
well im from mexico (cancun)
and i have a moto X but now is brick,
im sure hard brick not vibrated not on not recovery,
i was reading in this forum possibilities about this issue,
i have the "QHUSB_DLOAD"
How i can turn alive my phone?
Is it completely dead?
someone can help me? i will express gratitude and someone show me how i can repair... of curse i will pay them. thanks alot
AT&T 32 gb
The first thing to do on xda is always do a search or browse through the different sections for your phone.
http://forum.xda-developers.com/showthread.php?t=2629057
Sent from my N5 cell phone telephone....
kj2112 said:
The first thing to do on xda is always do a search or browse through the different sections for your phone.
http://forum.xda-developers.com/showthread.php?t=2629057
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
well, i was doing that any way i can put my phone in recovery but not success with flashing to come alive
davcastroruiz said:
well, i was doing that any way i can put my phone in recovery but not success with flashing to come alive
Click to expand...
Click to collapse
we need more info why can't you flash it back to stock what error's are you getting. more then likely you are trying to flash the wrong version of android and that is why it wont flash.
so we need
1. what error's you got
2. what model or carrier your phone is with
preflash validation failed
dray_jr said:
we need more info why can't you flash it back to stock what error's are you getting. more then likely you are trying to flash the wrong version of android and that is why it wont flash.
so we need
1. what error's you got
2. what model or carrier your phone is with
Click to expand...
Click to collapse
Thank u for reply
Ox56 failed to hab check for boot
Preflash validation failed for boot
" For" recovery
PIV block validation forma system failed
Invalid piv image: system
Also i try with att's fimwares
But 4.4.2 is not yet
I almost forget it before i see a conde
Partition (boot) security versión downgraded
I guess i need at't 4.4.2 right?
Or why i can do nothing ? With vwz or anything else like retails in other motorola..
try this: http://forum.xda-developers.com/moto-x/development/script-moto-x-restore-utility-windows-t2597625
helped me
ericizzy1 said:
try this: http://forum.xda-developers.com/moto-x/development/script-moto-x-restore-utility-windows-t2597625
helped me
Click to expand...
Click to collapse
thanks ericizzy but seems like there is not link for windows man :C only mac and linux i tried on ubuntu system 13.14 but doesnt work do u have the exe, for windows?? could u upload to a server ?? thank you!
davcastroruiz said:
thanks ericizzy but seems like there is not link for windows man :C only mac and linux i tried on ubuntu system 13.14 but doesnt work do u have the exe, for windows?? could u upload to a server ?? thank you!
Click to expand...
Click to collapse
http://rootjunkysdl.com/?device=Moto X
ericizzy1 said:
http://rootjunkysdl.com/?device=Moto X
Click to expand...
Click to collapse
doesnt work for me sir :/
failed also in piv and recovery and boot
anyway i guess i have to be patient and wait for the sw upgrade of at&t
thank you any way for the link i have now moto x restore utility
Hey ,
seems like you guys are my last chance. I will try to explain my situation:
So today I was just messaging when suddenly some process.google.media (cant recall exactly) error was spamming my phone. I restarted the phone and then the problems started happening. The moto X was stuck in the boot screen.
I read that i should install TWRP and factory reset. So after doing that I was pretty much stuck in recovery.
Whenever i turned the phone on, It was immediately booting the TWRP.
So I thought fine, I will probably have to install a ROM, so it can actually boot something.
I went for the xt1052 Lollipop 5.1 untouched EU version of the forum. Still It somehow didnt boot.
Next I came across the following youtube video: youtube /watch? v=ne46LQ3n7nA
(cant post url)
Followed all the instructions in the video and it actually got my phone to work.
I thought that now everything would be just like when I bought my phone.
So I installed the official lollipop update which popped up on my screen.
And now Im stuck again...
Im sitting in Fastboot Mode and get the following error:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
Dont know how many threads I read by now on here to find a solution but I cant find any..
I installed RSDLite, but Im not sure which version to use to flash now.
Tried two zip folders, but apparently the xml file was missing.
Im kinda scared to use the wrong zip anyways and screw my phone completely if it isnt already.
Id really appreciate any help since im currently clueless.
Thanks boys!
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
This is likely your problem and the result of flashing a lower version onto your Moto x. I would start looking how/if you can recover from a downgrade.
I might add some additional error description to make ppl find this thread in the future :
Stuck in bootloader - Fastboot - cant enter recovery - when choosing any options from fastboot: Load kernel (boot) failed
-----------------------------------------------------------------------------------------------------------------------------------------
Alright seems like i got it working again.
Since this forum helped me so much I want to contribute something to it by giving u guys my solution.
So I stumbled across alot of threads with @KidJoe replying. He really knows his stuff, when it comes to the MotoX.
I dont know how to quote off of other threads, but this quote of KidJoe got me on the right track:
" GPT.BIN is the partition table. Its important. When GPT.BIN and MOTOBOOT.IMG are mismatched from the rom on your phone you could brick when taking an upgrade.
In most cases, the GPT.BIN has matched from model to model when on the same rom (i.e. GPT.BIN from XT1060 4.4.4 rom has matched GPT.BIN of XT1053 4.4.4 rom).
However, try Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and see what happens. "
Alright so, here is what I grasped:
before things went bad for my phone, I was already on lollipop. Following the youtube video I downgraded it from 5.1 to 4.4.4.
While downgrading I already noticed that some commands failed, which was the gpt.bin stuff.
So after my phone was working on 4.4.4 and I used the Motorola Upgrade to 5.1 , there must have been a problem with the gpt.bin and motoboot.img , just like KidJoe said. Hence why I got stuck in Fastboot.
As I said in the first post, I had to find the right image for my phone.
In the Fastboot mode I saw that I was on 30.BE, and from what I understand that means im on lollipop and since I cant downgrade, I had to find the right lollipop version for my device.
Im also german, so I found this version:
XT1052_GHOST_RETDE_5.1_LPA23.12-15.5_cid7_CFC.xml.zip
KEEP IN MIND, my problem was having the wrong version all along, so you have to find the right version for your smartphone, dont make the same mistake I did!
I found my file on filefactory through this link here:
http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
(EDIT: I recommend using something like jdownloader to manage the download)
After I had the right version, I used rsdlite, chose my new file and my phone was working again.
However, I noticed that even tho my phone was working, the rsdlite actually failed somewhere between the lines. (I think it was step 7 or 9)
I was really happy to see my device boot up again, but wasnt happy with those errors and followed this link:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Option 5.
Now finally all the commands went OKAY in my cmd window.
After the motorola took some time to boot up again, I performed a factory reset via settings.
Just to make sure its fine and it seems like it is.
To end this thread off, I hope KidJoe will read this post.
Big thanks to you, your the man!
And even tho on some posts you came along a bit harsh, which really got me worried my phone would be completely dead, I wish you a nice christmas time dude!
Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Rodrigo_Codina said:
Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Click to expand...
Click to collapse
What is currently installed on each of the phones partitions?
JnNn98 said:
What is currently installed on each of the phones partitions?
Click to expand...
Click to collapse
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Rodrigo_Codina said:
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Click to expand...
Click to collapse
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
JnNn98 said:
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
Click to expand...
Click to collapse
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Rodrigo_Codina said:
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Click to expand...
Click to collapse
The error for the flash partition may be a result of using fastboot and not motorola's own fastboot. I've attached a motorola fastboot in a zip, so you can try again using that fastboot file. The extra commands don't help with anything really because they do not affect the flashing of partitions.
The fastboot getvar command is literally "get variable", so in that case it would just return the maximum file size that can be flashed I believe, and in case you were wondering:
fastboot oem fb_mode_set - Makes the phone automatically reboot into bootloader mode.
fastboot oem fb_mode_clear - Just resets the above commands setting back to normal booting.
The message I mentioned when I execute the command "fastboot flash partition gpt.bin"
sending 'partition' <32KB>...
OKAY [ 0.030s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.130s
Nevermind... I was trying to flash an old gpt.bin.
I guess that's the end, I give up. I don't know what to do, nothing works.
I'm thinking of buying an used device with broken screen for 1/3 of the price of a new one (350 reais, almost 100 dollars), disassemble everything and assemble only the motherboard in my device.
I really appreciate your help but I guess I need the Blanckflash and I searched and no one has it because motorola did not released for us.