Database Users

Win7 Auto Installs Wrong Drivers

Sorry, noob here. Please help!
My computer keeps on installing the wrong drivers everytime I plug in my Nexus 7. I don't know how to stop it.
When my tablet is in bootloader mode, Windows will try to install a bootloader interface driver that does nothing.
I have already:
- Went to Devices and Printers Installation settings and clicked on never install driver software
- Went to gpedit.msc and enabled: Prevent Installation of Devices not described by other policy settings,
So now my policy will block the auto install. But when I try to manually try to try Naked Drivers, it'll say it can't find any drivers.
When my tablet is in normal mode, the adb drivers comes back on.
I'm just trying to boot to recovery so I can install a new rom through the command prompt. Current rom is too unstable to do anything, new rom is already on the internal sdcard.
If any has any solutions, please let me know.
Thanks!

It sounds like you did things to prevent driver installation. But you need to install the correct drivers for things to work. Getting the correct drivers installed seems to be the biggest issue people have in being able to connect to a pc or use adb or fastboot. I know I installed the drivers from a root toolkit, installed rsd lite, android sdk, motohelper, etc. and still couldn't connect. Then I installed the pda.net app on the N7 and installed pda.net for android on my pc. Finally it worked and I can reliably connect to the pc, use adb and fastboot, and recognize the N7.
If all you are trying to do is get into recovery, why don't you just power off, hold the vol down and power until the screen comes on, use the up vol to change the menu to recovery, then hit the power button to enter recovery. Then you can wipe and flash. I hope I got those commands right. I'm using cwm recovery and I can get there like that. Usually, I just use Rom Manager to boot into recovery.

pdanet was what worked for me as well. none of the others did.
Sent from my Nexus 7

Thanks guys. that did the trick!
Sent from my Nexus 7 using xda app-developers app

[Q] Can go to fastboot but USB device not detected by PC

