Bloody Hell i still cant get work any usb connection from my Kaiser to my PC.. Im using W7 x64.. i think its biggest problem (x64)
and please, any manual how to get work ADB commands? step-by-step for newbies
I listed this problem to the issues list:
http://forum.xda-developers.com/showthread.php?t=748717
I have not been able to use ADB since Donut or so!
SuperJMN said:
I listed this problem to the issues list:
http://forum.xda-developers.com/showthread.php?t=748717
I have not been able to use ADB since Donut or so!
Click to expand...
Click to collapse
sry but you have ther only polaris.. add there kaiser please too
There are no windows drivers AFAIK, that's why it won't work...
I read somewhere about someone being able to do it on Ubuntu. I'm not sure about it though. I removed Ubuntu from my laptop couple of months ago and can't test ADB now.
I tried a lot with Win 7 32bit - for about a week, but no luck
If you want to copy files, just remove the SD card and use a card reader. Or you can enable recovery mode then the card will be readable in windows.
i have better think than remove SDCard.. i have FTP Server on my phone, and im connecting on it through Wi-Fi. Its pretty fast
And i have access on full /
on /system + sdcard
its faster than hacking through terminal
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
Having lost my XPERIA Arc S recently, the insurance company kindly sent me a replacement handset (as they do). The only problem was that the replacement wasn't an Arc S but an XPERIA S.
There I was for a minute thinking I had hit the jackpot and received a better handset only to encounter the PC connection issues experienced by so many others with this phone.
The phone I received: stock XPERIA S, not rooted, running Android 4.1.2 (build 6.2.B.0.200).
Shock, shock, horror, horror, shock, shock, horror you know the song
Nevertheless, being stubborn in nature, I kept trying to find a solution to the issue and started re-installing drivers, software, switching off firewalls, activating USB Debugging, etc ... everything I read about in other posts but alas, all to no avail.
Then I stumbled upon something strange, namely that when I selected the option:
"Settings" -> "Xperia" -> "USB Connectivity" -> "Install PC Companion"
two (2) drives mounted on my Windows 7 system:
Code:
1. (D:) Sony PC Software
2. [XPERIA S
Note: Developer Options, WiFi, Bluetooth, NFC and Screen Lock were all OFF for this to work. Mobile Data was ON.
Forgive me that I am unable to provide you with further information and/or an explanation.
My coding knowledge and experience = 1/10; My stubbornness knowledge and experience = 9/10
It would be good if someone could be so kind to investigate and explain.
If you're in a similar position perhaps this method may work for you (please hit the "Thanks" button if that's the case)
P.S. Have tested this in Linux Mint "Maya" but nothing ... don't know about other distros or Macintosh.
Normally you plug and it mount as portable media in PC. Perhaps try in Windows.
xminirom said:
Normally you plug and it mount as portable media in PC. Perhaps try in Windows.
Click to expand...
Click to collapse
Thanks for your reply xminirom.
If only it behaved normally xminirom, I would never have posted this thread :laugh: Perhaps it's worth noting that this method only worked in Windows 7 not Linux Mint.
Update: Have also tested this method in Windows XP and worked just like in Windows 7.
Will be testing if the same applies to Windows 8 and perhaps even in some other Linux distros. Perhaps it's worth saying that when it comes to Linux, I have followed every step of Lloir's guide on setting up MTP in Linux without any luck ... perhaps I ought to try with Android SDK installed come to think of it
Sorry but I don't have access to a Mac (and have no intention of having access to a Mac ... no offence meant by saying I'm not a fan of Apple)
prime-mass said:
Having lost my XPERIA Arc S recently, the insurance company kindly sent me a replacement handset (as they do). The only problem was that the replacement wasn't an Arc S but an XPERIA S.
There I was for a minute thinking I had hit the jackpot and received a better handset only to encounter the PC connection issues experienced by so many others with this phone.
The phone I received: stock XPERIA S, not rooted, running Android 4.1.2 (build 6.2.B.0.200).
Shock, shock, horror, horror, shock, shock, horror you know the song
Nevertheless, being stubborn in nature, I kept trying to find a solution to the issue and started re-installing drivers, software, switching off firewalls, activating USB Debugging, etc ... everything I read about in other posts but alas, all to no avail.
Then I stumbled upon something strange, namely that when I selected the option:
"Settings" -> "Xperia" -> "USB Connectivity" -> "Install PC Companion"
two (2) drives mounted on my Windows 7 system:
Code:
1. (D:) Sony PC Software
2. XPERIA S
Note: Developer Options, WiFi, Bluetooth, NFC and Screen Lock were all OFF for this to work. Mobile Data was ON.
Forgive me that I am unable to provide you with further information and/or an explanation.
My coding knowledge and experience = 1/10; My stubbornness knowledge and experience = 9/10
It would be good if someone could be so kind to investigate and explain.
If you're in a similar position perhaps this method may work for you (please hit the "Thanks" button if that's the case)
P.S. Have tested this in Linux Mint "Maya" but nothing ... don't know about other distros or Macintosh.
Click to expand...
Click to collapse
1- the phone has an installer package for the software PC Companion, setup to run when the phone is plugged in to a computer. It acts like a software installer CD-ROM being inserted into the PC.
when you first plug the phone into a PC, your phone should ask you if you want to install PC companion. It also gives the option to never ask to install again.
I would say that "1. (D Sony PC Software" is being reported like a separate partition of the onboard SD card. Using a root explorer, you should be able to find the install file and delete it (I always delete it just for the space). Deleting it should remove this entry.
2- The entry "2. XPERIA S" will be the SD card mounted in MTP mode. If you have USB Debugging selected you should get MSC mode for the card (thats how it works on my ION)
The good news is that you really did get a better handset
Toledo_JAB said:
1- the phone has an installer package for the software PC Companion, setup to run when the phone is plugged in to a computer. It acts like a software installer CD-ROM being inserted into the PC.
when you first plug the phone into a PC, your phone should ask you if you want to install PC companion. It also gives the option to never ask to install again.
I would say that "1. (D Sony PC Software" is being reported like a separate partition of the onboard SD card. Using a root explorer, you should be able to find the install file and delete it (I always delete it just for the space). Deleting it should remove this entry.
2- The entry "2. XPERIA S" will be the SD card mounted in MTP mode. If you have USB Debugging selected you should get MSC mode for the card (thats how it works on my ION)
Click to expand...
Click to collapse
Thanks for this Toledo_JAB. Although I didn't really need an explanation of how the process of mounting works, you're not a mind reader so I will try and be a bit more descriptive.
The problem is: device will not automatically mount when connected to a PC using a data cable, unlike my Xperia Arc S which mounts as soon as the cable is connected and is recognised as a phone (giving me access to the memory card and system when connected in MTP mode and only access to the memory card when connected in MSC mode). Have tried on several PC's now and it just won't connect when you plug it in. Initially I suspected it's Windows 7 causing the problem, so connected to a machine running Linux Mint Maya, another machine running Windows XP, yet another machine running Windows 7, and another machine running Windows Vista and finally last night another machine running Windows 8 Pro. The phone refuses to connect automatically to any PC running Linux Mint Maya, Windows XP, Vista, 7 and 8. Since it cannot connect to any PC as it normally should, I can't use the "Repair Phone" option using Sony's PC Companion to possibly repair the problem.
It's worth noting that the XPERIA S does not have a memory card slot (due to integrated storage), and therefore I couldn't just load a Stock ROM and install it from the memory card as I was able to do with my Arc S when it became unresponsive some time ago.
Having Googled my problem, I found from other posts (in this forum) and other forums that the XPERIA S and XPERIA Z are known for this problem and various solutions are suggested. However, not one of those solutions actually helped me and my XPERIA S just refuses to connect to a PC even with USB Debugging selected (MSC for the memory card doesn't even come up).
The XPERIA S I have only connects to a machines running Windows when the "Install PC Companion" option is selected. This is it: there is no other way to connect it to a PC. Furthermore, the conditions in my first post need to be met in order for this to work (various functions turned ON and others turned OFF).
It seems that nobody else has come across such behaviour or if they have, then they haven't shared it with the world, and it is this very behaviour I have found strange and couldn't understand/explain/find logic in. Hoping that someone could provide a logical explanation as why the phone behaves in such a way and only connecting to a PC under such conditions (see my first post).
Update: Since the first post, I have downloaded Flashtool by Bin4ry in the hope of creating a memory dump and/or back up of the installed ROM later today to help someone understand/explain why this particular XPERIA S refuses to connect to a computer in any other way than when the "Install PC Companion" option is selected.
Hopefully I am making sense this time and not confusing everyone again
Thanks again for all your replies people
To much info is better than to Little
Have you tried to reinstall PC companion and flashtool drivers?
For flashtool drivers I always just install all of them.
Moderating from my Xperia ION on 4.1.2 & RooTED by DooMLoRD, using XDA Premium mobile app v4
You can find the drivers in Flashtool's DRIVERS folder.
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 guys.
I have a Humax 2din car multimedia that seems it has linux os on it. there is only one usb port for this device, no sd card. it's locked and I want to unlock it to access terminal to do some stuff on it. I can attach keyboard and mouse to device via usb port and only Windows+R works! it rotates screen by 90 degree. no more action.
Why do I think it's based on Linux os?
because the Navigation software is polnav6 and when I wanted to upgrade it, upgrade files are like linux files. some .sh files and some other folders.
So, any idea about how I can unlock the device will be appreciated.