yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] Ameet:
Not forbiden stuff :) As I could understand from your question, you want to change the OS version of your Windows, right? There are many ways to do that, if you looking out only for updated numbers, then the d0b41563-b345-4444-aa15-986e7c7fff99.exe in OS folder needs Hex editing (I'm not sure if this file is responsible for the OS versions anyways) other way is to fully port the OS. Search is the best function to get info needed around here ;)
[Touch GSM ROM Development] humrod:
Thanks again, i'm going to search the forum.
[Touch GSM ROM Development] Gartak:
Custom RGU not working

Guys, I have, in my SYS folder, a package that contains only a registry tweaking RGU file. Of course the folder also has a DSM and an option.xml file.

The problem is that some of the registry settings done by this RGU file don´t work!

Since some of them work, and some don´t, I guess there´s something writing to the registry AFTER this package has been processed, overwriting some settings.

So, is there a way for me to be sure this custom registry package is the last thing to be run when building my ROM, so that it´s settings will prevail?

Thanks!

Eduardo
[Touch GSM ROM Development] dsixda:
Yeah, the problem may be that you have an RGU or provxml somewhere else that is overwriting the RGU file you added. you can try renaming the folder to something starting with "z" so that this folder and its RGU are processed last.
[Touch GSM ROM Development] Gartak:
Thanks for the help, but I did that, and it didn´t work..

It seems the folders aren´t sorted by their names during the built. Looking in the logs, RGUCOMP.EXE is the component that reads RGU and DSM files, and the RGU with my tweaks seems to be read near the start of the process...

It´s strange.. Last week I had the kitchen set up for another SYS/XIP version, and all my registry tweaks worked fine. Now that I rebuilt the OEM/ROM/SYS structure, I started to have this problem!

Eduardo
[Touch GSM ROM Development] Gartak:
It seems the answer will be to hunt each reg setting in all RGUs and PROVXMLs around!

I just found lots of junk in a lot of RUGs I didn´t even touch before, like the one in OEMDrivers folder!

Oh my.. this ROM cleaning thing is turning into an obssession!!! :)

Eduardo
[Touch GSM ROM Development] dsixda:
If your RGU file is in the SYS folder, it shouldn't be affected by the OEMAPPS/OEM_LANG/OEMDRIVERS folders. However, if it is under OEM then you'll run into the problems above ;) I made a custom RGU-related folder under SYS called zzz_dsixda that overrides the other registry settings.
[Touch GSM ROM Development] Gartak:
Really?? This is really strange, cause my custom reg package was inside SYS..

Anyway, I´ll start some serious cleanup in my OEM folders, it seems things like camera, htc home, and phone skin have reg settings scattered all over.

Thanks for the help!

Eduardo
[Touch GSM ROM Development] Noonski:
Well HTC is cleaning house if any of you has dumped the Touch HD rom just for fun.

You'll see that almost no apps and settings are going into OEMAPPS anymore.

Everything gets separated.

Even the Power EXE.

Making it even easier for my to make some Very cool and useful OEM packages that hopefully in the end hold all settings that apply to that app.
[Touch GSM ROM Development] trueg:
It does seem like HTC is making it easy for us cooks (OK, maybe they do it for themselves, but it sure makes a difference for us). The new WM 6.1 ELFin build (3.07.720.03) is similar I believe to what you describe. In the OEMApps folder, there are only 28 files, with 8 of those being shortcuts. We couldn't ask for a better setup!

My problem is, Hybrid Kitchen crashes when I try to build using this new release.

I had no problem dumping the ROM. BuildOS has no problem processing all of the files. When it gets to the point of patching the pagepool, I get an error. Then the OS files size reports as 0 MB. Finally when HTC ROM Tool tries to build an RUU it crashes (I assume because of the initial error patching and the resulting 0 MB OS.nb).

Any ideas?

