For the life of me, i can't get adb to work on my wi-fi streak 7. I've tried two different laptops and OS (windows 8 and XP). I both cases the driver installs correctly, but the commands "adb devices" and "fastboot devices" return nothing. The cable seems to be functioning ok, the tablet charges and I'm able to copy files. I installed the APX and ADB drivers, and i tried both the Google and Dell ADB drivers, still with no luck. It appears I'm forgetting something, but I can't see what it is. Any help?
marciolsf said:
For the life of me, i can't get adb to work on my wi-fi streak 7. I've tried two different laptops and OS (windows 8 and XP). I both cases the driver installs correctly, but the commands "adb devices" and "fastboot devices" return nothing. The cable seems to be functioning ok, the tablet charges and I'm able to copy files. I installed the APX and ADB drivers, and i tried both the Google and Dell ADB drivers, still with no luck. It appears I'm forgetting something, but I can't see what it is. Any help?
Click to expand...
Click to collapse
I should also add that the streak is running JB 10.1... I've reflashed this thing multiple times in the past, and never had this kind of problem, things just generally worked!
marciolsf said:
I should also add that the streak is running JB 10.1... I've reflashed this thing multiple times in the past, and never had this kind of problem, things just generally worked!
Click to expand...
Click to collapse
IIRC, ADB is broken on the latest build and won't be fixed till the new kernel being worked on gets done which could be a long time.
Does that apply to beta1 as well? I thought it was only on beta 2... how did you guys update to it then?
Sent from my Streak 7 using xda app-developers app
marciolsf said:
Does that apply to beta1 as well? I thought it was only on beta 2... how did you guys update to it then?
Sent from my Streak 7 using xda app-developers app
Click to expand...
Click to collapse
Use an older adb package.
Related
I'm aware that there are many forums about these various things but seemingly, no matter what I do, I cannot successfully restore my phone to working order. I just would like it to be stock again. This all came about in the process of trying to un-root my phone. Using TWRP i accidentally deleted my system files, and unfortunately have no back up due to the full wipe. I really am a somewhat uneducated in this realm of knowledge so I apologize ahead of time for that. I immensely appreciate any and all help possible! :fingers-crossed:
The Status of my Phone:
Sprint HTC ONE
Tampered; Unlocked, S=ON
TWRP Recovery
No OS, only have access to Bootloader, Fastboot, and TWRP Recovery
The Status of my PC:
Most recent Sdk file download
Most recent HTC Sync Manager (I think this means i have up to date drivers too?)
Fastboot files are installed.
The Stock rom i'm trying to push/flash/install is here: http://forum.xda-developers.com/showthread.php?t=2250904
These are My Problems:
Phone cannot be recognized while in fastboot. This cause me to be unable to re-lock the phone.
The command fastboot devices yields no results where as the command ADB devices does detect my phone.
My phone can be detected in recovery, not fastboot.
I have pushed the rom to my phone however upon install attempts from the recovery I simply "Error flashing zip" without any error number or anything.
If other information is needed please ask and I will try to provide it. I'm not sure where to go from here and would really not like having a brick since i have no way to replace the phone until my contract ends .Thanks again everyone, I really do appreciate any help, advice, or information
Try uninstalling HTC Sync, but leave the drivers. Hopefully this will allow fastboot to see your phone. Then run the ruu.
Sent from my HTCONE using Tapatalk 2
coal686 said:
Try uninstalling HTC Sync, but leave the drivers. Hopefully this will allow fastboot to see your phone. Then run the ruu.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Okay, just did that, and it hasn't seemed to change the issue. Should I try uninstalling all the htc files on the pc and then just find a file of just drivers? Thanks for your help coal.
You're welcome. That might work, but I'm unsure why it didn't work. Are you on Windows 8? There are some special steps you have to do I think. Also, the drivers don't work on the Windows 8.1 preview.
Sent from my HTCONE using Tapatalk 2
danchris329 said:
Okay, just did that, and it hasn't seemed to change the issue. Should I try uninstalling all the htc files on the pc and then just find a file of just drivers? Thanks for your help coal.
Click to expand...
Click to collapse
Go to your Device Manager in Control Panel. What does it say under Android Device?
Also, have you tried different ports?
And does it say Fastboot USB?
make sure you dont have windows 8.1
cuz nothing in hboot gets recognized with 8.1
flex360 said:
make sure you dont have windows 8.1
cuz nothing in hboot gets recognized with 8.1
Click to expand...
Click to collapse
That's what I said.
Sent from my HTCONE using Tapatalk 2
coal686 said:
That's what I said.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
i didnt even look before i posted lol
Coal:
I am using windows 8, but it is the latest official release, not 8.1.
Karn:
It does say Fastboot USB in all red text, and i have tried different usb ports. however they are all usb 3 so i don't know if that matters.
In terms of the connecting of my phone is unrecognized and windows say it has malfunctioned. In the control panel under devices my phone is displayed as follows in the picture.
The are special instructions somewhere on XDA for Windows 8. The exclamation tells me that may be the issue. I use Windows 7, so I'm not sure what they are.
Also, I do think people have sometimes had issues with using usb 3 ports, but my old computer doesn't have those, so I can't say personally.
Sent from my HTCONE using Tapatalk 2
coal686 said:
The are special instructions somewhere on XDA for Windows 8. The exclamation tells me that may be the issue. I use Windows 7, so I'm not sure what they are.
Also, I do think people have sometimes had issues with using usb 3 ports, but my old computer doesn't have those, so I can't say personally.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
That's a good point, i'm gonna go and try everything on a windows 7 pc with usb 2 ports and see if i have any luck. Thanks a lot coal, i'll post how that goes sometime soon with an update.
I've seen the other posts people have made and guides around here, but none of them work for me. I've had no problems installing the drivers on any of my other computers, just my new desktop. I'm running the same version of windows 8 on my old laptop and it works. Same drivers, same OS install disk.
I'm posting here as a last resort, I've tried probably 99% of every guide on the forum, and google.
I can't for the life of me get fastboot to work. ADB works fine, fastboot just will not work.
I have usb 3.0, and usb 2.0, I've been trying both and neither of them will work. I've tried using multiple different usb ports, I have 4 usb 3.0, and 3 different usb 2.0.
I've disabled signature verification to install the drivers, but it acts like it uninstalls it and installs it's own drivers again.
Then it says the last usb devices malfunctioned, and windows does not recognize it.
I'm uninstalled reinstalled, uninstalled, reinstalled. I've tried some "all in one" driver packs that people put together, but fastboot refuses to work.
I'm running windows 8 64bit.
Any ideas?
xxquicksh0txx said:
I've seen the other posts people have made and guides around here, but none of them work for me. I've had no problems installing the drivers on any of my other computers, just my new desktop. I'm running the same version of windows 8 on my old laptop and it works. Same drivers, same OS install disk.
I'm posting here as a last resort, I've tried probably 99% of every guide on the forum, and google.
I can't for the life of me get fastboot to work. ADB works fine, fastboot just will not work.
I have usb 3.0, and usb 2.0, I've been trying both and neither of them will work. I've tried using multiple different usb ports, I have 4 usb 3.0, and 3 different usb 2.0.
I've disabled signature verification to install the drivers, but it acts like it uninstalls it and installs it's own drivers again.
Then it says the last usb devices malfunctioned, and windows does not recognize it.
I'm uninstalled reinstalled, uninstalled, reinstalled. I've tried some "all in one" driver packs that people put together, but fastboot refuses to work.
I'm running windows 8 64bit.
Any ideas?
Click to expand...
Click to collapse
Did you disable "Fast Boot" option in Settings -> Battery? (nothing to do with the fastboot command, it's a setting in the power options)
And when you're in the Fastboot mode of the bootloader, does it say "FASTBOOT USB"?
nkk71 said:
Did you disable "Fast Boot" option in Settings -> Battery? (nothing to do with the fastboot command, it's a setting in the power options)
And when you're in the Fastboot mode of the bootloader, does it say "FASTBOOT USB"?
Click to expand...
Click to collapse
Yes, It works with my other computer so it's not my phone, or the way I'm doing it.
I get to the point where I can install the drivers, I install them and then it's like it reinstalls the old drivers.
Sent from my HTC One using XDA Premium 4 mobile app
xxquicksh0txx said:
Yes, It works with my other computer so it's not my phone, or the way I'm doing it.
I get to the point where I can install the drivers, I install them and then it's like it reinstalls the old drivers.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you check in device manager which drivers are installed, if they're the same as your other computer. I don't use Windows 8, so won't be of much help to you.
Good luck
Sent from my HTC One using xda app-developers app
nkk71 said:
Did you check in device manager which drivers are installed, if they're the same as your other computer. I don't use Windows 8, so won't be of much help to you.
Good luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yeah I've been manually uninstalling, and installing the drivers I want. It acts like the usb is crashing and going back to square one.
Sent from my HTC One using XDA Premium 4 mobile app
xxquicksh0txx said:
I've seen the other posts people have made and guides around here, but none of them work for me. I've had no problems installing the drivers on any of my other computers, just my new desktop. I'm running the same version of windows 8 on my old laptop and it works. Same drivers, same OS install disk.
I'm posting here as a last resort, I've tried probably 99% of every guide on the forum, and google.
I can't for the life of me get fastboot to work. ADB works fine, fastboot just will not work.
I have usb 3.0, and usb 2.0, I've been trying both and neither of them will work. I've tried using multiple different usb ports, I have 4 usb 3.0, and 3 different usb 2.0.
I've disabled signature verification to install the drivers, but it acts like it uninstalls it and installs it's own drivers again.
Then it says the last usb devices malfunctioned, and windows does not recognize it.
I'm uninstalled reinstalled, uninstalled, reinstalled. I've tried some "all in one" driver packs that people put together, but fastboot refuses to work.
I'm running windows 8 64bit.
Any ideas?
Click to expand...
Click to collapse
hi mate i had this same issue tried all sorts, various guides etc which non of them worked. in the end i did find a guide that got it working. my problem was that intel usb 3.0 aren't compatible whatseover you need to uninstall them and install some new modified drivers. this is a known problem with windows 8 64 and intel 3.0. it also does stop fastboot from working with your usb 2.0 ports. have a look for the guide, i will also try to dig it up and ill post back if i find it.
edit: go to this thread http://forum.xda-developers.com/showthread.php?t=2256359 you will see that im post #2. this was the only thing that fixed my problem. follow it to the letter and im sure it will work.
dazbutler1 said:
hi mate i had this same issue tried all sorts, various guides etc which non of them worked. in the end i did find a guide that got it working. my problem was that intel usb 3.0 aren't compatible whatseover you need to uninstall them and install some new modified drivers. this is a known problem with windows 8 64 and intel 3.0. it also does stop fastboot from working with your usb 2.0 ports. have a look for the guide, i will also try to dig it up and ill post back if i find it.
edit: go to this thread http://forum.xda-developers.com/showthread.php?t=2256359 you will see that im post #2. this was the only thing that fixed my problem. follow it to the letter and im sure it will work.
Click to expand...
Click to collapse
I guess I'll try that again when I get home. It didn't seem to work last time. (I had to reinstall my OS because something else was weird.)
Thanks
Sent from my HTC One using XDA Premium 4 mobile app
Hi,
I recently upgraded to Windows 8.1.
It does not recognize the fastboot mode in my Nexus One.
When the phone is connected in fastboot mode (bootloader), Windows gives the prompt 'The last USB device you connected to your computer malfunctioned and Windows does not recognize it.'
Is there a problem with my phone?
What can be done to rectify this?
What fastboot drivers would be required to be installed?
Thanks in advance.
viditbhargava said:
Hi,
I recently upgraded to Windows 8.1.
It does not recognize the fastboot mode in my Nexus One.
When the phone is connected in fastboot mode (bootloader), Windows gives the prompt 'The last USB device you connected to your computer malfunctioned and Windows does not recognize it.'
Is there a problem with my phone?
What can be done to rectify this?
What fastboot drivers would be required to be installed?
Thanks in advance.
Click to expand...
Click to collapse
Same to me. I have Windows 8.1 and when i connect my N1 in fastboot mode and it give me the same error. I don't think that your (our) phone is the problem.
Mirko Lona said:
Same to me. I have Windows 8.1 and when i connect my N1 in fastboot mode and it give me the same error. I don't think that your (our) phone is the problem.
Click to expand...
Click to collapse
Thanks, such a relief knowing that it is most probably nothing wrong with my phone. :cyclops:
No replies on this?
Please help guys.
There's anyone there?
I triend on Windows 7 and same message appears
I also have this issue. I keep trying to update/re-install the driver but it always reverts back to ADB Interface > HTC Bootloader (when looking at device manager). I have re-installed the Official Google Nexus Drivers, my Nexus 9, 10 and Galaxy Nexus all work fine.
And to be clear, it's only fastboot that is the issue. ADB works:
Code:
adb devices
yields the devices ID and
Code:
adb reboot bootloader
reboots into HBoot.
Also, to be clear, I just upgraded to Windows 10 and all of the devices listed above work still!
So any thoughts would be greatly appreciated. Otherwise I might try replacing the logicboard in this bad boy.
nisiwi
toonhead85 said:
I also have this issue. I keep trying to update/re-install the driver but it always reverts back to ADB Interface > HTC Bootloader (when looking at device manager). I have re-installed the Official Google Nexus Drivers, my Nexus 9, 10 and Galaxy Nexus all work fine.
And to be clear, it's only fastboot that is the issue. ADB works:
Code:
adb devices
yields the devices ID and
Code:
adb reboot bootloader
reboots into HBoot.
Also, to be clear, I just upgraded to Windows 10 and all of the devices listed above work still!
So any thoughts would be greatly appreciated. Otherwise I might try replacing the logicboard in this bad boy.
Click to expand...
Click to collapse
I'm experiencing the same problem on Windows 10 with a Google Nexus One Did you ever resolve it toonhead85 ?
I'm thinking about buying an old windows 7 laptop on ebay just to be able to keep working on the phone. I just can't let go.
anyone found the solution about this error message? I'm trying to give life to my old N1 and I can't see to find a fix for this error, and I really dont want to downgrade my notebook system just for that...
nisiwi said:
Did you ever resolve it toonhead85 ?
Click to expand...
Click to collapse
YES!!!
So, using VirtualBox I installed Windows 7 and this. No problems at all. I guess this means that there is some incompatibility with Windows 10 and Nexus One. I was able to remove BlackRose and install STOCK 2.3.6, which is what I wanted to do in the first place.
Best of Luck!
toonhead85 said:
YES!!!
So, using VirtualBox I installed Windows 7 and this. No problems at all. I guess this means that there is some incompatibility with Windows 10 and Nexus One. I was able to remove BlackRose and install STOCK 2.3.6, which is what I wanted to do in the first place.
Best of Luck!
Click to expand...
Click to collapse
Sorry to pull this thread up from the grave, but how did you get the virtual Windows 7 to see the device at all? I've only been able to get it to pick up devices with working drivers in my main Windows install.
HTC sync doesn't help.
I am so frustrated. I cannot run fastboot commands to get my token because no devices are found.
Any suggestions for this?
typhoonikan said:
HTC sync doesn't help.
I am so frustrated. I cannot run fastboot commands to get my token because no devices are found.
Any suggestions for this?
Click to expand...
Click to collapse
Have you made sure that you have the latest Fastboot available? I always check using the Android SDK Manager before attempting anything with a new device.
Unplug the device and reboot it. Then, try again.
If that doesn't work, try a different USB port (preferably one that is on the motherboard itself).
Also, you can try removing HTC Sync. You can always reinstall it after.
skizzled said:
Also, you can try removing HTC Sync. You can always reinstall it after.
Click to expand...
Click to collapse
This, HTC sync is good for syncing but tends to interfere with adb commands and stuff like that, most instructions tell you to remove it because of this.
Sent from M8 on XDA Premium APP
Thanks.
I had to reboot my pc everytime the phone went into a different mode almost. System to bootloader to system. Windows 7! Finally got it rooted. It was so simple with the toolkit bit such a hassle since my pc didn't like the phone apparently.
Now to lurk in the threads here for mods and roms.
Sent from my EVO using XDA Premium 4 mobile app
typhoonikan said:
Thanks.
I had to reboot my pc everytime the phone went into a different mode almost. System to bootloader to system. Windows 7! Finally got it rooted. It was so simple with the toolkit bit such a hassle since my pc didn't like the phone apparently.
Now to lurk in the threads here for mods and roms.
Click to expand...
Click to collapse
I've had similar issues with ADB and Fastboot not recognizing my phones after plugging them in. Usually a reboot of the phone and killing/restarting the service fixes the issue.
Glad you have it working now though. :good:
I have spent Friday and Saturday trying to get drivers installed on my Nexus 6. I have removed, uninstalled, added Google drivers, added sdk adb, computer needs to be returned Monday and this new Toshiba Satellite with one usb port with not recognize my phone. Even though the computer beeps every time I plug it in or out.
Any steps or detailed procedures would be greatly appreciated. Thank you!
Sent from my SGH-I337 using Tapatalk
Try using the Wug Fresh Root Toolkit in the Development section for the Nexus 6. Just make sure you follow the instructions. There are several different ways to find the correct drivers with his Toolkit. Good luck!
dave2metz said:
Try using the Wug Fresh Root Toolkit in the Development section for the Nexus 6. Just make sure you follow the instructions. There are several different ways to find the correct drivers with his Toolkit. Good luck!
Click to expand...
Click to collapse
Thanks man, but that's how I unlocked and rooted my phone. It's also how I screwed my phone up, trying to undo the forced encryption. Did it all with Wug's Nexus Tool Kit. I have been at this 25 hours with no success. Drivers are needed. I don't know why the computer doesn't recognize the phone, the computer beeps every time I plug it in or unplug it.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
I have spent Friday and Saturday trying to get drivers installed on my Nexus 6. I have removed, uninstalled, added Google drivers, added sdk adb, computer needs to be returned Monday and this new Toshiba Satellite with one usb port with not recognize my phone. Even though the computer beeps every time I plug it in or out.
Any steps or detailed procedures would be greatly appreciated. Thank you!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I always have issues with Nexus devices being recognized. I always have to plug the device in, go to the device manager, and delete anything that has to do with the device, including any labeled as ADB devices. I've also found it helps to go to "View" and hit "Show Hidden Devices". After deleting them all, I unplug and replug the device and install the Universal Naked Driver from this thread.
addcancercat said:
I have spent Friday and Saturday trying to get drivers installed on my Nexus 6. I have removed, uninstalled, added Google drivers, added sdk adb, computer needs to be returned Monday and this new Toshiba Satellite with one usb port with not recognize my phone. Even though the computer beeps every time I plug it in or out.
Any steps or detailed procedures would be greatly appreciated. Thank you!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I assume with it being a Toshiba Satellite its running windows, what version? The older OS's seemed to be less finicky then W8, Have you deleted and re-installed the google drivers from http://developer.android.com/sdk/win-usb.html or from another site? Have you tried any different PC's? Have you checked the windows hardware event logs for any error messages? Have you been able to put in say a thumb drive into the usb port and it work? Are you on as admin and all that security crap? Do you have usb debugging on in the developer area on the phone? Are you able to get it into fastboot mode? If you do fastboot devices does it show anything at all? I assume you have rebooted the PC, but I'm still surprised how many issues that fix's.
Just some suggestions, I know how frustrating it can be. Good luck.
Thanks. I did that and I downloaded an Intel driver so now the computer recognizes the phone in Device Manager.
Sent from my SGH-I337 using Tapatalk
jackpollard said:
I assume with it being a Toshiba Satellite its running windows, what version? The older OS's seemed to be less finicky then W8, Have you deleted and re-installed the google drivers from http://developer.android.com/sdk/win-usb.html or from another site? Have you tried any different PC's? Have you checked the windows hardware event logs for any error messages? Have you been able to put in say a thumb drive into the usb port and it work? Are you on as admin and all that security crap? Do you have usb debugging on in the developer area on the phone? Are you able to get it into fastboot mode? If you do fastboot devices does it show anything at all? I assume you have rebooted the PC, but I'm still surprised how many issues that fix's.
Just some suggestions, I know how frustrating it can be. Good luck.
Click to expand...
Click to collapse
No, I have a Nexus 6 that the computer won't recognize. ADB and SDK also don't recognize the phone.
I am using my old Samsung S4 for emergency support. It's not hooked up with AT&T since I got the Nexus 6. I have to return this computer tomorrow. I am starting to wonder if it's computer problems with phone problems.
Sent from my SGH-I337 using Tapatalk
When you type ADB command in the DOS Box, there should be a popup on the mobile whether you wanna allow access from this computer.
Did you select yes and remember that PC?
I had this problem when I did my nexus 6, something on the laptop I was using was conflicting, I moved to another laptop and it worked like a charm never went back to figure out what was conflicting. Do you have access to another machine?