How to make an extended rom - a tutorial. - P3300, MDA Compact III upgrading etc.

N.B. Disclaimer - try at your own risk - i am not responsible for anything that happens to your device.
Tools needed (all attached)
1. Winimage - open extended_rom.nb with this to view contents. (winimage is a trial but lasts 30 days of use i.e. only the days you use it)
2. Dark simpsons - Htc Rom Tool - use nb to make nbh for flashing
3. Dutty's tool - to extract os.nb (windows.nb) and extended_rom.nb from rom nbh file
(note os.nb can be left out if your simply modifying existing extended rom)
STEPS
1. Open extended_rom.nb with winimage - remove any cabs programs you dont want in your ext rom.
2. Extract config.txt to desktop - this gives instructions on which cabs etc to install.
{
"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"
}
3. Edit config.txt - add name of cabs in same format as shown
e.g. one i did for the touch but never used
LOCK:Enabled
CAB: \Extended_ROM\Customization_1.cab
LOCK: Disabled
RST: Reset
Second line is to install a cab
Lock enabled. lock disabled, rst reset always needs to be included.
4. Add cabs via winimage - inject or drag and drop
5. Delete old config.txt and inject or drag and drop new one.
6. Right click on cabs and config.txt in winimage and set 'read only' (other wise cabs will deleted from ext rom after install)
To resize extended rom - use Image - Change format
7. Save and exit winimage.
8. Extract windows.nb from your rom using dutty's tool (enclosed) - rename os.nb. (note os.nb can be left out if your simply modifying existing extended rom)
9. Open Dark simpsons htc rom rool -rom builder - choose artemis, select System - os.nb (nb see note in step 8), ExtRom - choose your extended_rom.nb
10. Save and rom tool will make Your rom.nbh
11. Then you can flash as normal with rom update utility.
Thanks to faria for images and info that i based this tutorial on.
I've included an empty (apart from config.txt) 2mb extended rom.nb that you can use and add files too.

Thanks, as I said you are one dedicated dude.

what is the max. ext_rom area size?
regards,

fdp24 said:
what is the max. ext_rom area size?
regards,
Click to expand...
Click to collapse
Largest ext rom i've seen 15mb (smallest in winimage - image - change format = 160kb) - i would use the smallest that you need.

wow....
Great work,
you earned another Guinness from me....
Now i think it's time to test it...
Thanks a lot
Cheers, Peter

Thanks Meschle !
And what about a new tutorial for newbies to make Roms ?
Cheers!

Newbies should'nt be making rom
This is my theory for a newbie who has such ambitions - take this path.
1. Successfuly edit registry
2. Unlock and flash cooked rom
3. Cook extended rom
4. Learn how to make cab files
5. Decompile nbh into nb's and compile new nbh with different nb's
6. After these 5 steps are completed newbie will no longer be a newbie and ready to cook a rom - it doesnt matter which order thats done in its just a guide - also cab making is not absolutely essential but preferable.

Hi Meschle, I will attempt to get to 3, so here's my question, is it possible to make items from the extended rom install onto the sd card or just the device? also, if the cabs are deleted after install, is the memory they occupied then free for storage? Thanks.

Hi uniqueboy - there is a way to force cabs to storage card using a xml cab - have not tried it myself for storage card but have for main memory - so really ext rom is for main memory only installation. If you do not put a read only marker on your cab its deleted but usually the ext rom becomes corrupted so nonuse-able.

hi meschle. Thanks for your tutorial.
is there a way to make a extended_rom.nb file from scratch (file,new) with Winimage by throwing-in cabs and config.txt and saving, with whatever parameters and naming as extended_rom.nb ?
I´ve managed to copy to desktop PC my extended_rom by using total commander, but from reading yor tutorial it seems that we need a ROM Dump to start with. If this is the case...would you please also tell us which is the simplest/safest way to dump a device ROM?
Thanks again

sirgawain123 said:
hi meschle. Thanks for your tutorial.
is there a way to make a extended_rom.nb file from scratch (file,new) with Winimage by throwing-in cabs and config.txt and saving, with whatever parameters and naming as extended_rom.nb ?
I´ve managed to copy to desktop PC my extended_rom by using total commander, but from reading yor tutorial it seems that we need a ROM Dump to start with. If this is the case...would you please also tell us which is the simplest/safest way to dump a device ROM?
Thanks again
Click to expand...
Click to collapse
Yes you always need an extended_rom.nb to start with - use duttys tools to extract all the nb's from the nbh - its quite easy.
I'll post the 2mb extended_rom.nb so people can use it as a template.

meschle said:
Yes you always need an extended_rom.nb to start .
I'll post the 2mb extended_rom.nb so people can use it as a template.
Click to expand...
Click to collapse
but how can we get our own device ROM dumped into an nbh?
WIKI refers to this thread:
http://forum.xda-developers.com/showthread.php?p=1155823#post1155823
which deals with extracting just the extended rom nb from the device (in quite a complex way). I ´d like to dump the whole ROM NBH in order to get the ext rom nb by using dutty tools, and follow your thread.

meschle said:
I'll post the 2mb extended_rom.nb so people can use it as a template.
Click to expand...
Click to collapse
Lets say i take your nb file, open with winimage, delete all your files, throw in my extended_rom files (copied to PC with total commander), and save....
Have i arrived to the same extended_rom that i have on my device?

sirgawain123 said:
but how can we get our own device ROM dumped into an nbh?
WIKI refers to this thread:
http://forum.xda-developers.com/showthread.php?p=1155823#post1155823
which deals with extracting just the extended rom nb from the device (in quite a complex way). I ´d like to dump the whole ROM NBH in order to get the ext rom nb by using dutty tools, and follow your thread.
Click to expand...
Click to collapse
It is not easy converting a dump into a nb\nbh - i would strongly suggest getting hold of original rom if you can. You can make an extended rom using the nb i posted but you need the os.nb to make a flashable nbh - extended rom will not flash on its own.

This is config.txt from my stock ROM:
LOCK:Enabled
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk
CAB: \Extended_ROM\MP_CVSDcpl_20060718.cab
XML: \Windows\MP_MMS3.5_HTC_Generic_Artemis_060818.xml
CAB: \Extended_ROM\PP_DefaultPage_WWE.CAB
XML: \Extended_ROM\PP_ExtVer.xml
CAB: \Windows\PP_CommManager_Patch_060808.CAB
CAB: \Extended_ROM\MP_ttn.cab
CAB: \Extended_ROM\PP_RemoveBTlnk.cab
CAB: \Extended_ROM\ST_PatchPeripheral.cab
CAB: \Extended_ROM\MP_TT6_Voice10_ESN.cab
EXEC:\Extended_ROM\ChgScutAttri.exe
LOCKisabled
RST: Reset.
Click to expand...
Click to collapse
if i modify to read:
LOCK:Enabled
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk
CAB: \Tarjeta de almacenamiento\MP_CVSDcpl_20060718.cab
XML: \Windows\MP_MMS3.5_HTC_Generic_Artemis_060818.xml
CAB: \Tarjeta de almacenamiento\PP_DefaultPage_WWE.CAB
XML: \Extended_ROM\PP_ExtVer.xml
CAB: \Tarjeta de almacenamiento\PP_CommManager_Patch_060808.CAB
CAB: \Tarjeta de almacenamiento\MP_ttn.cab
CAB: \Tarjeta de almacenamiento\PP_RemoveBTlnk.cab
CAB: \Tarjeta de almacenamiento\ST_PatchPeripheral.cab
CAB: \Tarjeta de almacenamiento\MP_TT6_Voice10_ESN.cab
EXEC:\Extended_ROM\ChgScutAttri.exe
LOCKisabled
RST: Reset
(Tarjeta de almacenamiento being Storage card in Spanish)
Could i get more memory in device by deleting those 7 cabs from extended_Rom and having them in storage card root, being automatically run (installed) on Hard reset?

