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

Search This thread

BrianXP7

Senior Member
Nov 16, 2011
729
279
For those with x64 machines, are you sure you enabled test mode (disables driver signature verification)?

Sent from my Nexus 7 using xda app-developers app
 
  • Like
Reactions: scandiun

dalex7777

Senior Member
Feb 4, 2010
88
7
Houston
Need help from you guys :(

can´t install the Drivers :( Error CODE 10

My prime will not work with ADB :( cant found a device .

Please someone can help me ?

my prime crashed , wanna push rom.zip to sdcard to install a new rom ...
:(:(:(

I read the guide at https://www.androidroot.mobi/nvflash-on-asus-transformer/

Also it helped me to watch WWJoshDew's video on YouTube. I honestly watched this over and over again and finally figured out what I was doing wrong. One thing is you are booting into different modes on the device, APX. ADB and recovery. These are not the same and require different combinations of up or down volume+POWER to work.

I wish I could walk you through it, but Josh does that in his video and now it's been a few months and I don't remember everything. But it is all in the guide here, which seems to be down but the Google cached version is here: http://webcache.googleusercontent.c...n-asus-transformer/+&cd=2&hl=en&ct=clnk&gl=us
 

FreyrNjord

Senior Member
Sep 2, 2011
53
1
Hello

Maybe it's been mentioned somewhere in the preceding 11 pages, but my Windows 7 doesn't support those drivers when switching from MTP to PTP, which is required to run the CyanogenMod Windows installer:
Windows was unable to install your Galaxy Nexus

Tried 0.72 and 0.73, same result.
 
Last edited:

fredgar75

Senior Member
Feb 18, 2012
2,933
1,858
Jacksonville
Hello

Maybe it's been mentioned somewhere in the preceding 11 pages, but my Windows 7 doesn't support those drivers when switching from MTP to PTP, which is required to run the CyanogenMod Windows installer:


Tried 0.72 and 0.73, same result.

Did you change the drivers directly for your device. If not then goto device manager and do so. I used these on my ex's nexus and they worked great. I also downloaded the drivers from Samsung and those worked as well.

Sent from a haunted carbon image of an EVO LTE
 

sharathnair_2190

Senior Member
May 8, 2012
86
10
Mumbai
Did you change the drivers directly for your device. If not then goto device manager and do so. I used these on my ex's nexus and they worked great. I also downloaded the drivers from Samsung and those worked as well.

Sent from a haunted carbon image of an EVO LTE

Friends even i had the same problem in Windows 7 and it worked fine with below steps...

Finally got the 4.3 updated to my Gnex.. Cured all the problems.. Guys for the ones who faced the same problem...Let me help you.

Steps :-
1. Go to the bootloader assuming that you followed all the steps i.e of unlocking the bootloader & rooting your device thru this wonderful tool (Long press power key & volume up & down key simultaneously).
2.Unplug the USB cable and re-plug it again.
3.Go to MY COMPUTER>DEVICE MANAGER> ANDROID> Now right click on the driver and uninstall it..You will be prompted whether to delete all files fr this driver...Press yes..(please make sure you remove all the ADB drivers installed)
4.Now follow step two again.
5.Windows will manually install ANDROID 1.0 i.e ADB interface.
6.Go to the tool press option 9 & let tool do his work..

I HAVE USED THIS TOOL http://forum.xda-developers.com/showthread.php?t=1392310

THATS IT.... Tool will update your phone ,it would take round about 15-20 min maybe even less then that.. A FRESH NEW LEASE OF LIFE TO GNEX.... Thank you very much MARK for this wonderful tool & NCguy - for taking time out n replyin to my post.. Much appreciated.


HIT THANKS, IF I HELPED YOU.. CHEERS ..WISHING YOU ALL A MERRY CHRISTMAS & A HAPPY NEW YEAR...
 

jpasher

Member
Jan 2, 2014
25
13
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.
 

outbackpaul

Senior Member
Oct 16, 2009
296
49
North Carolina
Yes they work for APX mode as well on the TF201, you will need to install the driver for each mode you connect your device in. ADB, Fastboot and APX.

I'm trying to get into APX mode and my TF201 isn't recognized. I tried installing the naked driver but got the attached error message.

I've tried multiple ways and just cannot get it to work. Help please.
 

Attachments

  • ScreenShot001.jpg
    ScreenShot001.jpg
    18.2 KB · Views: 106

outbackpaul

Senior Member
Oct 16, 2009
296
49
North Carolina
I'm trying to get into APX mode and my TF201 isn't recognized. I tried installing the naked driver but got the attached error message.

I've tried multiple ways and just cannot get it to work. Help please.

By the way, fastboot and adb mode works fine. It's just the APX mode that I cannot get recognized by my computer. I do have the Naked Driver installed.
 

Attachments

  • ScreenShot003.jpg
    ScreenShot003.jpg
    55.9 KB · Views: 119
Last edited:

fashion_live

Senior Member
Aug 6, 2012
507
18
Messina
My device is updated to 4.4.3

I unlocked the bootloader with toolkit 1.8.3

To reboot my tablet is blocked by a 2 hours loading. It's locked during movements of the colored balls

Why did not it work fastboot?

When I run a command, for example "fastboot oem lock", it remains blocked <waiting for device>?


I installed fastboot from SDK Tools



Drivers are installed correctly?
2im5734.jpg







when I restart the tablet and remains stationary here
2cx6ooh.jpg




start the installation of these drivers

2lvl6wg.jpg




but the installation failed
8yx7bn.jpg




Now, during the loading of colored balls, I installed the 0.72 drivers.
Android Phone Samsung / Google Nexus ADB Interface


Now what do I do for boot tablet?
 

russbird

New member
Mar 27, 2013
2
0
hail his noodliness, this works!

There is a solution for hash check, might be also interesting for Windows 8 users:

after a restart I could successfull install the drivers. :good::D

holy ****, it's 4:30 in the AM, and i've been trying to get these effing drivers installed since 9 PM... THIS DOES IT! go to hard forum, run the commands as admin, install the goddamn drivers and get on with your life. thank you THANK YOU!
 

Butel/=\

Member
Jan 28, 2016
22
2
Verona
Hi!
I downloaded "Universal Naked Driver 0.72" because I need to use APX to install TWRP on my TF101, but when I go in Device Manager and select the fold for the drivers the installation abort. My PC runs Windows 10. How can I solve?
 

Woodrow256

Senior Member
Oct 8, 2016
66
20
Jacksonville
In case anybody needs this info still. Windows 10
Select the “Start” button.
Type “startup”.
Select “Change advanced startup settings“.
Select “Restart now” under the “Advanced startup” area.
Select “Troubleshoot“.
Select “Advanced Options“.
Select “Startup Options“.
Select “Restart“.
A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
 
  • Like
Reactions: Gary_O

MrSwitch

New member
Jul 1, 2009
1
0
Www.switchbox33.com
Win 10 64bit

Having a hell of a time getting the drivers to be assigned and accepted.
Nvidia Shield Fastboot* --UND.72- driver installs without (!) but will not let me (Fastboot oem unlock)
Nvidia Shield ADB* --UND.72- driver installs with (!) No fastboot devices show up..
3.0 port loads generic driver and places it in Universal serial buss controllers, 2.0 port works and register's as Android device with the above cavat.

Hung here
trying to use other drivers like nvidia says (not compatible with system)
anyone else trying to do this from win 10 x64?
nvidia shield 2015 16gig


Unable to get past Fastboot OEM unlock.
Thanks for help in advance!
 
Jun 3, 2014
10
0
Bucharest
Hi everyone!
I hope I can find the answer to my problem here... :(
These days I wanted to upgrade my stock Asus TF101 to KitKat Android. I remember I did this in the past, 5-6 yrs ago and I reverted it back to Asus stock ROM. But yesterday I managed to brick it by using CWM recovery and trying to put the new ROM from SD card. Anyway, then I remembered about EasyFlasher (I used it in the past) and I tried to install the APX drivers.
I tried on several computers (win7, win8, win10, winxp), I get the same problem, I can't make the Naked Universal Driver to work. I am familiar with the installation procedure, but everytime I get the same yellow exclamation sign next to the Asus Transformer APX Interface in Device Manageramd the message: "This device cannot start (Code 10). A request for the USB device descriptor failed". I even tried to plug TF101 into an USB on an Ubuntu installation... same thing, can't recognise the device. As far as I undestood from the error messages, the USB device (my tablet) doesn't send any hardware ID or something like this. I even tried to change various USB setting from my computer's BIOS but no success.
When pressing VOL UP + PWR I hear the "New device detected" chime, so the APX mode button combination works as it should.
Is my TF101 dead forever?

Maybe somebody has the answer even if we are in 2020 :)
Thanks!

L.E.: I forgot to mention that I tried 2 USB cables, I even opened them to check the wires (one of them had one gren wire broken), I checked the continuity with a ohmeter, the signal gets all the way to the motherboard...so the hardware is OK with the cables. I tried to hard reset the tablet by removing the battery for a while.
 
Last edited:

t3chwizard

Senior Member
Jul 20, 2013
1,574
346

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