hey, im trying to flash a custom splash screen to my g1, when i try to use fastboot i get <waiting for device> in the command prompt window, i have tried this on 2 different computers.
both running windows 7 64bit
im using the engineering bootloader,
help?
just tried on windows xp 32bit system as well
finally solved. ran the whole thing out of the sdk/tools folder and worked amazing!
Related
Heya~ Ive recently upgraded to CM5, since then manually & Automatically updating the drivers to use fastboot have failed on Vista Home Premium (32bit)
I've also tested it on Win7 64BIT, in win7 it does appear on device manager as "HTC Bootloader", under ADB Interfaces. But does not appear when I do "fastboot devices" therefor it endlessly stays at <Waiting for Device> when trying to flash a file, It wasnt like this on Vista before upgrading from hardSPL to dangerSPL. Under windows vista it continuasly picks the device up as "Android 1.0" and cannot find drivers on the internet, and the drivers from the SDK arent working.
Is there a command to flash the splash1/2 via terminal or recovery prompt...because My computers dont want to cooperate.
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
I've searched and searched for a solution to this, nothing is working. Really need help guys.
Phone is on stock ICS rom, PC is Win8 Pro x64. All three files are in the folder, SDK is installed (x64 version), Google USB driver installed, Java for windows installed, and HTC Sync installed but not running.
When in FASTBOOT and USB connected it shows FASTBOOT USB. Device manager shows Android Phone - Android ADB Interface. Is this correct or should it show something else in device manager?
No matter what I've tried when running fastboot oem get_identifier_token in command prompt I get waiting for device. Also running fastboot devices returns nothing.
Don't know what else to try... Seems it doesn't recognize the device but it's in device manager.
Edit: have also tried different usb ports and I know the cable works.
Edite 2: I fixed it. Took me hours to get this working but for any one struggling like I was here is what I did.
Got rid of all the drivers and started back at Android 1.0 in device manager. Manually installed the official SDK google usb driver and selected Android Bootloader Interface for Android 1.0. Also boot the phone and manually install again and select Android ADB Interface.
Here is what really caused me problems. The HTC tutorial I looked at said to take adb.exe, fastboot.exe, and adbWinApi.dll and put them in their own folder. This absolutely does not work for me even now. I used the directory straight from the SDK (sdk\platform-tools) and added fastboot.exe from a previous sdk revision into that folder. Now everything works!!! Finally!
Hi everyone!! I have the same issue as brother bassvoykevlar but the solution here expresed is not all clear to me. Can anyone please give me a hand on this, i am really mad with it . Thanks in advance.
The Best Solution
this problem has also happened with me and i found a solution to this,
this usually happens if your system lacks fastboot drivers.
ADB drivers can only Run ADB shell so that is why you need to have fastboot drivers as well to use fastboot commands.
i think you must have tried this code:
"fastboot oem unlock"
then cmd may have got stuck on "waiting for device"
don't worry install drivers for fastboot then it should work.
google it then get it.
there is 15seconds ADB,fasdtboot installer available try that.
then give it another try.
Hey guys,
Wonder if you can all help me,
Im not new to Rooting, but i have never come across this error before, ive searched accross XDA and Google, but cannot for the life of me find a fix, found a couple of things about deleting a registry file, and installed the One drivers which i had downloaded from here. I Do not have HTC Sync installed.
When device is powered up normally and connected to USB it as fine. When i reboot the Device into fastboot and connect it, i get a Error saying USB Device not recognised.
When i goto device manager, its shows up as My One under HTC, but has a Yellow '!' in a triangle, when i click on properties it states a code 10 Device Fails To Start error.
Please help as this is really frustrating me... Ive tried everything! And i really dont want to re-set my whole laptop as i will lose ALOT of data!
Like i said, im not new to this, as been doing this since the days of the HTC HD2...Am i missing something? Having a thick moment?
Running Windows 8.1.
If anyone really knows what this could be and could possibly fix, let me know as have team viewer and would gladly let you connect to me to help me out (Donation for your time aswell)
Thanks in Advance!
Really simple mate, windows 8.1 isnt compatible with fastboot drivers for now. Only adb is working atm. So dont be scared, your phone have no problem, its only because you updated to 8.1
Sent from my HTC One using xda app-developers app
Edit: there is a possible fix if your computer is based on intel chipset usb 3.0. Just google something like Windows 8.1 fastboot fix. Otherwise I think you will need to wait or simply use another computer with win7 or 8.0 or maybe dual boot win7 or even boot win7 with a vm?
Edit 2: search the forum, there is a "how to" force win7 fastboot drivers installation on win8.
Perfect buddy worked a Treat! Thankyou so much! I was getting so frustrated haha!
Didnt know it was a problem with Windows, so just needed to change the search terms, do'h!
For all those that has the problem in the future, a link for the fix!
Clicky!
Mods, this can now be closed, fixed!
fastboot for windows 8.1 over linux and this is my option to work fastboot on win 8.1
load wubi (windows ubuntu installer) over the link http://wiki.ubuntuusers.de/Wubi
than install ubuntu, on harddrive C:// and reboot your Pc
Now you have a linux in your current system, you can remove ubuntu (linux) in Programms & feautures list in windows.
now reboot reboot the system and isntall in ubuntu fastboot.
you musst give in the terminal sudo apt-get fastboot
and now you can flash your bootloader in linux.
but you musst sudo bevor you type fastboot flash type sudo fastboot flash boot boot.img
adb is working to on linux
i love wubi <3
you say it is easy
gooogle wubi (windows ubuntu installer)
tried running ubuntu in a virtual machine still no go guess the vm needs the windows driver to see the damn usb ports ffs
anyone know if for sure it will work if i actually install ubuntu to a partition?
Sony vaio 13 i7-4500u so only got usb3 ports and small hard drive didnt wanna dual boot really
My vivid mobile when it is connected in fastboot mode , drivers are not recognised. I need to root my mobile
Is it recognized when not in fastboot? What os are you using, and so you run into the save issue on a different PC?
Sent from my Vivid 4G using XDA Free mobile app
projectisaac said:
Is it recognized when not in fastboot? What os are you using, and so you run into the save issue on a different PC?
Sent from my Vivid 4G using XDA Free mobile app
Click to expand...
Click to collapse
It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it
It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it
saiviru said:
It is recognized when the phone is ON. I'm using windows 8.1 64bit OS.
when it is connected in fast boot mode my OS does not detect drivers for it
Click to expand...
Click to collapse
Hmmm.... I'll have to test this with my girlfriends comp first, as I'm using win7x64 myself.
Sent from my Vivid 4G using XDA Free mobile app
test as fast as you can .I want to root my mobile
fastboot doesn't work on windows 8.1
using a virtual machine also doesn't work as the vm reads the host system's usb
you'll have to find a different machine to use fastboot
or you could try using a linux live cd (but i haven't done this myself, so i don't know if it works)
stuffed_tiger said:
fastboot doesn't work on windows 8.1
using a virtual machine also doesn't work as the vm reads the host system's usb
you'll have to find a different machine to use fastboot
or you could try using a linux live cd (but i haven't done this myself, so i don't know if it works)
Click to expand...
Click to collapse
I just saw this post today.
adb, fastboot works on my windows 8.1 64 bit machine though.
Win 8.1 has command prompt program. You have to run that command prompt "run as administrator".
sway8966 said:
I just saw this post today.
adb, fastboot works on my windows 8.1 64 bit machine though.
Win 8.1 has command prompt program. You have to run that command prompt "run as administrator".
Click to expand...
Click to collapse
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me
saiviru said:
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me
Click to expand...
Click to collapse
In the development settings... Make sure that you've granted root to adb and try again...
Sent from my Vivid 4G using Tapatalk
any solution yet?
saiviru said:
Everything works fine but when I give fastboot command in cmd it says waiting for device and it never detects my device.
and in the windows notification area it shows USB device not recognised.
please help me
Click to expand...
Click to collapse
same problem here... wondering if you could solve your problem...
I guess I wasn't clear enough.
Windows 8.1 doesn't load the driver for the Vivid while it is in fastboot mode because of a change in the way Windows handles USB devices. ADB and fastboot may work on Windows 8.1, but you'll never be able to "fastboot flash" anything because the device isn't recognized while the phone is in fastboot mode. It is not a phone driver problem, it is a USB controller driver problem.
Also, like I said before, you can't use a virtual machine becuase the the vm reads from the host system's usb.
You will have to use an operating system other than Windows 8.1 to do any fastboot flashing.
Trust me, I've dealt with this problem since 8.1 was released.