How To: Modify a ROM. - JAMin, XDA Neo, S200 ROM Development

How To: Modify a ROM. - JAMin, XDA Neo, S200 ROM Development

Over the coming days, I shall be writing more below as a tutorial for ROM cooking/Modification.
First, you will need a ROM kitchen. For ease of use, I would recommend Inteks Neokit which can be found here.
Next you will need a base ROM (any Prophet ROM will do) many can be found here.
Now, load neokit and then select the "Select nb/nbf" option. Select the ROM you want to modify and then click "dump rom". This will deconstruct the ROM and put all the files included in the ROM into a single directory.
If you know the files you want to change (such as images) you can simply find them in the "dump" folder (click on the "..." button on neokits main screen) and replace them with the files you want.
If you want to add a program, you can do it two ways:
Create an OEM Package.
Install a CAB after the flashing of the ROM.
If you want to change the registry, the "default.rgu user.rgu" tab must be selected.
To change shorcuts, you will need to edit the "initflashfiles.dat".
After modifying the ROM, you will need to build it back up so that you can flash it. Go to the main screen and click "build ROM" click yes, and then you will have to wait for this to complete.
Now you need to turn the *.nb files into a *.nbf. Follow the instructions in neokit for this.
This will be updated with more detail when I have the time to do so.
If you have any questions do not hesitate to ask as I and others will be willing to help.

What can be safely removed?
Below are the names of packages that can be removed without causing instabilities. Having said that, the may dramatically reduce the functionality of a ROM. The best way to find out what ca be removed is to try it yourself, flash it and see if anything works/doesn't work and then build on it from there. Post your findings here and help someone else!
Internet Explorer-Related Packages
Browsing--Base for IE
Browsing_DPI_96--Images related to IE
Browsing_Lang_XXX (where XXX is the region code) Can be removed or replaced for localisation.
BROWSINGCORE--This might cause instabilities to the OS as lots of programs rely on these files

Also reserved.

Thanks...
It's really helped...

What files I can remove for more space?

amaleena said:
What files I can remove for more space?
Click to expand...
Click to collapse
This question can't be answered, it is a bit the same as "How do I get to Amsterdam?" Without telling us where you are!
How can anyone tell you what is to be removed in your ROM if we don't know what files are there in the first place? This can be different depending on wich ROM you use; some are allready "cleaned out" while others are stuffed to the max.
But above all, it is up to you to decide what you will sacrifice to create more space. The challengeing part of this game is to try, explore and discover and experience that overwhelming satisfaction when a plan comes through!!
So, my advice: don't bother to refrase your question but just go for it yourself....

rondol1 said:
This question can't be answered, it is a bit the same as "How do I get to Amsterdam?" Without telling us where you are!
How can anyone tell you what is to be removed in your ROM if we don't know what files are there in the first place? This can be different depending on wich ROM you use; some are allready "cleaned out" while others are stuffed to the max.
But above all, it is up to you to decide what you will sacrifice to create more space. The challengeing part of this game is to try, explore and discover and experience that overwhelming satisfaction when a plan comes through!!
So, my advice: don't bother to refrase your question but just go for it yourself....
Click to expand...
Click to collapse
I agree with that, however from personal experience I think a short list of things that can be removed might be helpful...

Is it possible to change only the language of a rom? How can i Do it?

l3v5y said:
I agree with that, however from personal experience I think a short list of things that can be removed might be helpful...
Click to expand...
Click to collapse
That right!.I mean list of files that can be removed safely.Example, If I would like to remove Microsoft word. I should remove file1.exe,file2.dll,...etc.
Sorry for my poor English.

xfounder said:
Is it possible to change only the language of a rom? How can i Do it?
Click to expand...
Click to collapse
You have to overwrite the MUI files, change some paths in the Regsitry (default.hv and user.hv, konvert them first) and change the paths in the initflashfiles.dat! That's all!

What device is that from?
*.nbh files can be read using this: http://forum.xda-developers.com/showthread.php?t=377514

l3v5y said:
What device is that from?
*.nbh files can be read using this: http://forum.xda-developers.com/showthread.php?t=377514
Click to expand...
Click to collapse
HTC p3600, Trinity

The tools I mention in the first post are designed purely for the HTC Prophet... I have no idea about what to do for a Trinity...

l3v5y said:
Over the coming days, I shall be writing more below as a tutorial for ROM cooking/Modification.
First, you will need a ROM kitchen. For ease of use, I would recommend Inteks Neokit which can be found here.
Next you will need a base ROM (any Prophet ROM will do) many can be found here.
Now, load neokit and then select the "Select nb/nbf" option. Select the ROM you want to modify and then click "dump rom". This will deconstruct the ROM and put all the files included in the ROM into a single directory.
If you know the files you want to change (such as images) you can simply find them in the "dump" folder (click on the "..." button on neokits main screen) and replace them with the files you want.
If you want to add a program, you can do it two ways:
Create an OEM Package.
Install a CAB after the flashing of the ROM.
If you want to change the registry, the "default.rgu user.rgu" tab must be selected.
To change shorcuts, you will need to edit the "initflashfiles.dat".
After modifying the ROM, you will need to build it back up so that you can flash it. Go to the main screen and click "build ROM" click yes, and then you will have to wait for this to complete.
Now you need to turn the *.nb files into a *.nbf. Follow the instructions in neokit for this.
This will be updated with more detail when I have the time to do so.
If you have any questions do not hesitate to ask as I and others will be willing to help.
Click to expand...
Click to collapse
hi l3v5y :Moderator,
I was a new member of xdaDef...
i'd ever cook the rom base on the RK at PDAMobiz.com..
But i got the prob. about how to add the program into the OEM package 'coz some programs i got that contained the old version.
Anyway i used the package creator 5.5 to do create it into the OEM file...
after that i can collect the program in OEM and can build OS but after upping the ROM ....
it;s got HANG.... Oh no..
I tried many many time to change something but i didn't have the knowledge about RM..
could u pls. suggest me by e-mail how to cook the rom by myself after i d/l the SYS, OEM, and XIP of "CE 5.2.19960 (issue form HTC Raphael) ported for ELF"..
I wanna be a rom cooker asap....
Best Regards,
JoeMan
[email protected]

