I am using the hypercore kitchen and using its right's TNT.1437 TouchFlo as a base for building off of for my own Rom and I want to replace the standard SMS application with the WM6 Threaded SMS app in Rom instead of having to install a cab file every time I hard-reset.
Basically I want the standard SMS application gone, and the new Threaded SMS app in Rom. I want it to be just like a cab installation but without an actual installation.
Below attached is a zip file for "WM6 SMS Files"
Please someone help me out on this one.
Does nobody know how to do this?
I didn't download the zip file, but if there's a cab in there, just follow the directions in Sambartle's tutorial under the packaging section.
http://forum.xda-developers.com/attachment.php?attachmentid=44308&d=1184780703
I just used these directions today and it works great.
Alternatively, you can also add the cab to the ext ROM. There is a file you add the filename of your cab into and when the customization process starts, it'll auto-install your cab. I haven't yet figured out how to set up an ext ROM so I can't help with that part.
The link doesnt work but its right is helping me with this already. Thanks though.
You would add it to the extended rom.......
How to do this...I'm still...learning myself
dwny said:
You would add it to the extended rom.......
How to do this...I'm still...learning myself
Click to expand...
Click to collapse
There's a tutorial on XDA Ftp made by faria on how to edit the extended rom.
Basically you open the Extended Rom with WinImage, edit the config.txt and update the cabs you want in it.
Pretty easy thing to do.
P.S. You can also find an empty extended rom on the ftp. You can add autorun.exe and config.txt with the cabs you want.
Related
Given a moderate level of success with faria's WM6 ROM Kitchen, I decided to take the next step and take advantage of the extended ROM so that I could put some .cab files there to install for some apps that didn't work well as ROM packages. And using the detailed document faria put together, I've got this working pretty well.
However, I use a group of programs from SBSH (PocketWeather, PocketBreeze and iLauncher) and all of them run their settings program at the end of the install prompting for changes. This means I can't put these .cab files into the extended ROM (.cab files in the extended ROM must run silently to completion).
I've taken a look at the cabinet file using WinCE Cab Manager and I can't figure out what causes the settings app to run at the end of the install so that I could turn it off. Anyone know how to do this?
Thanks!
saeba said:
Given a moderate level of success with faria's WM6 ROM Kitchen, I decided to take the next step and take advantage of the extended ROM so that I could put some .cab files there to install for some apps that didn't work well as ROM packages. And using the detailed document faria put together, I've got this working pretty well.
However, I use a group of programs from SBSH (PocketWeather, PocketBreeze and iLauncher) and all of them run their settings program at the end of the install prompting for changes. This means I can't put these .cab files into the extended ROM (.cab files in the extended ROM must run silently to completion).
I've taken a look at the cabinet file using WinCE Cab Manager and I can't figure out what causes the settings app to run at the end of the install so that I could turn it off. Anyone know how to do this?
Thanks!
Click to expand...
Click to collapse
You would be looking for a file called setup.dll, get rid of that and try it again!!!
funman said:
You would be looking for a file called setup.dll, get rid of that and try it again!!!
Click to expand...
Click to collapse
That did the trick!! Thanks so much !
Being able to build applications as packages into the ROM and put other ones to install automatically via the extended ROM has really cut down the time to go from a hard-reset to a fully working system. I'd guess from 90mins or so to 30mins now. Very useful!!
Hi all,
I need some advice on doing something that was fairly easy to do in WM6.0 ROMs, which is changing the default keyboard skin by replacing the msim.96.dll.0409.mui file.
I've tried a number of WM6.1 ROMs and this does not work. The only way I have been able to get the .mui file working was to re-cook the ROM and using an OEM package. Even after I re-cook with a new keyboard skin and try to replace the .mui file it does not work. Very strange.
Any of the cooks out there have any ideas why this is? I did a reg. dump of a ROM with and without the keyboard OEM package but did not find anything specific that would show why this does not work.
Appreciate any feedback. I know this works without any issues in WM6.0 ROMs.
Thank you.
Don't know what your doing wrong buddy but most of the time you need to cook the new .mui file in like I always do and i have no issue with the WM6.1 roms ever using the grey keyboard that I always use in my roms. To get this straight your dumping the rom and then copying the new .mui file right over the old file if there is one at all then rebuilding the rom? that is the only way it will work you can't copy over it once you have rebuilt the rom it needs to be cooked in.
austinsnyc,
Thanks for the response.
If I cook the .mui file in a ROM it works fine. The problem is not being able to replace the file (even though the file is overwritten). I was able to do this in WM6.0 ROMs but it doesn't seem this is possible in WM6.1 ROMs and I just wanted to confirm it.
So if I dump, change file, re-cook, works fine. I guess I'll have to do that with any of the new WM6.1 ROMs I end up running.
Thanks again.
ecltech said:
Hi all,
I need some advice on doing something that was fairly easy to do in WM6.0 ROMs, which is changing the default keyboard skin by replacing the msim.96.dll.0409.mui file.
I've tried a number of WM6.1 ROMs and this does not work. The only way I have been able to get the .mui file working was to re-cook the ROM and using an OEM package. Even after I re-cook with a new keyboard skin and try to replace the .mui file it does not work. Very strange.
Any of the cooks out there have any ideas why this is? I did a reg. dump of a ROM with and without the keyboard OEM package but did not find anything specific that would show why this does not work.
Appreciate any feedback. I know this works without any issues in WM6.0 ROMs.
Thank you.
Click to expand...
Click to collapse
austinsnyc said:
Don't know what your doing wrong buddy but most of the time you need to cook the new .mui file in like I always do and i have no issue with the WM6.1 roms ever using the grey keyboard that I always use in my roms. To get this straight your dumping the rom and then copying the new .mui file right over the old file if there is one at all then rebuilding the rom? that is the only way it will work you can't copy over it once you have rebuilt the rom it needs to be cooked in.
Click to expand...
Click to collapse
Actually you can change it easily via cab install but you need to sign it first. You can try the attached cab, and here: http://forum.xda-developers.com/showpost.php?p=1610615&postcount=3 for other skin.
Try this. First import the attached Keyboard Cert registry file (use dotfred's task manager which does registry editing, or resco registry editor). Once you do that, you should be able to use the various keyboard cabs. I've attached one that has like 20 keyboard styles you can choose from (uses mortscript to do this). Choose the one you want, soft reset, and presto...
sakajati said:
Actually you can change it easily via cab install but you need to sign it first. You can try the attached cab, and here: http://forum.xda-developers.com/showpost.php?p=1610615&postcount=3 for other skin.
Click to expand...
Click to collapse
sakajati,
Works fine now. Thanks for the links.
mfrazz,
Thanks for the info also! Appreciate it.
I would also like to know how to install a .cab during Customization (in 3 seconds). Does anyone know how?
anyone?
What do you mean by converting a .tsk????
Just put the .tsk in the OEMOperators Package instead of the one the ROM does and change the config file...i
yeah, i dont think that "convert" was the best word choice, but i basically just wanted to use a custom theme in my rom and was wondering how to do that. ill give this a shot, though
ryncppr said:
What do you mean by converting a .tsk????
Just put the .tsk in the OEMOperators Package instead of the one the ROM does and change the config file...i
Click to expand...
Click to collapse
I can't find that package, where is it?
ok, sorry, I found it and changed the theme successfully. Now, I might as well ask this one question:
is there any way to install a .cab to the device while the device is configuring during the first startup? That way users can uninstall it if they want to?
im sory, but does anyone have the answer for this? im pretty sure laurentius26 uses it in his roms, but thid thread has had 150+ views and no respnses other than mine on one other one...
For OEM you could make an cab of it then use packages creator 5.4.exe Might not be the simplest solution but..
For UC use the cab you made above
Atleast now you have something to go on.
raiisak said:
For OEM you could make an cab of it then use packages creator 5.4.exe Might not be the simplest solution but..
For UC use the cab you made above
Atleast now you have something to go on.
Click to expand...
Click to collapse
is this the solution for the theme? because I have figured that one out Now I'm looking for a way to install .cab's when the device says "It will configure your device in three seconds."
opgadgets said:
ok, sorry, I found it and changed the theme successfully. Now, I might as well ask this one question:
is there any way to install a .cab to the device while the device is configuring during the first startup? That way users can uninstall it if they want to?
Click to expand...
Click to collapse
Use kaiserkitchen. Run KAISERKITCHEN.cmd and choose p option then open the cab. if you need more info read. All the info you need is here already.
opgadgets said:
is this the solution for the theme? because I have figured that one out Now I'm looking for a way to install .cab's when the device says "It will configure your device in three seconds."
Click to expand...
Click to collapse
Check config_operator.txt under kaiserkitchen\OEM\OperatorPKG
raiisak said:
Check config_operator.txt under kaiserkitchen\OEM\OperatorPKG
Click to expand...
Click to collapse
I can't seem to find that file
There are two methods you can use to cook a cab into the customization install.
To hardcode the cab into the install locate the config.txt and add a line for your cab. The formatting is pretty self explanatory once you look in the file itself, or to be more user friendly and allow used to decide whether or not they want to install the cab in the first place rather than just make it uninstallable go here and include the cab(s) in a separate UC package.
there is no reason for a .cab what so ever just put your .tsk in the rom dump (dont even use package tools) and edit the config to your .tsk its really simple as the config.txt all ready has a line that installs the defualt .tsk so just edit that to the name of your .tsk lets say custom.tsk
fiendz said:
There are two methods you can use to cook a cab into the customization install.
To hardcode the cab into the install locate the config.txt and add a line for your cab. The formatting is pretty self explanatory once you look in the file itself, or to be more user friendly and allow used to decide whether or not they want to install the cab in the first place rather than just make it uninstallable go here and include the cab(s) in a separate UC package.
Click to expand...
Click to collapse
Ok I'm going to go for the first method. Now, is the config.txt in the Tier Install Package folder?
anyone? all I want to know is how to install .cab files while the "device is configuring please wait..." during an initial hard reset/flash
opgadgets said:
anyone? all I want to know is how to install .cab files while the "device is configuring please wait..." during an initial hard reset/flash
Click to expand...
Click to collapse
We told you already mate...
Open: C:\kaiserkitchen\OEM\OEMAPPS\Config_AP.txt
You will se something like this:
Code:
CAB: \WINDOWS\CVC-PPC-WWE-705142-DopodPPC.CAB
CFG: \Windows\config.txt
CVC-PPC-WWE-705142-DopodPPC.CAB is actually cyberon voice command
Now what you do is:
1. Place youre cab here: C:\kaiserkitchen\OEM\OEMAPPS
(let call it: search4answer.cab)
Now you have search4answer.cab in youre C:\kaiserkitchen\OEM\OEMAPPS folder.
2. Open: C:\kaiserkitchen\OEM\OEMAPPS\Config_AP.txt
and insert the name of the cab.
Code:
CAB: \WINDOWS\CVC-PPC-WWE-705142-DopodPPC.CAB
CAB: \WINDOWS\search4answer.cab
CFG: \Windows\config.txt
Remember Config_AP.txt is locked, unlock it and lock after you have edited.
Close all, and cook it up. Now youre cab will be installed under what you call 1-2-3 customization install.
The cab will be uninstable if you flaged it to be so.
GL.
raiisak said:
The cab will be uninstable if you flaged it to be so.
Click to expand...
Click to collapse
A little off topic, but i always wondered why chefs don't make most of their cooked cabs uninstallable. Coz' there's always a program or two (or 10) that you don't use, but you like the rom and stick with it. having a dosen programs you never use is a waste...
question to cooks
slovoflud said:
A little off topic, but i always wondered why chefs don't make most of their cooked cabs uninstallable. Coz' there's always a program or two (or 10) that you don't use, but you like the rom and stick with it. having a dosen programs you never use is a waste...
question to cooks
Click to expand...
Click to collapse
Bether rom performance when cooked in Metod above is not what we call "cooked in".
raiisak said:
We told you already mate...
Open: C:\kaiserkitchen\OEM\OEMAPPS\Config_AP.txt
You will se something like this:
Code:
CAB: \WINDOWS\CVC-PPC-WWE-705142-DopodPPC.CAB
CFG: \Windows\config.txt
CVC-PPC-WWE-705142-DopodPPC.CAB is actually cyberon voice command
Now what you do is:
1. Place youre cab here: C:\kaiserkitchen\OEM\OEMAPPS
(let call it: search4answer.cab)
Now you have search4answer.cab in youre C:\kaiserkitchen\OEM\OEMAPPS folder.
2. Open: C:\kaiserkitchen\OEM\OEMAPPS\Config_AP.txt
and insert the name of the cab.
Code:
CAB: \WINDOWS\CVC-PPC-WWE-705142-DopodPPC.CAB
CAB: \WINDOWS\search4answer.cab
CFG: \Windows\config.txt
Remember Config_AP.txt is locked, unlock it and lock after you have edited.
Close all, and cook it up. Now youre cab will be installed under what you call 1-2-3 customization install.
The cab will be uninstable if you flaged it to be so.
GL.
Click to expand...
Click to collapse
thanks a lot raiisak!
however, it's not working. For example, I placed a custom-made .cab file in OEMAPPS, then told the config.txt file to load that, but it didn't work. Any suggestions?
Oh, and I still can't figure out how to get the darned theme to load as the default theme...
Hi all,
Perhaps it is a newbie question so please bear with me.
I have an i-mate K-Jam flashed with TNT rom (build 20273). It works perfect and nice, however (frankly speaking) I don't like or want some of the APPs installed with this ROM, but I can't uninstall them.
I've searched this forum to find a way to extract the OS (OS only) from TNT rom so that I can flash my wizard and then install all the APPs I want, with no luck. Perhaps my search skills are a little poor...
So would someone please explain if it is possible or not? and if yes, how?
Thanks in advance.
Regards.
You cannot remove apps from a cooked rom. Search for Vanilla roms if you just want the base rom without any extras and then you can install you own apps.
well you can, but for that u'll have to dump the ROM first, remove the apps you dnt like and recook it
you can not dump the TNT roms. when you try, there are no RGU'S or DSM's.
You can dump my rom if you like, but you will get some missing files you will have to put back into the oem.
the missing files come from me not editing the rgu's when I cook.
try dumping Hornet5. for the most part you will get complete packages, but also some "missing files". just put them back into the oem/sys and recook.
Thanks for info. Saved me a lot of time.
I finally managed to cook my own rom. Everything works perfect except that:
1) I've used XIP, SYS and OEM files/folders of different builds. Am I going to have problem later?
2) "CommManager.exe" was missing. I've searched the files used in kitchen and the only thing I found is "commmanager.htm". Later I managed to download and install HTC CommManager but I can't assign in to its button (button 6). Is there any solution for that?
3) How may I extract the "splash screen" from one build, and upload it to my phone?
4) Bluetooth is not working. It says there is no bluetooth hardware on device. Also WLAN disconnects after a few seconds. How may I extract the drivers from original ROM and upload it?
I know the above questions are too much, but actually I'm so excited that my first attempt to cook a rom was successful (almost). I hope one of you experts be kind enough to help me solve the above issues and have a perfect phone.
Thanks in advance.
you will have some problems with the initflashfiles.dat in the oem, as well as the "oemtranslation.prvxml" or something which controls your icons for programs and control panel.
The best thing to do is use the same build OEM SYS & ROM folders.
If you dumped hornet 5, then your best bet ist to work with everything in it. I was working at this rom after Sleurhut for about a month or two.
mixing builds of those folders makes you start from scratch again fixing up your oem again.. and again.
as far as the missing files, try using the Xdump method; or use the searcher on your PC to find the missing files folder and the contents.
Dear S.V.I
Thank you so much for your ongoing support and help.
As I've mentioned before, I'm a total newbie trying to have a clean WM6.1 on Wizard. I've searched and read lots of tutorials here and there, but there are still lots of questions remained.
I tried to play with HyperCore (multi-device) today and I failed in the first step. I've extracted the "nk.nbf" from official i-mate KJam ROM using WinRAR. HyperCore is installed and I've a "C:\Core" folder as well as a "HyperCore" folder on my desktop.
The "DumpRom" is asking me to make sure the "nk.nbf" is in "HyperCore\Extract\Source" folder. Well it is there. Press Enter and the error message says: "There is no nk.nbf in Core\Extract\Source".
No it is not. First, it asked me to put it in "HyperCore\Extract\Source" not "Core\Extract\Source". Second, there is no "Extract" folder under "C:\Core". Even after creating Extract\Source under C:\Core and copying nk.nbf there, the same error message appears again.
So, what I'm missing here?
Same
I'm also scratching my head on this problem too. I've even tried creating extract\source folders in locations C:\core\ and desktop\hypercore\ but still no luck.
I'm wondering however that the issue could be caused by vista/7's change from Documents and Settings\user\desktop (2000, XP) to Users\user\desktop.
It may change the way the batch files are called but i'm really rusty on batch commands these days
I would start with the sticky "How to cook a ROM" thread, focusing on CRACING's kitchen, then move to Nekid Angel (Post #3)
where you will find a more updated ROM ready to cook. If you want to try WM6.5 a good ROM and kitchen is at [WM Kitchen] Wizard Kitchen or CRACING's RC6. I have been playing around with that.
You might move your discussion to one of the cooking or kitchen threads mentioned above, too, since that is where others will look.
Perfect
That's what i was looking for thanks for the heads up N2rjt!
I have got the ROM Image Editor. I edit the nbh file of the ROM. I need to know how to add my cab files to the ROM so it gets installed automatically as I flash the ROM. This will help get things up running promptly with each new ROM I install.
Anyone can help ?
SASHIMI check my ROM thread for download if can't find....
already use Sashimi
I already have Sashimi 8.0 & I use it. But I see building the cabs within a new ROM in way that gets them all installed as I flash the ROM, would be great & fast.
I have the ROM Image Editor but I just don't know where to add the cabs within the ROM folders to reach the target.
Is there anyone who can help on this ?
Cooking
You're going to have to cook them into your ROM, which won't be in the form of .cab's any more. They'll be in EXT. And everytime you change roms, you'll have to extract whichever rom you dl, and recook it with the programs you want in there. SASHIMI is probably your best bet unless you feel like spending a lot of time on each and every ROM just so that when you flash it the programs are already in there.
Anyone feel free to correct me if I'm off base here, but it's probably not worth it for speed and ease issues.
Happy Flashing!
drumboy03
yassero said:
Is there anyone who can help on this ?
Click to expand...
Click to collapse
What ROM editor are you using? Perhaps htcRIE_0.5.0.12 from http://forum.xda-developers.com/showthread.php?t=377514 ?
If that´s the one you are using I don´t think is capable to do what you want, as drumboy said: Cooking is the way
luiggi said:
What ROM editor are you using? Perhaps htcRIE_0.5.0.12 from http://forum.xda-developers.com/showthread.php?t=377514 ?
If that´s the one you are using I don´t think is capable to do what you want, as drumboy said: Cooking is the way
Click to expand...
Click to collapse
Yes it is htcRIE_0.5.0.12. Do you know how to install the cabs in a ROM ?
Usually after a ROM is installed & during customization, some cabs appear in folder Volatile & are then installed. Can I place my cabs along those ?
yassero said:
Yes it is htcRIE_0.5.0.12. Do you know how to install the cabs in a ROM ?
Usually after a ROM is installed & during customization, some cabs appear in folder Volatile & are then installed. Can I place my cabs along those ?
Click to expand...
Click to collapse
Ok if you want to install it after flash, then you can do it a few different ways, like UC, XDA_UC or tom's autoinstall. But for all those you need to cook them in the ROM.
If you dont have it cooked in, then shashmi or programs similar to those will help.
You cant edit a ROM using htcRIE, in the sense add cabs and stuff, and recompile it to make it bootable in my opinion.
You can play with it and see! If the ROM is using runCC, then you need to add cabs, and mofify config_operator.txt file to add those cabs to execute in first boot.
Hope this helps.