Develop Bugs

htc rom tool: new software to deal with ROMs (NEW RELEASE 1.1.0)

htc rom tool: new software to deal with ROMs (NEW RELEASE 1.1.4)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------
htc rom tool version 1.1.4
by Dark Simpson
--------------------------
DISCLAIMER: I WILL NOT BE RESPONSIBLE IF YOU BRICK YOUR DEVICE USING THIS TOOL
This small application makes process of working with ROM's for some new HTC devices are bit more comfortable. htc rom tool will contain several instruments to deal with ROMs or it's parts.
Now, these instruments are implemented:
1. ROM builder. With this tool you can build a ROM (*.nbh) from a rom parts (*.nb) in a comfortable interface.
The built ROM is correctly signed (with my own cert), checked for errors and is ready to download into device. The device MUST be CERTIFICATE CHECKING unlocked for this (you need to use HACKED SPL for your device), or you will get an error while flashing (it is not fatal for your device I think, but keep attention on this fact!).
There is a possibility to add new devices to build ROM for by editing program's configuration file. This is described inside the "htcrt.ini" configuration file.
In the next versions these tools will be added:
- ROM extractor (to extract all *.nbh file or only a several needed parts from it)
- Splash tool (to deal with all kinds of ROM splash screens in a comfortable manner).
- ExtRom tool (to extract and rebuild "extended ROMs")
- System tool (to extract and rebuild an OS part and, maybe, to edit some contents inside unpacked system like initial registry and so on...)
---------------
Version history
---------------
1.1.3
Now and later you can get it here:
http://www.real-radio.ru/htcrt/
1.1.0
There is a new, rewritten, fully customizable dynamic engine that allows to add support for almost any of new HTC devices
+ Updating devices list automatically through your internet connection
+ Checking of blocks file sizes to meet specified criteria for device
+ Possibility to pad smaller blocks with 0x00's to the specified size
+ Coloring of block with respect to it's status
+ New checks and configurable warnings to protect from user mistake when building
+ Saving and loading projects
+ Command line support
+ Other additions
You can see other infos in the about - information of the program.
PLEASE HELP TO IMPROVE DEVICES CONFIG FILE: If you have knowledge about internals of htc devices rom files you can help me to improve, test and check different configurations for htc devices or to add new devices into program. If you want to participate please contact me. Firstly, you can check and validate existing config file's entries for different devices. If you want to add new one - I need to know all identifiers and names of all blocks and the default sizes of different blocks (as in the original firmware) if this is applicable to prevent user mistake in future And of course if you want to cooperate with me you woud like to understand syntax of the htcrt devices config ini file
!!! Now I have a big lack of time, and I think that I will be able to start working on devices config file only with second half of January 2008 Now you can start to collect infos, make corrections and additions to config and to debug them without my participation...
1.0.1
- ! Fixed bug with filepaths with spaces in ROM builder
- Added user warning when flashin IPLs or SPL in ROM builder
- Added new devices
1.0
- The initial release

Thanx a lot

Hey guys, I need to know your opinions about this
Write down all found bugs and your wishes here, please...

I'm waiting til you add the extractor and bits (as I havent got any nbh files etc to play with)
But looks very nice and cool

looks nice, could develop into a great tool

Can this tool sign the ROMs properly or the build ROMs r to b used with SSPL?

Yes, this tool signs resulting ROM file with my own certificate and if SSPL is not validating block hashes to be signed with OEM or HTC certificate while flashing (it may check blocks to be signed properly, but not to validate), than it can be used with SSPL. Of course, the CID checking must be eliminated in loader too, or you will need to type in the utility a valid CID.
Note, that with Artemis USPL this utility works without problems.

will the HTC StarTrek support in future?

Yes, soon I will release new config with the following devices:
Artemis
Trinity
Herald
Hermes
Athena
Breeze
Gene
Love
Startrek

So it does not support older htc models like Universal?
Edit: I see the config file only Artemis & Trinity.

If the format of ROM files for devices like Universal is different than of devices I posted in previous topic, then yes, my tool will not support these models...

great job Dark Simpson
Thanks again..!

Dark Simpson said:
...or you will need to type in the utility a valid CID.
Click to expand...
Click to collapse
I could enter in boot mode on my Artemis device and I got follow info:
ARTE1000 HTCE
It's means that my CID key is HTCE?
Thanks !!

Thank u ^^;