Also another suggestion:
When removing one or more software you should also remove the setting in initflashfiles.dat and the registry in default/user.rgu, that's call clean remove.
When adding softs, also include adding path and registry also.
For better removing or adding soft you should look inside their cab (I use WinCE cab manager)

legedug said:
Also another suggestion:
When removing one or more software you should also remove the setting in initflashfiles.dat and the registry in default/user.rgu, that's call clean remove.
When adding softs, also include adding path and registry also.
For better removing or adding soft you should look inside their cab (I use WinCE cab manager)
Click to expand...
Click to collapse
WOW..... LEGEDUG..... a rom master now....

legedug said:
Also another suggestion:
When removing one or more software you should also remove the setting in initflashfiles.dat and the registry in default/user.rgu, that's call clean remove.
When adding softs, also include adding path and registry also.
For better removing or adding soft you should look inside their cab (I use WinCE cab manager)
Click to expand...
Click to collapse
Thaks for yr suggestion....
But it is my hard understanding..
could u pls. show me the example?
i'll try it...
Regards,
JoeMan

Thank's dioxda2 for teasing me
But I'm a learning by doing,
Still too far away from being a rom master

monjikung said:
Thaks for yr suggestion....
But it is my hard understanding..
could u pls. show me the example?
i'll try it...
Regards,
JoeMan
Click to expand...
Click to collapse
Oke
For instance, you want to add smsbackup in your rom
Open smsbackup.cab with wince cab
There are 2 files (exe and dll), 1 shortcut (lnk) and 4 registry entry
So, you should add 3 files (exe. dll, and lnk) to dump folder (adding fiile from neokit tools from Inteks)
Adding some initflash.dat with some path (where do you want to put the link file)
Adding 4 registry key in default or user.rgu
For removing, the process will be reversing.
Hope this will help you
I think you should try practicing.

Related

To ROM cookers: working on a nice program for making ROMs

Hello everybody!
Even if this is my first post on this forum, I use to visit this useful place since years, I tried many of those great WM6 ROMs made by our ROM cookers (thanks to all), then I tried to cook my own ROMs using tools recommanded in the Wiki.
But those kitchen tools weren't conveignent for my use, it was a lot of work and patience for making ROMs, we need to use many different programs and scripts, and I thought that the cooking process could be really simplified using an unified graphical interface like dutty's tool. I was patiently waiting for his Hermes Rom Koch V2, but finally I started to develop my own kitchen tool!
Here are some features of this program:
- ROM file manager (to add/delete/extract files or to create shortcuts)
- ROM layout editor (to edit init flash files)
- Registry editor (to modify/import/export default & user registry)
- CAB install files integration
- ROM creation from original OS image or dump directory
I posted some screenshots for better explanations.
This program simply use aWaiter and ImgFS tools for ROM creation/extraction.
For now I still have a lot of work on it, but I would like some advises from experienced developers on this forum, because even if my program works, I would like to know if the cooking process is porper and safe, and how I could improve it (for example using internal functions for ROM creation/extraction instead of external programs, implementing NBH tools,...).
If some of our XDA-developers are interested, I would really like to make this project an Open Source "all-in-one" ROM cooking program, gathering all the others kitchen tools in an unified graphical interface offering the easiest way to cook nice ROMs for our Hermes and certainly for other devices.
I know that I didn't give many details about my program but don't hesitate to ask me about it. I would also have few questions for developers.
Developers and ROM cookers, I'm waiting for your feedback!
Thanks.

This looks very user friendly, I will be watching closely. Good work.

What language is it in? (programming language that is)

Midget_1990 said:
What language is it in? (programming language that is)
Click to expand...
Click to collapse
I developed this program in C# (using .NET framework 2.0).

Thx for your work! It would be better if the tool support packages.
http://forum.xda-developers.com/showthread.php?t=296861

Where to download??

Thanks for the link. I already thought about working with packages because it seems to be a better way to make "clean" ROMs, but I couldn't find enough information about how to extract/build packages in ROM.
I tried bepe's package tool on my own cooked ROM and I noticed that removed files were marked as missing in packages, and all the files I added weren't moved from dump directory. There is nothing surprising, but I wondered if adding/deleting manually files from ROM, causing "corrupted packages", can have any effect on final ROM. If not then why packaging information (like .dsm and .rgu files) are still present in ROM after all packages were merged? What exactly contains .dsm files, and how to create them for adding new packages?
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Thanks

I'm still working in this project, so I didn't plan any release yet.

Good idea and nice project.
Go on dude !
Good work.

Great work so far - I fullly support this project.
Lookign forward to the release.

