yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] Noonski:
I was just trying to challenge you. We'll get to know each other well enough.

It's just that i might have had long toes. Because we haven't really achieved a lot yet to simply take someones hard work modify it and stick a new name on it. We could also present fixes to his kitchen. But that's not saying a different name will never happen. Let's earn some feathers first.

As for a base rom, Well that's a discussion in itself.

I think that most bases around have one thing in comon.

They don't work when you remove to much files and they all look the same.

That was something i was going to add to upper threads. Remove-able Files. I think any files that you can succesfully remove and make a seperate Package for should me removed from OEM to Sys. And then find a minimum slection that will keep the device running.

As example "INTERNETSHARING" should be tagged with an option.xml file just so that every piece gets selectable in kitchen. It doesn't really matter a lot if you use one "INTERNETSHARING" in a different Base Rom anyway bacause there's not any big dif in the roms and all files are signed the same way anyway. I think making Packages out of anything in Sys is a must if you want to find a perfect vanilla.

The eventuall Rom being flashed needs to be a minimum size or the flashing tool wil give an error so we need to test flashing with different settings. If this doesn't make sense yet it will.

Just take the entertainment package attached below and replace it with your extracted versions. (it needs an initflashes so it's not finished yet)

Its part of OS but you can easily just take it out in BUILDOS. It will not Kill your OS. Now all these folders need to be mapped and indentified if other folders also belong to it. Then make an option.xml file for it. Only when all Sys folders are mapped and tagged can you start flashing different combo's. For instance not flashing Shell will kill the phone. So why not test a flash where you just put Shell folder inside OEM? And get it out of the kitchen. Or we can even move OEM folders to sys folder. It shouldn't matter should it.

What i'm trying to say, the above material should be enough material to **** around with, and just say what you tried moving, removing and what effect it had.

Let's just start trying stuff and worry about future later on.

First you break it apart, and then you build it back up again.

Any Touch Rom will do.

Anyone having any issues with the Extracting Part of NBH file?
[Touch GSM ROM Development] eefurt:
base rom

Hi all,

what is a good base-rom to start cooking from?
[Touch GSM ROM Development] Noonski:
Dopod Asia WWE 1.17

Uploading RUU_signed_OS5.2.1437.zip

Added to Thread 9

Thread 9...... nice name for a Band!
[Touch GSM ROM Development] tiggerbcn:
Thanks Noonski, for this interesting post, it is of great help for those that we cook roms, I am cooking roms in Spanish but I have a small problem that not solving and is to define a topic for defect, want that the topic that goes out the first time is not the HTC_Default.tsk, but one created by me.

Does anybody know as to do it?.

I have modified in the file tmxipupdate_zz_oemoperators_101_PPC+_All_HTCThemeLayout.provxml

this (mark in red):

<wap-provisioningdoc>

<!--

=======================================================================================

HTC Theme layout: Htc_default.tsk

=======================================================================================

-->

<!--Cust_HTC-Default-TSK.xml-->

<characteristic type="Registry">

<characteristic type="HKCU\Software\Microsoft\Today" translation="filesystem">

<parm name="Skin" value="\windows\ttb.tsk" datatype="string" translation="filesystem"/>

<parm name="UpdateFlag" value="1" datatype="integer" translation="filesystem"/>

<parm name="Restriction" datatype="integer" value="2" translation="filesystem"/>

</characteristic>

</characteristic>

</wap-provisioningdoc>

but the HTC_Default.tsk keeps on going out for me.

The file is ttb.tsk in the rom

Grettings
[Touch GSM ROM Development] Noonski:
Anyone Any Idea? About the TSK issue i never delved into this.
[Touch GSM ROM Development] bram_smulders:
You can do it with the ext-rom, but your storage memory drops by 10 megs.

I've seen another solution but i cant find it anymore. If i find it ill post it right away.

gr. bram
[Touch GSM ROM Development] mzmiric5:
The thing is that u probably edit HTC_default.tsk, thath's why it auto picks it, try adding a rgu that will edit the registry settings for skin. I will check for more precises data when i get my phone back. Or u could rename HTS_default.tsk to HTC_original.tsk and rename yours to HTC_default.tsk. Hope i helped.

OFFTOPCI: What is the best screen protector that i can get for touch besides HTC SP P130. PM me with an suggestion.
[Touch GSM ROM Development] Noonski:
Adding it directly to skin results into other weird behaviour when you switch themes. It will switch the bar color but retain the Background image or something like that. Why isn't it possible to run Fake Autorun from different location then Ext_RoM? I think i've seen somethng like that somwhere.
[Touch GSM ROM Development] Cloudyfa:
Make sure that Autorun.exe, CusTSK.exe and Config.txt are in your ROM (they're usually in ExtROM).

Edit rgu (in some cases, it's in some provxml files), and modify this reg:

[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG="\\[COLOR="Red"]Extended_ROM[/COLOR]\\Config.txt"
"AutoRun"="\\[COLOR="Red"]Extended_ROM[/COLOR]\\AutoRun.exe"
(change [COLOR="Red"]Extended_ROM[/COLOR] to [B][COLOR="Red"]Windows[/COLOR][/B])

Then modify Config.txt, add this line:

EXEC: \Windows\CusTSK.exe \Windows\[COLOR="Red"]Your Theme[/COLOR].tsk
[Touch GSM ROM Development] Bono2007:
Thank you for the update of hypercore, it works great now with HTC ;).

I'm looking for a thread that can explain me how to "install" 5.2.1978 version on a 5.2.1238 old version. I have no idea about it. Just replace .exe and .dll ? :eek:
[Touch GSM ROM Development] tiggerbcn:
The file config.txt does not exist. I will try it creating and changing these lines. Thank you

EDIT: It does not work, on having started remains hung on the screen of calibration. Thank you anyhow, in the end I have changed the values of the color putting those that my topic was giving me and it has worked.

[HKEY_LOCAL_MACHINE\Software\Microsoft\Color]

"SHColor"

"BaseHue"

"Restriction"

"DefSHColor"
[Touch GSM ROM Development] Seiya:
It works

but have uou save the config.txt file in unicode?
[Touch GSM ROM Development] Noonski:
********ing****.

No kidding i posted that Fake Ext rom solution earlier today.

In that post just a few above.

Really... but it didn't save. hahahaha **** ****.

I'm without I-Net so i'm doing everything over GPRS, so that might explain it.

Good thing it's posted anyway.

I'll haven't tested it myself, because i finally found out what was going wrong with default.rgu to default.hv consersion so i've been porting a lot of my registry settings to hive to clean up the rom some more. So this is going to take some time to make it neat.

Now here's another good one. Does anyone know which registry settings need to be changed to have the Longpress of red dialer endkey open a specific exe file. Because the new EndKey.exe App is of no real use if it can't be mapped to that long press.

Same goes for long press of power key. I would like to map psShutXP to that......
[Touch GSM ROM Development] starlit:
Hi Noonski,

I am using the PDAVIET and having some issue with "notes" in some of the latest versions. Wonder if you could advice me how I can extract the files from a pervious rom and insert into the current one. Or how I can extract and make a cab file, so I can sort of "patch" the problem. I suspect that the exe file may be corrupted, although there may be a million other possibilities like link file, registry ... etc.

I tried copying the file out using explorer but it says I cant copy a file in the ROM :(

Thanks in adv!!
[Touch GSM ROM Development] Ameet:
Where did you guys find the HTC Opal's ROM or its packages? :D
[Touch GSM ROM Development] dsixda:
In this thread :) Keep looking several posts earlier.

Also look here! http://xdaforums.com/showthread.php?t=425694

BTW Ameet, do you or anyone else have a black smart dialer skin??? None of the skins I see have smart dialing support, especially for the dialer by DxC.
[Touch GSM ROM Development] Ameet:
I have the Diamond black skin by poorlyduck. Btw, the TF2D works on my device but how do I make it full screen?
[Touch GSM ROM Development] dsixda:
There's a Large Title Bar OEM for the Opal. I think that does the trick? Just wait for Noonski to wake up :)
[Touch GSM ROM Development] dsixda:
Thanks!! And it has Smart Dialing! :D
[Touch GSM ROM Development] Ameet:
Wasnt actually talking about large title bar :) Have that already but wanted to know how to make the TF full screen. Or is it right what is seen in the screenshot?
[Touch GSM ROM Development] dsixda:
Sorry, I'm stupid.. even I got mixed up and deleted it from my kitchen even though I already flashed it earlier (the one with the volume icon and wi-fi etc. enlarged when you click on them..) :P

Anyways, I'll shut up now and let the experts figure it out .. hopefully in a few hours ;-)
[Touch GSM ROM Development] Noonski:
Well around here i have no problems saying that L26's Dump was actually more then enough because it turns out it did have the Hives files.

But then i went and got them from Ervius undumpable rom anyway and from that point it was women and children first.

Must say that it's to bad Gullum went underground and now prolly has everything working. But i can't blame him. after all the other hard work of him on some other ripped and ported apps and so many other Cooks using them and getting loads of donations.

But VetVito did some very fast comparasing of the files and secluding them into separate Packages.

I'm trying to now See why some packages work for him but not directly for Elves so true correct packages can be posted.

And since i was already working on the volume/startmenu & titlebar it was easy to finish these and make them Public.

But it looks like many are simply going to make roms either without proper fixes or for two minute fame of bringing out a ROM with Fixes.

(And in Gullum's case i think it would be deserved)

But any other Cook bringing out M2D without ever having contributed to the whole Public work, will be on my personal BlackList.

You can clearly see how many OEM packages have been downloaded for some of the apps. So i reckon half of that number has ran the M2D cab thro

You guys where right. (so was i)

ELVES is tight As Shizzle.

And truth is if the M2D thread in the ELF Forums did not get started.........
[Touch GSM ROM Development] ayyu3m:
how was ur sleep man...since u posted u were goin to sleep...i thought u gonna have a week's sleep and wudnt be up early...but you are here! ;)

hehe...and ELF is tightier as Shizzled...
[Touch GSM ROM Development] Ameet:
Herg's ported cab is about 14MB with unwanted proggys. I mean, I removed the title bar, taskmanager since that was making the TF2D so sluggish and also for external installation. Got the ab down to 11MB :) Sounds cool

Any idea what might be causing this? I get this after clicking on Music Tab in TF2D

If the MOD think this is in wrong section, then you may please move this post. gehehe.. Always wanted to write this :D
[Touch GSM ROM Development] dsixda:
Are you guys having trouble with the Opal Large Start Menu? It works but the recent programs' icons don't show. I'm not using Manilla, could that have something to do with it?
[Touch GSM ROM Development] dsixda:
Another Cooking issue...

I was building my ROM with Ervius' tool, but then later I built it in Bepe.

However, now if try to build that same set of files in Ervius again, the OS hangs at the splash sacreen after flashing :(

Any idea what went wrong???
[Touch GSM ROM Development] ayyu3m:
a similar thing happened while i was cooking in Hybrid Kitchen also. the OS.nb wud be built successfully and .nbh also. but when i flashed the device wont boot.

so i backed up my needed files and re-installed the whole kitchen again.

and problem got solved. i didnt try to find the root of the problem...but i know it must be a corrupted .bat file
[Touch GSM ROM Development] Noonski:
Try Backing up the DSM files in OEMDRIVERS and OEMAPPS and then making them Empty.

Also sometimes i found that Some OEM packages made By Ervius had something different with the DSM files so i delete that specific DSM file then made a new blank one with new UID number and also changed the option.xml and rgu files accordingly.
[Touch GSM ROM Development] dsixda:
I guess it has something to do with Bepe protecting the ROM when building? I mean I can build the files in Bepe after building in Ervius, but not vice-versa (i.e. the flashed ROM will hang on the splash screen).

Anyways, I had a backup so I don't need to go through any hassle, other than to repeat the same few steps again.
[Touch GSM ROM Development] dsixda:
How do I extract the Random Access (for Contacts) out of my 6.0 base? I tried copying SYS/Redist/outres.dll but that didn't work.

The reason I ask this is that the HTC Random Access that is downloadable from this thread has a sidebar that is too wide, and thus it blocks the "xyz" in the alphabet index that goes horizontally at the top. It's also missing the "#" character at the top. The one from my 6.0 Base ROM is just perfect.

EDIT: Nevermind, Noonski's got us Opal Random Access.. and it works great!!! WOOHOO!!!!!
[Touch GSM ROM Development] dsixda:
Ok more cooking problems from me. I had already tried searching the forum.. but I cannot find a solution although someone else had the same problem:

I tried to set FingerPressure to a certain value in TFLOSettings, under the OEMDrivers\.RGU file. However, the value stays at the original number after I cook it. I can however change it after I've flashed it on my device... but that kind of defeats the purpose of cooking.

This is the same place under which I had set TFLOSetting\EnableCube=0 and that had worked. I also removed the Cube. I don't know if those two are factors... but .. is there a way to cook the FingerPressure setting??? Shall I set it in some other file??
[Touch GSM ROM Development] ayyu3m:
dsixda! congrats!

hey ppl, guess whose outdone himself and turned a cook enthusiast!!

answer: dsixda (haha! cudnt leave u all guessing with so many cooks coming arnd lately and so fast!)

tested and working on ELF. if anyone wants to try, i assume pm dsixda or grab it from his signature while its hot

This is a clean rom, with only a few apps, and consist of the new Opal Task Manager, Volume Control and Large Start Menu

Speed and Performance: Absolutely awesome and smooth on a first time cooking.

Bugs: No more to squash. Except a missing windows mobile ringtone. But thats all so far :D
[Touch GSM ROM Development] Noonski:
Either use a Mort Cooking to sewt the Value ;)

Or make a ProvXml file with the App "reg to xml"

RGU files in Sys folders taken precedence over Registry settings in OEM.

So making a folder just with RGU with an X in front of (so it is the last folder that gets scanned in SYS, and gets the piority in the end Hive Building)

So if the above trick don't work you make a .Provxml file.

Good job, i can announce my Cooking Retirement soon ;)
[Touch GSM ROM Development] Ameet:
Congrats Dsixda :D You officially graduated from Noonski's institute ;)

Collect the certificate from his office :D

Hope to see some good new builds coming out of your kitchen soon :D
[Touch GSM ROM Development] dsixda:
Thanks guys, and especially to my chum ayyu3m ;-) I'll put out an official build soon!

I'll try the method that Noonski proposed. Geez I'm learning more and more every day! :D
[Touch GSM ROM Development] ayyu3m:
hehe anytime buddy. waiting for the official build eagerly as well. :D

btw www.htc.com :eek: touch 3G and touch HD!!!

i gotta get start saving some $$$ keke
[Touch GSM ROM Development] dsixda:
And there you go! :-)

