How to Install ADB and Device drivers automatically. Works for Windows, Linux & Mac!!

Most errors while using adb (Android debug Bridge), are either because adb was not  set up properly in the first place, or  because the right device drivers haven’t been installed. XDA member DieHappy has created an excellcent toolkit which will automatically install adb (Android Debug Bridge) as well as the appropriate device drivers for your Android phone on your computer, so that adb is able to recognize and interact with your phone.

Its called Knives-and-Forks, and is compatible with Windows, Linux and Mac. So it doesn’t matter what OS you are on, to be able to use this nifty little toolkit. This is a first release, and hence is a bit limited in features. Currently it only allows installation of adb and drivers, which by the way, is a pretty fine feature to have, in my opinion! DieHappy intends to incorporate Rooting and ROM customization features in future releases. So definitely a tool to keep your eyes on!!

I am going to cover the How-to guide for Windows & Linux. Unfortunately, I do not have a Mac that I can test this on. But Mac Users can visit the original development thread for the Mac guide.

Warning

The steps and methods included in this guide are considered risky. Please do not attempt to try this unless you know exactly what you are doing. Improper or careless usage of these tools can render your device unusable. You have been forewarned!!!

Compatibility

This toolkit is compatible with Windows, Mac OS X and Linux, and will work on any computer which is running any of these 3 Operating systems

Download Link

Knives & Forks Android Toolkit

How to use Knives & Forks on Windows

Note: I have tested this toolkit on a computer running Windows 7 32-bit

  1. Download the Knives & Forks toolkit to your PC (link provided above)
  2. Navigate to your User Profile folder and Create a new folder there. Name it “knives-and-forks“. Check the paths below depending on which OS you are running
    • For Vista, Win 7, Server 2008, Server 2009 RC2  →  c:UsersYourUserNameknives-and-forks
    • For Windows 2000, XP, Server 2003  →  c:Documents & SettingsYourUserNameknives-and-forks
  3. Extract the contents of the downloaded zip file (from Step 1) to the knives-and-forks  folder you just created in Step 2. Check screenshot make sure you have all the files
  4. Now navigate to the knives-and-forks folder in your user profile (check paths in Step 2)
  5. Find the file “Knives-and-Forks-Windows.cmd” and Double-click it. You can also cd into this folder through a command prompt and just type the command “Knives-and-Forks-Windows” without the quotes
  6. You should now see a DOS window, with the text “Loading”. The tool is now checking for Python ( a high-level programming language) which it uses. If you have Python already installed, fine, if not, the tool will automatically download it and install it for you. Check screenshot below.
  7. In case of Windows 7 and Vista, you may get a prompt to Allow or Deny installation. Select Yes
  8. Once it has installed Python, Knives & Forks will automatically bring up the Main menu in the DOS window. Check screenshot below
  9. At this point,make sure your device is plugged in, and USB debugging is enabled on your device.
  10. Type the number “1” (for the Option Device tools) at the prompt and press enter. The Main menu option will change to “Install adb & Device Drivers”
  11. Type “1” again and press enter
  12. The screen will change to something like this
  13. Press any key to continue, Win 7 and Vista users should get the Security prompt again, Select Yes
  14. It should automatically download the drivers for your device, and open up the installer which you can click through.
  15. Once the drivers are installed, it will automatically move on to Installing ADB, and prompt you to Press any key. Check screenshot below                           
  16. Pressing any key will Test the ADB installation, and return with a List of Devices Attached message with a sting of alphanumeric characters and the word device next to it. This is your phone.  Check screenshot below   
  17. The Main Menu Option will now blank out. Just type in the letter “x” (without  quotes) to exit and close the command window
  18. Now open a fresh command prompt, and type in the command “adb devices” (without quotes)
  19. You should see something like this.                                 
  20. ADB is now set up on your Windows computer!!

How to use Knives & Forks on Linux

