Database Users

steps to upgrade using vista

hi
here i m writing the steps necessory to run upgrade utility on vista. You need to do this only once.
1. install some zipping utility like WINRAR.
2. Right click on the setup file of activesync 4.5.
3. Extract activesync 4.5 on any location.
4. Run Windows Mobile Device Center and click on Connection Settings.
5. Uncheck the Allow USB Connections and click OK.
6. Run task manager and go to services tab and check the services 'Windows
Mobile-based connectivity' and Windows Mobile 2003-based connectivity'
are started. If not, click the services button at bottom and go to next pop
up page.
7. Click the service name and press the 'play' button on the top bar.
8. Start Device Manager.Expand the 'Mobile devices' section and click
the 'HTC USB Sync.
9. Right Click and Update Driver Software.
10. Click 'Browse my computer for driver software on pop up screen.
11. Click Let me pick from a list of device drivers on my computer.
12. Click Have Disk.
13. Click 'Browse', and browse to the location where you extracted the
activesync 4.5 in 3rd step.
14. Double click wceusbsh.inf.
15. Select HTC USB Sync from the list and click Next.
16. Finish the installation process.
17. Run Task Manager Then find the WMDC.EXE and click End Process.
18. Now run the update utility and done ur update.
19. when you want to start syncing normally again run Windows Mobile
Device Center enable the allow USB connection as you disabled in step 5.

It's not correct! ...if i Uncheck the Allow USB Connections the device is not present in the list ...
The drivers not recognized by Vista....
Have you a solution?

NikitaSor said:
It's not correct! ...if i Uncheck the Allow USB Connections the device is not present in the list ...
The drivers not recognized by Vista....
Have you a solution?
Click to expand...
Click to collapse
put ur phone in bootloader and cradel it u will see vista will detect it.

There are simple instructions here:
http://forum.xda-developers.com/showthread.php?t=291723&highlight=vista

Have you ever heard about the wiki?

Vista must die today!!!!

If only new users spend some time reading wiki, everything is there... When I had to upgrade using windows vista, it worked the first time... I just read and follow the step by step instruction from wiki...

Thanks, it's work!!!

Dangit, I can get these upgrades to work when I'm at work on an XP machine, but I can't for the life of me get it to work on my home Vista 64bit machines. And yes, I HAVE read the wiki, and this post, and that post and many other posts that all give the same directions.
Disabling driver signature enforcement on the 64bit driver doesn't do any good either. It gives an error trying to install the driver.
You just gotta love computers. A ton of people can get something to work, and then a person that programs for a living will come along and can't get it to work. Makes you feel like a total goober. *sigh*
Maybe I have an old XP machine gathering dust in storage somewhere. *grumble*

ADB Drivers for XP

Searched everywhere... couldn't find anything.
The drivers for ADB must be different for windows xp... no? When trying to use the the .inf file for the drivers from the package in the windows vista/7 thread, I get the following message:
The specified location does not contain information about your hardware
Click to expand...
Click to collapse
I looked around for a different XP driver package but couldn't find one. Everythings up and running great on my home box running windows 7... but I'd like to get all set up here at work on the XP box as well.
Any help much appreciated. Thanks!

As far as I know Moto only has 2 sets of drivers tha twork on any version of windows. You jus thave to make sure you have the right set depensing on the OS. They have them separarte at 32bit or 64bit.
Anywhoo I have used both sets from this link and have no trouble. Reason I say that is at work my comp is still XP, but at home the laptop is Win7 64bit
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers

sadly... same result with those drivers. get the following message when trying to use the .inf files with those packages:
The specified location does not contain information about your hardware
Click to expand...
Click to collapse

byproxy said:
sadly... same result with those drivers. get the following message when trying to use the .inf files with those packages:
Click to expand...
Click to collapse
Don't try using the *.inf. Install the app, then go to programs in XP and run the Moto driver installation to clean, then clean and reinstall and you should be good to go. Personally in all my experience I've never had good luck pointing to the *.inf

