Related
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
Hi everybody,
I've been searching on forums, tried multiple solutions but nothing helps. Though I'm familiar with all this, I'm just stuck on one point which makes all this unlocking process very frustrating. My phone is a Xperia P (JB) and I went to Sony's dev page in order to unlock the bootloader. Unfortunately, even if my phone is eligible for unlocking, I just cannot pass one of the point: fastboot mode.
Basically, when I power on, vol up, fastboot mode is enabled for a few seconds only (led) then disconnects from my device manager and stays with an amber (orange) led on. I just can't have my phone stay in fastboot mode. Same if I go with the command line adb reboot bootloader...
After looking for this problem on various forums, I've tried to update the drivers to (S1 fastboot) found on multiple posts, didn't help. I thought it was a problem with my PC (Win 7_64) so I tried with a fresh install in 32bits on another disk, didn't help. Tried even with Win 8 64 and 32, no chance... USB debbuging is on.
Is anyone experiencing the same problem or has anyone a solution for this? I'm just getting mad by not being able to unlock it.
Hi! I think that the driver is not properly installed! Another site I found this description to see if it helps!
Install Sony Xperia (P / U / Sola / Go) Driver and fastboot in Windows 7
Sony Xperia Driver Installation
Go to Setting > Development
Check USB Debugging
connect Xperia (P / U / Sola / Go) to PC / laptop
Open device manager
Right Click on SEMC HUSB (it should have a yellow triangle warning)
Then select “Update driver software”
Choose “Browse My computer for driver software”
Choose “let me pick from list of device driver on my computer”
Click “have disk” button
Browse to Xperia_P_Xperia_U_Xperia_sola_drivers extract folder
Select sa0104adb.inf
Approve all confirmation
Click OK
Sony Xperia Fastboot Installation
Turn off Xperia
Open Windows 7 device manager
Press and hold Volume[+] Sony Xperia button
Connect to Pc / Laptop
Right click on yellow triangle warning (device warning)
Choose “Update driver software”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list of device driver on my computer”
click “Have a disk” button
Browse to fastboot driver extract folder
Select android_winusb.inf
Approve all confirmation
Done
Note:
A sign that fastboot connection is success is LED will stay in purple
In fastboot installation, open device manager before connect the device is a trick. A yellow triangle (device warning) only appears around 5 sec
It`s better to restart the windows after driver and fastboot installation
Download Support Files
Download Sony Xperia (P / U / Sola / Go) Driver
Download Sony Xperia Fastboot driver
Hi Rajen,
Thanks for your help... I've done all this before, repeated it now step by step but no luck... Cannot have my P to stay with purple light on (fastboot). It still stays purple for 3-4 seconds then amber.
Any other idea?
@swissman you should open device manager on Windows 7 first then connect your phone......when its connected youll see anerror or something sign there and click it then choose install driver from pc......navigate to those drivers and Finish....hope this helped....
Sent from Space!
Hi! Thank you... I really did that... I think almost 20 times but nothing helps. I think I've done almost everything possible (Imagine, thinking that it might be a 64bits issue and Win 7, I've even tried to downgrade to Win 7 32 and Win 8 32! ..
But nothing helps. It installs correctly the drivers, computer reboot (or even not), replug the phone with Vol up and still getting a 3-4 seconds purple LED and then disconnection. I'm getting mad as I tried almost everything I found on XDA or others but nothing helps.
The only thing I haven't tried yet is to downgrade to ICS, try to unlock the bootloader and upgrade back to JB
Ok, I finally have been able to unlock it. What I did, VM with Windows 7 64, booted in fastboot and updated drivers with "Android ADB Interface" drivers from Google directly (not the one provided with SE modifications)... My phone stays now in fastboot and has been successfully unlocked.
Don't ask me how it did happen, I'm just being happy to have it fully under my control
Anyway thanks guys for your help!
When the purple led doesn't last it means you haven't installed it correctly......the thing we are teaching you is I think, a shortcut method,just in order not to install to many files.......so I recommend installing the whole android SDK if you have time......
Sent from Space!
Thats right good work
Sent from my ST27i using xda app-developers app
After browsing forums this what I found http://forum.xda-developers.com/showthread.php?p=23794050.........that is the exact way that you should do....
Sent from Space!
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,
I've got a Point of View POV Mobii 7 Bussinessline PROtab2 ( TAB-7C-4GW-1 ) which is stuck on the bootscreen.
- it does not power off when I press "power" for >10s
- the reset switch on the back powers it off
- pressing "home" while powering on results in an update screen after ~5s (little green android with box and arrow next to it) which changes to recovery ~1s later (android with exclamation mark) where recovery menu can be entered/hidden by pressing "home"
- wipe cache or factory reset in recovery didn't help
- "reboot system now" in recovery actually powers device off
I've downloaded the latest firmware from http://81.21.136.56/downloads/Tablets/ 7 Inch Tablets/TAB-7C-4GW-1 Firmware Upgrade/ which I was able to flash few years ago...
I've installed Telechips VTC driver which is part of the download.
Connecting the device via USB results in four "Telechip s, Inc.M801_88 USB Device" beeing recognized by windows as mass storage (empty drives) and an unknown device "M801_88" where no driver can be found.
It is the same in recovery mode and after regular boot. A usb reconnect is done when the device switches from update to recovery mode, but device constellation keeps the same.
Telechips Update-Tool "FWDN V7" (also part of the download) does not see a device (it should show a popup when a device connects, I guess)...
I've tried manually assigning the VTC driver to the unknown device, but that doesn't work. The driver supplied is just an installer... I found inf-files on the system after installing it, but assigning them says that they aren't drivers. Also listing all systems drivers doesn't who a driver from Telechip to select...
I've tried it on Windows 10 and in a Windows XP VM with identical results...
Any ideas what to do?
Edit: I managed to assign a generic ADB driver to the unknown device. It lists as "0123456789ABCDEF device" and limited shell is available (recovery?)
The device is okay again. I really hate it when things aren't reproducible, but after performing a factory reset in the recovery once again, it booted just fine...
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.