yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] kokotas:
If you use this rom's OS.nb as your OS.nb.payload then the cmd is:

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

and the secuence FE 03 00 EA 00 00 00 00 is found twice!

There is something wrong if you find it only once! Maybe you should redownload the Rom?

If your problem is that you get stuck at "Smart Mobility" Screen then it's possible that XIP is the cause!

Use the XIP which is dumped from that ROM without any changes and see if it boots..
[Touch GSM ROM Development] humrod:
Well, some advance: now boot but stck in the windows mobile green screen..

Actually the kitchen is with your changes in make a rom bat, the original XIP nd change the OS.nb.payload from the OS.n file.
[Touch GSM ROM Development] humrod:
To confirm that all is OK I dump the original rom and rebulid, but this is stuck on the green screen too.....
[Touch GSM ROM Development] kokotas:
I did the same thing with that rom and even though it seemed to get stuck at Green Screen,

it just took a loooong time to boot...

Even the screen went off before it decided to boot - lol:D

Don't know why this has happened, but since it boots I think it's ok!

Here is what I used in order to get it done.

Regards!
[Touch GSM ROM Development] humrod:
Hi Kokotas. after some probes, i detect the following:

I build a spanish rom in Neokit and it flash ok.

I took this OS.nb and dump in Hybrid. I need to put the missing files in correct place (neokit don't keeps the packages) and check that the default.hv and the user.hv in metadata has 3082 (or 0C0A) spanish lang as default language.

I build with ervius keeping the packages.

The device boots untill the first splash (WM 6.1 green).

I dump the RUU_signed.nbh (from Hybrid Flash ROM) OS.nb and dump this, and analyce the default.hv and user.hv the registry langs is in 0409 (english).....(after bluid!!!!)

Of course, I check the default.hv and user.hv in metadata (in Hybrid Build ROM) and it keeps the 3082 lang.

I rename the OS.n as OS.nb.payload (I thougth is possible that this file change the lang) and nothing: boot until green screen.

I'm confused.
[Touch GSM ROM Development] kokotas:
Hi humrod!

Sorry for the delay:)

The thing is that the kitchen's tools don't use the default.hv and user.hv in metadata but it builds them from your *.rgus.

I don't know why your phone doesn't want to boot!

If you still have this problem, I could try to help if you want to upload somewhere your OEM,SYS&XIP to take a look.

You could also try bepe's platformrebuilder - @ 2nd Post;)

Regards!
[Touch GSM ROM Development] humrod:
Thanks Kokotas. I was thinking about that and I'm cooking the rom same way, but changing the rgu, especially the one in SYS/Base Lang 0409. There's the NLS, MUI and curlang keys, basic for the translation. when finish I post the result here....
[Touch GSM ROM Development] humrod:
Well Kokotas, that's the key....

Basically the diference (in the topic of translation) betwen neokit and Hybrid, is in the form that rebuild the registry. The first uses the default.hv and user.hv, and hybrid uses the rgu's. That's the way neokit can manage the "protected" roms build with ervious and beep's.

Now I have a base rom in spanish (0C0A) but with the packages....

Thanks for your support and indications
[Touch GSM ROM Development] c2b2:
The first page says that we can modify Dumped and not cooked ROM.

Is there any tool that lets us modify Cooked ROMs? Checked out the pages of a few kitchens. They were not very clear. Can someone please suggest one.

I'm a newbie. I've only CID unlocked my phone and flashed a few ROMs. Thats my level of knowledge.
[Touch GSM ROM Development] humrod:
Usually we refer to Cooked roms a rom that was cooked with protection process. If you dump it you obtain a "Dump" carpet with all the files without packages. You can't recook it with this kitchen. A dumped rom is a rom that you can dump an obtain the OEM/SYS carpets.
[Touch GSM ROM Development] dsixda:
Where do you have proof of such a statement?

