HOW TO: Build your own rom, by ITJE **UPDATED 11 nov**

[itje]

Itjes Guide on how to cook your own rom, fast and dirty J Part 1
First of all, this guide will not tell you everything you need, I cant show you where to find reg entries, where all files are located. It’s a guide that will show you the basics. I will tell you how to extract a official nbh to os.no, how to dump it to respective oem and sys folders where you will do your “cooking”
First of all download Hypercore Kitchen here (http://forum.xda-developers.com/showthread.php?t=325061), then run the install file.
You will now have a folder called hypercore on your desktop, and a folder called core, located on c:\core


After install, download this fixed batch folder: batch (http://rapidshare.com/files/66570739/Batch.rar.html) or from mirror here: Batch (http://www.megaupload.com/?d=0HXYC6KW)
Delete the batch folder in c:\
Extract it to c:\core, and replace the original one.

The reason for doing this, is that there had to be some changes in the batch files for it to work.
Now you have a functional hypercore kitchen and you can start working.

I am gonna release a OEM, SYS and ROM folder for you, but not yet. I want you to understand how mutch work it takes to build a rom, and you need to go through some of the steps that all the other chefs must when they build roms. Why not just make it simple and give you everything? There is a answer to that, and you might not like it: Because I don’t want to….
Download your official RUU from here (ftp://ftp.xda-developers.com/Uploads/Herald/Official%20WM6%20roms/)
Use winrar or similar to extract the files in the installer, choose extract to a folder.
Open the folder you extracted the files to, and find the RUU_signed.nbh
Copy it to c:\core\tools

Open your command-promt (dos editor)
Go to c:\core\tools

Your command promt should now look something like this:

http://i143.photobucket.com/albums/r130/itjelta/1.jpg

When this is done, you must enter this: nbhextract ruu_signed.nbh
The nbh will now be extracted and in the core\tools folder you now have all the files dumped from the nbh
The screen should now look something like this:

http://i143.photobucket.com/albums/r130/itjelta/2.jpg

See the second last line Extracting: 06_OS.nb
That is the file you will need.
Rename the 06_OS.nb to OS.nb
Copy the OS.nb, then close the core\tools folder
Move to your desktop, and open the hypercore folder
Then enter the extract folder, and paste your OS.nb there
Go back to hypercore main folder, open the Panel folder, then open the Extract folder.
Inside the extract folder you will find a file/shortcut called Dump .nb and .bin

Now a panel will open and give you 4 options:
Now you are dumping the OS.nb into a xdump folder located in panel\extract

http://i143.photobucket.com/albums/r130/itjelta/3.jpg

Your answer here is 1 since im doing this guide for heralds
Now a new window is gonna pop up and tell you that in that windows your OS.nb should be placed, and if you did what I told you correctly, then the OS.nb is located there already. So close that window, and then another option in the command promt will ask you to hit enter when ready, witch I now suppose you are.
The OS.nb is now being extracted into the xdump folder located in the extract folder. This takes aprox a minute or so.
When the OS.nb is finished extracting, you will get a option to start pkg.tools. just close that option,its not working for some reason, I never really looked into it, I just did a “workaround”
In panel\extract you will find pkg tool

Start the pkg tool, and you get a command promt window, read it, and then press enter.
Now you should see this:

http://i143.photobucket.com/albums/r130/itjelta/4.jpg

Choose option 3
Pkg tools will now open.
Go to the file menu in upper left corner, chose open, then browse to hypercore\extract\xdump\
Highlight the dump folder and press ok.

GO TO NEXT POST IN THIS THREAD

[itje]

You should see something like this:

http://i143.photobucket.com/albums/r130/itjelta/pkg.jpg


Forget the missing manifests.
Now choose the Tools meny in pkg tools, and build packages, this will only take max a minute. (you will see nothing, just wait a bit.
When you have done his, browse to you xdump folder, open it, inside you will see the dump folder, rename the dump folder (not the xdump) to packages.
Copy the new packages folder and paste it into the hypercore\extract folder. Then close the pkg tools.
From now on, I will not give you screenshots of everything. You should get the picture on how it works now.
You will see a new commandpromt window, giving you 5 options, you choose option 4: Move oem and sys to hypercore\build.
You will get a question if you wanna backup, type n for no this time.
This takes 2-3 minutes, depending on your computer. The oem and sys is being moved to hypercore/build. Where the building process is gonna happen.

Next step is to go back to hypercore\panel\extract.
Open the dump XIP tool, and you get a new pop up window, just close it and press enter in the command promt. A new commandpromt window show you option 1 and 2, do both options, and when you have done this, the oem, sys and rom folder contains all you need to cook.

But that comes in next lesson.

I have now written this as easy as I can, if you don’t understand this, I cant help you more in this process, because I cant give it to you in a easier fashion.

Have fun
Itje

[itje]

Part 2 of Itjes cooking lessons

How to add and remove and build your rom
I assume you have followed the instructions in the first part, learned to extract both the .nbh and the os.nb into rom, sys and oem folders.

My way of cooking:
First you need to find out what you want and not want in your rom. I will try to guide you into building a small apps rom.
So first I do, is deciding what I don’t want to have in my rom, and I usually go to the sys folder, and start removing stuff I don’t use:
But before you start removing in sys, highlight the sys folder, right click and choose properties, uncheck the read only box, if you don’t you can’t edit files.

Remove:
Transcriber + Transcriber_lang_04xx (xx is the country code in your rom) + Transcriber_ Lang_04xx_DPI_96
See what you need to do? Remove all the folders with the name transcriber in it
You can also do this with: Office, windowslive. Internetsharing, entertainment (games)
Be careful removing in SYS folder, delete wrong stuff, and you will have a brick when flashing.
That’s a easy “clean up” of the sys, there are also other stuff you can do.

You can make your own startup image, that is located in the Redist_dpi_96_resh_240_resv_320 folder, and is called welcomehead.96.png, edit with either adobe photoshop or corel, or any other picture editors that support png files.
Open the welcomehead.96.png and do your changes, save and your done. How to and all that with photos/pictures im not gonna do, so you need to find a way to do so yourself.
Now, you can go to OEM folder, where you can add and remove a lot off stuff.
I will not show you everything, you must figure some stuff out yourself.

But download OEM packages (This is easy to fin, its all over the xda forum.
Im assuming you have found in some stuff you wanna add, in.ex total commander, htc home, networkwizard, CommManager. Ocourse you can add more or less.
Add the oem packages into the oem folder. Total commander and networkwzard don’t require removal off default files from the oem folder, but comm. Manager do, and so do htc home. The way I use to find duplicate files, is before I add the oem packages, I open in.ex the new package with comm manager, and I highlight the OEM folder and rightclick and choose searchtab. Search for files, type in search “comm.” And all files containing the word “comm.” Will be displayed, dele them (make sure they belong to comm manager, that the names matches the one in your package)

When you have searched for all files in your package, and deleted them from the OEM folder, you can add you package.
Follow same steps for all packages you add, that can have duplicate files, if you don’t you will get error when building the rom, and the build process will terminate, tell you what file is duplicate. You must then find the file, and remove it (don’t remove the one in your new package)

You can also delete stuff from oem folder, I will take as example adobe.
The easy way to remove adobe, is to find a oem package with adobe, so you can see what files needs to be deleted. Use same way as I showed you with comm manager.
You can also delete gif files, png files and wav files to make more space, be carefulll so you don’t delete files that are needed by applications you wanna keep.
Now I hope this was clear enough.

Now you can go to the hypercore/panel/build section where you will find buildOS, run it it follow steps there.

If you get errors with duplicate files, you need to remove the duplicate and start buildOS again. And continue to do so if you get more errors.
But when the buildOS is finished, close it and a new window will pop up, chose your device, and press enter, and your os.nb will be built.
flash it to your device, and test it. If it didnt work, then you have done something wrong, or im just a lousy teacher ;)

This was a very easy guide, I hope you find it usefull. There are lot of things you can do more then I have described now, but all you need is posted all over the forum. And if your dedicated enough, you will find all you need, just be patient. You cant find it all in one day,and you cant understand it all in one day.

Have fun
Happy cooking
cheers

[itje]

----------------------------

[3sr3v3r]

Good work. Hopefully we can get some new roms going around.

[LordPhong]

After install, download this fixed batch folder: batch or from mirror here : batch

Where's the link to the batch download?

[itje]

Where's the link to the batch download?

right there



lol, was a bit tired yesterday, forgot to add the link :)

[trallala]

Cool - thank you itje for all the effort and time you are investing...
Can't wait for the next parts :)

[itje]

Cool - thank you itje for all the effort and time you are investing...
Can't wait for the next parts :)

thx

has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?

[oddball1]

When is the next part due? I really am eager to cook!!!

[itje]

When is the next part due? I really am eager to cook!!!

havnt started on it yet :)
So I dont know maybe this weekend, but not later then the end of next week :)

patience, my friend, patience ;)