Edit: Sorry, never mind. There was a file (list.txt) in the root of OEM. I deleted it and now it builds fine. =)
[Touch GSM ROM Development] dsixda:
ARghh... I don't know what happened, but after adding the new files from the M2D Elfin ROM, Ervius' PkgToolsBuildOs gives me this message when I select Load Rom:

"Error, cannot Find \ROM Folder!!!"

I already have the correct folders there.. OEM, SYS, ROM (with XIP inside)

???

EDIT: Looks like it's the new XIP that I am using.. doesn't give errors if I use the old XIPs. I extracted the files inside of xip.bin with HyperCore.
[Touch GSM ROM Development] ayyu3m:
check ur PM bro
[Touch GSM ROM Development] trueg:
I guess I'm stuck with a different problem.

I dumped the ELFin 3.07.720.03 build using Hybrid Kitchen. It seemed to dump perfectly. I copied the OEM, XIP and SYS into the kitchen and built it. No problems with BuildOs or in making the final ROM, but after successfully flashing it, my ELFin fails to start up. It just hangs on the first boot screen. As suggested by another member, I extracted the full OS.nb from the same ROM and re-named it OS.nb.payload and copied it to \ROM. Again it builds just fine, but after flashing it just hangs.

No sure where to go from here. =(
[Touch GSM ROM Development] dsixda:
Did you change any registry entries?
[Touch GSM ROM Development] !Aman!:
which kitchen are u using for cooking?
[Touch GSM ROM Development] trueg:
Nope, straight from dump to kitchen. When it hangs on boot I would normally suspect bad registry entries, but I haven't touched anything. Perhaps a bad dump? I suppose I could download ayyu3m's dumped OEM, SYS & XIP.
[Touch GSM ROM Development] Noonski:
What huh, have i been sleeping "The new WM 6.1 ELFin build (3.07.720.03)"
[Touch GSM ROM Development] trueg:
Hybrid Kitchen
[Touch GSM ROM Development] !Aman!:
use Hypercore for dumping only. when u want to cook the ROM, use hybrid kitchen or bepe's kitchen.
[Touch GSM ROM Development] trueg:
Ya I guess so. =)

It was uploaded this morning.

http://xdaforums.com/showthread.php?t=442391
[Touch GSM ROM Development] trueg:
I use Hybrid Kitchen for both. Are you saying I should use Hypercore for dumping?
[Touch GSM ROM Development] Ameet:
I say you go manual all the way just so to know how its done ;) That way you may be able to troubleshoot what went wrong :D
[Touch GSM ROM Development] trueg:
Yikes, I'm already pushing it as far as using all of my free time cooking (and some not so free time). I don't know where I would find the time to learn manual dumping too. :eek:
[Touch GSM ROM Development] !Aman!:
:D

1. copy the RUU_Signed.nbh to Extract_ROM\Tools\ folder in your C:\ELF(in)_Hybrid_Kitchen. use NBHextract.exe RUU_Signed.nbh and get the OS.nb out of it.

2. imgfsfromnb.exe os.nb imgfs.bin

3. imgfstodump imgfs.bin

4. after step 3 completes, u will get "dump" folder.

5. run PKGTool.exe and browse to 'dump' folder. then chose Tools>build packages. after this u will get the OEM and SYS folders

For xip.bin:

1. RomMaster.exe -x -w 5 os.nb -o xip.bin
[Touch GSM ROM Development] trueg:
OK, maybe it wouldn't require that much free time. :D
[Touch GSM ROM Development] !Aman!:
yeah, needs not more than 5 minutes ;)

PS:

copy the xip.bin to C:\ELF(in)_Hybrid_Kitchen\Prepare_XIP folder. then run:

dumprom.exe xip.bin -5 -d XIP

