yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] !Aman!:
i've another method for u guys to change the PP. search the 03 15 A0 03 02 15 A0 13 00 10 83 E5 62 C2 FF EB in yours S000 of nk.exe and change the string marked in Red color to 00 00 A0 E1. from there onwards u can simply use the old Multi-platform PP changer.exe (that is also found in kaiser kitchen) to change ur PP on the OS.nb. this should make the kitchen even simpler :D

PS: this method works regardless of the device.
[Touch GSM ROM Development] VJstar:
Thx bro.I just do it... i uesd xip.bin all of for 3.10 Aus rom this time,i find 0x045210 and 0x045214 ..hehe.... but cht 3.07 why not ?

but i find new question this time.. i lost 3rd sceen pitcure and themes... i think xip have problem.... who can tell me why? i just remove hd.dll osaxst0.dll mencfilt.dll and boot_ms.rgu
[Touch GSM ROM Development] !Aman!:
if the device goes past the main splash screeen then xip doesn't have a problem. also u can remove those modules (hd.dll etc) without a problem.
[Touch GSM ROM Development] VJstar:
I forgot that I was the third screen into the theme of oem to use. Perhaps the problem could appear in the paper dsm.

the dsm is empty...dsm document is not associated with any documents
[Touch GSM ROM Development] VJstar:
I found the problem, when I use all_packages_to_one, the occurrence of such a loss. :confused::confused:

TOOLS\all_packages_to_one > nul

del buildpkg.wrn > nul
[Touch GSM ROM Development] !Aman!:
which kitchen did u use? Ervius' or Bepe's?
[Touch GSM ROM Development] VJstar:
bepe's .... help me fixed this. I have already met twice, very confused. This is the first 19972 is 20931

. Never happened before :confused:
[Touch GSM ROM Development] !Aman!:
interesting... i faced this problem at few times with Ervius' kitchen so i started using bepe's where i didnt face this issue. try Ervius' kitchen then, it is surely related to some dsms.
[Touch GSM ROM Development] VJstar:
I am grateful that you reply, I await your amendments. In any case, very grateful :D
[Touch GSM ROM Development] VJstar:
I am very sure that the problem here. But how are we to do? Dsm for a unified standard or re-improvement tools all in one? :eek:

PS: I repeated the test more than ten times more than the results obtained :D
[Touch GSM ROM Development] !Aman!:
try Ervius' kitchen without using All_packages_to_one.exe tool or try with empty dsms in the OEM folders.
[Touch GSM ROM Development] VJstar:
yes.. i just do this..i'm done. used bepe's kitchen is same..don't used all in one it's okay. :D
[Touch GSM ROM Development] kokotas:
Bro, I think I'm going crazy...

When I did the above change in nk.exe, the results were:

1.The Multi-platform PP changer(tried v2.1 & v2.21) didn't work.It recognized my pp as 2MB eventhough it was 12MB.

2.The ROM that was built with this nk.exe had a very strange behavior:

Available RAM was 118MB(!) and the pp size could not be changed!

Tried to make it (pp size) 0MB & 8MB but the RAM was always 118MB!

Actually, this is cool cause the free RAM was very high too(~97MB!) but I just wonder what the f#$% happened?:D

Regards!
[Touch GSM ROM Development] !Aman!:
that is the expected behaviour :D

after u change that particular HEX string (mentioned in RED), the HEX string (03 15 A0 etc etc) that we have been using till date becomes ineffective and changing the PP at those offsets is useless. PP changer works as it should i.e. 2 MBs PP for Elf as well as Elfin :D. hope its clear now ;)
[Touch GSM ROM Development] kokotas:
Thanx for the explanation bro:D

I understand now what's happened!

Very clever!
[Touch GSM ROM Development] !Aman!:
hehe, so i think u can introduce the PP changer in the kitchen at the end of the creation of OS.nb so that users can modify the PP. if people don't want to edit the hex string in the nk.exe, then there is another option. that string can also be edited after os.nb is created, followed by the PP changer ;)
[Touch GSM ROM Development] Demo[95]:
Best idea, i've ever heard :D
[Touch GSM ROM Development] !Aman!:
hehe, thanks :D.. but its upto the Kitchen owner and also upto the users.
[Touch GSM ROM Development] trueg:
kokotas, is there possibly a problem with Hybrid Kitchen and SD Encryption? I just noticed a few hours ago that all of my ROMs based on 3.10.710.0 had an error in SD Encryption were it would be enabled by default and could not be disabled.

The error existed in my original dump that I did with Hybrid Kitchen. I did a search and there are other Kitchens that had the same problem.