schaps said:
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Click to expand...
Click to collapse
Great project - and I agree, it definitely should support packages. If you've had a look at bepe's kitchen, you already know how much easier it is to understand the purpose of all the files in a ROM if they are organized in packages.
.rgu files are Registry "source code". They are not part of the package mechanism. And yes, when cooking a ROM you can leave them out, as they are not needed at run time. Saves a bit of space.
The .dsm files, otoh, are needed at run time.
When I cooked my ROM, I did find some information (written by bepe) here in the forum about how to make your own packages. Can't remember where that was, but I found it on my hard disk, so I simply quote it here again:
How-To build ur own OEM Package:
An OEM Package is just a simple folder containing files and registry settings for the ROM
First of all you'll need a GUID number for your Package.
Go to http://www.famkruithof.net/uuid/uuidgen to get one.
In my case:
283b9db7-cb03-4c1b-820e-ca49b2c3b5db
Necessary steps:
1. Create a new folder:
Dev/OEM/[Your package name]/
2. Create a empty text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.dsm
(CreateOS.exe will finish this file for you)
If needed:
3. Create an UNICODE text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.rgu
This file could be used to add registry entries to the ROM
First line is:
REGEDIT4
...
and there MUST be a empty line at the end!!
4. Create an UNICODE text file:
Dev/OEM/[Your package name]/initflashfiles.txt
This file could be used to create folders or copy files, shortcut on the ROM.
For Example/ Ilustration: Open or read Dev/LOC/initflashfiles.dat using a text editor or any premake initflashfiles.txt at one of the OEM folder.
and there MUST be a empty line at the end of iniflashfiles.txt also!!
Copy all files you need to Dev/OEM/[Your package name]/
Click to expand...
Click to collapse
Hope that helps. If I remember correctly, bepe told me that the OEM folder is treated a bit differently from the SYS folder, so it might be you can't create packages there. But then, you probably also shouldn't.
Oh, and about the initflashfiles.dat: you are aware that the initflashfiles.dat just copies files and does not move them? Using this feature extensively uses up ROM space very quickly, so it should be done for small files (like the start menu shortcut files) only.
Cheers
tadzio

Thanks a lot for your help tadzio!
I also read the different steps about how to add a new OEM package, I found information on this Wiki if someone is interested : http://wiki.ppcgeeks.com/index.php?title=Kitchen.
I think I know enough about it but what I would know is how to extract packages then to merge them for creating a ROM image, like do bepe's tools?
I confirm I also heard that OEM folder processing is different from SYS folder.
Concerning the initflashfiles.dat I guessed that files were copied from ROM to storage memory, good to have a confirmation. So it means that if we want to include a new program in ROM, we should better to let it in Windows folder than to put it in a Program Files folder, right? I have another question about initflashfiles.dat, I saw that it sometimes uses variables for directories instead of strings (for example Directory(LOC_XXX), Directory(0409_XXX),...), where could I find those variable declarations?

schaps for president

schaps said:
Thanks for the link. I already thought about working with packages because it seems to be a better way to make "clean" ROMs, but I couldn't find enough information about how to extract/build packages in ROM.
I tried bepe's package tool on my own cooked ROM and I noticed that removed files were marked as missing in packages, and all the files I added weren't moved from dump directory. There is nothing surprising, but I wondered if adding/deleting manually files from ROM, causing "corrupted packages", can have any effect on final ROM. If not then why packaging information (like .dsm and .rgu files) are still present in ROM after all packages were merged? What exactly contains .dsm files, and how to create them for adding new packages?
Could someone tell me more about building packages, or tell me where I could find all the information I need.
Thanks
Click to expand...
Click to collapse
Hi Schaps,
you can have a look in this link:
http://forum.xda-developers.com/showthread.php?t=312985
it's a tool to re-build DSM file, which is better than just creat an empty .dsm file when making new package.
hope this help. It will be cool if your new tool support package.

CAB To OEM for use with Pandora Kitchen

Hey Guys,
Yet another sleeples night, looking at something that is probably simple and getting no where.
THE PROBLEM:
APPARENTLY you can change a CAB file into an OEM so that it can be used in Pandora Kitchen, the kitchen thread says its possible, but doesnt really give directions as to how.
Considering this is a new thing to, and there is no info about this on the site (that i can find)
Can someone please tell me step by step how to do this, and by step by step i mean:
1).................
2).................
3).................
4).................
etc etc
Thankyou for your help in advance

Here is a test package I made, but I keep getting a registry errors. Maybe someone can tell me what im doing wrong. I think it was better to keep all this in the kitchen thread personalley but as long as I can figure this out I dont really care.
Extract this file and take the "Remote Desktop" dir and drop it in the OEM dir in the Kitchen, and it shows up and all but when you go to build with teh green arrow I get a registry compiling error.
I also attached the original cab file that I started with when attempting to create this package.
Also attached is the cab manager that Matt uploaded, I am sure its the same as the one posted above but this has a readme and what not.
First Matt told me this:
Using this tool (many out there, this one's free and does a good job), extract the cab to a folder, then click on XML and grab the .rgu contents. Be wary of the format, as you have to delete any spaces between entries, such as "biteme" = dword : 00000001 should read "biteme"=dword:00000001.
Also, ensure that any path in this file (file system, not registry) is in this format: "\\Windows\\Startup" The second slash is required. Also, remove any references like %ce%\Windows, just change it to "\\Windows". You'll get the idea. If it ain't right, BuildOS will fail while creating the registry.
Move all the files into the top level in the folder you made, and remove all the extra crap like the inf file, and sometimes there's an xml file there too - note that you may need to convert to a provxml if the settings in it are required.
Use this site http://www.famkruithof.net/uuid/uuidgen (verion 4) to get a new GUID. I'd suggest coping a .rgu and options.xml file from another package since the file has to originate a certain way - and only use notepad to edit.
Just follow the example in the other packages - you'll find just about every way to do things in there.
As far as more details on using the program, just play with it. It's pretty simple
Then Bennec83 told me this:
what exactly are you trying to do? extract a CAB? if you are, using the file i uploaded earlier:
1)Launch CAB Manager.exe
2)on main screen extract CAB to a folder
3)click on the XML tab in top bar of the main window of CAB Manager.exe
4)in the window that opens, select Registry Keys
5)copy everything from the screen into WORDPAD
6)remove all the spaces
7)save the file as "UNICODE", once saved change the extension to somename.rgu
if you are trying to add an OEM to this kitchen i dont think you can just add them, please correct me if im wrong.
i hope this helps, if not tel me abit more about wat u want to do n ill try to help abit more!!
I understand the INF file as well, I just dont know how to add multiple directories as the destinations for a package, when a cab inf will tell you where there all suppost to go.
--Update--
I removed the NON-WORKING package, as it is now obsolete, see post below I got it working.

