Unfortunately Prolific haven't written Android drivers for this chip. SlickUSB make a terminal for Android and their library recognizes the PL2303TA but their website is down. Can someone please give me a copy of this library or point me to an appropriate replacement?
any update?
Related
Does anyone need these, I know the Regs for non DB mode are out there didn't know if anyone wants these? Wont let me postoutside link.
Via the browser under files, please dont hotlink.
ADB Drivers:
vibrantsamsung.com/extra/files/Samsung_Vibrant_ADB_Drivers.zip
USB Drivers:
vibrantsamsung.com/extra/files/Samsungusb.zip
Current Version 1.0.26 ADB
vibrantsamsung.com/extra/files/adb_1.0.26.zip
You need Android Debug Bridge version 1.0.26 or newer I think this is the newest so far.
I could use the drivers.... The only thing I could find driver wise for the Vibrant was Samsung PC Studio, and ADB will still not detect my vibrant.
Thanks.
I could use the drivers too. Where did you find them?
I need the usb drivers too.
The drivers provided in the google sdk dont seem to work. My device is showing up as SAMSUNG_Android in the device manager, but i cant update the driver.
Came across this thread, t=728929 and the drivers worked for me. Im too new to post the entire link
forum xda-developers com / showthread.php ?t=728929
Ok guys sorry for the delay
Via the browser under files, please dont hotlink.
ADB Drivers:
vibrantsamsung.com/extra/files/Samsung_Vibrant_ADB_Drivers.zip
USB Drivers:
vibrantsamsung.com/extra/files/Samsungusb.zip
Current Version 1.0.26 ADB
vibrantsamsung.com/extra/files/adb_1.0.26.zip
You need Android Debug Bridge version 1.0.26 or newer I think this is the newest so far.
Hello. That's a vague question :
I have a custom USB device (class 0xff) and I want to communicate with it using my Android phone. I'm on ICS "stock" (original), and official API provides USB functionnalites.
I use a Java and C API to communicate with my device from my computer (libusb), so I though that it could be possible to do the same with my Androphone, and an OTG USB cable.
But my problem : When I plug the device to the Smartphone, it is correctly detected (and powered). Endpoints are correctly listed, and I can retrieve the serial name. But when I call the "claimInterface" function (Android API), it fails. I don't understand why, because the class of my device is unspecified and shouldn't be handled by Android OS or other App.
When I do a diagnostic with the XDA USB Host test software, I get "yes" in line "claimed" (Base API).
I realize that my question is too specific. My hope is to find someone who has already worked on this kind of problem, or who knows the limits of the USB host.
Thanks in advance.
(My phone is not rooted)
EDIT : Rooted. Same problem :/
It's an ainol Novo7 Venus, 7" tablet.
According to Windoiws ADB, the vendor id is 10D6, and the product code is 0C02.
I've successfully flashed Android version 4.2.2 onto the device (from 4.1) using Windows.
My main develoment machine runs Ubuntu 12.10, but ADB on this machine won't recognise the Anal (ainol) tablet.
lsusb identifies the device as 10d6:0c02 from Action Industries Ltd, so it's almost a dead cert that the vendor id is correct.
I've set up udev rules to try and get it recognised, but it just won't have it.
Any ideas?
Thanks.
Geoff.
Hello,
I want to make a simple python app which get some informations from the android Phone plugged in usb.
I'm actually using adb but I don't find a lot of documentation about how to make an application interact with a androidphone usb plugged
I'm using Linux environment to develop the app
The goal is to define which ROM can be install on the plugged phone depending on his caracteristics
Thank you
Do you mean that you will have your application just treat your mobile phone as an USB storage?
Clayzes said:
Hello,
I want to make a simple python app which some informations from the android Phone plugged in usb.
I'm actually using adb but I don't find a lot of documentation about how to make an application interact with a androidphone usb plugged
Thank you
Click to expand...
Click to collapse
Look inside here:
Access a USB device by using WinUSB functions - Windows drivers
This article includes a walkthrough of using WinUSB functions to communicate with a USB device that is using the Winusb.sys driver.
docs.microsoft.com
BTW: ADB's source code is foundable in Internet.
James_Watson said:
Do you mean that you will have your application just treat your mobile phone as an USB storage?
Click to expand...
Click to collapse
Sorry, I meant "get technicals informations" from an Android Phone like (android verison, available memory etc.."
jwoegerbauer said:
Look inside here:
Access a USB device by using WinUSB functions - Windows drivers
This article includes a walkthrough of using WinUSB functions to communicate with a USB device that is using the Winusb.sys driver.
docs.microsoft.com
BTW: ADB's source code is foundable in Internet.
Click to expand...
Click to collapse
Thank you for your answer , I forgot to say that I'm using Linux distribution but I'll try to find an alternative
I edited the post to add important informations
Clayzes said:
Hello,
The goal is to define which ROM can be install on the plugged phone depending on his caracteristics
Thank you
Click to expand...
Click to collapse
Each Android ROM - what exists of 1. Linux kernel, 2. Android framework (API), & 3. device peripherals (OEM drivers) - varies from manufacturer to manufacturer, varies from device model to device model.
My POV:
What you want to achieve requires in any case that you know of the "device tree" of the device you want to be explored what IMO requires to have access to OEM's source code. Good luck!
jwoegerbauer said:
Each Android ROM - what exists of 1. Linux kernel, 2. Android framework (API), & 3. device peripherals (OEM drivers) - varies from manufacturer to manufacturer, varies from device model to device model.
My POV:
What you want to achieve requires in any case that you know of the "device tree" of the device you want to be explored what IMO requires to have access to OEM's source code. Good luck!
Click to expand...
Click to collapse
OK ! that's what I'm doing to and I thought that it was wrong
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...