Camera Cab / How to strip down OEMAPPS? - 8525, TyTN, MDA Vario II, JasJam ROM Development

Hi folks,
I've been making my own ROM, trying to make it really, really bare basically and install everything from CABS (and trying to keep the windows directory with as few files in as possible).
As I don't much care for most of the OEMAPPS that are installed by default, I removed the OEMAPPS from OEM in the ROM. However, there is one thing in there that I do want: namely the camera.
If anyone could direct me to a camera cab (or better still, tell me how I can remove things from a package when they're all bunched in in a single folder) that'd be really helpful.
Thanks in advance!

caeci11ius said:
Hi folks,
I've been making my own ROM, trying to make it really, really bare basically and install everything from CABS (and trying to keep the windows directory with as few files in as possible).
As I don't much care for most of the OEMAPPS that are installed by default, I removed the OEMAPPS from OEM in the ROM. However, there is one thing in there that I do want: namely the camera.
If anyone could direct me to a camera cab (or better still, tell me how I can remove things from a package when they're all bunched in in a single folder) that'd be really helpful.
Thanks in advance!
Click to expand...
Click to collapse
if you want to remove the camera files before flashing, I'd suggest looking in my kitchen (check sig) and look at the camera packages in the OEM Pack. It'll give you a list of the files you can delete from your rom as well as the registry settings you could delete.

Related

Beta testing help - multiple cab install, settings backup, etc

Just that wanted to ask what ppl have found to be best ways to install all your favourite apps/settings if u are changing roms offten?
I just started recently and have tested some 3 or 4 roms now, but already i find that doing all my customizing and app install is tedious, so i was looking for some method to make it easier.
* i have seen an app that could roll multiple cabs into one - that would make reinstalling all cabs at once after new rom easier, but i cant find the app any more. any ideas on this one?
* backing up rom differences after doing customizations - what app could handle that? propositions?
If we can work some method to do this fast and easy we would get a lot more beta testers hence a lot faster development cycle could be achieved. (=
kakainis said:
Just that wanted to ask what ppl have found to be best ways to install all your favourite apps/settings if u are changing roms offten?
I just started recently and have tested some 3 or 4 roms now, but already i find that doing all my customizing and app install is tedious, so i was looking for some method to make it easier.
* i have seen an app that could roll multiple cabs into one - that would make reinstalling all cabs at once after new rom easier, but i cant find the app any more. any ideas on this one?
* backing up rom differences after doing customizations - what app could handle that? propositions?
If we can work some method to do this fast and easy we would get a lot more beta testers hence a lot faster development cycle could be achieved. (=
Click to expand...
Click to collapse
There are no shortcuts my friend. Some apps are installed to main memory and some to storage card, when installng apps there is interaction involved, therefore no universal solution.
Look here - you can integrate the new sys folders (apps) by building your rom in the kitchen (klick it on). http://forum.xda-developers.com/showthread.php?t=317866
You can do a backup with spb backup. This way you can keep all installed programs and changes. You can restor your backup in different roms too but you have to be aware that this would mess up a few thins.
Tryed this http://www.freewareppc.com/utilities/pocketpcinstallationcreator.shtml one out - managet to create install with multiple cab files - so far so good.
But when i installed this merged install on my wm5 emulator it ended up adding links to cab files in programms folder - so much for instalation - useless.
Gues the search goes on.
Make your own extended rom with all your cabs in, this will do the trick. Its quite easy - its not like cooking a rom - i could do a simple tutorial if people wish - it only requires 2 apps
Meschle - yes, please, a tutorial for extrom making would be good, as i am still a bit green to start cooking roms - extrom would be nice way to start i suppose.
meschle said:
Make your own extended rom with all your cabs in, this will do the trick. Its quite easy - its not like cooking a rom - i could do a simple tutorial if people wish - it only requires 2 apps
Click to expand...
Click to collapse
I would be very interested in this as well.
Cheers
Ok i'll post something tonight then in the artemis upgrading forum.
I'll keep it simple - the last tutorial posted by someone was way too complex - in the way i describe you'll make your own in 10 minutes
meschle said:
Ok i'll post something tonight then in the artemis upgrading forum.
I'll keep it simple - the last tutorial posted by someone was way too complex - in the way i describe you'll make your own in 10 minutes
Click to expand...
Click to collapse
You are one dedicated dude. I like it.
That's the spirit!
meschle said:
Ok i'll post something tonight then in the artemis upgrading forum.
I'll keep it simple - the last tutorial posted by someone was way too complex - in the way i describe you'll make your own in 10 minutes
Click to expand...
Click to collapse
That is a super solution! I would love it!
Hey guys one downside to ext rom way - when installing cabs it does not give you option where to install (main memory or storage card) so everything installs to main memory.
This is ok for the programs you normally install there and registry entries. You can make a new cab that installs directly to storage card but that is a different story
OK, now i am a bit confused. As i understand there is a ROM memory on Artemis(128MB) which is divided in multiple areas - IPL1, IPL2, SPL, Splash, Radio, OS, ExtRom.
This ROM memory is writable by way of flashing. There is also storage area(not microSD) in device and operative memory.
So, as i unterstand it, putting apps in ExtROM is a pure saving, cus ur storage memory is not wasted.
Do i understand it correctly?
With the artemis rom, if you omit extended rom in your nbh building you get more storage memory (an addition of roughly the size of the omited ext rom) Likewize if you include extended rom then you loose equivalent memory from storage - so there is no advantage to having apps (i.e executables) in extended rom but for convenience sake to have cabs and settings can be useful. I suggest keeping extended rom small (2mb) so you dont loose much storage space.
Extended rom tutorial added here http://forum.xda-developers.com/showthread.php?t=327203
well maybe not 10 minutes then
meschle said:
Make your own extended rom with all your cabs in, this will do the trick. Its quite easy - its not like cooking a rom - i could do a simple tutorial if people wish - it only requires 2 apps
Click to expand...
Click to collapse
For people who do not have an extended ROM - would'nt it be similar if they kept all the Cabs in 2577 Folder in the Storage Card with Autoexec and config files to execute them sequentially? I remember doing something like this when I was using the XDA IIs - but then now -
In my case, I rarely need to install anything except TomTom and Fullscreenkeyboard from SPB. The rest - I peek into the Cab using WinCE Cab Manager, then export the contents and now have made one big Cab (appx 4MB in size) with all my registry entries, tweaks, executables, shortcuts and copying relevant files into directories.
That way I execute only three cabs after a Hard reset and moreorless everyting is in place.
Yes dev - i used to have that in my orange spv - an autorun.exe in \2577 folder - last time i tried didnt work as i wanted - but i agree worth looking into.
With the ext_rom - the purpose was to add one for those that dont have.
Ok, was trying a quite a few roms that i had today, extracted em, but did not get the extrom.nb )=
Tried to open os.nb with winimage, but it kept saying something about wrong fat etc.
Is the extrom.nb different form os.nb and other *.nb? Why cant winImage open other nb files? Or is there something else i am missing?
Also, tiried SKtracker(didnt find any free app) demo - made snapshots before and after installing apps, then tried to export relevant registery subtrees.
That brings me to that there is no import functionality in phm regedit, but i found other free regedit app called TRE which can import/export edit etc.
Maybe this TRE tool is worth including in roms, if any cookers are reading.
Any better way to hack registery?
Hidden regedit
kakainis said:
That brings me to that there is no import functionality in phm regedit, but i found other free regedit app called TRE which can import/export edit etc.
(...)
Any better way to hack registery?
Click to expand...
Click to collapse
I mentioned this on another thread, but I discovered that FdcSoft's understated Task Manager v2.8 has a supperb regedit built in. It does everything that PHM Regedit does, but it can export and import really easily, just like Windows regedit. As meschle pointed out, PHM's is faster, but I still use the bloated Task Manager just because its regedit; and it also has lots of other stuff that comes handy on occasion.
Oh, great! So many stuff to fiddle with in meschle's PremiumPlus rom that I must have missed this one.

1st time cook a little confused

Hi. I've read hundreds of posts and followed dozens of tutorials. I'm aiming to gain an understanding of what actually happens during the rom cooking process and I think I'm getting there. I've used loads of different toolkits and kitchens and most recently I've been using 'romdonalds' which has given me a better understanding.
However I'm a bit confused about the difference between the dump directory with loads of files and folders, and the OEM/SYS versions of these which I've seen when using packagetool and buildos. I know how to go from the 'flat' structure to the oem/sys structure, but I don't know how to go back again.
I'd also like is to know what really happens behind the scenes when you click the go button in buildos.exe.
TIA
Matt
I could really use a little help to understand what's going on here. If there's some clear explanation of what actually happens during cooking that I've missed, could someone point it out to me please? I've searched thoroughly, read extensively, and pulled my hair painfully... but I just don't get it. I've analysed batch files in just about every kitchen there is but I've reached a point where I need some help.
If there's some unwritten quid-pro-quo requirement that I've missed before I can ask a question then tell me that too - I'm no freeloader, I've just donated to Slither2006 for his cube, and when I've fully grokked the process I'll write up everything I've learned in a really clear guide, I promise.
I'm not an idiot either - I was a technical architect at a large UK ISP until recently, doing stuff like building a huge virtualised server farm with custom management tools and a homebrewed iSCSI /LVM2 snapshot system that blows away anything commercially available, and now I work for myself... I've used HTC devices since the Blue Angel, also an Exec and now a hermes... but I could really use a hand here.
Thanks!
I suspect you are quite a bit ahead of me here, but here goes.
The OEM/Sys folders are just part of the Dump folder, but extracted and turned into a more logically arranged order for manipulation.
When you run buildos it just takes these and a few other bits such as the XIP section and puts it back in a format for rebuilding.
Best I can do I am afraid.
Thanks for your reply crazyc. It's getting a little clearer now. Can anyone else shed any light? Ideally I'd like to know exactly what buildos does to turn the organised folders back into the dumped ones.
Piecing it all together:
A: I know how to get the dump folder from a source rom (nbhextract->nbsplit->imgfsfromnb->imgfstodump).
B: I know how to make changes to the dump directory manually (add/delete files; extract/convert .hv files to .rgu; edit .rgu files and reconvert to .hv; edit initflashfiles.dat to create shortcuts on first boot)
C: I know that instead of all that I could convert the dump directory to the organised oem/sys pair (pkgtool) and know that in theory I could manage that with BuildOS.exe to integrate oem packages with the option.xml file in them - but I don't understand what's happening here relative to (B) above
D: I can turn the dumped folder (but not the oem/sys folder) back into a flashable rom (imgfsfromdump->imgfstonb->nbhtool)
Can someone who really understands what's going on explain where I'm confused?
Thanks
Matt
Here is my take about cooking....
When the dumped OS has all the rgu files in tact then spliting the dump folder as OEM and SYS will work.
Where as some OS do not have rgu file in them (some cooks prefer to cook this way...all OEM OS have rgu files). In this case you would have to use only the dump folder and edit default and user.hv to add and delete stuff. You cannot use package tool for this method.
You sure can turn OEM and SYS back to ROM, just use the right kitchen (Pandora, Bepe Kitchen, etc)
Hope this helps.

[TUT]ROM for everyone (video tutorial to cook the ROM )

Hi all
I was looking for the way to cook my own ROM. There is a heaps of info for a Kiser but not a Diamond. I had decided to start a thread that will show and explain in plain language how to do it on the Diamond. The aim is to have perfectly clean ROM without any unwanted applications or tweaks. The ROM will only contain bare minimum to run PDA. Everything else can be installed with cab files. Also registry tweaks can be applied after installation.
What is more important I want this thread to be a simple to follow guide to cook a ROM so everyone can make one for themself. Since I’m not an expert I welcome any help from anyone.
I had managed to cook my 1st ROM. I had removed some applications without modifying anything else.
I have tested it and it worked ok. However you perform it on your own risk and I take no responsibility if you stuff it up. Do not remove everything at once. Remove 2-3 application and see if it works. If yyou unsure just leave it alone. When you are confident you can remove the rest of apps. Also if you want to remove Opera and TouchFlo you need to change a setup files so lets leave it for now.
You need a Kitchen and the ROM file.
Video Tutorial (rigt click and Save target as)
Extract kitchen files directly to C drive (not to desktop as shown on the screen shot)
IMAGE
Extract rom files into BaseROM folder in the kitchen.
IMAGE
Open !BEGIN and choose option 1
IMAGE
Just follow the prompts and press ENTER when asked. When you get to screen below just wait till asked to press ENTER again. This might take a while.
IMAGE
When you arrive to this screen
IMAGE
your rom preparations are complete.Hit the ENTER to close window.
Go to Kitchen folder and you notice that rom files and packages are extracted.
IMAGE
To remove unwanted applications from rom look into OEM and SYS folders. You need to delete all folders related to paticular application. (create separate folder and move all packages there instead deleting. Later on you can convert them to .cab files and install them if needed)
IMAGE
If you have some cab files and would like to add them into the rom you will need THIS application. Just start it, make sure that Remodule option is deselected, open cab file and program will create new folder containig packagage file. Make shure that PACKAGE_Diamond_ is in front of the filename. For example if you converted TomTom cab you should rename it to PACKAGE_Diamond_TomTom. Now copy the folder to OEM folder in the kitchen. Repeat process till you add everything you would like to have in the ROM.
When you delete/add everything you want start !Cook file
IMAGE
This will start OS building application. Just hit a green button and wait till it finishes. It will create os-new.nb file needed later. Close window on top (never close a DOS window) and rom building application will start.
IMAGE
Fill all the info as shown on the screenshot.
IMAGE
Use apropriate version rom (ie FR, ME etc...). As for the system select os-new.nb which is in the kitchen folder. Also you can select boot images and radios but for now we leave as it is. When ready hit Build ROM button.
Name your new rom (anything you want).
IMAGE
And hit SAVE.
A while later you should see screen below
IMAGE
Hit OK. Wait till everything finishes. Just press ENTER when asked. On the end you get message that rom is ready to flash. Hitting ENTER closes a window. All you need to do is flash it to your device.
PS Everyone is welcome to help. I need information how to update Framework and OS and where I can download it. Please post suggestions, registry tweaks and links to updated cab files for the apps removed from the rom. I will make a video tutorial after I have all info needed. I want to make easy for everyone who wants to have personalized rom.
Credits: Thank you to all who provided these great tools and these that helped in this thread.
EDIT: If you manage to create your own ROM please do not flood forum with new ROMs (unless it is something we never seen). There are experienced cooks that created really nice ROMs. Lets keep this forums clean.
There is a thread in this forum which has a simple to use kitchen. Using it is just easy as Steps 1-2-3.. But it doesn't work for some ROMs, atleast for me. By far, it is a great tool simplified in batch files.
Are you using the same tool or your own customised one?
Regards,
Carty..
lolek74 said:
Hi all
I was looking for the way to cook my own ROM. There is a heaps of info for a Kiser but not a Diamond. I had decided to start a thread that will show and explain in plain language how to do it on the Diamond. The aim is to have perfectly clean ROM without any unwanted applications or tweaks. The ROM will only contain bare minimum to run PDA. Everything else can be installed with cab files. Also registry tweaks can be applied after installation.
What is more important I want this thread to be a simple to follow guide to cook a ROM so everyone can make one for themself. Since I’m not an expert I welcome any help from anyone.
I had managed to cook my 1st ROM. I had removed some applications without modifying anything else.
I'm off to bed now. I'll post screenshots and info tomorrow. Please register your interest.
Click to expand...
Click to collapse
Could do my... i just finished my one yesterday a perfect clean rom not staffed wth litter....i used the surface kitchen and based on ce 0s 5.2 20273 wwe a bit customized the manila that's all....
Is it a clean ROM with most apps removed? Do you want to share please.
Good initiative!
I really want to know what is the true performance of the Diamond, running it with just the minimum required.
Even when disabling TF3D and other extras, I find it so slow compared to other WM phones having less MHz... I just don't understand why.
Uploading my ROM now. It is slow. I will post the link tomorrow.
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
duttythroy said:
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
Click to expand...
Click to collapse
Really? Dutty, could you please explain that a little bit further? Don't we have a set amount of storage space? i.e. If you cook some apps in, then you lose some of that space. If you add them later, you lose some of that space. But at least you could uninstall them.
So please correct me if I have misunderstood and I'm only guessing, but are you saying there is a part of the ROM that is only available to the OS 'image', and cannot be accessed in the normal way once the device is up and running? And are you using that space to install some apps? If so, how much space in the 'OS image' part of the ROM is available for that purpose? I would like to start cooking my own ROM's, but I don't want to waste ANY storage space that I am not forced to.
I would really appreciate if you could shed a little light on that for me! Cheers
Thanks, this is great.
salada2k said:
Really? Dutty, could you please explain that a little bit further? Don't we have a set amount of storage space? i.e. If you cook some apps in, then you lose some of that space. If you add them later, you lose some of that space. But at least you could uninstall them.
So please correct me if I have misunderstood and I'm only guessing, but are you saying there is a part of the ROM that is only available to the OS 'image', and cannot be accessed in the normal way once the device is up and running? And are you using that space to install some apps? If so, how much space in the 'OS image' part of the ROM is available for that purpose? I would like to start cooking my own ROM's, but I don't want to waste ANY storage space that I am not forced to.
I would really appreciate if you could shed a little light on that for me! Cheers
Click to expand...
Click to collapse
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Perfect
I was hoping/loocking fopr a thread like this! BUT
Could anybody explaine to me how to dump a rom?
The one I am using right now is pretty good and I want to modify
it and loose all the unwanted programs...
But what happens to all the .cab programs I have installed at the moment?
Do they "get dumped" as well so I can preserve them as OEM? Or do I only dump the "base ROM"?
And what about the Reg tweaks? Do they get dumbed aswell?
Thanks for the help...
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
Thanks for the reply, so what is the reason behind that... How can that 1MB be shaved off? Is it compression?
duttythroy said:
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
And to top this, apps that are cooked run faster than an installed cab.
But for some, a ultra light rom works becouse they have not ,uch progs to use, and need to install less cabs.
gr.
Just a short notice, lolek:
I see you've extracted the kitchen to your profile folder.
You'd better extract it to the root of your drive, like C: or D:
batch files have a tendency to disliking spaces in file/folder names as well as names longer than 8+3.
surface_rom said:
And to top this, apps that are cooked run faster than an installed cab.
But for some, a ultra light rom works becouse they have not ,uch progs to use, and need to install less cabs.
gr.
Click to expand...
Click to collapse
exactly also if you look at some of the benchmarks as well the lite roms are not much better or even some of the full roms are faster, so its all about what u really need in the rom, if your going to install everything back in your rom with cabs, its better to go with a full rom
Thanks for the input. This is what I was hoping for. The aim is to have simple tutorial for anybody to create their own ROMs. I'm off to work tonight but I'll update 1st post tomorrow.
I have updated 1st post. It shows how to convert cab files to packages and add them to the rom. I apologize for the slow progress but I'm still learning myself.
I have asked around how to update framework and OS. As soon as I get reply and test it I’ll post it here.
I know there many experienced cooks so please don’t be shy and help create this guide.
When guide is complete I’ll make movie showing whole process.
lolek74 said:
I have updated 1st post. It shows how to convert cab files to packages and add them to the rom. I apologize for the slow progress but I'm still learning myself.
I have asked around how to update framework and OS. As soon as I get reply and test it I’ll post it here.
I know there many experienced cooks so please don’t be shy and help create this guide.
When guide is complete I’ll make movie showing whole process.
Click to expand...
Click to collapse
very nice man, keep it up!
this is very good idea to put together a tutorial to cook the ROM! cant wait to cook my own ROM with this.
thanks a lot man!
Having a Slight problem with the surface kitchen.
During the process of extracting a rom at the stage of '2a.ExtractDumpIMGFS.cmd'
'Recmod.exe' crashes.'
anyone know why and how i can solve this?
Thanks in advance

[Q]Replace/update OEM packages and other issues...

First of all I'm sorry for my english, hope you can understand me...
I'm going to cook my first ROM...
The idea is to make 2 versions (with/without manila) of a clean "uc capable" rom; what I want to do is take a 1.93 official base and update some oem app and sys (i.e. htc camera and netcf) and remove some others to replace theese with 3t part usefully app (i.e. putting in wktask manager instead htc task).
Now my doubts:
(I've readed a lot of wikies and thread but didn't find a CLEAR answer to all my questions)
1- If I use an official .exe rom as base I obiouvsly find inside it the radio part...have to remove this befor but in base folder due i don't need it for my work? How?
2- I'm able to remove oem pack from my rom base and I'm also able to repack new ones starting from a cab file...but I don't know if it's possible to take (exactly as they are) some oem pack from a stock/custom(when not protected) rom to use in mine...I saw that a lot of cookers use oem pack taken from raphael official roms to update thair roms and I would know if the process to do this is just open the rom, copy the oem and past it in mine... In this case...where can I find a good very update raphael rom?!
3- Opposite than this, for manila I would use the "animated switches" version. I want to downgrade it to the version with theese animations but I don't know if there's a particular process to replace this oem...can you tell me? PS: what is the exact manila version I need to do it?
4- TO UPDATE NETCF TO THE 3.5 VERSION WHAT HAVE I EXACTLY DO? And is the Alexandre's oem pack good for my pourpose?
Thank you a lot and sorry if (maybe) some questions were answered in other threads...I searched and readed a lot but there are too many informations in this forum for a noob/bad english speaker/... like me so I decided to ask!
GriFolle said:
First of all I'm sorry for my english, hope you can understand me...
I'm going to cook my first ROM...
The idea is to make 2 versions (with/without manila) of a clean "uc capable" rom; what I want to do is take a 1.93 official base and update some oem app and sys (i.e. htc camera and netcf) and remove some others to replace theese with 3t part usefully app (i.e. putting in wktask manager instead htc task).
Now my doubts:
(I've readed a lot of wikies and thread but didn't find a CLEAR answer to all my questions)
1- If I use an official .exe rom as base I obiouvsly find inside it the radio part...have to remove this befor but in base folder due i don't need it for my work? How?
2- I'm able to remove oem pack from my rom base and I'm also able to repack new ones starting from a cab file...but I don't know if it's possible to take (exactly as they are) some oem pack from a stock/custom(when not protected) rom to use in mine...I saw that a lot of cookers use oem pack taken from raphael official roms to update thair roms and I would know if the process to do this is just open the rom, copy the oem and past it in mine... In this case...where can I find a good very update raphael rom?!
3- Opposite than this, for manila I would use the "animated switches" version. I want to downgrade it to the version with theese animations but I don't know if there's a particular process to replace this oem...can you tell me? PS: what is the exact manila version I need to do it?
4- TO UPDATE NETCF TO THE 3.5 VERSION WHAT HAVE I EXACTLY DO? And is the Alexandre's oem pack good for my pourpose?
Thank you a lot and sorry if (maybe) some questions were answered in other threads...I searched and readed a lot but there are too many informations in this forum for a noob/bad english speaker/... like me so I decided to ask!
Click to expand...
Click to collapse
1. When dumping a ROM, it will dump separately the splashes, radio, os and extrom (if any.) Extract the exe with WinRAR and dump the nbh.
2. When dumping a ROM, it will create packages if ROM is unprotected. A good place of finding a Raph ROM would be the Raphael forums.
3. Delete the old package from kitchen and replace with new one (in your case, the old one, animated).
4. You can find ready made NetCF 3.5 packages. You should delete the old NetCF 2 from SYS folder and replace it with the 3.5
tnyynt said:
1. When dumping a ROM, it will dump separately the splashes, radio, os and extrom (if any.) Extract the exe with WinRAR and dump the nbh.
2. When dumping a ROM, it will create packages if ROM is unprotected. A good place of finding a Raph ROM would be the Raphael forums.
3. Delete the old package from kitchen and replace with new one (in your case, the old one, animated).
4. You can find ready made NetCF 3.5 packages. You should delete the old NetCF 2 from SYS folder and replace it with the 3.5
Click to expand...
Click to collapse
Thanks a lot!
So, to replace OEM, just put out (from a rom) and put in (in mine)...so simple?!
Ahahah...
Please, excuse me for my stupidity...BUT I REALLY NEED AN HELP!!!
(I'm following this guide: http://forum.xda-developers.com/showthread.php?t=413782&highlight=kitchen)
Here's what I do:
1) I've downloaded from htc site the last official stock rom (localized for my country) \HTC Touch Diamond\QMR\RUU_Diamond_HTC_ITA_1.93.408.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
2) I've extracted all files and putted them into Base ROM folder of surface kitchen.
3) clicked on begin and obtained some folders in the kitchwen one
Now if I go into one package folders in OEM (htc gesture in example) i can't see dsm or rgu files, but just dll and .provxml ones...WHY?! I don't think it's good, right? Where is my fault?!
SO SAD...
PS: I've searched a lot but I've not found a netcf prepared package to cook...
Thanks a lot!
GriFolle said:
Please, excuse me for my stupidity...BUT I REALLY NEED AN HELP!!!
(I'm following this guide: http://forum.xda-developers.com/showthread.php?t=413782&highlight=kitchen)
Here's what I do:
1) I've downloaded from htc site the last official stock rom (localized for my country) \HTC Touch Diamond\QMR\RUU_Diamond_HTC_ITA_1.93.408.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
2) I've extracted all files and putted them into Base ROM folder of surface kitchen.
3) clicked on begin and obtained some folders in the kitchwen one
Now if I go into one package folders in OEM (htc gesture in example) i can't see dsm or rgu files, but just dll and .provxml ones...WHY?! I don't think it's good, right? Where is my fault?!
SO SAD...
PS: I've searched a lot but I've not found a netcf prepared package to cook...
Thanks a lot!
Click to expand...
Click to collapse
You have to create the packages!
Don't know the kitchen but it should be like this in every kitchen.
Also, you can check inside provxml file (notepad will do), maybe the rgu (registry entries) are set through provisioning.
tnyynt said:
You have to create the packages!
Don't know the kitchen but it should be like this in every kitchen.
Also, you can check inside provxml file (notepad will do), maybe the rgu (registry entries) are set through provisioning.
Click to expand...
Click to collapse
confused...
I think I have to create just the packages of apps I would to add...not even all the apps contained in the stock rom!
Looking and reading tutorials in this forum I understood that If I would (i.e.) add/rmv apps to my rom I've just to put its files in base rom and then (after extract all) add/remove what I want. Then rebuild.
But for all others teorically I don't do anything...Is this wrong?
PS: thank you for the previous reply