I did OTA update to 4.3 of my N7 3G which was rooted and unlocked (I know now I shouldn't have done it...).
I got an error at the end of the update (when was installing radio).
Rebooted, and got stuck in the google loop...
NOW, I CAN ENTER FASTBOOT MODE, BUT THE PROBLEM IS THAT THE USB DEVICE IS NO MORE DETECTED BY THE PC (I tried Windows XP, Windows 7, Linux), so I cannot re-flash it... It's not a driver's issue, because at USB level the N7 is not even detected when connected to the PC (for instance, dmesg shows nothing in ubuntu and windows does not "beep").
Is it possible that that was corrupted only the "USB stack" of the bootloader??? I could not find a similar issue in this or other forums (??).
Is there any chance to get the USB working again?
Is there any chance to send it for repair to ASUS (I bought it one month ago) with this described symptoms and with the "unlocked" icon on power on?
Is there a payed service to flash it with JTAG?
Thanks to anyone who can give me a clue...

Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot

c0ldblooded said:
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
Click to expand...
Click to collapse
I solved by sending it to assistance. Excellent service by ASUS... I did not have to pay although the tablet was unlocked/rooted.
Andrea.

since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.

dilldoe said:
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
Click to expand...
Click to collapse
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea

andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
Exactly the case. Unfortunately I can't send it to ASUS

andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?

dilldoe said:
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
Click to expand...
Click to collapse
That's the point: I could boot into fastboot but 'fastboot device' was not detected by the PC (so I could not re-flash it). Now if I boot into fastboot the PC correctly detects the device...
What I find very, very strange is that an OTA update to 4.3 caused the USB port to stop working!! From what I read googling around, even with a problem during a system update going to fastboot mode (on + volume down) should always allow a connection to the PC for reflashing, or, at least, you could enter APX mode (on + volume up), which is an even lower level mode that is detected by the PC with different drivers (for direct programming, but need encryption key and SW not yet available for Nexus 7).
Maybe it was just a coincidence: an USB hardware failure just before I did the OTA update, which I realized only afterwards, when I needed USB for reflashing...
However the ASUS Service Repair Report states:
Problem/Symptoms: Pad Battery can't be charged. OS ERROR
Replaced Part:
ME370TG BAT COSLI-POLY FPAC
ME370TG MAIN_BD.1G/T30L/NFC
The first one looks the battery (????)
The second sounds like the mainboard...
Andrea

ADB Drivers not working Windows FIX

The drivers have been tricky with the Amazon Fire to say the least, and this seems to be because windows recognizes the driver as unsigned. To get around this issue, you will need to temporarily enable installation of drivers that are unsigned.
First go to Settings>Update and recovery.
from there click on advanced startup.
Your PC should say "please wait" then pull up a menu.
In this menu click on "troubleshoot" then click "start up settings"
Your PC will now restart
The PC will now boot into Startup Settings. Click 7 on your keyboard to disable driver enforcement then hit enter.
Your PC will restart once more.
Now your fire drivers should install as they are intended. Allowing installation of unsigned drivers can be a security risk, so once you have completed this process and installed the drivers reboot your PC and windows will automatically turn Driver Signature Verification on once again.

its smart to uninstall the fire drivers and reinstall them using the driver signature mode to make sure theyre installed correctly.
its also worth noting that in my case, the device needed a different driver from the downloaded for each mode (normal/on, fastboot, sideload), there is another thread on here for this but Ill add it here just in case someone else stumbles upon this first.
when installing the drivers in device signature mode, youll want to put the device in all 3 states while in signature mode to make sure you dont run into any problems trying to return the device to stock or moving on from fastboot etc. ( i did this, it was scary..)
1. when installing the drivers in signature mode youll come across 3 different drivers to choose from, the first driver "android ABD interface" is for when the device is in normal/on mode.
2. youll need to next boot the device into fastboot mode, i used the rootjunky amazon fire supertool and booted the device to fastboot, then disconnect and reconnected it to my pc and chose the second adb usb driver "android bootloader interface"
2. after installing that driver disconnect the device from the computer and power it down. power the device into the recovery mode by shutting it down then holding volume down and power (when holding the device in portrait orientation the volume down button is the one to the left) and navigate to the option that requires you to connect your device to a PC to load software (sorry i cant remember what option it is) it will say something like its waiting for a connection, connect the device to the PC and install the final driver "android composite ADB interface" now every facet of operation should have a driver, reboot your PC out of driver signature mode and if you were in the same boat as me, you should be able to sideload back to the android os, and flash roms or whatever else.

Bricked Oneplus 2 Not Connecting To PC

- How My Phone Got Bricked?: (Chinese Version Oneplus 2) I Was On Oxygen OS 3.0 And TWRP 3.0 And I Decided To Flash The Resurrection Remix ROM, I Did A Full Wipe And I Installed The Rom And It Failed To Installed The ROM. Now My Phone Is In A Bootloop With No OS Installed. I Have The Chinese Version OP2
- Current State Of My Device: My Device Is In A Bootloop With No OS Installed, I Did Notice That My Phone Was Not Being Recognized VIA Fastboot & ADB On My PC. I Went Fastboot Mode And My Phone Is Not Being Recognized By PC, And I Went To TWRP, ADB Was Not Working And ADB Sideload Is Not Working. I Also Tried A USB OTG With A USB Drive And Still TWRP Recovery Is Not Recognizing It. How Ever When I Connect My Device To PC And Check Device Manager And Press Scan For Hard Ware Changes My Device Shows Up As "COM 1". I Also Did Try To Put My Phone Into Qualcomm Mode Trying Alot Of Key Combinations But My Phone Is Not Getting Into Qualcomm Mode Or It Just Might Be Me Since I Heard Its Tricky For The Phone To Get Into Qualcomm Mode. I Did Try One Click ADB And Fastboot Installed And Qualcomm USB Driver, Still No Luck. And I Did Try The MEGA Unbrick Guide. I Have Tried This With 3 Other Computers Which Are All Running Windows 10 And Turned Driver Signature Enforcement Off And Still No Luck, And Also A PC Running Linux Mint And Still No Luck. Please Help Me And I Will Put All Thanks On All Of Your Replies And I Really Appreciate Your Help!
- Whats Working:
- My Device Charges From The PC And Wall
- I Am Using The Official OP2 Cable
- Can Access Recovery + Fastboot
- Turns On But In A Bootloop

I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable

Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?

foomanjackel said:
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
Click to expand...
Click to collapse
Yeah I did try typing ADB devices and Fastboot devices in both twrp and fastboot. I think the issue might be the cable

evertking said:
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Click to expand...
Click to collapse
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week

fahad999 said:
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
Click to expand...
Click to collapse
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.

evertking said:
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
Click to expand...
Click to collapse
My cable did used to work with adb and fastboot before, and I did unlock the bootloader with it before. I think now the cable got broken

Same issue working cable
Same issue... but my cable is working fine. I have a 2nd OP2 and tried the qualcomm connect with my cable and volume up, and worked perfect. More over, I swapped motherboards and still didnt work. I have access to twrp on the phone and I can get into fastboot. But no way to connect to my pc

Can't use fastboot on SM-A205U

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.

.