It seems that i am not able to get ADB to work on any of the 2.1 versions i tried.
I installed, uninstalled, reinstalled the Dell PC suite.
The phone is in USB debugging mode.
My device manager is seeing "Android ADB interface" under Android phone but doing "adb devices" is showing no connected devices.
I have an at&t locked phone which i upgraded to the O2 8105 release and then downgraded back to 6941 2.1 beta release.
I had no luck getting ADB to work on either firmwares. i never tested on 1.6.
Running windows 7 64bit and also tried on Windows 7 32bit.
Nothing works.
Anyone has any idea how to get ADB working?
I am starting to think that at&t somehow blocked ADB so we wont be able to install 3rd party APK's and it is hardware blocked. My Streak is two days old so i got it from recent batch.
End task your adb.exe in task manager, locate adeproxy within the dell suite software and use that in place of adb.exe. this allowed me to get the sideload app working on 1.6.
THANKS!!!
that works. i would never figured it out myself.
So is dell doing this on purpose?
Dunno if its on purpose, some kind of driver conflict with adb itself.
Related
Hi,
I have a Vodafone 845, and I couldn't get connection with adb.
I'm using windows 7 32b. My device is recognized as android adaptar usb device (cdrom driver), I tried to update the driver to android_usb_driver.
Any suggestions?
I ran into the same issue, could not uninstall Microsofts driver.
Use adbWireless (some old version (works fine) is attached).
I have the same problem,
your wifi adb apk needs a rooted phone.. but the reason I need the SDK connected ADB to the phone is because I can't find a root solution for this phone, and want to take screenshots via the Android ADK, but it wont' connect.
ADB connection
I'm new here but i did find a way to fix that problem. Im using Windows 7 32 bit.
I just installed the PC suite that comes with the VF845 (when u plug in the phone through the USB cable) and ADB ends up working.
Pretty sure this also works on XP....
Hope this helps
I recently bought the Motorola Droid RAZR and when I powered up the phone, I received a notification to update to System Version 6.16.211.XT912.Verizon.en.US
I agreed and the phone updated. I notice that I am now on Android 4.0.4.
I am trying to root the phone, but when I connect it to my PC, There is no Motorola ADB driver installed. All my drivers are up to date and I have tried this on multiple computers but to no avail. I also have the Android SDK installed.
What I have noticed is that when I connect my phone with USB debugging checked, the USB Networking driver is installed. Typically its the ADB driver that's installed but not in this case, so when I type in ADB devices my phone is not listed.
Anyone else have this problem? Any help would be much appreciated. Please let me know if you need any information and I'll be happy to provide it.
Thank you.
Same here...
I'm seeing the same thing. I've tried all combinations of settings on the phone, PC, Mac, Motocast Drivers, etc. No luck.
New Driver?
I noticed some new Windows drivers were released today on Motorola's dev site. I'm on my Mac today, so I can't give it a try myself.
This forum is blocking me from posting URLs (t00 n00b). developerdotmotoroladotcomslashtoolsslashusb_drivers
No luck...
That didn't work... The problem is that when I switch the phone from Mass Storage to MTP (Media Device), it installs Motorola Networking Drivers... I was expecting it to install the Motorola Composite ADB Interface Drivers....
Maybe an older version of the drivers would help? Not sure...
Fix Found
greatguitartist said:
That didn't work... The problem is that when I switch the phone from Mass Storage to MTP (Media Device), it installs Motorola Networking Drivers... I was expecting it to install the Motorola Composite ADB Interface Drivers....
Maybe an older version of the drivers would help? Not sure...
Click to expand...
Click to collapse
So after all my attempts at installing the ADB Interface failed, I performed the following steps (although a little grudgingly... lol)
1. a factory reset on my phone (currently on ICS 4.0.4).
2. Uninstalled ALL motorola drivers from my PC and installed the one that came with mattlgroff's DroidRazr Utility 1.7
After this, I turned on USB Debugging and connected the phone to my PC and voila! it worked. Even though the USB option was set as Mass Storage, It still installed the ADB Drivers. I set the USB Option to MTP and was able to successfully root my phone using the utility.
Hope this helps.
FYI - If you'd like to take a backup of your text messages then you can get the SMS BackupRestore app from the play store
greatguitartist said:
2. Uninstalled ALL motorola drivers from my PC and installed the one that came with mattlgroff's DroidRazr Utility 1.7
Click to expand...
Click to collapse
I think this is what got it working for you. Windows sometimes won't install USB device drivers if it thinks it's already been attempted.
This is a HUGE problem that I spent the last 12 hours researching how to fix. Instead of typing an essay on how to fix it, I made a blog post that outlines how to fix this problem. The blog post is here: Fix Adb Droid Razr Problems.
The phone and cables are good as I can get HTC Sync to work on my old PC and this one worked just a few weeks ago and I can even get it to work in a VMware session. But for whatever reason the phone just keeps showing up as Unknown and is put under Other devices as “Android phone”. On the other PC and in the VMware it is added as "My HTC" under Android USB Devices in Device Manager.
I’ve tried a bunch of uninstalling and rebooting and so on but something on my new Windows 7 PC is stuck when connecting the phone. It thinks it has no driver for it but it does. If I try and point any of the HTC INF files Windows just says they are not for this device.
Help!
Thanks.
Tanquen said:
The phone and cables are good as I can get HTC Sync to work on my old PC and this one worked just a few weeks ago and I can even get it to work in a VMware session. But for whatever reason the phone just keeps showing up as Unknown and is put under Other devices as “Android phone”. On the other PC and in the VMware it is added as "My HTC" under Android USB Devices in Device Manager.
I’ve tried a bunch of uninstalling and rebooting and so on but something on my new Windows 7 PC is stuck when connecting the phone. It thinks it has no driver for it but it does. If I try and point any of the HTC INF files Windows just says they are not for this device.
Help!
Thanks.
Click to expand...
Click to collapse
make sure you have the correct drivers for you phone, if you using the latest version download and install an lder version of the drivers then try to connect
That’s the thing though. The drivers were just fine a few weeks ago. The same drivers work on another PC with this phone and they work now on this same PC in a VMware session. There is something stuck in my Windows host install that no longer allows any new devices to be installed. Like one of the fixes I found on line was to remover your USB hubs and let Windows find and install them again but then they could not be installed and were added to the Other devices. I had no mouse or keyboard. I had to run a system restore under the F8 options on boot up. Unfortunately I don’t have a restore point older than the issue. Even if I unplug my working mouse and put it in a different USB port it too is added to Other devices and no longer functions. I just get messages about it being an unknown device and that no drivers can be found.
I have a new S4 with baseband MK2. I am getting ready to do the root etc. but I was testing ADB first to make sure it works.
I have installed the latest USB drivers, and turned debug on in the S4
I get get adb to launch, but when I use the command "ADB devices" nothing shows up.
I have rebooted both PC and phone with the same results.
Question,
Does the phone need to be rooted before ADB will work? If so....then how to I side load "Towelroot"? or anything else for that matter.
am I missing some sdk files...or something else?
Thanks
wetwaterdog said:
I have a new S4 with baseband MK2. I am getting ready to do the root etc. but I was testing ADB first to make sure it works.
I have installed the latest USB drivers, and turned debug on in the S4
I get get adb to launch, but when I use the command "ADB devices" nothing shows up.
I have rebooted both PC and phone with the same results.
Question,
Does the phone need to be rooted before ADB will work? If so....then how to I side load "Towelroot"? or anything else for that matter.
am I missing some sdk files...or something else?
Thanks
Click to expand...
Click to collapse
Usually when nothing shows up at all it's a driver issue. What drivers did you install where did you get them. Windows right?
Edit : root not required.
jawmail said:
Usually when nothing shows up at all it's a driver issue. What drivers did you install where did you get them. Windows right?
Edit : root not required.
Click to expand...
Click to collapse
Got the drivers from samsung site...latest ver 1.5.45. phone connects to windows computer and displays directories so I know the USB driver is ok.
I did some more looking and am updating my sdk devices right now. I expect that to correct the problem.
wetwaterdog said:
Got the drivers from samsung site...latest ver 1.5.45. phone connects to windows computer and displays directories so I know the USB driver is ok.
I did some more looking and am updating my sdk devices right now. I expect that to correct the problem.
Click to expand...
Click to collapse
Drivers are good then, update your SDK like you said and try again. It should work after that, I don't have an S4 but they're all the same when it comes to ADB and fastboot. Good luck.
jawmail said:
Drivers are good then, update your SDK like you said and try again. It should work after that, I don't have an S4 but they're all the same when it comes to ADB and fastboot. Good luck.
Click to expand...
Click to collapse
Yup....sdk's installed and all is well.....
I sure wish I knew exactly which downloads to take from the SDK download manager....
I played it safe with the 4.3 and 4.4. I didn't know if the updates were progressive (included all past needed stuff) or just specific for the version.
I installed the Win 10 drivers,
I installed ADB and its DLLs and fastboot.
I cannot install the Java run time as it doesn't
know Windows 10,
The VMware guest does see the the an droid phone
as an MTP device.
adb devices reports nothing
with the phone running adbwireless
adb connect [ip address] also fails.
Is it just Win 10 isn't ready for prime time yet?
Or is there something else I can try?
Update: Fastboot boot does see the device from the guest.
maybe it is a driver or DLL issue?
Don't have any issues with adb or fastboot on Windows 10 here. I have Java 8_35 installed. Don't know why you can't either.
I guess I was in too much of a hurry
After restarting, and reconnecting the phone, it decided to load new drivers.
ADB and fastboot both appear to work as expected.
Java still wont install, but doesn't seem to need either.
Maybe the Java requirement of the android SDK
is for other things?
thanks for replying
fuzzynco said:
After restarting, and reconnecting the phone, it decided to load new drivers.
ADB and fastboot both appear to work as expected.
Java still wont install, but doesn't seem to need either.
Maybe the Java requirement of the android SDK
is for other things?
thanks for replying
Click to expand...
Click to collapse
You on the latest preview build? It thinks mine is Windows 8.1
ye,s, it thinks mine is too (Win 8.1)
I guess Java isn't ready for Win 10