thanks for the info. tried that and again... no dice. it sucks, but i guess it's not a huge deal. i can adb in from my win7 box no problem. would just be nice to know i could do it from this xp box as well.
oh well! thanks anyway for trying to help though!

This just makes no sense. Be tha tas it may try this link out and grab the drivers they have posted there and see if it does the trick.
http://alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167

will2live said:
This just makes no sense. Be tha tas it may try this link out and grab the drivers they have posted there and see if it does the trick.
http://alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167
Click to expand...
Click to collapse
ya... i agree. i could see the drivers not working, but the message saying that the file doesn't even have info on my device is just weird.
the drivers in that post are the first ones i tried. they worked great on my win7 box at home... but same message here on the XP box.

yea it is odd t osay the least. and the even more weird part is I have 2 comps setup with the same OS's you have and don't have the trouble. there has got to be something corrupted or casuing the XP box to not work right for whatever reason.
One suggestion I'd have is to compeltely uninstall the drivers. then grab a copy od CCleaner which is free mind you and run the registry scan to clear up unneeded crap left behind. I'd run it a couple of times until nothing else shows up on the list. Once done reboot the comp and then try the drivers again and see what you get. Ccleaner does a grea tjob of cleaning up the registry and I've used it many times for friends trying to clean things up for them when they have issues.

byproxy said:
Searched everywhere... couldn't find anything.
The drivers for ADB must be different for windows xp... no? When trying to use the the .inf file for the drivers from the package in the windows vista/7 thread, I get the following message:
I looked around for a different XP driver package but couldn't find one. Everythings up and running great on my home box running windows 7... but I'd like to get all set up here at work on the XP box as well.
Any help much appreciated. Thanks!
Click to expand...
Click to collapse
In order to get adb you need android sdk files which are located here... Android SDK

dr154 said:
In order to get adb you need android sdk files which are located here... Android SDK
Click to expand...
Click to collapse
have sdk installed already. i was running my dinc off of the XP box before i got the DX... so sdk is already installed and ready to go.
i'll try a full driver clean-out tomorrow (if i have time) and see if that might work. it's just odd that the .inf file isn't registering with windows as being associated with the phone. seems to me that if it was a problem with an already installed driver, the new driver just wouldn't work after installed. the problem here is that i can't even get XP to accept the .inf file as one that works with the phone.
anyway... will play around with it tomorrow as time permits (after all... the xp box is my work machine. lol).
thanks gents for the input.

I had the same issue with my work pc which is xp pro. If you pm me ill give you the process to fix your problem when I get into work tomorrow. -Insta
Sent from my Droid X using XDA App
Update:
Now I'm at my PC so I can just write this out for you.
1. Plug in phone to PC. Set to charge only. Make sure USB Debugging is turned on. (Need help with these steps? Ask.)
2. Right click on My Computer and go to Manage.
3. Click on Device Manager.
4. Right click on Motorola ADB Interface and go to Properties.
5. Go to the details tab and make sure hardware IDs is selected in the dropdown.
6. Download the ADBDriver_v3_Google.zip from here: alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167 (Member forever but first time post lol cant give link)
7. Extract the zip file somewhere easily found.
8. Go to the usb_driver directory extracted from the zip and open android_winusb.inf with a text editor
9. Under the Moto Sholes edit the driver hardware ID after USB\ to match that of what your hardware ID is from step 5.
10. Save and close the .inf
11. Update the driver specifying the new .inf you created. (Need help? Ask.)
12. Repeat steps as necessary to install ADB drivers for Storage Card mode.
I've added pictures to try to help explain what needs to be the same.
PM me if you have any problems with this and I'll be glad to assist you with your driver.

