Has anybody gotten the Sony's official usb drivers to work? Its somewhat mandatory for xperifix et all.
I tried it on 2 completely different machines.
On win7 x64 box the driver complains about Error 10 - This device cannot start.
On a win10 enterprise thinkpad the error is similar:
"This device cannot start. (Code 10)
The specified request is not a valid operation for the target device."
I am starting to suspect that the drivers are faulty. FWIW the thinkpad has NEVER seen *ANY* adb/android/sony drivers before.
This is the "Sony sa0118 ADB Interface Driver" btw. Installed as a legacy device as per Sony's instructions. Driver is already not working before a device is connected. Device is subsequently also not recognized. Device works perfectly fine in flash mode on my Linux notebook, just not both windows boxes Ive tried (sadly Windows is required for Xperifix)
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
juandiazmora said:
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
Click to expand...
Click to collapse
tried these and they got me a little further - but not very. On first connect of the xz2c in "blue" mode Windows said something along the lines of configuring new device: Android. So far so good. Then started xperifix, which found the device and started to get device information during which it crashed (program got stuck, no .NET exceptions or anything). Now even 2 reboots later the phone is no longer recognized, I assume xperifix somehow borked up the fastboot drivers?
PS: the constant more often than not non-working recaptchas are getting a little annoying..
The drivers have to be installed in testmode on Windows 8-10. In Windows 7 it should work "out-of-the-box". And yes, I know I'm answering to one year old question, but it could be helpfull to someone one day. Maybe.
Related
Hey guys, I have been trying to get Windows 7 Drivers to work properly with adb on my A100. I have a Virtual Machine of Windows 7 and I have manually added the USB device ID's to the VBox settings for the VM client, Windows 7 sees the device ok and will mount the device fine via MTP. I can even get the drivers to say that they are working properly for the device, but when it all comes down to it they aren't.
I have tried using the ADB driver from the Android SDK which of course won't work out of the box since the device ID's aren't made for the Iconia A100, however I modified them to match the vendor/device IDs, but still - no go. I can do ' adb devices' and it will either show the device as offline or will just say the name and serial#, but when I try to connect it either says 'device offline' or it will give me a adb protocol error.
I don't know what else to really try, and at this point I am really thinking Virtualbox isn't passing the USB properly to the Guest OS, but what is odd, is my HTC WildFire S will work fine with adb (same binary).
I have also tried the Acer drivers that are available on the Acer Website, as well as a few other device drivers that I can't recall off the top of my head.
I guess some people are wondering if this is working in Linux why am I so concerned about getting it to work in a Virtual Machine running Windows. In short the answer is: I am developing kernels and recovery for the A100 as many may already know, and I am working on some automated installers that are cross platform compatible and I need to test the Windows side of things before I make releases, yet it's a bit hard to do when Windows is such a PITA when it comes to anything Android.. Yea, I'm a Linux person I know it's obvious - but I need this working somehow in a Virtual Machine because I'm not willing to do a native install of Windows on any of my machines, simple as that lol..
Anyone who may have a Virtualbox install of Windows 7 (or vista) that has adb working with their A100, please let me know the adb drivers you used and if at all possible attach them here, or give me a direct link. I greatly appreciate the help guys!
Here is a snippet of the troubles:
Code:
List of devices attached
037c624643a033d7 device
C:\Users\Lance\Downloads\godmachine81-Acer-A100-TWRP-Installer\godmachine81-Acer
-A100-TWRP-Installer-c8ccd42>adb shell
error: protocol fault (status 72 6f 6f 74?!)
**Edit: I kinda found a solution to my own problem, but not a great one. The problem was with EHCI 2.0 in VirtualBox, when this setting is disabled it will allow adb to work correctly, however on Windows 7 it will break the USB host so there is no possible way to use the tablet period, with Windows XP however it works fine. Windows XP has the exact same issue, but the USB Hub will actually work without EHCI 2.0, not really sure if there is a workaround to the Windows 7 problem, but I didn't really mess with it long - I'd say one might be able to uninstall the USB adapter and reinstall it after disabling EHCI and then also reinstall the Acer drivers. I got tired of fooling with windows 7 and just installed a copy of XP, wrote the batch script for windows, and will soon be uninstalling most likely haha.. Hope this might be some good info for others who run into a similar issue
I have an HTC Incredible 4G LTE. I underwent the process detailed here to unlock the bootloader.
When i got the HTCDev website, i ran a fastboot command and it just says <waiting for device>. I tried to detect the device with adb devices, and fastboot devices, but with no success. the THC Sync manager is not installed. HTC drivers should be installed. I am plugged into a USB 2.0 port, the same one used through out the process (i even tried the other one).
I am at a loss as to what is happening. I do know that the device manager sees my phone, and shows the drivers as the latest version. It does give this message:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
The device manager is listing the driver as version 2.0.7.3.
EDIT: Was able to get driver updated to 2.0.7.18
Also, when connected to the computer normally an orange light shows near the speaker. I wasn't concerned at first as I know the Android OS is not actually up and running on the phone, but do wonder if it doesn't indicated a problem.
Another note, I am running Windows 8.
EDIT 2: More research has yielded the following "Android Bootloader Interface". Every reference installing this from the usb_driver in the ../extra/google/usb_driver folder. When I attempt to do so from the device manager Have Disk ui I receive the following error
The folder you specified doesn't contain a compatible software driver for your
device. If the folder contains a driver, make sure it is designer to work with
Windows for x64-based systems.
Click to expand...
Click to collapse
EDIT 3: Removed entire android sdk, redownloaded and installed. Removed all HTC software and drivers. Booted phone into fastboot, and windows detected an "Android 1.0" device, installed the Android Bootloader Interface driver from the google usb_driver successfully. However, fastboot devices still does not detect the phone, and device manager still shows code 10.
As of now:
No HTC Sync, or HTC Driver
phone booted into fastboot, phone displays "FASTBOOT USB"
phone is set to usb debug
phone is connected to pc with good cable to a usb 2.0 port
I have:
rebooted pc, re-installed drivers, changed usb cords, changed usb ports, even tried a usb 3.0 port, i have tried some generic fixes for code 10 errors, and completely run out of ideas
EDIT 4: After using a different computer running Windows 7 I was able to complete the process, however, i would very much like toresolve the issue with my own PC, as the Win7 laptop is not mine. I utilized the adb/fastboot/winapi files from my Win8 machine. Win7 automatically found HTC drivers (2.0.7.18) and everything seemed to work just fine. Any ideas?
Hi There,
HTC ONE M8 Usb is not recognized under windows 7 64-bit enterprise.
tried drivers from HTC sync and tried stand alone drivers.
On a different pc 32bit running windows ultimate it works immidiatly as well as on a VMWARE machine.
any advice please?
Thank you!!!
anyone?!
The latest version of HTC sync drivers should work. However you will have problems with 3rd party drivers on 64bit systems as they are generally not signed and Windows 64 bit will not allow use of these drivers unless you disabled driver signing enforcement
http://sabrent.com/support/knowledgebase.php?article=14
unfortunatly that didnt do any change.
whatever i do windows does not except the driver. I plug in the phone and immidatly it shows with a exclamation mark in the device manager.
tried different ports and different cable, i uninstalled any previous smartphone drivers and software, although it works just fine with another computer running windows 7 (32bit).
any hint on how to troubleshoot?
thank you!!
Solved!
solved by using 3rd party software (wierrrd)
1. install moborobo http://www.moborobo.com/
2. plug the phone with "Usb debugging" ON
3. Accept the "not signed" driver warning
4. It will now automatically install the driver succesfully after which you can uninstall moborobo and the drivers will still work
credit to QUBiCA http://forum.xda-developers.com/showthread.php?t=2416223&page=4
Thanks
xwireless said:
unfortunatly that didnt do any change.
whatever i do windows does not except the driver. I plug in the phone and immidatly it shows with a exclamation mark in the device manager.
tried different ports and different cable, i uninstalled any previous smartphone drivers and software, although it works just fine with another computer running windows 7 (32bit).
any hint on how to troubleshoot?
thank you!!
Click to expand...
Click to collapse
Worked fine for me when I installed it on my work laptop running the same version of Win 7. I've got admin rights but explicitly ran the downloaded file as administrator and once I had connection confirmed, I deleted the synch manager portion of the installation (hey, great idea - let's make people download and install 130Meg of files just to get Windows device drivers... NOT)
i actually found another way to work with this...
search google for windows xp mode. it will take you to the microsoft website and it will download a pc virtualizer with xp built in. the software is windows xp 32 bit. i just unlocked my bootloader using this and it works great
Hi All,
I have been unable to get my oppo n1 (CM edition) to connect to my home PC (win8 x64). This is annoying as my work PC (also win8 x64) detected and interacts fine with the MTP end point on the phone when connected via USB cable.
Could someone take a look at their drivers when their phone is connected and if possible zip them up for me? i would grab the ones from my work place but it just when friday afternoon and i cant believe this is such a hassle for me.
for the record, my home system currently detects the oppo as USB\VID_22D9&PID_2764\58E10EA
all the other drivers i have found are either for the ADB end point or some other PID.
no, secure boot is too much hassle as wrangling inf files can wait till monday i guess.
TIA to anyone that responds.
ms_comp_mtp
welp i think i have traced this down to a strange fault in just my own PC.
tested my oppo on a win7-x64 machine - installs fine.
I am comparing the setupapi logs to see any divergences and have found one.
my win8 box windows is not "seeing" the usb\ms_comp_mtp "compatible ID" (this is the magic that allows one driver to match many different VID/PIDs, thus a generic MTP driver should work for anything that advertises it self as MTP).
Now for the hard question of why that isnt being sent/seen by my box...
also to add to the mystery - PTP mode works fine, just MTP gives me grief.
While my own journey is far from over, ive learnt the C:\windows\inf\setupapi.dev.log file is quite useful for assisting in figuring out what isnt working when it comes to device driver installations.
I am happy to have a mod close this off, given this problem appears isolated to just my machine.
Hi all,
I purchased a gemini wifi recently, but a 4g version arrived! I'm now trying to flash Linux on there, but I cannot get the flash tool to do anything.
I'm pretty sure that this is a driver issue, but I'm not sure what to do about it. I've tried windows 11 and 10, as well as ubuntu 20.04 to flash this thing and nothing is working.
On the windows 11 host I even disabled memory protection to allow the drivers to work correctly, but that made no difference.
Following the guides on planet computer, it's not clear what state the device should be in, but I've tried normally booted into android as well as in recovery mode (booted with Esc and side button depressed on boot}
What am I missing here? Does flashing this device just no longer work?
Thanks in advance for your help!
it still works presuming you are referring to this guide: https://support.planetcom.co.uk/index.php/Linux_Flashing_Guide
I unfortunately don't think I am able to help you debug the situation from the information you provided.
I am not sure where most of the users congregate, but I have seen some sporadic recent activity here: https://www.oesf.org/forum/index.php?board=192.0
From my own experience, windows 7 and windows 10 have worked flawlessly, ubuntu worked for me in the past, but had trouble recently. win7 and win10 in virtualbox requires delicate usb device setup adding device during gemini reboot, and still gives some trouble.
I haven seen any updates or security patches from planet on neither android nor debian, so got myself a sailfish X license to support their development, it looks like a lot of updates (most recently yesterday: https://forum.sailfishos.org/t/release-notes-vanha-rauma-4-4-0-72/ )
good luck