to get the new XIP folder which u can use inside the C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19XXX\ROM folder as such because this is from Elfin's shipped ROM and doesn't need porting.
[Touch GSM ROM Development] trueg:
Thank you for the help folks. It must have been a dumping issue. I downloaded the OEM, SYS and XIP.bin from ayyu3m's post. Used the above command to dump XIP.bin and tried again. This time it worked. :)
[Touch GSM ROM Development] !Aman!:
glad to know that :D but next time do try the manual dumping also ;)
[Touch GSM ROM Development] trueg:
Indeed. I didn't want to introduce yet another error from doing the dumping manually so I thought I would download the extracted OEM, SYS and XIP.bin.

My problems are not over though it seems. It finally booted properly, but it is not running like it should.

I didn't change anything from the downloaded SYS & OEM. I did manually dump XIP.bin though. The problem is that the theme was not set during customization (still using default blue instead of HTC black) and apparently it won't set manually either. Also, the connection manager isn't able to make any changes as it asks to reboot, but the settings are not there after a reset and then it tries to set them again.

How is this even possible? Assuming the OEM & SYS are exactly like the original, then somehow dumping the XIP manually caused a problem? Could there be a compatibility problem with this build and Hybrid Kitchen?
[Touch GSM ROM Development] !Aman!:
which os.nb.payload did u use? from new ROM or the previous one?

also, could u try all over again by manually dumping the ROM?
[Touch GSM ROM Development] trueg:
OK, so I deleted the OEM and SYS that I downloaded from ayyu3m's post. I went back to the OEM and SYS that I original obtained from dumping the ROM in Hybrid Kitchen. I kept the XIP folder that I got from dumping XIP.bin manually.

I no longer had the problem I was having before, so it must have been a problem with the XIP that was dumped by Hybrid Kitchen.

In addition, it is now working as expected. The theme was set correctly and connection manager was able to set my connection settings on the first try. I am sure there were other things wrong, but these were the two I first noticed.

Since all I did was delete the OEM & SYS that I had downloaded and went back to the OEM & SYS that I dumped in Hybrid Kitchen, do I assume that there is a problem with either the OEM or SYS from ayyu3m?
[Touch GSM ROM Development] trueg:
I have been using the OS.nb (renamed as OS.nb.payload) from this 3.07 release.
[Touch GSM ROM Development] !Aman!:
those issues should not arise because of xip. if the xip is faulty, the device won't boot at all. so i guess it might be a problem related to OEM or SYS.
[Touch GSM ROM Development] !Aman!:
then u have to modify the Insert command while using Hybrid/bepe's kitchen in a bat file which inserts the xip_out.bin into payload as imgfs start offset in new ROM is different from the old one ;)
[Touch GSM ROM Development] trueg:
Sorry, what I meant was my original issue where it would hang on boot must have been due to the XIP dumped by Hybrid Kitchen since I am once again using the OEM & SYS that I obtained by dumping in Hybrid Kitchen and no longer have the problem where it hangs on boot.

The issue where it didn't seem to build correctly (customization not running properly, problems with connection manager) was not related to XIP as you have stated above. This issue was somehow related to the OEM and SYS that I had downloaded. Once I went back to the OEM & SYS that I dumped myself in Hybrid Kitchen, this issue went away.

As it stands right now, everything is working perfectly. I have the OEM and SYS that was created by Hybrid Kitchen and the XIP that I did manually by dumping the XIP.bin that I downloaded from ayyu3m.

If everything is working, do I need to modify the batch files in Hybrid Kitchen?

Also, is there a problem with the OEM or SYS from ayyu3m since my problem went away once I switched to my own dumped OEM and SYS?
[Touch GSM ROM Development] kokotas:
Hi guys!

Why am I always so late??:D

Just saw the new official ROM and downloading it as we speak...

And so I see that there were problems dumping it with Hybrid Kitchen,right?

I will spend some time today with this issue.

My guess from what I read so far is that your problem was

instead of the OS.nb.payload that came with the kitchen.

Because if you want to use the OS.nb (renamed as OS.nb.payload)

then as Aman told you

meaning:

If you use PkgToolsBuildos,