Anybody else have this problem with 1.4.3?
[Touch GSM ROM Development] VJstar:
There is no problem, it's your own mistakes. If you xip in mencfilt.dll and boot_MS.rgu deleted. The result is that you like that. This module is the function. Hybird_kitchen is the default. The first page is described in detail

:D:D
[Touch GSM ROM Development] kokotas:
Notes

Ref_XIP_OUT & Ref_XIP folders inside Prepare_XIP are the latest 3.10ROM's XIP, but modified as follows:

-removed modules:

cachefilt.dll, hd.dll, mencfilt.dll, osaxst0.dll

-removed files:

boot_ms.rgu, bmui.nb0

-edited files:

boot.hv, boot.rgu,

REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\CacheFilt]
"Dll"="CacheFilt.dll"
"Order"=dword:2

[-HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\CacheFilt]
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\LsFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"

723fb954-d931-4348-b672-82a188e587b5.rgu

REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\ENCFilt]
"EncryptByDefault"=dword:0

-edited modules:

nk.exe

RTC is enabled

-ALL MSXIPKernel modules are relocated to achieve better XIPPorting

If you include LockStreamDRM PACKAGE in your ROM and you use the Ref_XIP as your \ROM\XIP(folder), add the removed (from boot.rgu) entries

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\LsFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"

in the PACKAGE's *.rgu.

If you are building your ROM with option 1 you need:

ROM\xip_out.bin ,

ROM\XIP\boot.rgu(ONLY) and

ROM\OS.nb.payload

This option doesn't build the xip_out.bin(buildxip.exe is not used).

You must build your xip_out.bin with XIPPort before starting building OS.

So you should select this option ONLY IF you used option 1 in XIPPorting (or IF you decided to use a dumped ELFIN xip.bin as xip_out.bin and the dumped boot.rgu too).

If you are building your ROM with option 2(or even just run the PkgToolsBuildos-4.3b1) you need:

ROM\XIP(ALL FILES and MODULES) ,

ROM\romhdr.bin and

ROM\OS.nb.payload

This option builds the out.bin(buildxip.exe is used)from the XIP(folder).

You could create your XIP(folder) with dumprom etc..

So you should select this option ONLY IF you used option 2 in XIPPorting (or IF you decided to use a dumped ELFIN XIP(folder)).

Easy(advisable) way to cook is option 2 in XIPPorting & Ervius PkgToolsBuildos! (Don't get confused with the other option)

PP Patching is included in the kitchen operation!

You just set your favorite pp size at the beginning(installing) and each Rom you build is already patched!

If you make the following hex change in nk.exe's S000

then the kitchen's PP Patching doesn't work!

You should use the suggested by Aman Multi-platform PP changer v2.21!

Finally, I don't have an ELF to test, but after the above change then I think that the pp size is the same for both ELF&ELFIN(not dynamic).

EDIT:Multi-platform PP changer v2.21 included in the kitchen and reuploaded today..

Regards!
[Touch GSM ROM Development] trueg:
OK, that was a lot of information to take in, but basically my problems arose because I used my dumped XIP.bin as XIP_out.bin. Since the dumped XIP.bin contains all of the SD Encryption crap, it was included in my ROM. It would have been removed had I ran XIPPort.

I'm guessing then that there is a problem cooking SD Encryption since it was corrupted in the dumping/cooking process?

I included LockstreamDRM in my ROM, mostly because it was in the original and I assumed I needed it. I need to add that bit of code to boot.rgu for it to work correctly? Can I just remove it? What does it do?

EDIT: I just checked my boot.rgu and all of the lockstream code is still there, I assume because I am using the dumped boot.rgu.
[Touch GSM ROM Development] trueg:
Could the problem I had with being unable to change sound and notifications and then getting stuck in the application be related to using the default kitchen boot.rgu and LockStreamDRM without adding the LockStreamDRM registry entries to boot.rgu?
[Touch GSM ROM Development] dsixda:
Hey, if you cook a 2.xx ROM with the new 3.xx OS.nb.payload AND with ULDR removed, is it going to work properly after a flash?

Also, I heard that Koko's kitchen has a new payload of only 29MB?? How'd you do that? I am using the OS.nb.payload from the 3.07 Indian WWE, which is over 100MB!
[Touch GSM ROM Development] kokotas:
Possible!

I think I did tell you to replace the boot.rgu with the dumped one;)

Generally speaking,

yes it will work!

I consider the payload as an (elastic) shell in which you "put" your files..