You could flash nbh with no ext_rom whatsoever or use smaller extended rom nb attached - but you still need original rom to do this. If you just delete the cabs out of the extended rom you have - it stays the same size - the nb is a fixed size.

meschle said:
You could flash nbh with no ext_rom whatsoever or use smaller extended rom nb attached - but you still need original rom to do this. If you just delete the cabs out of the extended rom you have - it stays the same size - yhe nb is a fixed size.
Click to expand...
Click to collapse
That´s understood.
My question now is about flashing an extended_rom with a config.txt file pointing to cabs outside extended_rom (in storage card):
Would that do the trick?
The problem I see using /2577 folder as workaround is that it runs every time you insert the storage card (And i´m not sure if it also requires operator action for every cab being run)

sirgawain123 said:
That´s understood.
My question now is about flashing an extended_rom with a config.txt file pointing to cabs outside extended_rom (in storage card):
Would that do the trick?
The problem I see using /2577 folder as workaround is that it runs every time you insert the storage card (And i´m not sure if it also requires operator action for every cab being run)
Click to expand...
Click to collapse
That will not work - cabs have to be in extended_rom.
Most of the cabs you listed will have no destination dialog so will install without any user input using the \2577 method - you could disable it until you needed by renaming autorun.exe to autorun.txt.

meschle said:
That will not work - cabs have to be in extended_rom.
Click to expand...
Click to collapse
As there are lines in stock ROM config.txt pointing to windows folder...
(as CAB: \Windows\PP_CommManager_Patch_060808.CAB)
Perhaps you mean : "cabs cannot be in external storage"?

sirgawain123 said:
As there are lines in stock ROM config.txt pointing to windows folder...
(as CAB: \Windows\PP_CommManager_Patch_060808.CAB)
Perhaps you mean : "cabs cannot be in external storage"?
Click to expand...
Click to collapse
I get your point - i've never seen anybody do that - it is probable that when the ext rom is initialized storage card has not yet booted and so it will not work. Worth a go though but device may just crash at that point.

Related

Splash screen

