[Q] Registry hive not saving changes - Tilt, TyTN II, MDA Vario III General

Hi i'm trying to change one key in particular for a build of Windows Mobile 6.5.5 Build 23569
I'm having trouble editing the default.hv registry hive. Basically i'm looking to implement registry changes prior to cooking the rom.
My process has been;
Copy default.hv (from SYS/metadata) to rgu-hv tool directory
Convert file to rgu
rename to .txt
add REGEDIT4
Make the following change;
GLYPHCACHE size to 16384
Save to .RGU, unicode.
Convert back to default.hv, At this point i've checked with HV editor that the entry has been changed correctly.
Reinserted into sys/metadata.
Flashed, And the registry entry is back to 8192.
What am i doing wrong? Is this the wrong default.hv or .rgu file to edit or is this key uneditable?
Thanks

[SOLVED]
Found out why it isn't saving, There is a duplicate entry in the following location, perhaps overwriting the original, Or maybe these are a prior extraction of default.hv.
In my case the location was 0409\Base_Lang_0409
and the file - 813fd1d1-ca6f-4b6d-96d2-c97fb99bd535.rgu
Once changed in this rgu. the change sticks and can be viewed by CeRegEditor.
Stoked

Related

Customizer.CAB - Registry changes in .reg instead of .CAB

