ok. I'm tired so go easy on me. I'm running Windows 7 32bit. I have Dell PC Suite installed. I've got the full SDK installed. I've also got the R288920 drivers installed. I've been trying (since 3.00am) to get Fastboot to work and it would seem no matter what i do i just cannot. My Streak (Steve's 1.90) shows up in Device Manager as "Android ADB Interface". I've tried all 6 usb ports on my pc. I've tried Adb Composite. Adb Bootloader. Adb Interface and nothing works. I should also mention i had to do a clean install of Windows yesterday and prior to that Fastboot worked fine. I'm a semi-noob and i'm convinced that this is a driver problem. My question is this, can someone please tell me where i've gone wrong? As the man with the steering wheel down his pants said to the Doctor "this is driving me nuts".
Problem solved. Fastboot file was corrupted.
Related
So I just got an Atrix and im trying to root it, however when I plug it in, after setting USB Mode to None and turning on the USB Debug, ADB drivers fail to install. It shows up in my device manager with a ! ontop of the icon, and windows tells me it cant find a driver. I manually downloaded the drivers but that still didnt help, my phone isnt making a connection of the bridge. Ive wiped everything everything motorola related, reinstalled the drivers manually, reinstalled the ADB driver manually, rebooted about 10 times and now im absolutely stuck.
Has anyone run into this before? Im going to try plugging the phone into my work computer today, but id like to be able to get this working on my home computer. I followed the guide thats available out there that tells you to run the driver installer and delete all the files it shows, and that didnt help either. Im on Windows 7 but i also have a laptop with Ubuntu available, however i couldnt find a rooting guide for linux so im not sure if that will help.
albinojoe said:
So I just got an Atrix and im trying to root it, however when I plug it in, after setting USB Mode to None and turning on the USB Debug, ADB drivers fail to install. It shows up in my device manager with a ! ontop of the icon, and windows tells me it cant find a driver. I manually downloaded the drivers but that still didnt help, my phone isnt making a connection of the bridge. Ive wiped everything everything motorola related, reinstalled the drivers manually, reinstalled the ADB driver manually, rebooted about 10 times and now im absolutely stuck.
Has anyone run into this before? Im going to try plugging the phone into my work computer today, but id like to be able to get this working on my home computer. I followed the guide thats available out there that tells you to run the driver installer and delete all the files it shows, and that didnt help either. Im on Windows 7 but i also have a laptop with Ubuntu available, however i couldnt find a rooting guide for linux so im not sure if that will help.
Click to expand...
Click to collapse
which windows 7 32 or 64?
32 bit.
Tried on 2 different PC's, my home computer and my work computer. ADB driver fails to install on both. Both running windows 7 32bit.
albinojoe said:
32 bit.
Tried on 2 different PC's, my home computer and my work computer. ADB driver fails to install on both. Both running windows 7 32bit.[/Q
try to use the drivers from this thread and see if that works
Click to expand...
Click to collapse
or this site use the motohelper
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
I got it sorted. Installed the ADB driver manually (choosing the regular adb driver NOT the composite driver) and then ran super one click to start the ADB service. Then once the phone was connected, ran aroot and it worked.
albinojoe said:
I got it sorted. Installed the ADB driver manually (choosing the regular adb driver NOT the composite driver) and then ran super one click to start the ADB service. Then once the phone was connected, ran aroot and it worked.
Click to expand...
Click to collapse
glad you got it
Hello, I'm having tons of trouble getting the drivers to work on my computer. When the phone is on and plugged in, the HTC drivers seem to be okay. When I boot into fastboot, the drivers stop working. I try to manually update the drivers (have the 64-bit drivers downloaded) while in fastboot but it doesnt work. What am I doing wrong?
Thanks for the help.
Try using the command and reboot bootloader to force fastboot, if its a driver problem it will still not work, make sure you have your terminal in the asb or SDK folder as well, if it still won't connect ill offer another fix
Alright so I'm no stranger to flashing ROMS and whatnot, but today I slipped up and deleted everything on my internal storage, including my NANDROID backup. I still have access to my recovery (CWM touch v6.0.4.5). So I thought "no problem, I"ll just ADB sideload". Well here we are.
Basically I can't get my ****ing phone to communicate with my computer. I installed every damn thing I could think of to get my device to show up after typing "adb devices". I tried the universal toolkit, but as expected it didn't work very well. I tried it on my laptop and desktop, through USB 2.0 and 3.0. I installed the generic Android USB ADB driver, I installed HTC sync for DNA drivers, I installed a standalone version of the DNA driver, and no dice. Can't even get fastboot to communicate. Even though my phone says fastboot USB my computer won't recognize it.
This is seriously ****ing pissing me off, because it should be a simple fix. Anybody have words of wisdom to help me out?
Thanks in advance.
FCO2011 said:
Alright so I'm no stranger to flashing ROMS and whatnot, but today I slipped up and deleted everything on my internal storage, including my NANDROID backup. I still have access to my recovery (CWM touch v6.0.4.5). So I thought "no problem, I"ll just ADB sideload". Well here we are.
Basically I can't get my ****ing phone to communicate with my computer. I installed every damn thing I could think of to get my device to show up after typing "adb devices". I tried the universal toolkit, but as expected it didn't work very well. I tried it on my laptop and desktop, through USB 2.0 and 3.0. I installed the generic Android USB ADB driver, I installed HTC sync for DNA drivers, I installed a standalone version of the DNA driver, and no dice. Can't even get fastboot to communicate. Even though my phone says fastboot USB my computer won't recognize it.
This is seriously ****ing pissing me off, because it should be a simple fix. Anybody have words of wisdom to help me out?
Thanks in advance.
Click to expand...
Click to collapse
When your in hboot/fastboot and connected to your computer does it say fastboot usb? If it does when you type in fastboot devices is it recognizing your device at all? Should bring up serial number. Are you on Windows xp/7/8 or 8.1?
Sent from my HTC6435LVW using XDA Free mobile app
Which version of the universal ADB drivers did you use, because I just did this to my phone about a month ago and had the same issue? Once I installed the universal generic driver everything communicated and worked properly.
Try installing PDAnet it blanket installs a bunch of drivers that got me out of a similar spot!
I have a Win 8.1 machine with the HTC drives installed and when I run ADB with the phone booted to the ROM everything is fine. ADB returns the device ID and it is recognized. When I boot into the fastboot, I get fastboot usb but ADB does not recognize the device, I get List of devices attached and then nothing. I have rebooted both the phone and computer, uninstalled and reinstalled the drivers but no luck. Anyone ever seen this behavior?
Please close thread.
For whatever reason fastboot on my PC (win10) doesn't detect my phone, adb detects it fine when it's in recovery or booted normally, I cannot send fastboot commands as it says waiting for device. I've tried a few things like the LG Mobile Driver and a universal driver but it still isn't working. Any ideas?
Just to clarify I am in Fastboot mode when trying this.
Edit: Also tried the Google USB drivers from the SDK manager, didn't make a difference
I ended up simply doing it on an Ubuntu installation. Works perfectly on there, not sure why Win10 doesn't work though.
My problem is solved.