[LordPhong]

is the next part just making the extended rom portion? I think there's a tutorial somewhere on this site but I can't seem to remember off the top of my head, right now.

[LordPhong]

Download your official RUU from here

I'm being a pain in the arse again. there's no link there and I don't know if it's the same one as the official tmo release. I know I can probably use that one but would rather not.

[zacwhite15]

hey itje the links for the new batch files doesnt seem to be working. i tried them and it just keeps popping up saying it cant DL


edit: nevermind i got it too work. it was blocked on the isp i was using.

[LordPhong]

thx

has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?

Rename the 06_OS.nb to OS.nb
Copy the OS.nb, then close the core\tools folder

where do we copy the OS.nb to? Since, I didn't know, I, manually, had to do it.

Copy the new packages folder and paste it into the hypercore\extract folderThen close the pkg tools.

This didn't work for me. I had to manually past it in %systemroot%\Core\Extract\Packages after I closed the pkgtools. For some reason, it didn't find the Packages folder correctly.

After that, I followed everything else and it worked fine. Just as you described. Just waiting for part dos (spanish not MS-DOS).

[punkcell]

everything works fine up until the end waiting on farther instructions.

[itje]

EVERYTHING YOU ASK FOR IS ALLREADY THERE, START READING........


Just as its clear, from now im not gonna answer anyone who ask for something thats allready described in the tutorial.