Ok then I understand the logic, and then the proper elaborated instructions can be pasted at the first or second topic of the Kitchen thread.
So I guess im doing something wrong with the reg, I have tried it a bunch of diffrent ways by comparing it to existing packages but I still cant seem to get it.
This quote by matt is what leads me to believe that.
Also, ensure that any path in this file (file system, not registry) is in this format: "\\Windows\\Startup" The second slash is required. Also, remove any references like %ce%\Windows, just change it to "\\Windows". You'll get the idea. If it ain't right, BuildOS will fail while creating the registry.

Ok I did it, I was reading an old post of bepe's and he said "add the reg to the end of the file (and the last line must be empty)" and so I hit enter and left the last line blank and BAM it worked so here is my first package contribution.
Maybe you can start adding these to the first post and we can start to make a collection for matt to add and test with his kitchen ?

Here is another one HTCustom 1.7 ready to go package for the kitchen

Damned if I can work it out!
Can anyone please package any of the following cabs?
Ive added JUVS HTC Home because the one included in the kitchen has the coloured icons not the original b&w.
Many many thanks in advance

I am still not able to completly figure out how to make a package where you must put files in diffrent locations other then the windows folder ? I would veyr much like to figure this part out.

I dont think he's having a go at you - he's just as frustrated as you and I with this. I would love to be cooking my own roms and with the wonderful pandoras kitchen I am getting alot further along but I guess I got a lot further to go!

well, by searching you can find how to do this!!!
click on this ftp://xda:[email protected]/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
this pdf file got what you need!!
under "Making a Package from a CAB file"

Look here bennec83, the comment i made was not meant to be a flame at all. If anything, it should have helped you alot with what you were trying to accomplish with the program and, making packages. I mean how much more direct can i be with helping you? As I said to you before, yes some of the chef can be a little vague with explaining the "How To's" of cooking or anything else, but that still didnt stop my progression of learning what i wanted to learn on here. What i explained in the CORE's Kitchen thread, was basically 80% self taught thru reading post & threads on xda, google searching, and trial and error. The other 20% was thru xda forum members input. I have a basic understainding of computers with no type of programming skills, and yet still, i was able to grasp the concept of cooking roms and making packages. Yes sometimes you have to put 2 and 2 together to figure things out on here. How I did it was I looked inside CORE's additional OEM packages and noticed that the files inside all the oem were extracted into the root of the folder's Dir...ok..so I would assume that you spent considerable amount of time trying to figure out that OEM package program(inside CORE's Kitchen its called Cab Analizer), then i would assume that you know that it extracts files within a .cab...ok... with that given....if you look back into an already made OEM package and many others, you'll notice that most ,if not all, carry an "initflashfile.txt"(which i figured out the correct data input) and many packages also carry .rgu & dsm files, so guess what....you need to find out what are .rgu & .dsm files, and there functions(if know no ones whats to tell you in a timely manor then, search or google, like i did!) Once you learn about those then, you'll notice that the OEM package program you have infront of give information about the reg keys of the cab (if available), then you start putting 2 & 2 together! You mention in your quotes that the programs sucks ass, well that program is a key part in making packages, If you can find a better one, please let me know!

NightmarE said:
well, by searching you can find how to do this!!!
click on this ftp://xda:[email protected]/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
this pdf file got what you need!!
under "Making a Package from a CAB file"
Click to expand...
Click to collapse
thankyou so much for this, i actually know what to do now i really appreciate this. you dnt know how much!!!
thanks alot

chrisnash said:
I dont think he's having a go at you - he's just as frustrated as you and I with this. I would love to be cooking my own roms and with the wonderful pandoras kitchen I am getting alot further along but I guess I got a lot further to go!
Click to expand...
Click to collapse
you are right that wasnt flamage!! i have been lookin so long in this forum i totally didnt think the answer would be in the wizard forum.
i have read and understood the instreuctions here:
ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
i just wish i cud have found it earlier