Those who "accept" donations are not hiding anything from anyone. 99% of the cooks in the Elf forum are the friendliest and most helpful people in xda. I wouldn't have gotten started without the help of people like Noonski, Kokotas, Ababrekar and Htctouchp.
[Touch GSM ROM Development] dsixda:
Yeah I have protected my ROMs since 4.1.2 because it runs much faster now (around 300 less files in Windows) ;)

But if you try to dump it with Bepe's kitchen or other kitchens you'll get the message "Contact me" :-)

BTW htctouchp... where have you been hiding!! Hi!!!
[Touch GSM ROM Development] !Aman!:
yeah, the so called "protection" reduces the load on \windows folder and makes the ROM better ;)

i've been hiding coz i'm not much needed nowadays with the kind of support u provide :) u have left nothing for me to do here now :D
[Touch GSM ROM Development] Demo[95]:
So our friend c2b2, can choose at least between Onyx and AEther OEM and SYS folders to modify and cook is own ROM...
[Touch GSM ROM Development] Ameet:
Feels great to post in here after a long time :D Hey koko. How you been?

Just cleaned up the last few "donation statement" posts. Looking good now as always :)
[Touch GSM ROM Development] dsixda:
Haha.. we always need you here man. We'll need all our minds together to get a fully working 6.5 for our ROMs in less than one month ;-)
[Touch GSM ROM Development] dsixda:
Nice to see you back too!
[Touch GSM ROM Development] kokotas:
Hey guys!

You've got it all wrong and it's not really your fault.

I believe that by "modify" you mean:

(1)"dump into Packages"

(2)"add/remove/edit stuff"

(3)"rebuild a flashable rom"

IF the first one (1) can not be performed then it is normal (logical) that this chain of events breaks and you can't "modify" the rom you are after.

In which case the first one (1) fails or works?

All the Official roms (Shipped and Dumped) include *.dsm(s), so they are "dumpable".

When a rom is cooked with all the *.dsm(s) included then it can be "dumped into Packages".

When a rom is cooked without *.dsm(s) aka "Protected_rom" then it can NOT be "dumped into Packages".

I disagree with the term "Protected_rom" but this is how it is known..

My opinion is that the case of a rom with no *.dsm(s) is not a Protected rom but an optimized rom!

Aman described much better what I mean:

And if you want to dump a "Protected_rom", you only have to do one simple thing: ASK the cook to share his ingredients and recipe...(but know that he/she has the right to deny)

Hey Ameet!Nice to see you here!

I'm doing ok! But I'm getting ready to be away for some time(going in the army for a year).

Keep the forum clean and interesting brothers!;)

Regards!
[Touch GSM ROM Development] c2b2:
Thanx Kokotas. Nicely explained.

I wanted to remove just a few apps that came preloaded in my ROM which I'm never gonna use.

But I dont mind leaving the ROM as it is. I though removing a few apps would be something very easy.

Thanx anyways.
[Touch GSM ROM Development] Ameet:
Hopefully I'll be counted in it too.. Will be great to learn XIP porting for the new Win ;) Am sure even Noonski's gonna play a good part in this :D

Hey koko. Wish ya all the best for the army thingy brother :) Going in the army as what buddy?
[Touch GSM ROM Development] dsixda:
Koko,

Just want to say, your latest version of the kitchen is fabulous. I can just hit "Run" and it does the building, the CREATE_ROM.bat, and the htcrt.exe ROM creation all automatically without requiring my interaction! And the new os.payload.nb is so tiny that it's easy to move the kitchen to my laptop or other PCs (even my work PC.. just kidding ;))!

Where's your donation link? ;)

So is this mandatory army service in your country?
[Touch GSM ROM Development] dsixda:
Yeah that will be awesome if the old crew comes out of Elf retirement ;)

I still have problems once in a while with XIP porting. I just rely on Koko's kitchen, close my eyes, and hope for the best. ;)
[Touch GSM ROM Development] !Aman!:
well u should try bepe's new kitchen... its far better than the previous ones, u just have to place the new msxipkernel into the XIP :)
[Touch GSM ROM Development] kokotas:
Glad that I helped a bit!

If you still want to cook a little, try this:

Dump one of the latest 3.xx roms and one of the 2.xx roms.