Insta said:
I had the same issue with my work pc which is xp pro. If you pm me ill give you the process to fix your problem when I get into work tomorrow. -Insta
Sent from my Droid X using XDA App
Update:
Now I'm at my PC so I can just write this out for you.
1. Plug in phone to PC. Set to charge only. Make sure USB Debugging is turned on. (Need help with these steps? Ask.)
2. Right click on My Computer and go to Manage.
3. Click on Device Manager.
4. Right click on Motorola ADB Interface and go to Properties.
5. Go to the details tab and make sure hardware IDs is selected in the dropdown.
6. Download the ADBDriver_v3_Google.zip from here: alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167 (Member forever but first time post lol cant give link)
7. Extract the zip file somewhere easily found.
8. Go to the usb_driver directory extracted from the zip and open android_winusb.inf with a text editor
9. Under the Moto Sholes edit the driver hardware ID after USB\ to match that of what your hardware ID is from step 5.
10. Save and close the .inf
11. Update the driver specifying the new .inf you created. (Need help? Ask.)
12. Repeat steps as necessary to install ADB drivers for Storage Card mode.
I've added pictures to try to help explain what needs to be the same.
PM me if you have any problems with this and I'll be glad to assist you with your driver.
Click to expand...
Click to collapse
You're awesome dude.. I was having this problem and these steps worked perfectly for me!

showson1 said:
You're awesome dude.. I was having this problem and these steps worked perfectly for me!
Click to expand...
Click to collapse
Glad it worked for you.

Insta said:
Glad it worked for you.
Click to expand...
Click to collapse
Worked for me too. You're a rock star. Thanks a ton for the help!!
FYI for others... the hardware ID's change for each of the USB connection modes. I just saved as two separate .inf files... one for charge only and one for mass storage mode.
Anyway, awesome instructions. Thanks again!

Insta. Can I be the father of your children? I love you that much..... haha!

Ok...that was freakin amazing!!!! I was busting my head all day at work trying to figure out why it wouldnt work.
Thanks so much!!

Also wanted to add my thanks, worked for me too.

THX
Nice work.

Insta said:
I had the same issue with my work pc which is xp pro. If you pm me ill give you the process to fix your problem when I get into work tomorrow. -Insta
Sent from my Droid X using XDA App
Update:
Now I'm at my PC so I can just write this out for you.
1. Plug in phone to PC. Set to charge only. Make sure USB Debugging is turned on. (Need help with these steps? Ask.)
2. Right click on My Computer and go to Manage.
3. Click on Device Manager.
4. Right click on Motorola ADB Interface and go to Properties.
5. Go to the details tab and make sure hardware IDs is selected in the dropdown.
6. Download the ADBDriver_v3_Google.zip from here: alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167 (Member forever but first time post lol cant give link)
7. Extract the zip file somewhere easily found.
8. Go to the usb_driver directory extracted from the zip and open android_winusb.inf with a text editor
9. Under the Moto Sholes edit the driver hardware ID after USB\ to match that of what your hardware ID is from step 5.
10. Save and close the .inf
11. Update the driver specifying the new .inf you created. (Need help? Ask.)
12. Repeat steps as necessary to install ADB drivers for Storage Card mode.
I've added pictures to try to help explain what needs to be the same.
PM me if you have any problems with this and I'll be glad to assist you with your driver.
Click to expand...
Click to collapse
Awesome! Did the trick for me as well!
I have a HTC Desire, if someone else need it, here is the lines to add to the file if you have Desire:
[Google.NTx86]
;HTC Desire
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87&MI_01
or
[Google.NTamd64]
;HTC Desire
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87&MI_01

Insta I can really use some help. I was so glad to find this thread and prayed it would work. I tried your instructions to the t but maybe i didnt understand something. when i went to update the drivers and pointed windows to the edited inf file it gave me an error saying the folder you specified doesnt contain a compatible driver blah blah. UGHHHH If only you could hear me screaming I HATE WINDOWS!!! Ok calm now, sorry for that. Please let me know what im doing wrong. Thanks

[GUIDE] ADB Driver Install for Dummies

