HOW To Make an OEM
Here is the tutorial for building an OEM, so, of course it can be used for any device,.
nb: try it at your own risk,.
OEM folder used as the place for any application that would be a default ROM application.
Here is step by step,.
1. Download & Install Hypercore Kitchen
2. Open Hypercore and go to panel/extra/CAB Analiser,.
3. Open or Drag and drop the .cab files that you would make it an OEM,.
4. Choose "XML" display then extract all cab files to a new folder,.
5. Go to "Registry tab", then copy all the registry setting from there, and paste to a new blank document
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6. The registry setting is absolutely unusable, to make it usable, it must be edited like this,.
(Before edited)
REGEDIT4
[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\WM5torage_Class]
"ActivateFlags" = dword : 00000000
"DeviceName" = ""
"NLEDWrite" = dword : 0000FFFF
"NLEDRead" = dword : 0000FFFF
"idVendor" = dword : 0000045E ---------------------------------------> There is a space between "=" and "dword", its Wrong,.
"ReadOnly" = dword : 00000000
"Dll" = %CE1%\WM5torage\WM5torage.dll --------------------------> It have only one slices, its wrong,.
"Product" = "Windows Mobile Device"
(After edited)
REGEDIT4 -------------------------------------------------------------------> There must be REGEDIT4 at the TOP
[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\WM5torage_Class]
"ActivateFlags"=dword:00000000
"DeviceName"=""
"NLEDWrite"=dword:0000FFFF
"NLEDRead"=dword:0000FFFF
"idVendor"=dword:0000045E ------------------------------------------> Take a look at this, there should be no spacing inside the registry,.
"ReadOnly"=dword:00000000
"Dll"=%CE1%\\WM5torage\\WM5torage.dll -------------------------> If the keys are pointing to somewhere else, it must be two slice like this,.
"Product"="Windows Mobile Device"
--------------------------------------------------------------------------------> Leave one line empty at the BOTTOM,.
7. Generate GUID Name, (The generaor could be downloaded HERE)
8. Okay, save it in UNICODE encoding, using (Generated GUID Name).rgu
9. Make another blank document, and rename it with, (Generated GUID Name).dsm
(The generated GUID name between .rgu and .dsm must be the same)
10. Make a "initflashfiles.txt",. -------> (I give the tutorial below,.)
HOW To Make a initflashfiles.txt
initflashfiles.txt used to copy a file from specified location, to another specified location,.
Here is the step by step,.
1. Just make a new blank document
2. Save that document as initflashfiles.txt
What should you write inside initflashfiles.txt?? you should write this (below),.
The formula is:
Directory("DESTINATION FOLDER"):-File("DESIRED FILENAME","FILE SOURCE")
So, it will be like this,.
-------> Means that you want to copy the file named WM5torage.lnk in \Windows folder, to \Windows\Start Menu\Programs\System folder,.
There you go, you have one working initflashfiles.txt now,.
--- Finally, make it in one folder, and give it a name, ex: OEM_WM5torage ---
NB:
That you have to remember when you build an OEM:
a. There must be REGEDIT4 at the TOP
b. Leave one line empty at the BOTTOM
c. Dont use Wordwrap view
d. Save with (GUIDname).rgu and use UNICODE encoding
GOOD LUCK,.
Happy ROM Cooking to all of you,.
- Kumara -
I dnt know why the pictures are not showing??!!
I think this is the problem !!
When u want to put a pic , press on *insert image* and put a direct link
not IMG code or HTML code
ghostrecon2050 said:
I dnt know why the pictures are not showing??!!
I think this is the problem !!
When u want to put a pic , press on *insert image* and put a direct link
not IMG code or HTML code
Click to expand...
Click to collapse
Hi buddy, i put this picture from a direct link, it might be your internet explorer setting,.
But serialz got the same problem but in the Atom Cooking tutorial thread :
he said : "please update the pics too..it's much easy to do it with visual guide.."
May be it's our IE settings ?? I'm confused !!
ghostrecon2050 said:
But serialz got the same problem but in the Atom Cooking tutorial thread :
he said : "please update the pics too..it's much easy to do it with visual guide.."
May be it's our IE settings ?? I'm confused !!
Click to expand...
Click to collapse
Image updated, could you see the picture now??
Link Megaupload please!
Thanks
mykolor said:
Link Megaupload please!
Thanks
Click to expand...
Click to collapse
What do tou mean by link megaupload?????
BTW, could you see the picture of my post??
Garmin said:
What do tou mean by link megaupload?????
BTW, could you see the picture of my post??
Click to expand...
Click to collapse
All the picture #1 page is not showing.
I want to download your ROM by link Megaupload
Yes , Now I can see the pictures , TY Garmin <3
Hi Garmin,
Thank you for the tutorial to make OEM. wonderful!
Your tutorial is good for standalone .exe files
but if you don't mind if i ask about cabs?
I have a question about cabs files:
how to input serial number into the cabs registry for programs Cabs that has serial activation? so everytime i install it.. it doesn't need to enter serial?
for example: i need to put "modified cabs" to extended rom. so it will install by itself every time i do hard reset.
Thank you garmin.
sliders7 said:
Hi Garmin,
Thank you for the tutorial to make OEM. wonderful!
Your tutorial is good for standalone .exe files
but if you don't mind if i ask about cabs?
I have a question about cabs files:
how to input serial number into the cabs registry for programs Cabs that has serial activation? so everytime i install it.. it doesn't need to enter serial?
for example: i need to put "modified cabs" to extended rom. so it will install by itself every time i do hard reset.
Thank you garmin.
Click to expand...
Click to collapse
Every apps is different. So if don't know where a reg patch (sn. insert in registry), that's unable to create registry
Yup agreed with abusalza, every apps is different and they store their serial and reg key differently. i found some at the registry, and some on the file folder itself, some even encode them in the registry.
For me i key in the serial and search for it in the registry, den backup the key, and create cab for the registration and placing of ringtones and placing of shortcuts (for appz and games that installed on storage)
This ways saved me many hours when i will tryin to cook my own ROM or tryin out new appz
Just wanna thank Garmin for creating this thread and really helped me alot!!
thank very much bro!!!
ckaidi said:
Yup agreed with abusalza, every apps is different and they store their serial and reg key differently. i found some at the registry, and some on the file folder itself, some even encode them in the registry.
For me i key in the serial and search for it in the registry, den backup the key, and create cab for the registration and placing of ringtones and placing of shortcuts (for appz and games that installed on storage)
This ways saved me many hours when i will tryin to cook my own ROM or tryin out new appz
Click to expand...
Click to collapse
Backing up the key is one beautiful idea!
Thanks for the help!
sliders7 said:
Backing up the key is one beautiful idea!
Thanks for the help!
Click to expand...
Click to collapse
Try Settings Saviour. I haven't tried though, but it is supposed to that what you need.
@Garmin: good job!
ckaidi said:
Just wanna thank Garmin for creating this thread and really helped me alot!!
thank very much bro!!!
Click to expand...
Click to collapse
Thanks Bud,.
BTW, Sorry for not in the forum so often,.
My computer has just attacked by many variant of virusses, and it started with one of the thread here,.
Becarefull guys,. someone try to distributing a SPAM in this forum,.
Take care,.
Some appz and gamez include a setup.dll in the cab which insert reg values. Anyone know how to decode it? This will really help in building OEM
Thanks!!
ckaidi said:
Some appz and gamez include a setup.dll in the cab which insert reg values. Anyone know how to decode it? This will really help in building OEM
Thanks!!
Click to expand...
Click to collapse
hi ck..
try using ResHacker (google it),.
or try reverse mode (search it in the forum),.
gud luck,.
wrong post, sorry
HI!
when I want to copy registry values from Cabs Analyzer there is no values...
It is S2U2 Cab, and some others too...but when i opend HTC keyboard cab registry values are shown
Related
The use of the Rom Kitchen is at your own risk!
Note: This is NOT for beginners, you need to have a good understanding of flashing G3/G4 prophets
This is NOT for answering or asking basic info, use the wiki/search for that.
Rom Kitchen Installation:
Download and install MS .NET framework 2 first
Extract the file ‘Prophet_WM6_RK_S-Core.rar’ anywhere.
The Folder structure will look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract ‘FlashOS.zip’ and ‘rgu-hv.zip’ anywhere.
Using the Rom Kitchen in Steps:
STEP (0): Making an OEM Package:(optional, more later)
This step is not necessary at beginning, unless you want to include new OEM Package in the OEM dir of Kitchen.
STEP(1): Run BuildOS.exe:
it will look like this:
Here you can select / de-select any packages you require.
Make sure you don't select too many or it will overflow the rom and you will get any error in the CreateRom.bat step.
Click the green button when you are done and it will create the OS dump.
If you get errors during this, it is probably due to duplicate files/modules in SYS and OEM dirs or due to bad registry entries.
If they occur, it has to be fixed by deleting duplicate files/modules (make sure you know what you are deleting) and correcting the registry (its hard to track registry errors, only change one package at a time).
If there are no errors BuildOS.exe will finish and prompt ‘Done’.
The temp dir will have dump,boot.hv,boot.rgu and log.txt
Do not delete any content at this point.
STEP(2) (a): Editing default/User .hv files:
This can be skipped, but all depends upon need.
This is needed for example when you need to ‘remove’ some reg entries.
For example see:
The base rom used in this kitchen is from the wizard, so we probably need this type of removal again.
To do it , copy default.hv and user.hv( user may not need both) files from dump created above to rgu-hv folder.
Run respective batch file to convert them in *.rgu files and rename *.rgu files to *.txt
edit *.txt files in notepad.
Remember these points:
--------(i)Turn off Word Wrap in notepad
--------(ii)1st line is blank line, type “REGEDIT4”(without quotes)on this line
--------(iii)Make sure last line is blank line
--------(iv)Files should be saved as Unicode not ANSI after editing
--------(v)HKCR & HKLM falls in default.rgu
--------(vi)HKCU and HKU falls in user.rgu
When saving *.txt files in notepad,
--------Select Encoding as Unicode
--------Select file type ‘all’
--------Rename as *.rgu
Now run respective batch file to convert *.rgu file back to *.hv files. Original *.hv files present in rgu-hv dir will be replaced by newly edited *.hv files.
Move new *.hv files back to dump folder in temp dir.
STEP(2) (b): Editing main initflashfiles.dat, why ? (Coming soon)
STEP(3): Run CreateRom.bat:
This batch file uses the dump dir., boot.hv and boot.rgu files to create the OS.nb file.
If there are no errors, the newly created OS.nb is placed in the temp dir.
STEP(4): Flashing the OS:
- Downgrade to AKU 2.2 first (wm5)
- Move your new OS.nb from the temp dir to the FlashOS dir and run UpgradeRom.bat
Screenshots:
Downloads:
PROPHET_WM6_RK_S-CORE
View attachment FlashOS.zip
View attachment rgu-hv.zip
View attachment Guide.zip
Updates:
#1 - 10/06/2007 Reduce imgfs size and put in more OEM/Files
(1)View attachment TOOLS+CreateROM.zip
Extract Zip and replace TOOLS dir and CreateROM.bat with old one in RK.
Modified File/TOOLS are optional, one can continue to work with old ones.
Info on Update #1
- Modified File/Tools repack imgfs block and hence OS.nb to reduced size!!
- Standard size of Shiped OS/Old cutom cook OS is 58368 KB(59,768,832 Byte)
- With the modified File/Tools new OS.nb can be less then 50 MB!!
- Hence its possible to include more OEM Packs and files untill the limit of 58368 KB
- Less imgfs blocks will not increase Storage.
- If OEM Packs/Files are deleted, initflashfile.dat must be edited, if not it will not boot properly
- Flashing reduced size OS.nb with FlashOS, may not prompt completion, so one has to wait as long as to approx 30 min or above to make it complete in hidden mode.
- If you add too many OEM/Files to the OS.nb greater than standard size without any error, but avoid such OS and dont risk ur device by flashing over size OS.nb
- experience with reduced size OS.nb - device switches off frequently after waking up, no other issue found yet.
Credits:
Mamaich,bepe and faria for base framework
Anichillus for base rom Core 2.n
Double_ofour for linux support
Zeusin/Smart1 for explaning ModelID
itsme and Tadzio for his tools
funman for the manual
And many others.........
Hi Nandlal,
Finally after a long wait... Am downloading it now, and will try it out asap. it looks grt and easy to use from what i can see. Thanks a lot for this, and hopefully we will have more custom stable roms coming out based on this RK
PS: SMART1 helped in figuring out the model ID.....so thanks to him
dmc3 said:
can this be use with smart1's???
Click to expand...
Click to collapse
its complete kitchen, u dont need any other rom to use with.
Kitchen uses anichillus's Core 2.n as base rom.
If u just use kitchen with all steps u will get a rom which looks as in post.
P4k1t0 said:
i forget to install it... i have formated my pc 2days ago
xD
Thankx for this pack nandlal_mk
It was good if it was more options to cook our proprly rom
Click to expand...
Click to collapse
Im still on improvement work, especially option to choose Language Packs via OEM packahe and more on registry changes, but the limitation is of time. I have free access to my PC only in night for 2Hrs
I answered my question by myself: it's explained in the PDF-File!
But I got another question:
Can I switch the Core-ROM? I'm customizing at the moment PDAViet 4.0.0.0.3 but I think it's not all to replace the OS.nb inside the Kitchen! Explain it please!
animelover said:
I answered my question by myself: it's explained in the PDF-File!
But I got another question:
Can I switch the Core-ROM? I'm customizing at the moment PDAViet 4.0.0.0.3 but I think it's not all to replace the OS.nb inside the Kitchen! Explain it please!
Click to expand...
Click to collapse
Hi animelover,
Nice to see u.
I have been out for some work and will complete remaining tutorial on first page.
Well, choice for Core rom just arises cuz i liked its speed and performence even when there is not much registry changes, i changed very little few reg to work with prophet, as it was consuming time of my work hour.
And its absolutely possible to port any custem rom to kitchen, that was my search which ends in a shape of this kitchen.
But as i stated in 1st post we should have a official WM6 for prophet then only the kitchen based on that will be perfect.
There is some inbuilt behaviour of BuildOS.exe, that it does not construct registry based on custom rom that has been ported to kitchen, rather it construct registry from deployed SYS/OEM structure.
Thats why when a custom rom ( say Smart1 v3 or any) ported in kitchen vanishes its customized registries on running BuildOS.exe, and newly created rom will have totally different registries than original one.
However original registries of custom rom r placed in SYS/Metadata but they r ignored during BuildOS.exe (Mods, please correct my findings if im wrong)
If there is a better chioce for a rom that should be ported, please mention, that will be ported in RK, but u know what i wrote above.
One has to make registry changes after BuildOS.exe to make rom more performative.
it looks promising,
when will tut on post#5 complete ?
Reduce imgfs size and put more OEM/Files
Extract Zip and replace TOOLS dir and CreateROM.bat with old one in RK.
Modified File/TOOLS are optional, one can continue to work with old ones.
Benefits & Facts of Enhancement #(1)
.....(1) Modified File/Tools repack imgfs block and hence OS.nb to reduced size!!
....(2) Standard size of Shiped OS/Old cutom cook OS is 58368 KB(59,768,832 Byte)
....(3)With modified File/Tools new OS.nb can be as less to 50 MB!!
....(4)Hence its possible to include more OEM Packs and files untill the limit of 58368 KB
....(5)Decrease in imgfs block does not grow Storage on flashed device.
....(6)If OEM Packs/Files r deleted, initflashfile.dat must be edited, if not then device could not be booted properly
....(7)Flashing reduced size OS.nb with FlashOS, may not prompt completion, so one has to wait as long as to approx 30 min or above to make it complete in hidden mode.
....(8)If too many OEM/Files included than these tools make OS.nb greater than standard size without any error, but avoid such OS and dont risk ur device by flashing over size OS.nb
....(9)My 2 days experience with reduce size OS.nb--- device switches off frequently after waking up, no other issue found yet.
Brakelseboer said:
This ROM is great. Beautifull bootscreen and finally sound for every tap, even the Start Menu.
One Problem:
When I change the backlight setting (everything off) and I switch off and on my device the backlight is gone. The only solution is to hard reset my device and set it up again. Is there a solution for?
Click to expand...
Click to collapse
there is no such problem on my device, but its possible different devices shows little variation in performence.
try using without backlight off setting or power offsetting for some time, i think it may help or remake-reflash in freash way.
im still on enhancement work, but with slow pace. However there is not much to change as base rom provided by anichillus is already superb.
But still i will post some more enhancement before reviving whole kitchen with any new good base rom.
Thread move to WM6 section, will update and clean later
Good work nandlal_mk
thanx for sticky
Jesterz said:
Thread move to WM6 section, will update and clean later
Good work nandlal_mk
Click to expand...
Click to collapse
Thanx Jesterz.
Its nice to see you again after a long time ( last activity 20-3-07 , i was eying/waiting to change it), really missing u all prophet forum user.
I need ur assistence, may i PM u later?
nandlal_mk said:
Thanx Jesterz.
Its nice to see you again after a long time ( last activity 20-3-07 , i was eying/waiting to change it), really missing u all prophet forum user.
I need ur assistence, may i PM u later?
Click to expand...
Click to collapse
Thanks ! and sure, give me a PM whenever
C ya
2 questions...
1. can i use this tool to cook ipaq rom?
2. if the pda has no phone function, how can i remove the phone module?
sorry i am newbie, pls bear with me if i asked silly questions
Anyone have the problem on the status battary?
nandlal_mk said:
Im still on improvement work, especially option to choose Language Packs via OEM packahe and more on registry changes, but the limitation is of time. I have free access to my PC only in night for 2Hrs
Click to expand...
Click to collapse
Please let me know if you need help for multiple lingual packs as I know japanese, korean and chinese. I still have the problem of doing a korean/japanese language rom. Tks!
Is there a way to convert OEM Packages into cabfiles that I can install like any other program?
OEM to cab
Infestor said:
Is there a way to convert OEM Packages into cabfiles that I can install like any other program?
Click to expand...
Click to collapse
I use this program for making cab files
Installation Creator
It's got everything you need
Just place the files in the right folder and edit the registry and go to build and your done
new core rom
I realy like to get a new core rom the one inside this kitchen is buging me.. as is restarts the prophet rapidly
Thanks gullum!
I only have some remaining questions:
First, is it correct, that the registry entries from the OEM-package are in the *strange-hex-code*.rgu? Do I need to enter this code anywhere? Is there a way to import this file directly into the Installation Creator or do I have to add the settings manually by editing the registry sections?
Second, how can I find out if there are any self registering or setup dll files that I have to specify during the setup process?
Sorry to bother you, if there is a thread or tutorial where this has been discussed before, just tell me which one it is.
I just downloaded the OEM.zip from the Wizard Forum and want to try some of the programs out.
Thanks again for your help!
PS: And yes, I have the same problems with the core here...my Prophet restarts every 10 inutes or so .
Help me
gullum; said:
I use this program for making cab files
Installation Creator
It's got everything you need
Just place the files in the right folder and edit the registry and go to build and your done[/QUOTE
Bro, thanks for the link but i dont really understand how to create cab file using this intallation creator tool but eager to try. I'm quite blur. Can you help me on this?
Click to expand...
Click to collapse
ATOM WM 6 AND WM 6.1 ROM COOKING TUTORIAL
nb: try it at your own risk,.
WHAT DO YOU NEED?
- Hypercore Kitchen
- Garmin XDA ATOM ROM Cooking Sets (UPDATED 14/03/08)
ADD-ON
- WM 6.1 SYS files
Usage Of Hypercore Kitchen
- Creates OEM and anything related to OEM
Usage of ATOM WM6 Kitchen
- Dump your diskimage_ver.nb0
- Build your new diskimage_ver.nb0
Already have it all?? Alright, now lets start working,.
1. Extract "Garmin XDA ATOM Cooking Sets" to somewhere you like, (There will be an original OEM and SYS folder, don't erase those, it required for dumping process,.)
2. Put your diskimage_ver.nb0 into ROM folder, (overwrite the original file there,.)
3. Run "DumpFiles.cmd" , (Then you'll see a working progress, until it ask you to press any key) ---- press any key then,.
4. There will be a new window come named "Package Tool", then Open where the "dump" folder is located, (The package tool help you build your OEM and DSM,.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Go to \Tools\Build Package, you will not see a working progress, when the content of the Package tool was changed, ITS DONE!!, and your diskimage_Ver.nb0 was dumped,.
(The original OEM and SYS folder will be gone,.)
--- Now go to "dump" folder and you'll see OEM and SYS folder ---
nb : If there are some files outside OEM / SYS folder, put it where it should by reading the last line of your package tool, after building a package,.
----------> means that these file should be in \SYS\NetCF folder,.
OKAY, take a rest first, have some experience with that OEM and SYS folder,.
You may change, add or remove some folder there, but BECAREFUL, some of them are SYSTEM file!!!
Satisfied experience with OEM and SYS folder?? Lets Continue,.
6. Now move your OEM and SYS folder (inside "dump" folder), to the first page (Where the original OEM and SYS is located)
7. Run "BuildOS.cmd" (You will see a new window "BulidOS",.) press the green button,.
8. When done, (you could see on the bottom left corner, written "Done"), close the BuildOS by pressing the [X] Button, (dont close the BuildOS.cmd)
9. You will see in the BuildOS.cmd, a progress, wait till it ask you to press any key,. ----- Press any key then,.
10. There you are, your new diskimage_Ver.nb0 is inside "FLASH" folder,.
Nb: For a tutorial about building an OEM, could be seen HERE, and How To Port XIP and SYS folder, could be seen HERE,.
nb: For WM 6.1 Cooking, you couldn't DUMP your ROM, because it removes all manifest to be one,.
GOOD LUCK,.
Happy ROM Cooking to all of you,.
- Kumara -
STICKY IT!!
udayrulz said:
STICKY IT!!
Click to expand...
Click to collapse
Thanks mate,.
the problem is where you get "your diskimage_ver.nb0" ?????? you will have to use an "already built" diskimage_ver.nb0 (like jiggs') and modify his rom, you can not create your own rom with another build like 5.2.1933 or else, I was trying to make a new rom from a new build but I wasn't successfull. Jiggs told me to read the wiki, but maybe I didn't do my homework so well.
medkid said:
the problem is where you get "your diskimage_ver.nb0" ?????? you will have to use an "already built" diskimage_ver.nb0 (like jiggs') and modify his rom, you can not create your own rom with another build like 5.2.1933 or else, I was trying to make a new rom from a new build but I wasn't successfull. Jiggs told me to read the wiki, but maybe I didn't do my homework so well.
Click to expand...
Click to collapse
It shouldn't be any problem mate,.
You could use any diskimage_ver.nb0 to dump,.
look at my new ROM (O2 Atom WM6 Premium), it was dumped from jiggs WM6 AKU 0.7a,.
Just use mine mate, (from O2 Atom WM6 Premium), its dumpable,.
@Ckaidi
Exactly , although i have no way near the knowledge required to make 1 but ...i just did a quick background check on you and figured out that you hv been cooking for a while now....so yea i understand wat you lookin at..
This is really different from what we used to cook for xda 2. How I wish cooking for an atom is as easy as cooking for an xda 2.
Anyway, good luck to all who would like to attempt cooking their own ROM. I'll just look at those available in here and copy those that I think will fit me best.
BTW, I hope somebody can teach me how to change the splash images. I would like to replace them with pictures of my family.
^welcomehead.96.png = splash image..
found in SYS folder..
Garmin said:
It shouldn't be any problem mate,.
You could use any diskimage_ver.nb0 to dump,.
look at my new ROM (O2 Atom WM6 Premium), it was dumped from jiggs WM6 AKU 0.7a,.
Just use mine mate, (from O2 Atom WM6 Premium), its dumpable,.
Click to expand...
Click to collapse
I know it,I know that your diskimage_ver.nb0 is dumpable (don't you see the rom I built pReDrT ?)
what I want to say is , you can not build your own diskimage_ver.nb0 based on a new build (for example 5.2.1933, the newest build), what you do is dumping a built diskimage_ver.nb0 from jiggs (the original one) which's build is 5.2.1908, don't you see that ???????
To build a new rom with a new build, it costs an arm and a leg, so much time spends on it. It's not easy as you said,but I really appreciate what you share here.
bro,
where's the part of the dump do i go to add new appz or new files?
the guide is just like extracting and compressing thing but how we add something?
where's the folder structure of \windows , \program files , etc..?
please update the pics too..it's much easy to do it with visual guide..
guide us please..
thanks a lot..
-=[serialzs]=-
You have to add them in OEM folder mate...
udayrulz said:
You have to add them in OEM folder mate...
Click to expand...
Click to collapse
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-
serialzs said:
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-
Click to expand...
Click to collapse
Yes , the files go to windows directory automatically
First download Ervius Packages Creator..
..say you want to include TCPMP in your ROM , You first need to Unzip all the files that TCPMP installs to a folder ..now open Ervius Packages Creator..navigate to folder .add a shortcut (option in the packages software..)
and click create package..now copy the folder to the OEM folder and build ROM..
Hope you get the idea..
yes i get the idea..what if i want to install it in program files folder? what should i do?
sorry for making ask again..i want to know it so that i can help you guys too..
thanks a lot..
-=[serialzs]=-
I dont know that ....sorry...
You can obviously create Custom Cabs and run put em in extended ROM for installing in program files..
You can search for OEM packages on the site.. u ll find plenty...
I am still learning so do pass on the knowledge..
Going a bit OT - Are you the one who made the DSU installed for ROM installation??
serialzs said:
yes i get the idea..what if i want to install it in program files folder? what should i do?
sorry for making ask again..i want to know it so that i can help you guys too..
thanks a lot..
-=[serialzs]=-
Click to expand...
Click to collapse
you will specify it in initflashfiles.dat, but you will have a double copy. The purpose of putting it to ROM is to have all the applications you need and consume less persistent storage vis-a-vis installing the cabs after a hardreset. However, having too many files in \windows will cause your system to lag; so, this is the purpose of utilizing the extended ROM wherein the skin files (like wireless manager / htc home / mediaplus) can be placed in the extended ROM and the program files in \windows.
serialzs said:
bro,
where's the part of the dump do i go to add new appz or new files?
the guide is just like extracting and compressing thing but how we add something?
where's the folder structure of \windows , \program files , etc..?
please update the pics too..it's much easy to do it with visual guide..
guide us please..
thanks a lot..
-=[serialzs]=-
Click to expand...
Click to collapse
To add a new appz, you have to make your appz (appz that you would like to have as a default appz) as an OEM,.
How do we make an OEM? i am working on it, i'll post it here soon,.
all the files there (inside SYS and OEM folder) will go to windows directory, then if you would like to move something to program files directory, you have to make an "initflashfiles.txt",. (usually for your OEM)
for example,
Directory("\Windows\StartUp"):-File("coldinit.lnk","\Windows\coldinit.lnk")
----- > it means that you copy file "coldinit.lnk" to \windows\startup folder,.
hope that help you,.
serialzs said:
and where do it go in our unit if we update???
can you be more detailed? is there a \windows and \programfiles folder in OEM folder?
thanks..
-=[serialzs]=-
Click to expand...
Click to collapse
It wont go anywhere, as long as we dont make a "initflashfiles.txt" for our apps (that have been changed to OEM), the shorcut of the apps wont go anywhere, it still in windows folder, (so, it wont be displayed in the main menu)
medkid said:
I know it,I know that your diskimage_ver.nb0 is dumpable (don't you see the rom I built pReDrT ?)
what I want to say is , you can not build your own diskimage_ver.nb0 based on a new build (for example 5.2.1933, the newest build), what you do is dumping a built diskimage_ver.nb0 from jiggs (the original one) which's build is 5.2.1908, don't you see that ???????
To build a new rom with a new build, it costs an arm and a leg, so much time spends on it. It's not easy as you said,but I really appreciate what you share here.
Click to expand...
Click to collapse
Ow i see,. sorry missunderstanding,.
Yep, absolutely you could, i am working a new ROM with upgrade of XIP to 5.2.1933 at the moment, if it success, i'll update the thread,.
but it havent finished, so the thread just till extracting and repacking,.
Gud luck,.
You are boring with default Boot Screen on Your Atom/ Atom Exec, and want to changes it with your favourite images. Read this instructions:
1. Download tools from HERE
2. Extract rar files in one folder with rom file diskimage_Ver.nb0
3. Install Hex Workshop 4.2 (hw32v423.exe) on your PC, or u can using another hex editor. But i'm personaly like this software.
4. Typed command RomMaster.exe diskimage_ver.nb0 -w 5 -b 0x0018000c -x -o xip.bin. It's will generated xip.bin for you
3. Run xipport, choose dump xip.bin and write maps. Close xipport
4. Prepare your own image with size 240x320, flip and rotate it 180 degrees. It's will look like screenshot. Save as bmp, file size must be 230.454 bytes. If u have Corel Paint Shop Pro Photo X2, it will save with this size automatically.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Run Hex Workshop 4.2 and open your own image, block all or select all than copy. Don't close Hex program
6. Open S000 from nk.exe region on your dumped xip folder with Hex Workshop. ctrl+F On your keyboard and on pop up windows choose text string, on value typed bm6, and ok. Select Edit on top left and choose Select Block. On pop up windows set block to 230454, Dec for decimal, and on method choose size of block. Paste in black area, than save. Select yes if program ask to make backup of S000 and move backup file to another location (for sometimes u want restore your boot screen). See at screenshot
7. Run xipport, realloc P, write maps than build xip_out.bin, specify address 0018000c for diskimage_ver.nb0 than click write xip_out.bin
8. Flash your new rom to device
ps: Follow this step to changes Hard Reset Screen on S003 from nk.exe region
Weel done, i hope this thread will help u
Regards,
Add download links for tools
This is possible to changes splash screen without flashing?
great job!!! this should be pinned!!!!
sticky it!!
brian_2cool4u said:
great job!!! this should be pinned!!!!
sticky it!!
Click to expand...
Click to collapse
Yeah, i second that!
Sticky it..!!!
aank said:
This is possible to changes splash screen without flashing?
Click to expand...
Click to collapse
I think that's impossible for now! maybe later if anyone make a program to changes "ROM FILES" on active device
abusalza said:
I think that's impossible for now! maybe later if anyone make a program to changes "ROM FILES" on active device
Click to expand...
Click to collapse
Nevermind,
i'll try to make one...
Thank You.
Thank You for your rom.
I will create from your sample and I found nice image.
Happy every time for you.
http://www.zune-wallpapers.com/a/all_recommended,2.html
Loedsiriya said:
Thank You for your rom.
I will create from your sample and I found nice image.
Happy every time for you.
http://www.zune-wallpapers.com/a/all_recommended,2.html
Click to expand...
Click to collapse
woaa... it's all so expresive. thnx, bro
anyway this threads sould be sticky, please mods
Other way, Direct modify.
I search by "first boot screen" and found someting from old post by someone.
this details.
I select modify at diskimage_Ver.nb0 file. It's easy modifying.
1.1st boot screen is black dragon on gold ray.
2. 2nd boot screen is BootScr.bmp. ====[black dragon on gold ray]
It's can use resco exploror replace after boot complete.
3.3th screen is show long time as 1st screen.
I use HitMan in Black color wallpaper. 3th file is welcomehead.96.png.
It's can use resco exploror replace after boot complete.
for 2nd and 3th image in \Windows and not flip
1st must flip vertical.
Please backup diskimage_Ver.nb0 before modify you boot screen.
When you find it by name. Your must found in the world. If have name.
=========================================
okay fellas, time to learn how to change the 1st bootscreen on your atom.
1. prepare your 1st boot screen 240 X 320 in bmp format
2. flip vertical (Must!!) and save it. file size is 230,454 bytes
3. Open your bmp file with Hex Editor (e.g. XVI32)
now you can change your 1st bootscreen either in nk.exe (inside xip during cooking) or on the diskimage_Ver.nb0
================================================== ===
on ATOM/ATOM Pure
xip mode.
1. goto nk.exe, open S000 file with hex editor.
2. the existing 1st bootscreen bmp file from address 3CD0 to 3C103
3. you may replace it with your bmp (cut & paste to that range address)
diskimage_Ver.nb0
1. open diskimage_Ver.nb0 file with hex editor.
2. the existing 1st bootscreen bmp file from address 184CDC to 1BD111
3. you may replace it with your bmp (cut & paste to that range address)
================================================== ===
on ATOM EXEC
xip mode.
1. goto nk.exe, open S000 file with hex editor.
2. the existing 1st bootscreen bmp file from address 3D50 to 3C185
3. you may replace it with your bmp (cut & paste to that range address)
diskimage_Ver.nb0
1. open diskimage_Ver.nb0 file with hex editor.
2. the existing 1st bootscreen bmp file from address 184D5C to 1BD191
3. you may replace it with your bmp (cut & paste to that range address)
================================================== ===
done!, enjoy your own 1st bootscreen on your device
** I'll assume you already know how to replace the block data (range address) in Hex Editor **
cheers!!
=========================================
thx all for sharing your knowledge
Yup, thanks for this tutorial, tried it and it works like a charm, very easy once you get the hang of using the Hex editor.
PaSSoA said:
Yup, thanks for this tutorial, tried it and it works like a charm, very easy once you get the hang of using the Hex editor.
Click to expand...
Click to collapse
Guys is suitable for ATOM LIFE?
Thankyou for you tutorial Abusalza, great work!
If we dont have corel Paint Shop but have Adobe Photoshop how can we adjust the image to that document size?
Any suggestions appreciated, thanks again.
well i think its pretty much the same.
but last time i used photoshop it saved size was 230.456 bytes.
so cut it the two byte using hex editor and its still showing fine
homer285 said:
Thankyou for you tutorial Abusalza, great work!
If we dont have corel Paint Shop but have Adobe Photoshop how can we adjust the image to that document size?
Any suggestions appreciated, thanks again.
Click to expand...
Click to collapse
Thanks worked it out
pdafre4k said:
well i think its pretty much the same.
but last time i used photoshop it saved size was 230.456 bytes.
so cut it the two byte using hex editor and its still showing fine
Click to expand...
Click to collapse
Yup. deleted 2 bytes on last line. sorry forget to explain before
pdafre4k said:
well i think its pretty much the same.
but last time i used photoshop it saved size was 230.456 bytes.
so cut it the two byte using hex editor and its still showing fine
Click to expand...
Click to collapse
becarefull, your xip module could be ruined, because the bootscreen want a place to be located either, if you port the 23x.456, it wont be bm6, but bm9 or 8,.
So, it will take place more than you think,.
you have to use some program like corel (adobe photoshop doesnt works easily for me)
then it will create 230.454,.
regards,.
Microsoft Paint works perfectly too save-as 24-bit bitmap.
Garmin said:
becarefull, your xip module could be ruined, because the bootscreen want a place to be located either, if you port the 23x.456, it wont be bm6, but bm9 or 8,.
So, it will take place more than you think,.
you have to use some program like corel (adobe photoshop doesnt works easily for me)
then it will create 230.454,.
regards,.
Click to expand...
Click to collapse
don't worry, mate. if u get files as bm8, bm9 or others, edit with hex and changes to bm6 and deleted 2 bytes last lines to get correct sizes...
i have been not in touch since i made rotorX
http://forum.xda-developers.com/showthread.php?t=349603&highlight=rotor
i was thinking of intergrating s2u2 and s2p into wm 6.1 into rotor wm6.1 ,if you have any possible links please for s2u2 1.01 and S2P-0.40
which are here http://forum.xda-developers.com/showthread.php?t=377627
and http://forum.xda-developers.com/showthread.php?t=377627
i would appreciate this help.
although i also needed touchflo which might be missing this time because its gone paid and oem might not be available for touchflo 2.7 .
p.s. integration of s2u2 1.01 and s2p 0.40 current versions into rom will be hot.
also many intelligent rommers might be making this by the time i am saying ,that will ease up my job to only downloading ,but my idea is to keep external rom free this time because then one cannot change dialpads and comm managers skins easily as it spoils device integrity.
i am still not sure yet but here are screen shots cause i have to do alot of homework.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
many methods exist ,what could be the best easiest way for making oem. asking the experts here.
The easiest way to create an OEM Package is using ervius package tool... (I've attached it below).
I'd check with A_C whether you can integrate the S2 apps within your ROM as some devs are fussy about that sort of thing...
For TouchFlo, you could integrate the free version of FTouchFlo from before it went comercial, or you could implement the original HTC Biotouch setup.
kamalneet said:
Click to expand...
Click to collapse
Sorry to go OT and be totally unhelpful, but what plugin is that below HTC Home? Is it a rlToday theme? I've been looking for something just like that, that has a few calendars.
What's the plugin with calendars? Looks like a rlToday plugin, but spent forever looking for one like that.
its modified rltoday clicking on it can display full calendar but i have disabled it and although it changes date everyday and R you see below it is prss reader for news rss feed ,
you have to uninstall any other rltoday before you install today.cab given here then you can latercopy themes as you do in rltoday or instal rip theme and put back in current rltoday anyway you like it to be.
The best for package creation is ervius package creator with MSCEInf (see atached file).
For S2[...] packege look into my attachment file too take it in your OEM folder and select packages in BuildOS (after replacing graphics if you want or/and the initflashfile.txt).
Good luck
ps.if you need more information PM me
With the initflashfiles above, all of the files are copied into the default directory. Because of the way S2U2 and S2P are coded, the files can reside anywhere, and so some of the lines in that file are unnecessary... I can create a modified one if wanted...
xvx45 said:
The best for package creation is ervius package creator with MSCEInf (see atached file).
For S2[...] packege look into my attachment file too take it in your OEM folder and select packages in BuildOS (after replacing graphics if you want or/and the initflashfile.txt).
Good luck
ps.if you need more information PM me
Click to expand...
Click to collapse
thank you .
l3v5y said:
With the initflashfiles above, all of the files are copied into the default directory. Because of the way S2U2 and S2P are coded, the files can reside anywhere, and so some of the lines in that file are unnecessary... I can create a modified one if wanted...
Click to expand...
Click to collapse
sure that will be expert solution
I'm going out very soon, but I should be able to do it later/tomorrow morning...
Maybe someone else can edit the file?
l3v5y said:
I'm going out very soon, but I should be able to do it later/tomorrow morning...
Maybe someone else can edit the file?
Click to expand...
Click to collapse
thanx ,me havin exams and alot of home work too lets see if i could build this before 17 may or i'll have to delay for more than 2 months by that time more advanced forms of s2u2 and s2p will come up.
I've just remembered I have exams too!
l3v5y said:
I've just remembered I have exams too!
Click to expand...
Click to collapse
we are in the same boat then ,but during exams our performances double in alternate areas ,actually i completely forgot how did i design rotorx back then now newer methods like neokit etc make it easy but i cannot concentrate properly like then.means multi tasking thread in my cerebal cortex seems to be working low this time unlike then.
another easy way coming in my mind was to take clean wpa2 cloudyfa rom and assing it to pick cabs from extrom and installing like default devices do but where in registry do i have to make that chage to modify autorun remains unknown due to lack of concentration.but for that i would need cloudyfa to give me permission to go ahead.
The cabs are all installed through the config.txt in the dump.
l3v5y said:
The cabs are all installed through the config.txt in the dump.
Click to expand...
Click to collapse
well thats called reigniting my sleepy ideas for better ,cloudyfa's clean edition config.txt says "EXEC: \Windows\SDAutoRun.exe " means i would have to now find config.txt of nvid wm5 to find what it used to do. so would try. well old prophet rom used to have autorun.exe ,install_tsk.exe and setup.exe well the rest are the cabs so my guess is something invoked setup.exe which then made run autorun.exe which then inreturn installed all the cabs (or viceversa)which were present on that extrom drive , but which was the file from mains drive who did this and if it was config.txt that means in my case command should be changed to
1. "EXEC: \ext_rom\autorun.exe"
2. "EXEC: \ext_rom\setup.exe"
3. none of the above because i am making a mistake which could be clarified by experts.
also \ext\rom needs to have proper name as in clean edition its named to \extended_ROM2 leaves me confused because some previous places it was named as \ishadow or \Extended_ROM\,it should have some default name leaves me confused.
main files gives error log of neokit "ImgfsToDump 2.1rc2
Cannot map file F:\OUTPUT~1\ROMDUMP\imgfs.bin" for nk.nbf of JAMin_WWE_213923_2139123_022021_ship.exe means it wont share files other that ext_rom which means deadlock to me as i will never be able to open it ,need reignition again.
it also would leave me with option to move back to UC clean option with oem packs where i was in my first post.
In the config.txt file, you'll need to add "CAB: \Extended_ROM2\...CAB"
for cabs (where Extended_ROM2 is the name of the extended_ROM).
In cloudyfas latest ROMs, it would be
CAB: \iShadow\test.cab
for a cab file called "test".
on cloudyfa's config.
It means that SDAutorun for UC would be run.
you can change it into this
Code:
LOCK: Enabled
[COLOR="Red"]CAB: \Extended_ROM\abcd.cab[/COLOR]
LOCK: Disabled
EXEC:\windows\SDAutoRun.exe
that means you can run some cabs fropm extended rom. The cab's name is abcd.cab
And SDAutoRUn( for UC ) will be running too later.
l3v5y said:
The easiest way to create an OEM Package is using ervius package tool... (I've attached it below).
I'd check with A_C whether you can integrate the S2 apps within your ROM as some devs are fussy about that sort of thing...
For TouchFlo, you could integrate the free version of FTouchFlo from before it went comercial, or you could implement the original HTC Biotouch setup.
Click to expand...
Click to collapse
Here you can find what you need:
http://www.pda4x.com/thread.php?fid=65
Could I point out that keygens are a form of warez, and that this forum is against the warez. I suggest you remove that link...
varanusvincent said:
on cloudyfa's config.
It means that SDAutorun for UC would be run.
you can change it into this
Code:
LOCK: Enabled
[COLOR=Red]CAB: \Extended_ROM\abcd.cab[/COLOR]
LOCK: Disabled
EXEC:\windows\SDAutoRun.exe
that means you can run some cabs fropm extended rom. The cab's name is abcd.cab
And SDAutoRUn( for UC ) will be running too later.
Click to expand...
Click to collapse
However, Cloudyfa has the Extended ROM called something else, so it would be
Code:
[COLOR=Red]SHOW:\iShadow\Background.BMP[/COLOR]
LOCK:Enabled
CAB:[COLOR=Red] \iShadow\[/COLOR]cabname.cab
[COLOR=Red]EXEC:\iShadow\CusTSK.exe \iShadow\theme.tsk[/COLOR]
LOCK:Disabled
EXEC:\Windows\SDAutoRun.exe
Code:
SHOW:
Allows you to show a background when customizing.
Code:
LOCK:
prevents users from running programs when the customization is taking place.
Code:
[COLOR=Black]EXEC:\iShadow\CusTSK.exe \iShadow\theme.tsk[/COLOR]
Allows you to install a theme of your choice. You will need CusTSK.exe and the theme file.
A little note, you should try and pad out the commands with " " (spaces) so that they are five characters long before the "\" of the file location. Otherwise, AutoRun.exe may have some trouble with the file
Code:
CAB: \test.cab
rather than
Code:
CAB:\test.cab
Download View attachment package-creator-v27.zip
After downloading the package creator Extract to any folder and run package-creator-v2.7.exe. Select language and select group to insert package. Here The group reffers to Programs. You can add or edit lang.xml to add or delete groups.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then click on Open Cab File and navigate to your cab file and Click Open.
Wait until it shows you done Confirmation window. Then navigate to the cab folder and you will see new folder with OEm package. This tool will generate initflashfiles.txt, option.xml, .dsm and .rgu for the kitchen ROM.
Copy the OEM package to your kitchen and have fun with customizing your Rom
(found this somewhere on internet, correct me if i m wrong)
Great work! Nicely done tut. Here is another method to do so. This one is a bit faster but it doesn't always works.
Cab2OEM is also a free software that can be used to convert cabs to packages. This software is a command-line utility with no GUI but it does its job pretty well.
Cabs are of two types, the older ones with an inf file with extension .000 inside that describes the installation process and the newer ones with a _setup.xml files. Cab2OEM works on XML ones only.
Usage:
Its simple, just fire up a command prompt and run this command:
Code:
Cab2OEM -f <path to cab>
Here, replace path to cab with a real path. In a few seconds, it will convert the cab into a folder in the current directory.
NOTE: Cab2OEM creates an option.xml file inside the package which provides a description to the package that can be seen while running build os. but by default, it doesn't adds the package to the buildos list. I recommend you to delete this file.
This method is not as advance as Package Creator but its a quick and dirty one Package Creator can work with all cab files.
The file is attached with this post.
Great Work
Good going man....
Can you suggest some good and easy Kitchen for old gene..
Can i also include cracked applications...in custom ROM
Ramerson's kitchen is the easiest one i have ever seen. But the whole process of cooking ROM can never be easy, no matter which kitchen you use.
We strictly dont support cracking etc here so no answer for that.
Many thanks Krazy.......
Can ur ROMs be used to delete some packages and include some freewares...
please guide me about the pagepool.....what are disadvantages of increasing or decreasing it...does it help in increasing RAM....
I read about a thread which says RAM can be increased by deleting ExtROM...
Your expert comments please....
Also the Ramerson's kitchen link and "How to gude" if possible........
That would be nice of you....
Heres a quick response:
1. Yes my roms can be dumped and modified as per your needs. The only thing you need is the knowledge of how to dump them properly for recooking. For that refer to ramerson's tut.
2. Pagepool is that reserved part of memory that is never available for the programs to use and iit is used by the OS to maintain its internal state, data structures and so on. More the pagepool memory, more resources the OS will have and more simualtaneous running programs you can have. But this clashes with the fact that programs also need RAM for other purposes other than the OS provided resources. So the contradiction is that you cant run more programs simualtaeously id you have less RAM. So increasing Pagepool decreases RAM but increases OS resources, Decreasing page pool increases free ram and decreases OS resources. Chefs have to keep a balance between that. For gene, 6 MB of Page Pool is recommended, keeping in mind all the specs of the devices. Pagepool has to be changed everytime you recook the ROM as of now.
3. My ROMS use 4 MB of ExtROM and that is optimal, by default you have 10 MB of ExtROM. SO no need to messup with that, device doesnt boots with extroms smaller than that. Ramerson has also confirmed this.
4. Ramerson Kitchen is a seprate thread in this same forum, use your eyes and mind for that. How to Guide is currently not available as step by step, but Ramerson's tut which is a sticky post, will help you greatly.
I hope my answers helped.
o my god my head is spinning
hi guys
i tried reading all this and my god o god my head went for a spin i think for me to do any thing cook rom and all this in this chapter will take me a long long time of reading which im realy not great at
but reading all this give me more repect for Krazy,ankit,ramersnow and all u great techi guys
u guys are great man hats off to all off u and thanks a million
^Thanks Hari. Actually the gene you are having in your hand is not very less complex than any other computer. So apart from some basic differences, most of the elements of computer engineering can be applied to this small buddy as they are applied to computers. Thats why it seems so darned techie, coz it is techie
i meant every word
hi
to all u great contributors to this great forum i thing all these tuts available are a great eye opener to a totally non techi guys like me who uses ur great services which you actually do for free i having read many many tuts have clearly understood the time u are spending for us to enjoy and i really really say from my heart hats off to u guys and thanks for ur great contribution
and in the future when things get better for me i will start donating
and the funny thing is i sell computers for around 10+yrs
but this info in the tuts is a total head spinner for me
getting to next level
Great Krazy....
U r true krazy about technology......
To run emulators like SPB Mobile shell in best performance what should be optimum pagepool....
New version of Package Creator
Please find newer version of package creator, Version 5.4 to be exact
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
Thanks man! this will really help
imblfmstr said:
Great Krazy....
U r true krazy about technology......
To run emulators like SPB Mobile shell in best performance what should be optimum pagepool....
Click to expand...
Click to collapse
SPB Mobile shell is not an emulator, its a shell replacement which actually runs on the top of the existing shell32.exe shell. There is no extra page pool requirement for it to run. 6 MB would be fine.
Cab Maker
Useful application for Making Windows CE compatible cab can be found here: http://forum.xda-developers.com/showthread.php?t=400221. It can be used by developers as well as cook.... OOPS Chefs
Another alternate is http://www.ocpsoftware.com/downloads/cecabmgr/CeCabMgr_Setup.exe
Could any One tell me how to make my own package and add it to ROM while cooking , or the link that i can found this
I already use the tools that mentioned here but while cooking process going on it give me an ERROR ( I use the cooking way in -[TUTORIAL]How to cook for GENE-)
Thanks in advance
facing one problem in cooking a ROM...
every time i add a custom package ...and then i run "build OS" i get an error
"Error in building in default.hv and user.hv"
and i if remove the content of .rgu files from the custom packages it run fine..no issue...
i am using the "package-creator-v2.7" to create packages..i want to have some registry settings in ROM...
Please advice how to overcome this issue....
orange2784 said:
facing one problem in cooking a ROM...
every time i add a custom package ...and then i run "build OS" i get an error
"Error in building in default.hv and user.hv"
and i if remove the content of .rgu files from the custom packages it run fine..no issue...
i am using the "package-creator-v2.7" to create packages..i want to have some registry settings in ROM...
Please advice how to overcome this issue....
Click to expand...
Click to collapse
I do not have a straight solution for this, But here is what I did, I exported the registry key, saved it as rgu and then used package manager 5.4 to make it into a package.
Registry file is not properly formatted. Keep following points in mind :
1. Registry file (.rgu) must be in unicode format, not ANSI, which is the default saving format of Windows Notepad. You can change it in the save file dialog of notepad.
2. The file must begin with the word REGEDIT4 in the first line saperately.
3. There should be atleast one or two blank lines at the end of the file.
4. Entries in the files should be properly formatted. Following are the general values and their formattings that you will find in rgu files :
a. Path to hives must be covered in square brackets, ex : [HKEY_LOCAL_MACHINE\Software\Microsoft]
b. All string values must be formatted like this : "Name"="Value". If there is a file path inside the string, it should be having \\ instead of \ as separator. Ex: "FilePath"="\\Windows\\AudioManager.exe"
c. All DWORD values should be in this format : "Name"=dword:8 digit number. Ex : "BacklightOff"=dword:00000001
d. All binary values should be formatted as : "Name"=hex:v1,v2,v3,v4...... Ex: "AValue"=hex:00,00,11,01,10
Follow these guidelines and your registry file will compile fine.
Thanks a lot Krazy...thats a valuable information .... i ll check the rgu files ... correct them and give a shot.....
and thank you Addicted2xda for your inputs... i ll try this one also ..
Also please note, inside the dump folder, there is a text file that contains the error log. The last 2-3 lines of this file actually describes in which file the error occured. Actually the Windows Mobile Registry is compiled from rgu files using a program called rgucomp.exe and is stored in files ending with extention .hv. Just for your information
Good luck!