You'll see that something is different...

The latest 3.xx roms are very "cook-friendly", meaning that almost everything is Packaged.On the other side the old 2.xx roms were more difficult to customize.

i.e.: If you want to remove the "ZIP" from the 3.xx rom you just have to remove the folders PACKAGE_Elfin_ZIP & PACKAGE_Elfin_ZIP_0409.

If you wanted to do the same thing for a 2.xx rom you should find all the regarding-"ZIP" files in OEM and search through the registry for any keys that have to do with ZIP in order to remove them.

So what I'm trying to say is

use the latest official shipped rom as your base for cooking and you'll see that removing a few apps won't be something very difficult.

Hey Ameet!

It is a mandatory thing, as dsixda said! It is just a (precious)time loss(a whole year of our lives)...Thanks for your wishes!

I'm happy to hear that brother!

This kitchen of course is based on tools from real developers - I just combined them... and without all of you this couldn't have happened!

Btw, you should listen to Aman[He is the Man!;)]:

Check the 2nd post @ 1st page. There is the link to bepe's new kitchen @ www.darkforcesteam.com and 2 examples by me.

Best Regards my friends!
[Touch GSM ROM Development] dsixda:
Hey guys, in Bepe's Elfin kitchen, are the Page Pool values stored at 0x43E10 of nk.exe\S0000? The reason is, I see the following, which corresponds to the actual page pool values: "03 15 A0 03 02 15 A0 13"

I didn't touch these PP values, but when I flash the ROM on my Elfin, I get 10MB extra(!!!!!!) program memory with my Onyx Ultimate, but I wonder if it's the page pool being too low (like 2MB and not 12MB?? ha ha). The loading of M2D does take a while.

Also the file size of the ROM is 2MB higher than with Hybrid kitchen (with Ervius' build tool).

Any ideas?
[Touch GSM ROM Development] Demo[95]:
Bepe kitchen do not autocmatically remove ULDR in the payload.... and you're right the pagepool is 2MB.

Ervius as updated his tool, and has integrated it with bepe new kitchen, so that it's even easier to use it.
[Touch GSM ROM Development] kokotas:
I have edited nk.exe's S000 so that the string "03 15 A0 03 02 15 A0 13 ..." is NOT responsible for the PagePool Size(link)

Open CreateROM.bat and you'll see the right offset and some (hopefully) helpful comments in there;)

Check which payload you used.

If you used to use the OS.nb.payload attached @ 1st post(where imgfs start @ 0x280000) with Hybrid Kitchen and now you use the supplied OS.nb.payload(where imgfs start @ 0x300000) then the increase of the rom size is normal:)

In my case

using the same payload in both kitchens, the same rom is built 0.6MB smaller than with Hybrid...

Regards!
[Touch GSM ROM Development] dsixda:
Ok, so there are options in CREATE_ROM.bat for the different page pool sizes... but how do I set page pools for both Elf and Elfin at the same time (e.g. 4MB if flashed to Elf and 12MB if flashed to Elfin)? I tried setting the same way as in the Hybrid kitchen, but that didn't work.

Oh nevermind, I think I know the problem. This kitchen doesn't look at option.xml file in each OEM package.. I had several OEMs that had the "checked" option set to "False" but were still found in the flashed ROM. I guess I'll have to delete them instead of using option.xml.
[Touch GSM ROM Development] !Aman!:
u can not set separate PPs for Elf and Elfin this way as both will be having default value of 2 MBs.
[Touch GSM ROM Development] sjeph8je:
xipporterex.exe marked as virus

just downloaded this kitchen and when I installed it, my virusscanner (AVG) reported the file XIPporterex.exe as virus. After online virusscan there are abt 7 scanners reporting it as a supicous file. does anyone have similar results? :confused:
[Touch GSM ROM Development] kokotas:
Check XipporterEx-ReadMe.txt!

But don't worry!It's not a virus.It's only a simple shortcut.

Regards!
[Touch GSM ROM Development] sjeph8je:
OK, no worries

