I cannot seem to get Windows to see the device when in USB Debugging.
I've installed drivers from http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black (v2.18.0). Uninstalled and reinstalled. Switched back and forth from PTP to MTP and back again.
Restarted ADB a few times but device manager is still showing drivers not installed when I switch to USB Debugging. As soon as I turn this off it will connect, but of course I cannot see my device in ADB.
I really need to update TWRP as I'm currently on 2.8.0.
I'm an idiot.
Solved with ADB drivers...Sorry...
Related
I have two S3 (GT-I9300RWDVD2).
The first one connects without any problem to my PC and shows in Windows explorer.
The second one connects but in device Manager a message shows "... no drivers loaded ..."
adb works well on both phones.
On the first working one is Omega Rom 6.0 installed,
The not working one has original Firmware I9300BUALF1 installed?
Maybe this is hardware related?
I already made a full wipe on the not working one.
Any ideas?
additional information: changing from MTP to PTP or disabling/enabling debug mode has no effect. adb works, mtp and ptp don't
After a hard reset (*2767*3855#) mtp works.
I had adb working on my computer on the kitkat official rom, and now I updated to the rooted lollipop (Jasime 5.0 base). Root works, I have usb debugging enabled, and have tried following USB modes: Charge, PTP, and MTP (only ones that are available).
I can't get ADB to detect the device anymore.
edit:
I can get it working in TWRP, and I can get it working in PTP, but not MTP (weird). The ADB Composite interface does not appear connected when in MTP mode even though Android says USB Debugging is enabled.
You're supposed to use PTP in order to use adb. Glad you solved it.
As the title suggests, bootloader unlocked no problem, tablet was connecting to ADB at the time, tried to flash recovery which as far as I can tell was not successful (I can't boot to recovery, get the injured Android icon), now I can't connect to ADB (get the "List of devices attached" result). So I'm completely stuck, can't move forward, can't go back to stock, what do I do?
Edit: Apparently it's an issue with my PC, my wife's PC worked fine, why it worked to unlock the bootloader and then stopped I have no idea. Can anyone link me to a solution to get ADB working on my PC again? I tried removing/re-installing drivers, rebooting, you name it, no luck.
With your device booted into recovery or the system do you get anything in device manager? If you get a device with a yellow exclamation mark, right click it. Go to where it allows you to choose a driver from a list on your computer. Select adb android composite (or something like that)
Sent from my Nexus 5 using XDA Free mobile app
Thanks for replying.
So before unlocking the bootloader, with USB debugging enabled I could get the tablet to connect using the ADB driver and could access it with ADB but could not access storage for file transfer, with USB debugging disabled and switching the driver manually to the MTP driver I could access storage but not ADB. I have had other device drivers installed on this PC for my Galaxy phones, I had issues initially with the tablet connecting but showing a yellow exclamation mark, then I removed all of the Android USB devices using USBDeview and installed the 15 second ADB tool to get it working, I'm on Windows 8.1 BTW.
After unlocking the bootloader, with USB debugging enabled I cannot get the tablet to connect using the ADB driver and but it does show as an ADB device with no yellow exclamation mark, I just get the "List of devices attached" result and anything that tries to access the device via ADB hangs or fails. I can still switch the driver to MTP and access the storage just fine.
My wife's PC is a Win7 box and has never had android drivers or ADB installed, I used the 15 Second ADB installer on her PC and the tablet works for ADB and storage access with USB debugging turned on, so there's something I'm missing that needs to be wiped out or reset on my box.
My end goal is stock lolipop rooted.
I botched a flash and now I cant get developer mode / ADB working.
When I started, my tablet was stock ROM, towelroot. I connect tablet in developer mode, flashed dual recovery and everything was great. I copied the pre-rooted lolipop ROM to my SD card and flashed it. HOWEVER instead of turning off the device, I selected reboot from recovery. This resulted in boot loop.
SOOOO, I figured no worries, just flash old ROM and try again. So did this:installed Androxyde Flashtool
opened XperiFirm
downloaded 1276-8392 and 1274-8801 (I've tried the rest using both ROMs btw)
Tools>Bundler>Create>Selected folder>selected SGP312 for device
For branding I entered the above ie 1276-8392
For version I entered the ver ie 10.5.A.230
Flashmode>checked boxes to wipe everything
The flash goes through without a hitch. Under about tablet, I see
Model : SGP312
Android Ver : 4.4.2
Kernel : 3.4.0-perf-g32ce454, [email protected]#1
Build Number : 10.5.A.0.230
I activate USB debugging and unknown sources, connect to USB and Flashtool returns: Device connected with USB debugging turned off
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
I downloaded Sony's ADB drivers, tried to manually update device driver and windows7x64 kicked back driver is not for your device.
I edited the INF to include the hardware ID exactly as it appears in device manager and tried again. This time windows let me load the driver. It shows up in device manager as 'Sony sa0107 ADB Interface Driver'
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Is there a way to verify developer mode on the tablet? What else can I try? The tablet gives me a notification when I connect 'usb debugging mode connected, ready to install software'
Thanks!
_sadpanda said:
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Thanks!
Click to expand...
Click to collapse
I had a very similar problem in 2014. I do not want to discourage you, but at the end I send it back to sony for a repair. They gave me a new tablet and said that the mainboard was broken.
Nevertheless, there is a thread in Sony cross device general, where people like you end up: http://forum.xda-developers.com/showthread.php?t=1849170
You can try and search for help there, maybe you have more luck then me.
Its odd... ADB was working and stopped after flash. Is this what you had or just no connection from the start?
Sorry, I misread your post. I thought your tablet would not start and you could not get flashmode working. Sorry for that.
What you could try:
1. Be sure you actually activated USB debugging in developer options
2. When you connect the device, you should get a prompt on the tablet to allow usb debugging from that computer
Maybe try "revoke USB debugging authorisations" in developer options and reconnect
3. Install the drivers from flashtool/drivers/ or install sony pc companion. Delete your old driver from device manager.
4. try switching between MTP and MSC mode in usb connectivity menu
Since ADB worked before it was probably no driver problem. Now you cannot be sure. Most probably you tapped away the said prompt of allowing usb debugging when connecting.
If none of this helps I don't know of anything more. Maybe try different usb ports or even computers.... Or try to flash again
bernddi said:
4. try switching between MTP and MSC mode in usb connectivity menu
Click to expand...
Click to collapse
UGH!!! I'm a jacka$$. I totally forgot about that menu/setting. fixed instantly.
Hi!
I have searched XDA forum and other forum concerning LineageOS. But I have not found a solution.
My latest experiments were with installation of the adb interface on windows. At first, this worked well and I got full massstorage access. The Galaxy and its both memories did show up in Windows Explorer (like in old ages).
At the next restart of Windows (Win 7 64-bit Pro) when I connected my phone, Windows immediately did install the samsung drivers again. And since that things got even worse: No even the MTP and PTP Mode did not work, so that the Smartphone does not show up at all in the Windows Explorer!
At F-Droid, I have found an app, called USB Mountr. I tried this, but without any effort.
In the device manager of Windows I can see an „Android Composite ADB Interface”. It tells, that the device would work OK.
Now I am stuck with this and I hope, someone will help me, to activate usb massstorage access.
BTW: I have flashed my Galaxy S2 with Heimdall, running on Ubuntu. Heimdall on Windows 7 did not work, because of libusb error -12.
Latest status:
I have uninstalled the app USB mountr and did reboot the phone. Now the USBconnector is only active for charging the battery. I even get no connection in PTP or MTP mode.
Then I have deactivated USB debug mode and ADB. did a reboot, reactivated ADB and USB debug etc. and did further reboot the phone but with no success.
USB connection is nearly dead and cannot have connect with LUBUNTU Laptop. On Win 7, I get the signal tone, which is typical for connecting an USB device. The GT.i9100 shows up in Explorer but cannot be connected. Device manager tells me, that it is an Android device and all would be OK.
As a work around I am using MyPhoneExplorer on Win-7 and KDEconnect for Ubuntu.
Please can anybody tell me, what I should do, to get back at least USB connection in MTP or PTP mode???
I have the exact same problem.
I did notice, that after first boot, there was a message (several times) the MTP daemon/service stopped working (Crashed ?)
Does anyone else encounter this ?
Did anyone else resolve this ?
(Currently I was only able to get/send files to the device via BT, which is slow, annoying,
and a lot of work moving files to their required places after transmitting over BT)
Quick Fix for stuck on boot
This probably isn't the right place but you said there weren't many solutions. If your phone randomly gets stuck on boot you need to Delete Everything including system, factory data reset, flash ROM again with ADB, go through setup. The reason it probably hanged is because you installed an old version of SuperSU Binary or because you flash OpenGapps before setting up phone.
Hope this works
P.S Sorry for the late reply