I'm sorry may be this is stupid question..
But i want to know can we use splash screen creator that created in this site... they said about using it on II mini and IIs, i assuming it can be use on our IIi but i'm not sure....
Every one who know about this can you tell me please...
Thanks before
Hi Cornelius,
you can use it - I've tried and it works fine.
You can create splash screens from bmp files using nb_image_converter_859_418.exe
There is a cab file somewhere around which can update your alpine to use these, or you can modify a custom extended rom to load it up ... choice is yours.
I'm working on a extended rom customiser that will let you do it via a GUI, but it's taking a little time.
If you can't find the cab file method anywhere let me know and I'll post it to you.
Bal
Step by step?
Hello bal666, Thanks for reply....
I've looking around the forum (maybe nat all), but i still confused (or maybe baecouse my bad english??? )
At forum :" Tool to create costume ext roms for alpine" if i'm right, you put splash screen when create ext rom wich it hidden....???
where can find splash screen? ( I cook my ext ext rom using your step by step guide and example from PUG rom, thanks for you all )
OR
can we put splash screen directly (with out cook rom again?) like step by step guide at magaician forum? and do just like that? (i mean folow that step by step instruction?)
He.he long question right?
Thanks before for your guide...
Hi Cornelius,
don't worry about your english ... you should hear me after a few drinks :shock:
Both methods will work - and I will post some details for you in the morning ... and the necessary files.
Bal
Waiting
Waw...
Thanks alot bal666
I'll waiting it...
Terima Kasih banyak ( Indonesian ) / thank's a million
Hi Cornelius,
sorry for the delay ... disaster at work.
I've attached a program (I found it in this forum) for making nb splash files from bmp files.
Now two ways of setting splash image:
1. Decode an alpine extended rom (or use your own)
a. open the *.fat file in a hex editor.
b. Paste your nb file at location 0x1880000, writing over the data there.
c. Encode the fat file into a new extended rom and burn to your alpine
2. use the MDA3_bootimage_changer2.CAB attached and follow instructions in the usage.txt file. NOTE - I think I've used this and it worked ... but don't remember too well :shock:
Hope that helps .... my suggestion is that if you're already using a custom extended rom then use method 1. Method 2 is a bit experimental and may cause problems.
Bal
I'll try it
thanks bal...
maybe i'll use both way,first one use for cooking rom, then the second way i'll use when i want to change only splash without loosing / reinstall my apps.
i'll work on it after back from hospital.
i'll inform if i failed or success.
Hex Editor
I'm sorry bal... but i need to ask you again...
1. I want to ask about 1st way...
did you mean"hex editor" is XVI32???
2. if yes how we paste our nb file to loc 188000 ( i think i can found loc 1880000, just how to replace those file? )
3. Can we extrac original nb file? & how
I'm sorry to take your time...
And thanks again for your time and help....
Original SplashScreen
Anyone please post here if you have an original xda IIi splash screen...
Hello Everyone
Sorry for disturb (I hope someone answer my question this time)
I'm doing same thing create my ext ROM for my mini same step like i create my ROM for XDA IIi ( i edited original ext ROM asia magician), after finished, i try to change my splash screen on my mini, all runs well.
then i update my ROM, after finish i did hard reset and my device booting, but... splash screen still same not going back to original one???
is that normal??
after my today screen appear nothing happen (seems my ext rom didn't run automaticly), so the result is programs on my ext ROM and my setting didn't installed (all of them)
Did the ext rom do not run because th effect from slash screen change???
or my mistake when creating mini ext ROM?
What should i do???
Please some one help me???
Hi Cornelius,
how did you change the splash screen for your mini?
Bal
Solved for Splash
Hai bal... nice to read a post from you again
I used the second way ( MDA3_bootimage_changer2.CAB way ) because it's easier and easier to go back to original splash )
Anyway i've solve the problem about splash screen i can get my original splash, even i download the original one from forum ... (errr i forgot)
Now the only problem is i dont understan why my Ext ROM mini didn't run any installation, i just did same thing for my IIi and it's work....
They said mini and IIi way is same....
Anyone can tell what i miss??
or direct me to right forum...
Thanks for your time to answer me...
Hi Cornelius,
can you post a list of files in your extended rom, but make sure there exists the autorun.exe and config.txt (I think!)
Bal
List file on Ext ROM
Here the list on my Magician Ext ROM:
CameraWizard_O2Asia_Customize.CAB
Caller_ID_Magician_Generic_WWE_RC13.CAB
SmartDialing_Magician_Generic_WWE_RC13.CAB
CAB-ArcsoftMMS-2.0.022-Magician-O2Asia-ENU-21Mar05.CAB
CV2.41.386_wwe.CAB
JMM101257_wwe_1004.CAB
DialerSkin_Portrait_091104.sa.CAB
DialerSkin_Landscap_091104.sa.CAB
default_103133.sa.CAB
DelAddStarMenu_092404.sa.CAB
O2_Base_v103116.sa.CAB
O2Auto.sa.CAB
O2_User_Angent.sa.CAB
BTHUSB_PATCH_AKU26.CAB
Band_Select_Enable.sa.CAB
Version_WWE_111922.sa.CAB
SetButtonLock.exe
Autoconfig.txt
Autoconfig.exe
setbuttonlock.exe
SetMyFavourites.exe
Config.txt
And others auto cinfig cab for indonesian operators..
My config.txt command:
CAB: \Extended_ROM\CameraWizard_O2Asia_Customize.CAB
CAB: \Extended_ROM\Caller_ID_Magician_Generic_WWE_RC13.CAB
CAB: \Extended_ROM\SmartDialing_Magician_Generic_WWE_RC13.CAB
CAB: \Extended_ROM\CAB-ArcsoftMMS-2.0.022-Magician-O2Asia-ENU-21Mar05.CAB
CAB: \Extended_ROM\CV2.41.386_wwe.CAB
CAB: \Extended_ROM\JMM101257_wwe_1004.CAB
CAB: \Extended_ROM\DialerSkin_Portrait_091104.sa.CAB
CAB: \Extended_ROM\DialerSkin_Landscap_091104.sa.CAB
CAB: \Extended_ROM\default_103133.sa.CAB
CAB: \Extended_ROM\DelAddStarMenu_092404.sa.CAB
CAB: \Extended_ROM\O2_Base_v103116.sa.CAB
CAB: \Extended_ROM\O2Auto.sa.CAB
CAB: \Extended_ROM\O2_User_Angent.sa.CAB
CAB: \Extended_ROM\BTHUSB_PATCH_AKU26.CAB
CAB: \Extended_ROM\Band_Select_Enable.sa.CAB
CAB: \Extended_ROM\Version_WWE_111922.sa.CAB
EXEC:\Extended_ROM\SetButtonLock.exe
CPY1:\Extended_ROM\Autoconfig.txt
CPY2:\Windows\Autoconfig.txt
EXEC:\Windows\Autoconfig.exe
RST: Reset
Yup thats it...
Hope you can help....
Thanks in advanced
Hi Cornelius,
it does look like you're missing the autorun.exe file (although this might not be required for the mini).
Best approach would be to compare what you have in your extended rom with that which comes with a "normal" extended rom that works.
See if the autorun.exe does exist there - if it does then you know you need to add it to your rom. Otherwise I've no idea, perhaps someone else on this forum can help.
Good luck
Bal
Thanks bal
Thank for all your time..
but bad luck for me, there is an autorun.exe on my ROM, and what i remove from nomal rom only the CAB files...
fiuh....
Thanks anyway bal for all
Any one can help me, please??
bal666 said:
Now two ways of setting splash image:
1. Decode an alpine extended rom (or use your own)
a. open the *.fat file in a hex editor.
b. Paste your nb file at location 0x1880000, writing over the data there.
c. Encode the fat file into a new extended rom and burn to your alpine
Bal
Click to expand...
Click to collapse
Hi Bal666
You said open *.fat file did you mean the *.nbf because the hex editor will not load the *.fat.
Thanks
Hawkeye,
nope, I meant the *.fat file. The name is a bit of a misnomer unfortunately, as in the version of the decoder that is currently available the extra data at the end of the fat file (not really part of the FAT image) is kept in place.
You should be able to open this file in a hex editor ...
You could wait a couple of days while I do the help file for the new tool, it's GUI based and will let you extract and insert splash files without resorting to hex editors
Bal
yeah i think i'll wait.
Thanks
Nuts, the help file is taking ages ... so I posted the thing to get it out of the way ...
http://forum.xda-developers.com/viewtopic.php?p=191164#191164
No help file and no user guide ... could be interesting

[Q]Question regarding Extended ROM

I have a question regarding the Extended ROM. I've read that this is the part that is executed whenever the device is hard reset and goes through the "Customization" phase (after the 3-second message).
Whenever we use the "nbhextract.exe" command on a shipped ROM, it produces an "ExtROM.nb" file which is separate from the OS.nb file. So that means our OS backups should not contain the ExtROM... However whenever I restore my ROM backup of my device, it does do the Customization, which means that the ExtROM actually is there, right??
Another confusing thing is that I remember a few times in the Device Info screen the ExtROM version would show up after a couple of resets (after restoring my OS backup). I cannot get it showing now, however.
There is a registry setting that can also show the Extended_ROM directory but it's not working for me either:
http://forum.xda-developers.com/showthread.php?t=315588
So my question is, is it really true that the Customization IS the Extended ROM and also, why is it being executed when I didn't even back that up?? If anyone can clear this up for me, that would be great
Custumisation can also be run without having an Ext rom.
The Autorun looks a t a registry setting that points to it's configuration file.
This Conifguration "config.txt" file in stock roms points most commands to the files on the \Ext_rom partition\
In most cases the config.txt file is only in the ext rom so autorun might run but not find the config file then quit.
Un custom roms the registry is changed and all files that then run in custimasation are simply in the Windows folder or it can be disabled.
It might be that some stock roms have a mix of files that need to be executed from ext_rom and some from Windows. But that should result in an error for the files it cannot execute from the ext_rom.
Ok, I just found an old backup of my documents and programs that I made with Spb Backup. It was made before I did any installs of ROMs to my device back in March. My ExtRom version now shows up in the Device Info (which probably answers the question of why I saw it show up after reboot!) Thank god I have an original Spb backup of the device!
The registry setting to show the ExtRom directory doesn't work, however. I'm still working on it.. (EDIT: I probably can't see it now because only the original intact ROM would contain the ExtROM.. I am just using the OS backup now)
Thanks Noonski, your answer probably answered the question as to why my OS backup hangs after doing the Customization. It's likely installing from the Windows directory but then looks for the ExtROM directory and can't find it, so it hangs. I'm going to see if I can back up my ExtROM files and then somehow make it into a ROM.
Edit: If anyone has a Rogers Elfin that has been unmodified, could you please PM me and let me know if that registry trick works. I'd like to have a copy of the Extended ROM directory and make it into a ROM backup.
dsixda said:
Ok, I just found an old backup of my documents and programs that I made with Spb Backup. It was made before I did any installs of ROMs to my device back in March. My ExtRom version now shows up in the Device Info (which probably answers the question of why I saw it show up after reboot!) Thank god I have an original Spb backup of the device!
The registry setting to show the ExtRom directory doesn't work, however. I'm still working on it.. (EDIT: I probably can't see it now because only the original intact ROM would contain the ExtROM.. I am just using the OS backup now)
Thanks Noonski, your answer probably answered the question as to why my OS backup hangs after doing the Customization. It's likely installing from the Windows directory but then looks for the ExtROM directory and can't find it, so it hangs. I'm going to see if I can back up my ExtROM files and then somehow make it into a ROM.
Edit: If anyone has a Rogers Elfin that has been unmodified, could you please PM me and let me know if that registry trick works. I'd like to have a copy of the Extended ROM directory and make it into a ROM backup.
Click to expand...
Click to collapse
This can be easily modified using Hypercore to dump the rom.
The look at the Rom/XIP folder and adjust the boot.rgu and the .rgu in OEM operators.
Or just change the config.txt in oemoparators.
Then recook the files into NBH file.
Since you are allready taking it apart it already is missing the original HTC signature after using HTCRT.
Noonski said:
This can be easily modified using Hypercore to dump the rom.
The look at the Rom/XIP folder and adjust the boot.rgu and the .rgu in OEM operators.
Or just change the config.txt in oemoparators.
Then recook the files into NBH file.
Since you are allready taking it apart it already is missing the original HTC signature after using HTCRT.
Click to expand...
Click to collapse
Aha! Thanks for the tip... this is what the config.txt says under /Windows:
LOCK:Enabled
EXEC:\WINDOWS\cusTSK.exe \WINDOWS\Rogers_White.tsk
XML: \WINDOWS\Menu_Operation.xml
CAB: \WINDOWS\pIE_Default_Page_Rogers.CAB
CAB: \WINDOWS\PT_PIE_DEFAULT_0409.CAB
CAB: \WINDOWS\DoMore.CAB
CFG: \Extended_ROM\Config.txt
Just taking out that line will probaby do the trick... However I want to get the entire ROM replicated, so it'll require me to get the Extended_ROM out.
I also found a cool tool by AnDim that can construct an ExtROM.nb from the Extended_ROM directory files:
http://forum.xda-developers.com/showthread.php?t=303049
dsixda said:
Aha! Thanks for the tip... this is what the config.txt says under /Windows:
LOCK:Enabled
EXEC:\WINDOWS\cusTSK.exe \WINDOWS\Rogers_White.tsk
XML: \WINDOWS\Menu_Operation.xml
CAB: \WINDOWS\pIE_Default_Page_Rogers.CAB
CAB: \WINDOWS\PT_PIE_DEFAULT_0409.CAB
CAB: \WINDOWS\DoMore.CAB
CFG: \Extended_ROM\Config.txt
Just taking out that line will probaby do the trick... However I want to get the entire ROM replicated, so it'll require me to get the Extended_ROM out.
I also found a cool tool by AnDim that can construct an ExtROM.nb from the Extended_ROM directory files:
http://forum.xda-developers.com/showthread.php?t=303049
Click to expand...
Click to collapse
Simply using Total Commander without any registry tweak.
Type in \EXTENDED_ROM
To get into the folder (original rom flash.)
And copy over the files and put these into any SYStem folder.
You would get the rom replicated without losing the space to EXT_rom partition.
EXT_Rom is So 90's
At least on the ELF
Ok, there was someone on the forums here (Boodah) who happened to have an unmodified Rogers Elfin with an intact ExtROM. So, using TFAT Image Editor I was able to make a working OS + ExtROM Now it functions like its original version
Thanks for the Total Commander tip.. with that app I was able to verify the ExtROM was flashed on my Elfin.
dsixda said:
Ok, there was someone on the forums here (Boodah) who happened to have an unmodified Rogers Elfin with an intact ExtROM. So, using TFAT Image Editor I was able to make a working OS + ExtROM Now it functions like its original version
Thanks for the Total Commander tip.. with that app I was able to verify the ExtROM was flashed on my Elfin.
Click to expand...
Click to collapse
Ah your not cooking it completly.
That would gain you at least 10MB
Noonski said:
Ah your not cooking it completly.
That would gain you at least 10MB
Click to expand...
Click to collapse
Yeah the ExtROM has to be 10,240MB or else it will not flash properly. But I want it to be like the original.
Anyways, nobody uses the original software anyway ;-) But the backup is there for people who need it for warranty or selling purposes.
dsixda said:
Yeah the ExtROM has to be 10,240MB or else it will not flash properly. But I want it to be like the original.
Anyways, nobody uses the original software anyway ;-) But the backup is there for people who need it for warranty or selling purposes.
Click to expand...
Click to collapse
Aye, hear that, all contribution, great work.
I thought this was just about making a stripped version.
Missunderstandings happen
Noonski said:
Aye, hear that, all contribution, great work.
I thought this was just about making a stripped version.
Missunderstandings happen
Click to expand...
Click to collapse
That's a good idea though - stripping down their ROM.
But I'll stick with the cooked ROMs Too much bloat in stock ROMs.

XIP 20721 for Polaris.

XIP 20721 for Polaris.
SHAYDER said:
XIP 20721 for Polaris.
Click to expand...
Click to collapse
Call me stupid.... what's XIP?
XIP is kernel of OS.
You can see a version of XIP: Start->Settings->System->About
OS CE 5.2.20721 is current XIP.
To build ROM with new XIP you must: put "MSXIPKernel" folder to "SYS" folder. Then build you new ROM with new XIP.
For Example you can use Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)
http://forum.xda-developers.com/showthread.php?t=379559
for build ROM.
thanks....
20721 seems have Microsoft touch function
and 20721 XIP seems good , too.
now trying ^^
Brilliant cooked in and working fine
I am a total n00b so took a risk flashing but it went in and reports as 5.2.20721
Shayder,
no more need for your imgfs.bin and os.nb.payload like in the
XIP 20296 you posted?
Olioaglio
German ROM to dump available?
Anyone has a recent (202..) GERMAN Polaris ROM which
is able to recook (with dsm, rgu correct header etc)?
Unfortunately all ROMs I tried (Glass 0.4, UDK R7 GER, bepe) which
are available cannot be dumped and/or repackaged
It's a real pity! Seems the only way is using WWE for getting
the advantages of the new builds....
ANY HELP IS APPRECIATED!!!
Olioaglio
My imgfs.bin and os.nb.payload needed to replace any XIP on any ROM.(It is templates)
My Kichen.
http://rapidshare.com/files/140893825/Kichen.zip.html
To build ROM:
1) Put "OEM" and "SYS" folders to "Build" folder. (dont delete any existing files)
2) Run Rom.bat Then put "1" then "8" then "0"
3) When running "BuildOS" Put 'Play' button.
To Extract ROM:
1) Put "RUU_Signed.nbh" to "Extract" Folder
2) Run Rom.bat Then put "2"
3) When running "Package Tool", File->Open and put way "...\Extract\dump"
Olioaglio said:
Anyone has a recent (202..) GERMAN Polaris ROM which
is able to recook (with dsm, rgu correct header etc)?
Unfortunately all ROMs I tried (Glass 0.4, UDK R7 GER, bepe) which
are available cannot be dumped and/or repackaged
It's a real pity! Seems the only way is using WWE for getting
the advantages of the new builds....
ANY HELP IS APPRECIATED!!!
Olioaglio
Click to expand...
Click to collapse
I cant help you. ((Glass 0.4, UDK R7 GER, bepe) they Specially so have made) You must find needed files in internet.
Good work my friend. Indeed a good help.
kindly post the os.nb.payload as you have posted in the other XIP.
....regards
...c_shekhar
"imgfs.bin" and "os.nb.payload"
First off let me say thankyou for putting this package together.
I have cooked a rom and it boots up fine so I have started to customize it. Run into a few problems that I am hoping someone will be able to fix.
Here goes
I have used the package creator to insert some cabs into the installation. 3 of my cabs went in fine the rest create errors when building the registry.
So I am looking for a way to auto run the cabs. When the OS loads it seems to run a UC application from 2 places.
config_operator.txt
config_PT.txt
These point to cabs in the \windows directory and are installed upon first running of the rom. Brilliant I though. I copied the cabs i wanted into the OEMAPPS folder. Now when the rom is flashed my cabs are 100% copied OK into the windows folder as I can see them and run them.
So I edited the config_operator.txt
CAB: \WINDOWS\googlemaps.cab
CAB: \WINDOWS\coreplayer.cab
CAB: \WINDOWS\3iepatch.cab
CAB: \WINDOWS\opera1938.cab
CAB: \WINDOWS\advancedconfig.cab
CAB: \WINDOWS\keyboard.CAB
EXEC:\WINDOWS\cusTSK.exe \WINDOWS\Htc.tsk
XML: \WINDOWS\Menu_Operation.xml
CAB: \WINDOWS\PP_AKv33-Defau
Now when I re-flashed and the OS boots and I can see it in the install run my cabs and it looks like they are installing. The last one restorepie.cab then resets the device.
Upone reset my cabs have not been installed even though it looked like they were. Why is this?
Also is there a switch I can put to delete the cab after install? something like
CAB: \WINDOWS\opera1938.cab -d
Thanks in advance.
I dont know. I cant help you with this. But i can help you with errors when building the registry.
in "*.rgu"
Usually errors such:
@=""Windows\\cecmd.exe" "%1""
You must correct to
@="Windows\\cecmd.exe %1"
errors in ""
Good luck
SHAYDER said:
I dont know. I cant help you with this. But i can help you with errors when building the registry.
in "*.rgu"
Usually errors such:
@=""Windows\\cecmd.exe" "%1""
You must correct to
@="Windows\\cecmd.exe %1"
errors in ""
Good luck
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU!!!!
I went through the rgu for my opera package and did as you said. Now build perfectly no errors.
Time to get some more cooking done!!
Shayder,
Trying to use your kitchen but got stuck on how to change the automatically splash screen already setup in the BAT file? I was looking for NB file so I could just change the path but didn't understand those files named polarishtcrtproj.....
Thanks a lot and also for sharing this stuff!
SHAYDER said:
My imgfs.bin and os.nb.payload needed to replace any XIP on any ROM.(It is templates)
My Kichen.
http://rapidshare.com/files/140893825/Kichen.zip.html
To build ROM:
1) Put "OEM" and "SYS" folders to "Build" folder. (dont delete any existing files)
2) Run Rom.bat Then put "1" then "8" then "0"
3) When running "BuildOS" Put 'Play' button.
To Extract ROM:
1) Put "RUU_Signed.nbh" to "Extract" Folder
2) Run Rom.bat Then put "2"
3) When running "Package Tool", File->Open and put way "...\Extract\dump"
Click to expand...
Click to collapse
To change main splash screen you must:
1) run ROM.bat
2) put 3
3) in ".nb Image Tool" put "load..."
4) "save .nb" (save as "mainsplash.nb")
5) replace "mainsplash.nb" in "Build" folder to you "mainsplash.nb".
6) in ROM.bat put 1 then 8 then 0
Good luck
Thanks Man!
Cooked already but is showing CE OS 20721 and Build 20275
Things happens
SHAYDER said:
To change main splash screen you must:
1) run ROM.bat
2) put 3
3) in ".nb Image Tool" put "load..."
4) "save .nb" (save as "mainsplash.nb")
5) replace "mainsplash.nb" in "Build" folder to you "mainsplash.nb".
6) in ROM.bat put 1 then 8 then 0
Good luck
Click to expand...
Click to collapse
version of build Depends from "SYS" (not XIP)
XIP is CE OS 5.2.20721
Yep...agreed
I have used Niki's SYS but got stuck on splash screen all the time
SHAYDER said:
version of build Depends from "SYS" (not XIP)
XIP is CE OS 5.2.20721
Click to expand...
Click to collapse
I can help? Just whot do you do?