I actualy did read the txt file, but it is still strange it gets reported

txs for the explanation.
[Touch GSM ROM Development] dsixda:
How would you do it then with this kitchen?
[Touch GSM ROM Development] !Aman!:
u either need to change the 00 00 A0 E1 back to 00 10 83 E5 so that u can get 2 PPs, one for Elf and another for Elfin or u need to cook separate ROMs for Elf and Elfin by setting desired PP using PP changer.
[Touch GSM ROM Development] dsixda:
Bah, I'll just stick to Koko's Hybrid Kitchen then ;) It's much more simpler.
[Touch GSM ROM Development] humrod:
Hi Kokotas, your last versión works very well. If you remember, I use it with a spanish rom with a ported hermes 21109 SYS and really work ok. In fact I use it in a "lite Cooking Class" in HTCSpain.

Just a question: how can I change the default setting "Use Payload yet..."?
[Touch GSM ROM Development] zoko:
it´s possible to use this kitchen on stock 2.20 Official ROM, i wanna just modify some stuffs on original ROM!
[Touch GSM ROM Development] dsixda:
I have a problem SOMETIMES when I try to port a new SYS/XIP to my existing OEM folder.

Whenever I try to select a new ring tone from the pulldown menu under the phone options, and then hit Ok, it will go back to the default ring tone and the window will not close.

The pulldown menu shows the following ring tones:

- All the ringtones (*.wma) that are under OEMDrivers

- All the ringtones (*.wma) that are under PhoneRedist_Lang_0409

I don't understand why it works for some SYS but not others... I even tried replacing PhoneRedist_Lang_0409 with a working SYS's folder but that didn't help either.

