We have lost the exteneded roms again.
This is the 2nd time that I know of.
I think this has to do with the fact that they were not linked to post thus unkonw files get killed. I read that some were when I first came here.
I have most of them and will start uploading them again, linking them to a post.
Anybody have a better idea or know why they have gone?
Not sure whether they've been deleted or not, unless you have been reposting. They are under BlueAngel_Roms instead of Extended_Roms. Things seem to keep getting moved.
And what are they doing there ?
Sure I have been uploading to ExtenedRoms for over an hour now.
I will move the buggers!
Rename The Folder Exteneded_Roms
Clean up the file names
Gee I love house work thought I was would be cooking in the Rom Kitchen, but no.
We are going to have to post the links as they got killed once before.
Thought you were out.
Can you belive this!
Got a folder name that says "Dont touch MDAIIIUser Uploading" and we have dowloades.
You around need so help.
ok done
cleaned up the Exteneded_Roms
Will post in the morning.
We need to take these apart and find what version they are then rename them.
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/IIs Asia WWE Ext ROM.zip
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/Seimens_SX66_Ext_ROM_ENG.zip
ftp://xda:[email protected]_MDAIII_Extended_Rom_Inc_DeviceInfo.zip
Do you need some assistance with the Excel sheet for ROM Versions and contained cab files?
Is there a neater way of structuring the ftp server directories? Is there any way of setting folder permissions on the server for read/write only and not alter/delete?
Bebbo
Do I need help in the Exteneded Rom Kitchen. Does the .... (ok no bad jokes)
Sure do BIG Time!!! Its not my kitchen, I just work there!
The Idea of the Kitchen is not realy to find out what version number Orange Rom A has for an application but to see if Orange's Rom A has application / Patches that are better than our base.
The Sheet just is a list of the files which go:
Base (I-mate) + Rom A + Rom B = Extended Rom Kitchen (ERK) Rom
My end goal is to generate a ERK Rom Version which is as upto date as possible.
And have this info on wiki so we dont need to hunt for it.
How far am I, Well The UK orange rom has been looked at but info not posted in the kitchen.
( I think RTP worked on that but I am not sure as I was haveing PMs with few people about that rom. )
We have the 3 roms above that need to be looked and info posted in the Kitchen and added to the Excel Sheet.
The Excel Sheet needs to be made to look nice so the rest of us can undersatand it.
We need to check against the "List of know Blue angels" to see what rom is missing and see if we can find it.
Oh yes and its friday, I get to pick my kids as its "The 3rd weekend of every month" and as my ex-wife has got a date, thus By 12:00.
Chances of me doing much till monday are ZERO.
So you want a job, pay is s**t, hours are bad, it can get hot in the kitchen when there is a fire and you lose all your stuff.
You need to understand Roms, read cab files, use your brain and most of all admit to the fact that you don't know everything and thus ask.
I am looking for Pastry Chef as well. One that can write applications.
Is there any way of setting folder permissions on the server for read/write only and not alter/delete?
Click to expand...
Click to collapse
Given that at the moment we are all the user XDA, I would say no.
What we need is a "BA_Admin" that revokes the rights of XDA to Read only, then we just get into the next problem, the person that posted (XDA) can't update it, so he needs to be BA_Admin...
The FTP site is a public place and like Toilets some people just can't pee in the Pot like the rest of us and sonebody has to clean up the mess.
Is there a neater way of structuring the ftp server directories?
Click to expand...
Click to collapse
Got some ideas, then share them with us.
Will have a look at dir structure but seems reasonable to me at the moment (Though Extended is the correct spelling ). Will use my WinCE CAB Manager to see what if anything is different on rom's you haven't had chance to view yet and generally assist where I can.
I will have a look at the orange rom as well, time permitting.
Would it be better to extract the .nbf files to sub dirs under the Extended_ROMS dir and have similar structure for radio and CE ROM?
ie ->
BlueAngel/Extended_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/ms_.nbf
(With cabs extracted as well under a cabs sub dir?)
BlueAngel/CE_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/nk.nbf
BlueAngel/Radio_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/radio_.nbf
Or leave as is and use the kitchen with a CAB's dir under it with all known versions of cab files so we can select the most appropriate ones?
I've posted the document on the Orange 1.12.139 ROM into the Kitchen. It's fairly large since there is so much in the Orange ROM.
Here's a link:
ftp://xda:[email protected]_1_22/Docs/Orange_WWE_1.12.139_ExtROM.doc
Unfortunately nothing really new though (Wish I had known you were doing this rom - just wasted 2 hours!).
I haven't looked at the WModem.exe update yet - any ideas what this is for?
Who keeps moving files in the BlueAngel section of the FTP server? Makes life difficult having to keep searching each time. Please let us all know what you are trying to achieve as it keeps breaking links on other web pages!
Running it comes up with this text:
The utility will simulate this device as a wireless modem, and let your PC/Notebook be connected to network wirelessly.
Before you press the 'Start' button, please make sure you have connected the device to your PC/Notebook by serial or IrDA connection and disabled the Activesync.
When the wireless modem is activated you will not be able to receive any voice calls.
Click to expand...
Click to collapse
It then gives options for Serial, IrDA, USB and Bluetooth. Start, Stop and View Log buttons. Plus connection status LEDs - Connection, Send Data and Receive Data.
I've never tried it. I tend to use something more direct for dialup from my laptop.
OK guys!!!
I don't know what your naming system is but I've uploaded the O2 UK EXT ROM and I've called it "O2_UK_XDAIIs_Ext_ROM_112178_WWE.zip". This one is the original from my device.
Regards,
Dom
Ext_ROM password??
MDAIIIUser said:
ok done
cleaned up the Exteneded_Roms
Will post in the morning.
We need to take these apart and find what version they are then rename them.
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/IIs Asia WWE Ext ROM.zip
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/Seimens_SX66_Ext_ROM_ENG.zip
ftp://xda:[email protected]_MDAIII_Extended_Rom_Inc_DeviceInfo.zip
Click to expand...
Click to collapse
Any known pw's for those .nbf files? I tried Rom editor but couldn't recognize the pw's
Re: Ext_ROM password??
Cyber-mate said:
Any known pw's for those .nbf files? I tried Rom editor but couldn't recognize the pw's
Click to expand...
Click to collapse
They aren't .nbf files???????? They are zipped up (rar'd up) cab files extracted from the extended roms.
+*+*+*+ FOR INFO +*+*+*+
The xda3nbftool has an extra command line option of -t which attempts to discover the xor key used to encrypt the .nbf files. This seems to work well for all files except the radio_.nbf file which causes it problems. Try it on roms that you are having problems with to see if it is the correct key. You can check the resulting .nba file with a hex editor to ensure the PH20B and other data is shown at the beginning of the .nba file.
+*+*+*+*+*+*+*+*+*+*+*+
I have pulled the above ext roms apart and the version numbers are as follows:
IIs Asia WWE Ext ROM.zip = Version "1.12.925 WWE"
Seimens_SX66_Ext_ROM_ENG.zip = Version "1.20.115 WWE"
T-Mobile_MDAIII_Extended_Rom_Inc_DeviceInfo.zip = Version "1.06.117 WWE"
Files renamed appropriately so any links will now be broken (plus the fact that some kindly person has renamed the Extended ROM directory to its correct spelling!)
Related
People; how can make a cab that automatically makes the settings for GPRS, MMS, WAP etc.? Every time I upgrade my pda2k to a new GREAT ROM, I have to make these settings manually. And as you know, GREAT developers on this site works hard and provide us with the latest unofficial ROMs in a short time.
PS: I'm not a programmer, so telling me only 'use a cab manager' won't be enough...
The helmi roms already have this, look for the "operator" cab files.
My operator isn't in the list. So I need to prepare a cab file by myself...
nonereal said:
My operator isn't in the list. So I need to prepare a cab file by myself...
Click to expand...
Click to collapse
This should help give you an idea of what you're looking for;
http://wiki.xda-developers.com/index.php?pagename=BA_PersonalCAB
When I did the Orange UK cabs I basically extracted the settings from the cabs that came in the original WM2003 ExtROM (that my phone came with). Then I created new cabs using WinCE Cab Manager by copying the ones Helmi shipped with his ROM and replacing the settings with the extracted Orange ones.
I have attached the relevant files I used, you could possibly hand edit these and then make cabs yourself if you can't find the settings shipped with your phone.
Thanks, I will try this.
I had posted this to the mamaich's thread. posting here as well since it is wizard specific:
I've been trying to use the tools for building an HTC wizard ROM. Now, before starting out on any modifications, I simply tried to break apart and rebuild it. So, I extracted a ROM using typhoondecode_v5, then followed this:
1. prepare_imgfs.exe OS.nb -nosplit
2. viewimgfs.exe imgfs_raw_data.bin
3. BuildImgfs.exe
But then my imgfs_raw_data.bin is not rebuilt and stays at its original self. The buildimgfs tool does not give me an error, however the last 3 lines of its output reas something like :
total sectors: 0000
used: <some number>
free: <some number>
I searched the forums but couldn't find an answer. Saw a couple of posts having the same prob but no answer. Since I havent done any modifications to the ROM and have tried with both AKU2.3 and AKU 3.3 (and custom ROMs as well as official Qtek ROMs), the ROM that i am using is also not an issue.
Now, since there are so many custom wizard ROMs out there and ppl swear by mamaich's tools so there must be a solution. Please help me out or let me know if there is no way out and I ve to use some other way to make ROMs, i also found bepe's kitchen post but couldn't find how to use it for wizard..
Thanks in advance.
for the wizard, this line:
1. prepare_imgfs.exe OS.nb -nosplit
should be:
prepare_imgfs.exe 80040000-OS.nb –nosplit
see if that helps...
prepare_imgfs.exe 80040000-OS.nb –nosplit
Click to expand...
Click to collapse
I used that one only, and I have no probs with the "prepare" and "view" commands. I correctly get the bin files as well the modules/files are correctly extracted. I have problem with the "build" and "make" commands.
side question. should have thought of this earlier. how do you know its not updating? its been stated that this file will for some reason not change date/time and size.
hopefully that helps.
see this post:
http://forum.xda-developers.com/showpost.php?p=1110892&postcount=13
see this post:
http://forum.xda-developers.com/show...2&postcount=13
Click to expand...
Click to collapse
oopsie I am sure I read that post some time ago when I was collecting all the info for ROM cooking, but somehow forgot abt it when I started. Thnx for reminding
But There's another problem after this. When I run make_imgfs command it gives me some weird characters, however, a couple of posts above the one that you pointed at, there is a comment that I've to give the name of the old file only instead of new one. Will try that tonight when I go home and report back.
Thnx for the help dude
Anyways, another question:
This one is about the "universal id" part (dont remember the name of the app correctly, smthing like genuuid), for which all packages do we have to use this app? I mean if I wanted to add an executable (say a.exe) to the ROM, is it enough to simply add it to the "dump" directory and follow the build/make path or do I have to use the genuuid app path, or is this app used for some special kinda apps?
Thnx in advance. I'm not a newbie by any means in programming, GSM, and programming for GSM etc (I work in a Nokia GSM BTS project ) but am cooking a ROM for the first time.
yupz, worked...I was able to rebuild the rom. (Though the size/date-time stamp of the final 80040000-OS.nb also remains the same as the older one. I take that to be OK like the same thing happening with img_raw_data.bin. Haven't flashed the ROM onto my phone to see...)
Moreover, about the uuidgen program, I found out that it is bepe's way of doing it. We can do it the mamaich way that is simply add the programs that we want to the /dump folder and rebuilding. Correct me if I'm wrong.
Now that I've tested the waters, I'm on to making a custom ROM myself...
Thnx xda-dev...
shantzg001 said:
yupz, worked...I was able to rebuild the rom. (Though the size/date-time stamp of the final 80040000-OS.nb also remains the same as the older one. I take that to be OK like the same thing happening with img_raw_data.bin. Haven't flashed the ROM onto my phone to see...)
Moreover, about the uuidgen program, I found out that it is bepe's way of doing it. We can do it the mamaich way that is simply add the programs that we want to the /dump folder and rebuilding. Correct me if I'm wrong.
Now that I've tested the waters, I'm on to making a custom ROM myself...
Thnx xda-dev...
Click to expand...
Click to collapse
Hi shantzg001
i too am doing similar steps and all gone well ( i.e breaking/rebuilding).
but im surprized why dump dir size is extremaly different in compare to
imgfs_raw_data.bin . I tried some OS.nb and got the size of dumb approx
456kb or 368 kb or some MBs. Also dump dir contains only some modules and
some files.
Am i doing some mistake or u too r getting similar result
reply ASAP
thanx
nandlal
That seems strange, because in my case the dump folder is even bigger than the bin file (more than double the size)..
Can you list out the exact steps that you are following, and which ROM were you breaking apart?
I am a software developer by trade and so I hope I will be comfortable with creating my own ROM. However, I have no idea where to begin! Can anyone point me in the right direction?
on the wiki you can all read about it.
xmoo said:
on the wiki you can all read about it.
Click to expand...
Click to collapse
Thanks for the quick replu xmoo. I've had a look there before but it's not answering any questions. I have no idea what dev environment I need nor how to do it. Am I missing something or is it just my Sunday head?
you need a kitchen, in the kitchen you unpack a ROM image, you then exchange, remove or add files to the extracted ROM image. then you repack it. thats it. no programming skills involved.
and all information regarding kitchens can be found in the wiki, I did at least.
schaggo said:
you need a kitchen, in the kitchen you unpack a ROM image, you then exchange, remove or add files to the extracted ROM image. then you repack it. thats it. no programming skills involved.
and all information regarding kitchens can be found in the wiki, I did at least.
Click to expand...
Click to collapse
Thanks for the info.
I have Hard-SPL'ed my X1 and am ready for a new ROM now. I have downloaded a NBH file and used the NBHUtil to unpack it. Is this the point at which I customise the individual parts? If so what do I use to do this with the NB files?
NBHUtil is not a kitchen, its a utility only. And NB files are just the components of the NBH file, like a NB for the radio part, a NB for the OS part, a NB for ... you get the idea. The actual contents (exe, dll, eg.: files that ARE windows mobile) are encoded inside the NB's.
Search for "RaphaelKitchen" version 0.62, download that. Once you got that far, get back in here and I'll give you the config files you'll need for the RaphaelKitchen.
Instructions on how to do what: http://forum.xda-developers.com/showthread.php?t=427507
In that message, leave out the parts about dumping and get directly to the instructions for the kitchen. The actual "cooking" (thats what its called, hence its called a kitchen) comes between instructions "e, b (for dumped ROM),space key" cuz now you just unpacked the ROM and you have tons and tons of DLLs, EXEs, eg.: you unpacked the NBH in NBs and decoded the NBs to its contents.
You cook by removing and adding stuff to the respective folders.
After you did that, continue by following the post: "c, a, press BuildOS Play icon and wait to finish, Close BuildOS, close PagePool Changer and press space" which equals putting the files back together and compiling a new NBH which you can flash...
and i'm sorry but the WIKI acutally REALLY does explain all that:
http://wiki.xda-developers.com/index.php?pagename=Kaiser ROM Kitchen Tutorial
The RaphaelKitchen is a modified version of alex kitchen for the kaiser, it is essentially exactly the same.
Cheers Schaggo!
I was looking at the Xperia Wiki not the main Wiki My bad sorry.
I'll give this a go later and report back
No problem, no problem. As I said, as you start cooking, get back in here and I'll provide pre-edited config files with all the settings for the X1.
schaggo said:
No problem, no problem. As I said, as you start cooking, get back in here and I'll provide pre-edited config files with all the settings for the X1.
Click to expand...
Click to collapse
Hi, could you provide the pre-edited config files for X1? Thanks.
Ok so here's what I have done:
Download and unpacked RaphaelKitchen 0.62 as stated.
Ran it with 'e' then 'a' as the command line parameter to extract the NB files again (just to see).
Found all the NB files in BaseROM folder and a sh*tload of mixed files in the temp folder. At the root I have a couple of BIN files as well as some NB related files. dump_imgfs and dump_xip are the main folders in there with lots of bits beneath then. Is this right?
Then ran the build ROM commands as you stated. Pagepool wasn't open though(?) or couldn't see it anyway. Everything else went to plan and I got a NBH file in the end.
I expected the packages folder to be populated but nothing went in. Has this all gone to plan?
**Edit: Also never saw PagePool **
Here is the extra config you need for X1
Extract and put the files in the root of the RaphaelKitchen.
Run "X1Kitchen.CMD".
This is what I am using for "e"xtract and "c"ook a room and it's working perfectly w/ me. Other options is not tested or use by me.
I even added/modded some more files. Replace all files and run RaphaelKitchen.cmd and continue as instructed in the manual.
Cheers guys. Will try this config tonight and get back to you
In the extract ROM there are two options:
- one needs RUU_signed.nbh only
- the other one needs RUU_signed.nbh + part01.raw and part02.raw
which is the right one to choose? if b): where do i get those files?
/edit: never mind, figured it out myself
Flashing now :-D
For future reference, if some more people ask:
if you just want to unpack an existing ROM image (nbh-file) use option 1. this unpacks the file and fills up the folders with the files to cook with.
if you want to reconstruct a ROM you (or someone else) dumped from his device, chose option 2. this decodes the raw-files (dumps) according to (simply spoken, please forgive my inaccuracy ) the template which is given by the nbh-file. without the nbh-file the kitchen doesnt know how to decode the raw-files, it needs a reference file (the nbh) to do so.
hi i'm a noob to the whole wm scene and i'd like to learn how to cook my own roms as well. I've downloaded the kovsky kitchen but i can't find anywhere on how to use it. i've looked in the wiki but can't find how to use kitchens. maybe i've overlooked something. at any rate, if someone could post a link on a tutorial or any info that could get me started, it'd be greatly appreciated. thanks in advance
figurine said:
hi i'm a noob to the whole wm scene and i'd like to learn how to cook my own roms as well. I've downloaded the kovsky kitchen but i can't find anywhere on how to use it. i've looked in the wiki but can't find how to use kitchens. maybe i've overlooked something. at any rate, if someone could post a link on a tutorial or any info that could get me started, it'd be greatly appreciated. thanks in advance
Click to expand...
Click to collapse
take yer pick, but the first one looks okay!
http://www.google.com/cse?cx=000825...orial&sa=Search&cof=FORID:0&ie=utf-8&oe=utf-8
thanks! one more thing... should i backup my original rom? if so, how do i do this?
Hypercore and X1 "kovsky"
i just had to ask, well kovsky kitchen works for the experia right? so hypercore multidevice, shows no experia or kovsky config, #11 post says raphael kitchen xperia.cmd, so you can use that kitchen for x1 as well, so how do you get hypercore/X1? to work
Hello!
My question is: how can I extract for eg. programs .cab files from .image or .nbh ROM?
I want to get original Mobile Opera 9.5 from R2AA UK Generic ROM, because some other version of opera overwritten it and I don't want it - just need original one back.
Check this thread in Development and Hacking, a tool to view files inside nbh ROM files: http://forum.xda-developers.com/showthread.php?t=377514
Thanks! It helped. Is it also a way of cooking a new custom rom?
Edit:
I exported the file... but its "hidden" without option to make it visible. How to make it normally visible?
I'd really kick back, make yourself a couple of weeks worth of coffee and read, read read and then read some more.
There's quite a lot in the wiki on how to cook roms, which serves as a good start but to do it properly it will help to know some of the background to what you're doing.
Hence the reading.
FWIW I've just started playing with ervius visual multilang kitchen, it's quite nice, much better than some of the others. Do a search on it if you want to find it and try visualkitchen_v2_1
Of course it's a bit worrying that you want to cook your own roms, without knowing what's inside the one you're using.
IF you want the opera from r2aa and you're using a stock unmodified R2aa then look in windows (using a proper file explorer such total commander)
or use the search on here, as the one I posted has been linked a huge amount of times already, including 3 times in the past 2 days. .
http://forum.xda-developers.com/showthread.php?t=469420&highlight=kitchen
This is the link to ervius' kitchen
http://forum.xda-developers.com/showthread.php?t=377514
this is a good prog for viewing .nbh files
vinokirk said:
http://forum.xda-developers.com/showthread.php?t=469420&highlight=kitchen
This is the link to ervius' kitchen
http://forum.xda-developers.com/showthread.php?t=377514
this is a good prog for viewing .nbh files
Click to expand...
Click to collapse
nah you need to let people learn to use the search engine
he he he...just doing a good dead...maybe st peter will let me thru the pearly gates for this
Also im getting sick of seeing things in a thread and then never being able to find them again!!!
Same thing with prog and apps, ill download them then i can never remember what they are for, where i put them or where i unzipped them to...ARRRGGGGHHHHHH
vinokirk said:
he he he...just doing a good dead...maybe st peter will let me thru the pearly gates for this
Also im getting sick of seeing things in a thread and then never being able to find them again!!!
Same thing with prog and apps, ill download them then i can never remember what they are for, where i put them or where i unzipped them to...ARRRGGGGHHHHHH
Click to expand...
Click to collapse
Big folder (or series of folders) on the SD card with a text doc listing what does what. that's what I do..
I’ve started cooking my own ROM’s only a week ago. I wanted to share my experiences here as it’s not as easy as it seems Well, with the right settings, tools, references, etc it makes it easier though. So this is my sharing back to the community, my tutorial/reference guide on how to cook a ROM.
The result of my days of hard work is named DaxyROM and can be found here.
If you want to start cooking, be prepared to read a lot and spent a lot of time trying your home cooked meals. But when it boots and works as expected, you’ll enjoy all the time spent.
There are 3 steps I’d like to discuss in the following 3 posts:
1) Basic ROM extraction and cooking
2) Adding / Removing programs
3) Upgrading your XIP/SYS (aka install new OS version)
First of all get to know what you’re dealing with. Understand what SYS/EXT/OEM/ROM/XIP is ‘cause at the end of the week you can’t think of anything else. Good source here.
1 Basic ROM extraction and cooking
I’ll be using the Ervius Visual Kitchen and the official WM6.5 ROM from HTC to start with.
* Download Ervius Visual Kitchen. Always use the latest version.
* Download WM6.5 ROM’s from HTC
* Download CustomRUU.exe
Preparing the kitchen:
Extract Visual Kitchen (VK) to C:\Kitchen (will be refered to as Kitchen now)
Create a directory in the Kitchen named RomDump
Open the WM6.5 HTC ROM .exe file with Winzip
Extract the file named RUU_signed.nbh to the RomDump directory
Now open the Kitchen (erviuskitchen.exe). Ignore the warning messages
Click on the bottom left button named “Dump nbh/nb/payload”
Open the RUU_signed.nbh file and wait till it’s completed.
Enter the Kitchen\RomDump\dump directory
Move all files to Kitchen directory
There seems to be an issue with kitchen_build_rom.bat while building your ROM.
Modify your kitchen_build_rom.bat file from this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
if not "%errorlevel%"=="0" goto error
To this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
REM **************** if not "%errorlevel%"=="0" goto error
You’re now ready to go.
Built your first ROM – The Visual Kitchen Basics:
Click on the pull-down menu next to RHODIUM and select RHODIUM
Ignore the messages. You’ll see the screen building now
Fill in the name of your ROM at the ROM ver. Field
Check the “Real WM 6.5 AKU” field
Click on the “Other” button
Change the –PP value from 6 to 18 and click on the Close button
Save the settings: hit the “Save ROM” button. Filename must end with extension .erv.
You’re ready to hit the Create ROM button
Wait till it finishes
Now open the Kitchen\RELEASE_Rhodium directory
Copy the CustomRUU.exe to this directory and run it
You’re now running the HTC WM 6.5 ROM rebuilded by yourself
Right now your kitchen is ready to use and you can modify it as much as you like.
Part 2: Adding / Removing programs
Right now we know that the kitchen works. We have rebuiled the official version and it boots up fine. Make sure to test your extracted ROM works otherwise you will loose a lot of time. Now it's time to make changes. Keep in mind that the following is what I've teached myself and that there might be better methods in adding/removing packages.
The easiest is removing packages. Just double-click on the package and it won't be included. If you want it back, just double-click again and it's back in. Easy as that.
Keep in mind that you can't remove OEM packages and that if you're removing packages from the SYS you have to be carefull as you might run the risk you remove a core application and that Windows won't boot anymore. You can however safely remove packages like LiveSearch, MSTag, OneNote, etc without any problems.
The EXT directory is where all packages reside. This directory is devided in 2 sub-directories. One for Rhodium specific packages and one for Shared platforms. By default all applications are in the Rhodium directory but you might want to change this manually to Shared if you're planning on building for multiple platforms. For now we'll keep them in the Rhodium directory.
You need to either find EXT packages online, or you need to convert CAB files to EXT packages. That is basically it.
I've found a lot of new EXT files here: http://www.everythingdiamond.info/showthread.php?t=94. You can download new EXT folders and copy them into the VK\EXT\Rhodium\<built>\Rhodium_External_Packages directory. Now load VK and Load your previous saved config. Scroll down the list and you will see your new package. This package is not yet included in the Kitchen. This is useful if you're upgrading packages so you'll know which one is new and which one is old.
If you're upgrading packages, keep in mind that some do depend on each other. For example Manila heavily depends on all kinds of other packages. When you're upgrading one, upgrade the others as well unless you're certain there are no dependances. You'll find out when your upgrading. Make sure to safe your work very often so you can always revert back to your previous situation.
As I mentioned you can also convert CAB's to EXT. This can be done using the package-creator from Ervius. TotalFire Package Converter does the job as well, but I haven't used it yet.
Download your application as cab file. Open the package converter, open the cab file and it converts to an EXT directory. This EXT directory can be copied into the kitchen again.
Adding your own EXT is more complicated. For example if you want to create a package which holds all your registry tweaks.
You can either download this file and change the .reg file, or you can take the hard way and learn by using this tutorial: http://www.mediafire.com/file/j15nqfzkwz5/CreatingOEM.zip
Both are written by user kwbr. See here for more info: http://forum.xda-developers.com/showthread.php?t=480714.
I believe this concludes this section. You should be able to add and remove packages right now. Next stop, installing a different Windows build.
Please sent me feedback on how to improve my posts.
Part 3: Upgrading your XIP/SYS (aka install new OS version)
It's time for the last part of my Tutorial. This time I will explain how to upgrade your XIP/SYS.
First you need to find your new XIP/SYS. I get mine WM 6.5.1 at http://forum.xda-developers.com/showthread.php?t=544445 but there are probably more sources.
First you need to know what to get. If I'm taking the above URL as example, there are several files.
The first one you need is the XIP/SYS one. This however is the OS for a screen resolution of 480x600 (The Touch Pro2 has a screen resolution of 480x800). You still need this file as it the the base OS combined with the (wrong) resolution files. That's why you need the 2nd file named "0409 USA English United States (Includes COMMON DPI, required for others)" as well. This is the english version for all resolutions.
The first file you can just extract in your SYS directory. It will create a new directory with the new build number and a directory named Shared.
The Shared directory you need to move to your ROM directory. This means you end up with a new build number in the Shared directory.
Now we just need to make sure the resolution files are copied. This means you need to copy a list of directories. At first create a directory named SYS\<build>\dpi_192_resh_480_resv_800. Just extract the complete 0409 Language file into a temp directory and the create the following directory structure by moving directories:
Code:
SYS\<build>\dpi_192_resh_480_resv_800\0409\Base_Lang_0409_DPI_192_RESH_480_RESV_800
SYS\<build>\dpi_192_resh_480_resv_800\0409\Themes_Lang_0409_DPI_192_RESH_480_RESV_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\base_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\MediaOS_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\Phone_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\Redist_dpi_192_resh_480_resv_800
This concludes the SYS, now the XIP.
The zip file you downloaded also contains a directory named "MSXIPKernel".
Extract this directory to your ROM\Shared\<build> directory.
Now go into the directory ROM\Rhodium.
Inside the builds you can find the OEMXipKernel which are basically the device specific drivers.
Usually these drivers don't change, unless you are upgrading the OEMXipKernel using a newly released ROM from HTC.
For now you have to copy the original build directory over to the new directory and you're done.
Right now your OS is ready to cook:
Open your Kitchen
Open your saved configuration file
Change the XIP and SYS versions (top right) to the new build version
Hit the Create ROM button
You're all set
After creating your new SYS, I suggest changing some default values. For example changing Unsigned Themes/CAB Policies:
Open the file named OEM\Rhodium\0409\Operator Pkg\mxipupdate_oemoperators_100.provxml
Find the section <!--337.01_SecurityPolicy-->
Add the following lines:
Code:
<parm name="4101" value="8" />
<parm name="4102" value="1" />
<parm name="4122" value="1" />
<parm name="4103" value="16" />
<parm name="4097" value="1" />
Save the file
Cook your ROM
Basically this means:
ID 4101: Unsigned CABS Policy = 8
ID 4102: Unsigned Applications Policy = 1
ID 4122: Unsigned Prompt Policy = 1
ID 4103: Unsigned CABS Policy = 16
ID 4097: Unsigned Prompt Policy = 1
Now you won't get warnings if you install unsigned applications etc.
One last thing to keep in mind. Don't forget to grab a new version of the OEM directory once it gets released by HTC.
I've ran into a situation where ActiveSync ran out of memory and a new OEM fixed this.
Thanks
Ervius: Big thanks to Ervius for his great Kitchen and Package creator: http://forum.xda-developers.com/showthread.php?t=469420
Da_G: For providing the latest WM builds: http://forum.xda-developers.com/showthread.php?t=544445
hilaireg: For providing his tuturial which was my starting point: http://forum.xda-developers.com/showthread.php?t=521632
kwbr: For his tutorial on creating applications: http://forum.xda-developers.com/showthread.php?t=480714
Everyone I forgot to add. Make yourself known and I'll add you of course!
This concludes my Tutorial. I hope you find it useful. Please feel free to provide feedback so I can adjust the tutorial or provide answers.
Eventually I may try cooking my own ROM.
Not because I can't find any good roms out there.
But just for the simple fact that I want to learn how to do it.
Thanks for taking the time to write this all up.
Just what I was looking for. I have been searching and reading and searching and reading but not getting anywhere. After following your post I've dissasembled a ROM, renamed it, and then reassembled it.
Now I was just following a recipe and didn't understand everything that happened (what is the -PP value and why am I changing it?) but I'm finally making some progress. Looking forward to your upcoming posts.
BTW, I just used the official TMo US 6.1 ROM that CDGuider dumped and made available. It'll do while I'm learning but I'm really waiting for the Official TMo US 6.5 to be released so I can use it as the main ingredient.
S
sleonard said:
Just what I was looking for. I have been searching and reading and searching and reading but not getting anywhere. After following your post I've dissasembled a ROM, renamed it, and then reassembled it.
Now I was just following a recipe and didn't understand everything that happened (what is the -PP value and why am I changing it?) but I'm finally making some progress. Looking forward to your upcoming posts.
BTW, I just used the official TMo US 6.1 ROM that CDGuider dumped and made available. It'll do while I'm learning but I'm really waiting for the Official TMo US 6.5 to be released so I can use it as the main ingredient.
S
Click to expand...
Click to collapse
Let me know if I missed something. I had to do it from the top of my head so if I forgot to add an action, let me know and I'll add it.
PS, the -PP allows you to change the PagePool size (sort of swapfile for WM).
Some people set it to 0, some to 12-18. I found 18 to be working fine. I must admit that I have too little knowledge to truly understand the PP stuff to come to a clear correct value (I believe it's questionable, the values).
If anyone disagrees, let me know
This is a great post.
I've subscribed because I'm really interested in learning and once I've ran through it myself will reference it on my site for all to use.
Well done you, supply and demand.
Daxy, On Tuesday I get my Pro2 and begin to try. Thanks for a great post!!!!!!!!!!!!!
I download the files of 23069, for example, where should I hold?
Xip and sys...
Awesome Information!! Thanks a lot and I appriciate it because rarely people share knowledge!
Thanks for the clear tutorial! Looking forward to future updates!
really excited to start making my own roms...
thank you for taking the time and making this
hopefully in the future ill be able to contribute to the community...
my touch pro2 could use some of my own flavor lol
thanx for the effort ...
gonna read thru it when i am more awake ... lol ... this seem to be what i am looking for ... wanna cook my own rom but proper info is few and far between for the rhodium ... unless i waslooking in the wrong places ... hehehe
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Thanks all for your kind words.
I've updated Post 2: Adding / Removing programs
Hope you like it. Please let me know if anything is missing.
Next post will be regarding using a new version of Windows, where to place files etc. This one should be up in a couple of days.
eddy16112 said:
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Click to expand...
Click to collapse
Customized ROMs are protected. You cant dump them. You can only dump official ROMs.
eddy16112 said:
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Click to expand...
Click to collapse
ai6908 said:
Customized ROMs are protected. You cant dump them. You can only dump official ROMs.
Click to expand...
Click to collapse
Correct! even if the customized rom was unprotected you still would not be able to rebuild a rom off of it because of the loss of rgu's and dsm's in the origional building process. would be very difficult.. best thing to do is ask for the kitchen files from the chef and hope they can share.
edit: one thing you can do is use an app called rom imaged editor and open the nbh with that, you can grab individual files out, even protected roms you can.. then you can add things on your own.
I've changed the topic to My first Rhodium ROM. Though it would sound better.
joshkoss said:
edit: one thing you can do is use an app called rom imaged editor and open the nbh with that, you can grab individual files out, even protected roms you can.. then you can add things on your own.
Click to expand...
Click to collapse
I have extracted files from kooked roms no biggie. saves time from flashing for sure...
I have tried to extract all files from kooked rom too, and it seems to work. but might be able to use some dll files.
Everytime I build the ROM (rebuilding the stock rom, not config changes) towards the end the kitchen gives me a runtime error, I have tried on a 64-bit vista and 32-bit XP.
After reviewing the log it appears that the problem is:
Executing: kitchen_build_rom.bat.....
ERROR! (errorlevel: 1)
ERROR executing: kitchen_build_rom.bat
ERROR!!!
Wait some seconds...
No ''SVN'' folders present...