http://xdaforums.com/showthread.php?t=426540
[Touch GSM ROM Development] absorber786:
Virgin cooker

Hi master chefs and cooks

Quick questions re the installation.....

Firstly the instructions say install to C drive. However a closer look at of the batch files show that it points to the %systemdrive% which in my case is not C but rather D (dont ask how that happened). So Hypercore install to the D drive! So based on that i copied the files into the relevant folders on D Drive.

Now using starting with Post 477 re the first steps in cooking...i dont get to the second screen shot! I followed the instructions and hit 'Enter' and the window closes! So this is my little problem..

[Now the question one ask me back is what ROM am i using. Well for now its a cooked ROM]

My questions

1) Is it possible that the a system path may be hard coded in the batches and could this be causing my problem?:rolleyes:

2) Would i need to reformat my system to cook?:eek:

3) Hypercore vs Kokotas Kitchen? Can someone explain pros and cons of these two?

4) Can I use the last official Dopod Rom as a base? (If i understand correctly, you can either use an official Rom or custom rom as base and work from there onwards) I know its a downgrade but it a starting block after which i move on XIP porting etc....

5) How much coffee do i need?

Thanks
[Touch GSM ROM Development] kokotas:
If you "installed" the VistaBatchFix, then there is no problem with the batches, cause %SystemDrive% is the drive upon which the system folder was placed, so in your case the value of %SystemDrive% is D: .

