Related
it's my first time trying to cook a ROM, and I am using shady313 kitchen for X1i here, but I have a lot of questions about cooking a ROM , I searched a lot but couldn't find the proper answer,
First: I want to know how can I add new applications to the ROM, I tried adding some EXT packages ( I just put the EXT package in the Kovsky_External_Packages in EXT folder ) but after flashing I couldn't find the application,
this is some packages I added from dumped X1 R3AA010 ROM
Code:
AdobePDF_2_5_1_0_363324_00
Arcsoft_MMS_5_0_43_98R7
Kovsky_Bejeweled2
Kovsky_Sudoku
PanelManager_1_0_20081215_MR1_R215
I also tried to add the application as OEM ( cause I noticed that shady313 used OEM to add applications ), I added the X2 task manager but I couldn't know how to make it available on the upper right corner of the screen the whole taskbar was messed up ( is there a tutorial for that )
Second: I want to use RunCC to customize the ROM at the 1st boot, I searched in XDA for a tutorial put I couldn't find one ( I found some comparisons ) but I downloaded EXT package RunCC 1.1.5 ( attached ), and I want to know how to use it to install cabs and arrange folders in the first boot ( I need a comprehensive tutorial please )
Third: how can I add Sense 2.5 to the ROM ( just the names of the packages needed ) and theme it with a MOD like GTX or Cookie Home Tap
Note: am cooking the WWE (0409) ROM
am really sorry for this trouble but there is no place to ask except here
Hello
I'm building with all Leo 3.04 EXT packages, no modifications except to use the 0409 files from Leo 3.02 to make it WWE.
I've encountered a few 'IDS_XXXX' menu items in contacts and messaging - does anyone know what they should say and which file to edit to fix them?
Screenshots attached
Edit: I found the IDS_MSGCLIENT_CALLVOICE in People_Pages.xml. It appears to reference "HTC\Common\simpledialog.mode9" so I'm guessing whichever mode9 manila file is the simpledialog must be missing some code to describe the voice call option...
Edit 2: IDS_ALLPEO_BACKUP and SIMINFO are in there too...
You used 0409 lang files from some older build of those apps (HTCMessagingClient I see there?) which don't have those resources (translations) available.
You're absolutely right. A bit of backtracking and version checking shows that I'm using Manila People v2.5.20161612.0 which I believe is taken from the Oboe ROM and therefore has references to some stuff that isn't in my Leo packages. The Leo 3.04 package version is Manila People v2.5.20161424.0 and I think I got them confused; I'll try the 3.04 package and see if everything works OK
Edit: Yep, switching to a Leo package instead of the Oboe package I was using fixes the problem
Hi, my first post here...
I just flashed the Energy 21908 Glass rom...
showpost.php?p=5044378&postcount=2
I was trying to enable the simplified chinese displaying on the phone without installing the IME...
So I installed the font in this thread: Arphic Crystal CHS Fonts
showthread.php?t=700311
However, when it restart, I found some of the interface changed to chinese but some of them remained in english...
Then I tried to uninstall the package but the characters which was in chinese before then displayed as "chequers"
I think the Arphic Crystal CHS Fonts package might be not compatible with the earlier energy rom..
I uploaded the edited cab file which I did some minor change with the registry... So far it works fine!
Please note: the revised cab is only suitable for those who want to read website, contacts, emails and message in chinese. it will not change the interface. the device interface will remain in English~~~
Regarding the TOMTOM issue... After the installation, it pops up an error window showing "bttray.exe is not a valid wince application"...
when I searched through the forum, someone suggested to delete the btcoreif.dll and btsdk30.dll in the rom after installation (but before restart)...
However, it did not work in my case...I tried to delete but the the two files are in rom and not able to be deleted. The cause of the problem is: when you install the tomtom, the older version file (i.e. btcoreif.dll and btsdk30.dll) in tomtom cab will replace the existing file in your rom...And then it could not be deleted or renamed!!! In your case, may be not...
So I deleted this two dll files in the tomtom original cab and then installed in my HD2... it works fine now... no popups, and the bluetooth works well... I uploaded to megaupload for someone who wants a simple solution~~~
megaupload.com/?d=KIED69VX
Lastly, I recommend a software: WinCE CAB Manager. When you open an cab file with this tool on your computer, it will clearly show the file structure... how the cab will modify your registry...what files will be added to your rom...etc.
Cheers,
conant
Your modified Arphic Crystal CHS Fonts package works fine. Thanks!
Hello,
after cooking my first i8000 lite roms, i want now to cook in several apps and maybe sense 2.5. After reading the whole night in the forums i learned that there are several ways to convert a cab file: to an OEM or and EXT package... but what is the difference? OEM works with provxml and EXT with app.reg? So the only difference is the way of installing to the rom?
thanks a lot
yetrael said:
Hello,
after cooking my first i8000 lite roms, i want now to cook in several apps and maybe sense 2.5. After reading the whole night in the forums i learned that there are several ways to convert a cab file: to an OEM or and EXT package... but what is the difference? OEM works with provxml and EXT with app.reg? So the only difference is the way of installing to the rom?
thanks a lot
Click to expand...
Click to collapse
OEM are flat packages (meaning that all the files and modules are in the root level of the package). EXT packages are multilevel packages, as they have the root folder and in the root is reg (app.reg) and initflash info (app.dat), along with another folder with all the common (non lang dependant) files ("files" folder), as well as a lang folder (0409 for WWE). Reg in OEM is .rgu extension, and reg in EXT is .reg extension, but both are ultimately cooked in the same location -- hives. OEM dy defination includes .dsm files which is simply package info not generally considered necessary for the function of the rom. EXT may or may not include .dsm, but is typically not reguired in an EXT package. provxml is no different in OEM or EXT, as provxml entries are not cooked into hives, they are implimented on first boot. Some kitchens use EXT, some OEM, and some kitchens use both. Before platform rebuilder came along, everything was OEM.
simply said:
EXT = OEM
but:
EXT - doesn't need dsm file (OEM neither, when using platformrebuilder-based kitchen)
EXT - all files except parts for initflashfiles.dat and hives are in files folder
EXT - instead of <guid>.rgu is app.reg in main folder
EXT - instead of initflashfiles.txt (used in BuildOS) is app.dat in main folder
so all in all, it is just simplified OEM so you don't have to generate dsm's and guid's
OEM files - are for your specific device. Other files maybe placed their by the carrier to make it do some of their pretty stuff.
EXT files - can be carried/upgraded from different roms.
Plus all that stuff that indagroove and ondraster said. Those are how I would see them as a novice.
thanks a lot for sharing your knowledge
afaik my kitchen for omnia2 works only with buildos, so i will use oem packages
BuildOs, I remember that one. So you won't have any EXT's. Before the EXT's came into existance if I remember right...
Doesn't the factory (HTC in my case) use EXT packages?
jwzg said:
Doesn't the factory (HTC in my case) use EXT packages?
Click to expand...
Click to collapse
They use OEM.
yetrael said:
Hello,
after cooking my first i8000 lite roms, i want now to cook in several apps and maybe sense 2.5. After reading the whole night in the forums i learned that there are several ways to convert a cab file: to an OEM or and EXT package... but what is the difference? OEM works with provxml and EXT with app.reg? So the only difference is the way of installing to the rom?
thanks a lot
Click to expand...
Click to collapse
thanks for the replies guys...
was just wondering ...noobie question tho...
if i want to install my own programs ,is it better to do so as oem or ext??
and in which folder should i put them?
TIA
cheers
krazy
Installing by phone you mean cooking into ROM? It doesn't matter, they both do the same purpose, there is nothing like SYS, EXT, OEM, ... in original platformbuilder, there is only Microsoft side (for us SYS and MSXIPKernel) and OEM's (htc, ..) part (for us OEM, OEMXIPKernel). With platformrebuilder, that deletes dsm's and relocation module parts, came simplification in terms of adding new packages. Since it deletes dsm, it doesn't need them at all and to specify what is .rgu for package, it moves all content into folder "files" (even modules) and .rgu is renamed in root to app.reg.
Have I explained it enough? Just ask
I have a problem cooking this app.
Ive open the cab and delete all languages except spanish, i save the cab, install it and i have the app in spanish, but if i convert it to ext package and i cook it in the rom the language i get is english.
Im using os kitchen last version.
Thanks
moebius15 said:
I have a problem cooking this app.
Ive open the cab and delete all languages except spanish, i save the cab, install it and i have the app in spanish, but if i convert it to ext package and i cook it in the rom the language i get is english.
Im using os kitchen last version.
Thanks
Click to expand...
Click to collapse
In OS kitchen there is an option to import a new ext package, just import the complete cab and after that you'll find the ext pkg with all languages in your kitchen, so now you can delete the other languages and edit the ext pkg.
If this isn't working you can always rename the Spanish into English,
Greetz,
Tanks Rataplan for your answer.
Ive tried that also and the results are the same it get instaled in English.
I do that with other apps and works fine maybe im doing something wrong but i dont now what.
Ill try to get another version (one more) and try again.
I've never used g-alarm, but when you've made the ext's, is there an english language file present that you delete? Or is english the default language, and other language resource files are added to the cab? Anyway, it sounds like you're missing a registry key in your app.reg file for the language. Check in HKCU (or HKLM)\software\galarm (or the name of the developer) after you've installed the cab and get the reg key. Or, check in the program folder and see if there are any setup files that have the language setting, and cook it into your rom (sometimes those files hide in windows or application data as well). If the file is going directly into \windows in your ext, it's possible that g-alarm doesn't like the fact that it's read-only, so you'll need to get a non-read-only copy into your \windows folder. Anyway, I'm just guessing. You could always figure out how to make the package using kheb 1.1.
Thanks Farmer Ted too
there are many languages .txt
What i do is open cab with cabmanager delete all except spanish i install it from the cab and installs in spanish.
with that cab i made the ext package and cook it in the rom and the language that apears is English.
Ive tried to rename spanish to english.txt and if i install it from de cab the language i get is spanish. i made again the ext package and cook it and i get english language.
I think the same as you may be some hidden file or something like that im gonna try the cab you post and try to find that file.