perhaps I'm an utter fool, but I'd like some clarification from those of you who understand this, mind you I do have Faria's PDF:
1) For a .cab with purely registration files (ie, the Cingular WAP Settings) that contains a .inf when extracted, all I would need is the .rgu to put into BuildOS, right?
2) The .dsm file (and iniflashfiles) are only needed if the .cab is an actual application, and the .dsm file that you create can very well be empty (from what I understand from Faria's rom).
Maybe it's a lack of sleep, but I'm just not getting my head around this and am so far using the Install Cabs feature from HTCustom 1.7 after flashing.

I was trying to do the cignular settings and It seemed to me that all those reg entries appear like blank er something was wrong with them, I could be wrong but thats what it appeared like to me.
Bennec, ok then bro, my mistake, I guess I shouldnt of assumed that post was directed towards me, it just felt that way and I know you were frustrated.
Lets make this the best CAB to OEM Package thread ever and start a collection on the first post, also with all you have learned now, have you figured out a way to make a package with a cab like opera where the files must be placed in to diffrent dirs ?

where are you all stuck at?
to move files to a different directory you need to use initflashes. Keep in mind that this copies it to a different directory not actually moves it. The original file will still be in \\windows
If all you want is to add registry entries, add them to an existing packages registry entries. If you create a new package for the registy entries it should have a dsm file as well.
If you want the check box in buildos you will need to create an option.xml file as well.

bennec83 said:
you are right that wasnt flamage!! i have been lookin so long in this forum i totally didnt think the answer would be in the wizard forum.
i have read and understood the instreuctions here:
ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf
i just wish i cud have found it earlier
Click to expand...
Click to collapse
I'm glad you found the info you need, and are on your way to making progress. I apologize for not being able to assist more than I did, but I've got my hands full getting v3 ready for release.
Good luck and happy packaging!
NYD - long time, no see!

goto the CORE's kitchen thread. Read my posts and familiarize urself with a program called "compare it". Use this program to compare ur registry when the app is freshly installed, to the registry without the app installed, and pull the reg keys that way!

mattk_r said:
I'm glad you found the info you need, and are on your way to making progress. I apologize for not being able to assist more than I did, but I've got my hands full getting v3 ready for release.
Good luck and happy packaging!
NYD - long time, no see!
Click to expand...
Click to collapse
I understand you have lots to do on your kitchen, congrats BTW!! amazing kitchen, how is touch flo goin?

notyourdaddy said:
where are you all stuck at?
to move files to a different directory you need to use initflashes. Keep in mind that this copies it to a different directory not actually moves it. The original file will still be in \\windows
Click to expand...
Click to collapse
Hmmmmmm.
So its not possible to cook a Rom with custom apps in Progam Files only? I mean if they are always in \\windows too then its better to install the files than to cook it in the rom.

I have always believed you should add as little as possible to Rom:
From Tadzio's 'Want more Storage' Thread.
tadzio said:
...clip...
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size.
...clip... make a ROM as small as at all possible, removing anything that users may not want, and turn every removed feature into a .cab that users can install to Storage...clip...
Cheers
Daniel
...clip...
Click to expand...
Click to collapse

How To: Atom Series Extended Rom Cooking

For Atom / Atom Pure / Atom Exec: Use WinImage Version 8.1 or similar program to edit IMG file. There are many programs that can do it.
Do not touch folders found in this image file. Programs that depend on these folders are: FM Radio, AutoConfig, WirelessManager, Camera, Equalizer, Album (life), ImageEditor (life)
The version of the Extended Rom is taken from the text file:
061020_AL1ARCWWE_EX0604.txt
The name is picked up versionCPAapplet.cpl (found in Settings->System Info)
So far, I did not encounter any problems changing the version numbers
The default folder name for this partition on your device is \_QHiddenPartition\ However, when we unlock this hidden partition at device runtime, we can not use the same folder name to install programs and lock it afterwards.
Normally, I used this partition to place the cabs I want to install at hard reset. This is no longer a problem with the cooked ATOM/ATOM EXEC ROMs we made because, serialzs introduced MortScript to do the automatic installation of cabs found in \_QHiddenPartition\ and \cabs\ folder found in storage card.
It is not necessary, however, to unlock the hidden partition just to edit the contents at device runtime. You can always use Total Commander to browse this partion by keying \_QHiddenPartition\ on the location bar.
For ATOM LIFE users, you can simply remove the 12-byte header of IMG file, and WinImage 8.1 can be used to edit the file. You need to restore the 12-byte header prior to flashing your device again.

tj your are very kind ^^;
Last time i ask.you say search.
i use search but still confuse cause alot of topic.
but now you posted this info.
THANKS YOU

thank you,i'm trying to cook and release WM 7.0 tonight. j/k

How to remove or add programs being install in order??? I found that del *.cab to remove the programs and copy *.cab to auto install the programs from extended rom. But i don't know the file where listed the programs is able install in the extended rom at hard reset. In the past,when i cooked BA rom, i remember that i can edit the file include the paths of the cabs I want to auto install at flash rom or hard reset.
jiggs said:
For Atom / Atom Pure / Atom Exec: Use WinImage Version 8.1 or similar program to edit IMG file. There are many programs that can do it.
Do not touch folders found in this image file. Programs that depend on these folders are: FM Radio, AutoConfig, WirelessManager, Camera, Equalizer, Album (life), ImageEditor (life)
The version of the Extended Rom is taken from the text file:
061020_AL1ARCWWE_EX0604.txt
The name is picked up versionCPAapplet.cpl (found in Settings->System Info)
So far, I did not encounter any problems changing the version numbers
The default folder name for this partition on your device is \_QHiddenPartition\ However, when we unlock this hidden partition at device runtime, we can not use the same folder name to install programs and lock it afterwards.
Normally, I used this partition to place the cabs I want to install at hard reset. This is no longer a problem with the cooked ATOM/ATOM EXEC ROMs we made because, serialzs introduced MortScript to do the automatic installation of cabs found in \_QHiddenPartition\ and \cabs\ folder found in storage card.
It is not necessary, however, to unlock the hidden partition just to edit the contents at device runtime. You can always use Total Commander to browse this partion by keying \_QHiddenPartition\ on the location bar.
For ATOM LIFE users, you can simply remove the 12-byte header of IMG file, and WinImage 8.1 can be used to edit the file. You need to restore the 12-byte header prior to flashing your device again.
Click to expand...
Click to collapse

cdmavn said:
How to remove or add programs being install in order??? I found that del *.cab to remove the programs and copy *.cab to auto install the programs from extended rom. But i don't know the file where listed the programs is able install in the extended rom at hard reset. In the past,when i cooked BA rom, i remember that i can edit the file include the paths of the cabs I want to auto install at flash rom or hard reset.
Click to expand...
Click to collapse
The script runs through all cabs present in the the two locations stated above. You don't have to edit any list like you do for AutoRun in BA. Also, AutoRun does not work with cab installation that require user interaction. Now, as for your question regarding the order they go - it's alphabetical.

Hi jiggs!!
You awesome! I have added my operator in autoconfig list, all work fine, now I have all settings for my operator!
THANKS A LOT!!

interesting in rom cooking, thats what i.m always thinking about,.
but i'm afraid to do this, i'm afraid i'll bring my atom unusable,.
thanks anyway jiggs,.

ex.image said:
Hi jiggs!!
You awesome! I have added my operator in autoconfig list, all work fine, now I have all settings for my operator!
THANKS A LOT!!
Click to expand...
Click to collapse
Pls post your settings for others, too. Thanks.

jiggs said:
For ATOM LIFE users, you can simply remove the 12-byte header of IMG file, and WinImage 8.1 can be used to edit the file. You need to restore the 12-byte header prior to flashing your device again.
Click to expand...
Click to collapse
how do you remove 12-byte header?

ichanz said:
how do you remove 12-byte header?
Click to expand...
Click to collapse
Open the file with an HEX-editor, cut the first 12 bytes and save the file. That's all.
You can use "XVI32". This Hex-editor is included in the original Scooter-ROMkitchen.

Hi all,
I use remotePROTECT as a security measure on my Atom - I find the program great.
It will be even better if I place it in extROM (hidden partition) so that it will install again upon hard reset.
I've followed the instructions that come with the software - they require me to place the program's CAB file in the extROM along with the setupE file.
I tried that - did a hard reset and nothing happened - didn't install.
I have an O2 Atom with an official ROM release installed.
Is there anything else I need to do? I note there is an Autoinst.dat file in the hidden partition, but it's encrypted or gibberish so I can't do much with it.
If I've overlooked anything can someone please suggest what I can do to make this do what I want - install itself again after hard reset.
Thanks in advance.

Avocado said:
Hi all,
I use remotePROTECT as a security measure on my Atom - I find the program great.
It will be even better if I place it in extROM (hidden partition) so that it will install again upon hard reset.
I've followed the instructions that come with the software - they require me to place the program's CAB file in the extROM along with the setupE file.
I tried that - did a hard reset and nothing happened - didn't install.
I have an O2 Atom with an official ROM release installed.
Is there anything else I need to do? I note there is an Autoinst.dat file in the hidden partition, but it's encrypted or gibberish so I can't do much with it.
If I've overlooked anything can someone please suggest what I can do to make this do what I want - install itself again after hard reset.
Thanks in advance.
Click to expand...
Click to collapse
If you have read the first post carefully, then you will understand that this won't work because the built-in AutoInstall of the official ROM restricts to signed CABs only as defined by list with no known format as of this date. That's why we have cooked ROMs to bypass this and created another AutoInstall script. There are work arounds for your purpose but definitely this solution is not for you. You have to do some research on this forum.

Anyone knows how to change or create new network settings. I found xml files in network folder and asked if there is a way to have my personal network settings like auto sms delivery or auto configure vms numbers or ...

vocian said:
Anyone knows how to change or create new network settings. I found xml files in network folder and asked if there is a way to have my personal network settings like auto sms delivery or auto configure vms numbers or ...
Click to expand...
Click to collapse
you need to secure this from your operator.
although you can edit the xml files with notepad, I don't know if the GUID found there is important. you can also generate your own GUID to have a unique value.
select the existing xml that best fit your requirements and edit it. you can't edit the cabs found in the networks because they are signed. you need to provision your own cabs. it's more like provisioning certificates using cabs.

jiggs said:
you need to secure this from your operator.
although you can edit the xml files with notepad, I don't know if the GUID found there is important. you can also generate your own GUID to have a unique value.
select the existing xml that best fit your requirements and edit it. you can't edit the cabs found in the networks because they are signed. you need to provision your own cabs. it's more like provisioning certificates using cabs.
Click to expand...
Click to collapse
thank you very much indeed. I found xml files for defualt operator and also txt file wich list this operators. Gussed that first input my operator to that list and then create new xml. but i figured if any guide for what all of this xml comands mean and the whole format.
and another question : how to edit or change cabs? I have a background of programming with c++ and visual basic.net. Is it possible for me to create my own cab without too much effort? and with which compiler ?
tnx

jiggs said:
It is not necessary, however, to unlock the hidden partition just to edit the contents at device runtime. You can always use Total Commander to browse this partion by keying \_QHiddenPartition\ on the location bar.
Click to expand...
Click to collapse
Jiggs,
I am using an atom life, I fould that I could not browse the extended rom with Total Commander. In my memory, I should be able to use TC to browse the extended rom on my ATOM EXEC. Do you know what I am doing wrong?
By the way, is it possible to unhide the extended rom?

vocian said:
thank you very much indeed. I found xml files for defualt operator and also txt file wich list this operators. Gussed that first input my operator to that list and then create new xml. but i figured if any guide for what all of this xml comands mean and the whole format.
and another question : how to edit or change cabs? I have a background of programming with c++ and visual basic.net. Is it possible for me to create my own cab without too much effort? and with which compiler ?
tnx
Click to expand...
Click to collapse
use PocketPC Installation Creator to create cabs.

hh93220 said:
Jiggs,
I am using an atom life, I fould that I could not browse the extended rom with Total Commander. In my memory, I should be able to use TC to browse the extended rom on my ATOM EXEC. Do you know what I am doing wrong?
Click to expand...
Click to collapse
You must simply type \_QHiddenPartition in Total Commander to switch to Extended ROM.
Btw: It's described in the Atom Wiki. You should read it.
By the way, is it possible to unhide the extended rom?
Click to expand...
Click to collapse
Yes:
hit me

scorpio16v said:
Open the file with an HEX-editor, cut the first 12 bytes and save the file. That's all.
You can use "XVI32". This Hex-editor is included in the original Scooter-ROMkitchen.
Click to expand...
Click to collapse
Thanks!! The problem resolve after I remove the first 12 bytes.

For AtomLife ExtRom.img.
Anyone was successful to flash editted ExtRom.img of AtomLife with DSUU? If possible, could you please show me few experience to Update ExtRom via DSUU.
Ex: Remove 12bytes header/edit(add or remove anything can do)/restore 12bytes header. Then replace new ExtRom.img in \Window\temp\ExtRom.img and delete \Window\temp\FLASH.DIO while completed extract of DSUU running. Then imitate DSUU instruction. Is it right? This way, I cuccessed to new Flash.dio for AtomLife.

how to reconstruct a dumped rom for my niki?

hi
before installing Tom rom I have decided to dump my original rom in case I needed to put it back.
anyway I have been able to dump the 4 Raw files. now I see that in the Kaiser section there is a guide on how to reconstruct a rom to make it flashable and I wonder if I can do the same with my Niki.
any expert could pls confirm this?
thanks in advance for your help.
cheers
edit: I ve just noticed that there are some other threads about this subject...anyway if someone can confirm the right procedure would be great. thanks

Yeah, also wondered about that Kaiser rebuilding tutorial.
Talked to a few people over PM who have the same problem.
But even in the Threads nobody who knows more about flashing/ROMs seem to be willed to help out with a fre informations. :-/
Still confused about the needed baserom in this thread.
-Is this available for Niki? (Where)
-Why do i need it / why can't i rebuild a rom ONLY with my phone and need something like a bsserom?
-if i use baserom from a english device, what will happen if I use with my german RAW files?

Thyraz said:
Yeah, also wondered about that Kaiser rebuilding tutorial.
Talked to a few people over PM who have the same problem.
But even in the Threads nobody who knows more about flashing/ROMs seem to be willed to help out with a fre informations. :-/
Still confused about the needed baserom in this thread.
-Is this available for Niki? (Where)
-Why do i need it / why can't i rebuild a rom ONLY with my phone and need something like a bsserom?
-if i use baserom from a english device, what will happen if I use with my german RAW files?
Click to expand...
Click to collapse
well..nice qustions..to which obviously I cant reply..hope someone will be so kind to help us out.

Thyraz said:
Still confused about the needed baserom in this thread.
-Is this available for Niki? (Where)
-Why do i need it / why can't i rebuild a rom ONLY with my phone and need something like a bsserom?
-if i use baserom from a english device, what will happen if I use with my german RAW files?
Click to expand...
Click to collapse
a baserom is nothing more then a normal rom, just put a rom you like, together with the dumped filen in the kitchen folder. maybe ruu needs some information from the rom file itself, which are not present on the device.
what you find on your device is just that what you dumped. (but after hardreset)
.. i know that this not matters for you anymore. but eroG needs to know.

therealholg said:
a baserom is nothing more then a normal rom, just put a rom you like, together with the dumped filen in the kitchen folder. maybe ruu needs some information from the rom file itself, which are not present on the device.
what you find on your device is just that what you dumped. (but after hardreset)
.. i know that this not matters for you anymore. but eroG needs to know.
Click to expand...
Click to collapse
well yes I defenitely needed to know these things...
now, if it is not of too much trouble for you, where do I find a baserom and is there a guide on how to do it...just to avoid stupid mistakes while doing it?
thanks a lot

So, from baserom there are not much information used. (Perhaps Header information for Rom file, or something like that)
My new ROM is (more or less) the same result as on my device?
And Baserom isn't a own file format, i can use the wwe-rom postet here in the forum?
thx for help

Thyraz said:
And Baserom isn't a own file format, i can use the wwe-rom postet here in the forum?
Click to expand...
Click to collapse
Yes that should work fine.

request guide on how to get dumped rom back to device
i've read alot about how to dump rom from device and how to get dumped rom back to device.
the more i read i got confident how to dump rom .... did it .. and now have my 4 raw files.
on the other hand the more i read about how to get dumped rom back to device ... more and more i got unsure how to do it.
so please all senior posters and specialists - can you please post a cookbook on how to get it back to the device ?
thanks ! alot and keep up the good work here !

Sackbauer, I totally agree with him.
I have 4 Raw files for a Norwegian ROM, but how do can i "transform" them into a acctually "flash" file?
Please someone with the knowledge, write a "easy to understand/ step by step" guide to the ones that don't have a clue about this..
Ole

im getting kinda confused with this also, dumping the rom is no big deal, but putting it back together and flasing my phone with it, thats the big how to...

I has contact with Tom.
And he busy with vietnamese new year now.
He said will back after 1,2 day and answer all questions..
Don't worry

... good to hear that tom will take care after his new year ;-)
also keep my fingers crossed that someone is able to check radio rom and possibly enable gps and wifi ...

