Hello all, I believe this is the correct thread for this topic post. Basically what I want to ask is, can you help me at all with this? What's happening is whenever I try to unlock the bootloader, I get to the part where it says "Getting CID", but it always says after < waiting for device >. I have tried all my usb ports, installed all drivers, it also is in usb debugging mode. I really want to do this but I just can't. Please help me with my problem. Thanks!
Does your phone say Fastboot USB with red highlighting?
If you not are in boot loader and not fastboot
Sent from my One X using xda app-developers app
Related
I posted this before but didn't get much response and I still have this problem. I rooted my phone using the 1.85 method, and am currently rooted, but not unlocked. I've tried to unlock the bootloader, but since device manager does not detect the device I can't unlock it. The phone charges when connected to the PC (IO panel, not front), but the connection type does not appear in the notification pull-down, and device manager does not display the device. This wasn't true before rooting, and now that my PC can't detect the phone I can't unlock and I can't copy over files from my PC to my phone. I have current drivers successfully installed, and I haven't updated any software beyond stock on my phone (1.85, 4.0.3), though AT&T has tried to push an update on my phone this morning.
How can I solve my problem? This is my first Android phone, and I wanted to unlock the bootloader to be able to flash ROMs and develop my own, but at the moment it isn't possible.
Yarok said:
I posted this before but didn't get much response and I still have this problem. I rooted my phone using the 1.85 method, and am currently rooted, but not unlocked. I've tried to unlock the bootloader, but since device manager does not detect the device I can't unlock it. The phone charges when connected to the PC (IO panel, not front), but the connection type does not appear in the notification pull-down, and device manager does not display the device. This wasn't true before rooting, and now that my PC can't detect the phone I can't unlock and I can't copy over files from my PC to my phone. I have current drivers successfully installed, and I haven't updated any software beyond stock on my phone (1.85, 4.0.3), though AT&T has tried to push an update on my phone this morning.
How can I solve my problem? This is my first Android phone, and I wanted to unlock the bootloader to be able to flash ROMs and develop my own, but at the moment it isn't possible.
Click to expand...
Click to collapse
Did you turn on usb debugging? And after you connect ur phone did you try adb to see if your phone is detected
Sent from my HTC One X using xda premium
abhipati said:
Did you turn on usb debugging? And after you connect ur phone did you try adb to see if your phone is detected
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, USB debugging is on. I tried adb using this guide (http :// www . thesuperusersguide . com/adb-backup--restore.html sorry can't post links), but once I paste in “adb backup –apk –shared –all –f /backup/mybackup.ab," I get back adb: unable to connect for backup."
Yarok said:
Yes, USB debugging is on. I tried adb using this guide (http :// www . thesuperusersguide . com/adb-backup--restore.html sorry can't post links), but once I paste in “adb backup –apk –shared –all –f /backup/mybackup.ab," I get back adb: unable to connect for backup."
Click to expand...
Click to collapse
When you type adb devices, what do u get output
Sent from my HTC One X using xda premium
In 1.85, there was the option to default your connection type. It may be set to charge only. Check your settings. This may be the issue.
abhipati said:
When you type adb devices, what do u get output
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
XNine said:
In 1.85, there was the option to default your connection type. It may be set to charge only. Check your settings. This may be the issue.
Click to expand...
Click to collapse
As it seems the USB port I was using wasn't connected properly to the motherboard, so I had to do some tinkering there. It all worked out though*, thanks for the help.
*Except that I accidentally installed the OTA update instead of postponing it and removing notifications... Now begins the wait for a 2.23 root method. Woe is me.
I am doing the new 2.20 root for the one x. Alright well i got through getting the Unlock_code.bin and when i type it into the command prompt it just says "waiting for device". My device is connected and i can see it the device manager. And it is in the correct folder and everything. ANy ideas on why its not working?
Try unplugging your phone, restart into fastboot and try again. It should work then
Sent from my HTC One XL using xda app-developers app
Or, if you're in your ROM. Go to settings and enable USB Debugging.
Ok guys so here is my problem... I am new to rooting android phones as I just converted from an iPhone.
So I found Hasoon2000`s awesome All In One Toolkit for my HTC One S. I went for it... I installed the HTC Drivers, registered at HTC DEV and wanted to get my Token ID but no luck. I plug in the phone (USB Debugging enabled, fast boot disabled) and click on go. The phone goes into the bootloader (I believe the one with the white background and diff. color text) and the cmd on my PC still says waiting for device. I dont know why, I tried both fast boot on and fast boot off, but neither works and I really want to root my phone I would really appreciate , if someone could help me because I cant seem to figure out how to get past this error.
Sorry but questions go in q&a as posted in the rules
Sent from my HTC VLE_U using xda app-developers app
Hello all,
i got a problem with my HTC Sensation XE.
I tried to root the device, following http://forum.xda-developers.com/showthread.php?t=1192300 and http://forum.xda-developers.com/showthread.php?t=1870233
But im unable to complete the htcdev part. When I boot the device into the bootloader and chooce Fastboot, it doesnt connect to my pc. When I try adb devices, it doesnt see it. When I try this when the device is normally booted, it shows using that command.
Is this a corrupt bootloader, and can I fix this?
remi1986 said:
Hello all,
i got a problem with my HTC Sensation XE.
I tried to root the device, following http://forum.xda-developers.com/showthread.php?t=1192300 and http://forum.xda-developers.com/showthread.php?t=1870233
But im unable to complete the htcdev part. When I boot the device into the bootloader and chooce Fastboot, it doesnt connect to my pc. When I try adb devices, it doesnt see it. When I try this when the device is normally booted, it shows using that command.
Is this a corrupt bootloader, and can I fix this?
Click to expand...
Click to collapse
Have you installed htc drivers?
Also use usb 2.0 ports
And in the bootloader screen make sure it shows fastboot usb
Sent from my HTC Sensation using xda premium
rzr86 said:
Have you installed htc drivers?
Also use usb 2.0 ports
And in the bootloader screen make sure it shows fastboot usb
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Indeed, had the wrong drivers. I found a thread with the correct ones and everything is solved now. My device is rooted.
Thanks for your reply
P. S for anyone looking if you have a corrupt bootloader your only option is jtag as your bricked. So make sure you use the correct terminology
Sent from my HTC Sensation 4G using xda app-developers app
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
InV15iblefrog said:
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
Click to expand...
Click to collapse
your phone must be in FASTBOOT bootloader mode..not in the HOME of your ROM..
if you don't wan to turn off your phone first and pressing volume down + power to go to bootloader..then you can using a adb command on cmd while your phone is still in the HOME of your ROM.. type "adb reboot bootloader" then select "FASTBOOT" now you can type "fastboot oem get_identifier_token"
don't forget to disabled Fast boot mode and enable USB Debuging first from the system settings and just connect your phone to pc as charge mode..
hope this help..
Sorry mate. Tried that before your post though.
However the person for whom I was doing this no longer needs it doing, and plans for a newer device, so I no longer have this device available. Thus, i thanked you, since it was a cue for me to mention that.
Cheers.
This model of HTC is died