Hello All,
Does anyone know where to get ADB Drivers for new Sony Xperia Tablet S?!
Also can any of the current owners confirm if they can charge their tablets through USB cable connected to the PC?
OK never mind I got it, I installed Tablet s ADB drivers the manual way and I got it working.
For those who need it, Download Here and follow below steps...
If the driver installation fails, you will need to manually install the driver.
Go to the Device Manager and find the failed install (typically the yellow "!" mark and "Sony Tablet")
Right-click on it and select "Update Driver"
Select "Browse my computer for driver software"
Select "Let me pick from a list..."
Choose "Show All Devices" and click "Next"
Click "Have Disk..."
Click "Browse..."
Browse to where you extracted the ADB driver installer and select "android_winusb.ini"
Click "OK"
From the list, select the 3rd choice: "Android Composite ADB Interface"
Click "Next"
A warning will pop up: "Installing this device driver..." click "Yes"
Another warning will pop up: "Windows can't verify..." click "Install this driver software anyway"
The driver should finish installing.
Click "Close" and it should now show up as an "Android Composite ADB Interface"
Restart PC
You can now use ADB through a command prompt window to run commands.
e.g. adb devices
Any issues, Check post at http://forum.xda-developers.com/showthread.php?p=22350827
Credits to BluechipJ
zorbakun said:
Hello All,
Does anyone know where to get ADB Drivers for new Sony Xperia Tablet S?!
Also can any of the current owners confirm if they can charge their tablets through USB cable connected to the PC?
Click to expand...
Click to collapse
According to Sony the tablet will not charge from a computer:
http://esupport.sony.com/docs/tablet/helpguide_sgpt2_3/US/contents/02/10/02/02.html#l1_connecting to a computer
Hi, when i try to install the ADB drivers, I find my tablet in the device manager, as a portable device under the name SGPT12 in stead of Sony tablet. Also when i want to upgrade the driver. It just gives me some options for MTP-drivers. When I say I want to browse for driver, I can select the ADB-file, but then it says it is not compatible with Windows x64...
Do you know any solution for this?
(I tried it with other USB devices and they can all get the ADB driver, but only my tablet does refuse it )
It seemed to have solved itself:good:
Bricked Tablet S after erroneous installed TWRP 2.6
Hello zorbakun and condi,
all is now alright! No brick at all thank god
Related
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
But when I reboot my tablet as USB mode and from my laptop I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
I have already unlock and rooted my tablet.
Why I can't see my device id ? Please help
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yeah this process is correct. Even I've experienced this.
What I did is:
Removed the USB cable connection and reconnect.
Kill adb.exe
Restart adb.
Then device was shown to be connected.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yes, I did that but still the same. Any other suggestions?
If on windows make sure your driver's are installed.
Type in cmd
adb kill-server
adb start-server
If that doesn't work try a different usb slot. You could also try moving adb and it's dependencies to your system32 folder. It's where all your commands are stored for cmd. You won't have to navigate to the android sdk tools.
Sent from my SPH-L710 using Tapatalk 2
Have you enabled Debugging on in your phones Developer settings?
ngaisteve1 said:
Yes, I did that but still the same. Any other suggestions?
Click to expand...
Click to collapse
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
no need for that.
close any adb process either from task manager or by typing: "adb kill-server" in adb console
close everything and use this customized adb file I attached, it'll show your device.
it also has instructions and necessary files for rooting your device.
Problem
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
I have LG Optimus G (E975) i wipped all from the device and now i can't put cm11 on it, adb sideload do not work, and list of devices attached is empty. what must i do to put CM11 on my phone?:crying:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
I have the same issue on my nexus 4. Yesterday it showed up with adb devices, now it's an empty list. I have USB debugging enabled and tried restarting the server. Nothing works. Any ideas?
ldemon360 said:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
Click to expand...
Click to collapse
unplug the device and adb kill-server then replug the device and try
turn debugging off and then on again
I had the same problem. In my case, i had forgot to enable usb debugging after new rom.
ngaisteve1 said:
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
Click to expand...
Click to collapse
In your case just disable USB debugging and then enable again.
fix the driver
I had this issue.
In my case when I went to device manager I could see the Device and wasn't installed correctly and could not load the drivers even after having installed them on the PC.
SO I clicked update drivers.
Select that will chose the drivers to install and select the Android Devices - ADB driver.
You will get a warning, but just ignore it and load the ADB driver for the phone.
Ensure you are in the sideload option of the recovery
Now
adb devices
it should show up as Sideload
Now sideload
Cheers
Dirk
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Thanks, this worked for me.
Just add ur device id in adb.ini
Same issue was faced by me on my micromax Q334 and xolo era, I search lot for that and finally just adding hardware id the device are detected under adb.The steps are clearly shown in my video below..
It will definitely going to sort this problem..
For that just right click on adb driver ,navigate to detail tab and search for hardware id then add to adb.INI
I have also uploaded video on that YouTube: Fix adb connection issue(Adb driver installed, but device not listed)
device listed as "? recovery"
hey,
am trying to connect honor 6(h60-L04) but am not able to see the proper name for my device is just showing "? recovery" and am trying to update the android version coz of the device is in reboot-loop so help me out here
if there is any other option to recover device give me link.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
not work my friend, the list of devices is empty
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.
vern.zimm said:
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
Click to expand...
Click to collapse
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.
I can't update my Nexus 9 because Windows 7 is not detecting my Nexus 9 during recovery mode. In non-recovery/normal mode Windows easily detects it as an "Android Device" -> "Android Composite ADB Interface".
I already tried:
-Using a different USB cable
-Uninstalling and reinstalling during recovery mode from Device Manager
-Installing latest driver from Google
Keep seeing "Error: Device not found" when I try to sideload 5.1.1 zip during recovery mode and an exclamation point next to "Nexus 9" in my Device Manager (No longer "Android Device" -> "Android Composite ADB Interface"".
Any ideas what I can try to do?
livinginavacuum said:
I can't update my Nexus 9 because Windows 7 is not detecting my Nexus 9 during recovery mode. In non-recovery/normal mode Windows easily detects it as an "Android Device" -> "Android Composite ADB Interface".
I already tried:
-Using a different USB cable
-Uninstalling and reinstalling during recovery mode from Device Manager
-Installing latest driver from Google
Keep seeing "Error: Device not found" when I try to sideload 5.1.1 zip during recovery mode and an exclamation point next to "Nexus 9" in my Device Manager (No longer "Android Device" -> "Android Composite ADB Interface"".
Any ideas what I can try to do?
Click to expand...
Click to collapse
What command are you typing?
cam30era said:
What command are you typing?
Click to expand...
Click to collapse
Typing the commands described here:
http://www.droidviews.com/manually-install-lollipop-5-1-1-ota-update-on-nexus-9/
livinginavacuum said:
Typing the commands described here:
http://www.droidviews.com/manually-install-lollipop-5-1-1-ota-update-on-nexus-9/
Click to expand...
Click to collapse
When you are in Recovery mode, hold Power button plus press and release volume up. This will get you into recovery menu where you can select sideload update via ADB. Then unplug your USB cable and plug it back in. Now your PC should recognize your device.
cam30era said:
When you are in Recovery mode, hold Power button plus press and release volume up. This will get you into recovery menu where you can select sideload update via ADB. Then unplug your USB cable and plug it back in. Now your PC should recognize your device.
Click to expand...
Click to collapse
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
livinginavacuum said:
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
Click to expand...
Click to collapse
You might try rebooting your PC.
livinginavacuum said:
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
Click to expand...
Click to collapse
Have you enabled USB debugging?
Usually means you don't have the drivers for the device.
If your device doesn't show up when you execute "adb devices", then it won't follow any commands.
http://developer.android.com/sdk/win-usb.html
Download that, and rclick the device with the exclamation, and point it to the android_winusb.inf when selecting the choose my own path.
After that, adb commands should work.
Alternatively, download the Nexus Root Toolkit, and go through the full driver installation.
That toolkit will make you clear all existing google drivers, and give you a fresh Nexus specific set of drivers.
AjunNg said:
Have you enabled USB debugging?
Usually means you don't have the drivers for the device.
If your device doesn't show up when you execute "adb devices", then it won't follow any commands.
http://developer.android.com/sdk/win-usb.html
Download that, and rclick the device with the exclamation, and point it to the android_winusb.inf when selecting the choose my own path.
After that, adb commands should work.
Alternatively, download the Nexus Root Toolkit, and go through the full driver installation.
That toolkit will make you clear all existing google drivers, and give you a fresh Nexus specific set of drivers.
Click to expand...
Click to collapse
I tried upgrading the driver to the android_winusb.inf path (from the same link as you provided).
Where can I download the Nexus Root Toolkit?
And wouldn't this still give me the same driver as from this link: http://developer.android.com/sdk/win-usb.html
livinginavacuum said:
Where can I download the Nexus Root Toolkit?
Click to expand...
Click to collapse
Anyone?
AjunNg said:
Have you enabled USB debugging?
.
Click to expand...
Click to collapse
Don't need USB debugging enabled to use ADB when in recovery.
livinginavacuum said:
Anyone?
Click to expand...
Click to collapse
http://bfy.tw/EcS
Hello guys, I tried a number of different methods to install VCOM drivers on windows 10, however when I connect the phone while being turned off, the pc pops a message saying the device could not be recognized and the display of the phone itself turns on showing the battery indicator for charging. Has anyone experienced this? I was not able to anything about it. Thanks
i have the same problem. Every time i want to flash something, i have to rescue my old windows XP laptop XD
Here is video tutorial.
Or manual from Elephone forum
1. Start device manager by pressing Windows key+x, select device manager from the list
2. You should see a device on the list with yellow exclamation sign, right-click that and select "update driver software..."
3. Select "browse my computer for driver software"
4. Select "Let me pick from a list of device drivers on my computer"
5. You get a long list of possible devices, I think you can select either "Android phone" or "Universal serial bus devices". Whichever you choose, you need to select "MTP USB Device" from the second screen's list of drivers.
After that the device should be recognized normally by Windows, but you still might need to change the USB setting within the phone from "charging only" to "transfer files".
sur. said:
Here is video tutorial.
Or manual from Elephone forum
1. Start device manager by pressing Windows key+x, select device manager from the list
2. You should see a device on the list with yellow exclamation sign, right-click that and select "update driver software..."
3. Select "browse my computer for driver software"
4. Select "Let me pick from a list of device drivers on my computer"
5. You get a long list of possible devices, I think you can select either "Android phone" or "Universal serial bus devices". Whichever you choose, you need to select "MTP USB Device" from the second screen's list of drivers.
After that the device should be recognized normally by Windows, but you still might need to change the USB setting within the phone from "charging only" to "transfer files".
Click to expand...
Click to collapse
Thank you for your answer, however my problem doesn't concern the MTP drivers but vcom ones..I get this error
"Unknown USB device. The last usb device connected to the PC does not work and it is unknown"..
In this case look at here.
Hope you will find solution
Had the same problem with my P9000 and newest firmware. Forget the usb-failure message after installed drivers.
Have to power off the P9000 and additionally press Power and Vol+ while connecting to USB. Then P9000 is recognized by SPFT.
PAPPL said:
Had the same problem with my P9000 and newest firmware. Forget the usb-failure message after installed drivers.
Have to power off the P9000 and additionally press Power and Vol+ while connecting to USB. Then P9000 is recognized by SPFT.
Click to expand...
Click to collapse
Thanks I'll try that today. What you mean is to go into recovery then?
Seems like newer P9000 need Power & Vol+ when plugging USB in to get SPFT (Download) to recognize the device to flash a custom recovery (= get red bar in SPFT).
Only powering off is not enough.
To enter custom Recovery (TWRP) after flashing it you need to press Power & Vol+ when powered off.
Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
opg2000 said:
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
Click to expand...
Click to collapse
No sadly not, with the second device I could hear it connect and show correctly. The problem phone shows in adb and edl but not fastboot
Knoppersd said:
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
Click to expand...
Click to collapse
I got the same issue but by installing the above driver and changing the new type-C cable.... helped me and solved my problem......
Knoppersd said:
Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
Click to expand...
Click to collapse
have yu got the solution of this because I am also facing the same issue.
No sorry, the phone is still dead and i moved on from it.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
Managed to connect my Redmi Note 9 (merlin) to Fastboot with my Windows PC and install stock ROM with MiFlash thanks to this driver.
To install the driver i did:
1. Download driver from link above (ignored Firefox's warning of potential risk).
2. Unpack the rar file.
Now we must disable Windows Driver Signature for the driver to install correctly. It will only be disabled during a single boot and the automatically revert to active and secure again after reboot.
3. Restart Windows while holding the "Shift" key through Start Menu -> Power ->Restart.
4. The blue Windows Advanced Boot menu should appear. Select: "Troubleshoot" -> "Advanced Options" -> "Startup Settings" -> "Restart"
5. Computer will restart to the Startup Settings Menu. Press number "7" key on your keyboard to select "Disable driver signature enforcement". Windows then will boot to Desktop.
6. Search and open "Device Manger" on Windows menu.
7. Under "Other devices" right click "Android" (for me it appeared with a caution sign because of the default driver error) and then "Update driver".
8. Browse my computer for Drivers -> "Let me pick from a list..." -> Select "ADB Interface" (not sure if it is important which type of device is selected) -> "Have Disk".
9. Browse the downloaded driver folder that was unpacked on step 2 and select "android_winusb.inf" (this is the Windows driver).
10. On the Windows Security prompt select "Install this driver anyway".
From here on Fastboot mode should be recognized by the PC and you can install a ROM using MiFlash or following any other guide to install via Fastboot in this forum.
Hi,
My Nord 2 have latest update DN2103_11_A.17, and I wanted to enable VoLTE.
My computer can't detect my phone in ADB when in recovery mode, it detects only when just powered on normaly and connected.
I have latest Android plateform tools installed on computer.
Any Idea of what's wrong ?
Thanks
Adb drivers and permissions.
Try in Linux, easier
I have exactly the same problem on my OneNeplus Nord 2. I installed the MediaTek_Preloader_USB_VCOM_Drivers drivers in auto mode and even in manual mode under Windows 10. When I type adb reboot recovery the smartphone reboots in recovery mode even if it tells me seems strange see photo (sorry very small text...) but then no other orders are accepted. Same problem in bootloader mode. So I can't unlock the bootloader. Any help is welcome...
Hey I had the same issue with fastboot device not showing up. Fastboot with other devices on my PC had never been an issue.
This Fixed it for me:
Open "Device Manager" from the Windows start menu.
Your device should be listed there as "Android Device" (with a yellow indication for missing driver)
Right click the device and select "Update Driver".
Click Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
From the list select "Android Bootloader Interface". It is possible that you need to deselect the "Show compatible hardware" button.
Good luck.
cukierkas said:
Adb drivers and permissions.
Try in Linux, easier
Click to expand...
Click to collapse
Hi, thanks I'll try. Any specific driver for Linux?
I've read that adb in recovery mode doesn't work since A.14 update, and I'm on A.17. Anyone Can confirm that?