If you cook a ROM with OEMXIPKERNEL from a 2.xx ROM in this kitchen(1.4.3) then it won't work, cause the pp patching will alter the wrong offset and you'll end up with nonbootable device.

UNLESS you edit the bat files in order to target the right offset, so it will be ok!

I recooked the payload, removed ULDR & reduced the xip available part.

Check change log bro;)

Regards!
[Touch GSM ROM Development] dsixda:
Damn! I didn't see that.. ;)

Also, would you guys say that XIP has a lot to do with memory leaks, or would SYS be more directly responsible (if you ignore OEMs)?
[Touch GSM ROM Development] trueg:
Exactly, by using the dumped one, all of the LockStreamDRM entries were put back in which corrected the sounds and notification problem.

Currently, I am trying to build a stock 3.10.710.0. I'm using my dumped OEM and SYS and then your Ref_XIP as the XIP. I added the LockStreamDRM registry entries back into boot.rgu and used option 2 (PkgToolsBuildos) to build a ROM which in turn creates out.bin.

I renamed out.bin to xip_out.bin and then ran option 1 to create a ROM for testing.

Everything flashed fine. Changing notifications worked (I assume because LockStreamDRM is working now).

Problem: Encryption under settings is checked! How can this be? I don't believe it is actually working since mencfilt.dll doesn't exist and I don't see a menclog file on my SD card, but the option is checked and can not be unchecked.
[Touch GSM ROM Development] kokotas:
That's a good question...

I didn't think of it till now. Well my vote (without being an expert) goes to SYS(&OEM)

cause the files in XIP do not require to be copied into ram before execution..

I hope someone has a more clear view of this:)

Since you used the Ref_XIP for XIP then the mencfilt.dll is not present, so this

control panel item is not really working(as you correctly said)!

Just hide it from your Settings and it will be ok:)

Oh! You could also remove DeviceEncryptionPolicy.dll from the Shell folder..

Regards!
[Touch GSM ROM Development] trueg:
If DeviceEncryptionPolicy is only used for SD Encryption and I'm not using it, I might as well get rid of it. Are there any registry entries tied to it that can also be removed?

Edit: even removing DeviceEncyptionPolicy.dll doesn't fix the fact that Encryption is checked. It's strange because last night when I first realized this encryption problem, all I had to do was delete mencfilt.dll and boot_ms.rgu and then I couldn't enable it. These files are indeed missing from Ref_XIP but it still gets checked. As long as it is not working, I guess I will just hide the control panel and assume I am safe.
[Touch GSM ROM Development] kokotas:
There are some reg_entries in SYS that should be removed too, but I don't remember which *.rgu...

Well, search your SYS *.rgus and when you see something like:

[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\ENCFilt]

remove it.

Edit: Try Shell,BaseApps,OS

As long as it is not working, you are "safe".

Happy Cooking;)!
[Touch GSM ROM Development] trueg:
How about this one?

[HKEY_LOCAL_MACHINE\Comm\Security\SDP\BootFunctions\DeviceEncryptionPolicy]

"Dll"="MencFilt.dll"

"DllEntryPoint"="LoadEncryptionPolicy"

"Order"=dword:20000

Note: both this and the entry you mention are in \OS\*.rgu
[Touch GSM ROM Development] kokotas:
Yes!

You got it!

You removed the file=>time to clean up your Registry too:D
[Touch GSM ROM Development] humrod:
Hi kokotas. I'm learning about your kitchen. I port a coredll.dll and it updated suscesfully, but appear a message: run createxip.exe and insert.exe.

The question is: i cant localize the createxip.exe.

the insert.exe is in tools folder.
[Touch GSM ROM Development] Ameet:
Actually this problem is mostly related to the physical ringtone present in the ROM. If you have removed the Ring_Windows (or something) .wma file then you get stuck in the Sound & Notifications tab and not able to change the sounds

Sorry if this is already answered
[Touch GSM ROM Development] trueg:
I wanted to find out why Encryption gets checked when I use the Ref_XIP and not when I use my dumped one with mencfilt.dll and boot_ms.rgu deleted. The key is...

723fb954-d931-4348-b672-82a188e587b5.rgu

REMOVED ENTRIES:
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\ENCFilt]
"EncryptByDefault"=dword:0

Once you delete this from the registry, Encryption gets checked and can not be unchecked. If mencfilt.dll is deleted, then it doesn't really matter, but I was glad to understand why this was happening.
[Touch GSM ROM Development] trueg:
In my case, no ringtones were deleted. It can be re-created easily. Simply remove the LockStreamDRM registry entries from boot.rgu and include LockStreamDRM in your ROM and you will run into a situation where it 'locks' up when you enter sounds & notifications. Either don't include LockStreamDRM in your OEM or ensure the registry entries are included in boot.rgu.
[Touch GSM ROM Development] kokotas:
If anyone is interested in trying something for me, here you go:

Hybrid Kitchen v2.0.0

Let me know if you find this setup more fast-easy2use than the previous..

Regards!
[Touch GSM ROM Development] VJstar:
I do not want to put it on the C disk, would like to put any letter, how do I do? :D

I changed the path of all but it's not working... :confused:

Can not be in the running for the first time on the path to personalized settings? :D
[Touch GSM ROM Development] kwbr:
Hi Kokotas, what has changed in the new version?
[Touch GSM ROM Development] kokotas:
The requirement for the kitchen to work is to "install" it directly to the drive where your windows are installed(systemdrive).

If your windows are in D drive , then place the kitchen in D drive.

If your windows are in E drive , then place the kitchen in E drive.

...

If you want to put it in another drive(not where your OS is)you have to edit EVERY batch file(including First_Run_For_ELF(in)_Hybrid_Kitchen.bat)&replace %systemdrive% with the drive's letter.

Regarding the cooking process,the only change is that I included the autopather by cmonex for the removal of sign/cert checking.

But I changed a lot the structure&the access of the kitchen!

Check changelog too.

Regards!
[Touch GSM ROM Development] jonbus:
Little problem

Hi everybody, i have a little "issue" here...

I build a rom using this wonderful Kitchen, and i wnated to update it and i took the generated nbh and try to dump it but it doesn´t create OEM ans SYS folders....neither this kitchen or any other or the PKGTool by itself....

Why could be that? any solution? unfortunately i did not save the base OEM and SYS folders....

Thanks in advance
[Touch GSM ROM Development] trueg:
If you cook using Bepe's BuildOS the resulting ROM will not be dumpable. You need to cook with Ervius PkgToolsBuildOS in order to have a dumpable ROM.
[Touch GSM ROM Development] jonbus:
that´s what i suspected....

Thanx Trueg!
[Touch GSM ROM Development] chihliouma:
I see. but what I am wondering if there is any other tool than PKGTOOLS that can be used to dump ROM cook by using Bepe's BuildOS ? Thanks.
[Touch GSM ROM Development] trueg:
No I don't believe so. The information needed to separate the packages is simply not included in the final ROM when built with bepe's BuildOS.
[Touch GSM ROM Development] trueg:
I don't know, I haven't used Hypercore in a long time. I just know that using option 1 in Hybrid Kitchen creates a ROM that can not be dumped (and have the packages separated into OEM & SYS). Option 2 seems to work fine for me. ROMs made with option 2 dump fine for me. They are also a few MB larger.
[Touch GSM ROM Development] !Aman!:
Bepe's kitchen is based on all_packages_to_one.exe, which removes all the rgu's, dsm's etc from the ROM and thus makes it undumpable :)

hypercore doesn't work on that principle.
[Touch GSM ROM Development] kokotas:
Sorry for that one!When I realized that I forgot that "&" in the batch, I reuploaded the kitchen!

I just wasn't fast enough...but it's good that you found that mistake&corrected it by yourself!

Regards!
[Touch GSM ROM Development] jonbus:
Thanx Htctouchp! but when does it stores the registry? in the hives (default and user)?

Ok Kokotas! thank you....

One more thing, may i have your permission to translate your kitchen to spanish? and use it in a cooking tutorial i´m planning to do?

Thanx Master!
[Touch GSM ROM Development] kokotas:
Hi jonbus!

You're correct! The registry settings are "stored" in the hives (rgucomp builds the *.hv from all the *.rgus) .

so go ahead and make this kitchen in spanish.It's not that I have a copyright or something:Dhehehe:D

Regards!
[Touch GSM ROM Development] aflika:
Please help

Rom edit problems