go to C:\ELF(in)_Hybrid_Kitchen\ELFIN_DEV_v2.1_Build_19XXX\TOOLS

edit the CREATE_ROM_For_ELF.bat @ line:

..\TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00310000 -s 0x00340000

where:

-i <file> Source file.
-o <file> Destination file.
-d <hex> Destination address.
-s <hex> Full size to fill up with 0xff.

Now you need to find the Destination address [-d] in your OS.nb.payload

I'm not sure how it's done!Maybe I'm doing it wrong all this time:DSo any suggestions are welcomed:)

Well try:

1.Open the Os.nb.payload with a hex editor

2.Search for this pattern "FE 03 00 EA 00 00 00 00"

3.If you find it twice, then the second address is the one we need:Note the address for the first byte "FE" and use it in insert command for -d <hex> parameter.

Now you need to find the size of xip "section" [-s] in your OS.nb.payload

1.Open the Os.nb.payload with a hex editor

2.Search for this pattern "FF F8 AC 2C 9D E3 D4 2B 4D BD"

3.Note the address for the second byte "F8" and use it in finding the -s <hex> parameter for insert command:

(F8 hex-address) - (-d <hex>) = -s <hex>

Regards!
[Touch GSM ROM Development] !Aman!:
since the imgfs starts at 0x660000 in new ROM, so the command would be:

\TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00310000 -s 0x[B][color=blue]00350000[/color][/B]

if someone wants to use new ROM as payload :)
[Touch GSM ROM Development] kokotas:
Thanks Aman!

I didn't thought about the size at all:o

The File is downloaded!

Now I can start playing:D

Something else...

I'm having a cooking issue:

It's about XIPPort!

What is the reason of the following error?

System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.
Parameter name: length

When I edit the imageinfo.txt with notepad no errors occur.

But if I make the same changes with a commandline text editor(gsar), I get this error!:confused:

Where is the catch?
[Touch GSM ROM Development] Ameet:
Ok. I dont support cross posting but its ok if thats done for a cause :D

Here's my cross posting question which will surely help in increasing the knowledge in the xip guide ;)

Scenario:

XIP size (figuratively speaking): from 00310000 to 00320000

imgfs starts at: 00350000 (0x660000)

Question:

Instead of filling up the space (from 00320000 to 00350000) with 0xFF, cant we instead realloc the ulRamEnd (RAM end address) to 00350000 increasing the size of the resulting xip_out.bin naturally and use that 0xFF in the XIP as free RAM instead? :D
[Touch GSM ROM Development] Ameet:
Hey koko. Long time :) I remember this error :D

Increase the physlast by 1mb in the romhdr to make more space for the ported xip modules. Then work your way on the vbase & realaddr addrsesses and then revise the physlast to the value which you get

Phew!! I think I just confused myself right now
[Touch GSM ROM Development] !Aman!:
u know very well that i'm not yet capable of answering these questions :D
[Touch GSM ROM Development] ayyu3m:
wow! the hype here is really big...and it shud be...cos its about time HTC released elfin users a ROM update....

btw to clear any further doubts with the uploaded SYS and OEM...lemme say

the SYS and OEM was dumped and nothing was changed, nor added or removed any files or components. so its an upload straight from the DUMP.

but it is a strange case trueg has faced since his dumping in HyperCore enabled him to use some of the features like customization and connection setup without any probs

:confused:
[Touch GSM ROM Development] trueg:
As of right now, using the OEM and SYS from Hybrid Kitchen, the XIP from manually dumping XIP.bin from ayyu3m and the OS.nb from 3.07 as my payload I am not having any problems.

I thought I had to use the OS.nb from 3.07. If I don't I will gladly go back. If everything is working, do I even need to change anything?
[Touch GSM ROM Development] !Aman!:
u can use any Elfin os.nb :)
[Touch GSM ROM Development] trueg:
..but if I don't want to have to change the parameters in Hybrid Kitchen, I should stick with the OS.nb.payload that came with it?
[Touch GSM ROM Development] !Aman!:
yes :) ...
[Touch GSM ROM Development] Noonski:
Okay attached is the O.R.E.E Noob Kitchen made from Bepe's original v 2.1.