But the link for ruu was not there, I'll give you that..

[ginolin]

i am cooking my chinese rom ,and thanks you working.

[itje]

i am cooking my chinese rom ,and thanks you working.

Glad I can help :)

[oddball1]

Honestly, if anything you did went wrong, is because you are not reading and reading it again before you do it!

Up to now, everything is well explained

[JLine05]

I remember itje saying that you may have to keep the ROM at 50mb or more for it to work. Has anyone verified that it has to be more than this to flash? Id like to cook one that has almost nothing in it.

[teamrinse]

awesome tutorial . cant wait for part two! successful up to this point:) :D

[papamopps]

I remember itje saying that you may have to keep the ROM at 50mb or more for it to work. Has anyone verified that it has to be more than this to flash? Id like to cook one that has almost nothing in it.

Great wish. I´m really looking forward to such a baserom like anichillus once cooked for wizard.
Nothing in and 33mb free ram.....

it was the baserom for all cookings...

Try to cook this - i wil test.

[Tha1nOnly]

thx

has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?


4 sure this was no problem using this tutorial itje ;) youre my man, wait and i will built german versions of touch it with the new htc album and some of the apps id like to have ;)

[Tha1nOnly]

itje when are the next steps coming? your howto is such simple had it in a few minutes and everything works fine for me until now. i wanna go on ;)

[kirstan]

Download your official RUU from here (ftp://ftp.xda-developers.com/Uploads/Herald/Official%20WM6%20roms/)


530 permission denied

[Tha1nOnly]

530 permission denied


tell me what ruu you need, which country?

[kirstan]

tell me what ruu you need, which country?

The English international one please

[Tha1nOnly]

The English international one please

i think you mean this one >> ftp://xdaupload:xda@ftp.xda-developers.com/Herald/Official WM6 roms/HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.e xe

[ginolin]

How To Manually Make your own OEM Package from a .cab

--------------------------------------------------------------------------------


please go on with your cource .i like it very much.

:)

You can use Cab analyzer.

But you might as well get your hands dirty. I have added the Cab in Question.

1. Put the Cab file in a working folder to play in.

2. Extract the Cab using a good unzipper like 7-Zip

3. You will get a whole bunch of files with weird names the only one that will make sense is the _setup.xml.

4. So let's open this in Note Pad and take a look.
First concentrate on translating all the filenames
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<characteristic type="touchpal.dll" translation="install">
<characteristic type="Extract">
<parm name="Source" value="touchpal.005" />
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

5. Simply said Rename "touchpal.005" to "touchpal.dll"
Any file left is either a .000 which is just a setup file not needed to make the app work so thow it away if it's mentioned in the XML file.

6. Now take a look at this part in the _setup.xml.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\DefaultIcon">
<parm name="" value="\Program Files\TouchPal\touchpal.dll,0" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\IsSIPInputMethod">
<parm name="" value="1" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\InprocServer32">
<parm name="" value="\Program Files\TouchPal\touchpal.dll" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}">
<parm name="" value="TouchPal" datatype="string" />
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

7. Make a new Blank .txt file in this directory and rename .txt extension to .rgu.

8. Translate the above registry settings into a correct format, the translation below should be reasonably self explanatory.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
REGEDIT 4


[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\DefaultIcon]
@="\\Windows\\touchpal.dll,0"

[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\IsSIPInputMethod]
@="1"

