yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] dsixda:
I'm talking about Windows access when you open the folder.

I found a noticeable improvement in boot time when I removed HTC Home from my ROM. I prefer to have less files in \Windows :) However for my ROM I provided a separate HTC Home CAB with my customized icons and plugin.
[Touch GSM ROM Development] trueg:
Understood. Would having HTC Home installed as a cab after the fact decrease performance more than cooking it into the ROM? Do you offer the cab for installation in Onyx? Does weather work in both Manila2D and then assuming you turn off TouchFLO and enable HTC Home, does weather work there as well?
[Touch GSM ROM Development] dsixda:
I think the writable program area is a bit slower than ROM.

I don't remember if I tried HTC Home weather after installing Manilla. No one has complained to me yet.
[Touch GSM ROM Development] trueg:
If you install HTC Home after the fact and don't plan on using Manila2D afterwards, it would probably work fine since HTC_HDlg.exe would be overwritten and the correct location of the registry would be used. If they tried to use Manila2D without uninstalling HTC Home first, I imagine Weather would not work. I guess since both programs use the same exe you have to choose which one you want to use and use the appropriate HTC_HDlg.exe. You can't go back and forth without changing that file.

The alternative would be to rename the HTC Home version of HTC_HDlg.exe and somehow point HTC Home to use that instead.
[Touch GSM ROM Development] trueg:
OK, so I edited HTCHome.dll to point to HTC_HDlc.exe (copy of HTC_HDlg.exe), but now I don't have the option of HTC Home in the Today screen. Is there some kind of check to make sure HTCHome.dll hasn't been edited or modified? Sorry if this is getting outside the nature of this thread. I can take this elsewhere if you guys prefer.

edit: I just found on some other site that editing the file makes it so that the signature doesn't match up anymore. Anyway around this?

edit2: wow, I really need to search before I randomly post stuff, sorry guys. I found another thread about unsigning dlls before editing. I will give this a quick try.
[Touch GSM ROM Development] trueg:
Damn, that's f'n cool.

OK, so I renamed HTC_HDlg.exe & HTC_HDlg.exe.0409.mui to HTC_HDlc.exe & HTC_HDlc.exe.0409.mui. I unsigned HTC_Home.dll. Modified it to point to HTC_HDlc.exe instead of *lg.exe. Signed HTC_Home.dll. I stopped HTC Home and copied all 3 files to \Windows. Restarted HTC Home and voilla HTC Home & Manila2D can now run on the same machine without a file conflict. =)

Man, this stuff is fun!
[Touch GSM ROM Development] Noonski:
Yup that's basicly what it does.

Combine all rgu files into just a few, but it also does the same to the DSM files.

It leaves behind just a few .dsm files and in on it just leaves behind the reference to make a folder called "Cook your own Rom"

So this method already gives you a file reduction of at least 100 files in windows folder.

No when "They" start cooking everything is just like with you nice in OEM and SYS packages.

During the Cooking after using BUILDOS, all RGU files and DSM files get combined and a specific value is added to the DSM files left behind.

The DSM files ussualy are the files that help unpack a rom into the package directories.

Just open one up in hex or notepad from the Sys folders.

You'l see that inside it will contain the file names of all the files in that folder, so it knows where the files belong.

Since the DSM files get cleaned up, these references aren't there to tell where the files should go.

Unsinging?

I know of re-signing, (also in a little bit of a rut getting Newer USB Pop Upfrom Rapheal ported to Diamond but then as a dutch version)
[Touch GSM ROM Development] trueg:
Ya, I realized after that my ROMs are getting cooked the same way. I choose option one in Hybrid Kitchen which cooks a 'protected' ROM using Bepe Buildos. I'm guessing I wouldn't be able to dump my own ROMs.

