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.
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 have registered on htcdev.com.
i followed the steps to the point where i had to execute the fastboot file to get an identifier token using a cmd command.
for some reason it say "waiting for device"
it has been like that for hours.
tried it about 3 times. I had a problem with rebooting into bootloader using VOLUME DOWN + POWER button so i ised abd and it worked
exact command i typed was "fastboot oem get_identifier_token"
PLEASE HELP ME
I don't remember all details altough my experience is quite fresh (week back) ...
Try disable your antivirus and start htc sync.
Device is no properly detected/installed by windows. You need proper driver. Drivers are part of htcsync so try to install or reinstall latest version of htcsync.
And, although I've only just.noticed it ...
Please don't double-post. There was no need to stick this in both the General and Q&A forums.
Usb debugging?
Sent from my HTC Desire S using xda app-developers app
From the screenshots I can see that your adb is working from c:\abd folder.
I guess your fastboot binary is there as well.
So you have 2 options:
1) issue the command "fastboot oem get_bla_bla" from c:\adb
2) copy the files from c:\adb to c:\Android (including fastboot) and try again
But IMO is much better to downgrade and S-OFF via revolutionary. Just take the time to do some research across the guides around and go for it
amidabuddha said:
But IMO is much better to downgrade and S-OFF via revolutionary. Just take the time to do some research across the guides around and go for it
Click to expand...
Click to collapse
+1
Sent from my HTC Desire S using xda app-developers app
changing usb ports have always helped me with , waiting for device problems,
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
I rooted my phone and unlocked it used the all in one tool kit.
my phone is htc one s (s4)
I can get into bootloader / fastboot menu I can get into twrp, when I connect usb it says "fastboot usb in red" in the fastboot boot loader menu so that should be connected but its not. Only time it connects is in twrp, my computer will detect "htc mtp device" it shows up fine in device manager, but after about 10 secs the device is no longer be detected and yellow ! will show over "htc mtp device" in device manager. What is weird even more is I can run certain command with adb " adb devices" tells me its connected but it wont sideload or fastboot , it just says "waiting for device". I can restart the usb by "adb usb", it will temporary install and run but 10sec or so later is disconnects and yellow! will show over "htc mtp device" in the device manager. Does anyone have an idea how to fix this? Is my phone a hard brick now?
Please help me.
Thank you very much.
You're in the wrong forum, this is the HTC One XL forum.
Sent from my Evita
timmaaa said:
You're in the wrong forum, this is the HTC One XL forum.
Sent from my Evita
Click to expand...
Click to collapse
im sorry.. i saw it say htc one so I thought it applied for all. where would I go for my problem to post?
Use Google, search for HTC One S XDA.
Sent from my Evita
Well, I managed to previously unlock bootloader, flash TWRP, then rooted an A9 I got on eBay for sprint. When I factory reset it, it went into some French mode, so I decided to start clean and used the official HTC 1.57XXXX RUU.exe Im still unlocked and S-off but I am not rooted and dont have TWRP.
SO now my problem; I CANNOT ****in get ADB command to pickup the A9, all it outputs is OFFLINE.
I went as far as CLEAN install of windows ten. Wiped EVERYTHING.
installed HTC sync manager
installed 15 ADB
restart computer
at this point any normal human being would think that the ADB command should pickup the phone by now.
BTW I've set developer mode, OEM unlocking and usb debugging and accepted that this computer can transfer files.
This sucks. please help. This is day 3 of troubleshooting on my own for something that should have been done in an hour
wholigan423 said:
Well, I managed to previously unlock bootloader, flash TWRP, then rooted an A9 I got on eBay for sprint. When I factory reset it, it went into some French mode, so I decided to start clean and used the official HTC 1.57XXXX RUU.exe Im still unlocked and S-off but I am not rooted and dont have TWRP.
SO now my problem; I CANNOT ****in get ADB command to pickup the A9, all it outputs is OFFLINE.
I went as far as CLEAN install of windows ten. Wiped EVERYTHING.
installed HTC sync manager
installed 15 ADB
restart computer
at this point any normal human being would think that the ADB command should pickup the phone by now.
BTW I've set developer mode, OEM unlocking and usb debugging and accepted that this computer can transfer files.
This sucks. please help. This is day 3 of troubleshooting on my own for something that should have been done in an hour
Click to expand...
Click to collapse
You should try changing USBcable
romanch said:
You should try changing USBcable
Click to expand...
Click to collapse
I did. I have HTC official from the A9 that should be 100% good and another from my GF's M9 and neither are working this is hopeless!
So "adb devices" give your nothing? not a mes on the phone to let adb connect?
Sent from my HTC One A9 using XDA-Developers mobile app
jaypeg123 said:
So "adb devices" give your nothing? not a mes on the phone to let adb connect?
Sent from my HTC One A9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Must have been a driver error because I was able to do it on my other laptop no problem. The weird thing is I flashed twrp via ADB on the A9 (on my pc before getting errors) and then I did my girlfriends M9 and thats when the drivers got funky.
Still tho problem remains I get device offline if I try to hook up to my PC, if it was because of any settings to select on my phone it would say "unauthorized" but thats not the case, I've authorized the phone for usb debugging to my PC
The offline must be due to you using the wrong version of adb, or could it be a firewall/antivirus prog blocking connection?
Sent from my HTC One A9 using XDA-Developers mobile app