[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\InprocServer32"]
@=""\\Windows\\touchpal.dll"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

9. Put this information into the rgu file and be sure leave one blank line at the end.
As you can see i have changed the directory to Windows. Since everything you flash to rom starts out in the Windows directory anyway there's no sense in copying it into another directory later on because then it will take up twice the amount of space on the device.

At the moment i think that the best way to interpret the empty Param Name is as either "default" or @. I used @ because it's what i see mostly used for CLSID's. (Whatever they are good for)

10. No more need for the _setup.xml file thow it out of this folder.

11. At this point you should only have all the files that could be renamed and a .rgu file.

12. Time to get a Unique IDentifier Code.
Go here:
http://www.famkruithof.net/uuid/uuidgen
Press Create and copy the code.

13. Rename the something.rgu to 659626bc-7794-11dc-8314-0800200c9a66.rgu

14 Create a new blank.txt file and without doing anything with it rename it to 659626bc-7794-11dc-8314-0800200c9a66.dsm

15. In the case of this app, it will not need a shortcut in the folder nor an initflash.txt file
Create a blank textfile again and change the extension .lnk the extension should now dissapear. On the first and only line type "23#"\Windows\APPNAME.exe".
And then save the file as "Shortcutname.lnk".

16. Download BuildDSM.zip and unzip.
Now read closely.
Drop the folder Containing all the files on top of the BuildDSM.exe.
The .DSM file should now populated with the needed info.
I still don't know what it's good for but i think it has some sort of use as some Cooks swear by it.
Why can tell my why this is so important? But you do this before adding initflash and option.xml becuase those will not go into rom.

17. Now this app will not need an initflashfiles.txt because it doesn't need a shortcut to the app but in case it does need it
Creeate a blank File with the name initflashfiles.txt
Write down:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Directory("\Windows\Start Menu\Programs"):-File("Shortcutname.lnk","\Windows\Shortcutname.lnk ")

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Take note off adding blank lines just for fun.

17. Create another Blank text file and name it option.xml.
Open it in notepad.

And paste in this
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="My New SuperDuper App" group="Applications - 300 Group" checked="true">
<Tip>My New SuperDuper App</Tip>
<Guid type="p">659626bc-7794-11dc-8314-0800200c9a66</Guid>
</Item>
</Items>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Note that You put the earlier created UID into the xml file.
If your package consists of more than one folder (in the case of WLM and office)
Ad extra lines for every extra folder with their UID numbers.

So it will look like this.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Guid type="p">659626bc-7794-11dc-8314-0800200c9a66</Guid>
<Guid type="1">50898fbc-e5a3-45e4-9cf2-a04a8a01d69b</Guid>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now when you open your BuildOS this app will be selectable so you can choose to Cook it or not.
Oem Packages without option.xml will always be cooked into rom.
Note that "<Tip>" is the info when you highlight the App in BuildOs.

18. Fini

I will ad a part how to adjust it so you can make SD installer for this to, soon.

Variables found in installers

%CE1% = Program Files
%CE2% = Windows
%CE4% = Windows\Start Up
%CE5% = My Documents
%CE8% = Program Files\Games
%CE11% = Windows\Start Menu\Programs
%CE14% = Windows\Start Menu\Programs\Games
%CE15% = Windows\Fonts
%CE17% = Windows\Start Menu

There are more variables so if any one knows more please tell.
Please report Inconsistencies and let's see who's the first one to get a working TouchPal OEM package.
BTW we can't publish it as it's not going to be Freeware and it's being patented at the moment. Which doesn't mean you can make it for personal use and PM it so others can test it
You can grab the cab from http://www.cootek.com/ or try with another of course.

[pkoper]

How To Manually Make your own OEM Package from a .cab

--------------------------------------------------------------------------------


please go on with your cource .i like it very much.

:)

You can use Cab analyzer.

But you might as well get your hands dirty. I have added the Cab in Question.

1. Put the Cab file in a working folder to play in.

2. Extract the Cab using a good unzipper like 7-Zip

3. You will get a whole bunch of files with weird names the only one that will make sense is the _setup.xml.

4. So let's open this in Note Pad and take a look.
First concentrate on translating all the filenames
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<characteristic type="touchpal.dll" translation="install">
<characteristic type="Extract">
<parm name="Source" value="touchpal.005" />
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

5. Simply said Rename "touchpal.005" to "touchpal.dll"
Any file left is either a .000 which is just a setup file not needed to make the app work so thow it away if it's mentioned in the XML file.

6. Now take a look at this part in the _setup.xml.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\DefaultIcon">
<parm name="" value="\Program Files\TouchPal\touchpal.dll,0" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\IsSIPInputMethod">
<parm name="" value="1" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\InprocServer32">
<parm name="" value="\Program Files\TouchPal\touchpal.dll" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}">
<parm name="" value="TouchPal" datatype="string" />
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

7. Make a new Blank .txt file in this directory and rename .txt extension to .rgu.

8. Translate the above registry settings into a correct format, the translation below should be reasonably self explanatory.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
REGEDIT 4


[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\DefaultIcon]
@="\\Windows\\touchpal.dll,0"

[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\IsSIPInputMethod]
@="1"