the Sys Oem and Rom folders need to be populated.

But i cant test the new Rom at the moment.

If any of you can test it that would be step one.

It's a Cook and Flash only Simple Kitchen for those that don't know the Concept.
[Touch GSM ROM Development] trueg:
Indeed, it still works after going back to the original OS.nb.payload and this way I know the addresses that Hybrid Kitchen is using are correct.

So, just to recap, originally I had a problem where my phone would hang after flashing to a ROM built with the SYS, OEM and XIP from ELFin 3.07 dumped by Hybrid Kitchen. It seems the XIP did not dump correctly as doing it manually corrected the problem. :)
[Touch GSM ROM Development] Demo[95]:
Hi guys,

i'm trying to apply your receipies (Extract Rom and XIP) and Cooking your First Plain Unedited Rom on the newly shipped rom 3.07.720.03 WWE.

I'm facing a stange problem, the dumping and the rebuilding are ok, the flashing works also.... but after being flashed, my device strangely freeze on the Windows splash.

Another strange thing is that the rebuilded Rom is only 87,6 MB whereas the original is 110 MB. Shouldn't the rebuild process be à 1:1 process (i mean nothing being lost)? BTW, I haven't removed anything.

Any ideas of what i may have done wrong?
[Touch GSM ROM Development] trueg:
If you want to eliminate possible dumping issues, you could download ayyu3m's OEM and SYS and then use my XIP folder. I had the same problem when I first tried to build a ROM using 3.07.

trueg
[Touch GSM ROM Development] Noonski:
Thanks, in case i'll need it in advance.
[Touch GSM ROM Development] trueg:
I forgot to mention that your new ROM is smaller because it doesn't have extra crap like IPL/SPL, splash, radio, etc etc, just the OS.
[Touch GSM ROM Development] Demo[95]:
First, thank for your replies trueg.

As i'm a noob (:o), and even if i'd like to understand what i'm doing wrong, i've downloaded those 3 archives.

For OEM and SYS, there was no problem.

But for XIP i don't know where to unzip it, cuz as i stated in my previous post i'm using Hypercore Kitchen and i didn't find where to put the file. I guess, the Hypercore kitchen work with the dumped version of the XIP, not in bin format... but i'm totally noob so i may be wrong :o

No no, IPL/SPL SPLASH etc were already removed as i've downloaded dsixda's file here : http://myunspace.com/?d=2D5457721

So that's not those craps that cause the extra size.

Here are some new questions :

- Is it possible to cook this newly shipped rom with Hypercore kitchen?

- Do i have to switch to Hybrid Kitchen as most of you seems to use?

- Does Extract Rom and XIP and Cooking your First Plain Unedited Rom

are still reference tutorial? if not would you please point me the right doc to read :D

[Mode dreaming]

I thought it would be simple for a french guy to become a great "chef"... but it's a long road... For now i'm only working in a Mac Donald Restaurant :D

[/Mode dreaming]
[Touch GSM ROM Development] ayyu3m:
Those are the correct documents that you are reading. And the screenshot tutorial denotes that they are NOT merely reference tutorials..but serious ones :)

There are 2 ways out for you on the XIP problem.

Using HyperCore

-Download the actual RUU_signed.nbh and follow the guide closely to successfully extract the XIP

Using Hybrid Kitchen

-Downloade the kitchen. Set it up. And Downloade the RUU_signed.nbh. and follow the on-screen instruction in Hybrid Kitchen.

btw as you have also noted, and as many has suggested using Hybrid Kitchen is much easier and user friendly cos it gives you a lot of options in one screen so that you dont need to watch here and there except follow the steps closely

Consider HyperCore as a stove that got you started. now its time for the real kitchen.