Ya, I used an app called UnSigner.exe (downloaded from a different forum here on XDA). You drag your signed dll or exe over the exe and it removes the signature. I then used siggner.exe to add a signature once I was finished editing the dll.
[Touch GSM ROM Development] dsixda:
I used Ervius' build tool (it works better for me) and it looks like the Protection mode works on Elfins BUT not Elfs.. it causes the splash screen to hang. So i've gone back to Protection-less, which means more files in Windows.. 199 RGU+DSM files to be exact.
[Touch GSM ROM Development] !Aman!:
i've always used that protection on my ROMs and my ROMs work equally well on Elfs.
[Touch GSM ROM Development] dsixda:
Did you use Bepe's or Ervius?
[Touch GSM ROM Development] !Aman!:
Ervius... i always have
[Touch GSM ROM Development] dsixda:
Well I guess life sucks for me then.
[Touch GSM ROM Development] kokotas:
Hey dsixda!

When you're saying "it causes the splash screen to hang"

do you mean the "welcomehead" is not visible and you only get a white screen,

but the phone boots normal into windows?
[Touch GSM ROM Development] dsixda:
People with Elfs were saying "stuck at first screen", so no mention of a white screen.
[Touch GSM ROM Development] kokotas:
I thought you faced this issue yourself...Didn't get that you were talking about others:o

Because what I described above happens to me sometimes and I can't find the cause..only guessing something:D

Regards!
[Touch GSM ROM Development] :
Well, I was using the new XIP and SYS 20759 1.4.0, and I am getting the problem with my Elfin.
[Touch GSM ROM Development] ayyu3m:
what kinda problems bro..can u describe the exact problem
[Touch GSM ROM Development] dsixda:
I mean my Onyx ROM before I re-uploaded it with non-Protection. :)
[Touch GSM ROM Development] dsixda:
I've been using same XIP/SYS for a while now. It is only when I enabled Protection that the problem started to happen.
[Touch GSM ROM Development] :
The cooking went fine. But can't get my elfin to go beyond the splash screen.
[Touch GSM ROM Development] ayyu3m:
can you tell me the file size of ur RUU_signed.nbh file in terms like this 58.2MB (XY.Z)MB format
[Touch GSM ROM Development] dsixda:
I've seen this blank white screen problem that you mentioned. I think it happens if I don't have the registry set properly in my custom settings.
[Touch GSM ROM Development] :
It was about 63.58MB

I am using Hybrid Kitchen. Tried it with option 1(Bebe) and 2(Ervius). The cooking went smoothly with no error. But was confused to why it was stuck at the splash screen.
[Touch GSM ROM Development] dsixda:
Ayyu3m has a funny solution for XIP hanging issue, but it works for him! :D

Whenever I have a splash screen hanging, it is because I set the registry improperly.

For example, I may have set something like this:

[HKEY_LOCAL_MACHINE\SOFTWARE\XDA\TEMP]
"Default"="hello world"

But instead I should have done this (which would prevent a splash screen hang after flash):

[HKEY_LOCAL_MACHINE\SOFTWARE]
[HKEY_LOCAL_MACHINE\SOFTWARE\XDA]
[HKEY_LOCAL_MACHINE\SOFTWARE\XDA\TEMP]
"Default"="hello world"
[Touch GSM ROM Development] ayyu3m:
okies. can u add an extra ringtone (less or equal to 100kb) file or anything else for that matter and try to make the file size 63.6MB

of coz logically rounding off 63.58 gives 63.6. but this doesnt happen on a physical level

try it with any kitchen you like bro..and lemme knw
[Touch GSM ROM Development] Noonski:
Yeah i also stumble upon this sometimes.

What might help is making the OEMAPPS, OEMOPERATORS and OEMDRIVERS .dsm blank (start with only one).

I got this mostly when i update ed apps that where allready in one of those folders but then got moved to their own separate folder.
[Touch GSM ROM Development] :
hmm...I didn't even look at the registry. :D

I was actually trying to keep the RAM low, and deleted a bunch of junks. :D
[Touch GSM ROM Development] ayyu3m:
anhaaaaaaaaaa Noonski, ma man! still with us eh man. :D :D
[Touch GSM ROM Development] dsixda:
Ohhh ok. What do you mean by "start with only one"?

