Database Users

Can't get Fastboot to recognise Nexus 7 under Win7 x64

I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?

Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Same thing happening with me, i want to re-lock my bootloader but when i am in bootloader mode windows does not want to recognize the device, i have tried everything too.

Did you install the correct drivers?

When connected and in the bootloader open the device manager in windows. You should see "android 1.0" near the top.
Update that driver. It should work.
Sent from my Nexus 7 using xda premium

Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Hey, As i said earlier i was having the same problem...try switching your usb cable then try. That is what fixed my problems.

ive done all mentioned above, even tried 3 different cables, no luck, anyone have suggestions

I dont know about what you want to do, but if you want to root and unlock use the wugfresh took kit. Its the bomb and as soon as I figure out where I can thank him and give a big kudos I will give thanks.
Sent from my Nexus 7 using xda app-developers app

I could be wrong, but I don't think adb works from bootloader, but the fastboot command should. I think you can also use Google's Composite ADB Interface driver too for it (I can't reboot my N7 atm or else I'd find out).
I don't have any other android-related drivers on my system either, only Google's USB driver from the SDK. I'm also on Windows 8, but I would assume Google's USB driver would work fine on Windows 7 too.
Also certain USB filter drivers may cause issues too, such as libusb, or even AMD's USB filter driver (however, I had no problems). Or if you want to wipe out any/specific USB drivers, I recommend getting: http://www.nirsoft.net/utils/usb_devices_view.html

Can't see ADB interface driver

I was using Wug's nexus root toolkit last week, then my laptop got broken and now i have to use my friends' laptop. I don't know why but when i plug my N7 with Developer option ON and USB debugging ON. N7 root toolkit can't find my devices, it said that there is no adb interface driver, i checked "device manager" but there is only "Nexus 7" in portable devices, nothing more, no unregconized drivers. What should i do now, i want to get back to my stock rom and update to 4.1.2 but find it impossible.

i installed the driver from Wug's and reboot already but it didn't works.

lonelyredfox said:
i installed the driver from Wug's and reboot already but it didn't works.
Click to expand...
Click to collapse
Make sure you are logged on as Administrator when the drivers are installed.

I logged in as Admin, install PDA net drivers and Samsung USB driver but it didn't work, my laptop couldn't regconize my device >.<. Can somebody help me please

Not working for me either
lonelyredfox said:
I logged in as Admin, install PDA net drivers and Samsung USB driver but it didn't work, my laptop couldn't regconize my device >.<. Can somebody help me please
Click to expand...
Click to collapse
Hmm, I've tried everything too. Every suggested driver, every uninstall and reboot, every workaround and fix, and on two different laptops. I suspect that this simply just doesn't work all the time.

[Q] Windows doesn't recognize my A500 through usb

Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks

SolomonAiel said:
Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks
Click to expand...
Click to collapse
What state are you connecting it in (recovery, fastboot, normal boot)?

Moborobo test program

Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.

SolomonAiel said:
Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.
Click to expand...
Click to collapse
tick the usb debugging

and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.

SolomonAiel said:
and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.
Click to expand...
Click to collapse
Moborobo, download the program and try it. Ami has worked with me many android devices
---------- Post added at 06:30 PM ---------- Previous post was at 06:26 PM ----------
Moborobo, download the program and try it. to me has run many android devices. sorry for my English

Your computer isn't detecting it at all, or is there an error while trying to identify it? Make sure you have the proper drivers for your device on your computer.

It's an error identifying it. I do have the correct drivers the a500 drivers from either the rooting guide or the Acer website neither has worked.

Moborobo does not work with the a500. I tried it and it still says to connect my device. which it is but it's just unrecognized.

If you have installed the driver correctly, AND you had administrator rights when you installed, should be no reason why you can't get the PC to recognize the device.
First, I would advise using a good USB cable. It's been known in the past, that some folks try to use a printer cable, and sometimes it doesn't work. If changing cables doesn't work, then do the following
1. In Device Manager, try loading the drivers manually. You should be able to have it search the windows system for the drivers. If it doesn't find it, then windows is being stupid. Try installing it manually (ignore the warning it may not be compatible,.....)
2. If that doesn't work, then you can use the Google USB drivers
http://www.redmondpie.com/android-u...r-samsung-htc-asus-sony-lg-and-other-devices/
Generally, we install the Android SDK first;
http://developer.android.com/sdk/index.html
And again, have Device manager look to that directory and manually select.
Either way, this should get you up and running.
And one more thing, turn on USB Debugging in your tablet's system properties.
MD

