Some basic questions - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

I'm still using default ROM on my kaiser, although i have hardspl and super cid installed. I just have couple of simple questions, which i could not find on forum.
1. Can i uninstall some applications that are cooked into the custom rom?
2. Is it better to cook applications to rom or to install them afterwards with cab?
3. Since i don't use all that stuff that chefs cook into their rom, should i take time and study rom cooking and make my own, or should i install the most basic and lite rom i can find, and then install cab's i need?
tnx all

1. There is no straightforward way to uninstall programs that are cooked into ROMs. You can install the program (overtop) via a .cab, then uninstall it. That will theoretically take everything out, but it's kind of a pain and no guarantee you'll get everything (depending upon the cook's custom settings and file locations).
2. I tend to cook in applications that probably aren't going to change versions for a while. But it's not such a pain to re-cook a ROM that it's not a big deal.
3. I would suggest going with a lite ROM and figuring out which programs you like before you take on cooking. Alex has really made it quite easy, but you can run into problems. You should flash a number of ROMs (and seen the issues that can result) before you try to do it yourself. There are a number of great ones out there. I'd suggest Alex's Lite and Q-Mobile to start. Both are great.

Related

Help with cooking with core kitchen

Well hardly cooking... All I want to be able to do is to take a base ROM that I like (core 2.0n vanilla or perhaps mfrazz's 1.7) and add the programs that I always install anyway. i figure this will make a hard reset easier if needed and give me a little more memory.
Okay... so I downloaded anchillius's rom kitchen and was able to follow all the directions he provided. I used his core 2.0n, which I have been running for a while but unless I am mistaken installing what I produced would basically be the same thing as installing it directly since it is vanilla anyway, right?
anyway I have a few questions...
1. If I dump a ROM like mfrazz's crossbow 1.7 and install that as is, will the reg tweaks that he made still be there?
2. Is there a readily available step by step on how to add programs. I tried google search and couldn't find anything. I know I am being lazy here but hoping that someone will help a brotha out! that and I am really quite busy at work (but not to busy to not be messing with my phone!)
I'm pretty sure that all the reg changes are the same, I cooked Crossbow 1.7 a little, and nothing changed (that I noticed).
And when u say programs, do u mean by cooking the programs into the ROM with cabs, cuz in this tutorial there is a way on how to install programs by cabs
P.S. While were talking about programs, how do I get the settings for a programs that have to register into a package of my cooked ROM? Is it something in the reg entries on my phone? If so, how do I find out what and how do I get it off of my phone and into the package?

what do u use to backup when flashing a rom?

Normally I use sprite, or i just copy everything off my device to a folder on my desktop, but it seems like theres no easy way to flash a rom and keep everything from your device previously.
when using sprite, it may save things in the windows folder or registry, causing this new flashed rom to not work properly, or not have all the effects it's supposed to.
yes you can disable this in sprite, but if you do that you may lose the registry settings or some files that some 3rd party apps used.
so what do you guys do when flashing a new rom?
I guess restoring over different roms is not such a great idea.
UC compatible roms do make it a lot easier.
Use settings saviour, create custom cabs to install registry settings, Install Apps on SdCard, then make a folder with the shortcuts and copy the shortcuts back to programs folder. Re-install from active sync,
The best though that I have used lately, is the UC compatible roms that allow Cabs and registry settings to be install automatically after Hard reset or rom install.
Some people copy pim.vol to sdcard and then copy back later, but since i use exchange activesync, I find that to be useless.
But Never, ever restore from a backup if upgrading to a new rom...Sometime people say it works and other times it causes issues...
rohanmaini said:
I guess restoring over different roms is not such a great idea.
UC compatible roms do make it a lot easier. Though, I am waiting for the day when we shall be able to install programs to the storage card....
Click to expand...
Click to collapse
You can use the app WinCe cab manager and modify the install directory, very usefull when using UC compatible roms.
This has been a common question when flashing ROMs....and unfrotunately there is no 100% answer.
Different ROMs/chefs put in different tweaks, progs in different locations, etc, so a traditional backup/restore will not work well (as you put it already).
There is some really good promise using UC Compliant ROMs. See here:
http://forum.xda-developers.com/showthread.php?t=366337
Using these UC compliant ROMS, you can do two things:
1. Automatically install your favorite progs. It does this after flashing and initially setting up your device. NOTE: you can only install progs to main mem, not Storage Card.
2. Automatically "tweak" your device beyond just installing cabs using XML based settings files. This is something I have not played with yet, but this could put back specific settings just the way you like them.
I am sure that there will still be some things that conflict on occasion, but at least it is a good timesaver.
There are also some commercial programs that can package up all your cabs into a "super" cab and install them all at once as well. I can't recall the name right now though.

Trying to make my own rom, questions.

Hey, I'm going to try to make my own rom.
Instead of trying to recook other people's rom, (which always fail at cooking)
i'll just try to make my own from scratch.
Custom roms have so many programs i never heard of and will never use.
I just annoys me seeing them.
anyway, have a few questions.
I'm currently following this guide:
http://forum.xda-developers.com/showthread.php?t=303195
if i want to remove Windows live, do I just take out these folders?
WindowsLive_DPI_96
WindowsLive
and where do people find all these registry cabs, and how come other builders don't share them?
I know theres a list of apps on the link, but they're not updated and not as complete.
also, I think that rom comes with Cnet2, how can i get the new Cnet3?
Also, Say i put Flash 7 in the oem folder, and next week flash 8 comes out, do I just install flash 8 and it will update it in my phone?
or do I need to recook, since you can't uninstall OEM stuff.
Why doesn't the FTP work? i tried xdaupload/xdaupload.
Thanks!

Recreate Official T-Mo ROM

I am a noob .... Just trying to get up to speed, so to help me understand this stuff, I have 2 questions.
1. Should i be able to extract an official T-mo wing ROM ...... and then be able to cook it to produce an identical/ almost identical rom to the t-mo stock? I understand there is no point in doing that..... but it helps me understand it better if I know this answer..... plus I was wanting to do that first as a benchmark .... so that I at least know I am doing everything right ... then start making changes from there.
Maybe a simple alternative question, the t-mobile stock rom has t-mobile specific OEM content (my faves for example) in it..... how would you go about extracting then baking that into a custom rom? Is that even possible?
2. when you flash to a signed Rom image nbh file ... What is it replacing (ipl, spl, OS, splash, radio, xip, imgfs)?? all of those things or just certain ones? Do different nbh files replace different compenants or is it consistant to where an nbh file always replaces the same thing?
I see in some of the kitchens... you can bake in your own radio, splash screen, etc... which got mo to thinking .... what will be different with the rom between baking one of those in vs not? It seems like it is optional.
Thanks
i would like a answer to this question myself...im only interested in the part about tweaking the original stock rom..can we beef it up at all?..change the pagepools..ect?
Originally quoted from JPick:
Just trying to get up to speed, so to help me understand this stuff, I have 2 questions.
1. Should i be able to extract an official T-mo wing ROM ...... and then be able to cook it to produce an identical/ almost identical rom to the t-mo stock? I understand there is no point in doing that..... but it helps me understand it better if I know this answer..... plus I was wanting to do that first as a benchmark .... so that I at least know I am doing everything right ... then start making changes from there.
HERE is a kitchen with the only two updates from tmobile, that are considered "stock ROMs;" cook with this kitchen to make a ROM that is with the WM 6.1 builds. This will show you what is involved in cooking a ROM that only has stock - OEM - packages. Also, don't forget to use 'LZX Compression.'
You can find the kitchen that I use HERE. The 23563 build is what I use (for reference). Use this kitchen from my guide to build a ROM with the latest build.​
Maybe a simple alternative question, the t-mobile stock rom has t-mobile specific OEM content (my faves for example) in it..... how would you go about extracting then baking that into a custom rom? Is that even possible?
You may be able to extract certain packages from the stock/update 6.1 ROM that you may be able to use in cooking a 6.5 ROM.​
2. when you flash to a signed Rom image nbh file ... What is it replacing (ipl, spl, OS, splash, radio, xip, imgfs)?? all of those things or just certain ones? Do different nbh files replace different compenants or is it consistant to where an nbh file always replaces the same thing?
Everything that you'd find in a true/stock update ROM you'll find in a cooked ROM.​
I see in some of the kitchens... you can bake in your own radio, splash screen, etc... which got mo to thinking .... what will be different with the rom between baking one of those in vs not? It seems like it is optional.
Unfortunately, I don't use that kind of kitchen. I feel it makes my ROMs a little bit more 'bulky;' my ROMs seem to not compress as well with the newer kitchens, therefore, I don't use these options you're talking about. So, I apologize, I don't really know the answer to this.​
Thanks
You're Welcome​
Originally quoted from idunnoV2i:
would like a answer to this question myself...im only interested in the part about tweaking the original stock rom..can we beef it up at all?..change the pagepools..ect?[/QUOTE]
Yes, you can change the pagepool.​

Kaiser Danish[21/03/10][WM 6.5 Build 23544][DK][Native kernel 85MB][Extendir]

This is my first ROM I'm releasing.
I have created a Danish WM6.5 ROM with 85 MB free ram
I have done everything I can to make it stable and fast. I'm using it myself and I'm very happy with it.
This ROM is based on the latest Danish stock ROM I could get hold of.
I have removed some of the stock programs, and have added the following programs:
Code:
Bluetooth notifier
Mortscript (Un-Installable)
The ROM is extendir enable. You can everything about extendir here
This ROM is created with ervius visual kitchen
I thank everyone that have made this possible.
If I'm distribution anything that I shouldn't or haven't mentioned any people that I should then please let me know. It is not out of respect of other people, it is simply because I either didn't realize that I have used some of their stuff or because I have forgotten.
To use this ROM you must have a storage card for the initial flash.
First you extract the contents of the lagerkort.7z to the root of the storage card, so that you end up with a folder called extendir with a few folders and one file inside.
If you want some cabs to be installed as part of the new flash then copy then to the extendir\setups\<sub folder>. only cabs that are in a sub folder in setups will appear. So make one and only one level under setups for the cabs. (they will not be installed automatic, you get to chose which you want to install, so all all you cabs if you want)
Then you flash the ROM and leave the storage card in for the first 2 boots.
on 1st boot after you have calibrated the screen the customization starts, WM looks awful here, don't worry about this, as this step will extract all of the missing WM files to to the extendir folder.
On 2 boot the preset installer will boot and you can chose a few extra cabs to install and the ones that you have added.
You can download the ROM from here:
4shared
You can download the extra package here:
4shared
Congratulation and wellcome new chef
I suggest you to include some pics because you will be ask for that
Cheers.
Thank you.
Pictures added
Danish rom with Manilla?
Would it be possible to create a version with Manilla? I would really love a danish rom with Manilla and HTC Weather...
Regards Ulrik
I possibly could create one.
But I recommend that you install Manilla after with a cab, or with zip files (in the extender folders) this should give the fastest rom. I can help create the scripts so that Manilla will install on first boot if you want?
hey man i can't get the hardware keyboard to input properly for æ, ø, å. I looked through your cabs but don't see a fix do you have one?
I tried this SkandinaviskTastatur5.CAB and XDA_JCEspi2005_Danish_Input_Kaiser.cab neither of which work. Let me know if you have a solution
I have a danish keyboard on my too, and the mappings are just fine on that one. So have no idea what could be wrong, unless there are more than one version of a danish keyboard. I access my æøå by FN and <UP><DOWN><UP> respectively.
I forgot to mention that I'm using a different rom to yours. Maybe you need a Danish WM 6.5 to get the hardware keyboard to work. If you could help me out in anyway that would be awesome cause it's a bit frustrating hunting around to find ? and stuff heh
Ahh that explains.....
I have no idea how to get the danish keys then. If I knew what to put in it I could create a CAB file for you, but I really have no idea what to put in to this cab...
I had the same problem when I used WWE roms, and never got it sorted.
@ Blindpet, try doing this:
Use a registry editor and change the following:
HKEY_LOCAL_MACHINE\Hardware\Devicemap\Keybd\CurLang to 1044, this worked for me
I tried your ROM and overall its pretty good but i dont know if its my phone thats not set up properly but this rom have got a lot of screen lag though.
Anyway would be great with a proper danish rom for this great phone, keep up the good work
//KillerBee
EDIT: This solution doesnt work for me now.. I am not quite sure how you are supposed to change the HW keyboard language for a winmo 6.5 phone

Categories

Resources