Any advice??
[Touch GSM ROM Development] dsixda:
You have to change the base ROM to one that is for 2.20 (I don't think the 3.xx base ROMs are compatible with 2.20 drivers or SYS), plus the create_rom.bat file may need to be changed. I may be wrong though, but some of my experiments in the past have shown issues when using 2.2x drivers/SYS/XIP with 3.xx base ROM.
[Touch GSM ROM Development] zoko:
tks dsixda i´ve tried with RUU_Elfin_HTC_PTG_2.20.410.1B_4.1.13.51_03.07.90_BLUE_Ship_Reduced and don´t work stuck on welcomehead.96.png!! sad!! :-(

There are any ELFIN Kitchen to work with this type of ROM!?
[Touch GSM ROM Development] dsixda:
Use a base ROM for 2.20 (get the OS.nb) and try again.
[Touch GSM ROM Development] dsixda:
Nevermind, I think this is the answer:

http://xdaforums.com/showpost.php?p=1932542&postcount=61

Need to add this:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"

This code is in the boot.rgu. Well, I had ported the XIP wrong and thus got the wrong boot.rgu. Bepe's new PlatformRebuilder kitchen will prevent stupid mistakes like this from happening again ;)
[Touch GSM ROM Development] niceguy001:
after a long search i couldnt find any solution to this error msg:

----------------------------------------------------------------

...

ImgFs partition starts at 0x00300000 and ends at 0x00310000

Dumping IMGFS at offset 0x00300000 (size 0x00010000)

Done!

ImgfsToNb 2.1rc2

Using bigstorage mode

Input file imgfs-new.bin cannot be opened. Exiting.

ERROR! (errorlevel: 1)

---------------------------------------------------------------

i have followed the steps from this kitchen. i'm using OS.nb (RUU_Elfin_hTC_Asia_AUS_3.10.710.00_4.1.13.71_03.34.90_BLUE_Ship)

anyone can help me?

second thing is that i want to remove some application that i dont need. how can i achieve that? just deleting packages from OEM folder wont be the right way?!?!

thnx in advance
[Touch GSM ROM Development] Timewolf:
Hi,

i've a problem:

Installed 2.07

Main Menu - A

Copied RUU_signed.nbh from a shipped rom to C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\BaseROM

1) Dump ELF(in)'s ROM (*.nbh or *.nb or *imgfs.bin or *.raw)

I got now C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp these folders:

Packages

xip.bin

Xip

Launched Kitchen, moved C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp\Packages\OEM and SYS to C:\ELF(in)_Hybrid_Kitchen\Build_ROM

Moved C:\ELF(in)_Hybrid_Kitchen\Extract_ROM\Temp\xip to C:\ELF(in)_Hybrid_Kitchen\Build_ROM\ROM

Go back to Main Menu, C, than BuildOS - Load Rom...

The problem that in Packages to insert in ROM i've an empty list... what's wrong? :(

Thanks

Fabio
[Touch GSM ROM Development] Shreyas:
Custom rom for Asus P527??

I know its a wrong place to ask this question, but do u have any idea where i can find custom roms for Asus P527 mobile? If u dont mind can u plz reply me with the info in this id shreyasjagadeesh@hotmail.com

Thanks in advance
[Touch GSM ROM Development] dsixda:
Try this subforum -

http://xdaforums.com/forumdisplay.php?f=259

I saw one for the P525.
[Touch GSM ROM Development] bijugv:
infected by virus!

Hi

Can anyone share the Elf(in) Hybrid kitchen files. The one here is infected by viruses.

:eek:
[Touch GSM ROM Development] bububang:
I have a problem.. when i trying to cook a shipped rom "RUU_Elfin_hTC_Asia_WWE_3.07.707.02_4.1.13.71_03.34.90_BLUE_Ship"

the file that generated in "Temp" folder is

1.dump(folder)

2.XIP(folder)

3.dump_MemoryMap(text file)

4.xip(bin)

What wrong that i did?
[Touch GSM ROM Development] humrod:
Hello again, in this case I'm trying to reloc the 5.2.2500 WM6.5 sys, but get an error "Integrer Overflow".

To experiment I insert the CHome packages in sys but get the same error

Where is the problem?
[Touch GSM ROM Development] fcukmayank:
i have made a custom rom

but it is stuck at smart mobility screen

i have placed the boot.rgu at xip and sys

were i am going wrong
[Touch GSM ROM Development] fcukmayank:
just bumping so dat i can find a solution
[Touch GSM ROM Development] dsixda:
If you respond right away to your original post then people will just decide to ignore you. People have busy lives, and it is also Easter break this weekend. They will reply eventually, so have patience.

Anyways, from my cooking experience, there are 3 reasons for a device being stuck at splash screen after flashing a self-cooked ROM:

Reason 1)

Your XIP is totally messed up. It looks like this is what you did. Make sure the OEMXIPKernel folder is the correct one for Elf and not for any other device - this folder gets re-used for your Elf whenever you cook a new XIP version; only the MSXIPKernel changes per new build. People already posted the Elf XIPs for 21040/21041 in this forum, so that could help you.

Reason 2)

Your custom registry settings were defined under registry folders that were not defined before.

e.g.

You may have an entry like this:

[HKEY_LOCAL_MACHINE\Software\Crap\Newb]
"YouSuck"=dword:00000001

The problem above is that the "Crap" subkey (or registry subfolder) was never defined earlier, so your device will most likely hang at the splash screen after flashing.

This is the safest way to define a value:

[HKEY_LOCAL_MACHINE\Software]
[HKEY_LOCAL_MACHINE\Software\Crap]
[HKEY_LOCAL_MACHINE\Software\Crap\Newb]
"YouSuck"=dword:00000001

Note that I defined the Crap folder before defining the Newb one.

Reason 3)