I've tried that. Didn't seem to work as windows would still not recognize the a500. And the usb debugging has been on since the beginning.

Okay i've gotten windows to the point of being able to install the drivers from the device manager but there is no clear option to choose. Here are the choices:
acer android communications port
acer android modem
acer hs-usb android diag
acer hs-usb diagnostics
acer composite adb interface
acer fastboot interface
acer picasso usb boot-recovery driver (google driver)
android bootloader interface (google driver)
So any suggestions cause I've tried installing the adb interface, fastboot interface and the android bootloader interface and haven't gotten any good results.
Thanks

Did you try a second PC? Sometimes a machine can get wonky if you've been using for years. Using a second machine or reinstalling Windows freshly would greatly increase the chances of detection.

Yep tried about 3 machines.

SolomonAiel said:
Yep tried about 3 machines.
Click to expand...
Click to collapse
I'm having the same issue with a bricked A500 I bought on ebay
Windows just recognizes it as an MTP USB device and fails to install the drivers
I have another A500 that comes up fine as an A500 on the same PC.

Try disabling the USB debugging in developer options I have the same issue with my Win 7 x64 system

[Q] USB and recovery problems after OTA upgrade to 4.3

I took the OTA to 4.3 on my Nexus 7. It was previously unlocked and rooted, but had no kernels, etc changed. After the update ran, I lost root as expected, however, in trying to get it back, I've discovered I'm having a couple of other issues.
First, the device is no longer working properly via USB on my PCs. On both my Win 7 and Win 8 PCs, the device won't properly connect to where I can browse files or anything else. On the Win 8 computer, I see a Nexus 7 device in Device manager, but drivers won't install. I downloaded the drivers from the Asus site, but trying to manually install them doesn't work on the Win 7 machine, and on the Win 8 machine, they install but don't seem to be working with the Nexus 7 as it still shows a problem in Device Manager.
The tablet also will not boot into recovery mode. I can power it up into fastboot mode, but if I select "Recovery Mode" and hit the power button, I just got the Android with the red triangle for a few minutes before it boots back into the OS. After doing some searching, I saw where you might need to have it plugged into a PC to get it to go into recovery, but that doesn't work, either (might be tied to the USB problem).
Ideas?

Did you turn on developer options, and USB debugging? Have you tried USB connection type PTP instead of MTP?
If you have the stock recovery, the red triangle and Android are normal. You can bring up a blue options menu by pressing the power and volume up buttons from the red triangle Android.
Sent from my rooted Nexus 7 @ 49.4 mpg

exglynco said:
Did you turn on developer options, and USB debugging?
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
Yes.

Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg

exglynco said:
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
I was using the stock drivers off the Asus page. I'll look around for the two you mention. I assume they're posted on here somewhere.

And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7

Red Devil said:
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Click to expand...
Click to collapse
Without USB access? That's my dilemma.

OK, I'm getting closer. I got TWRP installed and rerooted it. I had to do the "Revoke USB debugging authorizations" on the Dev Options screen. Then it would work via ADB.
Still not browsing files yet on my desktop, but at least I know I'm talking to it. So now I'll play with the driver installation a bit.
EDIT: Well, drivers reinstalled for about the 4th time, and it's still not allowing me to browse files from my desktop. Galaxy S4 works fine as soon as I plug it in, even if I also uninstall it's drivers. Ideas? I obviously have it working over USB because I can give it commands and reboot it via the PC.

OK, try this one. Plug in your tablet to pc, go to hardware manager, find your Android Device then choose Uninstall (choose Remove all drivers for this device), unplug and plug in your tablet again. Your Windows should discover few new devices (mine has discovered three) and download drivers for them then you should see Android ADB Interface in Android Devices and Nexus 7 in Mobile Devices.
--edit--
I've solved my issue
http://forum.xda-developers.com/showthread.php?p=44322739#post44322739

Already been done that road multiple times.

have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.

xxut said:
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
Click to expand...
Click to collapse
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta

SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I personally did all of those things. After having the Nexus "forget" all the other PC authorizations on the dev screen, I finally got it to accept ADB commands, just not to properly install drivers that would allow me to browse files like it had done on 4.2.

SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.

xxut said:
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
Click to expand...
Click to collapse
Try turning off usb debugging. My tablet cannot connect to pc but with usb debugging off it at least recognises tablet as a media device and this enables me to view its files
.but still the problem of not being able to root

[Q] Wugs Nexus Root Toolkit stuck on "ADB Device Not Found"

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.