Hey, I was wondering if anyone had a link to download the HTC Bootloader drivers. It fails when I try and load "something" in Windows.
Thanks.
p.s: This will lead to good things...
The only drivers that I am aware of are the ones that are in the Android SDK Toolbox and in the HTC Sync program. Correct me if I am wrong, but as far as I know, they aren't specific drivers ie "bootloader" drivers. They are just drivers to get your comp to recognize the phone when its attached.
I'm assuming this is something you're expirementing with to get root via the adb in recovery, if so, good luck.
-------------------------------------
Sent via the XDA Tapatalk App
Hi crax0r,
The folks at Android (aka Google) provide these instructions for installing the drivers. It involves installing their SDK first, and installing Java for that, and an IDE called eclipse.... UGH.
The HTC "Sync" Application that hoovnick is referring to can be found here.
It has been so long ago that I installed drivers (on a WinXp x32 laptop) that I can't remember what order I did things in, whether or not the driver used by HTC sync is sufficient for fastboot but not adb (or vice versa), whether I did the SDK install first, etc etc etc. As a matter of fact, it's been so long ago that the computer that I did it on is now dead, and here I am using a Linux machine.
For all I know, the order you do things in affects the outcome - it sure seems like a lot of folks with Windows 7 complained about driver troubles.
One thing is for sure, though - setting up the entire Android SDK (+ Java + Eclipse + ...) in order to install a device driver has to be the worlds most roundabout way of doing a driver install.
If you are considering using the "fastboot" method to install Amon_RA's recovery boot, you might try just installing HTC Sync first, and see if that is sufficient for getting fastboot talking to the phone. That install is way, way easier than setting up the SDK to get a driver installed.
The other thing which is an option, if you are a little bit Linux-savvy, is to boot one of those "Live CDs" (Ubuntu, SuSe, etc) on your PC - there are no drivers to install in the case of Linux, you just need to be running as "root" on the Live (linux) CD to get fastboot to talk to the phone. The downloads (fastboot for Linux and the Amon_RA recovery image) are small, and they will both easily fit in the /tmp folder of the Linux (Live CD) boot on the PC.
Once you have Amon_RA on the phone, you won't need the SDK any longer, unless you want to start doing dev-like things; that's why a one-time boot into Linux would also work.
bftb0
I <3 Ubuntu. It's amazing!
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
crax0r said:
It's OK. I'm running Ubuntu now.
Click to expand...
Click to collapse
Excellent. Just remember to always run fastboot as root, and if using adb, then the first time after you boot (the PC), run adb as root.
The reason is that by default, Ubuntu won't let an unprivileged user access the USB.
Since I have adb and fastboot in my Ubuntu (regular user) PATH, I usually just do a
$ sudo `which adb` blah-blah-blah
or
$ sudo `which fastboot` blah-blah-blah
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
I don't know - I've already forgotten everything I did with the driver install in Windows, and I don't currently have a working Windows machine. Sorry I can't be of more help. As I said, the troubles people have been having seem to depend on which version of Windows (Xp/Vista/7), whether its x32 or x64, phase of the moon, etc. Seems like people run into snags on Win7 or x64 versions of Windows more than Xp-32, but I don't know why that is.
Keep plugging away at it. If you are looking for resources to help resolve the problem, I would go look at docs relating to Windows driver install troubleshooting - the driver install problem seems to be a Windows issue, not really anything to do with the SDK.
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
Sounds like what happened to me. i had to hit the icon at the top of my phone that showed the usb cable.. i had to switch charge only to disk drive "mount as disk drive"... folder popped right up on my windows machine asking how i wanted to open the file
I have the SDK running and my phone being recognized on my computer with Vista but I have another one running XP 32 bit and windows will NOT recognize the .inf? Any ideas? I deleted all previous HTC drivers and tried that approach but nothing seems to be working.
Related
Hi.
I'm trying to make some custom native software for android but I need some help getting started.
What I have done so far is getting a HTC Hero, GSM version.
Flashed a custom rooted ROM. update-hero-generic-2.73.405.38-rooted-signed.zip
Installed the sdk and ndk on Windows.
Downloaded and built the open source android project in a VMWare ubuntu image.
What I'm trying to do now is to get ADB talking to my Hero.
I have USB debugging on in the applications->development menu on in the Hero.
When I attach the phone to my XP PC it detects it and asks for drivers, I point it to drivers in android-sdk-windows\usb_driver, windows won't load them because they do not match the hardware.
I can install the driver manually but eventhough the device manager lists it as working (android phone with android composite ADB interface) adb cant find it.
adb devices just give me an empty list.
I tried this on a Windows 7 box and it seemed to work there, is there something special I need to do to get it working on XP?
Installing HTC Sync (drivers included) should resolve.
Thanks!
I actualy tried that before posting but it did not seem to work.
I now tried it again and this time I manually installed the driver in the HTC directory and now it works.
Hi,
I know there have been threads on this before but largely they just mention installing the Vista 64 bit drivers (done that). I'm running Windows 7 64 bit with the Vista 64 bit drivers and MCR 2.8 (although I was on stock and 2.2 with the same problem). HTC Sync on the phone just will not find it on the PC. I can mount the SD card with no trouble, just problems with Sync.
Any suggestions as to what I can do? Please feel free to direct me to another thread that I've missed so long as it's not just about the drivers.
Ta
M
martint235 said:
Hi,
I know there have been threads on this before but largely they just mention installing the Vista 64 bit drivers (done that). I'm running Windows 7 64 bit with the Vista 64 bit drivers and MCR 2.8 (although I was on stock and 2.2 with the same problem). HTC Sync on the phone just will not find it on the PC. I can mount the SD card with no trouble, just problems with Sync.
Any suggestions as to what I can do? Please feel free to direct me to another thread that I've missed so long as it's not just about the drivers.
Ta
M
Click to expand...
Click to collapse
In addition to HTC sync and the drivers, have you tried getting the android sdk? I know that I had issues with HTC sync finding my phone as well when syncing it to Win7 x64, so try following this guide here, it might allow HTC sync to view the phone properly. The guide teaches you how to setup adb-usb drivers which might trigger the application to know that your phone is there.
I had the same problem, turns out one of the task killer apps that I had been using had killed the sync process. Might be a plan to check if the same has happend to you.
Florida.
Hi Princedwi and Florida,
Thanks for the replies. I'm confident that my sync process is still running as I've tried numerous reboots of phone and PC so the task killer wouldn't have had chance to stop the process. However I will give it a go just to make sure.
Regarding the SDK, I'll try that when I get home. I used to have the SDK installed but then I did a re-install of windows and haven't bothered installing the sdk yet. May well work, I'll let you know.
Ta
M
Hi,
Ok tried it at home. The SDK isn't installing in the same way as I remember it doing last time. A DOS box flashes up and then disappears when I run SDK setup.exe.
Any other ideas?
Ta
M
2.0.18 is out now... should be W7 compatible -
http://www.htc.com/europe/SupportViewNews.aspx?dl_id=847&news_id=471
I had to install the Vista 64 bits drivers twice to get them working properly. The first time my hero appeared as "HTC Hero ADB". Rebooted, connected to USB, opened notifier, selected PC-Sync and reinstalled drivers (always choosing the folder where HTC should be leaving their drivers). This second time it appeared as "MY HTC" and it worked fine then. So just try again until you see the magic word "My HTC".
yrreP said:
2.0.18 is out now... should be W7 compatible -
http://www.htc.com/europe/SupportViewNews.aspx?dl_id=847&news_id=471
Click to expand...
Click to collapse
I've installed it today on my 7 64bit ultimate installation, and still no avail, i installed the vista x64 drivers and it worked.
Gr. B
martint235 said:
The SDK isn't installing in the same way as I remember it doing last time.
Click to expand...
Click to collapse
Because from android 1.6 setup process has changed in SDK. Normally it opens a windows from where you can add the version of android SDK you want and install the driver.
martint235 said:
A DOS box flashes up and then disappears when I run SDK setup.exe.
Click to expand...
Click to collapse
Same problem here with windows 7 64bit. Not sure if it's related to java environnement installed (For example when i installed JRE on my win7 64 the JAVA_HOME env variable was not set, i had to do it manually).
martint235 said:
Any other ideas?
Click to expand...
Click to collapse
Nope for now but if I found the problem be sure i'll post it here.
Ok I found the solution. My problem is that I've installed only the JRE but according to the requirements (developer.android.com/intl/fr/sdk/requirements.html) we need the JDK also.
So i've uninstalled the JRE 1.6 (64bit) I had, and installed the JDK 1.6 (32bit as i saw many ppl having problem with 64bit and android SDK). And it worked, I run againg the "SDK Setup.exe" and it opened the windows as intended.
I had the same problem, even with 2.0.18. what I did was install HTC Sync 2.0.18 (with the drivers copied in Program Files\HTC\HTC Driver\Vista_x64). then go to device manager, ADB interface, update driver, browse for a list of compatible software and choose My HTC.
after rooting it (although I'm not sure this is the cause) it happened now and then to fail to get recognized by the computer so I followed the same steps to update the drivers to My HTC.
I can't install HTC Sync 2.0.18, it gives an error about some resource file not found and closes. I tried on two different computers with the same result. Anyway 2.0.8 works fine here after I reinstalled the 64 bits driver until it was detected as "My HTC".
the same for me.
after update to version 2.0.18 my win7 64bit didnt find my phone anymore...
Howdy everyone!
Without further ado, I humbly present my gift to the community (and the #nookcolor irc channel )
This collection of scripts will automagically install:
NookColor USB ADB Drivers
The necessary adb_usb.ini file for adb to recognize the NookColor
A stripped-down copy of the Android SDK, with just the requirements for adb.exe
adb.exe is added to your %PATH% variable.
Tested on Windows 7 32/64, Windows Vista 32, Windows XP SP2/SP3
Now I realize not everyone wants the do-all end-all script, so there's two versions: one that contains the drivers AND a cut down Android SDK, or the version that only installs the ADB driver and the proper adb_usb.ini file.
Instructions for use with combo pack (please read!):
Download the combo pack
With your NookColor unplugged from your PC, run the nookcolor-easyADB.exe file and allow it to extract to c:\
Follow the on-screen instructions and wait until you see "All done!"
Plug in your NookColor, tell Windows not to use Windows Update, and let it search your computer for the proper drivers.
Once the package has finished installing, and the drivers are installed, you can just open a command prompt window and type:
Code:
adb devices
If you see your device's serial number listed, you're good to go!
Instructions for the driver-only pack:
Download the driver-only pack
Extract it somewhere on your PC (may I recommend c:\android-sdk-windows\usb_driver ?)
Run install.exe in the extracted folder and follow the onscreen prompts.
For those of you that would like, the source of the driver installer is contained in both downloads as install.au3. Driver installation is accomplished using dpinst.exe from the Windows Driver Development Kit.
Also, to avoid any confusion, I am also known as IOMonster on IRC.
Okay now for the good stuff...
DOWNLOADS:
Combo Pack (all in one!): http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
Driver only pack: http://legacyschool.us.to/nookdev/nook-usb-installer.rar
Update: 0.2 version has been released. Should fix CPU architecture errors when installing. I have also changed the download protection on my server, you should be able to use download managers now.. just keep it to a sane number of concurrent downloads by IP.
Troubleshooting:
Make sure you're rooted
Sounds dumb, but trust me, it's happened.
Make sure you haven't used ADBWireless and forgotten to disable it
Guilty here. I spent a good half hour trying to figure out why it didn't work on one of my Nooks until I realized that I had left ADBWireless on.
Check device manager for a "Nook" device, you may just have to do an "update driver" on it
Just like it says, check for any devices labeled "Nook" or "USB Composite Device" with a VID of 2080
Uninstall ALL Nook-related devices in device manager
Check device manager for any USB devices (usually USB Composite Device or USB Mass Storage) with a VID of 2080 and PID of 0002, uninstall 'em and unplug/replug your Nook.
Please note that this is a VERY initial build. It may not work for you under some circumstances, but on the few machines I've tried it on, it seemed to work for me. If you encounter any weird bugs, please let me know- I'd love to know so I can fix it.
(As a side note, I really need to standardize my nomenclature for my driver pack..)
excellent work, thank you
This is awesome! Thanks!
nice job...I had helped test it in the irc channel for ya. I def think this will be great for the community now we just need something to root and and superuser. Anyway good job
First post. Wanted to let you know it worked on my windows7 x64 machine perfectly fine. so much easier than the long way.
I'm using Windows 7 32bit. I unzipped the driver pack, clicked install.exe, then it said something about not having a correct version of windows and to get windows 7 x86 or x64, then a window popped up saying it successfully installed. Assuming that it didn't and using my extreme deduction skills, I opened DPInst.exe and it did it's thing and installed fine. Don't know what happened with install.exe but it works now. Thanks!
Strange... do you remember the exact text of the error?
My install.exe runs DPInst.exe with the /q (quiet) switch, so it shouldn't have even given an error (even if there was a legit error message thrown by DPInst.exe).
Do you think you had install.exe set for compatibility mode? (check the properties for install.exe and possibly DPInst.exe)
Thanks for the feedback! I sure hope this alleviates most of the headaches associated with installing ADB on Windows.
The links are dead, can someone post them somewhere else?
Fault when I install but it installs fine.
It installed fine even though I got this message.
EDIT::::
Ignore me - I missed uninstalling the USB device...
Worked perfectly THANK YOU!
Rylynmila said:
It installed fine even though I got this message.
Click to expand...
Click to collapse
Are you by chance running Windows 7 32-bit?
And as for the links being dead, try disabling your download manager. I see people's download managers trying to do something like 20 concurrent downloads, and my server disallows that.
Rylynmila said:
It installed fine even though I got this message.
Click to expand...
Click to collapse
Hi, I did encounter this similar error as Rylynmila.
BTW, I am running WinXP SP2.
Hm, that's strange.. this worked on my XP SP2 machine, I wonder if it's possible that some machines report the architecture differently..
I'll make a quick script that should let me figure this out easier. It's probably just an error in my script's logic for deciding which version to use.
EDIT: Newly released version has been uploaded. This should fix the CPU architecture problems.
Ah, well, just found the culprit! My AutoIT script checks the architecture of the CPU itself, not the OS you're running.
On the Windows XP machine I tried it on, the CPU itself is only a 32-bit cpu (Athlon XP 3200+), therefore it reported it right.
I should have used @OSArch rather than @CPUArch in AutoIT. Oops.
I'll make an updated version and release it later today.
cant seem to get this working on my 64 bit vista machine.
installed fine, but adb devices shows nothing
DrewLGT said:
cant seem to get this working on my 64 bit vista machine.
installed fine, but adb devices shows nothing
Click to expand...
Click to collapse
When the installer came up, did it give you any errors? Check the device manager- you should have an entry for Android Phone -> Android Composite ADB Device.
If you do have that entry, try running
Code:
adb kill-server
then
adb devices
and see what you get.
thecubed said:
When the installer came up, did it give you any errors? Check the device manager- you should have an entry for Android Phone -> Android Composite ADB Device.
If you do have that entry, try running
Code:
adb kill-server
then
adb devices
and see what you get.
Click to expand...
Click to collapse
my wife is using the NC right now, so i'll give that a try when shes done.
i have another question though. i already had adb installed for my phone, now i have it twice. can i combine the two?
If you just want the ADB driver, just download the driver only pack.
If you had adb installed already, this will overwrite it if it's installed to c:\android-sdk-windows.
no luck with easy adb
I have xp and followed the directions given in the first post in this thread for the combo pack. I now have a lot of files in c:\android-sdk-windows\ but when I follow these directions (from Nook Devs) I do not get the proper output...
"Start > Run > cmd > Enter
* cd\
* cd android-sdk-windows\platform-tools
* adb kill-server
* adb devices
If you get output that looks like the following you have succeeded:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[YOUR NOOKCOLOR SN] device"
For my output, I get the first three lines but not the
[YOUR NOOKCOLOR SN] device
I looked in Device manager and do not see anything about Android in there. I am obviously an android noob - can anyone help me? Thanks
Can't wait to try this. Thanks!
I consider myself pretty proficient with electronics and computers but I could never get ADB working on my Win7 64 PC no matter which set of instructions I followed. The benefit of this is that I've learned how to use Root Explorer to accomplish a lot of things.
EDIT: This worked perfectly on my PC, although I wasn't prompted to install any drivers. Guessing I had already done so previously trying to get this to work. Thanks much!!
A tutorial for how to get ADB and DroidExplorer up and running for your Rhodium in Windows Vista.
All this information exists in bits and pieces of posts throughout this (and other) forums, though I felt it would be helpful to compile it in one place.
If you’re running a different version of windows, the differences should generally be fairly minor. Please let me know if there’s any mistakes or modifications I should make here.
ADB refers to the Android Debug Bridge, a tool put out by google, which lets you access your android device via the USB connection for the purposes of debugging it. One particularly useful component is the ability to access your phone from your PC via a terminal window (similar to a command prompt). While not necessarily intended for this purpose, it may be used for a rudimentary level of USB access to transfer files to and from your device. It will NOT let you have any of the advanced functions that a native driver would.
Optional First Step: Download ADB from Google:
You may choose to install the SDK yourself, but this will be incorporated in your installation of DroidExplorer in step 4 if you don't already have the SDK installed.
ADB is part of the Android SDK (Software Development Kit), which you can download from:
http://developer.android.com/sdk/index.htmlInstall the most recent version for windows. For simplicity sake, I suggest you extract/install it to the root, so for example, to
C:\android-sdk-windows\
Optional:
To make your life easier, it’s a good idea to add the folder containing adb to your system environment path, so you can use adb from anywhere on your drive.
To do this, right click on My Computer, click ‘Advanced System Settings’, and then click on ‘Environment Variables’.
Choose one of the PATH variables (either for your user, or the system wide one), and add the path containing the adb.exe file. For example, if you extracted the sdk to the root of C drive as I had suggested, the path would be:
[blah blah, preceding path values] ;C:\android-sdk-windows\platform-tools\
Make sure you remember to have a semicolon preceding the path you’re adding, so windows knows it is separate from the previous entry.
Second Step: Remove previous drivers:
If you have tried to connect your phone (in android mode) to your PC, you may need to go to the device manager and remove the incorrectly-installed drivers.
Third Step: Install Drivers:
The key obstacle here is that there is no driver made by HTC (or others) specifically to connect the Rhodium in Android mode to a PC. While there may eventually one day be such a driver, we need to resort to a work-around.
Drivers Option #1:
A product called PDANet installs software on your android phone and your windows PC that then functions as a PC and device driver set. (The application has other intended uses, as you can read on their website, but these are secondary to our purpose).
Download and install the latest version of PDANet, on both your android Rhodium (via marketplace) and your PC (via the below link):
http://www.junefabrics.com/android/index.php
You will then need to follow the prompts to connect your phone, select the manufacturer (HTC), and the HTX XDA Driver will be installed. Windows security may require you to approve the installation, as the driver is unsigned. After installing, you will need to restart your computer before the drivers will work.
As part of the install, you will be asked to connect your RHOD phone to your computer via the USB cable. The new hardware wizard should pop up, and you should choose to install the driver automatically (given that you’ve previously placed the driver onto your system with PDANet – if you’ve managed to locate the specific driver file as I’ve heard rumors of, then browse to that file).
USB Debugging needs to be enabled on your device, which it is in the stock builds provided here (Settings->Applications->Development->USB debugging).
Drivers Option #2:
Install the HTC Sync Drivers - this has been described for Windows 7, although there are mixed reports as to the success. Information is in the below links:
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
Optional:
To check that your phone is working, type ‘adb devices’ into your command prompt. If you see your device, you’re good to go. (if you didn’t set the environment path to include the location of adb.exe, you’ll have to either cd to the directory first, or type
C:\android-sdk-windows\platform-tools\adb devices(if you installed the sdk elsewhere, then modify the expression appropriately
What can you do now? To see a list of commands you can use, simply type adb from the command prompt.
To use adb to send a file ‘picture.jpg’ to your sd card, in your command prompt, go to the location of the picture, and then type :
adb push picture.jpg /sdcard/to see the contents of /sdcard , type:
adb shell ls /sdcard/Read more about ADB here: http://developer.android.com/guide/developing/tools/adb.html
And for more details on setting up and using ADB, see this (the source for this workaround):
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
--
Fourth Step: Install Droid Explorer
Now that this is working, you may appreciate an application called DroidExplorer, which gives you a GUI that lets you navigate your device in a manner similar to windows explorer. From here, you can copy, move and delete files, as well as install and uninstall applications.
Download and install DroidExplorer from here:
http://de.codeplex.com/
Startup DroidExplorer, and you’re finished. Do read up on ADB and DroidExplorer on their respective pages so that you know both what you can do as well as what you might inadvertently break by blindly playing with options.
As has been said frequently on this website, if you want safe, stick to the default ‘stable’ XDAndroid install for the Rhodium, and keep your windows mobile running as a backup. If you want more, know that you’ll have lots of learning to do, and potentially may loose all the data on your phone and need to spend hours learning and fixing it. You may even brick your phone (make it unusable and unsalvageable – make it about as valuable as a brick).
Helpful Links:
The wiki for ADB on XDAndroid:
http://xdandroid.com/wiki/FAQ#What_is_ADB_.2F_How-To_ADB
Original xda thread on getting USB to work on the rhodium:
http://forum.xda-developers.com/showthread.php?t=849718
If you have any additional comments/changes to suggest, please let me know, and I’ll modify this initial post.
Heh, I always meant to turn that "original XDA thread" into an ADB tutorial for Windows users... but I just never got around to it.
Thanks for putting this together - do you mind if I reference it in the FAQ?
Just skimmed over the how-to - perhaps you should mention that in lieu of the Android SDK, you can simply download Droid Explorer. It usually takes care of the nitty gritty stuff, but pdanet seems to fill in the gaps with driver issues...
I actually found the drivers we needed (XDA in Device Manager)
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
AkumaX said:
I actually found the drivers we needed (XDA in Device Manager)
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
Click to expand...
Click to collapse
Droid Explorer took care of all the drivers for me on Windows the first time. The second time, PDA.net took care of them for me. I had issues with a ton of different drivers the second time around; even tried wiping them from the system, etc... PDA.net was the only solution that worked for me, as you can see in the linked thread I started.
arrrghhh said:
Droid Explorer took care of all the drivers for me on Windows the first time. The second time, PDA.net took care of them for me. I had issues with a ton of different drivers the second time around; even tried wiping them from the system, etc... PDA.net was the only solution that worked for me, as you can see in the linked thread I started.
Click to expand...
Click to collapse
I installed Droid Explorer and was left w/ 3 (!) Drivers missing, CDC abstract control model ACM x 2, and XDA. After I installed the HTC Sync drivers, it found the driver for XDA and then that gave the ability to let Droid Explorer install the other two *shrugs*
AkumaX, which version of windows did you get the drivers working with? Had you previously tried to install other versions of drivers, or was this 'fresh'? I haven't tried this route (being happy with my PDANet drivers working) - would you say the instructions are good on: http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
arrrghhh, please go ahead and link to this post. I had included the SDK portion because I had mis-read the droidexplorer main page, where the author stated his intent to stop updating the SDK and default to the pre-installed SDK. I see now that he intends to link to the SDK, and thus facilitate its installation for the user. I'll update that in the first post.
slycker said:
AkumaX, which version of windows did you get the drivers working with? Had you previously tried to install other versions of drivers, or was this 'fresh'? I haven't tried this route (being happy with my PDANet drivers working) - would you say the instructions are good on: http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
arrrghhh, please go ahead and link to this post. I had included the SDK portion because I had mis-read the droidexplorer main page, where the author stated his intent to stop updating the SDK and default to the pre-installed SDK. I see now that he intends to link to the SDK, and thus facilitate its installation for the user. I'll update that in the first post.
Click to expand...
Click to collapse
I'm using Win7-64 bit, so I used those drivers. It was a fresh install, and I never even thought to use PDANet, my own searching stumbled upon that thread for the HTC Sync Drivers. It could be better that you install the HTC Sync Drivers before Droid Explorer, but I'd have to find another 'clean' system to try on
AkumaX said:
I'm using Win7-64 bit, so I used those drivers. It was a fresh install, and I never even thought to use PDANet, my own searching stumbled upon that thread for the HTC Sync Drivers. It could be better that you install the HTC Sync Drivers before Droid Explorer, but I'd have to find another 'clean' system to try on
Click to expand...
Click to collapse
That's what VirtualBox is for! lol.
yes i can install usb drivers thank you !
I'm trying to get adb to detect my Electrify on Windows 8, it would seem rooting and/or installing ROMs is impossible without adb, I have my phone plugged in and all the drivers installed except one "Motorola ADB Interface" of course. The manual driver installer errors out on "Cannot detect Operating System" is there anyway around this, either forcing the driver in, or not using ADB to root?
Use a linux live cd and install the android sdk, or use something like vmware, or try to extract the driver and force it to install in device manager, or dual boot an os that isnt in beta...
Sent from my MB855
The linux live cd should actually work I didnt think about that
I found this
http://forum.xda-developers.com/showthread.php?t=741824
It says its for use with HTC phones but could it possibly work with mine?
Its a year and a half old
Will the driver for my phone be installed/available?
I would post this there but its kind of a dead thread
If you have a spare thumb drive of 4gb or larger laying around you can do a persistent install of ubuntu (or just about any other distro) using LinuxLive USB Creator, which can be found here: http://www.linuxliveusb.com/
If you're not very familiar with linux, persistence is like having your linux operating system on a thumb drive with the advantage over a live cd being that any changes you make (such as installations or saved files) are not lost upon shutdown. So you could install the android sdk (which is all you should need) and then whenever you needed it you could just boot from your thumb drive. If you need help setting up (such as installing the sdk and setting the path and what not) let me know.
-devx