So I'm getting this issue where I can't locate the device via ADB. I've tried reinstalling drivers which doesn't work. The device regardless of if it's in debug mode or not fails to mount and instead, windows fails to even detect it branding it a "Unknown device". I've tried restoring to a previous nanddump (taken just after rooting) which has still failed to fix the issue.
Is there a fix or am I stuck with having to sideload every app I develop?
Edit: apologies for putting this in the wrong sub-forum
I had to go into device manager and force the unknown device to use the nexus 7 drivers from the android SDK folder manually, (after I have used the SDK manager to download them of course) I've had to do this on 2 windows 7 computers so far, so I would give that a go, if you need help I'll hunt a guide out for you.
dasmith91 said:
So I'm getting this issue where I can't locate the device via ADB. I've tried reinstalling drivers which doesn't work. The device regardless of if it's in debug mode or not fails to mount and instead, windows fails to even detect it branding it a "Unknown device". I've tried restoring to a previous nanddump (taken just after rooting) which has still failed to fix the issue.
Is there a fix or am I stuck with having to sideload every app I develop?
Edit: apologies for putting this in the wrong sub-forum
Click to expand...
Click to collapse
wugtoolkit has update the driver you search for try download that...
Since I can't post on the actual threads yet, due to being a new account, I will be posting here in hopes that someone comes across this and can help me out.
I have done a pretty hefty amount of reading trying to get my Nexus 7 rooted and for some reason I just can't get past the part of installing the necessary drivers for my computer.
Specs:
- Windows 7 32 bit. (Administrator account)
- Nexus 7 32GB (Wifi) running 4.2.1 w/ OEM cable (Also tried a non-OEM cable)
What I have done so far with Wug's Toolkit:
- Step 1
1. Plugged in my device and made sure USB Debugging was enabled. (At this point, the Device Manager recognized a device and tried installing drivers, but failed.) So the first thumbnail is what I have in my device manager from the start. Nexus 7 under "Portable Devices" and "Other Devices."
2. I uninstalled both of the devices.
3. Unplugged my device and used USBDeview to uninstall anything that resembled "Google" or "ADB", etc. like it states.
4. Rebooted my computer.
- Step 2
1. It says that the recommended solution is #3, so naturally, I tried that one first. I followed the steps and installed the Android Composite ADB Interface drivers successfully and it even shows it under "Android Phone" in my device manager, second thumbnail, when my device is plugged in. (USB Debugging enabled)
2. Now, when I click on the "Reboot Bootloader" button on step 6 is where it just hangs with the dialog box "Rebooting your device into bootloader mode..." but my Nexus never reboots or anything. My Task Manager show two "adb.exe" processes and none ever end. I read the thread and some users were having the same problem and they got it to work by ending one of the adb.exe processes. So I have to end one of them and after a while I get a "Checking Fastboot status" then a few seconds later this message box pops up, third thumbnail. It says that Debugging is not necessary for bootloader mode, so I turn off USB Debugging and my computer recognizes a new device. So it successfully installs Android ADB Interface and I try the Reboot Bootloader button again, and it still hangs. Only this time, there is one adb.exe. So I kill it, and after a while I get the same error dialog box as the third thumbnail. Like it states, I am using driver configuration #3, so I will go ahead and close the dialog box and go to step 7.
3. Since my device is already configured, I go to Step 12.
4. I hit the "Reboot Device" button, but nothing happens to my device.
At this point, I decide to try a different driver solution. So I go through the whole process all over again, with Solution 1. Go through and install the drivers, everything goes according to the tutorial. I get to Step 3, and hit "Full Driver Test" and it hangs on "Checking ADB Status". There are two
adb.exe's so I end one of them. I get a dialog box that says ADB device not found.
Finally, I decide to try Solution 2. So I go through the whole process. Yet I still get the same hanging with adb.exe. I even tried different USB ports, but nothing.
Now, with mskip's Toolkit I never get past the "Starting ADB..." message. It just hangs there.
So the problem lies with ADB.exe I'm guessing. I'm tired and I've spent hours just trying to root this thing. Am I SOL? Anyone have anything that I can try out or the same problems?
Have you tried rebooting your PC after installing the drivers? It took me ages to get mine installed and I think a reboot allowed the device to show up and work properly. I thought it would be easy being a nexus device. Turned out to be a right pain in the ass.
Yep.
davidoff59 said:
Have you tried rebooting your PC after installing the drivers? It took me ages to get mine installed and I think a reboot allowed the device to show up and work properly. I thought it would be easy being a nexus device. Turned out to be a right pain in the ass.
Click to expand...
Click to collapse
Hey thanks for the response. Yes I have. I tried rebooting after every driver change. (Uninstalling, re-installing, etc.) My device does show up, almost as if the drivers are working correctly. Though I'm not sure why adb.exe is giving me troubles.
Have you tried 'adb devices' via cmd prompt? I take it your all stock then?
davidoff59 said:
Have you tried 'adb devices' via cmd prompt? I take it your all stock then?
Click to expand...
Click to collapse
No I haven't. Is this what you are talking about? http://forum.xda-developers.com/showthread.php?t=1741395
EDIT: I just tried "adb devices" via command prompt in the Advanced Settings, "Daemon not running, running it now, daemon started successfully." Now it'st just hanging. Two adb.exe processes.
What I was hoping to do was to create a backup of all my apps and data before I mess around with it. Yes, I'm all stock.
Add me on gchat and hit me up. Not sure what you are having problems but I could help you trouble shoot.
{{ WugFresh }}
WugFresh said:
Add me on gchat and hit me up. Not sure what you are having problems but I could help you trouble shoot.
{{ WugFresh }}
Click to expand...
Click to collapse
Thanks for the response, I have e-mailed you.
I got a nexus 7 2012 wifi 32gb today, updated to 4.3, and I have had nothing but problems trying to root the thing. I have been unable to unlock the bootloader, currently whenever I'm in bootloader mode windows 7 64 bit just shows it as an "unkown device" when I look at the properties it says "Windows has stopped this device because it has reported problems. (Code 43)" I have tried "update drivers" and had it look at C:\PROGRAM FILES (X86)\WUGFRESH DEVELOPMENT\DATA\DRIVERS but it just says the drivers are up to date for my unkown device. There was actually a point where in bootloader mode windows had device manager say bootloader something instead of unkown device however it says drivers were not installed and I think the error code was 10 or something, basically it was still useless and would not recognise my device and install drivers. I have tried on my laptop which has windows 8 64 bit but it is far worse there, the computer keeps giving malfunction usb message or something over and over again as if the device is constantly connecting and disconnecting. Despite this however MTP works fine and I have transferred a music album over as a test and it was fine and the device charges fine too. Would really appreciate help as I'm desperate at this point.
Uninstall whatever out of date drivers that came with the toolkit then install the latest Android Composite ADB Interface Driver 8.0.0.0.
You also need to install this in order to use ADB while in recovery.
No dice, still unable to install the drivers for the bootloader interface, I go to device manager and right click the android bootloader interface thing and click update driver software navigate it to the universal naked driver folder however it always just says the drivers for your device are up to date, which is bull**** because the drivers have not installed. I have tried right clicking then clicking uninstall then unplugging and replugging but it will now just give a message saying the device is not recognised and it shows up as an unknown device in device manager, 90% of the time it just shows up as an unknown device and it is impossible to install drivers for it, it just always says the drivers are up to date and uninstalling them and trying again will just yield the same results. I have the other drivers installed completely fine, it's the bootloader drivers which are impossible for me.
Short of going back in and deleting (not just uninstalling) every USB driver, might be easier to borrow another computer?
lightlink7 said:
No dice, still unable to install the drivers for the bootloader interface, I go to device manager and right click the android bootloader interface thing and click update driver software navigate it to the universal naked driver folder however it always just says the drivers for your device are up to date, which is bull**** because the drivers have not installed. I have tried right clicking then clicking uninstall then unplugging and replugging but it will now just give a message saying the device is not recognised and it shows up as an unknown device in device manager, 90% of the time it just shows up as an unknown device and it is impossible to install drivers for it, it just always says the drivers are up to date and uninstalling them and trying again will just yield the same results. I have the other drivers installed completely fine, it's the bootloader drivers which are impossible for me.
Click to expand...
Click to collapse
The Android Composite ADB Interface Driver 8.0.0.0 driver from SDK is for bootloader and when booted into ROM. Naked Driver 0.72 is only for when in recovery or else your computer would show "Nexus 7" under Unknown Devices in the Device Manager.
Hi,
I tried a lot of other rooting applications and have had no luck with any of them. Then I found Wug's Nexus Root Toolkit. It works for my Nexus 4 (Jelly Bean 4.3) - until I came to the "Full Driver Configuration Guide" - where it gives a message: "ADB device was not found".
I have tried it over several times to no avail. Can anyone offer any clues as to what may be causing this?
btw, I am running the Wug's Nexus Root Toolkit v1.7.2 on Windows 8.
Thank you,
David
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
I am having the same problem. Where/how does the phone ask you to confirm USB debugging? It asks me when I turn it on, but not again later.
I have tried 3 or 4 different drivers, but, although the device is recognised by Windows 8, it is not recognised by Root Toolkit.
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
studacris said:
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
Click to expand...
Click to collapse
I'm not quite sure how this was supposed to help. My problem is that the ADB drivers do not seem to work on my computer. I have just tried installing the Android SDK (which comes with its own ADB drivers), having first uninstalled all the existing drivers. It did not help.
Not entirely sure where to go from here.
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
studacris said:
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
I had installed PDANet from within Root Toolkit, and it didn't work. Just now, I uninstalled everything again, and installed PDANet from their web site. Still get no ADB device in Root Toolkit. [NB I didn't have PDANet on the phone, but it seems to be there now]
I tried running adb from the android SDK, and it says "error: device not found".
However, I noted there was an adb prompt on the phone when I first plugged it in, this time (which I told to always accept).
[Later]
Wierd - it is now a bit further on. This is what I did:
Started PDANet on the phone, and enabled USB tethering.
Started PDANet on the computer, and it connected to the phone. At this point the USB debugging permission thing came up again, and I accepted it (also ticking the box to always accept).
Unticked USB tethering on the phone again.
Stopped PDANet on the computer (right click on icon, exit).
Tried the Root Toolkit again (pressed Root button), it connected to the device, and put it into fastboot mode.
The boot loader appeared on the phone, and the computer said "Checking Fastboot Status".
It seemed to stay like that for ever.
Killed the root toolkit. and tried again.
Left the computer for a while, and when I came back, it had completed.
So, it seems to be working now.
And when you try using fastboot directly instead of the toolkit....... what happens?
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
studacris said:
And when you try using fastboot directly instead of the toolkit....... what happens?
Click to expand...
Click to collapse
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Best idea i didnt notice too
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
Thanx !!!!!!!
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Thank you so much! This solved it for me :good:
nikkilocke said:
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Click to expand...
Click to collapse
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Click to expand...
Click to collapse
I found the same solution, changing over from MTP to CAMERA suddenly had the toolkit recognise the phone and could boot it to unlock then root it... Previously, I had installed PDA drivers...
I am astonished how PATHETIC nexus phones/tablets are at simply connecting to a PC. I am baffled at the attempt by google to make their devices as UN-plug & play friendly as possible... bizarre! I have a N10, N7 and have had two N5's and all have the same PITA random disability....
grrr...
Mark.
So the Nexus toolkit is able to see the Nexus 7 as a media device but not Windows ?
marcelin99 said:
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
Click to expand...
Click to collapse
So the Nexus 7 toolkit is able to see the Nexus 7 as media device with this method, but not Windows ? That's strange because Windows is supposed to see your files within the Nexus via Mtp mode. Is it that google removed the ability for Windows to be able to see Nexus 7 files in Android kit kat 4.4.2. What should I do then if I simply want to view files inside Nexus as a non root user ? B.T.W I'm currently on stock kitkat 4.4.2 build KOT49H. Therefore, I'd gladly appreciate it if anyone out there would answer this question and thanks in advance. Feel free to PM me on this so we can "talk" about this. : )
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Success.
Well, mtp connection works perfectly fine in my Windows 7 machine. But on my xp machine I could never get it to work no matter what driver combination I used.
I can see the reason they changed to mtp but I found mass storage to be much more user friendly.
Sent from my Nexus 4 using XDA Free mobile app
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Stuck on fastboot screen
GranPaSmurf said:
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Click to expand...
Click to collapse
Hi
Happy New Year to all! unfortunately I am left with the unusable nexus 7 that happened last night.
I was going crazy with the lags with lollipop and was waiting for the 5.0.5 update OTA but the delay was making me go crazy so I decided to take the risk of manually flashing the image using ADB and SDK.
Like many others pointed, I knew how to enable my computer to see my device by switching from MTP to PTP mode from my earlier rooting experience with Samsung, HTC and others. So that was not an issue for me.
I was following a tutorial from androidcentral and half way through I went to check a tutorial on youtube which I think caused the disaster. After I executed the adb devices no devices were detected and like I said I went and changed the MTP mode to off and bingo now my device was detected.
I executed device unlock and currently my device is in unlocked bootloaded state which is displayed in the fastboot screen where I am stuck now. Following the youtube instead of flashing each separately bootloader first and then the factory image I jumped to 'flash-all.bat' command...I saw something say on my command prompt on pc that completed in so many seconds or minutes which led me to get anxious and since no rebooting happened on the device I went and manually tried to press the power button.
From that time I am stuck on the fastboot screen. I can cycle through 'power off', restart booloader, recovery mode and start. But when I select 'restart bootloader' it comes to 'start' in the same mode and when I select that I can see a tiny 'Booting failed' in white letters in tiny fonts on the top left side of the 'Start'. I cannot go past this state.
Since I know the last time I had enabled 'usb debugging' and MTP off before everything went wrong I am presuming those states are still intact. I can see status on 'reboot bootloader' screen that my bootloader is unlocked.
Now, when I try to go through the process again my device is seen in device manager but when I send 'adb devices' command it cannot detect any devices. If my device is usable I can atleast go into settings to see if my MTP state and usb debugging status. Now I don't have that option. I even tried the Nexus Root Toolkit - everything is fine but until it tests the driver to finally say 'ADB device not found'.
After browsing so many posts I spotted there were some posts that said there is some discrepancy between the device id as listed by the driver to what actually is usb.inf, which all is too technical and overboard for me. And finally left me thinking that it is some issue of Windows PC as someone pointed that the ADB device was detected on a MAC. So I am now thinking to give it a shot in a mac machine as a final attempt to recover my device.
Anyone please suggest a solution, apologies if this is covered by someone elsewhere in the forum if so please point me there. I will make sure that from next time I will never do a manual flash of factory image.
please help!
It sounds like you are on top of it, but haven't hit the right combination yet. Thanks for the quote and I am sorry I am unable to offer any help. As mentioned in my post, I have switched to the Galaxy Mega and was pleasantly surprised by the OTA upgrade to 4.4. Now I am trying to figure out how to root it.
I'm not sure what to do here. I'm still running 4.4.2, and wanted to upgrade to Lollipop. The upgrade failed because I am rooted with the 0x1117008 error. I found somewhere that some guy said installing the update through the Verizon Software Upgrade Assistant worked. That tool is accessible when you first plug in your phone to a PC, there is an autoplay option to run that software.
When I try to run that tool, the little spinner on my cursor spins for a few seconds, then stops, and nothing happens. Then my phone changes from "connected as installer" to "connected as <whatever I set>" The software doesn't open. I've tested all available USB modes, same thing on each one. I have the latest drivers, I've tested shutting off USB debugging.. I'm out of ideas.
I tried it on my work laptop as well, same exact thing. The software won't start on either computer (both win 7). Any ideas? Could someone possibly post the installer files from their vs980? Maybe the software I have is just bugged or something. When you first plug in your phone, a new "CD Drive" appears with the LG icon, the files are all in there. Or if anyone has any other suggestions, I'm all ears.
thanks
EDIT: Solved. I'm dumb. I had "csmg.lgmobile.com" in my hosts file for some reason.
EDIT 2: In case anyone googling ends up here, using that tool DOES indeed allow you to install Lollipop if you were getting the 0x1117008 error trying to install the normal way.