let me try first:
- download this kitchen
- Copy your part01.raw and part02.raw into the BaseRom Folder of this kitchen
- Copy a Nike RUU_signed.nbh into the BaseRom Folder (e.g. tom_codons rom just open the. exe with winrar and extract the file)
- Open !Begin.cmd, press 2 and do everything, what is prompted
- Open !Cook.cmd and do what is prompted
- when HTC Rom Tool is opened press Rom_Builder and ... right from System. Then Choose os_new.nb and press built
i wrote this without testing again. so if i missed something tell me, please and i'll try to help.

sounds good !
will try it later this evening and will let you know ...
thanks so far

omg .... it appears that i just "cooked" my first rom out of my dumped files from my niki .
thanks therealholg for your guide !! thats what i was looking for.
the only thing which makes me a bit nervous about reflashing my just cooked rom onto my device is that during cooking it sometimes says "file not found".
but after ignoring these messages i have a nbh file which obvioulsy was not in the folder before !!! ;-) yeah
so, now i know how to revert the process but i am to anxious to try it as this is my only niki.
lets see and wait what others say about the step by step guide of therealholg ...
in anyway - you made my day therealholg
cheers

wow... thanks for this...
tryed it out and works...
the only thing is that it still says Niki Project on the boot screen...
everything else works just fine