[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\InprocServer32"]
@=""\\Windows\\touchpal.dll"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

9. Put this information into the rgu file and be sure leave one blank line at the end.
As you can see i have changed the directory to Windows. Since everything you flash to rom starts out in the Windows directory anyway there's no sense in copying it into another directory later on because then it will take up twice the amount of space on the device.

At the moment i think that the best way to interpret the empty Param Name is as either "default" or @. I used @ because it's what i see mostly used for CLSID's. (Whatever they are good for)

10. No more need for the _setup.xml file thow it out of this folder.

11. At this point you should only have all the files that could be renamed and a .rgu file.

12. Time to get a Unique IDentifier Code.
Go here:
http://www.famkruithof.net/uuid/uuidgen
Press Create and copy the code.

13. Rename the something.rgu to 659626bc-7794-11dc-8314-0800200c9a66.rgu

14 Create a new blank.txt file and without doing anything with it rename it to 659626bc-7794-11dc-8314-0800200c9a66.dsm

15. In the case of this app, it will not need a shortcut in the folder nor an initflash.txt file
Create a blank textfile again and change the extension .lnk the extension should now dissapear. On the first and only line type "23#"\Windows\APPNAME.exe".
And then save the file as "Shortcutname.lnk".

16. Download BuildDSM.zip and unzip.
Now read closely.
Drop the folder Containing all the files on top of the BuildDSM.exe.
The .DSM file should now populated with the needed info.
I still don't know what it's good for but i think it has some sort of use as some Cooks swear by it.
Why can tell my why this is so important? But you do this before adding initflash and option.xml becuase those will not go into rom.

17. Now this app will not need an initflashfiles.txt because it doesn't need a shortcut to the app but in case it does need it
Creeate a blank File with the name initflashfiles.txt
Write down:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Directory("\Windows\Start Menu\Programs"):-File("Shortcutname.lnk","\Windows\Shortcutname.lnk ")

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Take note off adding blank lines just for fun.

17. Create another Blank text file and name it option.xml.
Open it in notepad.

And paste in this
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="My New SuperDuper App" group="Applications - 300 Group" checked="true">
<Tip>My New SuperDuper App</Tip>
<Guid type="p">659626bc-7794-11dc-8314-0800200c9a66</Guid>
</Item>
</Items>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Note that You put the earlier created UID into the xml file.
If your package consists of more than one folder (in the case of WLM and office)
Ad extra lines for every extra folder with their UID numbers.

So it will look like this.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Guid type="p">659626bc-7794-11dc-8314-0800200c9a66</Guid>
<Guid type="1">50898fbc-e5a3-45e4-9cf2-a04a8a01d69b</Guid>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now when you open your BuildOS this app will be selectable so you can choose to Cook it or not.
Oem Packages without option.xml will always be cooked into rom.
Note that "<Tip>" is the info when you highlight the App in BuildOs.

18. Fini

I will ad a part how to adjust it so you can make SD installer for this to, soon.

Variables found in installers

%CE1% = Program Files
%CE2% = Windows
%CE4% = Windows\Start Up
%CE5% = My Documents
%CE8% = Program Files\Games
%CE11% = Windows\Start Menu\Programs
%CE14% = Windows\Start Menu\Programs\Games
%CE15% = Windows\Fonts
%CE17% = Windows\Start Menu

There are more variables so if any one knows more please tell.
Please report Inconsistencies and let's see who's the first one to get a working TouchPal OEM package.
BTW we can't publish it as it's not going to be Freeware and it's being patented at the moment. Which doesn't mean you can make it for personal use and PM it so others can test it
You can grab the cab from http://www.cootek.com/ or try with another of course.

Nice one ginolin!

You could have just posted the link to Noonski' guide.

http://forum.xda-developers.com/showpost.php?p=1575728&postcount=48

[itje]

Nice one ginolin!

You could have just posted the link to Noonski' guide.

http://forum.xda-developers.com/showpost.php?p=1575728&postcount=48

now thats tha hard way to do it, lmao

[ginolin]

Nice one ginolin!

You could have just posted the link to Noonski' guide.

http://forum.xda-developers.com/showpost.php?p=1575728&postcount=48

yes ,it is also can used for us ,hah:p

ITJE,can you gei us a course on how to change the ROM's language? and how to rebuilded the ROM?

thanks .......

[Tha1nOnly]

now thats tha hard way to do it, lmao

show us the easy way itje ;)

[itje]

search for "package creator"

[Tha1nOnly]

search for "package creator"

thousand thanks ;) nice work you do on the forum

[itje]

see post 3 for updates

[neiltoe]

Awesome tutorial with the batch files. Thank you I was able to do my own in no time. I am a total novice just got my wing a week ago found alot of useless apps and wanted to make it the way I do my PC "custom". With your help it was a really smooth process.

Great tutorial!

[FreeLancer2k7]

Hello itje,

thank you very much for your detailed howto!! It's really good and easy to follow.
Although, there's one thing which is not quite clear to me. Extracting one of the offical Rom's gives you a Sys and an OEM folder of build 17745. If you want to work with a newer one (say 18333), do you have to replace the sys folder with the new one? So i take the OEM from my herald Rom and the sys from Kaiser/Hermes/what else? And is the languag important in any way (Oem german, sys english)?

Thanks again,
FL

[ivanmmj]

I've been wondering about porting ROMs as well...

[itje]

Hello itje,

thank you very much for your detailed howto!! It's really good and easy to follow.
Although, there's one thing which is not quite clear to me. Extracting one of the offical Rom's gives you a Sys and an OEM folder of build 17745. If you want to work with a newer one (say 18333), do you have to replace the sys folder with the new one? So i take the OEM from my herald Rom and the sys from Kaiser/Hermes/what else? And is the languag important in any way (Oem german, sys english)?

Thanks again,
FL

Yes you have to use sys folder if you wanna port. oem is your device specific drivers and all, and the sys contains the os.