The most simple way is this thread. I've done all the editing work for you.
This guide is based on Windows 7 Home Premium. It may be different on your computer. If you are on a Linux build or Mac, you don't need this
Steps: Difficulty: Easy/Medium
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
-Note: If it says not signed, just click next anyway
13. Wait and if it says not signed, click install drivers anyway
14. Wait until it's done, then close all of your programs
15. Press the windows key and R at the same time on your keyboard
16. Type cmd and hit enter (Command prompt will appear)
17. Copy and paste the following code into it:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini
18. Type adb kill-server
19. Type adb devices, and your device should now show up
20. Hit the thanks button below
Thanks to cajl-jbmm from MoDaCo for posting the modification required for the drivers to work

adb devices isn't saying anything.
Good day. I followed your previous steps but when I do "adb devices" I get no response. That is, no message back. When I try it once more this is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Dell>"C:\Program Files\Android\android-sdk\platform-tools\adb.exe">adb
devices
C:\Users\Dell>"C:\Program Files\Android\android-sdk\platform-tools\adb.exe">adb
devices
The process cannot access the file because it is being used by another process.
C:\Users\Dell>
Any help you have is welcomed.

I am having a similar problem.
When I type "adb devices" in command prompt, it returns with:
'adb' is not recognized as an internal or external command, operable program or batch file.
Not sure how to access adb in command prompt.

You need first to install:
Android SDK Tools (can download from archos)

I have sdk installed already
I have sdk installed already. Anymore suggestions? Thanks

baari21 said:
I have sdk installed already. Anymore suggestions? Thanks
Click to expand...
Click to collapse
Is it in your path?
Sent from my ARCHOS 80G9 using XDA Premium HD app

I got it to work. Even though there was no response stating the device was connected I tried "adb reboot" to check if the device was infact working with the adb and it was. So i got it working but perfectly. Only thing is there is no response stating the device is connected but i can live without that. Thanks for the help guys.

adb tool has moved
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK, launch the SDK and AVD Manager (execute the android tool) and install "Android SDK Platform-tools"
Please also update your PATH environment variable to include the platform-tools/ directory, so you can execute adb from any location.

I hope someone is on to help me here, i've done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
BUT... when i click next, it comes up saying....
'the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.
SO WHAT NOW????

MrLarner said:
I hope someone is on to help me here, i've done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
6. Right click and select Update Device Driver Software...
7. Select Browse my computer for driver software
8. Select Let me pick from a list of drivers installed on my computer
9. Select Show all and click next
10. Click Have Disk, then Browse
11. Go to your extracted folder and go into it, until a file called android_winusb.inf is there. Double click that (NOT android_winusb_old.inf)
12. Click OK and then Next
BUT... when i click next, it comes up saying....
'the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.
SO WHAT NOW????
Click to expand...
Click to collapse
You have a 64 bit version of Windows so it's not compatible, sorry
Sent from my HTC Desire HD using XDA

Is there anything i can do about it?
is there something else i can download instead?
or is the only option to use another computer?

MrLarner said:
Is there anything i can do about it?
is there something else i can download instead?
or is the only option to use another computer?
Click to expand...
Click to collapse
adb should perfectly work on 64 bit windows 7. I used it in the past, now I mainly use linux.
Just download the driver from ftp://support.archos.com/ARCHOS it/ADB/adb_winusb_driver.zip
Edit: also look here http://www.archos.com/support/support_tech/updates_adb.html?country=nl&lang=en
divx118

divx118 said:
adb should perfectly work on 64 bit windows 7. I used it in the past, now I mainly use linux.
Just download the driver from ftp://support.archos.com/ARCHOS it/ADB/adb_winusb_driver.zip
Edit: also look here http://www.archos.com/support/support_tech/updates_adb.html?country=nl&lang=en
divx118
Click to expand...
Click to collapse
Is that link for the driver different to the 1 i got from the opening post?
will this 1 work on windows x64?
---------- Post added at 04:20 PM ---------- Previous post was at 04:16 PM ----------
Ignore that last post, i checked it and its exactly the same as the file in the opening post.
I need a file which will work on windows x64

MrLarner said:
Is that link for the driver different to the 1 i got from the opening post?
will this 1 work on windows x64?
Click to expand...
Click to collapse
The link I posted is the original driver provided by archos and works with windows x64. Where the one in the opening post comes from I don't know.
divx118