ayyu3m, you wanna beta test on your Elf for me later tonight? ;)
[Touch GSM ROM Development] :
My OEMDrivers has one .dsm, and nothing for OEMOPerators and OEMMAPPS
[Touch GSM ROM Development] dsixda:
This is what I have:

OEMAPPS --> has RGU and DSM

OEMDRIVERS --> has RGU and DSM

I don't have an OEMOPERATORS folder, I removed it.

So shall I remove the DSM from OEMAPPS and rebuild? Is that what is meant? Or do I delete it after building?
[Touch GSM ROM Development] :
Sorry dsixda, that was not a statement, but rather a question to Noonski.

My OEMDrivers has one .dsm, and nothing for OEMOPerators and OEMMAPPS

My three folders are missing .rgu . (wonder if that is the issue)
[Touch GSM ROM Development] !Aman!:
why so much fuss about these dsms :D? just rebuild them using dsmbuilder, no need to worry about rebuilding a dsm. i always rebuild my dsms in XIP, OEM or SYS after i delete/add some files.
[Touch GSM ROM Development] ayyu3m:
of coz ma man...my elf is like an open book for you to write on. keke
[Touch GSM ROM Development] ayyu3m:
yeah DSM builder does save you a lot of hassle on anything DSM related

:D
[Touch GSM ROM Development] dsixda:
You mean this one?

http://xdaforums.com/showthread.php?t=412272

You mean you have to individually select and rebuild every folder that has a DSM?
[Touch GSM ROM Development] dsixda:
I'd like to buy your Elf ;-)
[Touch GSM ROM Development] ayyu3m:
no way man...jus carry the DSM builder over the same folder which has SYS and run the tool...it will rebuild
[Touch GSM ROM Development] Noonski:
It's because they way they get merged into a few that causes a stuck at Splash screen bug.

Maybe something to check with Bepe.

And DSIXDA i meant only make one of these folders DSM files blank (So you can pinpoint which DSM is causing the problem, so you can then rebuild that DSM file and see if the problem dissapears)

The problem most times is not registry related.
[Touch GSM ROM Development] ayyu3m:
haha...well..you cant have all the luck :P
[Touch GSM ROM Development] dsixda:
I guess I'll try out DSM builder... but I'll need an Elf-owner's help :)

now.. where can I buy an Elf (not Elfin cos I have two!!)? ;-)
[Touch GSM ROM Development] Noonski:
Two is not enough ?

I'll be able to Test it to.

And euh maybe this would be fun.

http://xdaforums.com/group.php?groupid=24
[Touch GSM ROM Development] dsixda:
HA HA! Nice group, you two ;)

I need an Elf to solve those DSM issue and also memory testing. I can always trade my spare Elfin for a spare Elf ;-) But I don't have a shipped ROM or goldcard ROM for it.....
[Touch GSM ROM Development] ayyu3m:
jus when we thought Goldilocks was the "ONE"

oh well...somebody peek in on matrix and get NEO...come on!!!
[Touch GSM ROM Development] dsixda:
That's why it's called a "Limited Unbricker" ;-)
[Touch GSM ROM Development] ayyu3m:
:eek:

of coz this post got EDITED. keke
[Touch GSM ROM Development] dsixda:
What're you talkin' about, I went into retirement mode ;)
[Touch GSM ROM Development] ayyu3m:
ohhh...damn! i gotta update my news now...

okies bro..shows over...we have a grandpa going for early retirement