search in the development and hacking (http://forum.xda-developers.com/forumdisplay.php?f=260) section for answers to porting.

[ICP-Fan]

What does this error mean?

[error]
packages.sof missing!

Edit: I am the king of morons! if I would have EXPLICITLY followed the instructions, I would not have encountered this error.

[Bchocolate1221]

i really dont know where im going wrong here, but im able to do everything up until i have use the dump .nb and .bin, everything in the hyperCore\Panel\Extract folder has a missing shortcut.. did anyone else have this problem?

[ivanmmj]

i really dont know where im going wrong here, but im able to do everything up until i have use the dump .nb and .bin, everything in the hyperCore\Panel\Extract folder has a missing shortcut.. did anyone else have this problem?

Dunno.... I never use the dump .nb .bin shortcut...

[pickpocket]

:confused: I just read all of this.....my head hurts. :confused:

[ivanmmj]

:confused: I just read all of this.....my head hurts. :confused:

lol. At first it made my head hurt, too. But after a while, it was like "ohhhhhhh... Duh!"

[s4vva]

I read somewhere that we can not recook the Touch-IT roms as Itje has removed the rgu's. In one of the first posts Itje states he will be releasing his OEM & Sys folders, I would like to know if anyone knows what the latest is? Itje any plans to release them?

[ivanmmj]

I read somewhere that we can not recook the Touch-IT roms as Itje has removed the rgu's. In one of the first posts Itje states he will be releasing his OEM & Sys folders, I would like to know if anyone knows what the latest is? Itje any plans to release them?

He did release another ROM, the "stripped...almost" by his own words. It has all the RGU's intact.

[loco41]

i cant get it to extract the os.nb any help ?

[loco41]

nevermind got it to extract ;)

[s4vva]

He did release another ROM, the "stripped...almost" by his own words. It has all the RGU's intact.

cool do you remeber which ROM that was? I wanted to do something for myself based on Touch-IT 3.0, touchflo no cube.

[lurker525]

I've been having a small problem with this tool. I've followed the guide to the letter several times through now and I keep coming up with os.nb files that won't work on my wing. I've extracted the os.nb from the T-mobile RUU and for some reason if I try to reassemble the sys and oem folders without altering them after they've been extracted I end up with an os.nb file thats smaller than the original. Everything seems to work fine with the extraction tool but something seems to be getting lost somewhere. If i try to flash this to the phone it will just hang at the first splash screen after a reboot. Has anyone else had this problem? Is it a problem with the rom I'm trying to use or is it something that I'm doing wrong?

[ivanmmj]

Have you also extracted the XIP and moved it?

[lurker525]

Have you also extracted the XIP and moved it?

Yes I have extracted the XIP and it is moved over into the rom folder in Build OS. I have what looks like what I'm supposed to have, ROM, SYS and OEM folders. Does anyone have a link to a known working rom that I can try with just so I can figure out where I'm screwing up? I'd like to eliminate as many possibilites as I can.

Update: I tried to create the os.nb one more time and flash it and now I'm even more confused. It finally decided to work for some reason. But I'm still wondering is it normal for an os to be one size when you start out and another after running it through the kitchen? I've made no modifiactions at all to this rom and yet its still coming out about four megs smaller than it starts. And for whatever reason nothing loads from the extended rom.

[ivanmmj]

Yes I have extracted the XIP and it is moved over into the rom folder in Build OS. I have what looks like what I'm supposed to have, ROM, SYS and OEM folders. Does anyone have a link to a known working rom that I can try with just so I can figure out where I'm screwing up? I'd like to eliminate as many possibilites as I can.

Update: I tried to create the os.nb one more time and flash it and now I'm even more confused. It finally decided to work for some reason. But I'm still wondering is it normal for an os to be one size when you start out and another after running it through the kitchen? I've made no modifiactions at all to this rom and yet its still coming out about four megs smaller than it starts. And for whatever reason nothing loads from the extended rom.
Nothing loading from the extended ROM is strange unless the ROM is edited to act that way.
The ROM being smaller might be because of Tadzio's tools when they reconstute the ROM, they tend to cut the extra fat.

[lurker525]

Nothing loading from the extended ROM is strange unless the ROM is edited to act that way.
The ROM being smaller might be because of Tadzio's tools when they reconstute the ROM, they tend to cut the extra fat.

Thanks for the assistance.
Just for reference its not an issue of it not trying to load the extended ROM. It tries but nothing gets installed. Not that it matters much to me I don't usually let it anyway. Just thought it was a little strange.

[ivanmmj]

Thanks for the assistance.
Just for reference its not an issue of it not trying to load the extended ROM. It tries but nothing gets installed. Not that it matters much to me I don't usually let it anyway. Just thought it was a little strange.

That IS strange... sounds like the extROM is missing...

[ivanmmj]

cool do you remeber which ROM that was? I wanted to do something for myself based on Touch-IT 3.0, touchflo no cube.