xda lls flashing problem

help help help. tried to flash my windows 2003 phone to wm6 using maupgrade tool. didnt work propely now phone has dim display saying serial at the top and v.2.03 at bottom! pc wont recognise it, whwt have i done wrong!!! rga
Dude, did you follow the steps in the wiki? or did you just flash it using the tool without setting it up first?
read wiki, tell u what happened i was upgrading using baupdate tool and took phone out of dock b4 it had finished! so now at stuck in bootloader mode( serial at top, and v2.07 bottom), so when try and flash again same as it doesnt detect old system, to overide with wm6 software. i cant figure out how to sort it now as cant get off bootloader. connects to pc with usb link, but cant see phone in pc because it as if phone is empty at the moments, connects as an unknown device. just trying to find out how i would flash the phone from the start now! rga
ive done it. the problem i was having was finding the replacement driver for usb connection when i wanted to use mmty and baupgrade tools. sweet now , using wm 6.5 now its classsssss! RGA
so the question is...... Did you figure it out already or not?
@markanthonypr
i guess he's happy now man. he will love flashing his BA from now on hehehe...
@reggaedave
Congrats man!
reggaedave said:
help help help. tried to flash my windows 2003 phone to wm6 using maupgrade tool. didnt work propely now phone has dim display saying serial at the top and v.2.03 at bottom! pc wont recognise it, whwt have i done wrong!!! rga
Click to expand...
Click to collapse
You seem to be new to the forums. Thank you for joining XDA-Developers.
Please take a minute to go over the Rules and Regulations of the forum.
Also, it seems that you are a Blue Angel owner, in which case I will encourage you to go over the BA forum regulations here
For questions, please use the search function in the site or simply Google for an answer. More than likely, your question has probably been answered before and the answer is floating around somewhere in the site. That being said, unless you are contributing to the site with either skins, roms, ports, new applications, programs, games, etc., please [highlight]do not[/highlight] open new threads. However, if you do have questions, you can post them either in the BA Q&A section or in the General Q&A section.
Thanks.
ha yeah im happy enuf! i dont know anything about these phones, ive been modding Sony Erricson phones for the past 2 years but this ones all new to me!.
ROM VERSION 6.50.21.WWE
ROM DATE 03/28/09
RADIO VERSION 1.06.00
PRTCL VERSION 1337.38
EXTROM
In another pack i downloaded, nothing to do with what i flashed, it had a file labelled EXTROM, with loads of stuff in it, could this be put on my phone, bear in mind i know almost nothing at the moment? cheers off work 4 a week reggaedave!
the "file" extrom is an archive, which first needs to be unpacked to become the folder extrom. in there you find the following things:
1. Autorun.exe
2. CFG.txt
3. custom.bmp
4. a lot of cab files
there are 3 basic ways to handle the extrom after flashing:
1. you copy the cab files you want to an sd card and install them one by one
pro: fast if you know you don't need much or want to install to ramdisk or storage card
con: slow, when you install a lot of programs that go to the phone memory anyway and you plan to install the same progs every time you hard reset or flash a new rom
2. you customize you extrom by deleting cabs, adding new ones (you have to list them in cfg.txt)
pro: one folder to copy, installation process automated
con: all progs go to phone memory, you need to customize the cfg first
3. you take the extrom as it is
now for the explanation:
the extrom is a folder containing basic system programs that are not included in the rom, so their installation is optional. i don't know whether you worked with your device before, bust most names should ring a bell, if not, refer to the wiki or google the names for detailed descriptions.
what you need to do to install the extrom as it is: copy the folder extrom to an sd card and insert it after hard reset (make sure the cfg.txt lists all the cabs in the folder), a window will appear that tells you that the automated customization begins, you wait, after the next (automatic) soft-reset you have the programs on your device.
(mmh, probably that last part was the answer to your question, should have started with that. )
greetz
Chef_Tony
ok ill have a go now, thanks for the advice! cheers..RGA
Chef_Tony said:
the "file" extrom is an archive, which first needs to be unpacked to become the folder extrom. in there you find the following things:
1. Autorun.exe
2. CFG.txt
3. custom.bmp
4. a lot of cab files
there are 3 basic ways to handle the extrom after flashing:
1. you copy the cab files you want to an sd card and install them one by one
pro: fast if you know you don't need much or want to install to ramdisk or storage card
con: slow, when you install a lot of programs that go to the phone memory anyway and you plan to install the same progs every time you hard reset or flash a new rom
2. you customize you extrom by deleting cabs, adding new ones (you have to list them in cfg.txt)
pro: one folder to copy, installation process automated
con: all progs go to phone memory, you need to customize the cfg first
3. you take the extrom as it is
now for the explanation:
the extrom is a folder containing basic system programs that are not included in the rom, so their installation is optional. i don't know whether you worked with your device before, bust most names should ring a bell, if not, refer to the wiki or google the names for detailed descriptions.
what you need to do to install the extrom as it is: copy the folder extrom to an sd card and insert it after hard reset (make sure the cfg.txt lists all the cabs in the folder), a window will appear that tells you that the automated customization begins, you wait, after the next (automatic) soft-reset you have the programs on your device.
(mmh, probably that last part was the answer to your question, should have started with that. )
greetz
Chef_Tony
Click to expand...
Click to collapse
Excellent description Chef Tony! It should be added to the Wiki/Wizard page as there is no clear description of it there, and I had to search this forum for quite a while to get a definitive answer as to what an extrom was!
okey dokey failed! ha. file extrom contains AUTORUN, CUSTOM, CFG, and many CAB files. Placed it on memory stick. Tried to open cabs one by one none worked, said was unsuccessful. One thing is that the CFG file is blank, do i need to be writing text in there of some sort? This is harder than a sony erricsson phone! what and how do people use the display a deskbar on the main screen, ive disabled the windows default set of icons, is there a better external app to use for it? answer whatever you can i know nothing about ppcz
reggaedave said:
okey dokey failed! ha. file extrom contains AUTORUN, CUSTOM, CFG, and many CAB files. Placed it on memory stick. Tried to open cabs one by one none worked, said was unsuccessful. One thing is that the CFG file is blank, do i need to be writing text in there of some sort? This is harder than a sony erricsson phone! what and how do people use the display a deskbar on the main screen, ive disabled the windows default set of icons, is there a better external app to use for it? answer whatever you can i know nothing about ppcz
Click to expand...
Click to collapse
It sounds to me that you need to go back to suggestions of reading the wiki my friend. You need to downgrade to wm2003, and follow instructions step by step. This is where to start... Choose the proper answers and it will walk you through.
and if your cfg.txt file is really empty (which i don't understand, as many people downloaded the package and had it working), here is a sample extrom, that i wrote for myself:
LOCK:Enabled
SHOW:\Storage Card\EXTROM\Custom.bmp
CAB: \Storage Card\EXTROM\ADC.cab
CAB: \Storage Card\EXTROM\A2DPFix.cab
CAB: \Storage Card\EXTROM\Extrom_version.CAB
CAB: \Storage Card\EXTROM\GoogleMaps.cab
CAB: \Storage Card\EXTROM\HTC Large Title Bar.cab
CAB: \Storage Card\EXTROM\HTC_Task_Manager_2.1_34837.5.cab
CAB: \Storage Card\EXTROM\HTC_Touch_Calculator_Skin.cab
CAB: \Storage Card\EXTROM\HTC_WMP_Touch_Skin.cab
CAB: \Storage Card\EXTROM\Office_6.1.21202.cab
CAB: \Storage Card\EXTROM\PHM Regedit.cab
CAB: \Storage Card\EXTROM\PIE8_Flash3.1_21202.cab
CAB: \Storage Card\EXTROM\pocketrar.cab
CAB: \Storage Card\EXTROM\psShutXP.cab
CAB: \Storage Card\EXTROM\RDM_21202.CAB
CAB: \Storage Card\EXTROM\sipchange.cab
CAB: \Storage Card\EXTROM\skybox.CAB
CAB: \Storage Card\EXTROM\skybox.CAB
CAB: \Storage Card\EXTROM\SMS Delivery Receipt Fix.cab
CAB: \Storage Card\EXTROM\WMWidgets.cab
CAB: \Storage Card\EXTROM\youtubeplay.cab
LOCKisabled
HIDE:Enabled
EXEC: \Windows\DelCDetect.exe
HIDEisabled
RST: Reset
as you can see it is just some basic commands and a list of cab files, so you can do it yourself.
Oh, and where the smileys are, there of course has to be ":" "D" but as they stand without space, they make fun of the HIDE function should have posted it is code
@reggaedave,
How much free storage space do you have after a clean flash?
Everybody more cleverer than me im looking into extrom!
Storage
total: 43.26 MB
in use: 10.80 MB
free: 32.45 MB
program
total: 90.93
in use: 29.86
free: 61.07.
Learning the basics a bit now after getting bollocked! ... silly question but here goes, if i wanted to replaced png in the windows folder, should i just overwrite them with my own pngs, with same dimensions and names, is that how people change the interface graphics? apprentice ppc modder!....
Also trying to get my head around themegen program, because got loads of stock gfx to use so hopefully should be able to create some fantastic themes soon! over and out! Rga
reggaedave said:
Everybody more cleverer than me im looking into extrom!
Storage
total: 43.26 MB
in use: 10.80 MB
free: 32.45 MB
program
total: 90.93
in use: 29.86
free: 61.07.
Learning the basics a bit now after getting bollocked! ... silly question but here goes, if i wanted to replaced png in the windows folder, should i just overwrite them with my own pngs, with same dimensions and names, is that how people change the interface graphics? apprentice ppc modder!....
Also trying to get my head around themegen program, because got loads of stock gfx to use so hopefully should be able to create some fantastic themes soon! over and out! Rga
Click to expand...
Click to collapse
That is exactly what I thought! You should seriously taking a look at the Wizard in the Wiki that markanthonypr pointed to you. I'll put it in simple terms... you did not follow the process completely (didn't unlocked and resized the storage). The reason why you cannot install your cabs for your ExtRom is simply because the old ExtRom still exists in your phone. Also, since all of these files are still there taking up space, instead of having about 60 MB of storage, you have roughly 43 MB. Long story short, you have to start from scratch (and I do mean from scratch... go back to stock 2003). Please follow the Wizard in the Wiki [highlight]step by step by every single step.[/highlight]
After you get an OS installed properly, you can continue modding the phone to your liking, but at this point, it is meaningless since you will have to hard reset your device a few more times.
ERROR!
Oh lord... ok, ive seen a lot of info since i did my first flash, ( seen the formating storage info), ill have a look and see if i can sort it.Originally i was stuffed because i got to the point that my phone was stuck in bootloader mode and paniced so thats why a rushed flash happened, and because it was about 3 in the morning aswell. Ill follow link, when i did my flash i followed a post actually in a thread, not from wiki, suppose that didnt help me much.Ill try again from scratch!
Wowzer what a night. Not done it yet. Had a total nightmare. Flashed my phone back to WM6 again in the end. Followed the instructions but couldnt pull it off, have to have another go.
Got as far as getting Downgrade to wm2003 pack, put the nk.nbf file in folder that had been extracted, but couldnt get maupgrade tool to recognise my phone to reflash it. So phone was stuck in bootloader so flashed it again using maupgrade with the WM6 files in and it come up straight away, so just flashed it to get back to beginning.
Will have to make my own notes and do it myself without having to search pages, also b4 i couldnt get mtty app to get into phone, wouldnt let me type commands so that was doing my head in. Couldnt find any info in any wiki wizzard link about commands for mtty! anyhows im knackered. Work in progress. Am i right in thinking that i need to flash my phone back to a wm2003 rom, do the nessasary formatting of storage, then upgrade to a version of wm6?? is that what i should be looking at? Knackered No time for any REGGAE Dave!
Yes!
Yep Dave, that is correct.
You need to flash back to 2003, install the unlock and unhide cabs as per the Wizard and execute them in the correct order.
Follow all steps! Do not skip anything and you should be ok.
After that continue on through the Wizard instructions to flash your new rom.
Best of luck.