ROM cooking: smthing else than initflashfiles affects shortcuts

Hi, everyone! I´m still working on a Wizard (don´t want to touch my Hermes, yet). I´m pretty advanced... but
I dump the [latest] original cingular WM5. I rebuilt it with office 2007 and realize that the original shortcuts are still there. Of course, they are both useless (as I have new names for the apps) and annoying (because I can´t remove them before compiling).
This is the whole point: Those shortcuts are not coming from neither an xml update for the XIP nor an initflashfiles.txt
HOW ON EARTH DO I REMOVE THEM. I can´t find what is creating and copying those shortcuts
Are they embedded in the OS.nb file? If so, how do I take that file apart?
Any help is very much appreciated!
..provxml, m8..
Nope, had checked already
*.mopvxml, etc had been checked.
But... what did you mean by m8?.
BTW: I will check inside os.nb now, but please give me fresh ideas
You may also want to check for a file called initflashfiles.dat. That contains a lot of shortcut information as well. Especially for apps that are default for that particular ROM. It should be found in the OEM\OEM_LANG_* folder in the kitchen. The (*) is the locale number. For example, a WWE ROM would have the folder as OEM_LANG_0409.
Yep, solved (initflashfiles.dat)
Hey, thanks! You´re FAST!
I was about to post it. But thanks, you could have saved me hours
Anyways. If anyone ever reads this thread, remember: scavenging os.nb(a) isn´t that great. An automated kitchen does it all (Hypercore in this case).
I also found somebody claiming that certain shortcut came from a dll. Just keep as a sidenote.
Cheers!

Categories

Resources