When installing Customizer.CAB you will also install any .reg file found in Extended Rom. This way you don't have to make CAB's for simple registry changes. You can now quickly create .reg files to be included at hard reset.
.reg files in the following directories will be applied to registry:
\Extended_Rom
\Extended_Rom\REG
\Storage Card\Extended_Rom
\Storage Card\Extended_Rom\REG
\Storage Card\EXTROM
\Storage Card\EXTROM\REG
this way it will work with most of the custom WM5 versions.
How to use:
Add Customizer.CAB to your extended rom and add the appropriate line in Config.txt (CAB: \<extended rom>\Customizer.CAB
Then copy .reg files to any of the locations above.
Example of how to track changes in registry and create a .reg file:
1 - Use PHM RegEdit to export everything in registry to a new .reg file
2 - Make the neccesary changes to your device (Owner data, etc..)
3 - Use PHM RegEdit to export everything in registry to a new .reg file
4 - Transfer the two .reg files to your computer
5 - Use RegDiff (http://hp.vector.co.jp/authors/VA000007/regdiff.htm) to compare the two files and create a diff .reg file
6 - Remove unneccesary keys from the diff file (like state, date...)
7 - Transfer the diff .reg file back to your device
Hope someone will find this useful.

Personalising ROM's... without Ext_ROM

Okay, there a couple of CAB files I install no matter what ROM I use (Total Commander, Today Screen Speed Dial, MortRing [by .exe], Morphy's Call Filter etc), now that I'm getting to grips with the whole ROM building thing I have a question:
How can I add a program installed via a CAB into a ROM so that it is installed into ROM, I've searched on the forum and can't find much. I know it can be done as ROM's such a TuMa's, Logout's and Ivan's have apps in ROM which aren't there by default...
EDIT: In addition, I overwrite some of the default ROM stuff once I've installed (ETEN M600 Dialler in particular), so again, how can I get the 'bits' out the cab and overwrite the default contents of the ROM, this would make my life much easier...
If this has been posted previously then please point me in the right direction
First extract files, shortcuts and registry entries from the .cab using wince cab manager or similar http://www.ocpsoftware.com/, take note on what directory each file/shortcut is in. (often more reg entries will be stored as a file called 'platformxxx.reg' use these too)
Normal rom edit way: add the contents of the exported .reg files to default.rgu, making sure that you leave a blank line on the end, copy all the files to the \dump directory and edit initflashfiles.dat to copy them to the right directory on first boot. (remeber to remove the first two bytes - ff fe with a hex editor). then build your rom!
Bepe's rom edit way: create a folder '[your software name]' in the oem folder and get yourself a guid from here http://kruithof.xs4all.nl/uuid/uuidgen. create a blank file called '[yourguid].dsm and a blank text file called '[yourguid].rgu'. add the contents of the exported .reg files to '[yourguid].rgu' and make sure you save as unicode. then copy all the other files to the folder and create a blank unicode txt file called 'initflashfiles.txt' and use it like initflashfiles.dat in the first method except there is no need to hex edit out the first two bytes. then build your rom!
midget, you're a star, I thought it may be something simple... I'm off out with the family now for the day, but I'll work on this later, cheers!

initflashfiles.dat missing?

Hey!
I'm new to this stuff, don't be to hard to me!
What i have done yet:
1) Downloaded different Roms and created a dump of it, so i can compare them.
2) After this i, want to great my own Rom based of the German Qtek Rom.
For Comparison i took the "RIsidoro"-Rom.
i created of both the dump folder of the OS.
Now i want to add to the Qtek Rom for example CF2, Minimo and TotalCommander.
What i think i have to do:
-Copy the needed Files to the dump folder
-Edit the initflashfiles.dat
-Create a CAB in the Extended Rom to make the regestry entrys
My Problem is, i cant find a initflashfiles.dat in the Qtek Rom!
What i have done wrong?
Sorry for my bad english, i hope you can understand my problem
Thanks for your reply,
MAPero
Sry guys for post again.
But i haven't found any thing in this forum what could help me!
Everywhere is said, to edit initflashfiles.dat
But there is no initflashfiles.dat.
I have found a second way i think,
Normal rom edit way: add the contents of the exported .reg files to default.rgu, making sure that you leave a blank line on the end, copy all the files to the \dump directory and edit initflashfiles.dat to copy them to the right directory on first boot. (remeber to remove the first two bytes - ff fe with a hex editor). then build your rom!
Bepe's rom edit way: create a folder '[your software name]' in the oem folder and get yourself a guid from here http://kruithof.xs4all.nl/uuid/uuidgen. create a blank file called '[yourguid].dsm and a blank text file called '[yourguid].rgu'. add the contents of the exported .reg files to '[yourguid].rgu' and make sure you save as unicode. then copy all the other files to the folder and create a blank unicode txt file called 'initflashfiles.txt' and use it like initflashfiles.dat in the first method except there is no need to hex edit out the first two bytes. then build your rom!
Click to expand...
Click to collapse
But i am not sure, what is meant by oem folder!?!? is the dump folder meant?

Cooking a rom...

Hi, I followed the thread: "How to reconstruct a dumped ROM"... (obviously I had, before, did a rom dump!). Now I have a directory named "dump" with several subdirs.
In the step 3) there is written: "After this step you can optionally edit the OS files with the proper tools"... now the question is: what are these proper tools? I searched in the forum, in the other threads but I didn't find anything... My needs are: to delete some programs that are in the rom (for example Pocket Word, Pocket Excel, other..) in order to obtain more space, but to install other tools at the free space.
Thanks in advance for your help....
Great question ! i can't help you , but i wait for answers ....
I asked the same thing the other day, and got an answer(thx again to him).
Actually, I'm doing it right now, as a test I've successfuly dumped and rebuilt lsvw's rom using enhanced imgfs tools batch files, nbdump.bat nbname.nb & nbbuild nbname.nb, now I'm removing files from the rom and maybe add some other, like that quick gps thingy, latest msn(optimized for trinity, removed vga resources), phone pad, and some other thing on my custom extrom.
I had the same doubt as you, but it seems that we're overcomplicating things, you can simply use the file explorer to remove files from that dir, beware of which files you remove/alter.. initflashfiles.dat has some operations to be done after flashing the device(creating folders,renaming files, moving them to startup/start menu/etc folders), I thought that if the file didn't exist on the windows folder, whatever invoques initflashfiles.dat would crash, but it doesn't seem to be the case, I haven't put this to test, but I've found several missing files on the initflashfiles.dat(and a typo, "floder", go figure what it means - lazy/rushed editing IMO), so there seems to be some tolerance to the operations contained in that file.
I won't edit the wiki until I'm 100% sure that what I know is correct, but to sum it up:
dump the files
add/delete files with explorer
edit the registry using rgucomp
edit initflashfiles.dat using the original windows notepad & use an hexeditor to remove the 1st 2 bytes
run NBBuild.bat to create the *.nb file
OSchecker.exe to validate the *.nb file
nbhtool.exe to create the nbh
flash it(I prefer the sd card method)
Code:
rgucomp needs setting _FLATRELEASEDIR environment variable to current directlry like this:
set _FLATRELEASEDIR=.
Dump default.hv/user.hv file to .reg with:
rgucomp.exe -nologo -o default.hv > default.reg, then add line "REGEDIT4" to the beginning of REG file.
Modify the .reg file to your liking, (save it in UTF-16 with CR+LF terminations and a new line at the end of the file) and convert it back to .hv
And don't forget to flash Olipro's Hard SPL before, it may save your device.
"and convert it back to .hv"
http://forum.xda-developers.com/showpost.php?p=1186635&postcount=1
(no wonder I didn't find this info, forum search is almost useless, googled for rgucomp and voilĂ , first result(above) right answer)

Modification.

i cant find how to modify a ROM..
i mean after converting NK.NBF into DUMP folder if i want to remove any application and add another one how to do that?
like i want to add some plugins like arcsoft MMS,office and adictionary into a ROM how to do that..
thanx
well, that is done manually, you need to remove all the files/add the files from the OEM package there (exclude the option.xml and initflashfiles.dat and the dsm's and RGU) just copy the files, then when you goto the next step,or the step where you need to modify the HKLM and HKCU files, just open the OEM's RGU file, cpoy the keys and paste it in the Presented HKCU/HKLM and when you go to the other step, where you are required to edit the initflashfiles.dat, open the OEM's initflashfile in notepad, copy its content and paste it into the Main initflashfiles.dat of the ROM you are extracting, ther, that should do it
Note : make shure you hex edit the initflashfiles.dat and remove the first 2 bytes from the file (something like dd dd) or else your rom wont boot!!
if you dont want to hex edit, you can use my intiflashfiles Builder which is included in my kitchen, http://forum.xda-developers.com/showthread.php?t=378498
Ps. there is a guide too there

Categories

Resources