Pocha, I think if you can flash ROM signed not by HTC in your apparatus, then you probably:
1. Have bought IMEICHECK unlock
2. Using new shiny USPL
In both cases you can leave CID for 11111111... Else (if your device have standard unmodified SPL) you can't flash ANYTHING except original HTC's (or operator's) ROM and in this case htc rom tool will not help you...

Unfortunatly for me, I bricked my Artemis when I tried to upgrade to WM6 two weeks ago, my Artemis is SIM Unlock and Cid Locked, I bought it with no carrier, and I can't use ROMs in other languages..., when my Artemis is back I will upgrade SPL and I will try your program
Thanks !!

Then try this tool and confirm the results..if u could flash then this is the BIG moment for all of us here.gr8 job simpson

Thanks for this great tool
Attached htcrt.ini with support for the following devices:
Hermes
Trinity
Artemis
Love
Herald
Athena
Kaiser
Elf
Cheetah
Breeze
Excalibur
Oxygen
Startrek

StarTrek log:
ROM build process started...
Ceating temporary unsigned ROM file...
Writing ROM header...
Writing ROM contents:
cWindows.nb: 100%
Preparing destination...
Preparing ROM signer...
Signing ROM and copying it to destination...
ERROR: Signing process is not successful. Signer service
output:
ImageHash version 1.0
ImageHash Error: Invalid value for max packet size.
[there is going usage]
An error ocurred during signing ...

I used the original OS.nb from Dopod P800W shipped ROM (= HTC Artemis) to test your program but found following error:
ROM build process started...
Ceating temporary unsigned ROM file...
Writing ROM header...
Writing ROM contents:
OS.nb: 100%
Preparing destination...
Preparing ROM signer...
Signing ROM and copying it to destination...
ERROR: Signing process is not successful. Signer service
output:
ImageHash version 1.0
ImageHash Error: Invalid value for max packet size.
What happened? Any hint?

[07/28/2008]samWMEmuKitchen v0.2b - ROM Kitchen for Windows Mobile Emulator

Hi Folks,
when I ('m trying to) cook ROMs for Asus P525 its quite annoying flashing again and again on the slightest change (debugging). Especially the translating thing is veeery time consuming.
So, I created a little ROM kitchen for the Microsoft Windows Mobile Emulator. So far, its beta state and only testet with WM6.1 images. BUT, it works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Known Bugs
Unable to install any CABs (with some SYSs it seem to work, see post #10). I'm working on that one .
How to
Place PPC_USA_GSM_VR.BIN as template in BaseROM
Run UnpackEmuRom.cmd
Modify SYS and OEM as you like
Run RepackEmuRom.cmd
Start Device Emulator using the created NewRom.bin by running RunEmulator.
07/28/2008
Fixed: This image-replacing works.
Fixed: CPU load is normal.
Fixed: OEM folders are replaced in OEM (not in SYS).
Added: The Device Emulator program itself (you can test your ROM using the new batch 3_RunEmulator.bat)
07/25/2008
Fixed: Cleaning cleaned to much.
Download
samWMEmuKitchen_0.2b.rar

OMGsh...If this works...

Bugfix: Cleaning cleaned too much
Ok, I applied a little bugfix on the cleanup cmd. Using this cleaned the (necessary) binaries for the rebuild, too (which means you had to restart the whole process - UnpackEmuRom.cmd ... - again).
With the bugfix (download above) only the repack files are cleaned (except the created ROM ). So you can run Repack-cmd and use the cleaning cmd several times.

Update
New update: 0.2beta.
Fixed: This image-replacing works now.
Fixed: CPU load is normal now.
Fixed: OEM folders are replaced in OEM now (not in SYS).
Added: The Device Emulator program itself (you can test your ROM using the new batch 3_RunEmulator.bat)
This whole thing seems to work now. I created a new Emu ROM doing the following:
Placed PPC_USA_GSM_VR.BIN as template in BaseROM
Ran UnpackEmuRom.cmd
Replaced some stuff (taken from my Asus P525 cooking)
Replaced the whole SYS folder by another one (Build 5.2.20270 AKU 1.3.1)
Added some SYS stuff (Games, Office, OneNote, RemoteDesktop, .NET 3.5)
Added some OEM stuff (new Games, Calculator from HTC, JAVA)
Ran RepackEmuRom.cmd
Started Device Emulator using the created NewRom.bin by running 3_RunEmulator.bat.
Everyone familiar with ROM cooking should have no problem reproducing this.
Have fun!
SamuelTee

2_RepackEmuROM.cmd not working ???
this error
Running BuildOS
(Please press the "play"-button and exit when its "Done.")
The system cannot execute the specified program.
The system cannot execute the specified program.
Could Not Find D:\DATA\FOR MY PPC\FOR PHAROS\samwmemukitchen_0.2b\buildpkg.wrn
Fixing modules....
Path not found - D:\DATA\FOR MY PPC\FOR PHAROS\samwmemukitchen_0.2b\temp\dump
Path not found - D:\DATA\FOR MY PPC\FOR PHAROS\samwmemukitchen_0.2b\temp\dump
Path not found - D:\DATA\FOR MY PPC\FOR PHAROS\samwmemukitchen_0.2b\temp\dump
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Create ImgFS...
'BuildImgfs.exe' is not recognized as an internal or external command,
operable program or batch file.
'make_imgfs.exe' is not recognized as an internal or external command,
operable program or batch file.
Create ROM binary...
'NBMerge' is not recognized as an internal or external command,
operable program or batch file.
Cleaning up...
The system cannot find the file specified.
The system cannot find the path specified.
The system cannot find the file specified.
Done.

To get BuildOS working you need this.

Thakyou

this ROCKS! THANKS SamuelTee!
I was able to extract and rebuild a WM6 image!
BUT...I am unable to install CABs.
every time I try I get 'Installation of CAB unsuccessful'
it'd be nice to get this to work to test custom UCs
any ideas?

You're right. I noticed that yesterday on my own cooked EmuROM and I'm currently on it. There seems to be a problem with file permissions (since you can't even create a simple file in \Temp).

HURRAY!
I was able to get CABs to install by replacing the SYS folder with the one from my personal kitchen! It's really cool, it boots exactly like my phone (requiring screen calibration and setting time zone and password etc.)
Now I have a problem with adding stuff...there just isn't any space it seems. I can't add anything that makes the combined space used by the SYS and OEM folders any bigger than the space occupied by the original SYS and OEM folders from the original ROM dump.
It'd be awesome to be able to adjust the space to match whatever romsize your device allows during cooking so that ROMs can be tested with this.
I have a Wizard which doesn't have much memory, but, still, I can't add even half the stuff to this emulator ROM than I can add to my kitchen ROM.
I wish I knew more So I could help solve this problem, but I am totally in the dark and at the mercy of your expertise, SamuelTee.

@joemanb: Can you post your SYS for download? So I can make a diff. It makes it easier pinpointing the issue. Thanks.

Your wish is my command..
http://rapidshare.com/files/134410047/SYS.zip.html

Wow this is a dream for me! Simply awesome.
I will try it tomorrow and I will send you a feedback

Hi.
Where i find: PPC_USA_GSM_VR.BIN?
It's the first step and i cannot find this file...
Thanks.

@moshinho: See first post. Its part of the Microsoft Windows Mobile 6.1 Emulator Images package. You need this as a template for your custom ROM.

SamuelTee said:
@moshinho: See first post. Its part of the Microsoft Windows Mobile 6.1 Emulator Images package. You need this as a template for your custom ROM.
Click to expand...
Click to collapse
I download that file and i install it. I know that in that package there is the PPC_USA_GSM_VR.BIN, but i cannot understand how can make it work in the step 1.
Thanks

@moshinho
Ok, lets recap.
When you downloaded the package from post one (samwmemukitchen_0.2b.rar) and extracted it, there were 3 Folders (BaseROM, DeviceEmulator, Tools). The PPC_USA_GSM_VR.BIN provided with the Emulator Image Package from Microsoft should be copied in the first one: BaseROM.

Ok I've tested it today, everything works fine but there are some troubles with some package, when adding a package, like Opera then starting the emulator the screen is black and I can not do anything.

SamuelTee said:
Ok, lets recap.
When you downloaded the package from post one (samwmemukitchen_0.2b.rar) and extracted it, there were 3 Folders (BaseROM, DeviceEmulator, Tools). The PPC_USA_GSM_VR.BIN provided with the Emulator Image Package from Microsoft should be copied in the first one: BaseROM.
Click to expand...
Click to collapse
Yes. i have the file. The problem was to find the file in my computer...
Thansk for the help.
I will try it later.

@udK
I noticed that, too. See if there's a wince.nls somewhere. That was the problem in my case: a missing wince.nls.

Android x86 working build. [no sound compiled, and bugs, wifi and fun working )

I just found http://www.androidx86.org/ and took the time to break the dsk and the iso images to build a boot.ini via grub sitting in a directory on the disk version.
Really all you need to do is winimage the dsk from the tar.gz and then grab all the files and setup grubldr in boot.init
Anyhow It booted! On my two laptops I generally get wireless (not stable), and no sound, and vesa, maybe nvidafb on m200. The ibm t60 shows hda_intel on lsmod but files seems to be missing. The m200 didn't mention sound in the console output. The graphics didn't work on the high end (black out), but vesa did. Standby doesn't seem right but thats likely google standby behavior on a unit in gimp mode. I took some video of it running on my laptops need to upload it somewhere. I will join the x86 forum here in a moment. Just wanted to share the build here. Wish it had audio.
I don't think the android build is as advanced as what is here on the phones so development wise I'm curious if I can swap the system files from the phone to the latop but homework calls. I'm uploading the build now it says 200 minutes on my very slow connection.
Can I just say download mssmissions system.img and run the system.img or will binary-arm stuff throw me thus I need to pretend I am a gentoo user and compile stuff or is it all python and java and intependent in the system.img?
Can I merge an ubuntu and android?
Any pointers as far as setting up a dev enviroment within android? You can also run android.iso vrom virtualbox and I'm pretty sure you can tweak it to get sound but I got none if anyone is interested in that. If anyone can give me any kernel advice vs compiling known linux drivers that be nice. Can i confidently think it'll work cause I have generic linux sources. Any sage advice for ati x1300 driver or a nvidia g5500 mobile card? Also my waacom didn't work on my tablet . I just wanted to post the build someone mirror it?
When its done uploading I will edit this.. Don't want the message to time out..
I was very impressed by the browsing speed of droid on the machines...
I just sent a pm to a mod who will move this thread.

dam thats actually pretty legit lol

Drool.
Thanks I thought so too! I just found http://blog.android-x86.org/2010/01/eclair-test-build-20100115.html and my. I need to study :| android crack is bad. But eclair is out so I need to give that a shot. I just did donut. Someone who is going to go crazy please go do eclair now. please compile hoards of video and sound drivers and just upload
Download Donut prebuild. Edit boot.ini and reboot
http://rapidshare.com/files/401173367/android-system.rar.html
OR!!!!!
Download this to build your own.
http://grub4dos.sourceforge.net/
http://www.winimage.com/download.htm
http://iweb.dl.sourceforge.net/project/grub4dos/WINGRUB/WINGRUB 0.02 Build 6/WINGRB0206.EXE
http://www.androidx86.org/downloads.html
http://blog.android-x86.org/2010/01/eclair-test-build-20100115.html
(I don't think you'll need the iso, get the usb disk, but the iso is cool cause it boots in virtual box. I'm having sound issue but it looks like it is loaded. )
extract android-system from android.img from gz and put into c:\android-system
download wingrub. Run it tell it to copy stage files.
C:\grub is created
edit the attached menu.lst or use the one from the android.dsk.. Copy the splash screen.xpm.gz from the dsk root to android-system, or wherever and reference it appropriately in menu.lst.
my boot.ini
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
C:\wubildr.mbr = "Ubuntu"
C:\grldr="Start GRUB4DOS"
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
notice the grldr, Recovery Console, or Ubuntu is not necessary. After you install wingrub you can copy grldr to the root of the c:\ drive. Grldr is in:
C:\Program Files\WinGrub\GRUB
there is a file called grldr_p12 rename it to grldr and put at C:\grldr
my menu.lst in c:\grub
root (hd0,0)
splashimage=/android-system/android-x86.xpm.gz
timeout=600
title Live USB - VESA Mode
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode quiet vga=788 SRC=/android-system
initrd /android-system/initrd.img
title Live USB - Debug Mode
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode vga=788 SRC=/android-system DEBUG=1
initrd /android-system/initrd.img
title Live USB - Run Android-x86 without Installation
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode quiet SRC=/android-system
initrd /android-system/initrd.img
title Installation - Install Android-x86 1.6-r2 to harddisk
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode SRC=/android-system INSTALL=1 DEBUG=
initrd /android-system/initrd.img
title Windows at (hd0,0)
root (hd0,0)
chainloader +1
As far as differences in the directions to build your own or to just download the donut prebuild, I made the build I put grub in C:\boot\grub this is not the default. Wingrub installs the stage files to C:\grub by default so in the directions I went that route. I know it works either way cause I just redid that portion following my directions and it gave me stable mute android with wifi for about 30-50 minutes. Thats the only thing different between the build and the directions, and I believe if you move C:\grub to c:\boot\grub it would still work as they are booth search path for grldr.. Anyhow..
Or go download the cdrom iso's and burn it to cdrom/usb

hehehe
I've now entered all my bugs at:
http://code.google.com/p/android-x86/issues/list
here are some screenshots..
http://code.google.com/p/android-x86/wiki/ScreenShots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks promising if motivated:
http://code.google.com/p/android-x86/wiki/CustomizeKernel
eclair install not going so well initrd.gz referenced but not included on usb image. downloading iso which is good to have anyways for virtual boot in virtualbox. I hope initrd.gz and kernel are in there, but sadly they are older too. So donut maybe better after all. I'm waiting to test eclair. The donut kernel addresses system.sfs the eclair references system.img perhaps i should convert the format : I would try to do a rename but I am downloading the iso.

What does it have common with kaiser on android???

It it relates. It's like sql.
Select Interest from community where Tangent=Related
Okay man its a stretch. I just got excited at the prospect of running android on my other hardware. I should migrate my tangent babbling soon. I shouldn't even be working on this at all. I.E. what does this have to do with physics ii?
Duh.
But, when I saw it I thought ok great I boot android I'll be better able to work on android builds here maybe help out with the phantom haret issue all you l33t experts ignore. I.e. the last post about me not being up to date on stuff is crap. Seriously goto the n00b thread and fix my haret issue with instructions as clear as these..
Also kernel compiling is kernel compiling. I should go to the pure android forum and will move there I guess. But playing with this makes it much easier to work with kaiser droid. From what I've been reading it also makes me wonder about kubuntu and droid as booting android from ubuntu on os86 was mentioned and the kernel compile process seemed straight forward, so it may work? Making it work on my system I could then download all the dev stuff and maybe spew out a cross compile; but then again I'm not some sort of gcc guru. I'm just trying to get to know it is all? Why you downing me brah?
Also this build looks way less advanced maybe I can get some kind of merge on the sources here for the benefit of my 86x. It's funny how sound is an issue on 86x as much as it is here and even that says hey maybe in the 86x world with a keyboard and mouse could soomething so generic be fixed on 86x that it fixes a kaiser issue? But I agree were now in tangent territory. Need to find a better home and give it a link in a more suitable audience/ stronger relationship area.. I mean the affinity isn't that much higher.
I just got done building the last boot.ini grub environment. I'll leave it on that note and find a better place to continue this and link this to that and start over if i continue this work/effort. I just like people in this forum so I wanted them to benefit from my download. But I only was so stoked because I forget how easy it is to download an iso and boot from it when I have to do something else cause my m200 doesn't have a cdrom. Anywho..
-----
http://rapidshare.com/files/401231657/AndroidX86_2.0_and_1.6.basefiles.rar.html
move everything in the archive to the root of C:\
Download (From: http://code.google.com/p/android-x86/downloads/list)
AndroidX86-1.6: donut
http://code.google.com/p/android-x86/downloads/detail?name=android-x86-1.6-r2.iso&can=2&q=
AndroidX86-2.0: eclair
http://code.google.com/p/android-x86/downloads/detail?name=android-x86-eeepc-2.0.iso&can=2&q=
Open the each iso (WinImage, Winrar, MagicIso, or other iso program) then extract system.sfs and place it in its respective directory under grub
(i.e:
android-x86-1.6-r2.iso extract system.sfs from iso and put in C:\Grub\android-donut
android-x86-eeepc-2.0.iso extract system.sfs from iso and put in C:\Grub\android-eclair )
Edit boot.ini to include:
C:\grldr="Start GRUB4DOS"
Happy booting!
Alternatively:
You can of course boot the iso's using virtualbox
Go here: http://code.google.com/p/android-x86/wiki/Releasenotefor20091024dailybuild
for any more info or to report a bug about it.. I'll bet I don't work on this for a while..
-----

I find this interesting, and somewhat relevant, at any rate it looks fun to play with
I may have to experiment with this myself, lol, wonder if it'll work on my spare laptop? ........
Good find Tyler

also a neat find..
http://forum.xda-developers.com/showthread.php?t=553366
Looks like emulation is horrible. Thats sad its a linux kernel and it has a host someone needs to paravirtualize android? I'm reading the android thread it seems like alsa sound should just work so I'm being a ninnny nanny by not compiling stuff into the g.d. kernel, yet bug reports are abundant for lack of certain functions on different devices. grr.
This thread maybe moving soon to:
xda-developers > Android Development and Hacking > Android Software Development ?
bummer the emulator doesn't work well.. I wonder if the x86 kernel does virtualized arm support, someone need to do that...
man this is a distracting bummer. I have to compile a kernel.. I just installed a grub ubuntu too , I need to see if I can just start android in that no matter what, I may get lucky.. maybe even luckier if someone will hook it up in the other thread ..

tyler51773 said:
But eclair is out so I need to give that a shot. I just did donut. Someone who is going to go crazy please go do eclair now. please compile hoards of video and sound drivers and just upload
Click to expand...
Click to collapse
I made a working android-x86 alpha eclair 2.1 build with gapps. Designed for aspire one but also should work on vmware and vbox. Will boot and work (somewhat) on most computers (built with generic kernel config so all available .ko drivers are there) however you may have to modprobe the drivers for ethernet and wlan for your hardware. http://www.aspireoneuser.com/forum/viewtopic.php?f=90&t=19299&p=116492&hilit=aoa110#p116492
Make a bootable usb with unetbootin from the .iso is the best way to use it and you can install to hdd too from it.

Password?
just wanted to give the above aspireone-x86 build a try but the rar is password protected?

[DRIVERS] Latest HTC Drivers [4.2.0.001]

Latest HTC Drivers
Latest HTC Drivers extracted from HTC Sync v3.3.21 and HTC Sync Manager v2.0.61.0
Latest Driver Version (HTC Sync): 4.0.1.001
Latest Driver Version (HTC Sync Manager): 4.2.0.001
BMP Drivers are the same for both sets of drivers.
For those who don't want to have to download 120 some MB of bloatware called HTC Sync
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)
Click to expand...
Click to collapse
Links
ALL DRIVER FILES: www.mediafire.com/?o10b16j5b3r3o
OEM SETUP FILES: www.mediafire.com/?1rwmleoe17akd
Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe
Updated on 4.02.13
RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
Removed duplicate x86 BMP Driver
Updated instructions with link to determine if on 32-bit or 64-bit
Updated on 3.31.13
HTCDriver_4.0.1.002.exe
HTCDriver_4.0.1.002.msi
IPTInstaller_4.0.8.msi
Updated on 3.6.13
HTC_BMP_USB_Driver_x86_1.0.5375.msi
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTCDriver_4.0.1.001.exe
HTCDriver_4.0.1.001.msi
Updated on 11.28.12
HTC BMP USB Driver_x86.msi DELETED: Turned out to be the same 1.0.5375 as above. Download from link above.
HTCDriver_3.0.0.023.msi
Click to expand...
Click to collapse
------------
MD5 CHECKSUMS
Sometimes downloading from the internet can yield a corrupt download. To prevent this, make sure you always check the md5 checksum (also known as "md5sum") of the file. This method verifies the digital integrity of the file by verifying its digital signature with the MD5 algorithm.
After you download each file, make sure to check that the md5sum matches what is given.
Code:
[LIST]
[*]25912deacc5d55528e223ec7b99705cc [B]*HTCDriver_3.0.0.023.msi[/B]
[*]220c41f3b03f42190899db8cb081b5c6 [B]*HTCDriver_4.0.1.001.exe[/B]
[*]a578d837343fe2542ecf405a630d46a0 [B]*HTCDriver_4.0.1.001.msi[/B]
[*]8223ec1c2aa71503b431a0daabb23154 [B]*HTCDriver_4.0.1.002.exe[/B]
[*]4dfbd4ae8662124d06e0a04db2065069 [B]*HTCDriver_4.0.1.002.msi[/B]
[*]bf24b0adc2f792ee4180ca545e4b60a0 [B]*HTC_BMP_USB_Driver_x32_1.0.5375.msi[/B]
[*]7b461095d56f9a6814d8f3e14cac0859 [B]*HTC_BMP_USB_Driver_x64_1.0.5375.msi[/B]
[*]96e6d181192a995214493a6828e4287d [B]*IPTInstaller_4.0.8.msi[/B]
[*]92bd34ec7787e631231c68aba392b6e7 [B]*RemoveOldHTCDriver3.exe[/B]
[*]f281d8994ab9f1315828ac2226a9bb75 [B]*HTCDriver_4.1.0.001.exe[/B]
[*]ed6d5fc5cc7dcca653f7a0beab01035d [B]*HTCDriver_4.1.0.001.msi[/B]
[*]96589c02be46fd7b85160d5b15f4c88a [B]*HTCPluginChecker.exe[/B]
[*]36ba2c8627ba18c6540bfa25be3b67fc [B]*HTCSync_3.3.21.exe[/B]
[*]a356e5c828c7cb3869dc67058e5bbc2c [B]*SyncManager_2.0.53.0.exe[/B]
[*]da1e40e478725d3e829243e84043d21f [B]*SyncManager_2.0.53.0_STRIPPED.exe[/B]
[/LIST]
Click to expand...
Click to collapse
How to check the md5sum of a file:
Windows:
For windows you need to download the md5sum binary. I recommend the one from my dev-host.
After that, copy the file you're trying to verify to the directory where where you downloaded the "md5sum.exe"
Once that is finished, do SHIFT+RIGHT CLICK (inside the folder window) and choose "Open command window here"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then type the following ("fileNameHere" must include the extension):
Code:
md5sum fileNameHere
That will output a hash, which you can compare to the ones above.
Linux: No need to download anything, md5sum binaries are included in all distros, as far as I know.
Open a terminal and type the following ("fileNameHere" must include the extension):
Code:
$ cd path/to/download/folder
$ md5sum fileNameHere
Two important notes:
This method can be used with any files you download, as long as the download site (or the dev themself) provides the correct md5sum.
If any of the digits do not match exactly, you need to download the file again.

Thanks!

Re: [DRIVERS] Latest HTC Drivers [v4.0.1.002]
heslo.rb26 said:
Thanks!
Click to expand...
Click to collapse
No problem :thumbup:

Wow thanks! This little things sometimes can be pain in the ass too

glen.ricky said:
Wow thanks! This little things sometimes can be pain in the ass too
Click to expand...
Click to collapse
Haha exactly
Plus ~15 MB versus 100 or 200 something is a lot easier to download haha

Updated OP with md5sum how-to and checksums.

Bump

The latest version is v4.1.0.001.
Cheers

Thanks I needed this
Sent from my HTC One X using Tapatalk 2

avensakias said:
The latest version is v4.1.0.001.
Cheers
Click to expand...
Click to collapse
SCREENIE OR IT DIDNT HAPPEN. Lol JK.
Yeah i know, just havent had time to upload them yet
EDIT: But thank you for reminding me, check below

Updated Drivers to version 4.1.0.001.
Two important note, from here on out I will also be including fast links for the Sync setup files (HTC Sync and Sync Manager), as well as a SyncManager_XXXXX_STRIPPED.exe which will literally be ONLY the Sync Manager program, all drivers stripped out from it (as in, it won't install any drivers, hence a much smaller file size).
You will now be able to find the FULL setup files for HTC Sync and Sync Manager inside the Original HTC Sync Folder of the linked mediafire folder in the OP. This will provide a much faster download if you do want to install either one, rather than a capped speed download from the HTC site itself.
Well here's the changelog
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe

Hi I downloaded drivers and can flash Roms n all d stuffs but it fails to recognise my phone in mtp mod plz help
Sent from my HTC One X using xda app-developers app

sripin said:
Hi I downloaded drivers and can flash Roms n all d stuffs but it fails to recognise my phone in mtp mod plz help
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Uninstall everything that has to do with the HTC drivers. Then download the latest sync manager (from above, the full version not STRIPPED) and install the drivers through that. Then quit the installation when it tries to install the actual Sync Manager

Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe

One Plus One Toolkit v1.3.2 BETA + ADB/python library - UPDATED 12/30/2014

i present to you the latest release from my secret underground laboratory.......
THE HALF-ASSED ONE PLUS ONE TOOLKIT v1.3.2 BETA!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
old screenshots because i'm lazy
UPDATED 12/30/2014
NOW ON GITHUB:
https://github.com/eudemonics/1plus1toolkit
NOW WITH MORE UNIVERSAL FEATURES TO SUPPORT ALL ANDROID DEVICES!
THERE IS A REASON THIS IS CALLED THE HALF-ASSED ONEPLUS ONE TOOLKIT. don't expect frequent regular updates. i respond to support queries when i receive them, which means whenever i check my email or log onto xda-dev, which is not very often. though i do update it every now and then. now that it's on github, you can actually get updates without me having to go update the threads on every forum to make the announcement about it being updated.
USE AT YOUR OWN RISK. i'm not responsible for anything that might happen to your device as a result of using the toolkit. if you use the correct files in the package and follow the toolkit directions onscreen, your device should be just fine. i assume if you have the technical know-how to install python, the android SDK, and run the script, then you've got a pretty good idea of what you're doing already. if you need help, send me a message. the best way to reach me, to get the quickest response, is probably on facebook, as i do not log onto xda-developers or my email accounts regularly:
http://www.facebook.com/dreamcorporation
[***this project was originally posted in the Oneplus One "General" forum, as i'd assumed "Original Android Development" was restricted to ROMs, apps, and themes. i finally read the rules, though, so i hope my toolkit is useful/creative enough to qualify to be here. i could use some beta testers if anyone's brave enough to volunteer - doesn't have to be on the oneplus one, as i am adding more and more functionality to support all android devices. am also open to ideas and suggestions - if you want any features built, just ask. maybe i'll code it for you, and give you credit for the idea too.]
REQUIREMENTS: python 2.7, android SDK, opotoolkit.py, opointro.py pyadb.py. and of course, a machine running ANY OS that supports python and the android SDK (OSX, Windows, Linux, maybe even Chromium OS?)
installation:
download and install python 2.7: https://www.python.org/downloads/
download and install android SDK: https://developer.android.com/sdk/
download toolkit package using GIT:
git clone https://github.com/eudemonics/1plus1toolkit.git 1plus1toolkit
to run from there:
cd 1plus1toolkit
python opotoolkit.py
to update:
git pull https://github.com/eudemonics/1plus1toolkit.git
it should work with the adb and fastboot binaries provided in the github project (*****if on linux rename adb to adb-mac, fastboot to fastboot-mac, adb-linux to adb, and fastboot-linux to fastboot*****), but if not, you should install the android SDK. i recommend even MORE that you create an environmental path variable to the android SDK so you can run the commands from any directory.
setting up an environmental path variable (optional - recommended):
if you're on windows you can go to my pastebin, find the only powershell script on there, and steal/adapt the code to create your own environment path variable. but it's much easier to configure in system properties - i'm not on windows right now so these may not be exact instructions, but you should be able to right click on "my computer", select "properties", go to the "environment" tab in system settings, and add the environment path there. linux and OSX users just need to add the android SDK directory to their ~/.bash_profile or ~/.bashsrc or wherever environment paths are defined. if you still don't understand environmental path variables or symbolic links, i highly recommend google (or startpage.com, the private version).
if you don't want to go to the trouble of creating the environmental path variables, and you want to use the android SDK on your computer, then just extract all the files from the ZIP into your android SDK directory.
how to run the toolkit:
plug phone to computer via USB, turn on android debugging.
open command prompt or terminal window to scripts directory. start toolkit by entering:
"python opotoolkit.py"
if everything is installed and in the right places, you should see a menu like the attached screenshot. if for some reason you get a permission denied error, try launching the command prompt or terminal as administrator or superuser.
i'll continue working on it and adding more when i can so keep checking this space. everything's open source; use, share, steal whatever you want from the code. some credit would be nice, though.
you can use the pyadb.py library to incorporate adb/fastboot commands into your own python projects. i'll be adding more features to that, but for now most of the common features are covered.
here's the github link - it still won't acknowledge my repository exists, and if i try to create it again locally it gives me a fatal error. [[email protected]#[email protected]#] let's just say github and i are not exactly BFF's. you can check to see if the files ever manage to appear: https://github.com/eudemonics/1plus1toolkit
i've been working to expand this so it can be used with all android devices, though it'll require people to supply their own device files to use with it! just because the toolkit can flash device firmware DOES NOT MEAN that the included files meant for the oneplus one will work on a NON oneplus one device! hopefully that's not something i needed to emphasize. if there is enough positive feedback and support i'll create a GUI since people like to click things more than type into a terminal window
not gonna bug you for donations - all my code is open source - if you'd like to donate, please do so by purchasing my EP. hey, you might even like the music, too:
buy it here: http://dreamcorp.bandcamp.com
or search for it on itunes, google play, amazon, spotify, last.fm, cdbaby, and so on.
there are also links in the description for my video:
https://www.youtube.com/watch?v=2i-F4jiKtGg
special thanks to chainfire for superSU, cyanogenmod for CM11S, geohot for the towelroot exploit, team win recovery project for the TWRP recovery, the developers of philz recovery, clockworkmod for the CWM recovery, OnePlus for giving us such an excellent and affordable product, and everyone here on xda-developers for growing and developing the android community into the vital and creative force it is today!
XDA:DevDB Information
Half-Assed OnePlusOne Toolkit in Python/ADB-python library - now on github!!!, Tool/Utility for the ONEPLUS ONE
Contributors
eudemonics
Source Code: https://github.com/eudemonics/1plus1toolkit
Version Information
Status: Stable
Current Stable Version: 1.3.1 STABLE
Stable Release Date: 2014-11-13
Current Beta Version: 1.3.2 BETA
Beta Release Date: 2014-12-30
Created 2014-08-19
Last Updated 2014-12-30

How work sync
mENU 5 HAS SYNC... hOW WORK ? wHAT SYNC ?

I get a "SyntaxError: invalid token" when trying to launch. Did I miss something?

You guys have really tried using the 'half-assed' toolkit???!! Wow - brave.

Mr Woolf said:
You guys have really tried using the 'half-assed' toolkit???!! Wow - brave.
Click to expand...
Click to collapse
It's also quite nice to understand how the Python works as everything is open-sourced in Python without privatized code. Good for educational purposes.
But yeah, I get why you'd say that, haha!

I tranfered files to /sdcard it showed transfer progress and finished but files are nowhere to be found on phone???

nedooo said:
I tranfered files to /sdcard it showed transfer progress and finished but files are nowhere to be found on phone???
Click to expand...
Click to collapse
did you copy multiple files at once? what did you use for the destination? (syntax)

Single .zip file and syntax : /sdcard
Edit: I needed this tool to transfer files from PC on XP without administrator privileges (MTP was mission impossible), at the end I did it with Airdroid.
Thanks for replay.

Nice, I don't use it, but it has passed my tests