Help please! :(:(:(
[Touch GSM ROM Development] kokotas:
Hey man!

I can't understand what the error is about, but if you follow the instructions in 1st post then there shouldn't be a problem!

Plus have in mind that this is a WWE kitchen tested on WWE Windows.

Regards!
[Touch GSM ROM Development] aflika:
thanks... I'm sorry I'm bad english
[Touch GSM ROM Development] trueg:
Is this automatic when using Bepe's BuildOS? I just starting using Raphael ROM Kitchen and even when using what appears to be Bepe's BuildOS I get all of my OEM rgus in my Windows folder. Would that kitchen need to use rgucomp in order to get the same results as option 1 in your kitchen?
[Touch GSM ROM Development] Demo[95]:
I think it's TOOLS\all_packages_to_one.exe that produce this behavior.

Kind regards.
[Touch GSM ROM Development] lokura:
It is embarrassing how easy it is :o , a verry good job

thanks for your kitchen, i finally have my own rom cooked and working in my elfin

really a few changes, (removed sqm and .net 2, and added .net 3.5, remote tracker and security_off) but is a good begin for me

the pity is that infamous butterfinger efect on lattest oficial roms, any chance to solve this?
[Touch GSM ROM Development] kokotas:
v2.0.7 @ 1st post is up!

New version. Less confusing. Probably the Final.

Cause there is something new and better ;) ...

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

If anyone is interested here it is. Mostly as an example!

Regards!
[Touch GSM ROM Development] aflika:
thanks

thank you kokotas
[Touch GSM ROM Development] humrod:
Hi Kokotas, I'm trying to cook a spanish rom on the kitchen, but it doesn't boot. I make tha translation on Neokit and works fine. Is possible that i need to change somethings on the kitchen to work in 0C0A system lang? or it is indiferent?

Tell you what i did: Tried to make the translation in you kitchen as usual, bu don't boot. Starting with the same OS.nb, work on the other kitchen, and works fine. The problem is that kitchen doesn't keep the SYS/OEM structure.

I took the OS.NB from that kitchen and dump with your kitchen, fix the missing files and bluid: Doesn't work.

Can you give me some clue?

Thanks in advance
[Touch GSM ROM Development] kokotas:
Hey humrod!

I don't find something wrong in what you did, so it is a bit strange that the rom doesn't boot:confused:

Well, the truth is that I've been using this kitchen to build WWE roms ONLY.

I am going to try something different and

dump a non english rom

rebuilt it

flash it

and see what happens...

I haven't heard about the Neokit kitchen, so when I saw your post I searched for it and this is what I found:

NeoKit easy2use rom cook/modding tool

Is this what you used(but with some modifications)?

Regards!
[Touch GSM ROM Development] humrod:
Yes my friend....That's what I use..

I learn about it since i was on Prophet...!What a surprise¡ it works on elfin

It's not complete (about a elfin I mean) cause is not made for all devices, but you can dump an OS.nb and obtain an OS.nb

Just it don't manage the SYS/OEM system, but it's really powerfull.

If you found something about the lang i?ll be waiting
[Touch GSM ROM Development] Demo[95]:
Kokotas, Humrod,

I don't think it's related with the kitchen, as i'm currently using this kitchen for my WWE, FR and ITA Rom...
[Touch GSM ROM Development] kokotas:
Update on Lang Issue

Here is what I tried in detail:

1. I went and got myself a foreign Rom

2. Dumped it

3. Moved OEM & SYS to \Build_ROM and XIP to \ROM

4. Started PkgToolsBuildos and rebuilt it with no modifications

5. Flashed it ===> NO BOOT!

6. :confused: for a couple of minutes:D

What I did to solve this:

1. Renamed the OS.nb from the Rom I dumped (OS.n inside \Extract_ROM\BaseROM) to OS.nb.payload and moved it to \ROM overwriting the old one.

2. Went into \Build_ROM\TOOLS and edited the CREATE_ROM_For_ELF.bat:

Replaced the line

..\TOOLS\msflshtool OS.nb.payload -r ..\ROM\out.bin -p 0

with

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

and removed this one

goto :pppatch

SO you should try and edit the CREATE_ROM_For_ELF.bat @ those lines having in mind that insert.exe takes the following parameters:

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

If you need to find the Destination address [-d] in your OS.nb.payload 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.Note the address for the first byte "FE" and use it in insert command for -d <hex> parameter.

(If you find it twice, then the second address is the one we need)

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>

Hope this helps a bit...

Regards!
[Touch GSM ROM Development] humrod:
I start using as base the Asia_3.07.720.03_4.1.13.71_03.34.90_BLUE_Ship

Ok: I edit the Create_ROM_For_Elf.BAT

But the secuence FE 03 00 EA 00 00 00 00 is one time only....
[Touch GSM ROM Development] !Aman!:
did u remove the ULDR partition? if yes, then thats the reason it is only once.
[Touch GSM ROM Development] humrod:
No I don't remove it. I use the rom as is published here in the forum

But thinking in the coments of kokotas: I dump the RUU_signed.nbh andthen change the 0409 lng files for the 0C0A lang files from Diamond, adjust the Initflashfiles and some registry keys, like the mui and the nui.

I don't change the XIP (it was dumped from the same rom)