[SOLVED] Include .cabs in ROM?

I'm trying to include a newer Google Maps and a few other applications and converted the .cab installers to EXT in osKitchen. They get included in the list in EXT Packages and I select all of them but still I cant find them when I have flashed my ROM to my device.
Am I supposed to do something more?
Double check that they are in the windows folder. All you should have to do is check the package.
djr83 said:
I'm trying to include a newer Google Maps and a few other applications and converted the .cab installers to EXT in osKitchen. They get included in the list in EXT Packages and I select all of them but still I cant find them when I have flashed my ROM to my device.
Am I supposed to do something more?
Click to expand...
Click to collapse
If your ROM is not in english you have to edit the app.dat to use the correct start menu folder.
look into or show us your buildlog...
airxtreme said:
If your ROM is not in english you have to edit the app.dat to use the correct start menu folder.
Click to expand...
Click to collapse
Thanks! Havent tried the new rom yet but the paths in app.dat was wrong.
But I do have to change the path to the programs folder too, I guess?
When I check the path in file explorer it says \Program and in app.dat it says \Program Files.
If you use cab 2 oem and oem 2 ext the app.dat is automatic created with the correct path.
So if you use a WWE package it will be 'Program files' and for the shortcut 'start menu'. If you use another language (Dutch for example) 'program files' has another name 'programma bestanden' and 'start menu' becomes 'startmenu' in Dutch.
So you need to correct that path according to the language you use.
You can use initflashfiles.dat as an example for every language you use.
djr83 said:
Thanks! Havent tried the new rom yet but the paths in app.dat was wrong.
But I do have to change the path to the programs folder too, I guess?
When I check the path in file explorer it says \Program and in app.dat it says \Program Files.
Click to expand...
Click to collapse
Laurentius26 said:
If you use cab 2 oem and oem 2 ext the app.dat is automatic created with the correct path.
So if you use a WWE package it will be 'Program files' and for the shortcut 'start menu'. If you use another language (Dutch for example) 'program files' has another name 'programma bestanden' and 'start menu' becomes 'startmenu' in Dutch.
So you need to correct that path according to the language you use.
You can use initflashfiles.dat as an example for every language you use.
Click to expand...
Click to collapse
I'm using osKitchen Zero 1.31 beta1 and cab 2 oem doesnt seem to exist anymore. I think it was in my old kitchen, osKitchen 1.25 but I dont use that anymore.
One of my cabs is actually a today screen plugin. How do I choose what plugins which should be selected from start?
Hmm the program files gets into the correct folder and a link is created in the start menu, but the link doesnt start the program. I guess it's still pointing to the wrong path.
How do I fix this?
djr83 said:
I'm using osKitchen Zero 1.31 beta1 and cab 2 oem doesnt seem to exist anymore. I think it was in my old kitchen, osKitchen 1.25 but I dont use that anymore.
One of my cabs is actually a today screen plugin. How do I choose what plugins which should be selected from start?
Click to expand...
Click to collapse
Everything is in the universal package converter now
djr83 said:
Hmm the program files gets into the correct folder and a link is created in the start menu, but the link doesnt start the program. I guess it's still pointing to the wrong path.
How do I fix this?
Click to expand...
Click to collapse
Just edit the shortcut; total commander works well.
Farmer Ted said:
Just edit the shortcut; total commander works well.
Click to expand...
Click to collapse
Cant I change that in the ROM? I dont want to have to change a lot after flashing.
I did a quick search for you:
http://forum.xda-developers.com/showthread.php?t=510806&highlight=cab2oem
Today items you enable/disabled like the sample of registry below.
1 is enabled and 0 is disabled.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\HTC Sense]
"Enabled"=dword:1
djr83 said:
I'm using osKitchen Zero 1.31 beta1 and cab 2 oem doesnt seem to exist anymore. I think it was in my old kitchen, osKitchen 1.25 but I dont use that anymore.
One of my cabs is actually a today screen plugin. How do I choose what plugins which should be selected from start?
Click to expand...
Click to collapse
{
"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"
}
Laurentius26 said:
Today items you enable/disabled like the sample of registry below.
1 is enabled and 0 is disabled.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\HTC Sense]
"Enabled"=dword:1
Click to expand...
Click to collapse
Thanks! But the plugin doesnt even show up in plugin list when I pre-install it in the ROM. The plugin is TodayAgenda. Do I need to do something more when adding today screen plugins?
djr83 said:
Cant I change that in the ROM? I dont want to have to change a lot after flashing.
Click to expand...
Click to collapse
Just edit the shortcut and then swap the new one into your package for the bad one. Although this whole topic is confusing. Are you trying to install cabs during customization, or are you trying to make actual packages from cabs? If it's the former, then you'll need to edit the .cab file to fix the shortcuts (if they are the problem).
Farmer Ted said:
Just edit the shortcut and then swap the new one into your package for the bad one. Although this whole topic is confusing. Are you trying to install cabs during customization, or are you trying to make actual packages from cabs? If it's the former, then you'll need to edit the .cab file to fix the shortcuts (if they are the problem).
Click to expand...
Click to collapse
I want to be able to select which programs I want to include in the ROM. How it gets included doesnt matter (I think?).
What's the difference between installing them during customization and making packages?
I found the bad shortcuts now, thanks, so I guess that problem is solved now. But please tell me the difference between customization installing and packages. I want to do it the correct way
There are different ways to include apps into a rom. Installing a cab during customization isn't a whole lot different then just installing a cab normally. There's nothing really special about it, except that the cab file is stored in rom. This could be a good thing or a bad thing, depending on how you look at it. You don't get any of the benefits of cooking an app into rom when you use cab files.
Creating a package means extracting the files (and reg keys, if there are any) from the cab file and then cooking them directly into the rom. In many cases, you can re-locate the application directly into the \windows folder (from \program files), and this saves space and shortens the time for first boot. You may also be able to convert some of the files to modules, which can increase performance (mainly, the apps boot up faster), but it doesn't always work. Modules can also save a bit of ram by loading code into the page pool. As an example, you can create a package with TCPMP (core player) that loads all of the files directly into the rom. This is much better than having the files in their own folder in \program files\tcpmp, because you don't end up having duplicate files in \windows (if you use an app.dat to copy the files into the program file directory) or one big cab file sitting in \windows. It saves on storage. Also, some of the .dll's and the .exe can be made into modules.
On the other hand, some apps just don't work if the files aren't placed in the proper directory. I've had a bugger of a time getting the new resco keyboard to work properly. Most of the time, you can just move files and sub-folders from program files straight into \windows, but it doesn't work with resco keyboard. The bloody skin files have to be located in \program files\resco keyboard pro\skins (the same goes for the language and sound files). It's not a big deal, but I could save a bit of space if I could locate some of the files in \windows. I get these files into the program files directory by unzipping a zip file with a mortscript during customization. Zips are easier to edit than cabs, and install faster, so that's what I prefer to use. You also don't have to bother with uninstall info (I always seem to leave that crap in when I pack a cab, even though it's pretty much useless to me).
Customization is the step after the screen alignment. It's basically the time when you pretty up your rom, and put in the final touches so that when the phone is fully booted up, it's just the way you want it.
Your post is just kind of unclear. It sounds like you're just trying to install cabs during customization, but some people are telling you how to extract cabs to make EXT's. I'm not really sure what you're asking.
Farmer Ted said:
There are different ways to include apps into a rom. Installing a cab during customization isn't a whole lot different then just installing a cab normally. There's nothing really special about it, except that the cab file is stored in rom. This could be a good thing or a bad thing, depending on how you look at it. You don't get any of the benefits of cooking an app into rom when you use cab files.
Creating a package means extracting the files (and reg keys, if there are any) from the cab file and then cooking them directly into the rom. In many cases, you can re-locate the application directly into the \windows folder (from \program files), and this saves space and shortens the time for first boot. You may also be able to convert some of the files to modules, which can increase performance (mainly, the apps boot up faster), but it doesn't always work. Modules can also save a bit of ram by loading code into the page pool. As an example, you can create a package with TCPMP (core player) that loads all of the files directly into the rom. This is much better than having the files in their own folder in \program files\tcpmp, because you don't end up having duplicate files in \windows (if you use an app.dat to copy the files into the program file directory) or one big cab file sitting in \windows. It saves on storage. Also, some of the .dll's and the .exe can be made into modules.
On the other hand, some apps just don't work if the files aren't placed in the proper directory. I've had a bugger of a time getting the new resco keyboard to work properly. Most of the time, you can just move files and sub-folders from program files straight into \windows, but it doesn't work with resco keyboard. The bloody skin files have to be located in \program files\resco keyboard pro\skins (the same goes for the language and sound files). It's not a big deal, but I could save a bit of space if I could locate some of the files in \windows. I get these files into the program files directory by unzipping a zip file with a mortscript during customization. Zips are easier to edit than cabs, and install faster, so that's what I prefer to use. You also don't have to bother with uninstall info (I always seem to leave that crap in when I pack a cab, even though it's pretty much useless to me).
Customization is the step after the screen alignment. It's basically the time when you pretty up your rom, and put in the final touches so that when the phone is fully booted up, it's just the way you want it.
Your post is just kind of unclear. It sounds like you're just trying to install cabs during customization, but some people are telling you how to extract cabs to make EXT's. I'm not really sure what you're asking.
Click to expand...
Click to collapse
What I'm doing now is definitly makeing EXT's. But that doesnt mean I'm sure that it is what I want to do. I just want to include some programs in the ROM from the beginning and EXT's seems like a good way to go.
But if I want to install cabs during customization, how do I do that?
You create an EXT:
Sample:
Yourpackage\
Yourpackage\files\your cab
And you add a line to config.txt so it will be autoinstalled during device setup.
A sample of that line:
CAB: \Windows\your_app.cab
djr83 said:
What I'm doing now is definitly makeing EXT's. But that doesnt mean I'm sure that it is what I want to do. I just want to include some programs in the ROM from the beginning and EXT's seems like a good way to go.
But if I want to install cabs during customization, how do I do that?
Click to expand...
Click to collapse
Laurentius26 said:
You create an EXT:
Sample:
Yourpackage\
Yourpackage\files\your cab
And you add a line to config.txt so it will be autoinstalled during device setup.
A sample of that line:
CAB: \Windows\your_app.cab
Click to expand...
Click to collapse
Where should this config.txt be? Yourpackage\config.txt?
And can I add an app.reg to this EXT so I get some settings installed too? Will these settings be applied before or after the cab-install?

Categories

Resources