[ADB/FB/APX Driver] Universal Naked Driver 0.72

Search This thread

1wayjonny

Senior Member
Jan 3, 2007
466
1,187
Universal Naked Driver 0.72
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added

32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA

I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?

I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.



Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers

Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot

Code:
[B]Windows 8 Instructions[/B]

How to Disable Driver Signature Enforcement in Windows 8:

From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.

Enjoy!
 
Last edited:

1wayjonny

Senior Member
Jan 3, 2007
466
1,187
ran out of thanks...Thanks

Welcome I just used the new root from jcase with these and all is gravy. I couldn't have released these at a better time. I had them ready last week but lost motivation to release after the bootloader being locked. In light of today's announcement I finished them and posted as soon as I got home from real life.
 

1wayjonny

Senior Member
Jan 3, 2007
466
1,187
Do these support HTC as well, or will I need to keep those drivers installed?

Not yet but this is the first package that works with all devices including HTC. I have not added them yet but I will be taking request for phones very soon, I just have to make a quick tutorial for any user to send me the ID's.

Once I add the phones its a nail in coffin scenario.
 

chris61292

Senior Member
Jan 20, 2010
151
8
Only my nexus is showing up in adb =\ any suggestions?

I have both in USB Debugging and ive tried just 1 plugged in
 

Attachments

  • DriversUgh.JPG
    DriversUgh.JPG
    49.6 KB · Views: 8,706

1wayjonny

Senior Member
Jan 3, 2007
466
1,187
Worked like a charm, this is a great thing, really appreciate it, makes it much easier to do since I have several devices I use to root etc. Keep up the great work

Thanks for the feedback!

Just so everyone's knows their is really nothing beta about this other then your phone or device may not be added yet. =)

I will try to get a next update soon but its not easy work, not hard either but tedious and I work 65+ hours a week so I will try my best guys.

The good thing is if Goggle releases a new driver no work really needs to be done going forward.
 

rossikwan

Member
Mar 11, 2010
24
1
Hong Kong
Hm your driver doesn't work with my TF-201 in ICS OTA updated and finally, I using the ASUS Sync V1.0.76 in which working perfectly in my Windows.

Ref: Google "ASUS Transformer Prime ADB driver not working with exclamation mark" for my blog post ;)
 

1wayjonny

Senior Member
Jan 3, 2007
466
1,187
Hm your driver doesn't work with my TF-201 in ICS OTA updated and finally, I using the ASUS Sync V1.0.76 in which working perfectly in my Windows.

Ref: Google "ASUS Transformer Prime ADB driver not working with exclamation mark" for my blog post ;)

Thanks for the details but I have seen not issue with the ICS update as the update would not change your device ID's which are not an OS specific.

I am sure this was a case of the having older driver files while also having multiple registry edits for the attempts of previous drivers.

I will write a small tutorial soon on how to remove old drivers thoroughly to avoid issues like this.

But these work fine with ICS and I am glad that you got your issue resolved at the end of the day.
 

Keion

Senior Member
Nov 6, 2011
1,313
352
Danville, California
Wait... How I install? Sorry if I be a n00blet but ???? I only ever seen drivers in an exe. I would be grateful if any one of you wonderful people could answer my question. Thank you and good day/night/evening/morning/afternoon.
 

vostok4

Senior Member
Aug 20, 2010
105
17
Thanks for this, I tried installing it for my Transformer Prime in Win7 x64, the drivers showed up happily (I had to force the install through device manager/browse devices/have disk).

It installed without any bangs, showed up in device manager as ASUS Transformer Prime ADB Interface or such, but adb devices doesn't show it up. I tried unplugging/replugging, uninstalling-reinstalling, nothing.

Also, with these drivers installed how can we switch between MTP mode and ADB mode? I don't want to lose access to my storage :)
 

1wayjonny

Senior Member
Jan 3, 2007
466
1,187
Thanks for this, I tried installing it for my Transformer Prime in Win7 x64, the drivers showed up happily (I had to force the install through device manager/browse devices/have disk).

It installed without any bangs, showed up in device manager as ASUS Transformer Prime ADB Interface or such, but adb devices doesn't show it up. I tried unplugging/replugging, uninstalling-reinstalling, nothing.

Also, with these drivers installed how can we switch between MTP mode and ADB mode? I don't want to lose access to my storage :)


Hello not sure why it will not show you your device when running "adb devices" but possibly from trying other drivers before?

