Related
Hi,
Im sorry if this has been discussed in earlier topics. Im wondering if its possible to include commercial applications such as SPB Pocket Plus, Pocket Informant etc... , into the extended ROM ? - this way you don't have to install them again in case of a hard reset. If it is possible , can someone please specify the details ....
Thanks.
you can add any application to the extended ROM if you have the CAB(s) file of the installation.
First, you should unlock and unhide the extended ROM using the required tools from this forum. Then add your cab file to the extended ROM, and modify the file named "Config.txt" by adding the new cab file name among the rest of cab files. After that, you should lock and hide the extended ROM back.
Biso007 said:
you can add any application to the extended ROM if you have the CAB(s) file of the installation.
First, you should unlock and unhide the extended ROM using the required tools from this forum. Then add your cab file to the extended ROM, and modify the file named "Config.txt" by adding the new cab file name among the rest of cab files. After that, you should lock and hide the extended ROM back.
Click to expand...
Click to collapse
Thank for the reply. However - most commercial applications such as those mentioned on my original post do not come in single cab files. They are usually come in single installation .exe files/
Any ideas ?
Check your applications installation directory or the 'Program files/Microsoft Activesync/yourprogram' for the CAB files.
and often exe install files for pocketpc
can just be renamed to zip and you can open them and copy out the cab
file you need
I was wondering if someone would share some information about low level modification of the rom kitchens. I have been working with Dog Guys kitchen and an original rom image and i have done some extensive modifications. Unfortunately, it is really just a cluged mess. The problem is that I don't know how to modify the underlying registry keys.
NOTE: I am not talking about *.rgu files in OEM packages and I am not talking about boot.rgu.
I am talking about the registry keys associated with the version of the compact framework built into the rom. Or the registry entries that define what applications are initially set on the program menu. Or the keys with the various application that are installed in the rom by default.
I have done a great deal of searching and I clearly don't know what the key words are to find this information. It must exist because both DCD and No2chem were able to either find it or derive it. I am just hoping someone will point me in a direction where I might be able to learn the next stage of rom customization beyond simply adding different OEM packages.
Thanks
most of the programs have their own folders. In each folder there is .rgu file. that file contains registery entries for that program.
in oem folder there are folders oemapps and operator. those folders contain more than one programs in one folder. all the registry entries that are related to all those programs are in one single rgu file in those folder. There are some registry entries in .provxml files as well.
when one file contains registry entries for more than one program, most of the entries that belong to a single program will be next to each other ( not always true )
a1jatt said:
most of the programs have their own folders. In each folder there is .rgu file. that file contains registery entries for that program.
in oem folder there are folders oemapps and operator. those folders contain more than one programs in one folder. all the registry entries that are related to all those programs are in one single rgu file in those folder. There are some registry entries in .provxml files as well.
when one file contains registry entries for more than one program, most of the entries that belong to a single program will be next to each other ( not always true )
Click to expand...
Click to collapse
Could you tell me where the registry information is for the contents of the SYS directory. for example where are the registry entries for SYS/NET. there isn't a corresponding .rgu file.
thanks.
sys folder has lots of other subfolders .. they have their rgu files.
There are some programs in bin format. they are already encoded i think.
You can put registry entries in a cab and put it in extened rom .. and run it after hardreset .. that way it will overwrite the original keys.
atomclock, I found this old thread concerning a solution and troubles with cooking .net CF 3.5 into a ROM:
http://forum.xda-developers.com/showthread.php?t=350279
Keystone said:
atomclock, I found this old thread concerning a solution and troubles with cooking .net CF 3.5 into a ROM:
http://forum.xda-developers.com/showthread.php?t=350279
Click to expand...
Click to collapse
Thats funny... That is the oem package I'm using in my rom.
There seems to be three possible avenues to work this issue.
1. Build oem's and hope that the registry keys in the oem's .rgu file COMPLETELY overwrite the original entries. (Oemizer is a good tool for this http://tiermann.net/index.php?optio...d=3:personal-oemizer&catid=1:Desktop&Itemid=3 )
2. Review the registry after a rom is written and create an xml file that will overwrite and delete all unnecessary registry keys (here is a link for anyone interested http://forum.xda-developers.com/showthread.php?t=366337&highlight=kitchen )
3. Get the inside information as to where the registry keys are actually located and make changes at the source instead of trying to patch it after the fact. (If someone has a link for this information please provide)
Why is it so impossible to get the necessary information to proceed with option 3.
I want to port the drivers from the current official rom to an old wm5 kitchen. I really need to get access to the underlying workings.
NOTE: I already know how to proceed with options 1 and 2. I need the information for number 3.
If you can answer the following question then you have the information I want.
Where are the registry entries for the BUILT IN .net framework (/SYS/NET)?
Thanks
UPDATE 12-21-08
There is some talk that you need to also install the Sdcerts cab before this process will work. Freezing the phone sucks so i would do this first. I will add it to page one.
After bricking my phone three times-I finally got it right. I have a HTC Touch Pro-nobody really explained it to me like I was a two year old-so I decided to break it down. You have to be careful or you will freeze up the phone and then be forced to hard reset. That sucks. So this worked for me. You should extract your own shellres.dll.0409.mui using rom extractor. This is not difficult if you follow these directions. All of the programs are free and I am making a zip to include them all. I included my own shellres.dll.0409.mui. The 0409 refers to the language. It is the code for English.
1. I installed the cab -icon demarrer. It makes a couple registry changes that help the process.
2. Then I used a the rom extractor to get my shellres.dll.0409.mui and copied it to the storage card you have to enter path:\windows\shellres.dll.0409.mui and save to \storage card\shellres.dll.0409.mui To install the Rom extractor You just put the Rom extractor into active sync
3. Then drag the file to the desktop of your computer use unsigner-just drag the file over the unsigner and it is unsigned
4. Then drag the same extracted file over reshacker and navigate the file to change string 321 in the shellres.dll.0409.mui to whatever you want it to say
5. Then open msigner and navigate to your saved file shellres.dll.0409.mui to resign the file
6. Then go to settings/today/items and uncheck to turn off touch flo and then copy the new file from your desktop to the storage card.
7. Install Total Commander on your device-you do this by opening it on your home computer. Then open total commander on your device and navigate to the new file shellres.dll.0409.mui-in the storage card. Then press the stylus on the shellres.dll.0409.mui file and save to clipboard
8. Then use Total Commander to search windows directory for the shellres.dll.0409.mui that is still in the phone. (If possible-rename the file shellres.dll.0409.mui.bak or if not possible press the stylus on top of the shellres.dll.0409.mui that is in the phone and selected for the drop down menue that appears-Paste Here.
9. Then soft reset. Here it is. I included everything you need in the Zip file! Here is where I started-but it is vague-great start icons in the thread though. http://forum.xda-developers.com/showthread.php?t=426264
The HTC start icon is on the zip entitled shellres.192.dll
Just say thank you if any of this helps you
language codes
Your can use the file I included in the zip if you do not want to extract. just change the numbers
shellres.dll.XXXX.mui in place of the XXXX It is 0409 for english-if you want another you can use one of these codes. If you don't have an htc touch pro the file may be named shellres.dll.96.XXXX.mui
0404 CHT Chinese Traditional
0804 CHS Chinese Simplified
0405 CSY Czech
0406 DAN Danish
0413 NLD Dutch
0409 USA English
0407 GER German
0408 ELL Greek
040b FIN Finnish
040c FRA French
040e HUN Hungarian
0410 ITA Italian
0411 JPN Japanese
0412 KOR Korean
0414 NOR Norwegian
0415 PLK Polish
0416 PTB Portuguese Brazil
0816 PTG Portuguese Portugal
0418 ROM Romanian
0419 RUS Russian
041b SKY Slovak
0c0a ESN Spanish
041d SVE Swedish
041f TRK Turkish
You can also change the Start Icon which is really cool. In my touch pro it is in file shellres.192.dll under icon group 4609-
1. Download shellres.192.dll to your storage card. Use total commander to search the windows folder for shellres.192.dll
2. Press the stylus on the file and select copy to clipboard
navigate with total commander to the storage card and press the stylus there and select "paste here"
3. Use unsigner to unsign the file
4. use reshacker to open the file and navigate to "Icon Group" 4609. You will see your icon in the program.
5. Select menu "Action" and replace. Navigate to the icon you want. Select it. Save the file.
6. Sign the file with the Msigner
7. Place the file in the Storage card
8. Use Total Commander to locate shellres.192.dll and rename it shellres.192.dll.bak
9. Use total commander to find your new file in the storage card, and move it to the windows folder of your device.
10. Restart with a soft reset adn enjoy your new icon.
Useful thread where I learned a lot http://forum.xda-developers.com/showthread.php?t=426264 You can get ready made .ico files here
Can you explain one point ... ?
I tried to extract the file shellres.dll.040C.mui (french WM6.0) directly into \windows, and before modifying the file with my computer, I just re-boot the device with that change (so, just a ROM file extraction but without any modification in the file) ... and then, the device is frozen on the Windows welcome page.
Can you explain that ?
louis09 said:
I tried to extract the file shellres.dll.040C.mui (french WM6.0) directly into \windows, and before modifying the file with my computer, I just re-boot the device with that change (so, just a ROM file extraction but without any modification in the file) ... and then, the device is frozen on the Windows welcome page.
Can you explain that ?
Click to expand...
Click to collapse
Did you follow steps exactly? You have to be careful. You can see from my screen shots that it works. I change my text every day as i feel. Did you install the icon demarrer cab?
you should also be able to navigate to the file shellres.dll.040C.mui (with Total Commander) and press the stylus on it and select copy to clip board. Then navigate to the storage card and press the stylus on a blank area and select copy here. The handheld needs the dll to work-so it is not removed from the device it is just copied.
Also make sure that your computers folders are set to view hidden files. It took me a while to get this right-and there is no step by step tutorial but the one i made here-from what I found.
Ok, but the result is the file shellres.dll.xxxx.mui in \windows
Whatever the handling, from the ROM to the SD card, to the computer, ..., the clipboard, ..., the file is finally copied in \windows
So, how can we explain that a direct extraction to \windows cannot work ?
Which operation in your process can avoid the problem ?
I don't want to modify the icon, just the text...
.. and I'm sure that works on your device, I have no doubt about that. I just would like to understand.
I also use Total Commander and it displays the hidden files.
What is the icon demarrer (french word ?) cab ? And what is the unsigner/signer method ?
louis09 said:
.. and I'm sure that works on your device, I have no doubt about that. I just would like to understand.
I also use Total Commander and it displays the hidden files.
What is the icon demarrer (french word ?) cab ? And what is the unsigner/signer method ?
Click to expand...
Click to collapse
The icon demmarer is a cab made by a developer. i included it, and all the necessary programs in the zip file. The cab just changes a few resgistry settings to allow this. (i believe) The file once copied to your computer can be manipulated and string value 321 changed-then compile script, save and sign. all included in the zip.
I want to know that you are able to do it, as I am.
louis09 said:
.. and I'm sure that works on your device, I have no doubt about that. I just would like to understand.
I also use Total Commander and it displays the hidden files.
What is the icon demarrer (french word ?) cab ? And what is the unsigner/signer method ?
Click to expand...
Click to collapse
I am having the same problem as Lewis and my device locked up twice at the windows login screen. You cannot modify the file with commander no matter what you do with your steps. There has to be something you left out. I am very good at what I do and am very far from being an ameteur
Chosen4Goodness said:
I am having the same problem as Lewis and my device locked up twice at the windows login screen. You cannot modify the file with commander no matter what you do with your steps. There has to be something you left out. I am very good at what I do and am very far from being an ameteur
Click to expand...
Click to collapse
Total Commander is only used to move the file-not modify it. Follow the steps exactly. Rename the old mui to mui.back.
and install the icon demarrer cab fisrt. Turn off touch flo before. I have a Sprint HTC Touch pro with a stock rom.
The cab demarrer may be strongly needed, or/and the unsigner/signer software ?
It should be useful to know what the cab and signer/unsigner do.
Which key in the registry is concerned ?
Is ResHacker needed ? Is ROM extractor not enough ?
And mainly, why does only an extraction to \windows freeze the device after a reboot ?
I'm trying to contact the ROM extractor developer VK (a.k.a. THEVK, GreateVK)...
louis09 said:
It should be useful to know what the cab and signer/unsigner do.
Which key in the registry is concerned ?
Is ResHacker needed ? Is ROM extractor not enough ?
And mainly, why does only an extraction to \windows freeze the device after a reboot ?
I'm trying to contact the ROM extractor developer VK (a.k.a. THEVK, GreateVK)...
Click to expand...
Click to collapse
You have to read this thread. http://forum.xda-developers.com/showthread.php?t=426264 Someone else made the icon dem cab. All I know is I read every page of every thread about this tweak-none was a road map-I just knew it could be done so I kept trying til I got it. I had to mod my start text from trying and reading. I finally got it with this method. the extraction alone will not freeze the phone-since the file is not removed from the windows registry. It is in fact not possible to remove shellres.dll.xxxx.mui since it is the entire shell of the phone.
Read every thread about start text
Ok, but the extraction will freeze the device if we do only this
So, this is the reason why the icon cab and/or one of the other operations avoid that.
Probably like Chosen4Goodness, I confirm that, if I extract the file and re-boot without any other change, the device is frozen...
freeze
Anxious to hear that someone other than me was able to follow these directions step by step and not freeze their device.
Don't worry, I'm probably not soo good !
or my device, or the WM version is too sensitive !
And it seems that many people succeeded ! There are a lot of evidences on this site.
louis09 said:
or my device, or the WM version is too sensitive !
And it seems that many people succeeded ! There are a lot of evidences on this site.
Click to expand...
Click to collapse
Be brave. Give it a go Louis!
louis09 said:
or my device, or the WM version is too sensitive !
And it seems that many people succeeded ! There are a lot of evidences on this site.
Click to expand...
Click to collapse
louis09 said:
I read in one thread how to change the word "Start". I tried to do it and I got a frozen device after reboot. So, a hard reset was needed. Another guy in this site got the same problem this week.
In fact, if I only extract shellres.dll.040C.mui (WM6.0 french version) to \windows\shellres.dll.040C.mui without any other change, I get the same problem.
So, maybe you can explain in more details how to do. Where to save the extracted file and to install at the end ? Is another operation needed ?
louis09
Click to expand...
Click to collapse
I couldn't send you a pm because you have your profile set to not accept incoming pm. Anyways, these are the steps that I follow to do this:
1. Extract shellres.dll.XXXX.mui via ROM Extractor;
2. Open it with ResHacker;
3. Look for String Table -> 321 -> Line 5120 and change this to whatever you want;
4. Hit "Compile"
5. Save the file. At this point, you will have two shellres files - one of them will have "original" in the file name. Just save that one in case you want to keep it.
6. Transfer to device via ActiveSync (USB, I haven't tried any other connection such as BT, Wifi, etc) into \Windows
7. Soft Reset your device.
How are you doing the transfer back to the device? It might be that the file is not transferring completely to the device, or getting corrupted in the process. TotalCommander, and Resco have not worked for me for this purpose. Give it a shot and see if it works.
Good luck and let me know how it turns out.
Ok, I have modified my profile.
I need a precise information about the location "Save to" in ROM extractor.
Because doing only that, to \windows\shellres.dll.040C.mui (the same file location than the ROM), is enough to freeze the device after a reboot !
So, why ?
I tried only that "simple" operation because I tried the 1st time the complete one (modify the file and transfer to the device) and I got the same problem. I believed that was due to the change in the file but the extraction is enough.
Maybe we have not to extract in \windows ?
louis09 said:
Ok, I have modified my profile.
I need a precise information about the location "Save to" in ROM extractor.
Because doing only that, to \windows\shellres.dll.040C.mui (the same file location than the ROM), is enough to freeze the device after a reboot !
So, why ?
I tried only that "simple" operation because I tried the 1st time the complete one (modify the file and transfer to the device) and I got the same problem. I believed that was due to the change in the file but the extraction is enough.
Maybe we have not to extract in \windows ?
Click to expand...
Click to collapse
My quesstion is why the reboot after extraction to save to \storage card\shellres.dll.0409.mui?
Also I think the last post above yours neglected to unsign and resign the file. I have fund that improper signing causes a freeze.
I know it is damn tricky since I froze mine three times, prior to doing it this way. Let me know how it goes.
I have no storage card. I reboot because I often close the device.
Could you explain the sign/unsign method ? That seems important as you say !
Which tool we have to use ?
louis09 said:
I have no storage card. I reboot because I often close the device.
Could you explain the sign/unsign method ? That seems important as you say !
Which tool we have to use ?
Click to expand...
Click to collapse
The programs are in the zip. But I think you need a storage card. That way the Mui file is extracted to something other than the phone itself. Get a storage card and then try it. They are not expensive.
Once extracted to storage drag the file on top of the unsign icon-it will flash and that is it. It is unsigned. Then open reshack and change out the word "Start"
compile script
save
Now drag the file over the msigner.
You will have to tell the program where to find the file through the interface of the msigner program.
It will sign the file and then you will have two shellres files. One will be shellres.dll.xxxx_original.mui or something like that. That is the old file.
place the new signed file in your storage card.
then follow the rest of the directions
I have getting bunch of errors while trying to cook a ROM, during the last step of creating registry....I get the error and here is what the log says:
importing registry file ".\Registry\084c771d-5dd9-42b3-847c-7862312d8e9d.rgu"...
Failed to parse HKEY_CLASSES_ROOT\_wgt_opwidget\Shell\Open\Command!!!
InitRegistry FAILED in file ".\Registry\084c771d-5dd9-42b3-847c-7862312d8e9d.rgu" within a few lines of line 7.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\084c771d-5dd9-42b3-847c-7862312d8e9d.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Can someone more familiar with the process point me to the right direction so that I can fix this error.
basically I took the 405.1 ROM
Extracted it
Using the package tool, I created a few new packages using the cab files
Included them in the "C:\RaphaelKitchen\OEM" folder
Then when I try to cook, I put a check mark for the specific app that I added and click the Go button and that's when I get the error.
This specific error is related to the latest opera cab that I downloaded from this forum. I deleted the folder that was (under OEM) there with the shipped Opera was and replaced it with the one I created when I created packages.
Thanks (this is my first time trying to cook so this issue might be related to something basic I missed, just need some pointers)
Package Tool has a couple of known issues converting from cab to OEM's, most likely there are spaces or something in your file 084c771d-5dd9-42b3-847c-7862312d8e9d.rgu" within a few lines of line 7.
You'll need to open that .rgu in a text editor capable of supporting unicode.
thanks for the quick reply
sorry it was actually a newer version of Opera that was trying to replace before building, not GoogleMaps
here are the first few lines from the rgu, i am not sure what the issue is, the file looks pretty similar to other rgus that I have (for TomTom7)
Code:
REGEDIT4
[HKEY_CLASSES_ROOT\_wgt_opwidget\DefaultIcon]
@="\\Windows\\Opera9.exe,-162"
[HKEY_CLASSES_ROOT\_wgt_opwidget\Shell\Open\Command]
@="\\Windows\\OperaL.exe""" """%%1"
[HKEY_CLASSES_ROOT\.wgt]
@="_wgt_opwidget"
[HKEY_CURRENT_USER\ControlPanel\Keybd\ChangeBackVKeyCode]
"Opera_MainWndClass"=dword:00000008
[HKEY_LOCAL_MACHINE\Software\Opera\GSensor]
"IdleTime"=dword:000000c8
[HKEY_LOCAL_MACHINE\Software\Opera\Proxy]
"ProxyServerPort"="8080"
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:DEFBROWSER]
"0"="Opera Browser"
"1"="\\Windows\\OperaL.exe"
"2"=dword:00000001
"3"=dword:00000000
Is it possible to leave the cabs as is instead of converting them into OEM package then compile them into the ROM so that the cabs get installed at first bootup after the ROM is installed? (during customization)?
Where would I put the cabs in that case? under the "OEM\OperatorPkg" folder or somewhere else if that's even possible.
I see the problem, typical issue with package tool. does not handle escape characters properly..
Code:
@="\\Windows\\OperaL.exe""" """%%1"
should be:
@="\\Windows\\OperaL.exe \"%1\""
Also, yes you can put .cab's anywhere you like in \OEM (all gets mashed into one folder at the end, simply split up for convienience)
Just be sure to add a reference to that cab to config.txt or config_operator.txt or one of those config.txt's so the autorun routine runs it
Thanks for taking the time to help
I took the second option with keeping cabs and updated the config file
downloading apps to sign the cabs now.
cab won't install, just get copied over into windows folder
Thanks Da_G
I am having some issues trying to cook a cab into a rom, here is what I have done so far:
1) Extracted ROM
2) Created my certificate, added certificate as trusted root cert on PC
3) Signed cab with my certificate
4) Put the certificate in OEM
5) included the cab in OEM (sub folder within)
6) Included this entry in config_end.txt (CAB: \Windows\Fuze_Keyboard_Fix.cab)
7) Cooked ROM
8) Flashed
What I noticed was that during customization (after install) the Fuze_Keyboard_Fix.cab got copied over into the Windows directory on the Fuze but it was never executed/installed.
Is there something I am missing in the process?
I followed this link in order to create certificate and sign cabs, when I got the certificate cab created, I used the package tool to create OEM package of that cab and put the dsm, rgu files here (D:\RaphaelKitchen\OEM\mycert_cert) and the cert in OEM directory
I am not sure what went wrong:
1) either the certificate is not getting installed (I am not able to find the certificate in \Windows, but them again I am not even able to find oem.cert which should be there as well)
2) Or the issue is with the signed cab and that cab not getting installed properly.
3) Do I need to included the cab name in AAInfo.txt?
Thanks.
problem solved
I am posting a new reply in case anyone needs to use the above info to troubleshoot and fix similar issues
This is what I did to fix the issue:
Code:
1) Only pasted copy of the certificate into OEM
2) Went into "D:\RaphaelKitchen\OEM\OperatorPkg\mxipupdate_oemoperators_104.provxml" and appended the xml provisioning code that was created during generation of the certificate
3) Signed the cab and threw it into OEM folder
4) cooked & flashed.
My Fuze now had the keyboard and Name display fixed on Rogers network.
I will just have to sign new cabs and throw them in OEM and recook and flash in order to add other things.
Hi All,
with all of the kitchens found here, it is noticeable that when adding any packages to the OEM/SYS folders (i.e S2U2) then trying to re-build the rom specially in the process of BuildOS we got many errors that file already exist and then crashes.
after many research i got to know that the package will extract the files in windows folder for all packages on time then while installation, the files will be copied to the proper folders.
here is the problem, once trying to re-build the rom all files will be copied in the same folder.
is there a way to avoid this?
Hi robekia1,
Even I am facing the same problem when rebuilding os.
we will keep waiting for the seniors here to deliver a solution for us.
thanks to whom will help in this regard
I also faced this problem while cooking ROMs, Hey krazy! help please.
I guess, if we could know the file structure from the folder structue before installing, then it would be easy.
hmmmmmmmm, it seems that this problem have no solution as (Finding emulator for cooked ROM)
done the same and working
robekia1 said:
I guess, if we could know the file structure from the folder structue before installing, then it would be easy.
hmmmmmmmm, it seems that this problem have no solution as (Finding emulator for cooked ROM)
Click to expand...
Click to collapse
Hey I have done the same previously I love the s2u2 applications so I have cooked my rom with all 3 apps of s2u2 i.e. S2U2, S2P, S2V.
I created packages from package builder, then copied all files to one folder.
removing duplicates with latest one.
Also I changed the initflash file for the locations which is created by the package creator with the new folders path.
Then also I added the all item tag in XML to detect DSM files of the respective apps.
Make sure you have registry hack for installing third party apps in your ROM packages.
Enjoy... you will get all your S2U2 apps in your ROM.
Right now I dont have the folder I will upload it tomorrow if anyone wants.
Hope this information is useful to you all.....
Please Dooooooo
bhushangahire said:
Hey I have done the same previously I love the s2u2 applications so I have cooked my rom with all 3 apps of s2u2 i.e. S2U2, S2P, S2V.
I created packages from package builder, then copied all files to one folder.
removing duplicates with latest one.
Also I changed the initflash file for the locations which is created by the package creator with the new folders path.
Then also I added the all item tag in XML to detect DSM files of the respective apps.
Make sure you have registry hack for installing third party apps in your ROM packages.
Enjoy... you will get all your S2U2 apps in your ROM.
Right now I dont have the folder I will upload it tomorrow if anyone wants.
Hope this information is useful to you all.....
Click to expand...
Click to collapse
Thnx a ton budy for this information.
really, i can't wait till tomorrow for this folder because i want to see all these modifications whitch greatly will help all ppl here.
please upload it ASAP.
also, what about Cooked ROM emulation? i hope there is a solution up there whitch i'm not aware about.
registry hack
bhushangahire said:
Make sure you have registry hack for installing third party apps in your ROM packages.
Click to expand...
Click to collapse
What you mean by registry hack? it sounds something new for me.
do you mean any registry editor? or it is another OEM Package should be installed along with the ROM?
robekia1 right, all file will be in windows folder, if you put it in the "program files" folder, the files exist in windows folder too, that is will be wasto your phone storage. Avoid put in the program files folder will be increase your phone memory.
Usually the default directory of the CAB file is in the progam file, and if you use OEM creator to that CAB, it will copied to Program file folder and exist in windows folder, to make only in windows folderyou can use this method:
1. edit the initflashdat result of OEM creator, delete all value of program file, or
2. Before you use OEM creator, edit the installation directory of CAB file, use wincab manager to do it, or
3. use wincab manager to extarct the files in the CAB, and registry, after that you can make .rgu, dsm, shortcut, manually and input the shortcut location in the initflash.dat file (I always use this method).
Usually every CAB file have different files with other, and if the have same file it can be same with the SYS file or the author/maker of the CAb is same. you can choose the latest version of that file if it happend.
While cooking even though we separate files inside different packages, but at the time when imgfs.bin is created, all the files go to \Windows folder. Thats why there cant be two files with same name even when they are in different packages.
Now some apps have common dependencies. Like the DirectShow and mHubVO dlls are needed by Youtube, as well as streaming media. Now what happens is, if you take two packages for these, sometimes the author puts the dependency files in both the packages so that if someone uses one package and not the other, it still works. This mostly happens packages that are made by converting a cab to a package. So if you cook these packages, you need to make sure that they are not putting duplicate files.
The same thing also happens with also happens with registry settings. Somtimes, two or more packages update the same regisrty keys in their .rgu files. SO we need to take care of those too and remove the lines that dont apply to the version of files we are actually using in our kitchen. This is a necessary evil and thats why cooking is not a child's play.
Once a ROM is flashed, and phone boots for the first time, the initialization process takes place. Now the ROM cooks have two ways to initialize their packages : using the .provxml files, this works if you have newer OEM* folders like from Elfin or Opal, it basically requires the Autoshortcut.exe file as well as newer HTCUtil.dll. The other way is the older initflashfiles.txt files inside the packages.
The difference between two methods is that using initflashfile.txt you can only copy files and create folders on the file system, but provxml can be used to perform many different things like registry values, applying themes etc.
So using one of the methods you copy your files to appropriate locations. Do remember that this process if done wildly can decrease the availabel free phone memory noticeably. Thats why we sometimes go a bit furthur and do some programming stuff to minimize this. You people sometimes dont even notice what is happening behind the scene.
I tell you one such experience. Google maps is a package that copies all its files to \Program Files\GoogleMaps but i noticed if i dont copy the files by deleting the initflashfiles.txt, and run GoogleMaps.exe from \Windows, it runs just fine. This works in pro user's rom but in Manila ROMs, the Maps tab of Manila looks for GoogleMaps.exe in Program files folder. So i had a choice to either copy googlemaps.exe into program files folder and waste 2 MB of phone memory or loose the functionality of maps tab of manila.
What i did was the third way i thought of myself. I created a .NET application called GoogleMapsStub.exe and what it does is it runs the googlemaps.exe from windows folder and passes all the information to it that manilla passed to it while running it. This exe is copied into the \program files\GoogleMaps folder by using initflashfiles.txt as GoogleMaps.exe. So now manilla is happy that it has googlemaps.exe in its proper place and i am happy too coz the new exe is only 3.5 kb in size You can verify this in v3.1.1 of VanillaManila rom. Look in the program files folder you will get the 4 kb googlemaps.exe, put it on your pc and check its version in its properties, you will get my name there And if you check the windows folder, there will be a googlemaps.exe of 2 MB size and a GoogleMapsStub.exe of 4 kb size.
So sometimes hacks like these are necessary in order to make a perfect roms. ROM cooking is just like food cooking, It may appears to be like just putting the ingredients into a cooker and light up the gas stove and wait for the food to cook. But if you try that for first time, your food will not be eatable for sure It requires a careful balance of salt, pepper and other things to cook a tasty dish I hope i have made myself clear
Wonderful
AMAZINGGGGGGGGGGGG PPL
latest buildos/ visual kitchen has option to delete duplicate file while cooking but
i will make new kitchen in future (not soon) because current kitchen work fine for me and i have lots of other work like android + building to rom from weekly leaked sys of wp 6.5
Thanks ankit360 for the visualkitchen9.7, i'm already trying to use it but the problem is: the ROM generated by the kichen is not working for GENE.
i tried another kitchen for the same ROM and it still working fine, the only problem with it is the duplicate
bhushangahire, i'm still waiting for you to upload your files.
also, what about the reg hacker?
Hi Karzy,
" What i did was the third way i thought of myself. I created a .NET application called GoogleMapsStub.exe " you answered one of my query unknowingly, when I had extracted your ROM, I saw there was GogleMapsStub.exe which was not present in any other ROM I had extracted. So I was wondering what that file was about !!! Now I know what it was.
Thanks a lot karzy for sharing this info.
You have been always good in explaining things indetail, which helps a lot for new comers like me.
I m glad that i am able to help my buddies here.
find the files below...
robekia1 said:
bhushangahire, i'm still waiting for you to upload your files.
also, what about the reg hacker?
Click to expand...
Click to collapse
Please find the files below sorry for delay.....
S2U2 Application OEM folder.
S2APPS.7z (786.47 KB)
Registry Tweak OEM Folder.
Registry__Disable - Security warnings when installing non-certified application.7z (849 bytes)
Please find the link to ROM with S2U2 applications + Antivirus.
WM6.5_Old_21231.7z (51.91 MB)
bhushangahire said:
Please find the link to ROM with S2U2 applications + Antivirus.
WM6.5_Old_21231.7z (51.91 MB)
Click to expand...
Click to collapse
i guess this ROM is for OLD gene???Correct me if i'am wrong...
yup for old
htc3400 said:
i guess this ROM is for OLD gene???Correct me if i'am wrong...
Click to expand...
Click to collapse
yup you are right this rom is for Old ..
If anyone want it for new gene please ping here I will cook it for new also....
Thanks
bhushangahire said:
S2U2 Application OEM folder.
S2APPS.7z (786.47 KB)
Registry Tweak OEM Folder.
Registry__Disable - Security warnings when installing non-certified application.7z (849 bytes)
Please find the link to ROM with S2U2 applications + Antivirus.
WM6.5_Old_21231.7z (51.91 MB)
Click to expand...
Click to collapse
Thanks a Ton bhushangahire for sharing those links.
I appreciate this.
Now, i'm gonna read them character by character