yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] lliw:
registry change into dump rom

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.
[Touch GSM ROM Development] mzmiric5:
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
[Touch GSM ROM Development] lliw:
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
[Touch GSM ROM Development] evlimeca:
Cube Issues

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.
[Touch GSM ROM Development] Noonski:
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.
[Touch GSM ROM Development] Noonski:
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.
[Touch GSM ROM Development] bram_smulders:
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
[Touch GSM ROM Development] Noonski:
You have to use double dashes

"background" = "\\Windows\\BackGround.png"
[Touch GSM ROM Development] Noonski:
Extracting A Rom.

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.
[Touch GSM ROM Development] Xtriny:
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
[Touch GSM ROM Development] Noonski:
Well first of course the above.

Extracting A Rom.

Then taken from Anichillus tutorial:

[FONT=&quot]1.[FONT=&quot] [/FONT][/FONT][FONT=&quot]BUILD-ing :[/FONT][FONT=&quot][/FONT]

[FONT=&quot] [/FONT]

·[FONT=&quot] [/FONT]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.

·[FONT=&quot] [/FONT]

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

·[FONT=&quot] [/FONT](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.
[Touch GSM ROM Development] Xtriny:
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.
[Touch GSM ROM Development] Noonski:
Why don't you try with the Base ROM suplied in the first threads?
[Touch GSM ROM Development] Xtriny:
Downloading right now. I used probably "bad" ROM to cooking ;-)
[Touch GSM ROM Development] crazy_m:
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.
[Touch GSM ROM Development] Xtriny:
OMFG, it isnt possible, I'm going mad

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...
[Touch GSM ROM Development] Noonski:
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.
[Touch GSM ROM Development] Ameet:
I suggest check the provxmls if any that may be enabling the plugin or you may have a case of reg entry duplication somewhere in the rgus ;)
[Touch GSM ROM Development] trueg:
Ya, I was just about to post that it doesn't have it's own key, it has it's own value under Today. :)
[Touch GSM ROM Development] swordfish2009:
Hello,

I m bit confused.. what SPL should i flash? currently i hace 2.20 spl and i want to cook and update to 3.07 then what should i flash? 2.20 or 3.07?

I have one more question, i had recently updated shiped rom using gold card method. It had spl part i think and shouldnt it update my SPL?
[Touch GSM ROM Development] ayyu3m:
i m refering to SPL that have been patched bro. and by patched i mean CID unlocked. and i know bro that you wud know when a device is CID unlocked...you can flash any rom any number of times.

and so i come back to where i started...and that is pre-patched SPL which is shortly or sweetly known as USPL. there is a main thread abt USPL, so i assume u know already abt that bro...hehe...so no need to link rite??

so the advantages are...you dont have to wait for a succesful white screen to appear and see it fail also as white screen doesnt appear

so as mentioned pre-patched SPL or USPL has the CID unlocked for you permanently. so flash away ur test roms. and if u wana flash back the original rom, jus extract the OS.nb from it and prepare an RUU_signed.nbh without original SPL and IPL

so you dont have to worry abt CID lock again

coming to 2.2X and 3.07

you can use any USPL bro. if you want you can have a USPL 2.2X and IPL 2.2X

else you can update with USPL 3.07 and IPL 3.07

remember to match the USPL and IPL range...which means if the USPL is Y.25 then IPL shud match likewise as Y.25

where Y = Y

hehe...sorry if i went on telling something you already may know bro :D

and oh yes...i think flashin a goldcard will flash back a locked CID
[Touch GSM ROM Development] swordfish2009:
Thanks bro..

actully i knw some of it but it was not organised in my mind..

thanks for cleaning it ;)

Currently i have flashed 3.07 successfully.. so far no issues..

now will try to update my preious extracted and rebuild rom.

wish me a luck..
[Touch GSM ROM Development] swordfish2009:
again me with new questions..

I tried to update the extracted rom. now it says that this utility can not be used to update your pda phone error 328 !!
[Touch GSM ROM Development] Noonski:
What version did you give to your newly cooked Rom?

Give it a nice number from 2.0 or 3.0.000..... etc
[Touch GSM ROM Development] dsixda:
Search for the "RUU Error Codes" wiki page... 328 might be listed.
[Touch GSM ROM Development] trueg:
Does anybody here know what values control the fonts circled in my attached screenshot?

The circled word ROGERS for example in my ELFin build is larger than what I had in my Opal port.

Also, the lower words Call History and Calendar are smaller and bold in my Opal port.

Thanks
[Touch GSM ROM Development] Noonski:
Damn, i lost that bookmark from the M2D Skinning thread over at Development and hacking, no really i did.

Was so happy finding it in the first place.
[Touch GSM ROM Development] trueg:
Yuck, do you mean it would involve skinning Manilla? I was hoping for just a font value in the registry somewhere.
[Touch GSM ROM Development] Noonski:
It is a registry setting.

It was posted somewhere.

Maybe this one

http://xdaforums.com/showpost.php?p=2827653&postcount=581

Thanks to "m2d font change" and the Plugin i always blatently advertise for Hardcore XDA Users in my Signature ;)
[Touch GSM ROM Development] swordfish2009:
Hey mate noonski, I trik worked.. I flashed the extracted clean rom and my cell is up. :)

Thanks ayyu3m to ask me to update patch spl to cid unlock forever..

I will follow this thread to learn some cooking now..
[Touch GSM ROM Development] :
Error - seeking for help

I don't know what I did wrong.

I had to re-install hydrid kitchen, and start from scratch.

When cooking new ROM. I keep getting an error message "Error building default.hv and user.hv" when creating a registry.

Could someone please help me out? What is causing this?

Thanks
[Touch GSM ROM Development] swordfish2009:
Converting CAB to OEM problem:

I want to convert a cab to OEM now.

I followed these steps:

1 go to extras and ran InitFlashFiles Generator

2 A screen says " [ PLACE YOUR CAB ] and Press any key to continue"

3 I pressed enter and a exporer pops up.

4 I put the cab file to this folder

5 Pressed enter to command line

6 scree now says " = Starting MS Cab Analiser =

[ EXTRACT FILES AND EXIT ]

(Same folder)

Press any key to continue . . ."

Also can is renamed to appx

(shouldnt cab analyser open automatecaly???)

7 I extrated the appx to same directory as appx and closed explorer

8 pressed enter to command line.

9 error says that "system can not find the specified path" and command line closes"

initflashfiles file is created where i put the cab file but i doubt that its not good one.

Also when i try to open cab analyser manually from extra menu, some memory violation and run time errors come.

I am using vista on my laptop
[Touch GSM ROM Development] swordfish2009:
Replying to my own problem..

I read this wiki page and used BenThon's MSCEInf.exe and Ervius Package Creator to generate the OEM package from cab .. It seems to work for me..

I have added one OEM package to check if its working or not.

Rom is created and ready to be flashed.. will let you know the results ;)

EDIT : Flashed successfully with new package :)
[Touch GSM ROM Development] swordfish2009:
hpw to dump .payload? hypercore kitchen dumps only .nb
[Touch GSM ROM Development] kwbr:
Ameet was having similar problems in his early days. Maybe Orefkov's solution helps?
[Touch GSM ROM Development] trueg:
Thank you Noonski, I believe that may be what I am looking for. I loaded up my Opal port to confirm it actually looks different and it does, so I took screenshots.

Notice between shots 1 and 2 (Opal and then Touch) the font for Rogers in the first shot (Opal) is smaller and the date is displayed differently. Also, Call History & Calendar are different. I checked the Manila2D registry settings in Opal and all of the font settings are empty just like Touch. Could this be part of manila2d.exe? It almost looks like they use a different font.
[Touch GSM ROM Development] Noonski:
Well did you check the emd of the log.txt file that gets created in the Temp folder.

It will give you information which RGu the error is coming from and even around which line.
[Touch GSM ROM Development] trueg:
OK, I'm one step closer. Some of the differences are in the manila2d.exe. I copied the manila2d.exe over from Opal and it changed the date format (13/11/08 vs Nov 13, 2008) and the font used for Call History/Calendar. Though it didn't change the font used for the date or carrier. I don't know if it is worth using an older manila2d.exe in order to have these changes. I suppose if the settings are hardcoded into the exe, my only option is to try and figure out what font values to use in the Manila2D portion of the registry. :(
[Touch GSM ROM Development] Demo[95]:
Hi guys,

i'm currently wondering how initflashfiles.dat is created/generated...

In fact i'm struggling with this file as it's regenerated each time i launch bepe's buildos forcing me to modify it every time.

Anyone here for a good tips?:)
[Touch GSM ROM Development] Noonski:
Initflashfiles should not be completly recreated.

Or are you removing it from OEMLANG?

Buildos looks for all initflashfiles.txt and then appends them at the end of initflashfiles.dat.
[Touch GSM ROM Development] Demo[95]:
Ooops i didn't know it was present in this folder.... :o... now i know where to patch it.

Great tips... in the shipped rom i use as base for cooking, there are no initflashfiles.txt... but i guess it's normal; isn't it?

If i understand well, i guess that if i add one OEM package i can add an initflashfiles.txt in the folder and Buildos will automatically append instruction in the initflashfiles.dat?
[Touch GSM ROM Development] humrod:
Hi guys: I'm cooking an Hibrid rom (from opal and stock ESN) and have this problem: Main splash, animated gif, "White Screen" and finally the welcomehead in the calibration screen. I was looking in the forum, but there are some posts, but not an answer (or i didn't find it)

Thanks in advance
[Touch GSM ROM Development] Noonski:
This is a bugger to track.

I've had this happy on different ocasions.

Double posts of files in DSM files. ProvXML files that did two things with the same file.

Old fashioned 50/50 strikethrough troubleshooting. (if it was working before)

First replace the Sys with original or previous working one and Cook.

Most of the times the problem was in OEMDrivers or OEMAPPS with me.

Making the DSM files blank also resolved it somethimes.

This just isn't a sure thing as far as tips go.
[Touch GSM ROM Development] humrod:
Thanks nooski, will folow your tips and post here the results.

By the way, i saw in the forum some guys translated rom in italian and other lenguajes. I follow this process: Change the MUI files, translate the initflashfiles deleting the first two bytes, in registry change the folders and the key related to nui. Cook and flash. on boot the alignement and others initial screens like zone, etc doesn't appear, go directly to tha star screen. But the device isn't calibrated, and offcourse is inoperative.

Once again, with some tips i believe i can resolve this issue, and again thanks in advance
[Touch GSM ROM Development] letama:
I had this problem a few times. I thought first the problem was because of I was under 50Mb, but it occurs from time to time even after patching the right SPL. The issue disappeared by rebooting (or logoff) and rebuild the rom without modifying anything, it may be caused by a tool that lock file or something else, I don't know.
[Touch GSM ROM Development] Noonski:
Well some very nice guys pointed out to me that removing the first two bytes in initflashfiles isn't needed when you rename the .dat to .txt edit and then rename extension again. Or use a different Notepad that doesn not add these bytes.

The welcome wizard gets started by the welcome.lnk that should be in \Windows\StartUp\

But if on my completly based on NL rom that is \Windows\Opstarten\

So check the initflashfiles for that link, but also the registry settings somewhere in SYS\Shell or OS that hold the paths for Windows\Startup.