Note: I have tested this toolkit on a computer running Ubuntu 11.10 i386. Since I do not have a spare machine, I used a USB bootable version of Ubuntu 11.10. While the test was carried out on Ubuntu, the guide should work just as well for any distribution of Linux.

  1. Download the Knives & Forks toolkit to your PC (link provided above)
  2. Go to your Home Folder in Ubuntu and create a new folder. Name it “knives-and-forks” (without quotes) See screenshot below.
  3. Extract the contents of the file downloaded in Step 1 to the knives-and-forks folder you created in Step 2. Check the screenshot below to verify if you have all the files
  4. Now open a terminal session. You can do this by pressing Alt+F2 on your computer, and typing the command “xterm” (without quotes) in the field that pops up. This will bring up the terminal.
  5. Give the script executable permissions to run (this only needs to be done once) by typing the following command in the Terminal       chmod +x ~/knives-and-forks/Knives-and-Forks-Linux.sh
  6. Now change to the knives-and-forks directory you created in Step 2 by typing the following command in Terminal                             cd ~/knives-and-forks
  7. Execute the Knives and Forks script by typing the following command     ./Knives-and-Forks-Linux.sh  (The./ prefix ensures that the script runs within the same directory)
  8. This should bring up the Knives & Forks Main menu in a new Terminal window.  See screenshot below
  9. Now Type the number “1″ (for the Option Device tools) at the prompt and press enter. The Main menu option will change to “Install adb & Device Drivers”. See screenshot below
  10. Now type the number “1” again (without quotes). The screen will change to something like in the screenshot below
  11. Press “Enter” to continue. You should see multiple lines of text flash across the screen, before it comes to rest for the next command.  See screenshot below
  12. This is the time to plug in your phone to the computer via USB cable. (Do make sure that you have enabled USB debugging on the phone. It is usually found in Developer Options in the Settings menu on your phone. The location of Developer options vary depending on ROM and Android version.) Pressing any key now, will test the ADB installation and your screen will change to something like this–see screenshot below
  13. Now Type “x” (without quotes) to exit Knives & Forks, and close the Terminal window
  14. Fire up a fresh Terminal by pressing Alt + F2 on your computer and typing “xterm” or “gnome-terminal” in the field that pops up
  15. In the new terminal window, type in the following command without quotes     “adb devices” . You should see an alphanumeric string of characters and the word “device” returned in the terminal. This is your device, and adb has recognized it!! See screenshot below 
  16. That’s it!! You are now all set up with ADB on your Linux machine.

How To Install Knives and Forks on Mac OS X

You can find the guide for Mac at the original development thread for Knives & Forks. Sorry, I couldn’t post it here as I do not have a Mac to test on.

If you found this guide helpful, do share it with your friends. You can also visit the original development thread, to check for updates to this toolkit, and to track development progress. If you need any help with setting this up on your machine, give us a shout in comments below, and we’d be glad to help out.

15 Comments

  1. Do you think this method will work on a 64-bit?

    1. Outlook not good. Using the 32 bit versions seems to make the process easier.

  2. Do you think this method will work on a 64-bit?

    1. holy_crap_this_is_boring

      Outlook not good. Using the 32 bit versions seems to make the process easier.

  3. Do you think this method will work on a 64-bit?

    1. holy_crap_this_is_boring

      Outlook not good. Using the 32 bit versions seems to make the process easier.

  4. Worked like a charm. Thanks!

    BTW I’m running Win7 64bit, had no issues so far.

  5. Worked like a charm. Thanks!

    BTW I’m running Win7 64bit, had no issues so far.

  6. Worked like a charm. Thanks!

    BTW I’m running Win7 64bit, had no issues so far.

  7. This, sadly, did not work for me (Win7 64-bit). Everything seemed to go smoothly, but the Device Driver Installation Wizard popped up with “The device driver installation wizard successfully scanned your machine but did not find any devices to be updated.” Under that, there’s a dialog full of driver names for various mobile device makers, each with the status “Not needed (No device for update present).” My LG Lucid is definitely plugged in, and so was the Nexus One I’m working with too.

  8. This, sadly, did not work for me (Win7 64-bit). Everything seemed to go smoothly, but the Device Driver Installation Wizard popped up with “The device driver installation wizard successfully scanned your machine but did not find any devices to be updated.” Under that, there’s a dialog full of driver names for various mobile device makers, each with the status “Not needed (No device for update present).” My LG Lucid is definitely plugged in, and so was the Nexus One I’m working with too.

  9. This, sadly, did not work for me (Win7 64-bit). Everything seemed to go smoothly, but the Device Driver Installation Wizard popped up with “The device driver installation wizard successfully scanned your machine but did not find any devices to be updated.” Under that, there’s a dialog full of driver names for various mobile device makers, each with the status “Not needed (No device for update present).” My LG Lucid is definitely plugged in, and so was the Nexus One I’m working with too.

  10. The link no longer works!

  11. The link no longer works!

  12. The link no longer works!

Comments are closed.