Related
I bought eTouch tablet 7' ELONEX model ELX-765ETv2 some time ago and because of some problems on it I would like to install some diagnostic tools on it which require to root this tablet. To do so I need the usb driver to connect this tablet into pc to run adb program.
When I check it in the Device Manager on pc it shows it should be Android for Vortex driver
Is it any chance to get the usb driver for this tablet?
I would appreciate any help. Thank you.
I am looking for adb usb driver for my laptop ELONEX765
I had downloaded usb driver from LG website for phone LGV660 which is only Vortex one I've found anywhereLG LGVS660 Support: Find Manuals & Warranty Info | LG USA and afterwards I installed it and I did not see any difference (it just didn't work).
How to get adb usb driver for my tablet?
I've noticed my usb partly works only gives access to SD memory on tablet but it does not work for adb comments because tablet as device is not seen for adb commands. So I am guessing I must have adb usb driver which is a little different.
Still no idea where to get adb usb driver for my tablet?
How to get adb usb driver for my tablet?
Still no idea where to get adb usb driver for my tablet?
Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system:
Code:
[49875.145923] usb 1-1.2: new high-speed USB device number 12 using ehci-pci
[49875.240046] usb 1-1.2: New USB device found, idVendor=0bb4, idProduct=0c02
[49875.240057] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[49875.240063] usb 1-1.2: Product: MT65xx Android Phone
[49875.240068] usb 1-1.2: Manufacturer: MediaTek
[49875.240072] usb 1-1.2: SerialNumber: ...
but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi
prinz.z said:
Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system. but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi
Click to expand...
Click to collapse
I guess this is more an Ubuntu issue/question than Fairphone's..
You can follow instructions here
Code:
$ sudo mtpfs -o allow_other /media/MTPdevice
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=0bb4 and PID=2008) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:2008 @ bus 2, dev 20
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: FP1
Nautilus gave me read-only access to content under the custom mount point /media/MTPdevice. dmesg gave me the same log as yours when recognizing the device...
It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)
Okay, I see.. With my former phone (LG O4x, cm-11) it was working flawlessly with mtp on Ubuntu, that's the rason I asked.. With the fairphone, I'm simply using adb for the moment to copy single files..
elchi1234 said:
It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)
Click to expand...
Click to collapse
Hi,
I have a Lumia 950 phone running windows 10 mobile. and am intending to use a FTDI usb to serial(rs232) cable with the USB OTG port on the phone. however, the cable driver is not automatically installed. I downloaded an ARM-based winRT driver from FTDI but have no way to load the inf file to the phone.
Does someone did similar things before? help is much appreciated!
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
danhawker said:
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
Click to expand...
Click to collapse
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
melendi said:
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
Click to expand...
Click to collapse
Do you have a nvidia gamepad?
gengt said:
Do you have a nvidia gamepad?
Click to expand...
Click to collapse
Yes and I had already been in fastboot but on another android device with osm0sis ADB & Fastboot script there are no fastboot devices listed.
Hi
I want to flash a system through Flashtool to my Xperia Z1 Compact. I've installed the drivers and connected the phone in flash mode. But Windows says that "USB device is not recognized". In devices manager the Xperia is showed as "Unknown USB Device (Device Descriptor Request Failed)". I tried to connect to another usb ports or with other usb cables. I also tried to update drivers of USB Hubs (by clicking on them and selecting Update driver). I also tried to install the drivers straight from Sony Developer Site. I also installed Xperia Companion. Nothing helps.
Repairing software via Xperia Companion is impossible because of that.
I tried to install drivers again for at least 5 times. After that installer says this:
Sony (WinUSB) sa0109AdbDeviceClass 05/13/2013 2.0.0010.30018 - Ready to use
Sony Net (5/13/2013 6.0.6000.16501 - Not need (no devices to update)
Google, Inc. (WinUSB) AndroidUSBDeviceClass (12/06/2010 4.0.0000.00000 - Ready to use
Sony Mobile Communications (ggsomc) USB (11/10/2014 3.1.0.0) - Ready to use
It's weird because my other Xperia (Xperia L) is recognized without any problems.
Is there any solution to that problem other than installing a clean copy of Windows?
Computer Specification (maybe useful):
Windows 10 Home 1803 64-bit
AMD Ryzen 5 2600
GeForce 1060 Ti
AsRock B450 Fatl1ty Gaming K4
8 GB RAM
I installed drivers on Windows 10 as well. When I connected the device and entered in the power shell
Code:
./adb.exe devices
it answered: "List of devices attached", "daemon started successfully" and showed my device.
With
Code:
./adb.exe reboot bootloader
I put it in fastbood modus and the problems began.
If I understand correctly, that's the same state, you were in.
My solution was that the driver for fastboot was wrong. I downloaded an updated version for fastboot from Sony Website.
The driver was unsigned, therefor I had to go into Windows UEFI (new Bios) to enable installation of unsigned drivers... (at own risk)
When I installed this second driver, the device was recognised in power shell, when I typed in commands with:
Code:
./fastboot.exe
and also with flashtool.
Hey there, same problem with my Ryzen system as well. Something with the motherboard drivers or the USB drivers that are not updated to work with these new boards.
As you explained, adb and fastboot works, but flashmode detection is broken.
Flashmode still gets detected on my Surface Pro 4 and ThinkPad T450s.