marazi said:
wow... thanks for this...
tryed it out and works...
the only thing is that it still says Niki Project on the boot screen...
everything else works just fine
Click to expand...
Click to collapse
You can add the splash screen in HTC Rom Tool.

therealholg said:
let me try first:
- download this kitchen
- Copy your part01.raw and part02.raw into the BaseRom Folder of this kitchen
- Copy a Nike RUU_signed.nbh into the BaseRom Folder (e.g. tom_codons rom just open the. exe with winrar and extract the file)
- Open !Begin.cmd, press 2 and do everything, what is prompted
- Open !Cook.cmd and do what is prompted
- when HTC Rom Tool is opened press Rom_Builder and ... right from System. Then Choose os_new.nb and press built
i wrote this without testing again. so if i missed something tell me, please and i'll try to help.
Click to expand...
Click to collapse
What to do with part00.raw and part03.raw?

Part00.raw is the are with IPL, SPL and Splashscreen. We don't want to override our new SuperCID Bootloaders
Part03.raw is content of your local storage ... i think you can't flash this area with ruu.

hi all friends...!
I'm just back from some days busy with vietnamese new year.
And have made code kitchen for reconstruct a dumped rom niki device.
What we need to do now ?
1. Copy part02.raw u dumped from original rom to Tools folder and run step1.bat
2. Extract RUU_signed.nbh from Ship rom and put in ShipRom folder.
Link download :
http://www.asia.htc.com/download/RU....707.09_Radio_Nike_1.58.16.27_signed_Ship.zip
Or here :
http://www.asia.htc.com/download/RU....871.14_Radio_Nike_1.58.16.27_signed_Ship.zip
3. Run Reconstruct a dumped rom.cmd in my Tools and wait some times.When page DOS done it will exit .U go to Update_Rom folder already have new RUU_signed.nbh.This files reconstructed your original Rom with your languages.
Have funs..!