Before you try something like that, try to install MS .NET Framework (latest) and give it a go.

Better choose as a 1st base either an official or a dumped ROM, not a customized cause there would be a lot missing and you won't have the chance to see what's inside an official rom!

Then day by day(&flashing by flashing) you'll find out what could be safely removed, what tweaks would increase performance, etc...

At least this is what I did and still doing.

lol:D A lot of cups I guess..:D

Good to see more and more ppl getting into this cooking thing!

Imagine.. everyone having his/her own cooked ROM running on the ELF!
[Touch GSM ROM Development] absorber786:
:o i found my problem and fixed it! Copied the ACK and RUU files to the qrong folder

Did that...and boy! did it take a while to download

Perfect....i have more questions coming;)

lol:D A lot of cups I guess.

Hehe...its time to take over the world!!!
[Touch GSM ROM Development] absorber786:
Urgent help

Ohhhh..need some help..

Ok so i took an official dopod elfin rom...added a few cabs....build os.nb..changed the pagepool size and then created ruu_signed file correctly. There were were no issues so i thought things were going really well.

Then i even flashed the rom and still no issues the ruu utility worked fine. But now my touch wont even start up let alone go the boot loader screen!!

Help

btw i built the rom using Koko's kitchen

EDIT: I still had a SD flash image on my storage card which allowed me reflashed. The funny thing is I could not enter the tri-color bootloader. Why??