I'm not to sure why im getting the problem then?
any idea's?

MrLarner said:
I'm not to sure why im getting the problem then?
any idea's?
Click to expand...
Click to collapse
Sorry no idea, I used that driver without problems on windows 7 64 bit.
divx118

Something else i noticed,
when i done these steps...
1. Download this zip and extract it to your desktop
2. Open the start menu, type Device Manager in the search box, then wait and the Shortcut "Device Manager" will appear above in the box. Click it. Wait a moment and Device Manager will appear
3. Enable USB Debugging on your Archos device, in Settings > Applications > Development > Tick USB Debugging and accept the warning
4. Plug in your device into your PC
5. Go back to device manager and find ADB under Unknown Devices (will have a yellow ! next to it)
all went well until i got to 5, it didnt show up unknown devices, it showed up at portable devices and it did not have a yellow ! next to it????
does it mean anything?

Yes, that means you haven't checked USB - Debugging on the device or selected MassStorage in the dropdown.
Sometimes it's not enough that it is selected, so deselect it, leave the menu, get in again and select it.

fzelle said:
Yes, that means you haven't checked USB - Debugging on the device or selected MassStorage in the dropdown.
Click to expand...
Click to collapse
I have, 100% checked usb debugging on.
and where would this mass storage be? i cant find it.
also, for me to enable usb debugging, i have to go to...
{ } Developer options.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
ok think i solved it, i managed to go to storage settings and then had the option once the usb was connected to chose between MTP - Media Device, or, PTP - Camera,
so i changed it from MTP to PTP and now when i go to device manager, its showing up as other devices and then archos has the yellow ! next to it.
does this mean i can continue now?
---------- Post added at 06:37 PM ---------- Previous post was at 06:29 PM ----------
Blimey im hitting problems at every step
i've now got to here...
17. Copy and paste the following code into it:
Code:
echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini
18. Type adb kill-server
19. Type adb devices, and your device should now show up
20. Hit the thanks button below
But when i type adb kill-server it comes up saying....
'adb' is not recognized as an internal or external command, operable program or batch file.
what now???

I've looked into it and everyone says i need to change the path???
i cant find out how to do this, or what to change the path to, someone please help!

How to get ADB interface for Lenovo IdeaPad S2110AF

Since I bought the Lenovo IdeaPad S2110AF from NY, I was searching for how to root the device and I found this thread http://forum.xda-developers.com/showthread.php?t=1896899.
But I was unable to get the ADB interface on Windows 7 x64 laptop and I found the same problem is there for most of the users. Finally last night, I could fix this issue and root my tablet. How I did it:
Download the "S2110-Root.zip" file through the above URL. and extract it to a folder.
1. Enable USB debugging under Settings-> Developer options.
2. Connect tab to computer using the provided data cable.
3. The driver for OTP will be installed in Windows. But the ADB interface may not be installed automatically.
4. Go to Device Manager (Right click My Computer and Properties, the click Device Manager).
5. You can see Other Devices-> Android
6. Right click on that and click Update driver software.
7. Click "browse my computer for driver software"
8. Click "Let me pick from a list of device drivers on my computer" rather than browsing and selecting the driver folder.
9. Click Next and then click "Have Disk" .
10. Then choose the drivers folder and the inf file (in extracted files) - \S2110-Root\Drivers\android_winusb.inf
11. Then select the ADB interface and click OK.
12. Ignore any warning message (like not signed)
That is it. Now you got an ADB interface. You will see as Samsung device on the device manager, never mind it.
Now you got the ADB interface and follow instruction to root through the URL.
Note: I am not sure is this a right place, but I just wanted to post this, it may help someone

I had some problems getting root to work.
I found out to use root with adb the display must be on and unlocked.
I started to work on recovery.img, finally I extracted it and took a look on it. Seems not too hard to get it modified and after do some play with custom roms.

Diagnosing USB Driver and ADB issues in Windows

Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Thanks to:MaxRabbit

Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse