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
Related
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.
I have been having a difficult time getting the right usb drivers for my 2013 nexus 7. I have tried the manual download fron SDK, various toolkits available (wugfresh, etc.) with no success. The furthest I got was when I tried to unlock with the "fastboot oem unlock" command, i got a "waiting on device" message.
Is there a problem with Windows Vista loading these drivers.
Please help!! I'm about to throw this tablet through the window!!
BamaRalph said:
I have been having a difficult time getting the right usb drivers for my 2013 nexus 7. I have tried the manual download fron SDK, various toolkits available (wugfresh, etc.) with no success. The furthest I got was when I tried to unlock with the "fastboot oem unlock" command, i got a "waiting on device" message.
Is there a problem with Windows Vista loading these drivers.
Please help!! I'm about to throw this tablet through the window!!
Click to expand...
Click to collapse
For adb and bootloader, use these drivers direct from Google:
http://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
You might have previous attempts at install or previous drivers blocking the proper install.
Use Nirsoft USBDeview to get rid of any old Nexus 7 entries
I did that on the wugfresh toolkit, but still have issues loading a good driver that will let me unlock!
Even worse trying to find a driver which works across multiple devices..
what makes the android USB driver situation so unstable? shouldn't the devices just meet the MTP spec and no driver updates would be needed?
(obviously that is not true, but)
It has been a painful process, at least in my case. By watching the videos it seems simple. I have seen where Samsung drivers have worked in some cases. I'm wondering if Vista has something to do with it. I couldn't get any of the wugfresh toolkit drivers to work, which even had Samsung drivers. Then, finally windows loaded a Composite Android Device driver that let me get all the way to the unlocking command then said "waiting for device"??? I really want to root this tablet!!
BamaRalph said:
I did that on the wugfresh toolkit, but still have issues loading a good driver that will let me unlock!
Click to expand...
Click to collapse
Did you try all of them I had problems to with wugfresh but I used the PDA drivers and it worked for me make sure all previous drivers are deleted.
sent from my Nexus 7 2nd gen using tapatalk 4
zim2dive said:
what makes the android USB driver situation so unstable? shouldn't the devices just meet the MTP spec and no driver updates would be needed?
Click to expand...
Click to collapse
The devices don't alway advertise themselves as MTP compatible so the OS doesn't know to use the MTP drivers. It is a bug in the implementation on those particular devices.
For example, Nexus 7 2013 advertises MTP compatibility when USB debugging is turned off, but stops doing so when USB debugging is turned on.
When I plug in my phone to my PC the only thing that happens is it begins charging. Doesn't show signs of adb working, only thing that happens beside charging is my pc says it's an Unknown Device.
I tried all sorts of things, like USB Debugging on and off, MTP on and off, PTP on and off, I think even fastboot doesn't work. I tried to install all kinds of drivers (official, unofficial, uninstalling them afterwards if they didn't work ofc), I tried Wug's toolkit, nothing. I tried killing adb server then restarting it - nope. I even tried all of my USB ports, both 2.0 and 3.0. Also tried 3 different roms/kernels (L dev preview, Purity and Mahdi), didn't work aswell.
Things seem pretty hopeless at this point :/
Download wugfresh toolkit... look In the section of driver installation... They'll help you out
Sent from my Nexus 4 using XDA Free mobile app
driver installation...
As I said, I already tried the driver thing in Wug's Toolkit. Also my Windows allows unsigned drivers.
Bump :/
monitobeko said:
Bump :/
Click to expand...
Click to collapse
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
venu123 said:
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
Click to expand...
Click to collapse
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
monitobeko said:
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
Click to expand...
Click to collapse
Might be windows 8/8.1 giving you driver signature grief. Try the Universal adb drivers:
http://www.koushikdutta.com/post/universal-adb-driver
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.
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
AOSP100 said:
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
Click to expand...
Click to collapse
Update: Replacing the Google drivers (ADB, bootloader, etc) with Samsung ones in device manager broke everything so I had to reinstall the Samsung USB drivers, and uninstall platform-tools and the Google drivers through Android Studio
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
ninjasinabag said:
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
Click to expand...
Click to collapse
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
AOSP100 said:
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
Click to expand...
Click to collapse
Yeah, sadly the a205u will probably never get root or custom ROMs. We have an extremely small chance since Samsung promised two major updates for the A20.
Either way, https://forum.xda-developers.com/android/software/tool-universal-fastboot-adb-tool-t3475832/amp/
Has the fastboot drivers if you haven't tried that one yet.
.