NOTE: This is an older version of the driver, a newer version is available here.
This was pulled directly from the HTC Sync 3.0.5551 installer.
HTCDriver_3.0.0.007.exe.part1.rar and HTCDriver_3.0.0.007.exe.part2.rar are the executable driver installer. The other files are the drivers for the individual platforms.
Note: The last zip is labeled Win2k, but I suspect it is also intended for use with Windows XP.
NOTE: This is an older version of the driver, a newer version is available here.
Related
Hi every body,
I just downloaded the last Version of Zeno Sloim USB Host Drivers 2013.3. I unpacked the file and copied the *.cab and the PPC- Install- file to the sd-card of my Loox 718. I am running WM2003 but I get an error message saying the cab is not a valid file for Windows CE Setup. Did I miss something or what do I have to do in order to install the the new Driver?
Thanks in advaned
RB1109
Latest HTC Drivers
HTC Sync Manager v2.1.55.0
Latest Driver Version (HTC Sync): 4.0.1.001
Latest HTC Sync Manager v2.1.55.0
For those who don't want to have to download 120 some MB of bloatware called HTC Sync
Quote:Instructions:
Determine if your system is 32-bit or 64-bit
Download the BMP Driver for your OS type (x86 version if on 32-bit, x64 if on 64-bit)
Download the newest HTCDrivers file (choose either the "EXE" or "MSI" driver file, but not both)
Disable any antivirus program(s) present
Run both files downloaded above (the BMP.msi and the HTCDriver file)
Re-enable your antivirus program(s)
Updated on 9.Sep.13
Quote:
Links
http://forum.xda-developers.com/showthread.php?t=2217396
Pardon me if there is already a thread that has these, but I couldn't for the life of me find them anywhere. So I downloaded the latest SDK and pulled the binaries [file android-sdk_r22.3-linux.tgz, works on Android 4.4.2].
Should work on 32 and 64-bit [tested on 64-bit].
adb_fastboot-1.0.31.bz2 - 0.58MB - https://www.mediafire.com/?8guoc2ijera2jqw
Introduction
If you get your hands on a device with Cyanogen OS preinstalled and there is no factory image for it published by Cyanogen Inc. yet, then this script is for you. It constructs download links of factory image from a device running Cyanogen OS.
There are different files for a factory image: signed fastboot flashable zip, signed zip & boot-debuggable image.
Signed fastboot flashable zip: It contains the complete rom and can overwrite everything including your data partition. These cannot be flashed via recovery - extract their contents and flash via fastboot. An unlocked bootloader is required.
Signed zip: Normal recovery-flashable zip that contains just the system and kernel (they won't overwrite your data partition).
Boot-debuggable image: It is boot image/kernel that enables adb root and the developer menu options.
Requirements
1. Windows Vista or newer. 2000/XP should also work if choice.exe is present. Linux & OSX users should check the Python port.
2. Properly installed adb driver; see here.
3. Properly configured adb_usb.ini (optional); see here.
4. A device with regular Cyanogen OS (testing versions aren't supported) installed; list is here.
Download
https://github.com/Titokhan/cosfid
Usage
Download all of the files using "Download ZIP" option, extract somewhere (path with no space is recommended), connect the target device using USB cable & execute COSFID.cmd.
COSFID.py is intended for Linux & OSX users, though Windows users can run it too if Python for Windows is installed. The Python port is a quick-and-dirty one; it needs more refinement.
Don't confuse it by Cyanogen OS OTA trackers like the original one; read carefully to spot the difference.
Credit
1. qewlpal for inspirations in scripting
2. Jernej Simončič for providing Windows builds of GNU wget
3. Google for providing adb binaries under Apache license
4. Cyanogen for making Android more beautiful
Reserved for future.
Great job!
There is a way to get all ROM links for a specific model?
@bartito
Technically yes, but Cyanogen has made the tracking a little bit complicated now for 3rd parties. We also need to develop a database for historic data.
Titokhan said:
@bartito
Technically yes, but Cyanogen has made the tracking a little bit complicated now for 3rd parties. We also need to develop a database for historic data.
Click to expand...
Click to collapse
I'm refer to a way to locate new uploads.
Really not much interest on history but in the future
I recently got an ASIX AX88179 USB 3.0 to Gigabit Ethernet adapter for my Android device running CyanogenMod based on Android 5.1.1 and the 3.4.* kernel.
The drivers for the device are provided as source code and are available:
http://www.asix.com.tw/FrootAttach/driver/AX88179_178A_LINUX_DRIVER_v1.14.2_SOURCE.tar.gz
ASIX represents that the drivers are "For Android 1.x/2.x/3.x/4.x/5.x, Linux kernel 2.6.25 and later".
I attempted to compile the drivers using the CyanogenMod-included Terminal emulator App, but could not get anything to compile. It seemed that the "make" command or tool is not recognized.
I found a note in the drivers source readme file:
Code:
Prepare to build the driver, you need the Linux kernel sources installed on the
build machine, and make sure that the version of the running kernel must match
the installed kernel sources.
I found kernel sources on https://www.kernel.org/ . How do I make use of the kernel sources?
The version 3.4.* kernel is frequently updated. Should I be recompiling the driver with new, updated kernel sources every time a new kernel version is installed?
Must the drivers be compiled on the system they are to be used on?
Is there a better way to handle driver preparations or acquisitions?