Hi,
I just tried to setup the Arc as debug device, but it doesn't seem to work.
May app is declared "debuggable" (I already tested it on an LG Optimus Speed) and the "USB Debugging" option on my Arc is turned on.
I also did install the driver from here.
Now, if I connect the Phone with my PC (running Windows XP), it shows up in the connected hardware section as "Sony Ericsson sa0102 ADB Interface Driver" and my phone tells me it's "connected for USB-debugging".
However, I can't find it, not with "adb devices" nor with Eclipse > "run on target" option.
Has anyone got this working so far?
Kind regards,
cherryfish
Edit: maybe someone can move this to the developer forum, I can't post there yet.
install and reboot
After installing the special device driver you mentioned, installing the SE packs from the “SDK Manager” and rebooting the PC it worked.
But it put down SE even further down the line of potential next devices. So much unnecessary hassle.
Hi,
I should have come back to this thread...
My mistake actually was that I tried to do it the complicated way. What worked for me on more than one PC (Win 7, Win XP) later was:
- just plug in Xperia Arc via USB (debug mode turned on)
- wait (for the auto-install)
- happily see it working
Do I understand your post correctly that this didn't work for you?
Actually I was quite impressed how fluent and easy this was. I did the same procedure with an LG Optimus Speed and THAT was a hassle...!
Kind regards,
cherryfish
Related
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 everyone.
I was having a problem regarding usb debugging connection of the Xperia ZL C6502. I was using Win 7 64-bit. My problem is that under Device Manager, it shows C6502 (refer to attachment below). I uninstalled it and let it reinstalled, but still windows was unable to find ANY driver for it. I already installed the Google Drivers and ADB Universal drivers, even had Sony PC Companion installed to latest version (to date) too. Even that do not help as it was still unable to correct the problem. But strange thing is, when connected with usb debug off, it was working with proper driver installed, displaying as Xperia ZL in Device Manager. The same with Flashmode (SEMC Flash Device) and Fastboot mode (Android ADB Interface).
I was wondering if it could be the fault of my Windows system or that there is some solutions that I've overlook. Hope any devs or gurus could help me with this. I really need to solve this problem ASAP. Thanks in advance guys!
Edit:
[Device specs]
Sony Xperia ZL (C6502)
Android JB 4.2.2 | Firmware 10.3.A.0.423
Umm.. Anyone? I have searched high and low in the other threads even I tried Google, but still I can't seem to solve this problem. I've even brought myself into the solutions for Nexus devices, I tried the solutions but it seems that my problem is not solved. Oh please don't tell me I have to send it over to Sony
RE: xperia zl usb driver
I think that you have not done enough research...
anyways I got in the same problem today..
to solve the issue follow this steps:
1. download usb driver from this linkit is same for Z & ZL) [remove spaces it is not allowing me to post link]
h t t p : / / developer . sonymobile . com / downloads / drivers / xperia - z- driver /
2. unzip the drive file
3. right click on C6502 in device manager select update driver
4. n from that select file from my computer & select the driver folder...
5. go to eclipse -> window -> open perspective -> devices n check
Okay, I've did like you suggest, but Windows was unable to find any driver.
I've started up eclipse and do as you said, but (refer to attachment) I was unable to find the "devices".
What am I doing wrong? Arghh... I really need to root this phone, so that I can unlock the tracking feature or some security stuffs so that I can retrieve my phone when it got lost or stolen. Anyway, thanks for you help aks0020
re:ZL usb debugging
to see the devices you can also go to DDMS...
but first u need to install that driver successfully...
I suggest you to retry the driver installation keep phone connected with usb debugging & Allow mock location options on
After successful installation u should see new driver in device manager as shown in attached snaps....
Problem Solved, or so it seems..
Okay, stayed up whole night reinstalling a clean copy of Windows 7 64-bit, finally I am able to make Windows 7 recognize my Sony Xperia ZL (C6502) when connected in USB Debugging mode. Yup it is connected properly now, compared to earlier. Just a little patience and some determination
Apparently, I've followed aks0020's suggestion to turn on Mock Location as well, and perhaps having a 'clean' Windows 7 installation helped to correct this problem. Maybe earlier my Windows 7 has faulty drivers database
Anyway, problem is solved, I can finally root my Xperia ZL. And for those curious, can refer to the attachment below :victory:
Hi guys,
Not exactly a noob..
- got my new VK810 yesterday - JB 4.2.2;
- rooted with towelroot;
- installed SuperSU and BusyBox;
- declared myself a developer;
- checked USB debugging in the Developer options;
- installed the driver from LG website for VK810;
Now I connect it to my laptop, it is recognized immediately by the OS as VK810.
start command window, go to adb directory, run "adb devices" and..nothing.
If I connect my other android devices such as G3 etc they are recognized just fine.
What's wrong?
As a result, I cannot install TWRP.
I do not have this device but seem to remember reading that you need the verizon driver with the 810
muiriddin said:
I do not have this device but seem to remember reading that you need the verizon driver with the 810
Click to expand...
Click to collapse
I've installed LG driver for VK810...
Like I said, the tab is recognized in Windows as "Mobile device" VK810, not "Android" or phone.
ADB know nothing about it.
Tried on 3 different PCs, Win 8, Win 7 and even XP.
Maine_Coon said:
I've installed LG driver for VK810...
Like I said, the tab is recognized in Windows as "Mobile device" VK810, not "Android" or phone.
ADB know nothing about it.
Tried on 3 different PCs, Win 8, Win 7 and even XP.
Click to expand...
Click to collapse
Try going to settings/ pc connections/ select usb connection method/ internet connection and select ethernet. I believe thats what worked for me.
Sent from my GT-N5110 using XDA Free mobile app
Set correct USB Connection type
It is likely that you have the wrong USB connection type set (This devices defaults to Media sync - MTP). Mine wasn't working either, but this fixed it.
In:
Settings - PC Connection - Select USB Connection Mode
Choose:
Internet connection - Ethernet
Sean
Has anyone gotten their computer find their G4 through cmd (adb devices). I cant get the adb message on my phone to allow access to my computer. I turned on and off usb debugging several times but i still don't see the message on my phone to allow access. I let me computer download the drivers when plugging up my G4 as well as allowing the install of PC drivers.
yes, working great for me. Do u have updated and right drivers? u find tread here with right drivers..
Sent from my unlocked and rooted LG-H815
I was having the same problem..
You need to install the LG Drivers and then your phone will connect via adb..you will be asked on your phone to allow the port connection after installing the proper LG drivers. Verify and you will be good to go..
I used these ones below in the attatchment or you can grab them from.....
http://www.theandroidsoul.com/download-lg-g4-driver-for-windows-and-mac-mtp-adb-download-mode-77723/
I think I found the issue. I had Note 3, 4, Nexus 6, S6 edge, and G4 all still on my computer in the device manager. I uninstalled all of them plus I uninstalled the adb driver in device manager. Plugged my G4 back in and ran the PC driver update via G4 and it worked. I can now see my G4. Don't know if I had to do all that to get it working but hey it worked for me.
I was having issues with this myself and didn't find a solution. I found out that I was having better luck switching it to Camera PTP from the notification dropdown. Sometimes I have to toggle to MTP back to PTP, The dev notifcation should appear when it is actually connected.
1. PTP
(1a. switch to MTP back to PTP if it doesn't work)
2. 'adb kill-server'
3. 'adb devices'
-If you see your device, you can try to 'adb connect **IP**' but it will most likely say it was unable to connect
4. give it your adb commands you want
It's the only way I've been able to get adb, hope this helps!
I was having this issue also. After install win10 then adb connection to my LG G4 (h818) was not detected. Back to android.com, it said that if general USB driver doesn't work then we must find OEM driver to the producer web. LG ADB Driver was about 17MB. After installed the driver then it was immediately detected. Thank God, finally.
I have silly problem. I bought used G4 LG from someone found in online forum. Checked all series on phone (sticker), on software "about phone" all showing LG H815 software version H81510H, but by adb ( linux machine ) showed H812xxxxxx .... set on developer option debugging the command "adb reboot bootloader" just send device into android boot ( device boot ). I wish to unlock the bootloader and put CM. Hard button option > pushing vol up + power button simultaneously did nothing, vol up + power button then > connect to PC via usb, did nothing ( just send phone to device boot ) ..... I have no windows machine
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.