Touch IT....Kind off...stripped..for wing (http://forum.xda-developers.com/showthread.php?t=341983&highlight=stripped+kind)

[Bigg Wedge]

ITje,

Thank you for all of your effort on all of your ROMs, Thank you for your work on this guide. You are correct, all of it is on the site somewhere. So far I have not found it all and have yet to cook a ROM, but I will with the guidance you have provided. Just started realizing what My PPC was capable of, but I know now how to find out. And for that good Sir, Thank you. I shall attempt to repay it to the forums by creating something all Wing users can enjoy. Look for it in My Sig(soon I hope)

Much Gratitude,
Bigg Wedge

[itje]

ITje,

Thank you for all of your effort on all of your ROMs, Thank you for your work on this guide. You are correct, all of it is on the site somewhere. So far I have not found it all and have yet to cook a ROM, but I will with the guidance you have provided. Just started realizing what My PPC was capable of, but I know now how to find out. And for that good Sir, Thank you. I shall attempt to repay it to the forums by creating something all Wing users can enjoy. Look for it in My Sig(soon I hope)

Much Gratitude,
Bigg Wedge

ure welcome, good luck with the cooking

[lurker525]

Not sure if I thanked the OP for this guide before but anyway thanks for your work in making this guide.
Just as a suggestion you might want to remind anyone trying to use your kitchen that they also need to read all of the instructions in the Hypercore thread as well.
I'm migrating all of my tools over to a fresh install of XP on my laptop and missed a step setting things up. It gets kinda frustrating when you forget to update the device.txt file and you can't figure out why you can't get Buildos to work properly.:o

[Carty]

In previous posts you said the device wont boot or just stay in the Splash screen after flashed with the built ROM. Did you overcome that now? How?

Regards,
Carty..

[papamopps]

jus as a hint. the "hypercore" thread is psoted in several subforum. becuase it was the first (and only?) kitchen that was working for ALL devices....

BUT anichillus comes from wizard-forum. So there is also a thread to Hypercore kitchen. perhaps you can find help there.

OR: www.anichillus.net

regards

[lurker525]

In previous posts you said the device wont boot or just stay in the Splash screen after flashed with the built ROM. Did you overcome that now? How?

Regards,
Carty..

Not totally positive you were asking me, but I have managed to overcome the problems I was originally having.
The problems I was having seems to be related to my desktop having issues and apparently not being entirely stable. On the first several build attempts it just didn't build working roms and on one flash it apparently wiped out the Extended ROM completely.
I guess the lesson to be learned is to not try to build roms on a computer thats not known to be 100 percent stable.:eek:
Other than that make small changes when starting out and document everything change, or else you'll have a very cool looking paperweight. ;)

[ducvader]

http://i143.photobucket.com/albums/r130/itjelta/4.jpg

Next to where it says Herald next to the Device: - Mine doesn't say Herald. Mine has a blank after device. How do I get it to say Herald? I've followed everything step by step but mine doesn't come up the way everyone else probably has it. The steps are easy - getting to the finish line seems to be the hard part of this all.

Duc

[ivanmmj]

Did you set up the c:\core\ack\device.txt file to say set device=Herald?

[ducvader]

Did you set up the c:\core\ack\device.txt file to say set device=Herald?

Wow - geez - Thanks - for that. I've read and read Itje's guide to building rom 10+ times and no where did I see that part in the guide( Maybe its there and I missed it or I need to read another guide as a supplement to this one). Hopefully that's all I need to finish up the rom I'm trying to build with the buildOS.exe program. Thanks.


Duc

[ca7onc12ak]

im trying to install the touch it program onto my wing but every single time i try to do it, it installs two percent and my phone shuts off and the installation screen gives me the error code 270 which basically says that theres an update error, i tried restarting my computer and reinstalling it, but its still giving me the same problem...any suggestions? thanks!

[ducvader]

Man this Cooking Rom stuff is a harder and more time consuming than I thought. 8 tries and all bricks so far. Guess I just can't go in there and delete every single program that I choose not to use and hope that the rom will work. Will try deleting one program at a time and updating it to the same but newer version. BABY STEPS!

[ttran001]

Man this Cooking Rom stuff is a harder and more time consuming than I thought. 8 tries and all bricks so far. Guess I just can't go in there and delete every single program that I choose not to use and hope that the rom will work. Will try deleting one program at a time and updating it to the same but newer version. BABY STEPS!

Wait until you start adding new programs that dont work correctly...
Or try fixing stuff since you took out too much.

Cooking is not easy and yes very time consuming..

Good luck,

[ivanmmj]

im trying to install the touch it program onto my wing but every single time i try to do it, it installs two percent and my phone shuts off and the installation screen gives me the error code 270 which basically says that theres an update error, i tried restarting my computer and reinstalling it, but its still giving me the same problem...any suggestions? thanks!

This thread it about cooking. Please post this in the appropriate thread. Post it in the thread belonging to the version of touch-it you're flashing. Thank you.

[ivanmmj]

Man this Cooking Rom stuff is a harder and more time consuming than I thought. 8 tries and all bricks so far. Guess I just can't go in there and delete every single program that I choose not to use and hope that the rom will work. Will try deleting one program at a time and updating it to the same but newer version. BABY STEPS!

Welcome to our world... the aspirin is that way. The angry swearing room this way. The "why won't this crap work???" room to your left. And finally, the "Why doesn't it do what I want it to do even though YOU cooked it" room to your right. :D

[prscott1]

Welcome to our world... the aspirin is that way. The angry swearing room this way. The "why won't this crap work???" room to your left. And finally, the "Why doesn't it do what I want it to do even though YOU cooked it" room to your right. :D

LOL! Of course, some of us have the "I'll never try to cook again" room in our house!

[loco41]

can i make the hypercore kitchen portable ? have everything on a usb ?

[KrInEn]

It seems when I run this as per tutorial everything goes smooth until I get to the pkg tool part. I open the xdump/dump folder and everything on the screen is blank but the headers. it looks something like this.

[Selected Path]
C:\Documents and Settings\Admin\Desktop\HyperCore\Extract\XDump\dum p

[Core OS]

[Versions]

[Language]

[DPI]

[Certificates]

[Missing Manifests]


Now I have tried three different roms to cook and they all come up like this. i tried to just move on and everything sill worked up to the point of moving the sys and oem folders. Only about 47 files make it to the sys fold, zero to the oem and about 1400 to the missing folder.

For some reason this just does not sound right :)

