Database Info

Putting togeter exe from wm6 image (noob)

Hi,
Following this thread: http://forum.xda-developers.com/showthread.php?t=310287 I created a dump directory for a WM6 image. Inside the SYS directories are a number of subdirectories. Some of these subdirectories have familiar names (e.g. calendar.exe). Using calendar.exe as an example, there are 5 files: imageinfo.bin, imageinfo.txt, S000, S001, and S002. Here are my questions:
1. What are these 5 files?
2. What tool would I use to put the folder together to create a single executable?
Sorry for the noob questions but I can't find the answer on the forums!!

OK, after trying out all of the tools in one of the bundles, I found the answer to the second question:
2. Within someone's kitchen tools (I don't remember which one I downloaded) was a file called recmod.exe. Run it with the folder as a parameter and it will put the exe together.
I still don't have the answer as to what those 5 files are though.

My terms may be off base but I'll try to explain what these files are as I understand it (and hopefully not look stupid in the meantime as I'm also trying to explain it in layman's terms).
Many core files are constructed like this so that they are optimized in the Rom to make them run more efficiently on our devices.

Rom Files

Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.

Tambuyeye said:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Click to expand...
Click to collapse
When creating packages with Package tool it creates the following folders:
SYS
OEM
Missing <-- Thats what you are looking for.
I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily

When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.
If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.
This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.
If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.
Good Luck!

Creating a ROM Image for ATnT Tilt

I have been working on a project to insert debug messages in low level dlls [like coredll, ws2.dll] and so on. The testing so far was done on device emulators and the .nb0 image seems to be pretty stable on it now.
Where I need help from xda community is how to take the next step - how to generate a ROM image for my kaiser. Specifically what all build options should be specified to my platform builder to get the right image for my device.
I tried to search previous postings for help but could not find one - may be I did not search thoroughly. My apologies if I did not search thoroughly - if it has been discussed in the past - would be great if someone could point me a link to it.
Thnx

TPC and myself has kitchens available for download. Pick one and replace your files, and build ROM.

To be precise - download a kitchen from here?
http://m-s-j.net/tpckitchen/kitchens/

poifgh said:
To be precise - download a kitchen from here?
http://m-s-j.net/tpckitchen/kitchens/
Click to expand...
Click to collapse
yes any one will work

Thnx for helping .. have a few hickups setting the ROM up.
1. Downloaded http://m-s-j.net/tpckitchen/kitchens/TPC_KITCHEN_6.120146.7z
2. Doing a build_rom.bat results in the following errors
Failed to set data for 'htcrt_backup'
"There is no device found to meet your project configuration. Try to update your devices file with new one."
"Access Violation - read at 000000"
Do I need to setup some config file somewhere - do we have a README for the process?
3. I dont quite understand the point "replace your files, and build ROM."
I have changes done to coredll and ws2.dll which were compiled using the 'emulator' flag in platform builder
a. What compile flags should the I use before I copy/paste my dlls into the kitchen
b. In the current kitchen - coredll is a directory containing 5 files S00 to S04 and also contains imageinfo files. Do I put in my coredll.dll file? or is there a step in between?
As you could see from my questions, I am complete newbee in building ROMs for phones - would appreciate any help from the community
thnx

I guess you're using Vista, right? It did me too. There are two (three?) solutions:
1. Disable UAC
2. Ignore it and via htc rom tool build .nbh by yourself (click right -> run as administrator on TOOLS\htcrt.exe) - OS.nb is in TMP directory
3. (not confirmed) Run the build script via cmdline manually, AFAIK TPC has got it written somewhere there.

poifgh said:
Thnx for helping .. have a few hickups setting the ROM up.
1. Downloaded http://m-s-j.net/tpckitchen/kitchens/TPC_KITCHEN_6.120146.7z
2. Doing a build_rom.bat results in the following errors
Failed to set data for 'htcrt_backup'
"There is no device found to meet your project configuration. Try to update your devices file with new one."
"Access Violation - read at 000000"
Do I need to setup some config file somewhere - do we have a README for the process?
3. I dont quite understand the point "replace your files, and build ROM."
I have changes done to coredll and ws2.dll which were compiled using the 'emulator' flag in platform builder
a. What compile flags should the I use before I copy/paste my dlls into the kitchen
b. In the current kitchen - coredll is a directory containing 5 files S00 to S04 and also contains imageinfo files. Do I put in my coredll.dll file? or is there a step in between?
As you could see from my questions, I am complete newbee in building ROMs for phones - would appreciate any help from the community
thnx
Click to expand...
Click to collapse
this is not the right place to be asking this, if you have questions about my kitchen you need to look in my kitchen thread. you will find the answers to your questions have already been posted there and if you need more help ask there and we will help you.

twopumpchump said:
this is not the right place to be asking this, if you have questions about my kitchen you need to look in my kitchen thread. you will find the answers to your questions have already been posted there and if you need more help ask there and we will help you.
Click to expand...
Click to collapse
you know how it is anymore, Have a question = START A NEW THREAD.

msd24200 said:
you know how it is anymore, Have a question = START A NEW THREAD.
Click to expand...
Click to collapse
= Flying Fishheads lol

[HOWTO] porting a ROM for old radio to work with new radio