When you create a new OEM from a CAB using Ervius' Package Builder, you might need to enable the option for 'Prefix files for duplicate in package subfolders'. For example, when I added a new OEM for Esmertec Jbed, I didn't enable that option (I normally don't enable it for my OEMs), and then the device hanged at reboot. So after enabling this and flashing again, all was fine. This doesn't apply to all OEMs that are created, however. There is probably a reason for this, however, but I am too lazy to find out why.

Perhaps the best and easiest kitchen to use right now is Bepe's Platform Rebuilder kitchen, which Kokotas posted in the 2nd post. You can also visit www.darkforecesteam.com and view the tutorials on how to extract a XIP with his kitchen. There is no need to port SYS; this kitchen does everything automatically.

Anyways I hope this helps. Also, please don't PM me repeatedly regarding this question, I was out all day so I don't sit at a computer 24/7. Just post to the Cooking Class thread, but I advise you CAREFULLY read all the tutorials in that thread before asking a question. That is how I started.
[Touch GSM ROM Development] pkoper:
Using G'reloc may be the problem, try WM'Reloc
[Touch GSM ROM Development] humrod:
Thanks for your answer, i'm using it now
[Touch GSM ROM Development] Ameet:
Hey pk.. Long time buddy :) Can you post this WM'Reloc? Cant find it anywhere :( Heard its better than G'Reloc
[Touch GSM ROM Development] humrod:
Here is it. You have to put the g'reloc file in build and the wmreloc in bluid/tools and that's all
[Touch GSM ROM Development] fcukmayank:
hey humrod bro

is it working for u now???

i m using xip 20924 and sys 21220

is this combination correct

i repalce the .vm and .rom folders from my working sys to the new sys

i don't include a wincell folder coz its already there

but still it is stuck at smart mobility screen wid the green led blinking

can anyone tell me where i am going wrong

i m using the sys posted in the nike section
[Touch GSM ROM Development] humrod:
When this happens to me, in 99% is about the xip. Why you use a diferent xip/sys?

You can do that, but is't easy to work with the same xip/sys.

About the wmreloc i'm using it when work on wm6.5 sys. For the wm6.1 roms the g'reloc it's ok.

Follow this steps:

1º use a working sys/oem with the new xip. if boot

2º add the new sys. if doesn't boot, look for a miss/mistake in the sys rgu's

Of course, better if use a cleanest oem (i think all the cookers have one for this)
[Touch GSM ROM Development] fcukmayank:
ya man its working now

thankx
[Touch GSM ROM Development] + Que PPC:
Hi all...!

Nice work here... this kitchen is easier to follow even for a jerk like me... :)

And the process to basics is so good, I understand all the steps (basics)

when i try to load the rom in buildRom form ervius it doesnt shows nothing to set or disable... I use the full shipped rom 6.1 that I found on the first sticky here on elf forum... I have an elfin and cause i cant see any packages to set or disable i just push the play button and there it goes.... it finish and at the end says everything seems to be fine PP to 12 MB for elfin and 8 for elf... last ruu signed file is near 83MB Am I ready to upgrade it..? im on HSPL 3.10.cmon.

(forget about it... i just need to know if the optionxml into the packages is the file that allows to set or not in bepe's build OS every package...) i must to read in other threads to learn on how a cab or how an OEM package works)

Sorry if I heard like an idiot its just that I was playing arround with many devices but when I starts to learn the cooking art i lost my devices... ( hope it dont happens again tomorrow :) )this is my first attempt on dump and redo the os... well the kitchen does everything... thanks in avdance :cool: im so excited!!! jajaja

Where can i get the last build for 6.5? if I had it, and download the WMreloc, put it into the tools folder and try to dump and build the rom... may I start to learn on how to change the packages I want to use, edit initflash files and many other things? i think I need to start with 6.1 :p

Thanks for all, i only read to the page 7 or 8 but its late i need to sleep Im an accountant and the numbers gives me a headache if i dont sleep fine.
[Touch GSM ROM Development] kancrutt:
today i walk around in Prophet6, and found biggest Memory RAM

why ELF just have free memory RAM about 20mb?
[Touch GSM ROM Development] Nixeus:
Hi,

Please help me my friend :)

I have cook a lot of wm6.1 rom whithout problem.

When i cook wm6.5 rom, my elf don't boot :( :(

Have you and idea ?

I use the .rom, .vm and wincelens folder issue to my working wm6.1 rom !

Anyone could share a kitchen with sys,rom,and oem folder in wm6.5 ?It's not to publish a rom, but just in order to understand why my rom don't boot !

It will be very nice to you,

Thanks a lot,

regards,

Nixeus