Any help would be appreciated

[ivanmmj]

can i make the hypercore kitchen portable ? have everything on a usb ?

That's what I'm wondering... I'm too lazy to rewrite all the scripts...

[ivanmmj]

It seems when I run this as per tutorial everything goes smooth until I get to the pkg tool part. I open the xdump/dump folder and everything on the screen is blank but the headers. it looks something like this.

[Selected Path]
C:\Documents and Settings\Admin\Desktop\HyperCore\Extract\XDump\dum p

[Core OS]

[Versions]

[Language]

[DPI]

[Certificates]

[Missing Manifests]


Now I have tried three different roms to cook and they all come up like this. i tried to just move on and everything sill worked up to the point of moving the sys and oem folders. Only about 47 files make it to the sys fold, zero to the oem and about 1400 to the missing folder.

For some reason this just does not sound right :)

Any help would be appreciated

Have you set it to Device=Herald?

[KrInEn]

Have you set it to Device=Herald?

Yes I forgot to mention that I did do that also :)

[ivanmmj]

I just realized.... xdump? There shouldn't be an xdump. Should be C:\Documents and Settings\Admin\Desktop\HyperCore\Extract\dump I believe.

[KrInEn]

I just realized.... xdump? There shouldn't be an xdump. Should be C:\Documents and Settings\Admin\Desktop\HyperCore\Extract\dump I believe.

I just deleted the xdump folder and ran the dump and it re-created the folder along with the xdump/dump.
48 files to sys folder
0 to oem
and 4700 to missing
Still with the blank pkg tool. Im also using netcf3.0 on my pc I dont know if that makes a diffrence

[ivanmmj]

No. I use .Net 3.0, also.

hmm... And you're decompiling a Herald ROM?

You can always just grab my kitchen files and cook with those, btw.

[KrInEn]

Alright I got it working now up to the point of "build OS" I get and error on option one that flashes real quick it says:
removing RGU Files
File not found - c:\core\kitchen\temp\dump\*.rgu

It only says that because I manually made the path, before it said "could not find specified path"

:-(

[contracontra]

It seems when I run this as per tutorial everything goes smooth until I get to the pkg tool part. I open the xdump/dump folder and everything on the screen is blank but the headers. it looks something like this.

[Selected Path]
C:\Documents and Settings\Admin\Desktop\HyperCore\Extract\XDump\dum p

[Core OS]

[Versions]

[Language]

[DPI]

[Certificates]

[Missing Manifests]


Now I have tried three different roms to cook and they all come up like this. i tried to just move on and everything sill worked up to the point of moving the sys and oem folders. Only about 47 files make it to the sys fold, zero to the oem and about 1400 to the missing folder.

For some reason this just does not sound right :)

Any help would be appreciated

Same sh*t, guys... Please, help :(

[ttran001]

Same sh*t, guys... Please, help :(

Is this on a new rom your creating or trying to recook a rom created by someone else?

It looks as if the rgu files have been removed since this is a standard thing most cooks will do, including myself.

Regards,

[contracontra]

Is this on a new rom your creating or trying to recook a rom created by someone else?

It looks as if the rgu files have been removed since this is a standard thing most cooks will do, including myself.

Regards,

Yes, its not a standard rom. Is there a way to edit it? (i just need to delete some apps, change a bootscreen and replace some system dll`s containig icons and graphics)

[ttran001]

Yes, its not a standard rom. Is there a way to edit it? (i just need to delete some apps, change a bootscreen and replace some system dll`s containig icons and graphics)

Who's rom are you trying to recook?

Please make sure to ask the original cook before trying to recook their rom.

As long as they approve it I can help you recook it but not until then.

Regards,

[DaveTeu]

Okie so I've BuildOs-ed and wen to create OS.nb from Sys and OEM.

what do I do now?

How do i try toupdate my fone using the hardspl method (err..like what Itsblack did it)

[DaveTeu]

*cry* tried Flashing, and now my Hard-spl-ed c800 is bricked *cry*

[contracontra]

Ok, I have my modified os.nb file and nbgen01 utility, how can i create the nbh file to flash my device?

[ivanmmj]

*cry* tried Flashing, and now my Hard-spl-ed c800 is bricked *cry*

If it's hard SPLed already, just flash any other ROM and it will come back to life.

Okie so I've BuildOs-ed and wen to create OS.nb from Sys and OEM.

what do I do now?

How do i try toupdate my fone using the hardspl method (err..like what Itsblack did it)
AND
Ok, I have my modified os.nb file and nbgen01 utility, how can i create the nbh file to flash my device?

Use Dark Simpson's HTC Rom Tool to make your NBH. It signs the file. Even though HardSPL flashes any signature, it still requires A signature.