[REQ/Q] Rogers Call Display. How to cook a dll file into a ROM?

Hi all, I'm trying to make Fido Call Display to work on my Device, and I found the solution here. However the solution requires me to cook the rilphone.dll file into the ROM that I'm using (NAFT's v2.3). I've never cooked a ROM before and I'm far from understanding the procedure, but I don't think it's that hard to add a file in a cooked ROM. Can you guys help me out with this?
Please show me how to add/replace rilphone.dll in NAFT's v2.3 ROM. Thank you.

Replied on other thread

Da_G said:
Replied on other thread
Click to expand...
Click to collapse
Da_G said:
Yes, the reason my method does not work is because the rilphone.dll is not signed with a trusted certificate as I stated..
Pretty much leaves the only option as cooking it in, unless you are already using a ROM with a modified nk.exe in XIP to disable certificate checking.. then you can just drag and drop rilphone.dll and reboot.. but since stock ROMs are not modified in such a way, you cook it in, as all files cooked into ROM are trusted..
Unfortunatly there is no way to modify XIP without cooking either.
If a ROM is unprotected (still has it's rgu's) - download a ROM kitchen for your device.. extract the rom of your choice.. replace rilphone.dll in \OEM\OEMDrivers.. then re-assemble the ROM.. no registry manipulation needed.
For the raphael ROM kitchen, name your ROM "RUU_Signed.nbh", put it in \BaseROM
Run RaphaelKitchen.bat
select "e" for extract, then "a" for "From RUU_Signed.nbh"
let it go through its motions, when it's done replace rilphone.dll in \OEM\OEMDrivers
again in RaphaelKitchen.bat select "cf" then "b"
click "BuildOS" tab
click "Load ROM" button
navigate to RaphaelKitcken folder (has subfolders OEM, ROM, SYS, etc), press ok
click green "Go" button
when done, close the window
again the kitchen will go through some motions, when it pops up XVI32 and says "Page Pool Changer" in the command prompt window simply close xvi32
now it should prompt to flash to your device.. and you're done
Click to expand...
Click to collapse
Ya, I tried it with NAFT's v2.3, but it seems that the file is protected... the file can't be read.

I'm not sure I understand, you tried to cook the file into ROM and it gave you an error about it being protected? Or do you mean you tried to copy the file to the device, and it wouldn't let you overwrite? If that's the case that's why I suggest renaming rilphone.dll to rilphone2.dll before you copy to device, and then change the registry to point to that.. that way you don't have to overwrite the file that's already on the device.

Da_G said:
I'm not sure I understand, you tried to cook the file into ROM and it gave you an error about it being protected? Or do you mean you tried to copy the file to the device, and it wouldn't let you overwrite? If that's the case that's why I suggest renaming rilphone.dll to rilphone2.dll before you copy to device, and then change the registry to point to that.. that way you don't have to overwrite the file that's already on the device.
Click to expand...
Click to collapse
i tried what you told me to do on the other post; Rename the file, and extract it... I have no problem renaming the file, but when I tried to extract it with Raphael Kitchen, I got error like "Cannot read the file" or something like that... here is the dump log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
Click to expand...
Click to collapse
Nothing was extract.

hmm, sounds like the ROM kitchen is having a problem handing the .nbh you fed it, try it with a stock nbh and see if it works..
the rom you are trying to extract may be protected from extraction.
Just to make sure, you are trying to extract the ruu_shipped.nbh in \baserom.. which is the ROM image, somewhere in the range of 50 to 200mb large..

Da_G said:
hmm, sounds like the ROM kitchen is having a problem handing the .nbh you fed it, try it with a stock nbh and see if it works..
the rom you are trying to extract may be protected from extraction.
Just to make sure, you are trying to extract the ruu_shipped.nbh in \baserom.. which is the ROM image, somewhere in the range of 50 to 200mb large..
Click to expand...
Click to collapse
I redownload the Rom and it seems to work now. I can finally extract it.
As for the rilphone.dll... do you have the right one for Rogers Display? and the one that will work for Fido as well?
edit: I successfully reflashed my ROM, but the display thing doesn't work. Beside replacing rilphone.dll is there any reg I need to change? (can you give me the right rilphone.dll file?
I got the rilphone.dll file here

Sucessfully cooked in NaFT's v3.1, however it still doesn't work. It always show unknown Caller.
any help here would be much appreciated

Better Mobile App

welcome