i did all necessary stuff according to this tutorial: (windows 7, 64 bit)
http://forum.xda-developers.com/showthread.php?t=1583427
just after typing: fastboot oem get_identifier_token
cmd says: <waiting for device>
and now it just freezes at this point, i don't get any further
anybody got some advice?
garldehildehar said:
i did all necessary stuff according to this tutorial: (windows 7, 64 bit)
http://forum.xda-developers.com/showthread.php?t=1583427
just after typing: fastboot oem get_identifier_token
cmd says: <waiting for device>
and now it just freezes at this point, i don't get any further
anybody got some advice?
Click to expand...
Click to collapse
Sure. This happened to me at first. Try connecting your phone to a different USB port? Did you get a taskbar notification that a device had been connected? (Did you here the little dings? ha)
When cmd says waiting for device, it either means that your phone isn't in fastboot (which I assume it is, since you were following the directions), or that the device isn't connected.
Also, did you install the software package HTC sync? It's a fairly large download, but it might be a necessary one to get the required drivers to connect the phone.
Let me know if this helps.
Make sure you've installed the usb drivers required by selecting the check box for USB in the Extras.
Yep I got this error too and just had to install HTC sync from the HTC website to fix it. Easy peasy
Just use this guy's toolkit. Worked on my U.S one S.
http://forum.xda-developers.com/showthread.php?t=1604677
Sent from my HTC VLE_U using xda premium
well i downloaded this htc-sync stuff you said and everything just works fine
thanks a lot guys!!
Related
Ellos All. So I'm attempting to unlock the bootloader on on my Sensation. I'm following the instructions given via htcdev.com, everything was going okay but now I'm in CMD Prompt at the stage where I use the command fastboot oem get_identifier_token, and instead of the line of text that I'm supposed to get, I get <waiting for device> ... Any suggestions? thanks!
Did you follow the instructions? I've also done the HTC unlock method and it's flawless. I revolutionary'd after that but that's besides the point.
Not trying to sound like a douche, but you definately missed something. Maybe you didn't enable USB Debugging.
just do the s-off/rooted thing by this forum :
http://forum.xda-developers.com/showthread.php?t=1192300
and you will succed in 1 time oh and dont forget htc sync need to be on at phone with usb debugging
Yes, I've followed the instructions
I had a similar problem. I simply rebooted the phone (while it said "waiting for device") and all went well after that.
kaustic187 said:
Ellos All. So I'm attempting to unlock the bootloader on on my Sensation. I'm following the instructions given via htcdev.com, everything was going okay but now I'm in CMD Prompt at the stage where I use the command fastboot oem get_identifier_token, and instead of the line of text that I'm supposed to get, I get <waiting for device> ... Any suggestions? thanks!
Click to expand...
Click to collapse
first Enable USB debugging on phone . Boot your phone into bootloader. Connect your phone to pc via usb cable. Phone should read FASTBOOT VIA USB.
Make sure that HTC sync is off . ( Go to task manager, if you see the HTC sync is running, kill it)
Also remove anything else that may attempt to sync when you connect device.
Eg doubletwist, isyncr etc.
I relocked my bootloader and tried running a RUU but it keeps telling me that my phone is not connected. I'm using parallels for mac, I installed the drivers and I notice that when i connect the phone it doesn't say "fastboot usb" but when i push volume down is changes yet it still is unable to detect the phone. I installed the htc drivers but when I connect the phone is shows i dont have the drivers for " HTC Remote NDIS based device"
Could this be because im using parallels instead of a full windows pc?
please help, this is my very first android device and im scared I already ruined it
Yeah parallels is touchy. It works in VMware. Make sure in vm settings the usb device for the phone is set to always available to windows. If it is set to ask then it can lose connection.
Ok, Ill give a try.
I still have another problem. When I try to install the htc drivers, I get an error saying device not found. How am I able to install the drivers now?
I found the best way to get the driver installed is to install HTC sync
Thanks for the replies gunnyman, I have one last problem and hopefully theres a fix. I have a low battery and unable to flash the RUU. Is there a fix?
Is there battery actually low? Just shut down the phone and charge it up.
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Jaykelso said:
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Click to expand...
Click to collapse
Sorry. No idea. Sounds like it.
This seems very much to be a driver problem. Everything I find says Mac needs no driver for this device though.
dab works fine. android file transfer seems the device file structure fine. only thing not working, is when the device goes into fastboot mode, "fast boot devices" returns nothing. "fastboot oem unlock" sits and 'waiting for device' and never goes any further.
What's going wrong?
Blario said:
This seems very much to be a driver problem. Everything I find says Mac needs no driver for this device though.
dab works fine. android file transfer seems the device file structure fine. only thing not working, is when the device goes into fastboot mode, "fast boot devices" returns nothing. "fastboot oem unlock" sits and 'waiting for device' and never goes any further.
What's going wrong?
Click to expand...
Click to collapse
no driver's necessary, maybe your sdk installation is an old version and needs to be updated for kitkat?
fastboot is 1 word, not 2 as you have listed
you would execute this in the terminal:
./fastboot devices
( might be ./fastboot-mac devices )
ilanzo82 said:
no driver's necessary, maybe your sdk installation is an old version and needs to be updated for kitkat?
Click to expand...
Click to collapse
Yeah… not working at all. adb can see the device. I've never seen the mac fastboot see it. Also, it's fully updated to API 19.
Zepius said:
fastboot is 1 word, not 2 as you have listed
you would execute this in the terminal:
./fastboot devices
( might be ./fastboot-mac devices )
Click to expand...
Click to collapse
autocorrect keeps changing to two words in text boxes other than terminal. It's not finding anything. Others have seen different? That'd be shocking to me. With no drivers installed?
Blario said:
Yeah… not working at all. adb can see the device. I've never seen the mac fastboot see it. Also, it's fully updated to API 19.
autocorrect keeps changing to two words in text boxes other than terminal. It's not finding anything. Others have seen different? That'd be shocking to me. With no drivers installed?
Click to expand...
Click to collapse
I've used both adb and fastboot on a Mac for my Nexus 5, Nexus 4 and Nexus 7.
No drivers needed.
If you have adb and fastboot in the same directory and you can use adb without issues then fastboot should work as long as you've rebooted into the bootloader.
If it's still not working maybe take a look at this writeup about setting up adb and fastboot on a Mac... http://forum.xda-developers.com/showthread.php?t=1917237
Good luck!
Sent from my Nexus 5 using xda app-developers app
chef_christoph said:
I've used both adb and fastboot on a Mac for my Nexus 5, Nexus 4 and Nexus 7.
No drivers needed.
If you have adb and fastboot in the same directory and you can use adb without issues then fastboot should work as long as you've rebooted into the bootloader.
If it's still not working maybe take a look at this writeup about setting up adb and fastboot on a Mac... http://forum.xda-developers.com/showthread.php?t=1917237
Good luck!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Because I'm on API 19, that means I've already updated the SDK as far as is possible. ADB works. fastboot doesn't. What nexus 5 fastboot driver actually works?
Hello and good day/afternoon/night depending when you see this, I have a seems to be very frequent, the thing is that I've been trying to unlock my htc sensationg 4g (yeah, there are humans who still use it) and the thing is that every time I try to connect to the pc and write the
"fastboot oem get_identifier_token" command, the command line stucks at "waiting for device" and I know that that means it's not being recognized by the computer. I'll list everything I tried and all the information:
*My computer has windows 8.1 64 bit
*I installed the htc drivers and the android sdk
*my htc has android 4.0.3
*I have used usb 2.0 ports
*I have the fastboot files and all the files required
*I restarted the computer idk how many times to see if that does something
*everytime I connect the phone via fastboot mode, windows says device is not recognized
if need something else, simply ask for it, I have searched through thousands of forums and obviously here with no success, I hope you guys can help me
dark_paradox17 said:
Hello and good day/afternoon/night depending when you see this, I have a seems to be very frequent, the thing is that I've been trying to unlock my htc sensationg 4g (yeah, there are humans who still use it) and the thing is that every time I try to connect to the pc and write the
"fastboot oem get_identifier_token" command, the command line stucks at "waiting for device" and I know that that means it's not being recognized by the computer. I'll list everything I tried and all the information:
*My computer has windows 8.1 64 bit
*I installed the htc drivers and the android sdk
*my htc has android 4.0.3
*I have used usb 2.0 ports
*I have the fastboot files and all the files required
*I restarted the computer idk how many times to see if that does something
*everytime I connect the phone via fastboot mode, windows says device is not recognized
if need something else, simply ask for it, I have searched through thousands of forums and obviously here with no success, I hope you guys can help me
Click to expand...
Click to collapse
the issue is on win8
Search here in xda how to set up adb/fastboot on windows8
Or just download a Linux Live CD with fastboot and adb.
Just boot the cd and you can use fastboot and adb from terminal.
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
Turn on developer mode
Turn on OEM unlock and USB debugging
Install LG drivers
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
Type adb devices and authorize your computer on the phone
Type adb reboot bootloader
Type fastboot devices and make sure your phone shows up
Type fastboot oem unlock
Type fastboot getvar all
Should say (bootloader) unlocked:yes
Type fastboot reboot
What's the purpose for an Unlock bootloader?
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
At this point, nothing. It's a prelude to rooting.
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
Try fastboot devices and reinserting the usb cable. Doesn't make sense that adb sees it but fastboot does not unless it's a different driver. I think fastboot driver differs actually so do that driver too.
Ubuntu
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
You can also load Ubuntu on a flash drive and boot your computer from the flash drive. Then run the commands.
https://www.ubuntu.com/
Cheers
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
cordell12 said:
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
Click to expand...
Click to collapse
Do you guys have the oem unlock option at least?
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
wing_addict_usa said:
Do you guys have the oem unlock option at least?
Click to expand...
Click to collapse
yup, even warns us that certain things won't work if we enable it. adb works just fine too
cordell12 said:
yup, even warns us that certain things won't work if we enable it. adb works just fine too
Click to expand...
Click to collapse
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
wing_addict_usa said:
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
Click to expand...
Click to collapse
It's quite possible the process of rooting will wipe the phone anyway.
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Click to expand...
Click to collapse
power device off, hold volume up and keep it down and plug in USB cord while it's connected to PC. I tried fastboot from download mode though. the logs do look interesting, wonder what a T-MOBILE device says
Double0EK said:
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
Click to expand...
Click to collapse
Yup, I did that. And then I get an error. Well, not an error, just a lack of response. fastboot devices returns nothing. I'm currently downloading the full sdk, on the theory that perhaps it's a problem with the installation of 'minimal adb and fastboot' I have.
---------- Post added at 08:07 PM ---------- Previous post was at 07:36 PM ----------
manufan721 said:
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you do anything specific after installing Android Studio to get it to install the drivers? Cos I've installed Android Studio, but am still having the same problem-fastboot devices returns nothing, and fastboot oem unlock hangs on <waiting for device>. I went into device manager and had it search the entire C: for drivers for the android bootloader interface, and it gave the same 'already up to date drivers' message as before I installed Android Studio.
EDIT- Even after installing the Google usb driver, no luck. Giving up for the weekend.
I'm a newbie, may I know have to fastboot from download mode?
having same issue just hangs at Fastboot oem unlock if anybody can help thanks in advance
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
Click to expand...
Click to collapse
[ 0.711817] ro.oem_unlock_supported=1 1=YES
did some digging into last_kmsg while trying to boot into bootloader (AT&T device) and found a reason it may not be allowing it.
http://forum.xda-developers.com/showthread.php?t=2708466
Its a start :good:
of course we need root in order to dd anything
LG issued a new driver update for the v20. Driver version is 4.1.1+. You can get the driver from the website.