And apologies for posting in the wrong thread.....my brain was not functioning correctly at the time.

Now on to some questions to check were i screwed up..

1) i used this rom as a base - RUU_Elfin_DOPODASIA_WWE_2.20.707.1B_4.1.13.51_03.07.90_BLUE_Ship_Reduced.exe

Now from my understanding, all version 2 roms are flashable to an Elf, including this one. Am i correct?

2) The RUU update reached 100%. When the restart after flash happens, thats when it did not power back on again. Why?
[Touch GSM ROM Development] dsixda:
Maybe your battery was already dead? While flashing, it doesn't get any charge from your USB. Just let it charge for 10 minutes from your wall charger and see if it comes back.

If that doesn't help, take the battery out for 20 minutes, put it back in, charge it for 5 minutes, and try to restart ... If still no luck, push the reset button too.

Happened to me before.
[Touch GSM ROM Development] absorber786:
my battery was almost full...but as I said the sd flash worked...but why wasn't the bootloader thing not responding
[Touch GSM ROM Development] trueg:
Hey guys, I hope I'm not too late for the party. Lately, I've been flashing like crazy trying to learn how things work, what things I can change and stuff like that. I'm sure I must have flashed to my poor ELFin like 50 times in the last week. Anyway, using Hybrid Kitchen, I find that sometimes I can't dump ROMs correctly. Sometimes, it dumps correctly and I get an OEM and SYS folder full of goodies. Other times I get a folder full of packages with an empty OEM and SYS folder. If I understand correctly, this is possibly due to the DSM files? Is there anything that can be done about this? I wanted to dump Opal R2 to compare a few things to my own Opal port, but I just got a folder full of files and folders.
[Touch GSM ROM Development] Noonski:
Nope it's not possible.