Also this should not interfere with the MTP mode but I will check that as well.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 213
    Universal Naked Driver 0.72
    ** Google Nexus 4 Added
    ** Google Nexus 10 Added
    ** Google Nexus Q Added
    ** Google Nexus S Added

    32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
    MD5: 30D25BC073F010CA01178CD6E2C5E4FA

    I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?

    I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.



    Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers

    Code:
    Google Nexus Devices ADB & Fastboot
    Samsung Devices ADB & Fastboot
    Asus Devices ADB, Fastboot & APX
    HTC Devices ADB & Fastboot

    Code:
    [B]Windows 8 Instructions[/B]
    
    How to Disable Driver Signature Enforcement in Windows 8:
    
    From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
    Click ‘More PC Settings’.
    Click ‘General’.
    Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
    Wait a bit.
    Click ‘Troubleshoot’.
    Click ‘Advanced Options’
    Click ‘Windows Startup Settings’
    Click Restart.

    Enjoy!
    4
    ran out of thanks...Thanks

    Welcome I just used the new root from jcase with these and all is gravy. I couldn't have released these at a better time. I had them ready last week but lost motivation to release after the bootloader being locked. In light of today's announcement I finished them and posted as soon as I got home from real life.
    4
    All,

    These drivers do not include the necessary settings to fully work with the TF300T. You can make it work with a few modifications. Here's some info after my experience (these are all for Windows 7):

    Background

    These drivers are just the generic Google Android drivers with .inf files that include the hardware IDs for "supported" devices. Since most Android devices will be supported, it's just a matter of making sure the hardware IDs for a device are present in the file.

    Finding the hardware ID

    • With the device connected, open up the Device Manager (just run the program devmgmt.msc)
    • Right click on the device, go to Properties, then click on the Details tab
    • In the Property drop down, select Hardware Ids

    The hardware IDs will be listed in the box. You will use these later in the event that your hardware is not recognized.

    Finding old drivers

    First go to the Program and Features Control Panel and look for any entries related to USB drivers. Anything that says ASUS in the name could potentially be a driver, so you might need to uninstall a few things.

    After that, we need to remove any old lingering hardware entries in the device manager.

    • Open an administrator command prompt
    • Type set devmgr_show_nonpresent_devices=1 and press enter
    • Type devmgmt.msc to open up the device manager
    • On the toolbar, click View -> Show Hidden Devices

    After you do this, you should be able to see both connected and disconnected devices that your system recognizes. You need to look for any old devices related to your tablet (things with ASUS or ADB in the name are prime targets). When you find the device, right click on it, then choose Uninstall. In the popup window, make sure Delete the driver software for this device is checked (if it exists).

    At this point, you should (hopefully) have all of the old drivers cleared out and you are ready to install the naked drivers.

    Installing the naked drivers

    BEFORE YOU PLUG IN YOUR DEVICE, MAKE SURE YOU PERFORM THIS STEP!

    You must disable the feature in Windows that automatically downloads drivers for your device to avoid old drivers coming back.

    • Click on the Start Menu, then type installation. You should see a choice for Change device installation settings. Click it.
    • Select the option No, let me choose what to do, then select Never install driver software from Windows Update
    • Save changes

    Remember that drivers are needed for EACH boot mode: APX, ADB, and fastboot. This means you need to boot the devices into each of these modes, plug it in, then update the drivers (three times, once for each mode).

    Now we install the drivers.

    • Plug in your device. Windows should show the "Installing new hardware" balloon tip, then report installation failure
    • Click on the failure message to know exactly what the device is (temporarily) being called by Windows
    • Open up Device Manager and find the device with that name
    • Right click on the device, then choose Update Driver Software...
    • Choose Browse my computer for driver software
    • Point the directory to the root directory that contains the naked drivers, then click Next

    If all goes well, it should recognize your device and install the drivers. When you receive a warning about the drivers being unsigned, just choose to proceed with the install.

    Making Windows recognize the TF300T

    You will need to add the hardware IDs for the TF300T in the driver to make it recognize the ADB interface

    • Open the file android_winusb.inf in the naked drivers directory.
    • Look for the section titled [Google.NTx86] (for 32-bit systems) or [Google.NTamd64] (for 64-bit systems)
    • Add the following lines to make it recognize the TF300T hardware (it doesn't matter where, but I put it after the existing entries for the TF201 APX interface)
      Code:
      %AsusTransformerADBInterface%		= USB_Install, USB\VID_0B05&PID_4C81&REV_0232&MI_01
      %AsusTransformerADBInterface%		= USB_Install, USB\VID_0B05&PID_4C81&MI_01
      %AsusTransformerADBInterface%		= USB_Install, USB\VID_0B05&PID_4C83&REV_0232
      %AsusTransformerADBInterface%		= USB_Install, USB\VID_0B05&PID_4C83

    After the information is added, you should be able to install the drivers as usual for the device. If for some reason the device is still not recognized, you'll need to find its hardware IDs and add those to the file.

    Hopefully this helps out a bit.
    3
    Do these support HTC as well, or will I need to keep those drivers installed?

    Not yet but this is the first package that works with all devices including HTC. I have not added them yet but I will be taking request for phones very soon, I just have to make a quick tutorial for any user to send me the ID's.

    Once I add the phones its a nail in coffin scenario.
    3
    Worked like a charm, this is a great thing, really appreciate it, makes it much easier to do since I have several devices I use to root etc. Keep up the great work

    Thanks for the feedback!

    Just so everyone's knows their is really nothing beta about this other then your phone or device may not be added yet. =)

    I will try to get a next update soon but its not easy work, not hard either but tedious and I work 65+ hours a week so I will try my best guys.

    The good thing is if Goggle releases a new driver no work really needs to be done going forward.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone