PDA

View Full Version : [REF] Cooking Class Class of 2007/08/09 [ONLINE]


Pages : [1] 2 3 4 5 6 7

Noonski
10th October 2007, 12:42 AM
This thread is going to be for Junior chefs and other cooking enthousiasts.

Any one can join in and contribute and share mistakes made.

Touch only Please.

Most other devices are pretty well covered.
But Touch Forum is one of the youngest and a lot of touch users are new to WM6 and flashing and i find a lot of threads started that would belong pretty well in this thread. Not every Touch User goes onto other threads to find the information he needs

And no please don't consider me as the main man. There's still enough i need to learn and mistakes i still need to make ;)
(And experiments i still need to do)

Graduates and Teachers:
SwiftBlade, Teacher
Xtriny, Chef in Sabatical
Koala996, Chef Avec Le Francois
Bram Smulders, Graduate before even starting
ayyu3m, Cook and instant Teacher
Ameet, Chef and XIP Port Teacher

Noonski
10th October 2007, 12:43 AM
Below is a slighty edited version from the original thread,
just to get you started.
As the original is still beta (but a mighty fine beta at that) any issues found will be reported on original thread. Please try to keep request in this thread as much as possible. And let's not bother Anichillus to much with questions and try to find out as much as possible our selves.
~~~~~~~~~~~~~~~~~~~~~~~~
HyperCore
Touch BETA
HyperCore Was Assembled and put together By Anichillus.
Who's added a nice Extract and Cook Tutorial in the Help Folder.
Many of the tools were created by those in Special thanks part below.




The most complex KITCHEN a begginer cook may ever need.
Easy to use but also very complex, it can be usefull to anyone.
Why ask and wait for others to make the perfect ROM for you when you got the power to do it yourself ?


~. Base ROM .~
* NO BASE ROM ! but ANY ROM !


~. Best part .~
* IT USES TADZIO TOOLS
* YOU CAN OPTIMISE EXE's and DLL's, SO IF YOU WANT EVEN MORE SPACE, YOU'LL GET IT
* IT CAN BE USED ON ANY DEVICE WITH VERY LITTLE MODIFICATIONS !!!!!
* NO LONGER LIMITED BY ANYONE OR ANYTHING.
* YOU CAN COOK ANY ROM YOU LAY YOUR EYES ON VERY EASY
* IT HAS ADVANCED ERROR CHECK

~. Guides .~
* Hermes Cookbook (http://forum.xda-developers.com/attachment.php?attachmentid=44308&d=1184780703) - THANKS to sambartle
* My Way of cooking (http://forum.xda-developers.com/showpost.php?p=1374154&postcount=138) - THANKS to Anichillus
* How to ADD/REMOVE programs (http://forum.xda-developers.com/showpost.php?p=1457844&postcount=180) -THANKS to mfrazzz

~. Notes .~
Since this is still a public BETA, I await your problems/ideas/concepts.
If you spot a bug, i suggest discussing it first before posting it to official HyperCore Kitchen Thread.
I suggest having a ROM to make a backup in case you do something wrong
This kitchen was created and tested for WindowsMobile 6 , but WM5 should work OK too.


~. Download .~
RapidShare (http://rapidshare.com/files/50880220/HyperCore_V1.01.exe)
Special thanks for those that made the Kitchen Possible :
* Anichillus - for creating the most complete Kitchen around and letting me start this thread
* Papamopps - for support on HyperCore Kitchen
* nandlal_mk - DSM editor
* mfrazzz - for his
* mUn - for finding the time to answer some of my questions
* molski - for i started working on his tools and still used some of them
* Tadzio - for his tools and patience
* bepe - for his tools
* the-equinoxe - for his splash-screen tools
* naboleo - for his initflashfiles generator
* dutty - for his NBH Tool
* Faria - Because i liked his way of cooking and he created one of the first kitchens i ever tried out.
Names will be added. I'm a very strong believer in showing apreciation to the hard work of XDA contributors.

Noonski
10th October 2007, 12:45 AM
1. Be clear on what your specs are. So use your signature so you don't need to post your Base Rom and such.
2. Keep it clean. Ignore useless posts that have nothing to do with the thread. Because it will just become a very long book with no substance.
3. Read the thread before asking. And again ignore Questions you know are allready in the thread.

Noonski
10th October 2007, 12:46 AM
1. Installing Hyper Core Kitchen For Elf (http://forum.xda-developers.com/showpost.php?p=1574779&postcount=33) (Re-Edit By ayyu3m)

2. Making DumpRom of Original Stock Rom (http://wiki.xda-developers.com/index.php?pagename=Elf_HowtoDumpRom). (By r0p3 (http://forum.xda-developers.com/member.php?u=413304))
(haven't done this unfortunatly for my device so i won't be able to do it fully, so if anyone has a full explanation that also extracts, SPL/IPL/Radio/Ext_Rom please post it, unless i'm missinformed and the Wiki covers this)
(for more about this and updates check this thread by r0p3 (http://forum.xda-developers.com/member.php?u=413304) Wiki entry: Backup your Elf ROM - dump and restore) (http://forum.xda-developers.com/showthread.php?t=327073)

3. Extract Rom and XIP (http://forum.xda-developers.com/showpost.php?p=2526864&postcount=477). (Amazing Pictorial By ayyu3m)

4. Cooking your First Plain Unedited Rom (http://forum.xda-developers.com/showpost.php?p=2527024&postcount=479) (Pictorial By ayyu3m)

5. How To Manually Make your own OEM Package from a .cab (http://forum.xda-developers.com/showpost.php?p=1575728&postcount=48)

6. Adding an OEM Package.

7. Removing Files from the ROM.

8. Edditing default.hv and user.hv (more like cleaning up, as direct editing is not advised)

9. Editing and making Fake Ext Rom.

10. Finding Specific Registry Settings To Cook.

11 A. How to Change PagePool In Rom Before Flashing (http://forum.xda-developers.com/showpost.php?p=1634462&postcount=144) (For Pre 2.20 ELF's) (By Noonski)

11 B. How to Change PagePool In Rom Before Flashing (http://forum.xda-developers.com/showpost.php?p=2274534&postcount=1) (For After 2.20 ELF/IN's (http://forum.xda-developers.com/showpost.php?p=2274534&postcount=1)) (By SwiftBlade)

12. Replace Graphics in Exe Files and DLL's (http://forum.xda-developers.com/showpost.php?p=1902704&postcount=297) (Tute 14 also has info on this)

13. Export the XIP from another Device Rom To Work With ELF/IN (http://forum.xda-developers.com/showthread.php?t=379598) or Porting XIP manually (http://forum.xda-developers.com/showthread.php?t=438676) (By Ababrekar)

14. Editing MUI files in a Nutshell (http://forum.xda-developers.com/showpost.php?p=2847318&postcount=36)

X. Changing Precooked Tabs Settings (http://forum.xda-developers.com/showpost.php?p=1574903&postcount=34)
X. How to find specific registry settings

If any one has any extra Tutorials or wants to Change/perfect Tutorials allready made, please do, it's an open Kitchen.

Noonski
10th October 2007, 12:47 AM
1) Packages may only consist of free software or software embedded in a factory ROM.

2) Package(s) must work and have been used by the poster in cooking a ROM. Please state the kitchen you used.

3) Uploads must be named according to contents (i.e. 300_Compressed_Office_2007_MM.zip). (MM=Main Memory SD=Storage Card)

4) You must state the contents of the package in your post. Not every little thing but enough for a person to make an informed decision to use the package or not. Packages do not have to include an option.xml file. However, they must include an initfileflashes.dat as well as .rgu and .dsm files.

5) If your package is too big, please use the uploads "/Elf/Cooking Class/OEM Packages" section of the FTP to post and post the link.

If you are posting a request:

1) Click on the paperclip icon on the main forum page next to this thread to see if a package you are requesting has already been posted. This is the most important rule!


I have a naming Scheme for most of my packages to easily find stuff back and have some order in my kitchen.

000 Personal Settings For Rom.
100 Interface Cutimisation Packages.
200 Home Screen Plug Ins
300 Applications
700 SIP Input Methods
800 Registry Tweaks
900 OS packages (Auto Update, Enterprise, etc)

Of course this is open for discussion. But for now try to keep numbering for Packages.

I'll contact a Moderator to see if it's okay to use some FTP space on XDA.

No Warez, No Warez and..... No Warez. Only Free Apps with permission from creator and Original Software found in Stock Rom's can be added to the repository.


REPOSITORY
000_Fake Extended Rom MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/000_Extended_ROM.zip) (by Noonski (http://forum.xda-developers.com/member.php?u=243942))
000_Launch Extended Rom Install MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/000_Launch_Extenced_Rom_CheckAutoRun.zip) (by Noonski)(For those that like to clean out their kitchen ;))
100_Different_Syncing_Animation_MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/100_Different_Syncing_Animation.zip)
100_NewBatteryIcons_MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/100_NewBatteryIcons.zip)
300_Adobe Reader LE MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_AdobeReader_WWE_MM.zip)
300_HTC_Audio_Manager_Blue_MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_HTC_Audio_Manager_Blue_MM.zip)
300_HTC Duo Touch EndKey App WWE MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_Dou_Touch_EndKey_WWE.zip) (By Noonski (http://forum.xda-developers.com/member.php?u=243942) & koala996 (http://forum.xda-developers.com/member.php?find=lastposter&t=331155))
300_HTC_Random_Acces_MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_HTC_Random_Acces.zip)
300_GoogleMaps MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_GoogleMaps_WWE_MM.zip) (By Noonski (http://forum.xda-developers.com/member.php?u=243942))
300_Pocket Rar MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_Pocket_Rar_MM.zip)
300_psShutXP Power Off Replacement MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_psShutXP_0.0.29_MM.zip)
300_Redial MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_Redial_MM.zip) (By Faria)
300_VOIP_MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_VOIP.zip)
700_HTC Duo Touch KeyBoard WWE (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_Touch_KeyBoard_WWE.zip) (By Noonski (http://forum.xda-developers.com/member.php?u=243942) & Special TNX To Tom_Codon (http://forum.xda-developers.com/member.php?u=341738) & Special TNX to "A Good friend Of XDA-Developers.Com")
900_Windows Live Messenger 1.6.32 WWE_MM (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_WLM1.6.32_WWE.zip) (By boy_de_ghet (http://forum.xda-developers.com/member.php?u=304977))

Noonski
10th October 2007, 12:51 AM
I'll think of of a better way of filling in these first threads. But it's better to be safe then have not enough space so please be fiorgifefull for now.

Noonski
10th October 2007, 12:52 AM
Let's try and get some information together about working with localized Roms here.

I've seen a Spanish, French, Chinese and Dutch Cooks around.

Noonski
10th October 2007, 12:53 AM
Dopod Asia WWE 1.17




(DO NOT DOWNLOAD AND FLASH THE ROM BENEATH LINK IS FOR RESEARCH PURPOSES IT IS A FULL ROM WITHOUT SPL EXTRACTED)
Uploading RUU_signed_OS5.2.1437.zip (http://rapidshare.com/files/61786658/RUU_signed_OS5.2.1437.zip)

Noonski
10th October 2007, 12:53 AM
Either your in or your not.

Let's not but any pressure on people then.

Any good suggestions to fill the first threads?

Xtriny
10th October 2007, 02:33 AM
Xtriny ;-)

eefurt
10th October 2007, 08:15 AM
Hi Noonski,

I'm in :)

bram_smulders
10th October 2007, 09:15 AM
Hi Noon,

I'm in to!
Nice Initiative of you man, maybe we can sticky this thread!
It's helpfull to us all!
Mayb Post all the current available roms also, becouse everybody can extract them to build their own??

Gr. Bram

Noonski
10th October 2007, 09:40 AM
Yeah i set up Thread 9 to collect those in.

When it becomes intersting it will propably become sticky.

Great to see you guys. I'm of to do real work.

bram_smulders
10th October 2007, 11:07 AM
Pick me, Pick mee, register mee? :p

koala996
10th October 2007, 11:11 AM
Hi Noonski,

Thanks for the thread. I'm in and I hope this thread will be kept clean.

Biffert
10th October 2007, 11:36 AM
Ive been trying to cook my own stuff for a while now, but only partial succes. Ill be following this thread :)

Nice initiative :)

Noonski
10th October 2007, 11:39 AM
Nice to see we got's us a good sense of Humour here.

LittleBigBen
10th October 2007, 11:48 AM
I'm in and ready to cook:)!!!

Noonski
10th October 2007, 12:16 PM
Damn

Here's what i just did.
I edited a Registry setting using PHM reg edit.
It was the setting that tells what to run in the HTC home Pug in.
Will have to look at home but i think this registry setting is also present in a provxml file when cooking. After reset it froze on third Boot.

Going to try and reproduce this step now.
Not cooking issue but still important and interesting i thinks

It was HKLM\Software\HTC\HTCHome\Launcher\5\Path=

Shit i could not reproduce it.

Second attempt, again it did not freeze.
So it looks freeze can still happen with new HTC home. I could try and replace the files with original DUO Touch dll and exe files that have 6 tab standard.
Maybe i need to restart faster after reg edit.

mzmiric5
10th October 2007, 12:38 PM
Hey Noonski count me in.

Vista fix is working, and to save time to other people i uploaded edited batch folder(link in my sig).

Could we add Touch configuration to the Kitchen and include RUU too, coz Artemis RUU doesn't work.

mcdull
10th October 2007, 12:43 PM
Count me in, thanks... But I am currently very busy with my work.... >.<

bram_smulders
10th October 2007, 12:44 PM
Damn

Here's what i just did.
I edited a Registry setting using PHM reg edit.
It was the setting that tells what to run in the HTC home Pug in.
Will have to look at home but i think this registry setting is also present in a provxml file when cooking. After reset it froze on third Boot.

Going to try and reproduce this step now.
Not cooking issue but still important and interesting i thinks

It was HKLM\Software\HTC\HTCHome\Launcher\5\Path=

Shit i could not reproduce it.

Second attempt, again it did not freeze.
So it looks freeze can still happen with new HTC home. I could try and replace the files with original DUO Touch dll and exe files that have 6 tab standard.
Maybe i need to restart faster after reg edit.

Hey noonski,

How did you get the touch dual Dll's?
Becouse if we have that, we've got also the picture vieuwer!!

Gr. bram

LittleBigBen
10th October 2007, 01:03 PM
I just checkt out the HCT Homepage and they have the video playing introducing the touch and touch dual. and on both homescreens you can see the 4 (6) taps.
has htc a new rom-update for the touch? then you wouldn need the dual dlls....

Noonski
10th October 2007, 01:10 PM
Hey Noonski count me in.

Vista fix is working, and to save time to other people i uploaded edited batch folder(link in my sig).

Could we add Touch configuration to the Kitchen and include RUU too, coz Artemis RUU doesn't work.

We could. But we could also wait for officail version. But if we can make it work, why not take some work out of Anuchillus hands.

For now it should be easy to at least have an edited version by just copying the artemis values and creating an extra entry for the touch. I don't know how the ruu files are set up but we can try that to.

Hey noonski,

How did you get the touch dual Dll's?
Becouse if we have that, we've got also the picture vieuwer!!

Gr. bram

Let's keep it at "from a good friend of XDA".
At the moment piecing together all the files is not really my piece of cake, so i've sent the files to some Senior God Mode XDA-ers.
That have a better change of making cheese out of it. And if they do we all benefit anyway.

I checked the version numbers on the dll's and they matched. Thing is i think one is from Kaiser as they differ in files size. I don't know what Schen changes to the exe files and dll's. I couldn't run the HTChome Exe's fomr my machine because it did'n't ecept the certificates. So maybe they are being signed differently. Making them unuseable for me. (not all new files BTW). This is way beyond my level.

Noonski
10th October 2007, 02:09 PM
Hey Noonski count me in.

Vista fix is working, and to save time to other people i uploaded edited batch folder(link in my sig).

Could we add Touch configuration to the Kitchen and include RUU too, coz Artemis RUU doesn't work.

Great thanks i'll post it to first threads and to Anichillus thread.

Ah you allready sorta did ;)

I think you allready showed why this thread is a good idea. I know Koala996 was having Vista issues. He can try the fix now.
And i see i need to update my sig.

Swiftblade
10th October 2007, 02:21 PM
Hi Noonski... very nice initiatives. I had tried my hands cooking a couple of times using Hypercore Kitchen but without much success (sighed...).

Like to join in as an apprentice or junior cook though if you don't mind..:D

Originally Posted by mzmiric5
Hey Noonski count me in.

Vista fix is working, and to save time to other people i uploaded edited batch folder(link in my sig).

Could we add Touch configuration to the Kitchen and include RUU too, coz Artemis RUU doesn't work.

I have added Touch configuration settings to the kitchen by copying and editing the Artemis one and it worked fine. The edited device.txt and setting.txt files are attached below:
http://sblade.250free.com/Device.txt
http://sblade.250free.com/Settings.txt

Noonski
10th October 2007, 02:47 PM
Hi Noonski... very nice initiatives. I had tried my hands cooking a couple of times using Hypercore Kitchen but without much success (sighed...).

Like to join in as an apprentice or junior cook though if you don't mind..:D



I have added Touch configuration settings to the kitchen by copying and editing the Artemis one and it worked fine. The edited device.txt and setting.txt files are attached below:
http://sblade.250free.com/device.txt
http://sblade.250free.com/setting.txt

Posted these to second thread tnx for contribution.
I can't check or test these right now work proxy restrictions.
Any one that can verify?

Swiftblade
10th October 2007, 02:55 PM
Posted these to second thread tnx for contribution.
I can't check or test these right now work proxy restrictions.
Any one that can verify?

Hi Noonski... sorry the earlier links to the files not working. Updated the links and should work now. You can re-post them to the 2nd thread again.

mzmiric5
10th October 2007, 03:05 PM
Posted these to second thread tnx for contribution.
I can't check or test these right now work proxy restrictions.
Any one that can verify?

they work fine for me

warriorvibhu
10th October 2007, 05:11 PM
Commendable work noonski ... god bless ya ;)

Now i can start making a bit more professional and bug free ROMs.....

Noonski
10th October 2007, 07:13 PM
Commendable work noonski ... god bless ya ;)

Now i can start making a bit more professional and bug free ROMs.....

Welcome.


I'm testing the device settings for flash setting.

Just replaced Settings & Device in second thread.

Just flashed with new files for RUU folder it's working with new settings.

Noonski
10th October 2007, 07:19 PM
Follow these steps to setup HyperCore Kitchen for ELF in Windows XP/Vista Machine

1 - Download HyperCore (v1.01) (http://rapidshare.com/files/50880220/HyperCore_V1.01.exe) Kitchen

2 - Double click HyperCore_V1.01.exe to extract and install. The setup will create a folder Core in your C:\ drive

3 - Download ACK.zip (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/Core/ACK.zip), extract and place the extracted ACK folder into "C:\Core\" to overwrite the existing files

4 - Download RUU.zip (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/Core/HyperCore/Tools/RUU.zip), extract and copy the contents of the folder to Desktop: \Hypercore\Tools\RUU to overwrite the existing files

5 - Vista Users, download Vista Batch Fix.rar (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/Core/Vista%20Batch%20Fix.rar), extract and place the Batch folder in "C:\COre" to overwrite existing files

6 - The Hypercore Kitchen has been setup now. You can start Cooking (Note: This kitchen has been setup exclusively for Elf and will not work for other devices)

Credits for Fixes
*ACK.zip courtesy of Swiftblade (http://forum.xda-developers.com/member.php?u=516412)
*RUU.zip courtesy Noonski (http://forum.xda-developers.com/member.php?u=243942)
*Vista Batch Fix.rar courtesy of mzmiric5 (http://forum.xda-developers.com/member.php?u=614689)

Lets move to Step 2. Extracting the ROM (OEM, SYS and XIP)

Noonski
10th October 2007, 08:09 PM
1. Open Any .rgu file from Package in Sys folder or from HTCHome Package with notepad.

2. Ad,

[HKEY_LOCAL_MACHINE\Software\HTC\HTCHome]
"TabSetting"="1,2,3,4,5,6"

Or

[HKEY_LOCAL_MACHINE\Software\HTC\HTCHome]
"TabSetting"="1,2,3,4,5"

If you need less tabs.

Or

[HKEY_LOCAL_MACHINE\Software\HTC\HTCHome]
"TabSetting"="6,5,4,3,2,1"

If you want to change the tab order.

Don't forget to leave a blank line at the end of .rgu file and not use Wordwrap, and then Save the file.

Break Time.

evlimeca
10th October 2007, 08:34 PM
nice. I totally agree with this idea, although for simple information exchange, i think its a much better idea to setup a Touch IRC channel, or some other form of group chat where we can quickly discuss problems (if people are around), and post any useful information to this thread. It's already gotten horrendously long with just the people saying I'm in.

as you said the touch is a really new device, and in many ways completely different than most of the devices before it in the fact its nearly buttonless. I equate it to the dos-windows gui interface jump. If anyone is somewhat smart they can figure out where this leads. buttons are dying, and as much as some people don't like it, change is inevitable. that being said there are some things to consider.

1) despite the fact that many individuals are cooking up some extremely impressive roms. (lets not do credits now to everyone) it seems theres a real lack of community involvement in a project. goals? simple create a better more effecient rom than htc itself is producing. improving capabilities and user friendlyness across the board.

2) customization. I mean seriously i understand the lack of space on the touch, but Oo my wm6 device came with 4 different skins! look this one is orange! thats a total joke.

3) its safe to assume nobody who is ever going to flash a touch is going to ever own a touch without a memory card, and said memory card is never going to be smaller than 1gb (thats also low in my opinion)

4) This is my big one. In a globalized world, i have no idea how HTC and Microsoft have done such an amazingly horrible job with multi language support. Lets not talk about U.S. users here (and I am an American so save the attacks or defensive retorts) but Americans are the one people who have the least use for multi-language support. we Don't care what you speak, you should speak English. Anyone who is not a native English speaker, needs at the very minimum English plus their native language, and any additional languages they may speak. For me its Chinese.

In my opinion the age of GUI pocket pc's is upon us, telecommunications and media are about to make the same, if not greater leap than they did in the early 90's. In three years time the laptop and the desktop will be obsolete for anything other than gaming and graphical design. The average worker is going to carry a company issued cellphone that bluetooth's to a keyboard and a mouse, with a display hookup coming out of a phone no bigger than the touch. the touch dual is already 400mhz, overclocking might push 600. its going to be sick.

Unfortunately, I studied project management, and not CIS. what i see when reading these forums is alot of really really good programs put out by techies. but unfortunately the roms theyre cooking up are for techies, with very little thought given to what the actual average cellphone user has in mind.

now a lot of you may be thinking, who cares about the average cellphone user, they're idiots. and while people may or may not agree with you, the fact is that these people are the ones buying the phones, so its great for us to figure out a new way to tweak something with registry editor, but who's really working on the fact that audio manager sucks and makes the programs crash.

Its hard to be taken seriously by anyone, when serious flaws exist in the roms that are getting dumped out. I agree that a cooking course is a great plan. but honestly who wants to see 400,000 more new roms every day. i /care about the new WWE big storage that saved me 200k more space. i truthfully dont even use the 15 MEGS i was given with the factory rom.

therefore, i propose to move the class to a public real time chat room, work together on making one solid rom, and improving the overall quality of the users experience and using xda, to post results and field problems. but thats just my idea :P

koala996
10th October 2007, 08:51 PM
4) This is my big one. In a globalized world, i have no idea how HTC and Microsoft have done such an amazingly horrible job with multi language support. Lets not talk about U.S. users here (and I am an American so save the attacks or defensive retorts) but Americans are the one people who have the least use for multi-language support. we Don't care what you speak, you should speak English. Anyone who is not a native English speaker, needs at the very minimum English plus their native language, and any additional languages they may speak. For me its Chinese.

Hey .. I agree a lot of what you say .. but I need to explain why I HAVE TO have a FRENCH rom even if I'm fluent with english :

Cause 1 : people I talk with .. they speak french ! I can't send them a text message in english ...
Consequences : I have to have a FRENCH keyboard (to have accentuation : éèàç ..) and I need to have a FRENCH dictionnary (yeah it's horrible to have autocompletion in english when you are typing in FRENCH !)

Cause 2 : not used with hours .. and dislike to have "AM" and "PM" symbols
Consequences : I need to have the 24 hours a day .. I know I can change it with WWE with the regional settings .. but if I understand well what you mean .. you would cut it too.

That's why I needed to come back from WWE to FRE :(

I'm not against your idea... but these 2 things explain what we need to have our natural language... even if we are able to speak english fluently.

Noonski
10th October 2007, 08:58 PM
I agree on most of your views. But I also think that this thread will contribute to making things better. My personal main goal is to get a Rom as clean as possible, and with the shared resources we will probably get a great Vanilla base out together. I think some wouldn't mind a IRC chat. But I also know that some like the distance you can take by using a thread. When it's full we can start a new one with the first threads linking to all the archived information.

I'm not going to profess the way I’m trying to cook by moving Apps away from Rom to optimize Performance. And your right there are to many Roms out there. But it is inevitable that this Thread will eventually although also having a learning process produce a simple Kitchen (without advanced tools) that can tutor to any one's need. A stripped Rom with maxed out options in BuildOS. You want Help Files? Just tick them on!

Just before I already dedicated one of the first threads to Localization. And as stated there. This thread already contains Some cooks that want to make Localized versions.

If you want to set up an IRC I salute the idea I’m not against it.
The difference is that you get an Immediate hardcopy of information using a tread. Which basically means. When new people join in reading becomes a must. With IRC you might jump in at a moment and miss what went on. Off course a combination is always a good idea. But what guarantee is there that Found solutions get hard copied.

But does this mean we’ll be seeing you around ;)

And Koala i don't think he meant it his remark as a negative about Locales. I think he perfectly describes the general atitude that brings forth the Bad support for localization. I don't think he means to say he's against it.

evlimeca
10th October 2007, 09:06 PM
no i totally agree with you. basically what im saying is there has to be a way to get issues like this solved, so we can all use the same rom, and in whatever language we please. like i've said many times i'm no techie, but i seriously doubt there aren't ways to do it.

even still i understand wanting to have your rom in your language and thats perfectly cool. but in the end wouldnt it be a hell of alot easier to setup a RUU that asks for a selection of which language you'd like to install on the rom? Or find some way to stick T9 dictionaries, on the memory card, taking up like a total of 20 megs, but you have language support for every language on the planet?

I'm not sure if i'm understanding this right, but it looks like all one has to do to switch the language in a rom is to change the name of a couple of files and install a different font pack? seems...silly to not be able to stick them all together. now i understand space is huge, but noonski has started sticking applications on the memory card that are linked through the rom, I havn't done any benchmarking, and it may slow down the phone to do it this way, but the possibilities seem endless once the memory problem is out of the way.

Noonski, is it possible to get some basic tutorials posted up, like the one you have. but simple things...
1)changing the language on your phone
2)importing your own graphic files for icons
3)How to link an application meant to install on a storage card, with a shortcut embedded in the rom. (don't keep sekrets!)
4)Navigating the kitchen...whats where, whats it do? this is for real retards like me. but give me some frame of reference to start learning and i'm off like a rocket.
5)an explaination of the kitchens pieces...maybe this is a better idea to ask the kitchens creator to do for us. he made it.

basically compile the mandatory reading list for novice chefs.....i'd like to call it Freebasing for Dummies.....cooking sounds great, but disaterous results mean you order out. cooking for phones is alot more like cooking crack :P mess up bigtime an you lost your whole investment, and potentially have a horribly scarred face.

Noonski
10th October 2007, 09:09 PM
Theoraticly it should be possible. If you clean out the OEM folder of MUI files and then make seperate Packages containing Localised .HV files and initflashes and MUI files. Same goes for packages. You can have them in language flavours. Off course there might be some more hurdles.

We can test t9 from SD card BTW.

koala996
10th October 2007, 09:13 PM
And Koala i don't think he meant it his remark as a negative about Locales. I think he perfectly describes the general atitude that brings forth the Bad support for localization. I don't think he means to say he's against it.

I know it wasn't something negative.. And I hope my answer will not hurt him or someone else. I have just explained why we have to do rom that supports another language. I agree with him and I'm not finding his remark negative at all. I just wanted to show him concrete examples of what makes locale still important.

What I think that could be the best ... is to make a program that create the RUU for noobs. A program that just ask people what they want :
- main colour
- choice of theme
- choice of language (not important)
- choice of keyboard/phonepad ...
- choice of the buttons he want
- choice of program he want and where to put it (SD or Main Storage)
...

I think we all have the ability to make something really easy .. because we all have made great programs and roms. It's not only a powerful rom, but a powerful rom building.

evlimeca
10th October 2007, 09:48 PM
no koala, my meaning was actually that we MUST have better support for localization. how many posts do we see, that show the same rom in a different language...eliminate that problem by having a selectable RUU like you said.

how many posts do we see about input methods? eliminate those by adding input methods on the SD card for all supported languages.

I in fact totally agree with you and your need for whatever language you possible desire, hell throw in klingon if it really makes you happy, release the first star-trek rom i dont care just make it easy.

mzmiric5
10th October 2007, 10:35 PM
I know it wasn't something negative.. And I hope my answer will not hurt him or someone else. I have just explained why we have to do rom that supports another language. I agree with him and I'm not finding his remark negative at all. I just wanted to show him concrete examples of what makes locale still important.

What I think that could be the best ... is to make a program that create the RUU for noobs. A program that just ask people what they want :
- main colour
- choice of theme
- choice of language (not important)
- choice of keyboard/phonepad ...
- choice of the buttons he want
- choice of program he want and where to put it (SD or Main Storage)
...

I think we all have the ability to make something really easy .. because we all have made great programs and roms. It's not only a powerful rom, but a powerful rom building.

There are two possible solutions for this(that i know of). We could make this multi-language ROM as a community project and then make number of roms(each rom for each language) and pack them in a separate installer which will be started before RUU. After selecting language from that "pre installer" it would run the ruu(which would be compressed in the installer) based on choice. Other solution is to put all files, themes, and other stuff u want in to rom and have a little ppc application in extrom(something like the thing that starts after u hard reset[it says that installing will begin in 3 sec]) and after choosing options u want the app would delete the files that are not needed anymore after configuration and installation.

BTW i'm still waiting on anichillus to reply but if i get his permission i will rebuild the new kitchen just for touch and implement GUI for easier usage.

P.S: Post some names for the new kitchen if i get his permission i was thinking something like "Touch'n'Bake"

evlimeca
10th October 2007, 10:50 PM
1) EZbake 2.0, remember the box with a lightbulb all the girls had when you were young, well this one fits a hell of a lot more than one cupcake inside.

2) Wake-and-bake! i mean cmon this one was easy and fun.

Noonski
10th October 2007, 10:59 PM
There are two possible solutions for this(that i know of). We could make this multi-language ROM as a community project and then make number of roms(each rom for each language) and pack them in a separate installer which will be started before RUU. After selecting language from that "pre installer" it would run the ruu(which would be compressed in the installer) based on choice. Other solution is to put all files, themes, and other stuff u want in to rom and have a little ppc application in extrom(something like the thing that starts after u hard reset[it says that installing will begin in 3 sec]) and after choosing options u want the app would delete the files that are not needed anymore after configuration and installation.

BTW i'm still waiting on anichillus to reply but if i get his permission i will rebuild the new kitchen just for touch and implement GUI for easier usage.

P.S: Post some names for the new kitchen if i get his permission i was thinking something like "Touch'n'Bake"

Don't jump ahead to fast.

Everything is possible but first let's lay out all the facts and get confident with the kitchen. You first have to find all registry settings for locale also in .hv files and get every file into a seperate package.

I made a deal to keep request out of his busy hair. But off course you can rebuild the kitchen. It allready is a rebuild o sorts.

Anichillus allready made and started several Core threads.

Oke you know what in an hour i'll post the New MSn package. Let's see how you change the language for that ;)
No really. make it work.

Here's my first contribution to Oem Packs
WLM 1.6.32 (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages/300_WLM1.6.32_WWE_MM.zip)

And now i'm really of to hunt for food.

evlimeca
10th October 2007, 11:06 PM
www.MIRC.com (http://www.mirc.com)

go to quakenet servers.

#xdatouch

thats the room, let me know if any problems, my net connection times out often, but its a good place to do quick chatting of solutions and trial and error, and basic noob help for retards like myself who have no idea about cooking a rom.

mzmiric5
10th October 2007, 11:36 PM
Oke you know what in an hour i'll post the New MSn package. Let's see how you change the language for that ;)
No really. make it work.


First of all, i'm all new to this ppc development and i don't know a lot about it. I suggested the ppc app thing coz i had something similar for my old HP rz1710(and it worked quite well, it had 10 languages, 40 themes and about 70 apps). I develop a lot for PC in free time and i have allready started on the GUI earlier today but now i'm so tiered(had to learn German hole day and now i had my French lessons) so i will continue to work on it tomorrow. Please come up with some fancy name. BTW where could i get MUI files for the hole OS, coz if we have that then with a few reg tweaks we would be able to change languages in seconds. bram responded to a question "where to get MUI files" with a link to Microsoft Localized images for Device Emu.I don't get how to extract mui files from them? I will have to do as much possible with this things this week coz i'm free of school, and next week is really busy. Any other ideas witch base rom could we use, or we are gona cook some vanila to use as a base??

Noonski
11th October 2007, 12:31 AM
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 fuck 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?

Noonski
11th October 2007, 02:42 AM
You can use Cab analyzer or you can use Ervius Package Creator.

But you might as well get your hands dirty. And learn as much as possible from the ground up as if you didn't have all these new tools.

I have added the Cab in Question.

1. Put the Cab file in a working folder to play in.

2. Extract the Cab using a good unzipper like 7-Zip

3. You will get a whole bunch of files with weird names the only one that will make sense is the _setup.xml.

4. So let's open this in Note Pad and take a look.
First concentrate on translating all the filenames
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<characteristic type="touchpal.dll" translation="install">
<characteristic type="Extract">
<parm name="Source" value="touchpal.005" />
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

5. Simply said Rename "touchpal.005" to "touchpal.dll"
Any file left is either a .000 which is just a setup file not needed to make the app work so thow it away if it's mentioned in the XML file.

6. Now take a look at this part in the _setup.xml.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\DefaultIcon">
<parm name="" value="\Program Files\TouchPal\touchpal.dll,0" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\IsSIPInputMethod">
<parm name="" value="1" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\InprocServer32">
<parm name="" value="\Program Files\TouchPal\touchpal.dll" datatype="string" />
</characteristic>
<characteristic type="HKCR\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}">
<parm name="" value="TouchPal" datatype="string" />
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

7. Make a new Blank .txt file in this directory and rename .txt extension to .rgu.

8. Translate the above registry settings into a correct format, the translation below should be reasonably self explanatory.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
REGEDIT 4


[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\DefaultIcon]
@="\\Windows\\touchpal.dll,0"

[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\IsSIPInputMethod]
@="1"

[HKEY_CURRENT_USER\CLSID\{802C691C-EB46-442c-BC54-DC2C42B156C3}\InprocServer32"]
@=""\\Windows\\touchpal.dll"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

9. Put this information into the rgu file and be sure leave one blank line at the end.
As you can see i have changed the directory to Windows. Since everything you flash to rom starts out in the Windows directory anyway there's no sense in copying it into another directory later on because then it will take up twice the amount of space on the device.

At the moment i think that the best way to interpret the empty Param Name is as either "default" or @. I used @ because it's what i see mostly used for CLSID's. (Whatever they are good for)

10. No more need for the _setup.xml file thow it out of this folder.

11. At this point you should only have all the files that could be renamed and a .rgu file.

12. Time to get a Unique IDentifier Code.
Go here:
http://www.famkruithof.net/uuid/uuidgen
Press Create and copy the code.

13. Rename the something.rgu to 659626bc-7794-11dc-8314-0800200c9a66.rgu

14 Create a new blank.txt file and without doing anything with it rename it to 659626bc-7794-11dc-8314-0800200c9a66.dsm

15. In the case of this app, it will not need a shortcut in the folder nor an initflash.txt file
Create a blank textfile again and change the extension .lnk the extension should now dissapear. On the first and only line type "23#"\Windows\APPNAME.exe".
And then save the file as "Shortcutname.lnk".

16. Download BuildDSM.zip (ftp://xda:xda@ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/Core/Tools/BuildDsm.zip) and unzip.
Now read closely.
Drop the folder Containing all the files on top of the BuildDSM.exe.
The .DSM file should now populated with the needed info.
I still don't know what it's good for but i think it has some sort of use as some Cooks swear by it.
Why can tell my why this is so important? But you do this before adding initflash and option.xml becuase those will not go into rom.

17. Now this app will not need an initflashfiles.txt because it doesn't need a shortcut to the app but in case it does need it
Creeate a blank File with the name initflashfiles.txt
Write down:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Directory("\Windows\Start Menu\Programs"):-File("Shortcutname.lnk","\Windows\Shortcutname.lnk")

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Take note off adding blank lines just for fun.

17. Create another Blank text file and name it option.xml.
Open it in notepad.

And paste in this
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="My New SuperDuper App" group="Applications - 300 Group" checked="true">
<Tip>My New SuperDuper App</Tip>
<Guid type="p">659626bc-7794-11dc-8314-0800200c9a66</Guid>
</Item>
</Items>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Note that You put the earlier created UID into the xml file.
If your package consists of more than one folder (in the case of WLM and office)
Ad extra lines for every extra folder with their UID numbers.

So it will look like this.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Guid type="p">659626bc-7794-11dc-8314-0800200c9a66</Guid>
<Guid type="1">50898fbc-e5a3-45e4-9cf2-a04a8a01d69b</Guid>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now when you open your BuildOS this app will be selectable so you can choose to Cook it or not.
Oem Packages without option.xml will always be cooked into rom.
Note that "<Tip>" is the info when you highlight the App in BuildOs.

18. Fini

I will ad a part how to adjust it so you can make SD installer for this to, soon.

Variables found in installers

%CE1% = Program Files
%CE2% = Windows
%CE4% = Windows\Start Up
%CE5% = My Documents
%CE8% = Program Files\Games
%CE11% = Windows\Start Menu\Programs
%CE14% = Windows\Start Menu\Programs\Games
%CE15% = Windows\Fonts
%CE17% = Windows\Start Menu

There are more variables so if any one knows more please tell.
Please report Inconsistencies and let's see who's the first one to get a working TouchPal OEM package.
BTW we can't publish it as it's not going to be Freeware and it's being patented at the moment. Which doesn't mean you can make it for personal use and PM it so others can test it ;)
You can grab the cab from http://www.cootek.com/ or try with another of course.

eefurt
11th October 2007, 08:37 AM
Hi all,

what is a good base-rom to start cooking from?

Noonski
11th October 2007, 01:32 PM
Dopod Asia WWE 1.17
Uploading RUU_signed_OS5.2.1437.zip (http://rapidshare.com/files/61786658/RUU_signed_OS5.2.1437.zip)

Added to Thread 9


Thread 9...... nice name for a Band!

tiggerbcn
11th October 2007, 02:27 PM
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_HTCThemeL ayout.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

Noonski
11th October 2007, 08:49 PM
Anyone Any Idea? About the TSK issue i never delved into this.

bram_smulders
12th October 2007, 10:33 AM
Anyone Any Idea? About the TSK issue i never delved into this.

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

mzmiric5
12th October 2007, 10:35 AM
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_HTCThemeL ayout.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

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.

Noonski
12th October 2007, 12:04 PM
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.

Cloudyfa
12th October 2007, 03:12 PM
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?.

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="\\Extended_ROM\\Config.txt"
"AutoRun"="\\Extended_ROM\\AutoRun.exe"
(change Extended_ROM to Windows)

Then modify Config.txt, add this line:
EXEC: \Windows\CusTSK.exe \Windows\Your Theme.tsk

Bono2007
12th October 2007, 06:57 PM
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:

tiggerbcn
12th October 2007, 07:50 PM
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="\\Extended_ROM\\Config.txt"
"AutoRun"="\\Extended_ROM\\AutoRun.exe"
(change Extended_ROM to Windows)

Then modify Config.txt, add this line:
EXEC: \Windows\CusTSK.exe \Windows\Your Theme.tsk



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"

Seiya
13th October 2007, 12:25 AM
It works


but have uou save the config.txt file in unicode?

Noonski
13th October 2007, 02:26 AM
ShitFuckingShit.

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 fuck shit.

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......

starlit
14th October 2007, 05:50 AM
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!!

tiggerbcn
14th October 2007, 02:56 PM
It works


but have uou save the config.txt file in unicode?

No, this where my error. Thanks

Noonski
14th October 2007, 04:11 PM
No, this where my error. Thanks

Now for the real challenge.

Have you ever tried changing the path of Ex_rom to \Storage Card\Extended_ROM\ ???

Hehehehehe?

orouborus
14th October 2007, 06:11 PM
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!!

i also tried using total commander but it didnt work also.... tried copying the notes file from windows tree and there was an error, could this be really done and make a cab file out of it?

lliw
16th October 2007, 09:41 PM
Hi everybody,

I'm quite new here. And very interessed by this cooking post.
Actually i'm trying to cook my own rom , first with a skin custom.
It already works but now i'd like to go further.
I saw in many post that the actual way to change registry settings is for most of you with the use of a third part prog like phbm (or resco ...) or by using a batch.
But is there anyone here who knows how to directly set regristry string in the dump rom? It would be very efficient for customization.
I don't have the answer but i'll work hard to find it. But if someone already knows it'll save me some time.
I'll post news a soon as i find something.

Cu soon.

mzmiric5
16th October 2007, 09:56 PM
Hi everybody,

I'm quite new here. And very interessed by this cooking post.
Actually i'm trying to cook my own rom , first with a skin custom.
It already works but now i'd like to go further.
I saw in many post that the actual way to change registry settings is for most of you with the use of a third part prog like phbm (or resco ...) or by using a batch.
But is there anyone here who knows how to directly set regristry string in the dump rom? It would be very efficient for customization.
I don't have the answer but i'll work hard to find it. But if someone already knows it'll save me some time.
I'll post news a soon as i find something.

Cu soon.
i'm new to this but as noonski already wrote in this topic(or it was some other) registry changes are possible using .rgu and .dsm files to put the registry settings in to the rom. Try reading this topic from beginning and u'll find that post, but u could ask for specific changes and maybe some1 could tell u where is it in the registry. i hope i helped

lliw
16th October 2007, 11:48 PM
ok thank mate.
I'll check for it tomorrow.
At the moment i don't need a particuliar reg string. I already know which one i want to edit and/or delete.

At least i'm wondering if it's possible to use the RIL (Radio interface layer) to use particular function of the rom radio ( i'm not sure if post it in the right place but maybe it will interest someone).

And did you know for the one who possess an orange custom rom that there is a particuliar zip (provision.zip ) in the dump which is password locked.
It contains some orange custom xml files.
But these guyz are very funny. Why encrypting these files if the password is so poor. Make the try the password is 1234. I tried it tonight on my Elf 1.14.74.1 FRE.
There is nothing really interesting in this zip but it was funny to break through.

CU

Will

evlimeca
17th October 2007, 12:25 AM
Noonski, i redid all the cube graphics, nothing special just some masks to create a glossy look and give it some lighting effects, i can definitely improve but just wanted to test.

I install all the files in my windows folder and they voerwrite the ones on the rom...but for some reason the app launcher one won't overwrite....any idea's what might be wrong? i posted in the cube customization thread but no answers yet.

I've uploaded the cube to this post in hopes that its just my rom being stupid...who knows what the pda viet guys did to it so i'm forced to look at thier green coloring forever. have a look and lemme know

Edit: if anyone else wants to give it a try for me. just download the unzip the file. Connect to activesynch, open my device. In explorer, click tools>folder options>view....uncheck "hide system folders" after that you just drop the .brn files into the windows folder on your phone...if you dont like it you can just delete them, the ROM ones never go away so you can go right back to the originals....if something really bad happens and you lose all your cube graphics, send me a PM and i'll make sure you get the originals or better back.

also please feel free to give input, these were all made fast just using the same mask technique...with a weeks time i could make something super hot.

Noonski
17th October 2007, 04:10 AM
ok thank mate.
I'll check for it tomorrow.
At the moment i don't need a particuliar reg string. I already know which one i want to edit and/or delete.

At least i'm wondering if it's possible to use the RIL (Radio interface layer) to use particular function of the rom radio ( i'm not sure if post it in the right place but maybe it will interest someone).

And did you know for the one who possess an orange custom rom that there is a particuliar zip (provision.zip ) in the dump which is password locked.
It contains some orange custom xml files.
But these guyz are very funny. Why encrypting these files if the password is so poor. Make the try the password is 1234. I tried it tonight on my Elf 1.14.74.1 FRE.
There is nothing really interesting in this zip but it was funny to break through.

CU

Will

Well i replied but the post did not save.

Just find any RGU file and put your custom settings for registry there.

I Patched the provisiong zip to because the Dutch NL T-Mobile settings were incorrect.

I thought i had posted a how to change Provisioning file somewhere in wizard thread.

Noonski
17th October 2007, 04:15 AM
Noonski, i redid all the cube graphics, nothing special just some masks to create a glossy look and give it some lighting effects, i can definitely improve but just wanted to test.

I install all the files in my windows folder and they voerwrite the ones on the rom...but for some reason the app launcher one won't overwrite....any idea's what might be wrong? i posted in the cube customization thread but no answers yet.

I've uploaded the cube to this post in hopes that its just my rom being stupid...who knows what the pda viet guys did to it so i'm forced to look at thier green coloring forever. have a look and lemme know

Edit: if anyone else wants to give it a try for me. just download the unzip the file. Connect to activesynch, open my device. In explorer, click tools>folder options>view....uncheck "hide system folders" after that you just drop the .brn files into the windows folder on your phone...if you dont like it you can just delete them, the ROM ones never go away so you can go right back to the originals....if something really bad happens and you lose all your cube graphics, send me a PM and i'll make sure you get the originals or better back.

also please feel free to give input, these were all made fast just using the same mask technique...with a weeks time i could make something super hot.

In My Roms they are AL_06_HL.png til AL_06_HL.png & AL_Bkgd.png.
Maybe you need to remove your start up items in Windows\Start UP\
Because There are some preloads that start the cube. Also you might need to restart before the graphics kick in.


I have added my Fake Ext_Rom Oem Packages.

bram_smulders
18th October 2007, 12:04 PM
Hi guys, i was cooking on my new project and i ran into a problem.
I've added dDockView to the oem folder started buildos.

It all went well but at the creating of the registry he gives an error. I found out that it had to do with the rgu file, but i can't find any problems with it, i thing it should work but it didnt.

this is the rgu file:

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\ dDockPlugin]
"DLL" = "dDockPlugin.dll"
"Enabled" = dword : 00000001
"Flags" = dword : 00000000
"Options" = dword : 00000000
"Order" = dword : 0000001E
"Selectability" = dword : 00000001
"Type" = dword : 00000004

[HKEY_CURRENT_USER\Software\dopod\dDock]
"background" = "\Windows\BackGround.png"
"clockcolor" = dword : 00000000
"clockflag" = dword : 00000001
"datecolor" = dword : 00000000
"Lockflag" = dword : 00000000
"lunarcolor" = dword : 00000000
"lunaflag" = dword : 00000000
"weekdaycolor" = dword : 00000000
"weekdayflag" = dword : 00000000



anyone can help me?
mayb i'm missing something here

gr. bram

Noonski
18th October 2007, 04:02 PM
Hi guys, i was cooking on my new project and i ran into a problem.
I've added dDockView to the oem folder started buildos.

It all went well but at the creating of the registry he gives an error. I found out that it had to do with the rgu file, but i can't find any problems with it, i thing it should work but it didnt.

this is the rgu file:

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\ dDockPlugin]
"DLL" = "dDockPlugin.dll"
"Enabled" = dword : 00000001
"Flags" = dword : 00000000
"Options" = dword : 00000000
"Order" = dword : 0000001E
"Selectability" = dword : 00000001
"Type" = dword : 00000004

[HKEY_CURRENT_USER\Software\dopod\dDock]
"background" = "\Windows\BackGround.png"
"clockcolor" = dword : 00000000
"clockflag" = dword : 00000001
"datecolor" = dword : 00000000
"Lockflag" = dword : 00000000
"lunarcolor" = dword : 00000000
"lunaflag" = dword : 00000000
"weekdaycolor" = dword : 00000000
"weekdayflag" = dword : 00000000

anyone can help me?
mayb i'm missing something here

gr. bram
You have to use double dashes

"background" = "\\Windows\\BackGround.png"

Noonski
20th October 2007, 06:39 PM
Please be aware that most of this tutorial comes from Information written by others, but then edited my way.

1. There are two types of ROM downloads. A selfextracting version that runs the updater automaticly (ussualy a stock ROM). And then there's the zip package that shows you all the files inside.

2. With the selfextracting EXE you simply rightclick on it and choose to extract here/all. You need a Separate Extractor like Winzip or 7-Zip to do this.
The file we are after is the "RUU_Signed.nbh".

3. With the zip type it's the same. Extract the package and look for "RUU_Signed.nbh".

4. Place the "RUU_Signed.nbh" into "C:\Core\HyperCore\Extract\Source".

5. Run "C:\Core\HyperCore\Panel\Extract\1. DumpRom" And press Enter in the next Dos Dialog Box, This will take some time.

6. Once it's done you get two options "1. Start Package Tool" & "2. Move Os.NB to..". Press 2 first, wait and then press 1 and again Press Anter at the filled DOS screen.

7. Now you get 5 options. Press Option "3. Manual". This starts the package tool.

8. Click > File > Open > Browse to "C:\Core\HyperCore\Extract\" and select the "dump" folder. Click "OK".

9. Click > Tools > Build Packages. And wait a while. For now Ignore Missing files. IF you are Extracting a Stock rom these shouls be around three missing dsm files. Extracting a custom rom might result in more.

10. Rename the "C:\Core\HyperCore\Extract\dump" Folder into "C:\Core\HyperCore\Extract\Packages". And then click > File > Exit, in the Package Tool.

11. Back in the 5 option Dos Dialog, choose option "4. Move Sys & OEM...". When it asks you if you want to make a backup folder Choose whatever you want. Me personally being confident enough i always Choose No to this. Wait A While till the Dos Dialog is back into 5 option screen. Then Choose Option "5. Moving OS.NB...". Once that's done Press Enter to Exit out of Extracting Dos Box.

12. Now we need to extract XIP to Build Folder. Run "C:\Core\HyperCore\Panel\Extract\3. DUMP XIP".

13. Running it the first time will open the Folder that needs the "OS.nb". It should allready be there since we copied it over. If the Dump XIP Dos Dialog doesn't show any option to continue, close it leaving the "C:\Core\HyperCore\Extract" open.

14. The second time around it should have the "Enter"" Option, so press "Enter". Press Enter To Continue, Untill you have 2 options. First do Option "1. Copy XIP to....." Press Enter and you are back to two options. Press Option "2. Move OS.NB to...." (Ignore the Fact it is mentioning the wrong Folders). Once option 2 is done Press Enter to Exit.

15. You are now ready to start Cooking. Thanks to Anichillus for including the instruction on how to extract in the HyperCore Kitchen and modifying all the scripts. And thanks to It'sme for the original extracting script Pof & the Blasphemer for making it more user friendly and Bepe for the Package Tool.

Please report any mistakes ore additions for a better cooking experience.

Xtriny
24th October 2007, 12:04 AM
Hi all, I have a dumb question. I cooked my own ROM, but I did some mistake during rebuilding. After Flash it stucks on first boot screen. I tried to only extract and rebuild original ROM, without changes and the same (after rebuitd it was smaller) Can anyone tell me please how to rebuild it step by step. Thanks a lot

Noonski
24th October 2007, 11:42 AM
Hi all, I have a dumb question. I cooked my own ROM, but I did some mistake during rebuilding. After Flash it stucks on first boot screen. I tried to only extract and rebuild original ROM, without changes and the same (after rebuitd it was smaller) Can anyone tell me please how to rebuild it step by step. Thanks a lot

Well first of course the above.
Extracting A Rom.
Then taken from Anichillus tutorial:
1. BUILD-ing :

· Now that you have dumped your first ROM, you must learn how to Build it back to the flash-able so that you may flash it to the PDA. Okay, so we don’t need to work anymore on the EXTRACT Panel, so close it and go to the BUILD Panel. For beginning, i strongly disagree on starting to “cook” right away. So please follow my advice and you may actually learn something.
· BuildOS – This will prompt you with couple of choices. It’s pretty easy. Select “1” and this will start the actual BuildOS program. Since you just extracted the ROM, you won’t see any selectable packages there. Those are made possible by a little “option.xml” placed in the OEM or SYS folder. I will provide in the near future a tutorial on how to build that too, but i think it’s useless. All packages, programs you want to exclude from the ROM it’s easier to move them in or out of the OEM and SYS folder than editing the option.xml so you can check them later. Good, now click on the little green arrow and it will start processing the ROM. Beware for errors. If any errors occur, close the BuildOS and the batch program and fix the error and then try again! You shouldn’t see any errors now, most of the cases there are duplicate files that mess with the program. When it writes “Done” on the bottom, you can close it so that the batch program may continue
· (batch= http://en.wikipedia.org/wiki/Batch_file). It will start creating the ROM, you’ll see alot of text ... not really important. When it’s finished it will go back to the status screen. The options are numbered as you should use them so again no rocket science. That’s it. It wasn’t that hard, was it ?

And don't use the suplied RUU updater in german unless you have replaced it with the updated elf updater and Scripts.

Xtriny
24th October 2007, 02:27 PM
Thanks for your advice, but still the same. I did everything you said, but the RUU_Signed file is after rebuilding smaller (original RUU_Signed had 57,3MB, after rebuild it has 57,1MB) without any changes.

Noonski
24th October 2007, 10:42 PM
Thanks for your advice, but still the same. I did everything you said, but the RUU_Signed file is after rebuilding smaller (original RUU_Signed had 57,3MB, after rebuild it has 57,1MB) without any changes.

Why don't you try with the Base ROM suplied in the first threads?

Xtriny
24th October 2007, 11:01 PM
Downloading right now. I used probably "bad" ROM to cooking ;-)

crazy_m
25th October 2007, 04:55 PM
I had the same problem. I have used RUU_Elf_DOPODASIA_WWE_1.17.707.2B_4.1.13.46_02.97. 90_BLUE_Ship.exe in kitchen but without success.

Xtriny
25th October 2007, 06:53 PM
Still the same!!!
So...here is what I did, step by step:

Installed Kitchen, applied ACK, RUU, and Vista Batch fix (running on Vista Home Premium) and overwrite files.
Downloaded RUU_signed_OS5.2.1437 (as provided by Noon), copied RUU_Signed to C:\Core\Hypercore\extract\source\
Run DumpROM (from C:\Core\HyperCore\Panel\Extract\), when done, choosed option 2. (move OS...), than option 1. (start PKG)
Than it shows 5 options - choosed option 3 (manual), in PKG tool opened File-Open and choosed dump folder from C:\Core\HyperCore\Extract - than choosed Tools-Build Packages. Than Rename Dump folder to Packages and exit PKG tool.
Than choosed option 4 (move OEM and SYS), when done, choosed option 5 (move OS) and exit when done.
Run DumpXIP from C:\Core\HyperCore\Panel\Extract - it opened Explorer window with OS_nb, than pressed ENTER - when done, choosed option 1 copy XIP, when done, choosed option 2 copy OS and than exit.

I did no changes

REBUILDING:
Run BuildOS from C:\Core\HyperCore\Panel\Build - choosed option 1 (Start build OS) - when it Started, click on green arrow (no errors provided). whne done, exit it and choosed option 2. Create OS_nb (it shows a lot of text) - when done, choosed option 3. start htcrt
In htcrt in ROM Builder changed device to ELF, than choosed OS_nb from opened Explorer window (C:\Core\HyperCore\Tools\Convert) and click on Build ROM and save file as RUU_Signed
htcrt shows this:

ROM build process started...
Ceating temporary unsigned ROM file...
Writing ROM header...
System is 400h
Writing ROM contents:
OS.nb: 100%
Preparing destination...
Preparing ROM signer...
Signing ROM and copying it to destination...
Maximal chunk size is 1024 Kb
DONE: All seems to be ok!

click on OK and EXIT

the RUU_Signed file is after rebuild about 300kb smaller, than original

Than flash, but after flash it stucked on first boot screen.

Please does anybody know, what I did wrong?

P.S. tried 3 various ROMs, but still tha same problem...

Noonski
26th October 2007, 01:39 PM
Still the same!!!
So...here is what I did, step by step:

Installed Kitchen, applied ACK, RUU, and Vista Batch fix (running on Vista Home Premium) and overwrite files.
Downloaded RUU_signed_OS5.2.1437 (as provided by Noon), copied RUU_Signed to C:\Core\Hypercore\extract\source\
Run DumpROM (from C:\Core\HyperCore\Panel\Extract\), when done, choosed option 2. (move OS...), than option 1. (start PKG)
Than it shows 5 options - choosed option 3 (manual), in PKG tool opened File-Open and choosed dump folder from C:\Core\HyperCore\Extract - than choosed Tools-Build Packages. Than Rename Dump folder to Packages and exit PKG tool.
Than choosed option 4 (move OEM and SYS), when done, choosed option 5 (move OS) and exit when done.
Run DumpXIP from C:\Core\HyperCore\Panel\Extract - it opened Explorer window with OS_nb, than pressed ENTER - when done, choosed option 1 copy XIP, when done, choosed option 2 copy OS and than exit.

I did no changes

REBUILDING:
Run BuildOS from C:\Core\HyperCore\Panel\Build - choosed option 1 (Start build OS) - when it Started, click on green arrow (no errors provided). whne done, exit it and choosed option 2. Create OS_nb (it shows a lot of text) - when done, choosed option 3. start htcrt
In htcrt in ROM Builder changed device to ELF, than choosed OS_nb from opened Explorer window (C:\Core\HyperCore\Tools\Convert) and click on Build ROM and save file as RUU_Signed
htcrt shows this:

ROM build process started...
Ceating temporary unsigned ROM file...
Writing ROM header...
System is 400h
Writing ROM contents:
OS.nb: 100%
Preparing destination...
Preparing ROM signer...
Signing ROM and copying it to destination...
Maximal chunk size is 1024 Kb
DONE: All seems to be ok!

click on OK and EXIT

the RUU_Signed file is after rebuild about 300kb smaller, than original

Than flash, but after flash it stucked on first boot screen.

Please does anybody know, what I did wrong?

P.S. tried 3 various ROMs, but still tha same problem...

First The Obvious, Did you flash USPL?

Make a New folder in OEM folder called Missing and place files from Missing Files folder into it.

Second it might be in the RUU updater.

Place the RUU-Signed into folder of any other Custom ROM along side the Update Utility.

Xtriny
26th October 2007, 01:50 PM
Hi Noon,

no, I didnt flash uspl in this ROM (I did CID unlock a few weeks ago)
In missing Folder I had three folders - I put them to its place, as provided in PKGTool (but it was only when I used another custom ROM. In original ROM nothing missing)
I tried to use RUU_Signed file with another RomUpdateUtility (from working ROM) but still the same

One more thing - flash process of this rebuilded ROM is much slower, than other ROMs, but it goes to 100%


P.S. In PKG tool it shows this:
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
4e71f192-a1e0-da69-6fa4-eef7baef76bd.dsm

I found this three files in XIP directory. Do I have to do anything whit it?

Swiftblade
26th October 2007, 03:25 PM
Hi Noon,

no, I didnt flash uspl in this ROM (I did CID unlock a few weeks ago)
In missing Folder I had three folders - I put them to its place, as provided in PKGTool (but it was only when I used another custom ROM. In original ROM nothing missing)
I tried to use RUU_Signed file with another RomUpdateUtility (from working ROM) but still the same

One more thing - flash process of this rebuilded ROM is much slower, than other ROMs, but it goes to 100%


P.S. In PKG tool it shows this:
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
4e71f192-a1e0-da69-6fa4-eef7baef76bd.dsm

I found this three files in XIP directory. Do I have to do anything whit it?

Hi Xtriny.. You seems to be doing everything right then the most likely explantion for this is that you have a missing file "wince.nls" inside the WinCENLS_WWE folder under SYS. Go check Build-->SYS-->WinCENLS_WWE and see whether you have the "wince.nls file. Without this file the Windows CE can't start...

Xtriny
26th October 2007, 03:41 PM
Hi Xtriny.. You seems to be doing everything right then the most likely explantion for this is that you have a missing file "wince.nls" inside the WinCENLS_WWE folder under SYS. Go check Build-->SYS-->WinCENLS_WWE and see whether you have the "wince.nls file. Without this file the Windows CE can't start...

You're right man :-) I cant find it anywhere. So what to do?

Noonski
26th October 2007, 04:33 PM
You're right man :-) I cant find it anywhere. So what to do?

Here it is attached.

Xtriny
26th October 2007, 05:05 PM
Here it is attached.

Thanks Noon, but still the same. BTW, in your attached folder, I found only .dsm file, option.xml file, but no wince.nls file....

Swiftblade
26th October 2007, 05:36 PM
Thanks Noon, but still the same. BTW, in your attached folder, I found only .dsm file, option.xml file, but no wince.nls file....

Xtriny... you must set your stupid Vista folder to see the hidden files and system files. If not, what cannot be seen by the program will not be copied or built into the ROM and CE will not start.. Hope this help.

Edited: Notice the WinCENLS_WWE folder given by Noonski has the Option.xml file. Delete it for the present moment.

Xtriny
26th October 2007, 05:40 PM
Xtriny... you must set your stupid Vista folder to see the hidden files and system files. If not, what cannot be seen by the program will not be copied or built into the ROM and CE will not start.. Hope this help.

Edited: Notice the WinCENLS_WWE folder given by Noonski has the Option.xml file. Delete it for the present moment.

Heh, my mistake...I can see it now, so it means, that I had wince.nls already. The only file I didnt have is option.xml...Trying to rebuild...

EDIT: still doesnt work. The rebuilded RUU_Signed file is still about 300kb smaller than the original - Try to do everything once more with new Explorer settings

Xtriny
26th October 2007, 06:24 PM
IT WORKS!!! The only thing was to set Explorer to show system and hidden files, than reinstal Hypercore kitchen....that's all.

Thanks to Swiftblade and Noonski for their great work and help :-)

Now I can start to cook.... :-)

alx75
26th October 2007, 07:37 PM
3. start htcrt
In htcrt in ROM Builder changed device to ELF, than choosed OS_nb from opened Explorer window (C:\Core\HyperCore\Tools\Convert) and click on Build ROM and save file as RUU_Signed


Let me explain,
1.In htcrt in ROM Builder changed device to ELF

2.Click on <...>(System),choose the OS_nb from opened Explorer window (C:\Core\HyperCore\Tools\Convert)

3.Click on <...>(Splash),choose the MainSplash.nb from (HyperCore\Extract\Splash)

4.Then click on Build ROM and save file as RUU_Signed(on Desktop)

5.Click on OK and EXIT

6.Choose no.4 and flash it

7.Cheersss, a new ROM has created

Correct me if I'm WRONG,me also had a few attemps(failure) till I found out:D :D :D

Xtriny
26th October 2007, 07:40 PM
3. start htcrt
In htcrt in ROM Builder changed device to ELF, than choosed OS_nb from opened Explorer window (C:\Core\HyperCore\Tools\Convert) and click on Build ROM and save file as RUU_Signed


Let me explain,
1.In htcrt in ROM Builder changed device to ELF

2.Click on <...>(System),choose the OS_nb from opened Explorer window (C:\Core\HyperCore\Tools\Convert)

3.Click on <...>(Splash),choose the MainSplash.nb from (HyperCore\Extract\Splash)

4.Then click on Build ROM and save file as RUU_Signed(on Desktop)

5.Click on OK and EXIT

6.Choose no.4 and flash it

7.Cheersss, a new ROM has created

Correct me if I'm WRONG,me also had a few attemps(failure) till I found out:D :D :D


Number 3. is wrong. You cant change the splash with this kitchen. Do everything without it, it should work

alx75
26th October 2007, 07:43 PM
Number 3. is wrong. You cant change the splash with this kitchen. Do everything without it, it should work

U try 1st,then see if it works.BTW is Splash not SPL.
The MainSplash.nb is Original from what U dump out
Sorry for my poor english

Xtriny
26th October 2007, 07:48 PM
U try 1st,then see if it works.BTW is Splash not SPL

I tried, it works. in htcrt choose only os_nb and change device to elf. That's all

alx75
26th October 2007, 07:54 PM
I tried, it works. in htcrt choose only os_nb and change device to elf. That's all

But U cannot boot up(Fully) if never add the mainsplash_OS.
Cos I got the same problem as U had now.
Anyway if it works For U,then Cheerssss

Xtriny
26th October 2007, 08:07 PM
One question:
I would like to add new HTC Home with 6 tabs (I used ROM as privided by Noonski in firsts threads, it has only 3 tabs). How to do it? Can I only add OEM Package to OEM folder, or do I have to delete previous files? thx

Swiftblade
26th October 2007, 08:17 PM
But U cannot boot up(Fully) if never add the mainsplash_OS.
Cos I got the same problem as U had now.
Anyway if it works For U,then Cheerssss

Adding mainsplash is optional. You can or do without it and it will flash successfully. Flash only if you want to change the main spash screen.. Try cooking and enjoy!

Noonski
27th October 2007, 02:12 AM
You can only add the original Mainsplash from Extracted Rom.

It seems that most conversion tools don't convert custom Splash screens.

Pherhaps it has to do with the amount of bytes in the file.

Good to see your problem is gone Xtriny.

Was busy finishing my new SPC rom and all the new cool stuff being finished here:

http://forum.xda-developers.com/showthread.php?p=1581981#post1581981

Most new Apps from Duo Touch are working.

Swiftblade
27th October 2007, 02:21 AM
You can only add the original Mainsplash from Extracted Rom.

It seems that most conversion tools don't convert custom Splash screens.

Pherhaps it has to do with the amount of bytes in the file.

Good to see your problem is gone Xtriny.

Was busy finishing my new SPC rom and all the new cool stuff being finished here:

http://forum.xda-developers.com/showthread.php?p=1581981#post1581981

Most new Apps from Duo Touch are working.

HI Noonski.... nice jobs on the Duo Touch applications there. Really impressive! Can I use them in building my next new ROM? (HOPE.. HOPE)

One more question: How to use dword to delete "Quickdial" from the registry to release the favourite persons tab in Kaiser Home UI plug-in?

Noonski
27th October 2007, 02:47 AM
HI Noonski.... nice jobs on the Duo Touch applications there. Really impressive! Can I use them in building my next new ROM? (HOPE.. HOPE)

One more question: How to use dword to delete "Quickdial" from the registry to release the favourite persons tab in Kaiser Home UI plug-in?

Well most of the apps were eventually pieced together by others.

And they are free to cook that's what they are for, there are more OEM's then Cab's. And ussualy it's smarter to start with OEM packages as Cooks are better to find issues then most the people just installing a cab.

Seen your Rom looking nice, have you thought about bringing the HTC home down with the nice Iphone Icons?

the trick is that it originally should be string value
"Quickdial"="1.232323.232.32.32.3"

As soon as you change it into a dword with any fake value (i use 0)
It releases it

So
"Quickdial"=dword:0

pronto

Xtriny
27th October 2007, 02:55 AM
Another problem....lol

I would like to replace HTC Home with newer with 6 TABS (KAISER HOME UI), so I deleted every htc home file from OEMAPPS folder and put HTC HOME Package to OEM folder, but it doesnt work. Which settings do I have to change, please?

Swiftblade
27th October 2007, 03:04 AM
Well most of the apps were eventually pieced together by others.

And they are free to cook that's what they are for, there are more OEM's then Cab's. And ussualy it's smarter to start with OEM packages as Cooks are better to find issues then most the people just installing a cab.

Thanks. I will try to build some of these nice features in my next ROM..:D

Seen your Rom looking nice, have you thought about bringing the HTC home down with the nice Iphone Icons?

Thank again.. Yes, I would really like to to do that but unfortunately I am no good in graphic design stuff like you. You are a real pro in those graphic stuff. I have to resign to what others can offer me...:(

the trick is that it originally should be string value
"Quickdial"="1.232323.232.32.32.3"

As soon as you change it into a dword with any fake value (i use 0)
It releases it

So
"Quickdial"=dword:0

pronto

I tried "Quickdial"=dword:0 trick in the HTC Home OEM package but didn't work out...Why? Overwritten?

Noonski
27th October 2007, 03:27 AM
Thanks. I will try to build some of these nice features in my next ROM..:D



Thank again.. Yes, I would really like to to do that but unfortunately I am no good in graphic design stuff like you. You are a real pro in those graphic stuff. I have to resign to what others can offer me...:(



I tried "Quickdial"=dword:0 trick in the HTC Home OEM package but didn't work out...Why? Overwritten?

Funny graphicly i'm a doovus, but i used to support Adobe Applications so i now better how to cheat.

Oke it should be:
[HKEY_LOCAL_MACHINE\Software\OEM\MASD]
"QuickDial"=dword:0

But it could be that it is overwritten by another RGU file.

You could also try the mothod of removing the Entry from Default.hv
(never Edit .hv the settings don't stick with me)

It could also be that the registry setting is in an provxml file which will always override the RGU (which goes into .hv files in the end).

Or remove the setting from ProvXML , RGU and .HV files ;)

Swiftblade
27th October 2007, 03:45 AM
Funny graphicly i'm a doovus, but i used to support Adobe Applications so i now better how to cheat.

Oke it should be:
[HKEY_LOCAL_MACHINE\Software\OEM\MASD]
"QuickDial"=dword:0

But it could be that it is overwritten by another RGU file.

You could also try the mothod of removing the Entry from Default.hv
(never Edit .hv the settings don't stick with me)

It could also be that the registry setting is in an provxml file which will always override the RGU (which goes into .hv files in the end).

Or remove the setting from ProvXML , RGU and .HV files ;)

Many thanks for your thoughtful and eveready helps...:D Yes I did put in correctly the registry tweak given above. Looking into every ProvXML and RGUs and .HV files will be like finding a needle in a haystack.. Shit... haha;) Leave it alone for now... oh oh ..maybe can write in ProvXML to overwrite the others... workable?

Xtriny
27th October 2007, 07:25 PM
Hi guys. Pls, where to find settings to change pagepool?

Noonski
27th October 2007, 08:27 PM
Many thanks for your thoughtful and eveready helps...:D Yes I did put in correctly the registry tweak given above. Looking into every ProvXML and RGUs and .HV files will be like finding a needle in a haystack.. Shit... haha;) Leave it alone for now... oh oh ..maybe can write in ProvXML to overwrite the others... workable?

That might be a good idea.

I will look for these settings but i'm done for tonight.


Triny, Indeed we need a good tutorial to do this on Touch.
I haven't done this and would like to make my ROM 6 mb.

I think Bram smulders knows some one that knows how to do this.

Xtriny
27th October 2007, 08:34 PM
ok, tnx. I will make it with Smart pagepool changer, for now :-)

Swiftblade
27th October 2007, 11:51 PM
ok, tnx. I will make it with Smart pagepool changer, for now :-)

Xtriny,, don,t use the smart pageppol changer from Shark. Try this one by vippie, it's much easier and the pagepool is change within a minute...:D
http://forum.xda-developers.com/showthread.php?t=324594&highlight=change+pagepool

Noonski
28th October 2007, 01:44 AM
Xtriny,, don,t use the smart pageppol changer from Shark. Try this one by vippie, it's much easier and the pagepool is change within a minute...:D
http://forum.xda-developers.com/showthread.php?t=324594&highlight=change+pagepool


Thant's the same one i package with my Rom's...

But how do you cange it from scratch before you flash it ;)

bram_smulders
28th October 2007, 08:25 AM
Hi guys, can anyone take a look at this reg setting in their htc touch.

I want to know if it matches.

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CommManager\WLAN]
""="\\Windows\\WLanMgr.exe"
"DeviceName"="{98C5250D-C29A-4985-AE5F-AFE5367E5006}\\TIACXWLN1"


Gr. bram

Swiftblade
28th October 2007, 03:09 PM
Thant's the same one i package with my Rom's...

But how do you cange it from scratch before you flash it ;)

Need a hex editor to eidt the pagepool address to do the trick. You know anyone who is good in hex editing to help? I got the pagepool address for Touch somewhere somewhere in my lappy.....(Looking... looking.... still looking)

Xtriny
28th October 2007, 07:27 PM
Hi guys. I have a little problem with comm manager. I replaced the original with "Comm Manager 10B Touch by Tao", but WLAN doesnt work. Every other button works fine, but WLAN doesnt. If I tap on it, it working for a while, but WLAN stays off. If I turn on it in setting-connections-wlan, I cant turn it off anyway. Can you please hepl me, what can be wrong?


EDIT- it work yet. I have some bad settings in .rgu file

Noonski
29th October 2007, 01:26 AM
Hi guys, can anyone take a look at this reg setting in their htc touch.

I want to know if it matches.

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CommManager\WLAN]
""="\\Windows\\WLanMgr.exe"
"DeviceName"="{98C5250D-C29A-4985-AE5F-AFE5367E5006}\\TIACXWLN1"
Gr. bram

I have \\TNETW12511

At the end.

Hi guys. I have a little problem with comm manager. I replaced the original with "Comm Manager 10B Touch by Tao", but WLAN doesnt work. Every other button works fine, but WLAN doesnt. If I tap on it, it working for a while, but WLAN stays off. If I turn on it in setting-connections-wlan, I cant turn it off anyway. Can you please hepl me, what can be wrong?


EDIT- it work yet. I have some bad settings in .rgu file

What was it because i'm going to be using ten version to soon (eventhought i don't need it, let's say i'm thinking about it)

Xtriny
29th October 2007, 01:58 AM
What was it because i'm going to be using ten version to soon (eventhought i don't need it, let's say i'm thinking about it)

Hi Noon,

in original file, provided in CommManager OEM package is missing these settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CommManager\WLAN]
"DeviceName"="{98C5250D-C29A-4985-AE5F-AFE5367E5006}\\TNETW12511"

without it, WLAN cant work.

see the attachments - CommManager (blue) OEM Package with working .rgu file

Xtriny
29th October 2007, 02:01 AM
Hi guys, can anyone take a look at this reg setting in their htc touch.

I want to know if it matches.

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CommManager\WLAN]
""="\\Windows\\WLanMgr.exe"
"DeviceName"="{98C5250D-C29A-4985-AE5F-AFE5367E5006}\\TIACXWLN1"


Gr. bram


This is right:

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CommManager\WLAN]
"DeviceName"="{98C5250D-C29A-4985-AE5F-AFE5367E5006}\\TNETW12511"

tried it, and it is working

bram_smulders
29th October 2007, 08:21 AM
This is right:

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CommManager\WLAN]
"DeviceName"="{98C5250D-C29A-4985-AE5F-AFE5367E5006}\\TNETW12511"

tried it, and it is working

Jup fgured it out myself. Just copied from the original rom.
I think this is is also the problem of Xtriny.
Just change the reg key in the RGU file

gr. bram

Xtriny
29th October 2007, 01:15 PM
Another problem came....I have ShutXp in my ROM, but it doesnt work correctly.
I want to have today icon, but after every softreset it is gone...Any ideas? Or can someone please upload working ShutXp OEM Package? Thanks

Noonski
29th October 2007, 01:28 PM
Another problem came....I have ShutXp in my ROM, but it doesnt work correctly.
I want to have today icon, but after every softreset it is gone...Any ideas? Or can someone please upload working ShutXp OEM Package? Thanks

What do you mean with Today Icon?

If you have set to it right soft key, i ould suggest trying the left.

As it's a default bug that Windows does not keep information about modified Right key customization.

Xtriny
29th October 2007, 01:41 PM
What do you mean with Today Icon?

If you have set to it right soft key, i ould suggest trying the left.

As it's a default bug that Windows does not keep information about modified Right key customization.

I mean, that if you tap on shutxp, it will show a few possibilities - Shut down, Reset, Switch off the display - and under it you can choose "Today Icon". This place icon to the tray. But after soft reset is tray icon gone.

Xtriny
29th October 2007, 08:11 PM
So, I'm done...Finally, I'm running on my own ROM. I will test it for a few days, than I maybe upload it to xda....


Special thanks to:

Noonski for this thread, help and for great skin files
anichillus for the HyperCore Kitchen
pof for USPL
Swiftblade for help

Thanks guys

Swiftblade
30th October 2007, 03:06 AM
So, I'm done...Finally, I'm running on my own ROM. I will test it for a few days, than I maybe upload it to xda....


Special thanks to:

Noonski for this thread, help and for great skin files
anichillus for the HyperCore Kitchen
pof for USPL
Swiftblade for help

Thanks guys

Hi Xtriny... glad to know you got your own ROM runnin. Upload it to xda soon ya..

Noonski's initiatives of this cooking class is creating alot of awareness, interests and ROM makers. That's great and thanks to Noonski for upkeeping this interesting thread...:D

tiggerbcn
30th October 2007, 10:29 PM
Hello, I hope someone can help me, I do not find information of this:
I now have a spanish rom cooked based in the build 1.17.707.1B, have seen that last roms are based on several builds: Dopod1.17.707.2B and Dopod 1.17.707.2G That is what I must change into my rom, to put one of these builds?
I want to do it is a rom in Spanish based on the last build Dopod 1.17.707.2G
Thanks

mzmiric5
31st October 2007, 12:22 PM
Hey guys, i'm still working on my rom, does any1 know how to map the right hardware key(red one) long press to run touch dual endkey app. It should be possible to change that somewhere in rom(maybe registry).

Thanks in advance
Mišo

Noonski
31st October 2007, 01:28 PM
Hello, I hope someone can help me, I do not find information of this:
I now have a spanish rom cooked based in the build 1.17.707.1B, have seen that last roms are based on several builds: Dopod1.17.707.2B and Dopod 1.17.707.2G That is what I must change into my rom, to put one of these builds?
I want to do it is a rom in Spanish based on the last build Dopod 1.17.707.2G
Thanks

Ask your self this question:
Why?
Who ever said you need to upgrade to newer Dopod Rom versions?

Anyways the only one i know has some experience with some rom translations and locales is Bram from Dutch Touch & his new Touch Dual.

I think Koala worked from a french base.

Almost everything that is in a newer Touch rom can be ported to an older rom anyway. As long as you install the extra certificates that disable invalid software. The never version numbers don't say a lot at the moment as none of these are new and official AKU updates from M$

Hey guys, i'm still working on my rom, does any1 know how to map the right hardware key(red one) long press to run touch dual endkey app. It should be possible to change that somewhere in rom(maybe registry).

Thanks in advance
Mišo

Believe me i tried a lot of shit in the registry and replacing files to get exactly this going but the file responsible i think is "shutil.dll"
I tried looking at it in Reshack but nothin comes up. Anyone finds this will get one virtual beer.

pkoper
31st October 2007, 07:25 PM
need some help with the DUMP_ROM batch file. all it does for me is just wipe the SOURCE folder clean. the error message is : The system cannot find the batch label specified.
I know, probably something silly, but I am just stuck


*** figured it out, sometimes reading helps :-)

mzmiric5
31st October 2007, 08:13 PM
Peeps could some1 please post rom localization tutorial in this tread, i saw bram is localizing his new rom, it is very useful to have rom in different language that the base rom. i'm playing with the multi lang rom installer. BTW would any1 like to help with translations. When i get to that part i will post lang template(english) here so if any1 wants to help please upload version in your lang.

evermick
1st November 2007, 03:43 AM
Hey, you may want to try this Random Access Package. I make it as default contact manager (i.e. Random Access will be launched inside Phone and no need softkey hack!)

Seiya
1st November 2007, 06:42 AM
I'd like to change the build of my french ROM to a newest (17745 to 18533 for exemple)

I could take a ROM with this build and re-translate it

But is ther another way?


(For the PagePool : when you've modified it with the PagepoolSmartChanger, put the new os.nb in your ROM directory (whe the XIP is), and your futurs build will always have the pagepool you prefer)

bram_smulders
1st November 2007, 09:06 AM
Peeps could some1 please post rom localization tutorial in this tread, i saw bram is localizing his new rom, it is very useful to have rom in different language that the base rom. i'm playing with the multi lang rom installer. BTW would any1 like to help with translations. When i get to that part i will post lang template(english) here so if any1 wants to help please upload version in your lang.

Hi,

If you want to make multilanguage roms, youll need the MUI(Multilingual User Interface) files from microsoft. Then replace the 0409 files in the kitchen with the MUI files of your language.

Gr. bram

bram_smulders
1st November 2007, 09:08 AM
Hey, you may want to try this Random Access Package. I make it as default contact manager (i.e. Random Access will be launched inside Phone and no need softkey hack!)

Nice!! i'll use it in my next rom!

Gr. bram

evermick
1st November 2007, 10:33 AM
Find yourself a HEX editor.
It needs to be done before you package the ROM into .NBH.

1. Open OS.nb in your HEX editor.
2. goto offset 0x37B55A
3. change the value to your desired pagepool size:
4M = 40
6M = 60
8M = 80
12M= C0

Hope this help our chefs

mzmiric5
1st November 2007, 01:42 PM
Hi,

If you want to make multilanguage roms, youll need the MUI(Multilingual User Interface) files from microsoft. Then replace the 0409 files in the kitchen with the MUI files of your language.

Gr. bram

Yeah, but where can i find them. Earlier you posted the link to ms wm6 images for emulator that had multi lang and you sad that peeps can get MUI from there but i can't find the way to extract them from there. Can some upload some.

Noonski
1st November 2007, 07:03 PM
Another problem came....I have ShutXp in my ROM, but it doesnt work correctly.
I want to have today icon, but after every softreset it is gone...Any ideas? Or can someone please upload working ShutXp OEM Package? Thanks

I tried searching for some sort of Parameters for pxShutXp but could not find any.

Noonski
1st November 2007, 07:09 PM
Hey, you may want to try this Random Access Package. I make it as default contact manager (i.e. Random Access will be launched inside Phone and no need softkey hack!)

Very nice i'll check this out for sure and i'll paste it to the DUo Touch thread to.

Find yourself a HEX editor.
It needs to be done before you package the ROM into .NBH.

1. Open OS.nb in your HEX editor.
2. goto offset 0x37B55A
3. change the value to your desired pagepool size:
4M = 40
6M = 60
8M = 80
12M= C0

Hope this help our chefs

Holy Crap Cinderella this lookd almost to easy.
Thanks a bunch again. When i've done this i'll post it to the tute tutorial.
Good research.

Noonski
1st November 2007, 07:12 PM
need some help with the DUMP_ROM batch file. all it does for me is just wipe the SOURCE folder clean. the error message is : The system cannot find the batch label specified.
I know, probably something silly, but I am just stuck

It sounds likem your device.txt isn't set either to Artemis or ELF (if you have updated the needed files which allready have this set, in the ACK folder

pkoper
1st November 2007, 09:20 PM
It sounds likem your device.txt isn't set either to Artemis or ELF (if you have updated the needed files which allready have this set, in the ACK folder


That was exactly the case....

Using your tutorial I know dumped/extracted a couple of of ROM's, rebuilt them and flashed them back to the phone.

I would now like to try adding and removing programms. Can you recommend any reading on this?

Thanks,

Noonski
1st November 2007, 10:02 PM
That was exactly the case....

Using your tutorial I know dumped/extracted a couple of of ROM's, rebuilt them and flashed them back to the phone.

I would now like to try adding and removing programms. Can you recommend any reading on this?

Thanks,

Here's the Mini tutorial.

1. Download one of the OEM packages from the Repository in one of the first threads.
2. Place it in Sys folder (after unzipping)
3. Run Buildos, it might give errors about files allready existing. And you will it will tell you whee in the status bar.
3. Cut and paste the file from that location into the Packages folder with the red cross. (if not, and you chose to make a backup of the oem and sys folder while extracting) Build os will still use the original file from the backup up folder and not from the new OEM pack.
4. If it finishes without errors you can continue cooking.
5. Be on the look out for provxml files that are both in sys and oem as buildos doesn't always pick up on those and it might kill your rom.
6. Examine the rgu file and initflashes files in the oem package because you will be working a lot with them in the future.

pkoper
1st November 2007, 11:23 PM
Here's the Mini tutorial.

1. Download one of the OEM packages from the Repository in one of the first threads.
2. Place it in Sys folder (after unzipping)
3. Run Buildos, it might give errors about files allready existing. And you will it will tell you whee in the status bar.
3. Cut and paste the file from that location into the Packages folder with the red cross. (if not, and you chose to make a backup of the oem and sys folder while extracting) Build os will still use the original file from the backup up folder and not from the new OEM pack.
4. If it finishes without errors you can continue cooking.
5. Be on the look out for provxml files that are both in sys and oem as buildos doesn't always pick up on those and it might kill your rom.
6. Examine the rgu file and initflashes files in the oem package because you will be working a lot with them in the future.


Thank you.

Trying to add acrobat I copied the 300_Adob... folder to the sys folder. Buildos always says that the dupe files are in the temp\dump folder. This one is however wiped everytime buildos is run. So although I cut and paste the files to the packages folder the error returns every re run of buildos. without adobe the rom rebuilds and flashes fine.
Probably a real noob mistake.... but help appreciated.

pkoper
1st November 2007, 11:34 PM
@noonski

I have to place the oem package in the build area not extract, right?

cheers

koala996
2nd November 2007, 01:17 AM
Thank you.

Trying to add acrobat I copied the 300_Adob... folder to the sys folder. Buildos always says that the dupe files are in the temp\dump folder. This one is however wiped everytime buildos is run. So although I cut and paste the files to the packages folder the error returns every re run of buildos. without adobe the rom rebuilds and flashes fine.
Probably a real noob mistake.... but help appreciated.

I think I can answer you .... in fact if you look everywhere.. you will see two URL ... one "temp\dump" (that is in fact what is currently creating...) and another with where you have to look for the file.

Check the lower bar of the BuildOS when running it... you'll see "Processing: SYS\..." and that's where you should find which directory has the already used file ! The MessageBox you get saying "The file 'temp\dump\...." exists already just tells you WHICH FILE.

So you have to take the url on the BuildOS windows.. showing now "Error, last status: "Processing: OEM\...." and then look for the file pointed by the MessageBox (after 'temp\dump\).

I hope it helps you :) good night

koala996
2nd November 2007, 01:19 AM
@noonski

I have to place the oem package in the build area not extract, right?

cheers

oem package... are almost all the time in a ZIP file... you have to extract them .. And you get a directory with all the needed files.

just put this directory in the directory "SYS" (yes.. in BUILD in directory .. the exact URL is : C:\Core\HyperCore\Build\SYS) beside all the directories like "Base_DPI_96, Entertainment,..."

Xtriny
2nd November 2007, 03:53 PM
Thanks a lot, Noon. I made new OEM package with the newest psShutxp version, and it works fine now

Noonski
2nd November 2007, 10:45 PM
Find yourself a HEX editor.
It needs to be done before you package the ROM into .NBH.

1. Open OS.nb in your HEX editor.
2. goto offset 0x37B55A
3. change the value to your desired pagepool size:
4M = 40
6M = 60
8M = 80
12M= C0

Hope this help our chefs

Well i searched and searched.

And first i though you where just full of shit (you know how angry you can get when you don't get it) and that you meant 37B557.
And when i found out that the offset 37B557 stands for the first block then 8,9 and then indeed A "08". I thought i was full of shit.

It's tested going to start writing tute now.

pkoper
3rd November 2007, 01:14 AM
I think I can answer you .... in fact if you look everywhere.. you will see two URL ... one "temp\dump" (that is in fact what is currently creating...) and another with where you have to look for the file.

Check the lower bar of the BuildOS when running it... you'll see "Processing: SYS\..." and that's where you should find which directory has the already used file ! The MessageBox you get saying "The file 'temp\dump\...." exists already just tells you WHICH FILE.

So you have to take the url on the BuildOS windows.. showing now "Error, last status: "Processing: OEM\...." and then look for the file pointed by the MessageBox (after 'temp\dump\).

I hope it helps you :) good night

Thank you all so much! Probably a small step for you but a giant leap for me. All went well and the best thing is it even works!

Noonski
3rd November 2007, 01:33 AM
How to change your PagePool Size
First let me say that this is one of the most dangerous things you can do. So bes ure to have a spare Stock rom for your device around. And even that might not be enough.
First download XVI32.exe from:
http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm
But you can use another Hexeditor (Winhex doesn’t do Files bigger than 200k or something efter trial period) And i like using free tools.
After downloading and opening this program go to “C:\Core\HyperCore\Build\ROM”
And drop the “OS.nb” into “XVI32”.
In XVI32 click “Adress > Goto..”. Change the settings in the next screen if they don’t match. Hexadecimel Checked, Absolute Checked.
In the search field put “$37B55A” and search
If that doesn’t work manually scroll down to 37B557.
It should look something like this:http://i230.photobucket.com/albums/ee270/Noonski76/22-Jun-2007_HxD.jpg
http://i230.photobucket.com/albums/ee270/Noonski76/22-Jun-2007_HxD.jpg

The most important part is in the values below.4MB = 00 00 40 00
6MB = 00 00 60 00
8MB = 00 00 80 00
12MB = 00 00 C0 00
Click on the block with the two numbers in my case it was “08”.
In “XVI32” click “Edit > OverWrite String”. Be sure the settings are set to “Hex String” and Unicode off (haven’t tried it with on but i fit worked why change it.)
Enter the two numerical value for the pagepool you want and press oke.
Save the file and proceed cooking as ussual.
You don’t need to change this everytime your going to cook a new ROM now.Please verify this working for you as this needs to be exact.

The most usefull source for this tutorial was the info from
http://www.modaco.com/content/Daily/256280/Pauls-guide-to-changing-the-HTC-Touch-T-Mobile-Wing-PagePool-size/
& evermick

Xtriny
3rd November 2007, 02:31 PM
working fine. Thanks Noon

mzmiric5
3rd November 2007, 03:55 PM
can some1 please tell me where can i get mui files? I'm setting up my multi lang ROM and it is working for French and English but i need MUIs for other languages.

Thanks in advance
Mišo

koala996
3rd November 2007, 05:51 PM
Thank you all so much! Probably a small step for you but a giant leap for me. All went well and the best thing is it even works!

good to hear that it works fine :) we are here to help eachother , it's my pleasure to see you happy .. you know some weeks ago I was not knowing anything about cooking ... and now I have the almost "perfect for me" rom .. :) thanks to a big guy of XDA --> NOONSKI !!

tiggerbcn
3rd November 2007, 06:36 PM
Hello, there is a thing that I have not even obtained and it is to create a file NBH, which it contains rom and extended_rom,.
I have 2 files: Rom.nb and rom_ext.nb, the first one is the rom and the second one her ext_rom, with the program htcr.exe (Dark Simpson), I indicate him in system: Rom.nb and in ExtRom: rom_ext.nb, create to me the file NBH but once in the pda the extrom does not work, is There any way of doing it?
What is what I harm?
Greetings

Noonski
3rd November 2007, 09:41 PM
Hello, there is a thing that I have not even obtained and it is to create a file NBH, which it contains rom and extended_rom,.
I have 2 files: Rom.nb and rom_ext.nb, the first one is the rom and the second one her ext_rom, with the program htcr.exe (Dark Simpson), I indicate him in system: Rom.nb and in ExtRom: rom_ext.nb, create to me the file NBH but once in the pda the extrom does not work, is There any way of doing it?
What is what I harm?
Greetings

Questions:

How big is your storage memory in total?
Do you have the Auto Run Files and the rgu files to run Autorun and the lines in intitflashes to copy the needed files to \Extended_Rom\
You can find the correct values in boot.rgu i thought.
And what do you want to do with the Ext Rom?

Let's sauy that the files in your ext rom are 5MB.
The ext rom would still take of 10MB of your storage space.

If you use Fake ext rom EOM package the files might even become smaller and still take up less space in rom as the copied versions don't get counted as doubles.

evermick
3rd November 2007, 09:51 PM
Hey Noonski,

Do you know how to upgrade OS Build by cooking? I tried to use other's OEM & SYS, but ended up bricking my Touch!

I could not find any article here for OS upgrade... Appreciate if you could share. Thanks.

pkoper
3rd November 2007, 11:41 PM
What is the imageinfo.bin file? Trying to make a package out of a cab file using sambartle's tutorial and keep getting error message that this file is missing????

tiggerbcn
3rd November 2007, 11:45 PM
Questions:

How big is your storage memory in total?
Do you have the Auto Run Files and the rgu files to run Autorun and the lines in intitflashes to copy the needed files to \Extended_Rom\
You can find the correct values in boot.rgu i thought.
And what do you want to do with the Ext Rom?

Let's sauy that the files in your ext rom are 5MB.
The ext rom would still take of 10MB of your storage space.

If you use Fake ext rom EOM package the files might even become smaller and still take up less space in rom as the copied versions don't get counted as doubles.
My rom is 60Mb storage total, but do you want to say that the bigstorage uses the space of the ext-rom???. What want do in the ext-rom it is to put programs not to have to put them in Storage Card.
Grettings

Xtriny
3rd November 2007, 11:46 PM
What is the imageinfo.bin file? Trying to make a package out of a cab file using sambartle's tutorial and keep getting error message that this file is missing????

Dont know that tutorial, but you can try Noonski's tutorial here:
http://forum.xda-developers.com/showpost.php?p=1575728&postcount=48

it works fine for me

pkoper
4th November 2007, 12:00 AM
is there an obvious mistake in the file attached?

The guide I used was posted by noonski on the first page in this thread.

thanks

Xtriny
5th November 2007, 05:33 PM
Hi guys, I have some problem with pagepool. I cooked new rom (based on 2.20.707.1B), and I changed pagepool size to 6MB. After flash it, everything goes fine, free Ram is about 24MB, but after softreset it goes back to 8 MB Pagepool and free RAM is about 21 MB.In my first ROM it worked fine. Does anybody know, what could be wrong? Thanx


EDIT - I tried to only extract ROM (2.20.707.1B), the only thing I changed was PagePool size (to 6MB) and built it back, but the same problem. It seem like there is some bug in this ROM. It is impossible to change Pagepool. After softreset, pagepool goes back and its RAM is about 20-21MB

Noonski
5th November 2007, 07:47 PM
Hi guys, I have some problem with pagepool. I cooked new rom (based on 2.20.707.1B), and I changed pagepool size to 6MB. After flash it, everything goes fine, free Ram is about 24MB, but after softreset it goes back to 8 MB Pagepool and free RAM is about 21 MB.In my first ROM it worked fine. Does anybody know, what could be wrong? Thanx


EDIT - I tried to only extract ROM (2.20.707.1B), the only thing I changed was PagePool size (to 6MB) and built it back, but the same problem. It seem like there is some bug in this ROM. It is impossible to change Pagepool. After softreset, pagepool goes back and its RAM is about 20-21MB

That sounds almost impossible. But i'll be checking this Rom out to soon.

Do you have a link to this Rom?
Sorry to be lazy but keeping up with my threads and cokking is taking a way time researching XDA.

Xtriny
5th November 2007, 07:55 PM
That sounds almost impossible. But i'll be checking this Rom out to soon.

Do you have a link to this Rom?
Sorry to be lazy but keeping up with my threads and cokking is taking a way time researching XDA.


here you are ;)

http://www.dopodasia.com/download/RUU_Elfin_DOPODASIA_WWE_2.20.707.1B_4.1.13.51_03.0 7.90_BLUE_Ship_Reduced.exe

Noonski
5th November 2007, 07:55 PM
is there an obvious mistake in the file attached?

The guide I used was posted by noonski on the first page in this thread.

thanks

Yes there is.
You can't make a folder structure in an OEM package.

remove the squares at the end and beginning of the initflashes file.

The reason you don't need a folder structure is because the Iniflashes.txt file tells Windows where the files need to go and the folders then get created at the end of flashing. The flashing sequence does nothing more then dump EVERYTHING into windows folder. Iniflashes.txt gets merged into iniflashes.dat by Buildos and After flash the installation starts reading it.
here you are ;)

http://www.dopodasia.com/download/RUU_Elfin_DOPODASIA_WWE_2.20.707.1B_4.1.13.51_03.0 7.90_BLUE_Ship_Reduced.exe

Cracias

Vale46
5th November 2007, 08:37 PM
@Noonski: Would it be possible for you to cook an original no SPL, no ExtRom version of the new 2.20 WWE Rom? I thought Bram_smulders was working on it, but there has been no update, apart from the touch_dual version for Elf. Much appreciated!

Xtriny
5th November 2007, 08:47 PM
Hi guys, I have some problem with pagepool. I cooked new rom (based on 2.20.707.1B), and I changed pagepool size to 6MB. After flash it, everything goes fine, free Ram is about 24MB, but after softreset it goes back to 8 MB Pagepool and free RAM is about 21 MB.In my first ROM it worked fine. Does anybody know, what could be wrong? Thanx


EDIT - I tried to only extract ROM (2.20.707.1B), the only thing I changed was PagePool size (to 6MB) and built it back, but the same problem. It seem like there is some bug in this ROM. It is impossible to change Pagepool. After softreset, pagepool goes back and its RAM is about 20-21MB


So I tried both "via activesync" pagepool changers, as provided by vippie and by shark, but tha same. After softreset its RAM is still about 20MB. That sucks..

Noonski
5th November 2007, 09:21 PM
@Noonski: Would it be possible for you to cook an original no SPL, no ExtRom version of the new 2.20 WWE Rom? I thought Bram_smulders was working on it, but there has been no update, apart from the touch_dual version for Elf. Much appreciated!

I will do this weekend.
First i'm going to make a normal bigstorage with added certificates and now SPL and shit. so everyone can start cooking but mostly testing it. (Unless someone beats me to the punch it's still the start of the week). First thing of course to test is Keyboard Notification bug, Pagepool switching back and multitabs Third Boot Freeze. It could be that the adress has changed but using the Pagepool tutorial we'll find out. Unless Xtriny can check the adress. If the adress has changed we need to change the Pagepool Smartchanger .bat files.

Xtriny
5th November 2007, 09:30 PM
I'm going to play with pagepool.....Original value in pagepool's address in hexeditor i 00 00 20 00 and the pagepool size is 8MB - it is a little bit strange, isnt it?

EDIT - I tried to change original value...00 00 20 00 is 8MB in original, I changed it to 00 00 10 00 and again - after flash it worked (pagepool = 4MB and 26MB free RAM!!! the same outcome when value chaned to 00 00 60 00), but after softreset it goes back to 8MB PP and 20 MB RAM. omfg

Another thing - it doesnt matter, which pagepool size I set in HexEditor. When I tried 4MB or 6MB PP size, free RAM after flash was nearly 26MB, after softreset 20-21MB in both cases

pkoper
5th November 2007, 11:36 PM
@Noonski: Would it be possible for you to cook an original no SPL, no ExtRom version of the new 2.20 WWE Rom? I thought Bram_smulders was working on it, but there has been no update, apart from the touch_dual version for Elf. Much appreciated!



I removed the ExtRom, SPL and radio.

http://rapidshare.com/files/67709002/RUU_Signed.rar

Vale46
6th November 2007, 02:42 AM
pkoper: I should replace the Ruu_signed.nbh from another updater, with the one you supplied in the rar? Is it really that simple?

longdi
6th November 2007, 02:44 AM
pkoper: I should replace the Ruu_signed.nbh from another updater, with the one you supplied in the rar? Is it really that simple?

That's what i did and it works.

Bw, i found that the network wizard is gone.....

evermick
6th November 2007, 02:48 AM
That's what i did and it works.

Bw, i found that the network wizard is gone.....

Network wizard comes with ExtROM. If you need it, you could just grab a cab to install.

pkoper
6th November 2007, 08:03 AM
pkoper: I should replace the Ruu_signed.nbh from another updater, with the one you supplied in the rar? Is it really that simple?

Yes, just replace the file.

Everything that was in the ExtRom is gone.

savale
6th November 2007, 08:42 AM
Thanks for the big storage rom! But a question: what is SPL?

mikkelnl
6th November 2007, 08:51 AM
I removed the ExtRom, SPL and radio.

http://rapidshare.com/files/67709002/RUU_Signed.rar

You might want to post this in a separate thread, people will like this but might miss your post here :)

pkoper
6th November 2007, 04:28 PM
Thanks for the big storage rom! But a question: what is SPL?

SPL : Secondary Program Loader
it is the bootloader

But someone else might want to answer that one, goes as bit beyond my knowledge.

Flashing the SPL from the original Dopod ROM woulld CID lock your device. You would only be able to flash Dopod ROM's in future or you would need to unlock your touch again with eg. USPL.

evermick
7th November 2007, 06:46 AM
I'm going to play with pagepool.....Original value in pagepool's address in hexeditor i 00 00 20 00 and the pagepool size is 8MB - it is a little bit strange, isnt it?

EDIT - I tried to change original value...00 00 20 00 is 8MB in original, I changed it to 00 00 10 00 and again - after flash it worked (pagepool = 4MB and 26MB free RAM!!! the same outcome when value chaned to 00 00 60 00), but after softreset it goes back to 8MB PP and 20 MB RAM. omfg

Another thing - it doesnt matter, which pagepool size I set in HexEditor. When I tried 4MB or 6MB PP size, free RAM after flash was nearly 26MB, after softreset 20-21MB in both cases

I bump into the same problem. I use UltraEdit.

Default value is 20. I tried 80 and it works ok for a while. After reset, it changed back to 20..

Anyone could figure a way to fix it?

asiliem
7th November 2007, 09:35 AM
The things you did is very good

I was trying to cook my ROM, but I found there are many much more professionals than me, so I started to think about changing the setting of some tools inside the ROM like the dialpad to redesign it to include the smart-dialing and 3G video call button like this Picture:

http://www.pdaclub.pl/images/screenshot/HTC_Touch_Dual_SS_Phone.JPG

so from where I can get the smart-dialing sources? and does anyone has any tools or ideas to help?

Xtriny
7th November 2007, 12:41 PM
I bump into the same problem. I use UltraEdit.

Default value is 20. I tried 80 and it works ok for a while. After reset, it changed back to 20..

Anyone could figure a way to fix it?


No success for me. I try to recook this ROM again..

mzmiric5
7th November 2007, 10:18 PM
is it possible to map psShutXP to power button?

evermick
8th November 2007, 04:08 AM
No success for me. I try to recook this ROM again..

hmmm, verified.. no matter what value I have put in.. the free memory is still the same. Looks like they have changed the location for PP...

evermick
8th November 2007, 04:14 AM
added:

I had made a Vanilla ROM which is ready for cooking, no extract is needed. See link below
http://forum.xda-developers.com/showthread.php?p=1647904

But it looks like ppl have no idea what to do with it.. so, nevermind.

I link my thread here so that I could find my thread easier when it drops behind page one :)

iii_see_tagpi_run_iii
8th November 2007, 03:41 PM
i just wanted to ask, is it really normal that any .nbh file that is cooked with a file size of lower than 50mb would result in an error in flashing?

Vale46
8th November 2007, 03:58 PM
i just wanted to ask, is it really normal that any .nbh file that is cooked with a file size of lower than 50mb would result in an error in flashing?

Filesize makes no difference between a good flash, and a bad one. The skills of the cook that made the particular ROM (and I'm not dissing the cooks now), and the skills of the flasher are the main source of errors

iii_see_tagpi_run_iii
9th November 2007, 07:18 AM
Filesize makes no difference between a good flash, and a bad one. The skills of the cook that made the particular ROM (and I'm not dissing the cooks now), and the skills of the flasher are the main source of errors

then im really doing something wrong... may i ask when would be the best time to remove programs from the rom when cooking and are there any precautions i should look out for like dll files maybe? i always get an invlid file seize error when flashing:(

Vale46
9th November 2007, 03:34 PM
then im really doing something wrong... may i ask when would be the best time to remove programs from the rom when cooking and are there any precautions i should look out for like dll files maybe? i always get an invlid file seize error when flashing:(

I would guess the best time to remove programs would be when all the packages are split up in OEM and SYS folders, after building with pkgtool. When removing .dll's you should always be carefull, especially when removing from the SYS dir. I haven't gone as far, but I do know that removing them is sometimes not enough. Certain initflash files should also be edited to update the new filestructure or filesize of replaced files, before proceeding to cook. An experienced cook should correct me on this if I'm wrong.

Xtriny
9th November 2007, 03:45 PM
This is may way of removing -adding apps.

1.extract the ROM
2.Select what you want to add or remove
3. In total commander open OEM Package in first window and extracted rom in seond window
4.find every file, which is in oem package, in extracted ROM and delete it - when not every file in OEM package is in ROM too
5. if in OEM Package is .rgu file, you have to update .rgu file in the ROM too - it is usualy placed in folder, where you've remove files. The sam with initflashfiles (Be very carefuly)
6.place new OEM package to OEM folder and run BuildOS, if there are any duplicates (errors). If yes, delete them in ROM (not in OEM), if not, you can go to the next Package.

When I want only to remove anything, I use OEM package of it anyway, for control

mzmiric5
9th November 2007, 04:14 PM
OK, ppl i found a software that enables you to remap all buttons(hardware and software buttons) on the phone. Could someone figure out how to use this to preconfigure the buttons in rom? I tried to make OEM but can't find what goes where in registry and it seams that the program needs to be loaded all the time.

iii_see_tagpi_run_iii
9th November 2007, 04:27 PM
This is may way of removing -adding apps.

1.extract the ROM
2.Select what you want to add or remove
3. In total commander open OEM Package in first window and extracted rom in seond window
4.find every file, which is in oem package, in extracted ROM and delete it - when not every file in OEM package is in ROM too
5. if in OEM Package is .rgu file, you have to update .rgu file in the ROM too - it is usualy placed in folder, where you've remove files. The sam with initflashfiles (Be very carefuly)
6.place new OEM package to OEM folder and run BuildOS, if there are any duplicates (errors). If yes, delete them in ROM (not in OEM), if not, you can go to the next Package.

When I want only to remove anything, I use OEM package of it anyway, for control

i guess ill try to do that... another noobie problem is, how do i enable the overwriting of files from the windows folder in an already working rom from a phone? the latest rom released would not enable this function.. thanks for the help.:D

Noonski
9th November 2007, 05:00 PM
i guess ill try to do that... another noobie problem is, how do i enable the overwriting of files from the windows folder in an already working rom from a phone? the latest rom released would not enable this function.. thanks for the help.:D

Clarify do you want to overwrite after flashing or before cooking?

Noonski
9th November 2007, 05:03 PM
i just wanted to ask, is it really normal that any .nbh file that is cooked with a file size of lower than 50mb would result in an error in flashing?

Yes that is normal.

50MB is the absolute minimum.

The bootloader has a specic amount of memory assigned for this.
So nothing you do in NBH file will change this.

iii_see_tagpi_run_iii
9th November 2007, 05:09 PM
Clarify do you want to overwrite after flashing or before cooking?

after flashing. im really sorry for all these questions.. atleast i now know several things important in cooking roms:)

iii_see_tagpi_run_iii
9th November 2007, 05:12 PM
Yes that is normal.

50MB is the absolute minimum.

The bootloader has a specic amount of memory assigned for this.
So nothing you do in NBH file will change this.

thanks so much.. i really thought this had something to do with the filesize.. would it be possible remove apps within the rom and thus have a filesize of less than 50mb but inorder to fill up the space would it be possible to just include a file so as it would make it still 50 or more? say id make a tone with a file size equivalent to the size needed to make 50 mb?

iii_see_tagpi_run_iii
9th November 2007, 06:52 PM
thanks so much.. i really thought this had something to do with the filesize.. would it be possible remove apps within the rom and thus have a filesize of less than 50mb but inorder to fill up the space would it be possible to just include a file so as it would make it still 50 or more? say id make a tone with a file size equivalent to the size needed to make 50 mb?

ignore the query... it works i just added additional tones to complete 50 mb minimum... now i have the rom i really wanted.. thanks to this thread ive learned a lot.. now running on my own rom! i just wish i knew what to set before flashing inorder to enable overwriting after the flash..:D

Noonski
10th November 2007, 12:18 AM
after flashing. im really sorry for all these questions.. atleast i now know several things important in cooking roms:)

You can't overwrite these files then.

The files aren't actually in the Windows folder.
These are fake sort of.
The files are in the ROM part which you actually don't see or ever delete.
The files in windows are sort of links.
That's why when you would use initflashes.txt to copy a file to a different directory tey still are in Windows folder. But the file in the folder where you copied it over to can be deleted.

You can overwrite a file in windows folder but it will take up more space since you are actually adding it to the Ram part of the memory. The original file will still be in Rom only the reference will change. That's why modifying files allready present in the ROM/windows folder will slow down the device.
Yes they are the same size and amount but Opening Windows also means that all the changed references have to be read. And you get a very long opening time of the windows folder.

I hope all of this wasn't to confusing.

But i think a lot of people think that the files Cooked into windows are actual files.

But again i might be explaining it wrong.

vippie
10th November 2007, 07:58 PM
First of all I want to thank Noonski for this thread. Trying to cook a little for fun and it's going really well because of the info in here.

Got some questions:
- I'm a bit confused about the XIP section of the rom. I understand it's like the language independent core of the ROM. Is the OS version inside the XIP? Is it possible to take the XIP from another elf rom to update the OS version?
- Did someone find a tutorial on how to change version numbers like the ROM version?

Noonski
10th November 2007, 08:08 PM
First of all I want to thank Noonski for this thread. Trying to cook a little for fun and it's going really well because of the info in here.

Got some questions:
- I'm a bit confused about the XIP section of the rom. I understand it's like the language independent core of the ROM. Is the OS version inside the XIP? Is it possible to take the XIP from another elf rom to update the OS version?
- Did someone find a tutorial on how to change version numbers like the ROM version?

Yeah i know it's poddible to use a different XIP.
Some do this when using a Artemis Rom to port it to Elf.
Haven't done this but i'm pretty sure there's a tutorial some where (ELF WIKI Extract ROM is only a part of it)

I haven't got the registry keys here. But you can start in the OEMVersion folder. Open the XML file.

Here's a Vanilla Based on 2.2 os 5.2.1933 (http://rapidshare.com/files/68804210/RUU_signed.zip)
You can extract the Rom and recook it.
4MB PP
It's 50.1 MB 62.63 Storage It's Nice and Neat.Everything not in it can be found in repository.
(The only thing i forgot is to remove the ZIP link)

vippie
10th November 2007, 08:44 PM
Here's a Vanilla Based on 2.2 os 5.2.1933 (http://rapidshare.com/files/68804210/RUU_signed.zip)


Thanks.... will use that one as a basis!

iii_see_tagpi_run_iii
11th November 2007, 12:53 PM
how do i install those oem applications youve posted about some htc duo applications? at which part of cooking must they be added? are there things i need to know first and not just be adding those files on the sys/oem folder prior to cooking? ive seen htc album working from the cube and id like to make one also myself, i plan to use the older versions of rom as base and not the newly released rom (2.20.707).. and again, thank you for all those things you have shared with us.:o

pkoper
12th November 2007, 01:51 AM
First of all I want to thank Noonski for this thread. Trying to cook a little for fun and it's going really well because of the info in here.

Got some questions:
- I'm a bit confused about the XIP section of the rom. I understand it's like the language independent core of the ROM. Is the OS version inside the XIP? Is it possible to take the XIP from another elf rom to update the OS version?
- Did someone find a tutorial on how to change version numbers like the ROM version?

The ROM version number ( that what is displayed ) can be changed in the default.hv file ( convert to .rgu and back when finished).

Xtriny
12th November 2007, 01:53 AM
The ROM version number ( that what is displayed ) can be changed in the default.hv file ( convert to .rgu and back when finished).
You mean OS version? Rom Version can be changed in OEMVersion folder. Simply open .xml file in Notepad and you can change it, but changing OS version only with ovewrite values in .hv file isnt fair for other users.

tschan
12th November 2007, 03:32 AM
The guide is only cover extract and customize ROM. What about next step, build ROM after customized? Can anyone provide us the guide?

crazy_m
13th November 2007, 12:09 AM
I bump into the same problem. I use UltraEdit.

Default value is 20. I tried 80 and it works ok for a while. After reset, it changed back to 20..

Anyone could figure a way to fix it?

Open OS.nb file with Hex editor (I use HxD), goto 37b55A (default offset), and :
for 4MB put 10
for 6MB put 18
for 8MB put 20

Trick is, 10(hex) is 16(dec) so 16/4=4, 18(hex) is 24(dec) so 24/4=6, 20(hex) is 32(dec) so 32/4=8 ...

So these hex numbers,converted to decimal, divided with 4 gives you a size of page pool in MB. :-D

I have tried this with my own cooked ROM (thanks to Noonski and people in this thread) and it's working perfectly ...

Best

Xtriny
13th November 2007, 01:16 AM
Open OS.nb file with Hex editor (I use HxD), goto 37b55A (default offset), and :
for 4MB put 10
for 6MB put 18
for 8MB put 20

Trick is, 10(hex) is 16(dec) so 16/4=4, 18(hex) is 24(dec) so 24/4=6, 20(hex) is 32(dec) so 32/4=8 ...

So these hex numbers,converted to decimal, divided with 4 gives you a size of page pool in MB. :-D

I have tried this with my own cooked ROM (thanks to Noonski and people in this thread) and it's working perfectly ...

Best

I tried it in "old" 2.20 ROM, and it didnt work. After flash I got about 26MB RAM, but after first softreset it goes back - free RAM is only 20-21MB. Try it ;)

Btw, we have new 2.20 ROM version, with known pagepool values, so it doesnt matter yet

Aspirina750
13th November 2007, 01:51 AM
Noob question :)

First, I just extracted and built a new rom, everything went well, so thanks for all this guides and tips :)!!!

Now, I have a doubt, I tried to cook a new rom adding a package, the shutXP one. When I built the OS it gave an error, that
PowerOfWarning.exe was already there, so I went to OEM/OEMAPPS and deleted the PowerOffWarning.exe over there, is that correct? Should I do anything else?

Thanks!!!

Xtriny
13th November 2007, 02:00 AM
Noob question :)

First, I just extracted and built a new rom, everything went well, so thanks for all this guides and tips :)!!!

Now, I have a doubt, I tried to cook a new rom adding a package, the shutXP one. When I built the OS it gave an error, that
PowerOfWarning.exe was already there, so I went to OEM/OEMAPPS and deleted the PowerOffWarning.exe over there, is that correct? Should I do anything else?

Thanks!!!

No, you're right. You have to run buildOS and wait, if it will show error. If not, it is ok. If so, you have to delete file in OEMAPPS (or anywhere), but not in your new OEM Package. You probably use Noonski's shutXP, which replace original PowerOff.

In the attachments you can get shutXP, which doesnt replace original PowerOff

Aspirina750
13th November 2007, 02:08 AM
No, you're right. You have to run buildOS and wait, if it will show error. If not, it is ok. If so, you have to delete file in OEMAPPS (or anywhere), but not in your new OEM Package. You probably use Noonski's shutXP, which replace original PowerOff.

Yup, got the error, so I deleted the poweroffwarning from the OEMAPPS and built the os.

Got something strange, this new ROM with the shutXP is the same size as the one with the original poweroffwarning. Weird:confused: :confused:

I'm gonna dump the new rom and check the size of the poweroffwarning.

Thanks!!!

BTW, I based this rom on the Spanish 2.20 ESN and changed the pagepool from 20 to 10, is that correct or it's something else?

Thanks!!!

Xtriny
13th November 2007, 02:13 AM
Yup, got the error, so I deleted the poweroffwarning from the OEMAPPS and built the os.

Got something strange, this new ROM with the shutXP is the same size as the one with the original poweroffwarning. Weird:confused: :confused:

I'm gonna dump the new rom and check the size of the poweroffwarning.

Thanks!!!

BTW, I based this rom on the Spanish 2.20 ESN and changed the pagepool from 20 to 10, is that correct or it's something else?

Thanks!!!

Forgot anything about size with or without. You can add 5 new OEM packages and the size will be the same, or you can add only 1 and it can be bigger or smaller - forgot it - flash it ;)

And that value about pagepool will not work - you can flash it, but you will get free RAM like without any changes. Like Noonski said - there are some errors in this ROM - the pagepool size cannot be changed in this version

Aspirina750
13th November 2007, 02:34 AM
Doing a backup of my system and I'll flash, crossing my fingers ;)

Xtriny
13th November 2007, 02:39 AM
crossing my fingers ;)

me to..... ;)

Aspirina750
13th November 2007, 03:01 AM
me to..... ;)

Flashed and working so far ;)

Thanks!!!

Now I only need to learn how to clean up a ROM!!!

Any guides around ;)

Thanks!

Xtriny
13th November 2007, 03:08 AM
Flashed and working so far ;)

Thanks!!!

Now I only need to learn how to clean up a ROM!!!

Any guides around ;)

Thanks!
Congratulations, man
I think you can find some guide, but the best thing is to try. If you will delete anything from ROM, in the same folder will be .rgu file. Open it in Notepad, find that app you've just deleted and delete it from rgu file too - but be very, very carefull here.
You will have to try it. You will get a lot of errors, but at the end you will get your own ROM and that's it.

Aspirina750
13th November 2007, 03:16 AM
Congratulations, man
I think you can find some guide, but the best thing is to try. If you will delete anything from ROM, in the same folder will be .rgu file. Open it in Notepad, find that app you've just deleted and delete it from rgu file too - but be very, very carefull here.
You will have to try it. You will get a lot of errors, but at the end you will get your own ROM and that's it.

Thanks!

Will try and report back ;)

Report back all my errors ;) lol :D

Edit:
BTW in the optimise option in the kitchen what folders should I put in the original folder?
Thanks!

crazy_m
13th November 2007, 10:17 AM
I tried it in "old" 2.20 ROM, and it didnt work. After flash I got about 26MB RAM, but after first softreset it goes back - free RAM is only 20-21MB. Try it ;)

Btw, we have new 2.20 ROM version, with known pagepool values, so it doesnt matter yet

I used RUU_Elfin_DOPODASIA_WWE_2.20.707.1B_4.1.13.51_03.0 7.90_BLUE_Ship_Reduced.exe to cook and it's working, even when I read this value directly from flash, it doesn't change the size.

pkoper
13th November 2007, 01:12 PM
Trying to cook my own rom at the moment and ran into the "java not working" issue.

I tried the 2.20 "vanilla" ROM posted by Noonski as well as Xtriny's V3.

Is this some issue with this particular build? Everything else works, just not the java bit.


Thanks

Xtriny
13th November 2007, 01:22 PM
Trying to cook my own rom at the moment and ran into the "java not working" issue.

I tried the 2.20 "vanilla" ROM posted by Noonski as well as Xtriny's V3.

Is this some issue with this particular build? Everything else works, just not the java bit.


Thanks
Hi,

I got the same problem.You have to replace it with another MidletManager - maybe Noon have deleted anything of it. I've replaced it, copy backn some important files from original ROM and it works now

pkoper
13th November 2007, 01:26 PM
Which are the important files?

Xtriny
13th November 2007, 01:38 PM
Put back all folders from OEMAPPS from original ROM. Dont know, which is important for midlet manager, but it works for me. You have to take a look in rgu file in OEMAPPS and serch for midlet and java. Compare it with rgu from original. I cant remember it.

pkoper
13th November 2007, 01:58 PM
Will try this evening. Thanks!

Aspirina750
13th November 2007, 07:56 PM
Back with more questions ;)

I tried to create a package with the Touch calculator skin by nanoflower.

My problem was that there where no registry entries to put into the rgu, so I created a blank one and added a blank line. Is that correct?
Then I used the BuildDSM and got the dsm file.
I'm uploading the package I created, could you guys check it?

Thanks!

Edit: New package added in another post

Xtriny
13th November 2007, 08:45 PM
Back with more questions ;)

I tried to create a package with the Touch calculator skin by nanoflower.

My problem was that there where no registry entries to put into the rgu, so I created a blank one and added a blank line. Is that correct?
Then I used the BuildDSM and got the dsm file.
I'm uploading the package I created, could you guys check it?

Thanks!

It is wrong. you have to install your app to the device like cab, and export registry entries. This entries you have to put to rgu file.

Aspirina750
13th November 2007, 08:49 PM
It is wrong. you have to install your app to the device like cab, and export registry entries. This entries you have to put to rgu file.

Ok, but the entries should show on the XML file inside the cab no? And how do I check what entries changed? Any recommendations?

Thanks!

Xtriny
13th November 2007, 08:53 PM
Ok, but the entries should show on the XML file inside the cab no? And how do I check what entries changed? Any recommendations?

Thanks!

Yes, registry entries is provided in xml file. You can "translate" them to rgu file, or export entries with CeRegEditor directly from device and copy them to rgu file. You have to try this and learn how to do this.

Aspirina750
13th November 2007, 08:55 PM
Yes, registry entries is provided in xml file. You can "translate" them to rgu file, or export entries with CeRegEditor directly from device and copy them to rgu file. You have to try this and learn how to do this.

The problem with this cab is that there were noreg entries in the xml ;)

What should I do?

Xtriny
13th November 2007, 09:00 PM
The problem with this cab is that there were noreg entries in the xml ;)

What should I do?
If there are no registry entries, try to cook it without any rgu file, and if it will not eork, do what I said - install cab and export entries from the device. That's it.

Cheers

Aspirina750
13th November 2007, 09:14 PM
If there are no registry entries, try to cook it without any rgu file, and if it will not eork, do what I said - install cab and export entries from the device. That's it.

Cheers

Done!

It only found this:

[HKEY_CURRENT_USER\Software\SpbCalcTemp]
"FileType"="gif"

So I added it to the rgu, added the regedit 4, and built it with the BuildDSM.

lol, Thanks again!

Noonski
13th November 2007, 09:50 PM
Done!

It only found this:

[HKEY_CURRENT_USER\Software\SpbCalcTemp]
"FileType"="gif"

So I added it to the rgu, added the regedit 4, and built it with the BuildDSM.

lol, Thanks again!

Almost perfect.
But add this key to to be on the safe side
[HKEY_CURRENT_USER\Software\Spb Software House\Spb Calculator]
"FileType"="gif"

And the RGU was Saved as ANSI. ussually that results in hive creation errors with me. So save as Unicode.

And the Graphics aren't actually real Gif Files.
They are PNG files with Gif extension.

When you build the DSM file always remove Initflashes.txt and Option.xml first.

As these won't go into the Rom.

Good Job Grasshopper.
You now know the Way Of the Crouching DSM ;)

Xtriny
13th November 2007, 10:09 PM
Noon, he's right with file type. I have two Spb calc OEM packages with png or gif.

Noonski
13th November 2007, 10:18 PM
Noon, he's right with file type. I have two Spb calc OEM packages with png or gif.

I know but the Gif has a PNG file heaader (not that i checked)

But the simplest test is opening Gif file in FireWorks.

It will give an error about the filetype being incorrect.
Not a biggy.
It's a very silly workaround. Somtimes no matter what you do when you save a gif file the quality gets awfull anyway. So you save the high quality PNG file with a gif extension. It works on a lot of ocasions.

Noonski
13th November 2007, 10:20 PM
Yup, got the error, so I deleted the poweroffwarning from the OEMAPPS and built the os.

Got something strange, this new ROM with the shutXP is the same size as the one with the original poweroffwarning. Weird:confused: :confused:

I'm gonna dump the new rom and check the size of the poweroffwarning.

Thanks!!!

BTW, I based this rom on the Spanish 2.20 ESN and changed the pagepool from 20 to 10, is that correct or it's something else?

Thanks!!!

Some files get compressed some allready are.

The file size in Windows Folder might be the same as OG. But the file in actuall ROM is compressed.

Aspirina750
13th November 2007, 11:52 PM
Almost perfect.
But add this key to to be on the safe side
[HKEY_CURRENT_USER\Software\Spb Software House\Spb Calculator]
"FileType"="gif"

And the RGU was Saved as ANSI. ussually that results in hive creation errors with me. So save as Unicode.

And the Graphics aren't actually real Gif Files.
They are PNG files with Gif extension.

When you build the DSM file always remove Initflashes.txt and Option.xml first.

As these won't go into the Rom.

Good Job Grasshopper.
You now know the Way Of the Crouching DSM ;)

Thanks! Well, this supposely was an easy one:p , I'll start working on other useful apps I use:rolleyes:

Now, one thing I was thinking, would it be possible to create a master list of things that can be removed safely from the ROM?

Thanks again!

Edit:

Noob ataaaaaack ;)

1 more question, if I remove something from the OEM/OEMAPPS folder for example the 1-nature_15fps.mp4 I check the RGU to see if there's any associated registry entry or something else no? If there was I should grab the folder and rebuild the DSM. Is that correct? If there is a registry entry deleting the entry and the file should do the work no?

Thanks!

pkoper
14th November 2007, 01:11 AM
You mean OS version? Rom Version can be changed in OEMVersion folder. Simply open .xml file in Notepad and you can change it, but changing OS version only with ovewrite values in .hv file isnt fair for other users.

it could be not fair, because you could change it to whatever you want. But most people would probably just like to see their handles somewhere. Don't think many would fake a version.

iii_see_tagpi_run_iii
15th November 2007, 12:46 PM
i kinda cooked a rom and everything goes sweet from the cooking till flashing until its already working when installed on my touch but im having difficulty figuring or looking for anything which may point out as to how i can enable actions where i want to delete some apps on the /widows/startup folder but an error always pops up. ive seen it enabled with no problems on those other cooked roms... any help pls?:( :confused: :

Noonski
15th November 2007, 01:58 PM
Thanks! Well, this supposely was an easy one:p , I'll start working on other useful apps I use:rolleyes:

Now, one thing I was thinking, would it be possible to create a master list of things that can be removed safely from the ROM?

Thanks again!

Edit:

Noob ataaaaaack ;)

1 more question, if I remove something from the OEM/OEMAPPS folder for example the 1-nature_15fps.mp4 I check the RGU to see if there's any associated registry entry or something else no? If there was I should grab the folder and rebuild the DSM. Is that correct? If there is a registry entry deleting the entry and the file should do the work no?

Thanks!

The problem when you want to recreate OEM DSM is that the module folders (folders called like the files inside them) Won't be included into the buildDSM. Resulting still in a mess.
Don't worry to much about missing files from OEM folders.

Noonski
15th November 2007, 02:12 PM
i kinda cooked a rom and everything goes sweet from the cooking till flashing until its already working when installed on my touch but im having difficulty figuring or looking for anything which may point out as to how i can enable actions where i want to delete some apps on the /widows/startup folder but an error always pops up. ive seen it enabled with no problems on those other cooked roms... any help pls?:( :confused: :


Very Unclear Whta you mean.

iii_see_tagpi_run_iii
15th November 2007, 02:25 PM
Very Unclear Whta you mean.

ooops sorry i just wanted to ask if there is something i need to edit within the rom or sys folder before cooking so that when its already finished and flashed, it would be possible to delete some application shortcut located at the startup folder.

vippie
15th November 2007, 03:13 PM
ooops sorry i just wanted to ask if there is something i need to edit within the rom or sys folder before cooking so that when its already finished and flashed, it would be possible to delete some application shortcut located at the startup folder.

You can prevent the rom from copying links to the startup folder in initflashfiles.dat.

iii_see_tagpi_run_iii
15th November 2007, 03:32 PM
You can prevent the rom from copying links to the startup folder in initflashfiles.dat.

ummm may i ask what folder is this file located? thanks

zeflash
15th November 2007, 03:34 PM
Not sure if this has been reported before or not, but it got me confused the first fiew times I cooked my roms (just starting) with the hypercore kitchen:

In the folder Hypercore/tools/RUU, after the first rom has been flash I believe the kitchen renamed the previous ROM to old_ruu_signed.nb, and puts the new one as ruu_signed.nb.

Well, on my OS, Elf_RUU.exe picks up the old one all the time!
I was wondering what was going on for a while, my changes not being there until I flashed it again ...
IF that can save some trouble ...

Noonski
15th November 2007, 03:44 PM
the easy way would be to just delete the files from the rom indeed.

But the correct way would be to edit initflashe.dat in OEM_LANG to.
You need to remove the lines containing your removed files.

But after editing be sure to open the .dat file in winhex and remove the first to Bytes (4 chars) and resave.

Some good Text Editors don't have this issue. but normal notepad does.

mkhattab
15th November 2007, 07:56 PM
I think I may have a similar issue... Once I've created a ROM, how do I "clean" my Hypercore-based kitchen so I can create other ROMs? I've had the problem that a new ROM will still be flashed to my device as the previous one I was working on... Any help will be very much appreciated.

The way I'm doing it now is that I delete and entirely re-create the C:\Core directory structure when I start cooking a new ROM

I'm very close to publishing my first ROM to XDA. This forum is absolutely wonderful and the support is admirable. I am trying to master my ROM so that when I do upload it, the quality really is up to par with the rest of the stuff being produced by the XDA community...

Aspirina750
15th November 2007, 09:35 PM
Hi guys! I'm back with more OEM Packages problems ;)

I built an OEM package from a HTC Task Manager cab, but when I try to build the OS BuildOS guives me an HV error????

Any ideas?

BTW, Could it be possible to have the original cab from the posted packages, so we can compare and learn a bit from there?

Thanks!!!

Xtriny
15th November 2007, 09:42 PM
Hi guys! I'm back with more OEM Packages problems ;)

I built an OEM package from a HTC Task Manager cab, but when I try to build the OS BuildOS guives me an HV error????

Any ideas?

BTW, Could it be possible to have the original cab from the posted packages, so we can compare and learn a bit from there?

Thanks!!!
If it gives hv error, you have something wrong in rgu file. Why dont you use existing OEM packages, and waste your time with making anything, what allready exist? You can fin all-in-one package here on xda

for example here: http://rapidshare.com/files/65449450/OEM_Pack_v1.2.zip.html

Aspirina750
15th November 2007, 10:01 PM
If it gives hv error, you have something wrong in rgu file. Why dont you use existing OEM packages, and waste your time with making anything, what allready exist? You can fin all-in-one package here on xda

for example here: http://rapidshare.com/files/65449450/OEM_Pack_v1.2.zip.html

Hehehhe, I'm just looking for some practice, I actually downloaded the OEM pack from the Dev forum, I don't know if it's the same one from your link, but I'll DL that too. Anyway, I'm just trying to learn it the hard way ;)

Cheers!

crazy_m
16th November 2007, 12:19 AM
Can someone tell me how to integrate HTC Home Plug found here: ftp://ftp.xda-developers.com/Uploads/Elf/Cooking%20Class/OEM%20Packages into ROM?
When I put it in the ROM, and flash ROM, HTC Home wont show up, just blank space on it's place at home screen.

And if someone have working HTC Home Plug OEM (backlight fix, standard icons, 6 tab, tab settings ...) please, share it. I've tried every package found here on forum and none of them are not working (backlight error, missing weather icons, no tab settings ...).

Thanks.

Noonski
16th November 2007, 12:46 AM
Did you also add package for Clock Graphics?

Look for Reg setting in rgu file

"tabsettings"="1,3,4"
And change to
"tabsettings"="1,2,3,4,5,6"

Backlight is working as it uses original dll for that function.

Noonski
16th November 2007, 01:09 AM
Hi guys! I'm back with more OEM Packages problems ;)

I built an OEM package from a HTC Task Manager cab, but when I try to build the OS BuildOS guives me an HV error????

Any ideas?

BTW, Could it be possible to have the original cab from the posted packages, so we can compare and learn a bit from there?

Thanks!!!

RGU wasn't saved as Unicode in 2.0 version

crazy_m
16th November 2007, 03:34 AM
Did you also add package for Clock Graphics?

Oh my God, I can't believe I missed that. Thank you Noonski.

mkhattab
16th November 2007, 03:57 AM
I think I may have a similar issue... Once I've created a ROM, how do I "clean" my Hypercore-based kitchen so I can create other ROMs? I've had the problem that a new ROM will still be flashed to my device as the previous one I was working on... Any help will be very much appreciated.

The way I'm doing it now is that I delete and entirely re-create the C:\Core directory structure when I start cooking a new ROM

I'm very close to publishing my first ROM to XDA. This forum is absolutely wonderful and the support is admirable. I am trying to master my ROM so that when I do upload it, the quality really is up to par with the rest of the stuff being produced by the XDA community...

Any help? Anyone?

evermick
16th November 2007, 06:37 AM
I tried it in "old" 2.20 ROM, and it didnt work. After flash I got about 26MB RAM, but after first softreset it goes back - free RAM is only 20-21MB. Try it ;)

Btw, we have new 2.20 ROM version, with known pagepool values, so it doesnt matter yet

Hey Xtriny, which one is new 2.20ROM? Noon's one?
http://rapidshare.com/files/68804210/RUU_signed.zip <==?

vippie
16th November 2007, 09:23 AM
The way I'm doing it now is that I delete and entirely re-create the C:\Core directory structure when I start cooking a new ROM

I'm doing the same thing. It's faster than deleting files.

totalcmdext
16th November 2007, 01:21 PM
Hi,

I have the following problem.
When i try to put a new OEM packages or change an existing the BuldOS.exe finished without any problem and always crash the BuildIMG.exe.

Because i use CreateOS.bat the new OS.nb file always create even if the crash the BuildIMG.exe

Please help me because i cannot make any ROM!!!!

baituo
16th November 2007, 01:34 PM
Hi guys! I'm back with more OEM Packages problems ;)

I built an OEM package from a HTC Task Manager cab, but when I try to build the OS BuildOS guives me an HV error????

Any ideas?

Thanks!!!

You can check the log file inside temp folder.
I encountered this error due to rgu errors.

pkoper
18th November 2007, 07:38 PM
PKG tool is reporting several rgu files missing. The rom does not recompile correctly, ie hangs on first bootscreen.
Because this is a working rom the registry changes would have had to be
done elsewhere, I figured.
Other roms I looked at do not have the rgu file in question, but PKG tool runs fine and the rom works.

Is there something simple I am missing?

Noonski
18th November 2007, 09:23 PM
Any help? Anyone?

I always use numbering codes in all my modified OEM packages.
And try to break apart all graphical elements into seprate OEM packs.

So when i start a new ROM i start clean and copy all my modified Old OEM packs into new kitchen.

Then i start removing doubles.

Noonski
18th November 2007, 09:25 PM
Hi,

I have the following problem.
When i try to put a new OEM packages or change an existing the BuldOS.exe finished without any problem and always crash the BuildIMG.exe.

Because i use CreateOS.bat the new OS.nb file always create even if the crash the BuildIMG.exe

Please help me because i cannot make any ROM!!!!

Do you have a package to check and are you on vista?

Noonski
18th November 2007, 09:26 PM
PKG tool is reporting several rgu files missing. The rom does not recompile correctly, ie hangs on first bootscreen.
Because this is a working rom the registry changes would have had to be
done elsewhere, I figured.
Other roms I looked at do not have the rgu file in question, but PKG tool runs fine and the rom works.

Is there something simple I am missing?

Which Rom are you using as a Base?

And which RGU is missing so whe can check what it's for.

Is the RGU in the missing folder?

And when you just flash the Rom is the RGU in the windows folder?