|
||||
I have always been curious about the ExtRom. I understand that it includes carrier-specific software, but mine has never been overwritten by the ROMs that I have cooked. (I prefer this, as some of the software in my ExtRom configures my carrier-specific settings.) Is it just that I am lucky, and that most cooked ROMs include a replacement ExtRom, or do they simply add to the carrier's ExtRom? The latest ROM I installed included things like Total Commander, yet my carrier's software still installed on the first boot, so it does not appear that it replaced it. Once I know how it works, I can contribute more to this specific thread.
|
|
||||
If you guys want to work on an ExtRom, I believe the focus should be on a "global" release. I messed with this a while back when I had a rom with a twist. The twist was that the ExtRom would prompt you to choose your carrier and then install the proper cabs. This is the easiest and more editable way to have a packaged product for all carriers. Unfortunately, to get it to work, I had to change some things in the rom and it would not allow for users with thier own custom ExtRom to install their ms_.nbf without some reg edits and another hard reset. I am still working on this, but haven't messed with it in a while.
The big thing that needs to be done is to consolidate the different carrier ExtRoms down as much as possible. When I had all of the carriers in one ExtRom, it was almost full (9.5MB or something close to that). If we can condense down to 2-4 cabs per carrier, we would get rid of a lot of redundant waste.
__________________
Kitchen updates at www.ppckitchen.org and you can get BuildOS help Here
If you have been helped by me or would like to support developers like Olipro, helmi_c, and others please feel free to Donate ALWAYS FLASH BACK TO YOUR CARRIER'S OFFICIAL ROM BEFORE TAKING YOUR PHONE IN FOR SERVICE OF ANY KIND |
|
||||
What if the web-based front end simply allowed you to select your carrier of choice and thus update the ROM to include the appropriate ExtRom as well as the carrier logo? That would be so sweet.
|
|
||||
well, I can say that all you need on the VZW side is, well, not really anything. The only semi important ones are... the one that sets up the #'s and the data connection, and the one that sets up MMS, The MMS one is kind of nice, as there are lots of customizations that need to be made to the OEM if you want to use it. Oh, and wireless sync, if you're into that sorta thing.
Go http://pdaphonehome.com/forums/ppc-6...reakdown.html? for more.
__________________
C-C-C-A-A-A-R-R-R-L-L-L
|
|
||||
Quote:
|
|
||||
EDITED AGAIN 4 NEW PRL CAB:
EDIT: I updated the Cabs for the 3.x roms I was testing. These are a little more streamlined. Out of 23 Cabs, In windows folder I have now have 3 NG.txt Files: cab1_NG.txt = some "umatched registry" so it added it in the, "PPST_File_SPCS_with_PRL20227.sa.CAB" cab6_NG.txt = some "umatched registry" so it put it in cab23_NG.txt= the "CONTACTS" CAB... doesnt say anything actually wrong since no files but 1 Dll file. I have updated since alot of the roms as well as the RC2&3 roms dont have cabs pre-loaded. Keep in mind, not all cabs listed here are essentail, I just like 2 have all bases covered by having them. Check Colonel thread on Extrom list HERE: http://www.ppcgeeks.com/viewtopic,p,40825.html#40825 So after all this I am going to leave "as is" for anyone else to put any comments suggestions to this. |
|
||||
Another fun little goodie for anyone that is running a rom where you have to copy a file from the storage card to \Windows to get it to work. For example, in my 3.5, I have VC mostly installed, but you have to install voicecmd.exe from the SD. Anyway, just add lines like this to you config.txt.
Code:
CPY1: \Storage Card\voicecmd.exe CPY2: \Windows\voicecmd.exe |
|
||||
Quote:
|
|
||||
Quote:
__________________
|
|
|
|