Yes, I have searched... ALL OVER!
I have the new 1.6 sdk installed. I'm running the Cyanogen 4.1.999 ROM Donut/1.6. I have adb working. But, I can NOT get fastboot to recognize my device.
I have tried the following:
I have uninstalled the mass storage device - problem here is that Windows automatically installs the drivers again and I CAN'T stop it!
I have gone into the device manager/mass storage device and instructed it to update the drivers using the new 1.6 sdk. The message I received was that I was using the most up to date drivers.
I have found additional tips to solve this problem if I was running Linux. But, I can't find anything I haven't tried for Windows 64-bit....
You even title your question Q and don't post in the Q&A section?
Sorry, I didn't realize I was still in the Android Dev section when I started the thread. I was in a hurry.
If a Moderator will please move this to the Q&A section!
you are running fastboot from the SPL arent you...if not you need to boot up with (Cam+Power)
you need the engineering spl, hardspl, or haykuro spl for fastboot. you also need to make sure fastboot is active on the phone (make sure it says fastboot on it in the bootloader. if not, press the back button)
Yes, sir done all of the above. ADB works great. Boot into spl - shows Fastboot USB. I just get "waiting for device" in the command window. This should be a windows setting, driver install process, or something that either I am missing, doing wrong, or that I don't have installed. But, I have attempted everything I can find on the net. I worked at it for about three hours the other night. The wife was pissed b/c I was on the computer for so long.
Well is fastboot devices showing up under device manager?
it is most likely a driver error. note that if you have haykuro's spl, he has different drivers for it. you will need to get them from his google code page
ok I'm trying to get the PSGroove so what is fastboot? An app? Please explain
shaneaus said:
Yes, I have searched... ALL OVER!
I have the new 1.6 sdk installed. I'm running the Cyanogen 4.1.999 ROM Donut/1.6. I have adb working. But, I can NOT get fastboot to recognize my device.
I have tried the following:
I have uninstalled the mass storage device - problem here is that Windows automatically installs the drivers again and I CAN'T stop it!
I have gone into the device manager/mass storage device and instructed it to update the drivers using the new 1.6 sdk. The message I received was that I was using the most up to date drivers.
I have found additional tips to solve this problem if I was running Linux. But, I can't find anything I haven't tried for Windows 64-bit....
Click to expand...
Click to collapse
If you cannot get the sdk usb drivers to work for you when your entering into fastboot, try installing htc sync. It has additional drivers that may work. I have attached a driver pack that i use.
Related
USB/MicroSD mount is working, but I cannot get ADB to work. This is really pissing me off. I had it working fine on Vista but I'm a dumbass and decided to upgrade to Win7 Ultimate.
Device Manager does not show "Android Composite ADB Interface" or "Nexus One" or anything that looks remotely like that.
The instructions here: http://forum.xda-developers.com/showthread.php?t=613054 -- do not work for me, as you can see in the screenshot I've provided below, nothing shows up.
SCREENSHOT (same also attached in case something happens to the link): http://imgur.com/uoaWH.jpg
1. The Android SDK is installed.
2. Java JDK 64 & 32 bit versions are both installed.
3. Plugged in my phone, turned on USB Debugging, nothing happened. Device manager list didn't change at all. No alerts near the systray from Win7.
4. I used "USB Deview" and uninstalled everything that looked like "Google" or "HTC" (saw nothing that said HTC or Android, just Google).
5. After #4, gave this POS a reboot, no change when plugging the phone in.
I have the driver downloaded, separately, as well as the one that comes with the Android SDK.
I'm at a complete loss.
Help is deeply, truly, appreciated, and I'll be clicking on some "DONATE" links if you can help me fix this.
EDIT: RESOLVED
Windows7 didn't like this ROM: http://forum.xda-developers.com/showthread.php?t=702191
But it loves this one: http://forum.xda-developers.com/showthread.php?t=714184
Needless to say... I'm pretty happy!
usb driver installed?
rori~ said:
usb driver installed?
Click to expand...
Click to collapse
Yes.
And USB debugging is enabled.
I can mount the SD, but it looks like Windows thinks my phone is nothing more than a storage device. The ADB crap is not showing up in the Device Manager like it did on Vista, nor is there *anything* that says "Nexus One" except in... see new screenshot.
http://imgur.com/J7OzA.jpg
Is your Nexus running 2.2?
I had this exact problem as soon as I updated to 2.2; Windows 7 simply refuses to accept the device.
Put your device in recovery mode and see if fastboot can detect it. For me it can, but ADB and DDMS both think nothing is connected when the phone is on and in debug mode.
I have a HTC Magic as well which works absolutely fine (even when running CM6, which is 2.2 based) but the Nexus on 2.2 is just a no go. If you've unlocked your bootloader you could downgrade to 2.1 again. I never had problems on Win7 with 2.1.
Your only other option is to add your comments to the bug, here: code.google.com/p/android/issues/detail?id=9437 (sorry, I'm still not allowed to post proper links yet)
It seems very few people are experiencing this (or reporting it when they do) so my hopes for them fixing it are pretty low.
Are you on version R3 of the USB driver?
What happens when you plug in the phone with usb debugging turned on (on the status bar) ?
Does it ask for a driver? if so manually point it to C:\android-sdk-windows\usb_driver (may differ)
below is a SS of the driver files being uses on my win-7 64 bit desktop.
Try something for me. I am having the same as you but try this. Boot your phone in recovery mode and see if adb works then. My pc sees the phone as adb in recovery but it doesn't see it as adb on the home screen. Not sure why this is but it worked at one time.
Prod1702 said:
Try something for me. I am having the same as you but try this. Boot your phone in recovery mode and see if adb works then. My pc sees the phone as adb in recovery but it doesn't see it as adb on the home screen. Not sure why this is but it worked at one time.
Click to expand...
Click to collapse
Holy ****.
I love you.
I've been pulling my hair out. Seriously.
I booted into recovery, plugged the phone in, Windows tried installing drivers, but failed, then I saw "Nexus One" listed in Device Manager, and after installing the drivers that came with the SDK, the "Android Phone" and "Android Composite ADB Interface" stuff shows up in the device manager, and adb commands work... when my phone is booted into Recovery.
Recovery was the key.
Thank you!!!!!!
Could the ROM I'm using have anything to do with this?
ADB recognizes the device when I'm recovery, and the "adb push" commands do their thing, but I don't see the files being pushed where I'm pushing them to.
Do I just have to enable the "USB toggle" thing?
I just installed Win 7 and used these directions from the android developers website and everything worked flawlessly from the getgo:
http:// developer.android.com/sdk/index.html/
Hmmm, correct url, not working, 404, maybe it'll work if you copy/paste and take the spaces out from between // and developer.
What recovery image are you using? I've had good luck with ClockworkMod and it's 'mount system' option as far as push/pull while in recovery.
IT WAS THE ROM.
I went back to the ROM I was using previously, and ADB WORKS FINE NOW IN WINDOWS 7.
I was using this ROM: http://forum.xda-developers.com/showthread.php?t=702191
adb remount
adb devices
Nothing worked!
Completely wiped and, went back to this: http://forum.xda-developers.com/showthread.php?t=714184
It works now!!!
Something had to be wrong....that's stable rom. There's more than one custom rom that has it for a base.
pendo said:
Something had to be wrong....that's stable rom. There's more than one custom rom that has it for a base.
Click to expand...
Click to collapse
I'm not knocking the ROM or the developer of the ROM, but I made a backup, wiped everything, flashed the MCR ROM again, went back to the same problem.
Putting the other ROM back... no more problem. ADB commands work fine, and Windows7 sees my phone.
Ryjabo said:
I'm not knocking the ROM or the developer of the ROM, but I made a backup, wiped everything, flashed the MCR ROM again, went back to the same problem.
Putting the other ROM back... no more problem. ADB commands work fine, and Windows7 sees my phone.
Click to expand...
Click to collapse
And I don't doubt what you're saying...I was just thinking it was strange.....but hey strange things do happen so who knows, lol.
I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.
I am sorry for making a new thread for this reason, but I have tried for about 6 hours of reading forums and trying different drivers, countless reboots, etc and cannot figure out adb or fastboot for the life of me, so please help
I am running Windows 7 64bit, have download and unzipped the android-sdk_r10-windows.zip and have updated the platform-tools and usb drivers revision 4. I plugged my phone in and it immediately found the drivers without me touching anything, and I tried "adb devices" from an elevated cmd prompt and got nothing in return, so I went into device manager and updated the driver software to Google's usb drivers from the SDK and tried once again, but no luck. I then downloaded USBDeview and uninstalled all references to HTC or Android device (while the G1 was unplugged). Plugged G1 back in after un-installation of drivers and it recognized it right away, again no need for drivers. tried "adb devices" and nothing (yes, the phone is fully booted into CM6.1 stable from Cyanogen with a 1.33.2005 HSPL and compatible radio, along with Amon_RA 1.7.0 recovery).
I read in a thread that Hayakuro's SPL has its own usb drivers on http://code.google.com/p/sapphire-port-dream/ and I downloaded them and went to device manager and updated the drivers to this version...still no adb luck (always running from cmd "run as administrator"). Then I looked into USBDeview to see the properties of the installed drivers...they never changed from Default micrososft windows drivers, where the HTC drivers for the G1 should have had obvious different properties than the default MS drivers.
So I am just plain stuck and have no idea what to do...I've reflashed the HSPL and CM6.1 using AmonRa recovery, still don't know.
I am trying to eventually use fastboot in order to put ezterry's 2708+ kernel and ezterry's gingerbread port on here, but I cannot setup adb or fastboot. As of last night @ 2:30am (CST) I had adb working, but not fastboot (while in Recovery mode) and now while in a full boot, adb and fastboot refuse to work.
I have read through http://forum.xda-developers.com/showthread.php?t=532719 and followed all directions (except for using the newest android sdk .zip package
I'm also wondering about using HTC's specific "fastboot.exe" on their developers page or the "fastboot.exe" included in the SDK?
Hopefully I have explained everything that you would need to help me solve this unrelenting PITA (Pain in the A$$)
This is why XP beats the **** out of Vista & Windows 7.
Have you followed this?
http://developer.android.com/sdk/win-usb.html#Win7
And if yes then I have to ask what is your current spl and radio? Had trouble helping someone last night get it sorted on Windows 7 also, the perfect example of how stupid Microsoft think their users are that they now better than the users on how they want their machines setup.
What a cup of coffee can do for the brain ;-)
shadowch31 said:
This is why XP beats the **** out of Vista & Windows 7......
Click to expand...
Click to collapse
I can see how XP is better for a development platform since it doesn't have all the bells and whistles I....never use haha
And I just got it to work!!!! I used Ohsaka's superwipe (found here: http://forum.xda-developers.com/showthread.php?t=834812) re-flashed the radio 2.22.19.26I.zip, then the spl-signed.zip (hboot 1.33.2005) from http://code.google.com/p/sapphire-port-dream/ and then Cyanogen's CM6.1 for Dream and performed a full boot and plugged in the G1 and it recognized it immediately and installed drivers for it ran an elevated command prompt and "adb devices" (while in full boot) and "fastboot devices" (while in fastboot) works! I think the reason was I had never completely wiped my phone with the aforementioned SuperWipe v2 and/or maybe the updated radio 2.22.23.02 was messing up some low-level functionality of the spl
Mods feel free to edit/delete this, but I feel this would be a good addition into the adb/fastboot guide/sticky on the front page, because this specific situation called for a complete wipe of the phone and flashing an older radio in order for fastboot to work
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.
anyone?
i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.
TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???
Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.
ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.
HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible
blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem
Okay, I'm not sure exactly what happened, but long story short:
I flashed a rom and instead of getting a new rom on my phone, the phone rebooted into fastboot. I tried to enter recovery... no dice. Somhow my recovery uninstalled itself. So now I'm stuck with a phone with no rom installed, and no recovery installed. Frustration.
First step would be to reinstall recovery right? But when attempting to use fastboot flash command, i get stuck at <waiting for device>. I have the htc phone driver installed, and it's recognizing the phone is plugged into the pc in device manager. The phone screen even says FASTBOOT USB. I have no idea why it's not flashing. The recovery i'm trying to flash is twrp, the latest sprint build. It's the same one I had before it somehow uninstalled itself.
Please help out guys?
Thanks.
What phone?
Sent from my SM-P600 using Tapatalk
Details
Sorry for not making this clear earlier: the phone is the HTC One, Sprint. Just the regular one.
I'm really in a bind in here. Right now I have no recovery or rom to work with, and the only rom on my phone is the one that caused all this mess. I'm going to have to sideload a rom, but right now I need to get twrp on there. For some reason, it still won't get on, i'm still stuck at <waiting for device>. The phone is coming up on device manager as "My htc", so it's definitely plugged into the computer correctly. I have no idea what's going on.
Smells like bad usb drivers.
What does this command say:
fastboot devices
The result should be your device id. It not, your usb drivers are not working.
If it does work, I would RUU back to stock. Look at the faq page for links.
tdhite said:
Smells like bad usb drivers.
What does this command say:
fastboot devices
The result should be your device id. It not, your usb drivers are not working.
If it does work, I would RUU back to stock. Look at the faq page for links.
Click to expand...
Click to collapse
The command doesn't return anything. I guess this means my drivers aren't working. This doesn't make any sense though (pun intended): the phone is being recognized in device manager under "Android USB Devices" as "My HTC" via HTC's drivers that come with htc sync. I already downloaded htc sync and uninstalled it, keeping the driver files. This is really wierd stuff, any idea on how to get the drivers working? I'm sure if I could just get a recovery on there, resolving the issue wouldn't be too difficult via adb. Thanks.
Sounds like you are running Win 8.1.
Your phone won't be recognized if your hboot is 1.44
BD619 said:
Sounds like you are running Win 8.1.
Your phone won't be recognized if your hboot is 1.44
Click to expand...
Click to collapse
I am running 8.1, but my hboot is 1.55.
There it's a specific question in this in the faq page, particularly 8.1 and usb. Did you look at that?
See this: http://forum.xda-developers.com/showthread.php?p=49038239
EXDetonator said:
I am running 8.1, but my hboot is 1.55.
Click to expand...
Click to collapse
Did you install HTC sync? You need it for the proper drivers
Fixed! ...halfway
Alright guys, I flashed a recovery.
I actually started off with HTC's drivers, but they were causing the issue.
Thankfully the information the thread tdhite posted had a link to a working driver.
Thanks everyone! Now I need to sideload a rom.