keke ;)
[Touch GSM ROM Development] dsixda:
How the heck do I use this dsmbuilder.exe? What do you mean to carry it over the folder? If I load a DSM in it, it gives me an Access Violation. I'm using the one mentioned in that URL from a few posts back.
[Touch GSM ROM Development] Ameet:
Sometimes a blank dsm gives you that error. Gave me errors especially on the dsm files created by the package creator. Best way to edit through the DSMBuilder is to asctually build a dsm file with itself or use the BuildDsm.exe to create a dsm and then edit that in this proggy
[Touch GSM ROM Development] dsixda:
So does that mean I have to go through every single folder and build the DSMs individually??
[Touch GSM ROM Development] dsixda:
This is really bizarre ---- I still can't figure out how to set the FingerPressure to a custom value that sticks in the ROM. I have put the value in a PROVXML and in a custom RGU (like any other personal regsitry setting), but after flashing it gets reset back to 2700 or a random value that is close to 2700.

I then used a MortScript and put the registry setting script under the Windows\Startup folder, and after flashing the ROM that didn't work either, UNTIL I soft resetted it. However, I don't want to leave a script like that in the Startup folder, because if someone decides to change it to their own preferred value it will get overwritten by the value in Startup after reboot. I prefer to have my custom default in the RGU.
[Touch GSM ROM Development] !Aman!:
generally not required for SYS. if u do that in the OEM alone, that is enough. as far as your own OEM packs or opal's oem packs are concerned, u can remove the original dsms altogether as empty dsms will be generated automatically by the kitchen with the uuid same as the rgu
[Touch GSM ROM Development] Noonski:
Hehehe, Another Vote for Manual Package Creation, or at least clean up the initflashfiles Package creator makes and remake the DSM file.
[Touch GSM ROM Development] dsixda:
So I should remove every single DSM in the OEM folder and then build my project again with Ervius' tool?
[Touch GSM ROM Development] dsixda:
Ok another question --

I've seen some discussion in the past about the SYS/SQL* folders. I've seen arguments for and against removing them. I currently have SqlCeMobile, SqlCeMobile_LAng_0409 and SQLCE. They are about 3.5MB total. Can they be removed or are they required for indexing certain things in PIMs and folders??
[Touch GSM ROM Development] !Aman!:
i would say just rebuild the dsms for various folders inside OEM using DSMbuilder.exe. there are only 7-8 folders and that won't even take 5 minutes. as for all other OEM packages like M2D, randomaccess, etc etc if u are using the original dsm, u can delete all of those.
[Touch GSM ROM Development] !Aman!:
i advice against the removal of SQLCE. other 2 could be deleted if u like, they are not much useful i guess, never had them in my ROM.
[Touch GSM ROM Development] dsixda:
BTW Do you put all your programs (M2D etc.) under OEM\ or SYS\? I have them all under OEM. That probably is another problem of mine.
[Touch GSM ROM Development] !Aman!:
i use Ervius' kitchen, so i have all of them inside "packages" folder. but it doesn't really matter if they are inside OEM or SYS.
[Touch GSM ROM Development] :
I place them all in SYS folder, for my OEM is blank and it is fine.
[Touch GSM ROM Development] Ameet:
This usually happens when the align screen is run after the provxml is applied. Noonski was my teacher for UCE with his trick of making Mort run the provxml after the align screen ;) Well, in a way

Thats an idea which is workable :) Normally you may need to update the dsm only if you have added any files to the package
[Touch GSM ROM Development] dsixda:
Maybe that could be why the "Check Names" feature in pocket outlook is not working for some users in your TESS ROM? Or did you find a solution for that?
[Touch GSM ROM Development] !Aman!:
that feature always works for me, i can't help others much over this issue.
[Touch GSM ROM Development] dsixda:
Do you have a link to this trick? I'd like to use it! Would save me all that time wasted flashing.

