View Single Post
  #165 (permalink)  
Old 10-12-2010, 01:24 AM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update

Quote:
Originally Posted by damage_them View Post
have no idea..nate suggested it..i guess he knows..lol
For those on Windows, Droid Explorer is an awesome tool. You can browse the file system, delete files, push files to it, run the ADB shell, and all sorts of other stuff from one simple program. Check it out at Droid Explorer

As for it not working, damage_them, if you check Device Manager, you should have three unidentified devices. Download the drivers linked below (I just took them from the Android SDK, so you can use those if you have downloaded them already), and force the unkown devices to use the basic ADB interface driver. Don't worry about figiruing out which is which

Once you have the driver for ABD forced, Droid Explorer will see it. I thought Droid Explorer would automatically install the driver for you which is why I recommended it as a starting point

http://dl.dropbox.com/u/11790134/usb_driver.zip
Reply With Quote
This post has been thanked 1 times.