AND working in McDonald'? how abt some free burgers man??!!!
[Touch GSM ROM Development] Demo[95]:
Ok... i've managed to (re)pack my first rom with Hibrid Kitchen... but i had to figure that i should manually move the OEM PACKAGE folder before rebuilding it. I thought the kitchen would do it automatically.:p

Anyway, thanks ayyu3m for your help...

I guess i'll be back here in very little time with some new questions for you Gurus.
[Touch GSM ROM Development] swordfish2009:
Hello,

I have followed steps for extracting the rom and building the unedited ruu_signed.nbh.

But when i try to flash it, it says error 228 invalid file size..What could be the problem.

I have followed the exact steps and used latest 3.07 shiped rom as reference.
[Touch GSM ROM Development] ayyu3m:
er...do you have ur device CID unlocked??
[Touch GSM ROM Development] swordfish2009:
yes it is but i used uspl to make it temporary cid unlocked
[Touch GSM ROM Development] ayyu3m:
its time you moved to permanently patched SPL bro....it will save your phone...should you by mistake flash without CID unlocking...cos this is one tip all cooks rely on

its always better to have ur device CID unlocked in a permanent manner if ur into cooking

and shud you feel you wana go back...jus flash a SPL that is locked
[Touch GSM ROM Development] vadyarik:
Open hidden regimes shooting:

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\Camera\P6]

"Enable"=1

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\Camera\P8]

"Enable"=1

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\Camera\P9]

"Enable"=1

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\Camera\P10]

"Enable"=1

:D
[Touch GSM ROM Development] dsixda:
Vadyarik,

What do 9 and 10 unlock?

6 = Burst Mode

8 = Sports

There two empty tiles in the 2nd list of modes, probably for 9 and 10.

I thought 10 was for geo-positional shots?

EDIT: Nevermind, 9 = Video Share, 10 = GPS Photo
[Touch GSM ROM Development] vadyarik:
I think it is most important:

:)
[Touch GSM ROM Development] dsixda:
P10 (GPS Photo) is not shown.. I guess we need a GPS chip like the Vogue, for it to be unlocked?
[Touch GSM ROM Development] Ameet:
I dont think you need GPS chip to unlock the mode in camera. Although you cant use that mode since the camera would search for a GPS chip, but thats only to actually use it. I had it unlock through Advance Config in ElfIn as well as Diamond
[Touch GSM ROM Development] dsixda:
Where in Advanced Config is it? I don't see anything relevant under 'GPS'.

BTW, the XML file has "Assisted GPS" but I don't see it in the options under GPS.
[Touch GSM ROM Development] Noonski:
The option should be under camera, it's where i got the registry trick from.
[Touch GSM ROM Development] dsixda:
No, under Camera I only have

- save location

- encode photos in portrait m ode

- capture key delay

- key delay

- capture key delay time

This is on the Elfin. I saw in the XML he has some stuff about Diamond and other devices for certain settings.

I'm using version 3.3
[Touch GSM ROM Development] dsixda:
I noticed in my ROM that right before M2D starts up, the 'Date' item for Today is showing up. I tried creating a new key called HKLM/Software/Microsoft/Today/Items/Date, and then setting Enabled to 0, but that doesn't do anything after re-flashing... I still get that Date screen on a hard reset.

The stock 3.07 ROM doesn't have this behaviour, but mine does...

EDIT: Nevermind... I think it's this:

[HKLM/Software/Microsoft/Today]

"Date"=0

I notice it changes to 1 if I enable Date in the Today items screen.

Instead of having its own key, Date is a value. ?????
[Touch GSM ROM Development] Noonski:
Well Advanced config changes options according to devices.

So the options are hidden.

You will find it there under diamond settings inthe XML file ;)
[Touch GSM ROM Development] tiggerbcn:
No, this where my error. Thanks
[Touch GSM ROM Development] Noonski:
Now for the real challenge.

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

Hehehehehe?
[Touch GSM ROM Development] orouborus:
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?