After working with the extended ROM, another thought occurred to me. This is all working fine for faria's ROM... but in future I may not have a ROM Kitchen to reconfigure the ROM. Is there another more generic way to solve my problem of getting my custom apps and settings on a new ROM release? Setting up the extended ROM and using autorun.exe to autoexecute .cab files got me thinking....
Is it possible to run autorun.exe manually after a ROM installation and by setting registry keys appropriately point it to a group of cab files on a storage card? Or is there some other way to do this? For a vanilla ROM, I have like 20+ cab files to install to get all my applications and customizations installed. Automating this process as much a possible would be hugely helpful !
Thoughts? Anyone doing something like this?
So what would you like this app to do?
Auto install all cabs in the ExtROM
Configure the network of your choice
Process some XML which has all of you personal tweaks and speedials or even activesync settings in it
This is all possible with a simple c# application.
Maybe this will do the job
http://www.freewarepocketpc.net/ppc-download-pocket-pc-installation-creator-v1-8.html
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!!
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.
Hi all, I've been trying for quite some time to cook my first rom. I've now read a lot on the subjects here on these forums but it seems the vox is not the easiest device to start with I've successfully extracted all files from an .nbh rom upgrade. I've then extracted everything to /dump folder using prepare_imgfs.exe and imgfstodump.exe. Here I can delete/change/add files in the directory and rebuild the rom with buildimgfs.exe but it is not a very clean cooking... I'd like to be able to use Package tool. Actually I can use it and get the two folders /OEM and /SYS but then I really don't know how to rebuild the rom using Buildos.exe. Does anyone know how to do this ?
Tell me if my english is not very understandable..
I've finally been able to use these tools after a lot of trials and errors. But there is a lot of fixing to do in the building process. For exemple after running OEM and SYS folders through BuildOs a lot of files are missing in temp\dump
It seems every important file is missing in each of the subfolders. Missing dll's, missing exe's...
For example if I look in the zlib.dll\ directory I can see 5 files : imageinfo.bin, imageinfo.txt, S000, S001, S002, S003 BUT no zlib.dll ?! So I have to manually reimport those files... Is this a known issue with buildos and if so is there any solution to it ?
Thanks for any help
My bad, just realised reimporting the dlls is not at all needed
Still speaking alone ?
Perhaps this thread from the Kaiser forum helps you.
Dr Gonzo.... i would have lied to said something but my knowledge of cooking ROMs is zilch.... but i was hoping someones cooks a ROM for the Vox ... so wanted to ask u how its going?
I've been able to build an awkward "kitchen" for the Vox but I don't know yet if the roms built with it are really stable. Awkward because I don't really know how to write batch files and because I had to add a .dsm taken from Bepe's kitchen for Buildos.exe to work (but I delete it once the dump folder is rebuilt). But I have been able to add/remove packages and it seems to work.
I am currently building my rom from the Arabic one with smarttoolkit included, custom system screens, commanager and homescreen, office and HTC audio manager removed, windows live updated, Jbed instead of Jeodek etc... It seems to be stable but some things don't work yet (I still need to edit the registry)
But what I'd really like would be the possibility to add Bigstorage to the rom as it increases free memory from what I've read.
Maybe I can release this kitchen with some instructions and someone better than me could improve it ?
RE
Yeah that would be awesome to get some Vox Rom cooking happening when can you post your kitchen?
I'm in the process of writing a quick guide to go along my very dirty kitchen to show how to use it. For the moment only with HTC_Vox_ARA_1.27.415.4_4.1.13.47_02.98.90 as a base rom because I haven't tested anything else yet.
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.
Vodafone runs a setup application when the phone is booted after the roms is flashed, it installs some software and sets it up for Vodafones 3G/HSDPA network. Is there a way to extract this? I have the rom, but after running the scoter kitchen extract option I couldn't find anything that might be it...
So is it possible?
LOTG said:
Vodafone runs a setup application when the phone is booted after the roms is flashed, it installs some software and sets it up for Vodafones 3G/HSDPA network. Is there a way to extract this? I have the rom, but after running the scoter kitchen extract option I couldn't find anything that might be it...
So is it possible?
Click to expand...
Click to collapse
You mean the Network Wizard
http://forum.xda-developers.com/showthread.php?t=332697
I'm still missing some things after installing this.
I used to have a push mail installer from vodafone and I had 4 connections now I have 3. I think I'm missing the mail from the list.
theres couple different things the autorun does. Changes themes, bootscreens, and couple connection settings. I'm assuming you want the connection settings. There are cabs all around for certain connection settings. If you end up doing this yourself, you will have to play around with the kitchen and extract the NBH files. After extracting, all the files would be in the OEMoperator folder.
Yeah i found a bunch of stuff. Not in the oemoperators folder but the operatorpkg.
Is there a way of installing this in a allready installed rom, or should I rebuild and reflash the rom with this in it?
As it looks to me I should probely stuff the entire OEM folder in the new rom...
Use this, its for the dutch operators
This simple tool to automatically setup your data connection
its posible to run the cab with the 1e installation
I managed to rip out and insert the oem from the vodafone rom and insert it in to the rom I wanted to use. I was just wondering if it was posible to create my own OEM package from it, but there are some files (particulary the operator and menu config) that conflict and have to be merged. Is there a process so I can use it on other roms to without having to merge it manualy every time?