New Roms - Palm Treo 750 ROM Development

Hey Guys, just wondering what the status is on any new Rom for our treos.

Well.. My laptop is cluttered with hacked up ROMs. I haven't really sorted out a good direction to take as far as additions, subtractions etc. The extended ROM took me some time to figure out, but here's what I know so far.
There are two file in extended ROM - one is the carrier database which holds configs for the data settings (carrierdb) The other file is a compressed package of customizations (cappackage). Both have the extension "pxp" but are standard zip files.
Inside the package file are various cabs and xml files which write config data to the registry via the provisioning api. There is a primary xml config file which directs the installation of everything in the package. Autorun and config.txt are not used on the Treo.
There is no extended ROM .nb reader/writer that works on the Treo extended ROMs. However you can use the Hermes extended ROM creator to build an nb, and then using a hex editor go in and lop off everything beyond a particular address (don't have the address in front of me at the moment). This is because the extended ROM size on the Treo is smaller than on the Hermes.
What I'll probably do real soon is create a OS-only ROM based on the Aussie release and include an empty extended ROM which can be unlocked and used for storage. Once I upload the various extended ROMs folks can pick and choose what they want from them.
manfly9884 said:
Hey Guys, just wondering what the status is on any new Rom for our treos.
Click to expand...
Click to collapse

summiter said:
Well.. My laptop is cluttered with hacked up ROMs. I haven't really sorted out a good direction to take as far as additions, subtractions etc. The extended ROM took me some time to figure out, but here's what I know so far.
There are two file in extended ROM - one is the carrier database which holds configs for the data settings (carrierdb) The other file is a compressed package of customizations (cappackage). Both have the extension "pxp" but are standard zip files.
Inside the package file are various cabs and xml files which write config data to the registry via the provisioning api. There is a primary xml config file which directs the installation of everything in the package. Autorun and config.txt are not used on the Treo.
There is no extended ROM .nb reader/writer that works on the Treo extended ROMs. However you can use the Hermes extended ROM creator to build an nb, and then using a hex editor go in and lop off everything beyond a particular address (don't have the address in front of me at the moment). This is because the extended ROM size on the Treo is smaller than on the Hermes.
What I'll probably do real soon is create a OS-only ROM based on the Aussie release and include an empty extended ROM which can be unlocked and used for storage. Once I upload the various extended ROMs folks can pick and choose what they want from them.
Click to expand...
Click to collapse
Thanks for your quick response. If I can help you in any way, please let me know.

Related

Post Exteneded Rom Links Here.

We have lost the exteneded roms again.
This is the 2nd time that I know of.
I think this has to do with the fact that they were not linked to post thus unkonw files get killed. I read that some were when I first came here.
I have most of them and will start uploading them again, linking them to a post.
Anybody have a better idea or know why they have gone?
Not sure whether they've been deleted or not, unless you have been reposting. They are under BlueAngel_Roms instead of Extended_Roms. Things seem to keep getting moved.
And what are they doing there ?
Sure I have been uploading to ExtenedRoms for over an hour now.
I will move the buggers!
Rename The Folder Exteneded_Roms
Clean up the file names
Gee I love house work thought I was would be cooking in the Rom Kitchen, but no.
We are going to have to post the links as they got killed once before.
Thought you were out.
Can you belive this!
Got a folder name that says "Dont touch MDAIIIUser Uploading" and we have dowloades.
You around need so help.
ok done
cleaned up the Exteneded_Roms
Will post in the morning.
We need to take these apart and find what version they are then rename them.
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/IIs Asia WWE Ext ROM.zip
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/Seimens_SX66_Ext_ROM_ENG.zip
ftp://xda:[email protected]_MDAIII_Extended_Rom_Inc_DeviceInfo.zip
Do you need some assistance with the Excel sheet for ROM Versions and contained cab files?
Is there a neater way of structuring the ftp server directories? Is there any way of setting folder permissions on the server for read/write only and not alter/delete?
Bebbo
Do I need help in the Exteneded Rom Kitchen. Does the .... (ok no bad jokes)
Sure do BIG Time!!! Its not my kitchen, I just work there!
The Idea of the Kitchen is not realy to find out what version number Orange Rom A has for an application but to see if Orange's Rom A has application / Patches that are better than our base.
The Sheet just is a list of the files which go:
Base (I-mate) + Rom A + Rom B = Extended Rom Kitchen (ERK) Rom
My end goal is to generate a ERK Rom Version which is as upto date as possible.
And have this info on wiki so we dont need to hunt for it.
How far am I, Well The UK orange rom has been looked at but info not posted in the kitchen.
( I think RTP worked on that but I am not sure as I was haveing PMs with few people about that rom. )
We have the 3 roms above that need to be looked and info posted in the Kitchen and added to the Excel Sheet.
The Excel Sheet needs to be made to look nice so the rest of us can undersatand it.
We need to check against the "List of know Blue angels" to see what rom is missing and see if we can find it.
Oh yes and its friday, I get to pick my kids as its "The 3rd weekend of every month" and as my ex-wife has got a date, thus By 12:00.
Chances of me doing much till monday are ZERO.
So you want a job, pay is s**t, hours are bad, it can get hot in the kitchen when there is a fire and you lose all your stuff.
You need to understand Roms, read cab files, use your brain and most of all admit to the fact that you don't know everything and thus ask.
I am looking for Pastry Chef as well. One that can write applications.
Is there any way of setting folder permissions on the server for read/write only and not alter/delete?
Click to expand...
Click to collapse
Given that at the moment we are all the user XDA, I would say no.
What we need is a "BA_Admin" that revokes the rights of XDA to Read only, then we just get into the next problem, the person that posted (XDA) can't update it, so he needs to be BA_Admin...
The FTP site is a public place and like Toilets some people just can't pee in the Pot like the rest of us and sonebody has to clean up the mess.
Is there a neater way of structuring the ftp server directories?
Click to expand...
Click to collapse
Got some ideas, then share them with us.
Will have a look at dir structure but seems reasonable to me at the moment (Though Extended is the correct spelling ). Will use my WinCE CAB Manager to see what if anything is different on rom's you haven't had chance to view yet and generally assist where I can.
I will have a look at the orange rom as well, time permitting.
Would it be better to extract the .nbf files to sub dirs under the Extended_ROMS dir and have similar structure for radio and CE ROM?
ie ->
BlueAngel/Extended_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/ms_.nbf
(With cabs extracted as well under a cabs sub dir?)
BlueAngel/CE_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/nk.nbf
BlueAngel/Radio_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/radio_.nbf
Or leave as is and use the kitchen with a CAB's dir under it with all known versions of cab files so we can select the most appropriate ones?
I've posted the document on the Orange 1.12.139 ROM into the Kitchen. It's fairly large since there is so much in the Orange ROM.
Here's a link:
ftp://xda:[email protected]_1_22/Docs/Orange_WWE_1.12.139_ExtROM.doc
Unfortunately nothing really new though (Wish I had known you were doing this rom - just wasted 2 hours!).
I haven't looked at the WModem.exe update yet - any ideas what this is for?
Who keeps moving files in the BlueAngel section of the FTP server? Makes life difficult having to keep searching each time. Please let us all know what you are trying to achieve as it keeps breaking links on other web pages!
Running it comes up with this text:
The utility will simulate this device as a wireless modem, and let your PC/Notebook be connected to network wirelessly.
Before you press the 'Start' button, please make sure you have connected the device to your PC/Notebook by serial or IrDA connection and disabled the Activesync.
When the wireless modem is activated you will not be able to receive any voice calls.
Click to expand...
Click to collapse
It then gives options for Serial, IrDA, USB and Bluetooth. Start, Stop and View Log buttons. Plus connection status LEDs - Connection, Send Data and Receive Data.
I've never tried it. I tend to use something more direct for dialup from my laptop.
OK guys!!!
I don't know what your naming system is but I've uploaded the O2 UK EXT ROM and I've called it "O2_UK_XDAIIs_Ext_ROM_112178_WWE.zip". This one is the original from my device.
Regards,
Dom
Ext_ROM password??
MDAIIIUser said:
ok done
cleaned up the Exteneded_Roms
Will post in the morning.
We need to take these apart and find what version they are then rename them.
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/IIs Asia WWE Ext ROM.zip
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/Seimens_SX66_Ext_ROM_ENG.zip
ftp://xda:[email protected]_MDAIII_Extended_Rom_Inc_DeviceInfo.zip
Click to expand...
Click to collapse
Any known pw's for those .nbf files? I tried Rom editor but couldn't recognize the pw's
Re: Ext_ROM password??
Cyber-mate said:
Any known pw's for those .nbf files? I tried Rom editor but couldn't recognize the pw's
Click to expand...
Click to collapse
They aren't .nbf files???????? They are zipped up (rar'd up) cab files extracted from the extended roms.
+*+*+*+ FOR INFO +*+*+*+
The xda3nbftool has an extra command line option of -t which attempts to discover the xor key used to encrypt the .nbf files. This seems to work well for all files except the radio_.nbf file which causes it problems. Try it on roms that you are having problems with to see if it is the correct key. You can check the resulting .nba file with a hex editor to ensure the PH20B and other data is shown at the beginning of the .nba file.
+*+*+*+*+*+*+*+*+*+*+*+
I have pulled the above ext roms apart and the version numbers are as follows:
IIs Asia WWE Ext ROM.zip = Version "1.12.925 WWE"
Seimens_SX66_Ext_ROM_ENG.zip = Version "1.20.115 WWE"
T-Mobile_MDAIII_Extended_Rom_Inc_DeviceInfo.zip = Version "1.06.117 WWE"
Files renamed appropriately so any links will now be broken (plus the fact that some kindly person has renamed the Extended ROM directory to its correct spelling!)

XDA IIs ROM Cooking

Hi,
I've read through the WiKi on the extended ROM on the blue angel, and i think i have a basic understanding of how it works now.
I have several CAB files (Microsoft .NET framework CAB files, and some of my own). Would i be right in saying that to put these into my Extened ROM all i have to do is...
- Unlock The Extended ROM folder on my blue angel
- Paste in the CAB files
- Edit the config file to add my CAB files to the execute list.
- ReLock Extended ROM
Would that work? If i were to create this extended ROM arranngement would it be possible to install it on several XDA IIs so that they would always automatically reinstall my program upon a hard reset? I was also wondering if it would be possible to customise things like the splash screen, menus, and hardware button settings within the Extended ROM?
I hope that wasnt to much of a long question!! Any ideas or thoughts would be great!
Many Thanks
James.
but also remember there is a limitation on the rom max of file size is 16MB.
happy cooking

Extract files from Extended rom (on the PC)

I've extracted the nk.nbf file from O2's upgrade Rom, and have then extracted the following files:
80040000-OS_0.nb
9b000000-Extension.nb
96000000-GSM_0.nb
91000000-SPL_1.nb
etc...
Now i know that the cab files i want exist within the 9b000000-Extension.nb file (as i am guessing that this is the Extended Rom). But i can't figure out how to extract the cab files (or all the files) from within in it.
I've searched around, and it's helped me get this far, but i can't seem to figure out how to get past this point. Can anyone tell me how to do this on my PC.
Many thanks.
I know someone in here can give me a quick answer to this one. All i want to do is get some cab files out of an O2 extended rom file on my computer (i can't use the extended rom unlocker on my pocket pc because i am currently using the crossbow OS, which doesn't include the O2 extended rom).
Thanks for any help.
If you are using orwell's wm6 your extended rom is probably still on your phone unless you wiped it off.
look for a software called winimage & load the extrom.nb file then u will see the contents.

Modded Cappackage.pxp Files

So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
EDITED 12-30-2007: Note - this altered cappackage.pxp file is based off the "leaked" ATT WM6 ROM.
abs99 said:
So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
Click to expand...
Click to collapse
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?
john_99 said:
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?
Click to expand...
Click to collapse
I honestly do not know. Sorry. You might ask Olipro as he seems to be very knowledgeable.
abs99, what tool did you use to repackage your PXP file. I've tried several archive tools to .ZIP and rename, but no joy. I've looked, but can't find any info on PXP file creation. Surely, I'm missing something simple here.
TIA
I found that "winrar" can handle the files without a problem. I had also noticed that the date stamps were the same for all the files in the original package, so I also use a tool called "stamp it" to set all the dates on all the files in the new package to the same original date.
thanks. I found that 7-zip is working too.
Now, the next step, I'm trying to mod the capdata.xml file and for whatever reason the device will not recognize it after my mods.
Here's my version of an ATT config file:
Code:
<?xml version="1.0" encoding="utf-8" ?>
- <Varnish xmlns="http://www.ephox.com/product/editliveforxml/document/Untitled20062026011007629">
<Version />
<Notes />
<UpgradePath>always|</UpgradePath>
- <PolA>
- <Certificates>
<File>CingularCert.prov.xml</File>
</Certificates>
- <Certificates>
<File>Class3_PCA_G2_v2.xml</File>
</Certificates>
- <Certificates>
<File>entrust_gssl_ca.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA1024RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA2048RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>VeriSign_C3_PCA_G3v2.prov.xml</File>
</Certificates>
- <Ringtone>
<File>AT&T Tone.wav</File>
</Ringtone>
- <ProvXML>
<File>ATT_Settings.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>MSFPHeartbeat.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>ResetRequired.prov.xml</File>
</ProvXML>
- <InstallApp>
<File>WindowsLive.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Theme.CAB</File>
</InstallApp>
- <InstallApp>
<File>ProxyManager.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Content.cab</File>
</InstallApp>
- <ExtractZip>
<From>DevState.zip</From>
<To>\Windows</To>
</ExtractZip>
</PolA>
- <Welcome>
<WaitImage>E_PolishImage.bmp</WaitImage>
</Welcome>
- <Sweatshop>
<AccountName>GEN</AccountName>
<VarnishName>ENG</VarnishName>
<BuildName>005</BuildName>
<User>[email protected]</User>
<Environment>Sweatshop QA Staging</Environment>
<CoreVersion>1.9.9</CoreVersion>
<Treo750Version>3.0.0</Treo750Version>
<DateStamp>Wed Aug 22 6:10:15 PDT 2007</DateStamp>
</Sweatshop>
</Varnish>
Any thoughts? This is just a basic mod and plan to get more detailed configs in there once I figure out what I'm doing wrong.
TIA
The issue with this file may be that editor you are using is adding "white space". I found that some editors caused this to occur. I ended up the file in notepad to avoid the problem as it was a real mess to deal with any other way. You should open the original unedited file and your new edited file in notepad and compare both. For whatever reason, the OS does not like to deal with a properly formatted .xml file!
Thanks mate, the white space and file size were the culprit. Was trying to cheat and use MS xmlnotepad - very easy to use, but it added the whitespace as it made it pretty to look at. I also was trying to cram too much into my archive; the extracted archives need to fit in the 8.4mb along with the archive itself.
Attached is a custom CapPackage.PXP with the following (based from ATT 2.25 ROW, CapPackage.PXP):
ATT Theme
Regional Settings: US, - 5 EST
ExtROM mount and rename
Custom ringtone
Custom Sounds Settings
Delete poutlook.lnk from startup
Set Hello to ATT
Disable CAB security policy
Removed all ATT applications (CV, real, win live, etc)
TODO: Incorporate RegHacks of additional settings customization and tweaks (lots of typing...), right now I install and merge the apps I want after initial setup completes.
Cheers
HOW TO
***always a good idea to backup existing files before attempting any modification***
1. mount your extended rom (search for the cabs and instructions on this site)
2. copy the CapPackage.PXP from ExtendedROM\Partition to your PC
3. extract the contents to a folder named CapPackage on your PC (any ZIP compliant archive tool will do)
4. remove/add the *signed* cab files your desire (unsigned cab files simply get passed over)
5. open capdata.xml in epcEDIT or notepad.
6. add/remove the configuration information as desired - this is where some trial and error comes in trying to determine what commands control what function.
7. ZIP (no other archive format seems to work) the CapPackage folder to CapPackage.PXP (or rename .zip to .pxp).
8. copy to ExtendedROM and hardreset.
TODO:
-Hope to be able to post a list of commands for the XML to enable configure of most if not all device "settings"
-Hope to figure out a way to get unsigned cabs to install (present workaround is a zip extract and registry commands if the app isn't too complex (e.g. lots and lots of typing required)
--Not sure yet if reg hack setting "HKLM\Security\Policies\Policies' valuename '0000101a' to dword:1" will resolve this during initial setup
Okay, after getting my questions about how this all works and saves the space on the phone, I took the plunge and upgraded from 2.23ROW to 2.25ATT. Went smooth as butter, and I have a "decrapified" phone with the official, supported ATT release (just in case I have any problems and need support).
Of course, being a hacker, now I'm totally intrigued by this cappackage customization, and want to play with it myself. So, Tim et. al., two questions:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.
microsoft word has a wonderful xml file editor. rather than try and keep everything straight in that jumbled up mess you get out of notepad or some other editor, word indents all the xml, and makes it look like it should. it was a snap to edit. I used Winrar and opened the PXP file. I never extracted the contents. Just the capdata file. I edited it, and then put the edited version back into winrar. using winrar I deleted the files I didn't want. saved the archive and moved it back to the device.
dwallersv said:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.
Click to expand...
Click to collapse
1. The XML will bypass anything it can't actually do.
2. I have tried it both ways and feel like I've had no issues, but I have seen some reports of strange behavior without it. I currently have it in my ExtROM since I hard reset my device often as I test apps and config settings. If you don't hard reset very often then once the device is hard reset you may delete and gain an additional 1.45mb.
The thing I intend to work on next is creating a provisioning XML to call an external XML (outside of the cappackage). I'm hoping this way I will be able to strip even more out of the cappackage (literally everything but the capdata.xml) and hav an on the fly configuration capability and call installations and configuration from the SD card. Haven't had much time to play with it though.
Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).
Hmm, I can't seem to find the original thread either. Really just registry entries, but the cab's make it easier.
See attached...
Run each in order, then soft reset
Cheers
FYI: You can use my cappackage (see pg 1) as a starting/reference point for building the extROM mount into the initial config process after hard reset...
Try this. ...............
sodak said:
Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).
Click to expand...
Click to collapse
Thanks to both of you for the quick response
I don't know whether it is because of this or because of something else. But I started modding this CapPackage file, and all of a sudden my treo just started acting weird. I had to hard reset it several times throughout the day. Then I upgraded to the 2.25 WM6. And that is where **** really hit the fan (I upgraded and put my own CapPackage version in it). And after that I've had nothing but trouble. Soft resets didn't work anymore, it just crashed on the boot screen. Hard resets work, but really slow, takes about 20min. So now I'm re-upgrading to 2.25 and just leaving that CapPackage file alone for now .
The tale away message: Don mess with this unless you know what you're doing, which isn't me
-Robert