I would love to help the community by using your kernel for the newer radios to port any roms for the older radio... is there any help you can give me? should i use your boot.img from the test-donut.img/test-eclair.img?
Click to expand...
Click to collapse
first, a thing we must know for porting job is what boot.img included.
here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
the ramdisk do some initializing jobs, so if we port a ROM, we should ensure that the content in ramdisk and files which are included in ramdisk (like init.rc), have necessary things the ROM needed.
for the first step, we can just extract the boot.img from the ROM, and extract the ramdisk from the boot.img which extracted just now, then repack it with my kernel (you can extract the kernel from my boot.img with same tools).
(to execute the perl script in link above, you need linux or just cygwin. )
but if we are sure that the ROM we want to port have nothing special with ramdisk, just like common ROMs, we can use my boot.img files directly. for eclair ROM, I suggest you extract the boot.img from my ROM, and don't use the first boot.img (test-NOCDB.img) I had posted.
after this, make our update.zip (use other's ROM as an example, especially the update-script in META-INF directory). sign our zip with testkey and apply it, then we can make our phone booting into desktop.
(you can find information about sign and download tools here: http://forum.xda-developers.com/showthread.php?t=471586, though the thread is not talk about how to sign things)
the main troubles we may meet probably are symlinks and setperm* in the update-script. if there is already a file/link has a name we want to symlink to, or if there isn't a file we want to symlink from or setperm, we will fail. so check the files carefully.
the next step is make everything work properly. we can use file from a ROM which made for new radio (and work well of course) to replace the one in the ROM we are porting. we can find these files in my 2.x ROM for eclair, or other's 1.6 ROM for donut (and for new radio, since the maker of them tested them already).
the most important files are (to my knowledge):
system/lib/libhtc_acoustic.so
system/lib/libhtc_ril.so (if something wrong with mobile network)
system/lib/libcamera.so
system/lib/libcameraservice.so
system/lib/liboemcamera.so (for 2.x) or system/lib/libqcamera.so (for 1.6)
system/lib/libgps.so
system/bin/akmd
(are there something I missed?)
(if we want to use NCommander's work on CameraHardwareInterface with a 2.x ROM, we should use my kernel for DONUT instead. I didn't try it, and I don't recommend it.)
these files are some thing work with hardware partially, so different radio may need different files. but if something just work fine, don't hurry to replace the file for it.
and now...., I don't have more thing to talk about, since we have most things work well. but for further tweaks, there are lots of things to do.
everyone can post your question here. if I know the answer I will post it. if I don't or I am not online, I think others will response you. and if there are things I missed or made some mistake, plz point it out
I will update this post when we collection more info or correct something. I find that I don't organized everything in order . I will update it later.

Thanks for the post... what's the difference between your eclair/donut kernel? (This is based on your original post about your kernel... is there an updated kernel somewhere i should know about?)
Edit
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions

Thank you very much for this sanpei. This is the type of posts that really should be on this forum
Appreciated so much. waiting for your next updates.

Phil_McRevis said:
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Click to expand...
Click to collapse
sorry for my poor ability of expression
asero said:
This is the type of posts that really should be on this forum
Click to expand...
Click to collapse
I expect more people can share their knowledge, and we can make a wiki for all

Hello!
I have to edit some lines of init.rc of your kernel. I've thus extracted the ramdisk, edited the file, repacked and tried booting with fastboot boot kernel-img ramdisk-img, but the phone hangs on the operator logo. I've tried even just extracting kernel+ramdisk and boot them - same result (the boot.img works well).
how can I fix it? Thanks

Wrong post

PC script to auto remove apk's

Hey everyone!
On the rom I currently use there are about 20 apk's I have no need for. What I do is download the rom, and individually delete the apk's before flashing the rom. The thing is I flash quite often (cheeky, I know ) and this is getting quite frustrating.
Ideally I want a script that does this all for me. I found one but it seems be for running on the phone, after the apk's have been installed. Does anyone know how I can create a script for the PC that does this before I even install the rom?
Thank you for any suggestions.
Oh and here's the thread I found that looked relevant...
http://forum.xda-developers.com/showthread.php?t=674357

edcoppen said:
Hey everyone!
On the rom I currently use there are about 20 apk's I have no need for. What I do is download the rom, and individually delete the apk's before flashing the rom. The thing is I flash quite often (cheeky, I know ) and this is getting quite frustrating.
Ideally I want a script that does this all for me. I found one but it seems be for running on the phone, after the apk's have been installed. Does anyone know how I can create a script for the PC that does this before I even install the rom?
Thank you for any suggestions.
Oh and here's the thread I found that looked relevant...
http://forum.xda-developers.com/showthread.php?t=674357
Click to expand...
Click to collapse
Over what OS?
If in Windows (or any M$ OS, incl. DOS) you can make a batch file.
My file is adjunted as example (modify as you like, put in the root dir -obviously to the unzipped ROM- and run. Rezip and maybe re-sign)
salu2

Thank you. This is exactly the kind of thing I am after. If I had of been born just a few years earlier I would probably know all about batch scripts. Fortunately, I just missed the DOS days!
Anyway, I puzzled out / looked up the commands in the script you posted. Based on that I extracted the rom, then placed the batch file within it, so that the cd (current directory) command runs correctly.
Unfortunately this mucks up the signing on the rom. Do you re-sign your CM7 roms every time you do this or is there an easier way?
Edit: My PC is Win 7, 64bit, soon to be Win 8 Consumer Preview.
Edit: The roms do not need resigning.

I don't re-sign the ROM, simply flash again over Clockworkmod Recovery.. and work.
But, you can:
1) sign using Auto-Sign....
2) Click [Thanks]...
Salu2
__________________________________________________________________
I know, I know.... my english is ****ty... but my spanish is much better... ;-)

Big thank you. That's solved that one nicely for me!

You're welcome.
Updated zip in my first Post.
Salu2

Hey again. I was hoping to build on the script you kindly provided. At the moment I am using various alpha roms where the exact apk's present changes fairly often. It would be great if I could see the outcome of each action. This way I would know if the apk has had it's name changed or been removed. How would I enable this?