I'm trying to update my phone using adb side load and it keeps saying device not found. Adb works until I get into recovery. I'm also running windows 8. Any ideas?
Sent from my Nexus 4 using xda app-developers app
handman29 said:
I'm trying to update my phone using adb side load and it keeps saying device not found. Adb works until I get into recovery. I'm also running windows 8. Any ideas?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Go into device manager and install the ADB driver for the now unknown device.
I have the exact same problem, i used the driver that SDK manager downloaded.
In device manager its called "Android Composite ADB Interface"
but when i reboot Nexus 4 into recovery mode, windows does not recognize the device..
Update adb.exe to the latest version (from sdk) , connect and allow to use PC with ADB in android for the first time, then it should work in recovery also
Adam
I did that, still doesn't work
Sent from my Nexus 4 using xda app-developers app
handman29 said:
I did that, still doesn't work
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Install the naked drivers (found here on xda). And if sideload isn't recognized, your SDK is not up to date.
OK maybe my drivers..do you know if they work on windows 8
Sent from my Nexus 4 using xda app-developers app
Side load is recognized but adb can locate my device in recovery
Sent from my Nexus 4 using xda app-developers app
handman29 said:
Side load is recognized but adb can locate my device in recovery
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Did you select the adb option in recovery? If you did, then your drivers are not installed.
same problem here, i just downloaded SDK now, and the first thing i did was to use SDK manager to update the USB driver..
it does work when Nexus is booted in normal mode, but not in recovery.
i guess this is a windows 8 driver issue.
tried to install the driver from this thread:
http://forum.xda-developers.com/showthread.php?t=2019273
but it will not even install in windows 8
So there are different drivers for fast boot and recovery?
Sent from my Nexus 4 using xda app-developers app
I did a driver test from all in one tool kit and all the drivers work just not in adb recovery
Sent from my Nexus 4 using xda app-developers app
I had the same problem, on Windows 8, but while your device is in recovery, go to Device Manager, and choose 'Let me pick from a list of device drivers...', there you will see something like 'Android ADB device'. Install that, and voila! your device will now be recognized in recovery mode.
Sideloaded 4.2.2 on my N4 last night.
ravneetg said:
I had the same problem, on Windows 8, but while your device is in recovery, go to Device Manager, and choose 'Let me pick from a list of device drivers...', there you will see something like 'Android ADB device'. Install that, and voila! your device will now be recognized in recovery mode.
Sideloaded 4.2.2 on my N4 last night.
Click to expand...
Click to collapse
On my computer, the device is not even listed in device manager while in recovery mode, so there is no device to update..
wierd.
same issue here; I tried to do it in linux (linux doesn't need any driver), using the latest adb (I downloaded the sdk this morning) but still nothing: Error device not found
I was having the exact same problem and the below steps, posted by a member in reply to my problem, solved my problem-
I downloaded the nexus 4 drivers from this link- http://forum.xda-developers.com/showthread.php?t=1992345
mashedbymachines said:
Had the same problem.
Right click the "nexus 4" with the yellow exclamation mark.
Go to the details tab
Choose "hardware id"
you will see something like
USB\VID_18D1&PID_D001
USB\VID_18D1&PID_D001&REV_0228
Open your folder with the usb_driver
edit the android_winusb.inf
depending on if you use 32/64 bit, navigate to
for 32 bit
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
for 64 bit
[Google.NTamd64]
xxxxx
;Google Nexus (generic)
xxxx
Add these two lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Be sure that the text after "USB_Install" matches what you had on your hardware id tab in device manager.
Now try to install these drivers and voila, it should install and work under recovery!
Click to expand...
Click to collapse
if you are still having issues, definitely try the naked drivers. I couldn't get other drivers including the SDK ones to detect my phone that is in recovery/sideload mode. The naked ones worked right off the bat.
whatsandroid said:
On my computer, the device is not even listed in device manager while in recovery mode, so there is no device to update..
wierd.
Click to expand...
Click to collapse
Adb won't be recognized in stock recovery until you choose the sideload option.
Adb access recovery wide is a custom ROM feature.
Sent from my Nexus 4 using xda premium
El Daddy said:
Adb won't be recognized in stock recovery until you choose the sideload option.
Adb access recovery wide is a custom ROM feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
OK, did not know that.
but still getting the same error message as the OP when i try to sideload.
and adb devices is not showing any devices, should adb devices work on a device with stock while in recovery?
also tried that "naked" usb driver that someone posted
whatsandroid said:
OK, did not know that.
but still getting the same error message as the OP when i try to sideload.
and adb devices is not showing any devices, should adb devices work on a device with stock while in recovery?
also tried that "naked" usb driver that someone posted
Click to expand...
Click to collapse
Did you try the method which I posted? I was having the same exact problem.
ADB devices should work while in recovery.
Related
Okay i know there are a millio0n and one topics here regarding this but after trying PDAnet android app and SDK routes and downloading V/A usb drivers i cant unlock my boot loader.
Running win & 64bit, now when im in boot loader i can't see the Android 1.0 in the device manager.
any ideas fellas ? getting desperate i only want to install clock work mod FFS
update driver"
browse computer for driver"
let me pick from list"
select
android bootloader interface ver.4
demo23019 said:
update driver"
browse computer for driver"
let me pick from list"
select
android bootloader interface ver.4
Click to expand...
Click to collapse
I tried this also but nothing happens.
I have USB drivers installed from the SDK from google.
and when i run CMD and got fastboot devices it just reports that its not a valid command under Windows
Are you executing fastboot from the sdk directory? Like "cd c:/sdk". Then running the fastboot command? Otherwise make sure you have compatible 64bit drivers which you could Google. There was a similar thread here with the same problem as you I think.
Sent from my Nexus S using XDA App
Finally got it to work turned out to be a bad USB bribery file in the ask after md5 checks I really dledand I'm away
Sent from my Nexus S using XDA App
After several hours of frustration, I'm just going to ask.
I have USB debugging enabled. When I plug in the Nexus 4 Windows auto installs drivers for MTP.
It's listed under portable devices in device manager. I am trying to uninstall the driver and install the Naked driver. But as soon as I uninstall in device manager, Windows reinstalls, despite me having turned off auto-installation of drivers. I am not able to use the advanced method listed here http://www.addictivetips.com/window...utomatic-driver-installation-in-windows-vista because gpedit.msc doesn't exist for Home users.
I have unplugged the device and manually put it into Fastboot and plugged it in. Windows does not try to autoinstall drivers. I am able to install Naked drivers and the device appears as "Android Phone" in device manager.
How can I proceed?
Donteventrii said:
After several hours of frustration, I'm just going to ask.
I have USB debugging enabled. When I plug in the Nexus 4 Windows auto installs drivers for MTP.
It's listed under portable devices in device manager. I am trying to uninstall the driver and install the Naked driver. But as soon as I uninstall in device manager, Windows reinstalls, despite me having turned off auto-installation of drivers. I am not able to use the advanced method listed here http://www.addictivetips.com/window...utomatic-driver-installation-in-windows-vista because gpedit.msc doesn't exist for Home users.
I have unplugged the device and manually put it into Fastboot and plugged it in. Windows does not try to autoinstall drivers. I am able to install Naked drivers and the device appears as "Android Phone" in device manager.
How can I proceed?
Click to expand...
Click to collapse
Try checking the drivers thread link in my signature.
Stryder5 said:
Try checking the drivers thread link in my signature.
Click to expand...
Click to collapse
The problem is that Windows is auto-installing the driver as soon as I uninstall it from device manager. I have this setting disabled in Device Installation Settings but nevertheless it continues auto-installing.
Donteventrii said:
The problem is that Windows is auto-installing the driver as soon as I uninstall it from device manager. I have this setting disabled in Device Installation Settings but nevertheless it continues auto-installing.
Click to expand...
Click to collapse
When you plug in your n4 in your pc, does it allow you to open the folder for your phone. If it does the drivers are installed. Mine n4 did the same as you when I plugged it in my PC, and did show Android in the device manager.
Use the nexus 4 toolkit to do it.
http://forum.xda-developers.com/showthread.php?t=1995688
jt.61 said:
When you plug in your n4 in your pc, does it allow you to open the folder for your phone. If it does the drivers are installed. Mine n4 did the same as you when I plugged it in my PC, and did show Android in the device manager.
Click to expand...
Click to collapse
It's showing up as portable device, not as Android when MTP is connected. If I manually boot into fastboot, and connect to PC it will show as Android.
Nexus 4 toolkit doesn't work. When I connect the device, it still only shows up as MTP device connected.
How can I stop the "Nexus 4" driver from auto installing the MTP driver?
Nobody else is having this problem?
Sent from my Nexus 4 using Tapatalk 2
Donteventrii said:
Nobody else is having this problem?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Bump
For the love of bump
...
Sent from my Nexus 4 using Tapatalk 2
You could try this installer. If a prompt ever says not to install a driver just do it anyway.
http://www.junefabrics.com/android/download.php
I was having the same issues, toolkit didnt work, auto kept auto installing MTP only, junefabrics.com didn't work by itself, LG drivers didn't work. finally I tried the drivers in sig and adb was installed but the tool kit still didn't recognize it. I ran the one from junefabrics.com after that and hit no to not reinstall the drivers when it asks, but it's hanging when installing pdanet on my phone.
TCMan5190 said:
I was having the same issues, toolkit didnt work, auto kept auto installing MTP only, junefabrics.com didn't work by itself, LG drivers didn't work. finally I tried the drivers in sig and adb was installed but the tool kit still didn't recognize it. I ran the one from junefabrics.com after that and hit no to not reinstall the drivers when it asks, but it's hanging when installing pdanet on my phone.
Click to expand...
Click to collapse
im in the same boat
I'm having these same issues. Very frustrating.
Just fixed the problem by following the directions in this post - http://forum.xda-developers.com/showpost.php?p=34154052&postcount=7
His instructions about cmd prompt didn't work for me, so in device manager I selected View -> Show Hidden Devices.
I removed all android, nexus, other android phones and then reinstalled the drivers via the toolkit. Seems to be working so far!
The MTP driver will always install as that's nothing to do with adb. If you open Device Manager it should have the other option - you then manually install the driver by browsing the the drivers folder when using the 'Update driver' option in the right-click menu when you click on it in Device Manager
BUMP
Donteventrii said:
...
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I am having the same problem my windows xp is not reading I install a couple of different drivers still nothing. This the only phone/tablet I am having this issu that my pc is it's not reading the files of my phone.
OTA JOP40D
2nd Batch phone
hello, now nexus 4 updated to 4.2.2 and when i connect to computer the device could not be found
i updated SDK , all the required things inside android 4.2 but still device not found
is there drivers that i can install instead of checking for updates and so on?
jasonmiracle said:
hello, now nexus 4 updated to 4.2.2 and when i connect to computer the device could not be found
i updated SDK , all the required things inside android 4.2 but still device not found
is there drivers that i can install instead of checking for updates and so on?
Click to expand...
Click to collapse
Try downloading pdanet on your pc or downliad a nexys4 toolkit from here and they let u install the drivers
Sent from my Nexus 4 using xda premium
casonswag said:
Try downloading pdanet on your pc or downliad a nexys4 toolkit from here and they let u install the drivers
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried pda but failed
its caused by the android 4.2.2 update...
For anyone still having problems, these are the steps I followed that fixed it for me. (After updating to the latest sdk version and downloading the google usb driver)
1. Uninstalled the driver from Device Manager
2. Let it automatically install the generic 'MTP device driver'
3. Right clicked on the new device and selected 'Update Driver'
4. Selected 'Have Disk' and pointed it to [android-sdk-dir]\extras\google
5. Watched an 'ADB' driver install.
6. Opened Eclipse to successfully run on my N4.
Hey guys,
I'm trying to install the latest OTA on my nexus 4 with "adb sideload". I have an updated sdk on my windows 8 64bit pc; ADB works perfectly when the Nexus is turned on, but after "adb reboot recovery" and Apply update from ADB, but then, "adb devices" doesn't show anything.
So I thought this might be related to windows 8 adb driver, so i gave a try on my other laptop, which run archlinux 64 bit (linux doesn't need any driver to run adb properly); I installed the sdk, and adb works here too when the device is on, but than, in recovery mode, it won't show up.
Im having the same issue...let me know if you get a fix
Sent from my Nexus 4 using xda app-developers app
quiro91 said:
Hey guys,
I'm trying to install the latest OTA on my nexus 4 with "adb sideload". I have an updated sdk on my windows 8 64bit pc; ADB works perfectly when the Nexus is turned on, but after "adb reboot recovery" and Apply update from ADB, but then, "adb devices" doesn't show anything.
So I thought this might be related to windows 8 adb driver, so i gave a try on my other laptop, which run archlinux 64 bit (linux doesn't need any driver to run adb properly); I installed the sdk, and adb works here too when the device is on, but than, in recovery mode, it won't show up.
Click to expand...
Click to collapse
Somehow I recall adb devices doesn't work in recovery mode, nor it does it fastboot mode. Just try to chose sideload on your recovery and then run sideload command.
quiro91 said:
Hey guys,
I'm trying to install the latest OTA on my nexus 4 with "adb sideload". I have an updated sdk on my windows 8 64bit pc; ADB works perfectly when the Nexus is turned on, but after "adb reboot recovery" and Apply update from ADB, but then, "adb devices" doesn't show anything.
So I thought this might be related to windows 8 adb driver, so i gave a try on my other laptop, which run archlinux 64 bit (linux doesn't need any driver to run adb properly); I installed the sdk, and adb works here too when the device is on, but than, in recovery mode, it won't show up.
Click to expand...
Click to collapse
When your in the boot loader you have to use fast boot,so do flasboot flash
And put the name of the update after fastboot flash
tried but it shows me "Error: device not found" on the terminal
KyraOfFire said:
Somehow I recall adb devices doesn't work in recovery mode, nor it does it fastboot mode. Just try to chose sideload on your recovery and then run sideload command.
Click to expand...
Click to collapse
my bootloader is locked, so I can't use fastboot flash
heat361 said:
When your in the boot loader you have to use fast boot,so do flasboot flash
And put the name of the update after fastboot flash
Click to expand...
Click to collapse
I was having the exact same problem and the below steps, posted by a member in reply to my problem, solved my problem-
I downloaded the nexus 4 drivers from this link- http://forum.xda-developers.com/showthread.php?t=1992345
mashedbymachines said:
Had the same problem.
Right click the "nexus 4" with the yellow exclamation mark.
Go to the details tab
Choose "hardware id"
you will see something like
USB\VID_18D1&PID_D001
USB\VID_18D1&PID_D001&REV_0228
Open your folder with the usb_driver
edit the android_winusb.inf
depending on if you use 32/64 bit, navigate to
for 32 bit
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
for 64 bit
[Google.NTamd64]
xxxxx
;Google Nexus (generic)
xxxx
Add these two lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Be sure that the text after "USB_Install" matches what you had on your hardware id tab in device manager.
Now try to install these drivers and voila, it should install and work under recovery!
Click to expand...
Click to collapse
I have the same issue with a different device - a RK3066 based tablet in WinXP.
I put the tablet in Service mode, connect the USB, install the drivers correctly..
and adb doesn't detect the device.
I included the Vendor ID in adb_usb.ini with this command and still nothing.
echo 0x18D1 >> "%USERPROFILE%\.android\adb_usb.ini"
Is there anything else I can try?
(18D1 is the Google vendor ID if anyone wants to try this for the Nexus4,
it's something else for Rockchip)
Solved, thanks! I had to use this (https://laslow.net/2012/03/14/disable-driver-signature-enforcement-in-windows-8/) to install the new driver but now it worked!
sunny4691 said:
I was having the exact same problem and the below steps, posted by a member in reply to my problem, solved my problem-
I downloaded the nexus 4 drivers from this link- http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
I tried everything in this post and it doesn't wortk. Like in the original post, "adb devices" recognize my device when it's started with "USB Debugging activated", but when I'm in recovery mode, my phone is not recognized by ADB.
I want to try UbuntuTouch on my Nexus 4, and I need to do a adb push, but when I do it return me this error message: "error device not found".
I tried this solutions:
sunny4691 said:
I was having the exact same problem and the below steps, posted by a member in reply to my problem, solved my problem-
I downloaded the nexus 4 drivers from this link- http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
quiro91 said:
Solved, thanks! I had to use this (https://laslow.net/2012/03/14/disable-driver-signature-enforcement-in-windows-8/) to install the new driver but now it worked!
Click to expand...
Click to collapse
I have also tried this modification:
Originally Posted by mashedbymachines
Had the same problem.
Right click the "nexus 4" with the yellow exclamation mark.
Go to the details tab
Choose "hardware id"
you will see something like
USB\VID_18D1&PID_D001
USB\VID_18D1&PID_D001&REV_0228
Open your folder with the usb_driver
edit the android_winusb.inf
depending on if you use 32/64 bit, navigate to
for 32 bit
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
for 64 bit
[Google.NTamd64]
xxxxx
;Google Nexus (generic)
xxxx
Add these two lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Be sure that the text after "USB_Install" matches what you had on your hardware id tab in device manager.
Now try to install these drivers and voila, it should install and work under recovery!
Click to expand...
Click to collapse
ADB works in TWRP recovery for me. Im on Windows 7 if that makes any difference.
Well, thanks a lot! Now it worked.
Rizy7 said:
ADB works in TWRP recovery for me. Im on Windows 7 if that makes any difference.
Click to expand...
Click to collapse
Worked for me !
sunny4691 said:
I was having the exact same problem and the below steps, posted by a member in reply to my problem, solved my problem-
I downloaded the nexus 4 drivers from this link- http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
Thanks
sunny4691 said:
I was having the exact same problem and the below steps, posted by a member in reply to my problem, solved my problem-
I downloaded the nexus 4 drivers from this link- http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
This worked like a charm. added the lines of code and installed the driver. My Nexus 4 was detected on recovery mode and I just finished installing KitKat.
Mythsoul said:
This worked like a charm. added the lines of code and installed the driver. My Nexus 4 was detected on recovery mode and I just finished installing KitKat.
Click to expand...
Click to collapse
I connected my nexus with debugging enabled. Did "adb reboot bootloader". As soon as it entered bootloader, the device got disconnected from PC.
I could see the yellow exclamation mark over Nexus 4 on the screen.
I right clicked on nexus 4.
1. updated driver software
2. Browse my computer
3. Let me pick from list of device drivers
4. click on android
5. Click on adb bootloader interface.
6. Done
I had a frustrating issue trying to do the exact same thing. I tried stock and TWRP recovery. Something I did not try was removing Supersu.
Try unrooting. I expect the Google update zip doesn't allow itself if it's there.
Sent from my Nexus 4 using XDA Premium 4 mobile app
possible soltion under linux
quiro91 said:
Hey guys,
I'm trying to install the latest OTA on my nexus 4 with "adb sideload". I have an updated sdk on my windows 8 64bit pc; ADB works perfectly when the Nexus is turned on, but after "adb reboot recovery" and Apply update from ADB, but then, "adb devices" doesn't show anything.
So I thought this might be related to windows 8 adb driver, so i gave a try on my other laptop, which run archlinux 64 bit (linux doesn't need any driver to run adb properly); I installed the sdk, and adb works here too when the device is on, but than, in recovery mode, it won't show up.
Click to expand...
Click to collapse
I'm noob, so no links; but stackoverflow /questions/9210152/set-up-device-for-development-no-permissions has the answer;
says the key is to be root when restarting the adb server; in ubuntu:
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices
Worked for me!
Hi guys,
I'm currently experiencing a probem with my Nexus 4. No matter what OS I use (Linux or Windows) or what driver I use adb keep saying that my device is offline. As I saw elsewhere I tried an other usb cable or port but nothing seemed to work. Does anyone got an idea for this ? This thing is gonna drive me crazy !
Thanks
Task Manager, then kill the ADB one. Then open ADB, adb devices again.
Otherwise, did you check the debugging =.= Or reinstall the driver manually (not by WIndows).
I have had a problem with this and it has been unsolved as of yet, but I may be able to help you. In the SDK Manager, there is an extras area, if you don't have the drivers from there I have found you may have trouble. It could be something else, but this should be a sufficient launchpad.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Are you on 4.2.2 they changed somethings with the update. Have you updated your SDK?
Try installing PDAnet drivers. They will make it work.
xdaOSdev.team said:
Try installing PDAnet drivers. They will make it work.
Click to expand...
Click to collapse
I can verify this, it solved the problem I have been having for a few months in Linux OSes.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Guys, he said he's using ubuntu lol there are no usb drivers to install
try this...it sounds like your adb may be out of date. This will also reinstall fastboot, unless you leave 'android-tools-fastboot' off the last command
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
btw, if you haven't already done so, you should get the full sdk installed. It's better to have it and not need it than to not have it and realize after three hours of pulling your hair out you should have had it all along lol (I've done it, so I speak from experience)
Thanks @hp420 but sadly the device is still offline. I'm just realizing it now but I didn't have the warning message about the association with the computer that I usually have when activating USB debugging with 4.2.2
Load latest SDK version. Load driver inf fix. Search forum. Known problem. Easy fix.
sent from my nexus 4; cat on lap, beer in hand
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
No need for driver i'm running linux...
Sent from my Nexus 4 using xda app-developers app
Nark.GA60 said:
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
Click to expand...
Click to collapse
Tanks fort that answer I'll try it as soon as possible !
Sent from my Nexus 4 using xda app-developers app
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
try a live cd of ubuntu and see what happens. that will at least narrow it down to whether it's your ubuntu installation or your phone. if it still won't mount in the live cd we can assume it's an issue with your phone. from there you can run a nandroid backup and reflash the factory images to see if that fixes the issue. if it does, you can try a fresh install of the rom you're using. if it still works, then restore all your apps/app data
if it's your ubuntu installation there are other avenues you can try.
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
scream4cheese said:
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
Click to expand...
Click to collapse
UBUNTU!!!!!
lol
hp420 said:
UBUNTU!!!!!
lol
Click to expand...
Click to collapse
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
scream4cheese said:
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
Click to expand...
Click to collapse
Thann you all for your answers! I use linux mint which is my main OS. I manage to resolve my problem in a weird way: first I push a CWM recovery with fastboot and then I flash the ZIP from SuperSu ! From now USB debugging is working properly and I get the usual warning !
What I would like to know now is why ? Does the SuperSU ZIP reset something ?
Sent from my Nexus 4 using xda app-developers app
I am generally good at rooting any android phone. I am having a hard time locating the drivers for the VZW LG G2. I have the zip file from the post on how to root the phone, but I am not sure which file to install.
Any input would be appreciated.
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
iowabowtech said:
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
Click to expand...
Click to collapse
I needed to install LG VZW_United_WHQL_v2.11.1 then go to LG website and download drivers from the G2 support page. I couldn't upload the exe file. Restart computer and all went well. I had same issue and struggled to solve.
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Bxrider117 said:
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Click to expand...
Click to collapse
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
i'm having the same issue. i'm trying to root, and it won't list it at all, and i'm not getting the debugging icon on top. no serial number popping up on the abd devices and i just tried with both 3.8 and 3.10 drivers. anything?
If I remember correctly I had to go to settings>pc connection>select USB connection method and then choose Internet connection, then choose modem in order to get the debugging icon to appear.
Sent from my VS980 4G using xda app-developers app
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
thanks!
bigox said:
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
Most likely it's because you don't have the right drivers installed. Try installing these http://g2-lg.com/download-lg-g2-android-usb-drivers-ver-3-10/.
Sent from my VS980 4G using xda app-developers app
The drivers aren't working for me so i will link where you can get the drivers from the actual website. Please note: this link is for Tmobile D801 but you can search for your device on there.
http://www.lg.com/us/support-mobile/lg-D801
LG's website has drivers for D800 and D801. I'm looking for D802 drivers. Where can I find them or which are compatible?
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
cggorman said:
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Where can I find Universal drivers? Not on LGs website.
I installed this:
http://forum.xda-developers.com/showthread.php?t=1379875
And after that it worked fine. I have a ls980, so the att and t-mobile don't work for me. This did.
This took me a while to sort out. There is a certain driver package for the verizon phone. The drivers listed here dont seem to work for me. I'm using win 7. Here is what I needed to use, then everything just came together - LG VZW_United_WHQL_v2.11.1
These can be downloaded at LG's site. Make sure you search for drivers pertaining to the model number of your phone.
Hope this helps someone
EVOme said:
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
Click to expand...
Click to collapse
I am having the same issue..what is the sdk with adb installed and what directory do i browse to? sorry for the noob questions, ive always had nexus's, so much easier to flash recoveries etc
LG Drivers failing to install
I Install LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1.exe from LG website, it installs and I get a "successful" message from the software package. However, shortly after windows pops up a bubble with "not successful". Details:
Uninedntified Device - No Driver Found
Creative Game Port - Failed
Plug in phone and select “PC Software”, since none of the other options make any sense (USB charge, Media Transfer, Tethering, and Picture Transfer). Sidebar: None of the other options seem to change anything even when tried. "Media Transfer" is the only one that seems to actually install something successfully, but nothing changes with the device list. Back on track: Get a new windows “installing” bubble. Shortly after I get another “not successful” message with the following:
MTP USB Device – Failed
I go to Devices and Printers, select the phone, and look in the properties. Click “update driver” and pick the LG folder in Program Files. It says “driver already installed”.
Rebooting the computer accomplishes nothing.
I’ve tried several full uninstalls.
No matter what I try, if I run “adb devices”, I get “List of Devices Attached” then my prompt back, meaning none found I assume.
Yes I have turned on dev mode on the phone and I get the debugging icon when the USB cable is plugged in. I’m on Win7 64. WTF is wrong with this driver?
Thanks for any help you can give!
Uncheck usb debug? Had this on my htc one x. Maybe helps
Sent from my LG-D802 using XDA Premium 4 mobile app