How to merge multiple .cab files into single .cab file

Hi,
I am looking for a utility to merge multiple small ( free ) utilities into a single .cab file to automate the installation; just to ease the installation process after the hard reset or ROM upgrade.
Though i tried Win CE Cab Manager but unable to achieve that functionality - its look like to me that i am missing something somewhere.
Regards.
I'd like to know this too...
Does this help? Not used it myself
http://forum.xda-developers.com/showthread.php?t=392983
mic_888 said:
Does this help? Not used it myself
http://forum.xda-developers.com/showthread.php?t=392983
Click to expand...
Click to collapse
Thanks mic for the link... But according to that software ... one have to place all the required cab files in a specially designated directory and software start installing the files from there one by one...
But; what i am looking is a software that creat a single .cab file which includes all the required ( individual ) cab files along with the parameters e.g. installation location ( Device or Storage Card )....
sashami is the best solution which was actually inspired by a script called autorun back in the days of win mo but only way to do a auto install of cabs or all one one would be to attempt and cook into you're own rom or see if it's possible to cook all cabs into 1
Maybe extract all cabs with ini or XML file. Merge ini or XML place all extracted components in same folder and use cab building program to build cab from ini/xml...
Maybe.
This is the best thing I have found........not really an app per se.
What is UC? It is a feature contained in UC capable ROMs. A UC capable ROM extends initial customization to your SD card so you can load cabs and install XML files that are located there too. What this means is that once you get your customization scripts right, you can flash any UC capable ROM and all your apps and settings will be restored as part of the initial customization process whenever your SD card is inserted in the slot.
http://forum.xda-developers.com/showthread.php?t=366337
I have been using Slueth's ROM and this UC method for quite a while now and it works fantastically. Takes a little effort but anything worth it's oats will take atleast a little effort.
http://forum.xda-developers.com/showthread.php?t=366284
I just come a across while searching, here is another solution:
http://www.pocketpctoolkit.com/
this should not be a advertisement, because it is not freeware, but a suggestion.
you can add cabs and the program builds an desktop or device installer and merges the cabs (and other files). the device installer is a exe not a cab....
if you look deeper in the internet you find a full time solution...
hope it helps...
chipsxj said:
This is the best thing I have found........not really an app per se.
What is UC? It is a feature contained in UC capable ROMs. A UC capable ROM extends initial customization to your SD card so you can load cabs and install XML files that are located there too. What this means is that once you get your customization scripts right, you can flash any UC capable ROM and all your apps and settings will be restored as part of the initial customization process whenever your SD card is inserted in the slot.
http://forum.xda-developers.com/showthread.php?t=366337
I have been using Slueth's ROM and this UC method for quite a while now and it works fantastically. Takes a little effort but anything worth it's oats will take atleast a little effort.
http://forum.xda-developers.com/showthread.php?t=366284
Click to expand...
Click to collapse
i flash phones like everyday. using that method is for doing a couple of cabs. if you are trying to do like 100 cab files it will take a loooooooooooong time.
wince cab manager
if you just want to make one cab i would use Wince Cab Manager (OCP Software) (google it) to extract all the neccesary information from all the cab files.
then re-import all the information (links, registry, files etc) into a brand new Cab File.
so long as you keep all the extracted cab files separated this should be easy enough, but time taking.
Hope that helps. =D
Dan

Categories

Resources