Hi- it was working then stopped- tried different cables and the following remedies with no luck
Android Won't Connect to Windows Over ADB? How to Fix in 3 Easy Steps
Is ADB not detecting your device? When Android is unable to connect to ADB, here's how to fix it and get connected again.
www.makeuseof.com
Here is what I see on PC after a clean ADB install and PC reboot and A53 attached
C:\Program Files (x86)\ADB\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
C:\Program Files (x86)\ADB\platform-tools>adb devices
List of devices attached
Screen shot of device manager attached. I did install ADB drivers but device manager does not see them (or am i missing something. I also have Driver easy- nothing to report there (unijstall devcie etc reinsatll etc has no effect)
Thanks!
Use Android USB Driver as provided by Samung for the phone: the ADB driver you installed is for Google devices!
Enable USB Debugging on phone.
By the looks of the screenshot, I can see that you have a pretty cluttered system.
Use this:
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
ze7zez said:
By the looks of the screenshot, I can see that you have a pretty cluttered system.
Use this:
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you - I gotta laugh- USB debug must not have survived a reboot-I thought it did. I am good.
Related
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
LOL, I just switched back from Ubuntu to Windows 7 just to see how things have progressed. There are so many little Windows 7 quirks that drive me crazy that drove me back to Ubuntu almost instantly. Give Linux a try. A good starting Linux OS would be Linux Mint:
http://www.linuxmint.com/index.php
I had a similar issue when I tried it. Despite the fact that there are 64-bit drivers for Vista/7 available, I don't believe they actually work for ADB currently. I'm pretty sure everyone who has ADB working is using Windows XP 32-bit.
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
ch4dr0x said:
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
Click to expand...
Click to collapse
I faced the same problem a few days ago. I have Windows 7 Ultimate x64 and in a first installations the drivers work fine and the device has been displayed, but BAM when I try to use ADB no way.
After many tries I resolved the issue running the Command Prompt as "Run as administrator" and VOILA worked fine.
I hope this can help you.
ch4dr0x said:
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
Click to expand...
Click to collapse
Try Mint instead of Ubuntu. Mint is Ubuntu based. The big difference with Mint is that it already has all of your codecs installed - great for beginners.
If you installed first the htc sync, you have to remove the current drivers..
and had the drivers from the androidsdk pack! There's is a a lot of program who delete usb installed hardware/drivers.. delete all from htc on this programs!
Hope this solves ur issue!
I use Win7 64bit(rc1) .. i have the amd64 driver installed..
I see the phone from adb (not fastboot) when it's normally connected with USB debugging turned on.
I see the phone from fastboot (not adb) when it's in fastboot mode.
I have no choice but to laugh at myself, just realized I was IN FASTBOOT on my phone and not recovery. Fail me.
Now if I could just edit this apps2hd code /sigh.
ricardomega said:
If you installed first the htc sync, you have to remove the current drivers..
Click to expand...
Click to collapse
and remove htc sync, there are a process than cause problem with adb (i don't remember the name)
I kill this process and adb 100% work fine, or unistall HTC Sync..
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
ricardomega said:
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
Click to expand...
Click to collapse
Except that... that wasn't my issue Its ok thanks for the input.
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
parrot5 said:
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
Click to expand...
Click to collapse
The same confi, the same result
Everything works fine here with Win 7 Ultimate x64, you just install the driver in the Android SDK.
make sure u have usb debugging checked... cause i have windows 7 rtm ultimate and my adb works fine... i just loaded the needed file into windows/system32 and also put my fastboot.exe in there and added the tools folder to the environment variables and have no problems
What do I load to the system32 folder? I can't install the drivers from the SDK package. Is there a way to overwrite the ones Windows automatically installs and thinks is more up to date?
detonate said:
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
Click to expand...
Click to collapse
Make sure your phone is in recovery mode and NOT fastboot mode.
Finally, I experienced that error you people had been reporting. It MAY have to do with the HTC Sync driver, as suggested, but it really had worked fine with other roms before, so I am not sure. I tried uninstalling and reinstalling the driver, tried to push the ADB driver manually, but that didn't work. And, before I try to uninstall the HTC Sync driver as suggested (I don't even know if I have that installed), I got it working by just plugging in another USB flash drive. Go figure.
So for anyone still having the issue after trying all other solutions, try this bizarre one:
1. Go to device manager and uninstall the HTC disk drive device. (This alone won't work, I tried)
2. With phone still plugged in, plug in a USB disk drive (or maybe just any USB device?) into another USB port.
3. Suddenly Windows 7 detect that unknown ADB driver, as it should. Now you can go ahead to install the correct ADB driver.
As a side note, this computer running Windows 7 Beta/RC have had a lot of problems with USB disk drives in general. The problems disappear after Windows 7 RTM (final).
I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.
Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk
Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!
I wasn't sure where to post this, as the only Blackview-related subforum is for one of their phones... Anyway, I recently bought Blackview Tab 8 (a 10" tablet), and I'm quite pleasantly surprised about its quality (even the box is almost wooden-like ) and the fact that they give you basically everything you need in the package (unlike some manufacturers who keep taking away things season by season...). Also, pure Android without any bloatware - there were a couple of games and apps I don't really need, but they can all be easily uninstalled, or at least disabled (the latter didn't reappear so far, I hope it stays that way).
Three questions for now:
- Any idea which ADB drivers should I install to be able to use adb on this device? I already have three on my Windows 7 computer from before, but connecting this device to the computer didn't find a suitable one.
- How can I remove the "silhouette" of Google Search widget/box on the home screen (other than the workarounds such as changing the launcher, or moving icons to a secondary page and leaving the silhouette alone)? It just stays there after disabling Google/Assistant/etc apps, but doesn't do anything and it can't be moved. I had a similar issue in the past (I think it was a Chuwi tablet).
- How can I tell if the device can be connected to an external display via USB-C to HDMI adapter?
Google's ADB & Fastboot drivers basically are both device and Android OS version independent. However how they got implemented by OEM/Carrier is different. Also in most cases it's required to install an additional "Android USB Driver" provided by OEM/Carrier to make ADB and/or Fastboot flawlessly work.
A link to an ADB / Fastboot installer is to be found in my signature.
I think I actually need those "additional drivers". From what I can see your script downloads what I already have (from platform-tools). adb.exe doesn't show any devices, though. The exclamation marks in Device Manager are at "ADB Interface" and 3x "Unisoc Phone".
Neuromancer said:
I think I actually need those "additional drivers". From what I can see your script downloads what I already have (from platform-tools). adb.exe doesn't show any devices, though. The exclamation marks in Device Manager are at "ADB Interface" and 3x "Unisoc Phone".
Click to expand...
Click to collapse
Here you go:
Unisoc / Spreadtrum SPD drivers for Windows (SCI & USB)
Its important to install SPD drivers else Spreadtrum flash tools like Research Download, CM2 SPD etc won't be able to detect the phone. This is a collection of unsigned (.inf) drivers to be installed
forum.hovatek.com
I tried
Spreadtrum SCI Android USB drivers
Spreadtrum Drivers
SCI android usb driver jungo v4
SPD drivers 2018 ver2.0.0.131
but none of them worked.
In the end, I was able to make it work using these drivers:
How-to install SPD Driver R4.20.0201 (Easy Guide)
Step-by-step guidelines to download and install SPD Driver R4.20.0201 on Windows Computer to connect SPD/Unisoc Devices.
gsmusbdriver.com
But truth be told, I'm not sure if that was the only requirement (because there were also remnants from previous manual install from the link jwoegerbauer provided).
I'm really having a hard time getting ADB drivers to work on Windows 7 so that I can connect my Android phone to my computer to run some ADB commands. I've tried three different packages; I guess the latest ADB MSI installer and another couple various packages. And I can't get any devices to show up when I type ADB devices. I need something simple if somebody can help treat me like a newbie although I have some experience with Linux and the command prompt but I really need something dead simple that will just install ADB on my computer so I can run a command on my phone. Any help would be greatly appreciated.
Wjbell said:
I'm really having a hard time getting ADB drivers to work on Windows 7 so that I can connect my Android phone to my computer to run some ADB commands. I've tried three different packages; I guess the latest ADB MSI installer and another couple various packages. And I can't get any devices to show up when I type ADB devices. I need something simple if somebody can help treat me like a newbie although I have some experience with Linux and the command prompt but I really need something dead simple that will just install ADB on my computer so I can run a command on my phone. Any help would be greatly appreciated.
Click to expand...
Click to collapse
While plenty of people know adb better than I do, I can try to help you where we need to start at the beginning I think, which is to state that there is nothing to "install" on either Android or Windows, other than the one adb.exe executable on Windows.
However, you do need to enable a few options in Android settings.
With that, you can get Windows to talk to Android over adb as shown in my screenshots below, whether over USB or completely over Wi-Fi.
My first question to you to help you is to ask a basic question.
Q: Did you turn on USB debugging in Developer options?
A: ?
Yes I have us debugging on on my Android phone. I've installed USB drivers before on an older phone to allow me to use my Android phone for an internet connection on my PC and it was pretty simple and word flawlessly.
I have an rca tablet I can not get any drivers to work to get to replace/update the firmware and I was wanting to ask if anyone has found anything that works.
I have tried mediatek, rca and all other drivers I can find and nothing seems to work on windows 10 64.
Thank You
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
xXx yYy said:
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
Click to expand...
Click to collapse
Thank You will give a try
I have a Windows 7 64 bit system and I am trying to find drivers to access an rca rct6703w13
I have tried every driver I can find and nothing seems to work does anyone know something that will work?
I would be very grateful if anyone could help?
Thank You
Oh boy, I still remember this pain trying to find and use such drivers on Windoze:
- try another port
- try another cable
- try this driver or that one
- try doing a rain dance with 3 days old undies on your head, and turn only clock wise, unless it's full moon, then turn counter clockwise but stop briefly after ever two and a half turns
Maybe, as workaround, you could boot from a linux CD and try your approach from there.
Whenever I flash from my debian, it works: If "fastboot devices" still doesn't show anything then usually I have forgotten to plugin the cable
By using my "Yet Another Universal ADB Driver" Package (see the link in my signature) one can remove all the old adb drivers if that is the issue, but this case seems to be more interesting...
On win10 it seems that the adb is embedded to the winusb driver the same or similar way (registry wise) that my package is using. Now that I have tested, the behavior is similar with my devices. When using file transfer connection the adb is not recognized. With others, charging, photo, midi the abd works fine. To make adb work with file transfer one have to install the correct driver. In this case google's general driver could be okay, one match for vendor and product ids in it ...
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
What I tested using virtual win7 64bit, it seems to behave the same way... which is a bit weird as I've tested it with my driver package. Worked okay then I think. The Android device used has changed since though.. It worked on win10 back then too.. the change has to have happened later.. or I didn't use file transfer..
@steadfasterX 's maid or salt or whatever it's called nowadays might be usable in this case. It's a Linux having SP flash tool etc. available..
edit: tested and it turned out that the updated phone is the problem... using another phone my driver package worked as expected..
@resxwni01
1. Don't confuse USB-driver and ADB-driver: the USB-driver since ever is by default part of any OS, so also of Windows OS. The ADB-driver is an extra protocol what allows you to communicate with a phone's Android ecosystem via an USB-connection.
2. Latest generic ADB-driver ( correct: ADB client ) got released August 2022 and is officially versioned 33.0.3.
3. AFAIK a 64-bit version of ADB-driver doesn't exist.
With regards to install this ADB-driver on a Windows 7,8.1,10,11 PC:
It's NO USB-driver installer - as introduced above by @CXZa - needed what unnecessarily bloats the Windows registry with crap.
You
1. simply create on any mounted drive of Windows PC a folder named "ADB",
2. extract there to the 3 files what are in the attached ZIP file,
3. add path of created folder "ADB" to Windows environment variable PATH, thus ADB-driver is systemwide accessible -
how to is described here
How to Set the Path and Environment Variables in Windows
Information on how to set the path and environment variables in Windows 2000, Windows XP, Windows Vista, and Windows 7.
www.computerhope.com
@jwoegerbauer , you're funny guy...