Can't find device via ADB - Nexus 7 Q&A, Help & Troubleshooting

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...

Related

[Q] How to update drivers to Kindle Fire?????

So I was using the Kindle Fire Utility to root my Kindle, and that went perfectly, then I installed, the gapps, and that worked perfectly. But I planned to install CM7 on it so attempted to use the install recovery image option. (knowing now that it was broken and it was updated as I was performing this). SO it would go into a boot loop, so I was confused and tried to get it to boot in recovery with no progress. So I tried to see if it could even boot into anything besides normal, so I tried to boot it to fastboot, and now it's stuck on the Kindle Fire boot screen with no flashing.
So, I was freaking out, thinking I bricked my Kindle, and I read around, and noticed that the Utility was updated, but when I launched it I realized that it said offline. So I checked the drivers and it said "Code 10 Error" under device manager. So I uninstalled the drivers, and tried to re-install them. The computer see's my Kindle as an Unknown device, and when I plug it in it says that the USB devices attached to this computer has malfunctioned and windows does not recognize it. So, when I try to update the drivers for the unknown device I get "The Folder you specified doesn't contain a compatible software driver for your devices." Even though it does, and if I try to do it another way it says "The Driver is up to date."
I didn't mess with any permissions, or anything like that I just tried to get it to boot in recovery or in fastboot, and it's stuck and now my computer can't recognize it.
Am I SOL? Did I brick it permanently?
Any suggestions would be great. Thank you all for your help.
Manually install the drivers by selecting them from the list (don't tell Windows to automatically search for them).
TheDoctor1177 said:
So I was using the Kindle Fire Utility to root my Kindle, and that went perfectly, then I installed, the gapps, and that worked perfectly. But I planned to install CM7 on it so attempted to use the install recovery image option. (knowing now that it was broken and it was updated as I was performing this). SO it would go into a boot loop, so I was confused and tried to get it to boot in recovery with no progress. So I tried to see if it could even boot into anything besides normal, so I tried to boot it to fastboot, and now it's stuck on the Kindle Fire boot screen with no flashing.
So, I was freaking out, thinking I bricked my Kindle, and I read around, and noticed that the Utility was updated, but when I launched it I realized that it said offline. So I checked the drivers and it said "Code 10 Error" under device manager. So I uninstalled the drivers, and tried to re-install them. The computer see's my Kindle as an Unknown device, and when I plug it in it says that the USB devices attached to this computer has malfunctioned and windows does not recognize it. So, when I try to update the drivers for the unknown device I get "The Folder you specified doesn't contain a compatible software driver for your devices." Even though it does, and if I try to do it another way it says "The Driver is up to date."
I didn't mess with any permissions, or anything like that I just tried to get it to boot in recovery or in fastboot, and it's stuck and now my computer can't recognize it.
Am I SOL? Did I brick it permanently?
Any suggestions would be great. Thank you all for your help.
Click to expand...
Click to collapse
Here is the exact way to re-install the drivers again if you did not do so already...
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
You should be good now!!
Click that thanks if I helped ya
Big thanks to Jcase for Burrito Root

[Q] No OS, can't transfer files to or from phone, WHAT DO I DO?!

I realise I'm supposed to be an RC but it's been ages since I've visited XDA or even flashed anything on my phone so I need to be treated as a complete noob if possible!
So I was on PA 3.99 RC2 and tried to flash PA 4.0 BETA 6 in CWM but in a moment of pure stupidity didn't realise I may need to update the radio or bootloader. It resulted in a 'status 7' error during flashing which I understand to mean that recovery is detecting the ROM isn't compatible with the device. I've had a look at the solutions available for fixing status 7 errors but none of them worked. My backup failed on me so I can't revert to that.
My phone has no OS and is not being detected by the PC. I've tried setting up ADB using this guide (I had it on my old PC but that's completely gone) but it doesn't seem to have worked, I get a 'waiting for device' error when I try to type a fastboot command. From what I gather, this is caused by no drivers being isntalled but I don't know how to install the drivers when I can't enable USB debugging on the device and it's not detected by the PC. Typing 'adb devices' when the phone is connected in fastboot mode gives me an error saying
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
In CWM I can't mount my SD card so I can't seem to transfer files to or from the device in its current state. However, when I connect my device to the PC I do get a noise telling me it's been connected and it starts charging. I refuse to believe that I could have actually screwed myself over this easily so any suggestions are hugely appreciated even if they seem incredibly obvious or basic!
I don't know what other info may be required, my laptop is running Windows 8.1 if that helps.
I do have a friend with a heavily modded Nexus 4 who PROBABLY has a PC with the drivers and everything installed already, if there's no way I can fix it then he should be able to fix it... right?
Thanks in advance to anyone that decides to help me
UPDATE: Okay so I now have access to a PC without any of the Android SDK and stuff installed yet but my phone appears on the device manager under 'other devices' listed as 'Android' and the icon has a triangle with a yellow exclamation mark in it, is this progress?
You still don't have the drivers set up correctly. I would try the only tool I recommend, Google tool adb fastboot drivers xda.
You'll need to either push a rom on the phone using adb. Or if that doesn't work then fastboot the factory image.
jd1639 said:
You still don't have the drivers set up correctly. I would try the only tool I recommend, Google tool adb fastboot drivers xda.
You'll need to either push a rom on the phone using adb. Or if that doesn't work then fastboot the factory image.
Click to expand...
Click to collapse
Thanks, I sorted it out earlier by flashing TWRP via fastboot and then the ROM and everything seems to be working fine but for some reason my Titanium Backups aren't working, tbh I don't really care that much about my apps anyway haha

Soft brick? (No ROM installed but can sort of boot into recovery)

howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand

Huge mistake

Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.

Nexus 2012 3g bootloader issue.

I have windows 10, and am attempting to root and flash a custom recovery and ROM onto my nexus 7. Everything functions as intended until i have to enter bootloader. windows 10 is not able to recognize the device drivers when plugged in while in bootloader mode. It simply says that the device is not recognized. I read that the issue is needing to edit the .INF with updated hardware ID's for the device and reinstall the drivers using that INF file. However, trying to do that yields no results because when i uninstall the driver i cant find the device plugged in anywhere to be able to update its drivers in the device manager, and simply trying to override the devices currently installed drivers via device manager also does nothing. I even tried installing the driver update while the device was in bootloader via device manager (the device is recognized in device manager but has a yellow exclamation point and says device descriptor failed) with no results. What am i doing wrong? can anyone help? I've never had an issue this frustrating while trying to root an android device. Is it a windows 10 issue? I need a complete (and simple to understand) step-by-step please.
No help?

Categories

Resources