That would be easy to do it in all one shot (searching for *.dsm instead of going into all folders one at a time), but all of a sudden the Search function on my XP no longer works and causes my taskbar to hang now :mad: (EDIT: Nevermind... I googled and found out that if My Documents is no longer the first icon in your desktop then Search stops working. Stupid Windows.)
[Touch GSM ROM Development] Ameet:
Dont have those files with me, remember my HDD crashed liked a plane crash :( Lost all the data. But Noonski has his package, maybe you might have to edit it a bit here n there
[Touch GSM ROM Development] dsixda:
Ok thanks.. Hey Noonski, can you help me out bro? In the meantime I'll search around the forums as well. I just started using and scripting with Mortscript yesterday.. it is very useful.

BTW I remembered to back everything up yesterday to extra drive (all old ROMS and kitchens). To start with, use Acronis to back up -- what a useful program.
[Touch GSM ROM Development] :
Question

I am using DSMBuider to build dsm for my new OEM to my new SYS for OS 20921移植资源.

My question is: The program ask for version? If I leave these blank, I will get an error when I tried to build the rom. I examined other OEM files, and for example with Opal ROM. In OEMAPPS: version is 19.3.126.707 and in OEMVersion: version is 86.6.8100.707.

So how do I know what version to enter for the new OS 20921移植资源? HELP!
[Touch GSM ROM Development] Noonski:
Well you got mort cooked in don't you.

I deleted welcome from windows\startup in the initflashfiles.dat.

Then made a mort script that runs at first start that does some stuff and copies the next mortscript.

initflashfiles.txt

Directory("\Windows\StartUp"):-File("ReplaceFileOperations.mscr","\Windows\RFO.mscr")

RFO.mscr

Copy( "\Windows\CLASC.mscr", "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "system", FALSE)
Delete( "\Windows\StartUp\ReplaceFileOperations.mscr" )

Then at second boot after Autorun is run and reboots

CLASC.mscr

PlaySound("\Windows\Startup.wav")
RunWait("\Windows\welcome.exe")
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "system", FALSE)
Delete( "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )

These are just the snippets from the whole script to run welcome wizard after PROVXML and stuff, there's a lot more going on in the ones i use.

That would overwrite any PROVXML setting from welcome wizard being aplied at first boot.

At least i just quickly looked and think that's what Ameet meant.

I don't have a complete grasp of the problem but the above trick might not help with the finger presure issue.

Still using the old fashioned way with that sole BUILD dsm file from Hypercore kitchen.

Dropping the folder on the builddsm.exe (temporarily taking out the initflashfiles.txt and option.xml)
[Touch GSM ROM Development] Ameet:
God I miss my old ROM data after mr HDD crashed :( How we wrote scriots that could write files out of thin air :D

Also with this script, there could be a provxml that gets applied or a rgu entry with the current screen alignment data which can help in the next welome screen :)
[Touch GSM ROM Development] dsixda:
I also want to make sure it gets applied once after flashing, and not all the time (if user wants to set his own value). Does this do that?

I may just skip all this and let the user take care of it, because it looks like it does a customization and 2nd reboot.

Thanks Noonski
[Touch GSM ROM Development] Laurentius26:
Hi guys,

Can I still join this cooking class, looks fun! :D

Great work Noonski!

Grtz,

Leo :)
[Touch GSM ROM Development] bydaimon:
ababrekar your data on HDD even it`s crashed , you can recover all you data with some programs !
[Touch GSM ROM Development] Ameet:
Nah!! It crashed like a fighter plane going down like the black hawk :( HDD already repartitioned. Htctouchp knows how badly I've taken few files from him for me Elfin before going after the Diamond :D
[Touch GSM ROM Development] bydaimon:
sory to hear that !:(
[Touch GSM ROM Development] Noonski:
Well that should teach you not to have an open Kitchen that you can download older versions from ;)

Didn't you Pass the Kaiser Kitchen Cooking Class?

I heard you already had a pass to the Black Lodge.
[Touch GSM ROM Development] vadyarik:
Camera 6.13

Elfin_Camera_6.13_32715 :)
[Touch GSM ROM Development] Noonski:
Cool Bean Thanks for sharing.
[Touch GSM ROM Development] dsixda:
Any improvement in this camera compared to, for example, 5.09?

Where'd you get this?
[Touch GSM ROM Development] trueg:
Has anybody tried this yet? Any benefits? Vadyarik, are you able to let us know where you found this, or is it a secret? =)
[Touch GSM ROM Development] dsixda:
I tried it.. The interface is easier to use with fingers than before, but I was unable to unlock the Panoramic stitching mode (even though I set the proper part in the registry). There's probably a way. Themes are also missing.
[Touch GSM ROM Development] trueg:
Would this have been hacked up from a different device or is there a newer ELFin OEM floating around somewhere?
[Touch GSM ROM Development] kokotas:
Thanx vadyarik for the new Camera cab!

I hope you don't mind posting here the OEM Package from that cab too..

And I hope that you have more goodies for us in the near future;)

EDIT:

Attaching a fully working OEM Pack, cause the previous one was missing the Theme function...:o
[Touch GSM ROM Development] ayyu3m:
thankx man! i was gonna prepare an OEM pack myself for this. :D
[Touch GSM ROM Development] letama:
Feedback from a rookie cook and a question

Hi guys,

I finally managed to cook a rom for my touch. I spent a good week learning stuff around and want to share a few mistakes I made to help newcomers:

1) Don't use hypercore if you want to upgrade XIP and SYS, use Hybrid Kitchen instead.

2) I used sample4cookingbase + oemv2 from ameet and had problem with playing mp4 files: the issue is in mxip_WMPlayer_Regs.provxml in OEM_Lang_409, it has some quotes missing. I removed it and voila!

I still have one issue remaining: I can't flash my rom from SD. If I add some dummy files to make it above 50M and flash it with RUU, no problem, but if I rename it and tries to flash it from SD, the bootloader doesn't recognize it. The card is working fine with Ameet's one or Tess, it's only with mine.

Is there anything to take care of to be able to flash it from SD?

Thanks,

LeTama
[Touch GSM ROM Development] trueg:
In order for my ROMs to flash from SD I have to make sure I set the model ID to ELF010150. If it is set to ELF010050 or anything else really, then the bootloader doesn't recognize it as a valid ROM for flashing.
[Touch GSM ROM Development] letama:
Thanks! I changed the ModelID and it worked.

I faced another issue, the same one that Ameet had with his last SD UC: it seems that if the ROM is too small, some files can't be read anymore (boot pictures, today background...). Not a big deal, I added a few packages to make it bigger and it works now.
[Touch GSM ROM Development] Noonski:
I heard that the File size of the rom limitation, is no problem with the newer SPL.

But HTCTouchP and Ababrekar and some other now more about that.

I've been with my head in the Diamond and Wizrd so much lately i haven't followed some of these progressions on ELF lately.
[Touch GSM ROM Development] Ameet:
True. With Aman's latest USPL you can now flash any size ROM with the RUU. I wonder when we get one of that for Diamonds :D
[Touch GSM ROM Development] !Aman!:
yeah, with new USPL we don't need to worry about the ROM size being less than 50 MB. i'll also enable this feature in USPL 2.26 soon.
[Touch GSM ROM Development] letama:
Thanks Guys! I flashed latest SPL, it works perfectly now.
[Touch GSM ROM Development] humrod:
Problem with the notes

Hi everybody: I'm making some experiments upgrading a WM6 to WM6.1, by changing the MUI carpets and all work ok, instead of the notes, that not open. I'm look the files and seems to be ok: the notes.exe in windows, the notetake.ink, and by the way i don't touch anything in the notes.dll in dump.

anyone has an idea.....where to start?.....something i miss?

Thank's in advance
[Touch GSM ROM Development] Ameet:
Which build did you use the notes.exe from? Try using the notes.exe from 19958 build and try again. Check the link to notes.exe in ini*.dat in OEM_Lang_xxxx
[Touch GSM ROM Development] humrod:
Thanks ameet, you sugestión works perfect. BTW, when we manipulate or change the os applications and in general several programs, is possible to edit the os versión (if in case how) or it depends on certain files?

Thanks again for your comments

p.d.: or it's a forbifden stuff (in that case sorry)