But you can check the files being dumped in the Dump folder (right before the packages should be made.

I'm not familiar with the Hybrid Setup. But it should also dump everything into one folder before the packages are made.

It would not make that much sense as having the actual packages sorted, but you can convert the default.hv and user.hv to .rgu files and at the very least you would have a registry to compare.

There's been this whole discusion that this cooking method that makes a ROM not dumpable is only because people want to keep their rom secret.

It might be a reason for some but Performance is the other big reason this method can be chosen.
[Touch GSM ROM Development] dsixda:
Are you saying this will cut down on all those RGU files under \Windows and combine them all into one? (e.g. a22602c-2bdflkdsjf-4325432j5-3254324 blah blah blah)

If so, then I am all for this idea. I dont care if my ROM is secret or not, but if it saves the user some boot time then that's more useful.
[Touch GSM ROM Development] trueg:
HTC Home + Manila2D

Has anybody attempted to get HTC Home and 2DManila installed on the same device? I would think that it would be nice to have a ROM that provided the option of either.

While testing the Opal OEM with the 20758 SYS & XIP I wondered about adding HTC Home and simply turning off TouchFLO in the Today settings. I made up a HTC Home OEM that installed nicely and works great with this ROM. The only issue is setting the Weather location for HTC Home.

In order for the HTC Home OEM to install I removed all of the HH_WEATHER*.png since they were already provided with 2DManila. They are a different dimension in 2DManila (140x90 vs 125x118), but that doesn't seem to be a problem. The issue is setting the location. HTC Home and 2DManila set the values in different locations. The values for HTC Home do not get set when I enter them, I assume because HTC_HDlg.exe that came with Manila2D is pointing to the registry settings under Manila2D\Weather. If I set the HTC Home location settings manually in the registry, it works.

Is my only option going to be to rename HTC_HDlg.exe to something else and somehow get HTC Home Weather to use this exe instead?
[Touch GSM ROM Development] dsixda:
The main question is, are you ok with having thousands of files under \Windows? The graphic files for both M2D and HTC Home add a LOT of overhead to boot time and \Windows access.
[Touch GSM ROM Development] trueg:
Yes, they are all dumped into one big folder. I'm new to this, so I can't tell by looking which packages belong to SYS and which to OEM.

So you are saying that when they build their ROM, they start with a folder full of packages instead of a separate SYS and OEM? What type of speed increase is there to be had by doing this?
[Touch GSM ROM Development] trueg:
Yes I suppose that would be a concern. The HTC Home folder without the HH_Weather pictures is only 717 KB and 119 files. I didn't notice much of a difference with boot time. As for \Windows access do you mean viewing the Windows folder and that taking longer to load or would it effect run time performance?