yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] cmiguelzeferino:
Hi... Sorry but I read all your posts here and did all what is here and I still can't load the rom to my kitchen... See the error I got... I will like a litle help please... Thanks in advance...
[Windows Mobile] BesFen:
Hi All,

I read the first page and it said that the kitchen support for GENE also.

Can someone confirm it??

Thanks.
[Windows Mobile] airxtreme:
I don't think anybody has tried Gene support yet but if it works with ervius kitchen without changes it should work fine.
[Windows Mobile] twisted:
hi,

is it possible to upload the latest kitchen in this thread. all network storage are blocked at work. i just wanna try this new kitchen while i'm idle at the moment. thanks very much for this update.

regards,

mike :D
[Windows Mobile] qball1616:
Ok I can successfully dump the stock Sprint MR1 ROM. Have made several builds and none of them are getting past the initial HTC screen. WinCE is included in the SYS, and I am letting the kitchen recmod the 3 packages it suggests (Audio Booster, Notification Enhancement, and Concurrence Manager).

I can build this exact ROM with v 1.25 with and it boots with no problems however with 1.26RC1 it just stays at the initial screen with the red writing in the bottom left....any ideas what I could be doing wrong?

I verified in the build log that the packages were recmodded.

any suggestions would be great!

BTW I love your kitchen! I liked 1.25 (and all the versions leading up to it), but I absolutely love the new version now I just have to get a bootable ROM
[Windows Mobile] cac2us:
Latest Kitchen

Can you access 4Shared?

OOPS:

Post #1491. v1.26TEST3.
[Windows Mobile] airxtreme:
RC1 is out on the first post
[Windows Mobile] cac2us:
i910 support?

Thanks,

I will try that for my HTC6800's & XV6900.

Any thoughts about support for i910?

The new UI is much nicer.
[Windows Mobile] qball1616:
Ok must be one of my packages causing the issue...I just rebuilt the stock ROM that I dumped and was able to flash successfully. So I am guessing it is either a package or the fact that I spinlocked patched the OEM drivers or possibly that I have included DummySQM and DummyFWUPDATE. Trying a build now without spinlock patching and including SQM from the SYS
[Windows Mobile] airxtreme:
I can't support the i910 because libnb can't yet unpack its files correctly.
[Windows Mobile] qball1616:
none of those fixed it any ideas on how going about figuring out what package it would be, or could there be something in the SYS causing it not to boot? I have used this SYS in an older vesrsion (1.25) with no problems.
[Windows Mobile] airxtreme:
If the SYS is the original one from the ROM most likely not.
[Windows Mobile] mari8b:
Porting from another kichten

So there's no possibility to port from another kitchen (e.g. bepe's) w/o importing a stock ROM?

Which configuration files need to be generated?
[Windows Mobile] airxtreme:
Two XML files for libnb and one for the kitchen. Messing with the libnb files can mean permanently bricking the device so I strongly discourage it. Downloading and importing a stock rom takes only a couple of minutes (http://shipped-roms.com/ is full of stock and updated ROMs) since the kitchen can directly import the EXE updaters without even having to get the NBH out of them.
[Windows Mobile] mari8b:
I know that. No problem. I just won't import crap from the stock ROM.

I'm a noob, not a experienced cooker. I don't know what for are these files:

.ROM

.VM

imgfs-template.bin

os.nb.payload

romhdr.bin

Do I need them all? Or only some of them?

I understand, that I need these:

Device Informations.xml

NBH Structure.xml

OS Structure.xml

Thanks for you patience...
[Windows Mobile] airxtreme:
You need all the file except the payload that shouldn't be there at all. If you import a stock ROM all you would have to replace is OEM, EXT, OEMXIPKernel and the WM build folder, it only take a few seconds.
[Windows Mobile] BeeGee_Tokyo:
Testing V1.26RC1 rev2

Nice new kitchen.

First feedback:

A)

B)

C)

D)

Can you check this? Do you need any log file?

Small request, when starting the "Run before" and "Run after", can you give parameters like ROM build, device, date, version to the program?

I love to have the created ROMs named and categorized by build, cook date and ROM version. In EVK I could get this from within the bat file.
[Windows Mobile] ultrashot:
Great kitchen!

Found a little bug. If you select multiple packages, "delete package" option doesn't work.
[Windows Mobile] SimpTheChimp:
Airxtreme,

What if I already have my OEM folder(s) all set up from a previous version of your kitchen (1.25)? So I am not going to need to have the new version of the kitchen 'explode' an .exe installer. Can I then use the new RC1 kitchen to build an i910 ROM? All I want to do is copy my source stuff from the old 1.25 kitchen to the new 1.26 kitchen (in the appropriate folders, of course).

If I do this can the new kitchen build an i910 ROM like the old 1.25 did?

/Chimp
[Windows Mobile] airxtreme:
Fixed

That was a LibNB limitation but I've fixed it with another temp folder.

Fixed

Fixed

With the RC2 I've just released you now have 4 environment variables that you can use in your batch files: %ROM_Windows_Mobile_Build% %ROM_Device% %ROM_Version% %ROM_Date% %ROM_LCID%

You can use the same variables in the ROMFileTemplate parameter of the "Device Informations.xml" file. Since the file template can also include subdirectories if you only needed batch files for sorting the ROMs you can do that directly in there.
[Windows Mobile] airxtreme:
That's wasn't actually a bug but laziness to avoid having to parse all the selected packages but now it should work even with multiple packages.
[Windows Mobile] airxtreme:
As written in the first post the kitchen for now supports only HTC phones. Until Da_G fixed dumping of NB0 files with reserved regions adding Samsung phone support back would mean having to redo all the code with the old tools and that would be a lot of time wasted.
[Windows Mobile] imzkng:
I am having trouble with the new kitchen version and my GSM Palm Treo Pro. I have 1.25 working great. I have imported the same rom that works with the old version. It seems to import fine. I have tried rebuilding a rom from the import, and also building from a newer 6.5.x with no success. The process goes all the way through, and it says the rom has been built, but the Palm Treo Pro Output folder is always empty.....what the heck am I missing or doing wrong?!
[Windows Mobile] airxtreme:
You should enable the tools log to see if any tool is failing. Also please link me the ROM you used so I can test it.
[Windows Mobile] af974:
Im testing cooked roms with both 1.26 and 1.25...well

A fully light Kaiser build.

Same packages on both sides.

1.25 result:

Nbh output 40.2 mb.

Total storage memory available 168.65 mb.

1.26 result:

nbh output 43.8 mb.

Total storage memory available 135.00 mb :eek:

It is something related with TemporaryOs.nb or i need to set something?

PS: i checked packages and tools 3 times.
[Windows Mobile] airxtreme:
Can you please try dumping the old and new rom (with nbimagetool and xidump) and use winmerge to compare the files inside? Also please compare the folder size to see if it explains the difference in available space.
[Windows Mobile] af974:
Ok, attached to this post.

Main difference that i found are content of default.hv,user.hv,a dsm...made with Beyond Compare.

Missing boot_ms.rgu in XIP from xidump but there is it in Kitchen Folder.
[Windows Mobile] af974:
Ok i solved it....i was right, fault was of TemporaryOs.nb i changed it and now it works fine.
[Windows Mobile] airxtreme:
How could that happen? The temporary os.nb is supposed to be an exact copy of the original os.nb
[Windows Mobile] af974:
really dunno but i had TemporaryOs.nb from the stock rom dump size about 83 mb,i replaced it with a new one of 40 mb and i had a slim nbh with my total available storage size back of 169 mb.

There is a way to decrease it much more?

Sorry,last question, this new kitchen is patching the shell aswell like the old one?

Thanks.
[Windows Mobile] magawa:
Omnia i900 ??

why you didn't import a method for omnia in 1.26

1.25 works perfectly
[Windows Mobile] dcelluser:
Remove Default IE Favorites

I have a suggestion. Please add a option in the customization section to remove default IE favorites. Would be nice if I didn't have to delete these 2 files everytime I imported a SYS:

browsingie\mxip_wpclang_favorites_1000.provxml

browsingie\mxip_wpclang_favorites_1001.provxml

Thought this might be handy to others...

Thanks and keep up the excellent work!
[Windows Mobile] Mikolaj612:
The wince.nls is not presented in the build XIP, whats going on ? In 1.25 I never had this error.
[Windows Mobile] shark147:
Hi Airxtreme,

Yestarday, i have try add radio rom in new kitchen v1.26RC2 but when i add NB file, this file write in splashscreen...

You can check this?

Thanks
[Windows Mobile] Badwolve1:
Testing RC2 version :)
[Windows Mobile] Badwolve1:
Yes! It made a booting ROM :D Nice work!!!

Is any of it still based on the original OSKitchen? #

Nice work :)
[Windows Mobile] malatest:
wince.nls is in folder WINCENLS_WWE in Common folder of SYS. In 1.25 was the same
[Windows Mobile] imzkng:
Here is the Rom I have been importing.

TreoPro GSM 6.1 Stock.7z
[Windows Mobile] BeeGee_Tokyo:
I did just this with my ROM. Ported (manually) all files from 1.25 kitchen to the new folder layout of 1.26 and first run brought up a working ROM.
[Windows Mobile] BeeGee_Tokyo:
Great! Downloading new RC2 and trying it tonite.
[Windows Mobile] airxtreme:
I think the reason of the difference is that the old kitchen was using implantxip to remove/reduce the uldr and that saved space. I'll see if the same can be done using osnbtool or I'll go back to implantxip for the xip insertion hoping it wasn't that was breaking the opal roms.

The code for shell patching is still present but I have never tried to see if it worked. If you're using a timebombed build just look at the log to see if there's anything written regarding patches.
[Windows Mobile] airxtreme:
As I already wrote several times the new kitchen does not support any Samsung phone yet.
[Windows Mobile] programatix:
Hi,

I'm getting a half mix unicode text in the final config.txt. Is there a way to overcome this?

Thanks.
[Windows Mobile] SimpTheChimp:
That is what I was thinking. I already have a DC22 OEM folder setup, so I don't need to have the new 1.26 version pull in and recreate the OEM stuff from a stock build. I just want to copy the old stuff from 1.25 and then use 1.26 to build the ROM.

Other than copying the old files to the new folder setup, anything else special you had to do?
[Windows Mobile] magawa:
I know But it will be nice if supports omnia i900000

Ok ...When will be the next ver. that supportس omnia ?

sorry bad english maybe ...
[Windows Mobile] airxtreme:
It's very weird, nbmerge crashes while rebuilding the rom, I'll have to do some other testing
[Windows Mobile] Xinot:
Builded some working ROM's for Topaz already, but what the **** is v1.26RC2 doing when it's "idling"? Cpu usage is almost 100% all the time if i open my project to it and do nothing... :confused:

Actually it jumps to 50% cpu usage if i just choose "open project" and cancel that... :rolleyes:
[Windows Mobile] airxtreme:
That is not normal at all. What is your OS?
[Windows Mobile] airxtreme:
I don't know because I was waiting for libnb to support samsung NB0 files before adding support for the Omnia but now that Da_G is busy with windows phone 7 I have no idea.
[Windows Mobile] magawa:
Thanks for replay and waiting you and da_g

Keep Nice work ffriend
[Windows Mobile] Xinot:
W7 Pro 64bit.

No problems with 1.25 and earlier builds.

Pic Click.
[Windows Mobile] airxtreme:
I really have no idea. I use W7 64bit too and I have no issues. If you didn't start any building process and the kitchen is on idle then it should use 0% cpu because it has no background processes working. It must be some apps or something you use that hangs to the kitchen and makes it go crazy because there is really no other probable explanation for the cpu usage while idling.
[Windows Mobile] Xinot:
Yep, cpu usage jumps to 50% as soon as i click "open project". If i'm only one with this, then it must be in my setup here. I'll try to figure this out. Thx.
[Windows Mobile] dcelluser:
I say try turning off you antivirus and see if it makes a difference. Some AV programs get confused when scanning 32 bit programs on 64 bit platforms.
[Windows Mobile] airxtreme:
Loading the config.txt file and saving it as unicode would certainly solve the problem but will that work with the htc autorun?
[Windows Mobile] imzkng:
Thanks for looking into it.
[Windows Mobile] programatix:
htc autorun could not recognize the unicode part. Opening the file in the device using pocket word will result in the same condition as the screenshot I've posted but the 0x00 byte char will be displayed as a box.
[Windows Mobile] airxtreme:
If you open config.txt and save it as unicode then when the kitchen appends stuff to it the output will be a completely unicode file. Try that to see if it works because I have to decide whether to merge the file in unicode or ascii but I think that unicode should work or it would be a mess on east asian phones.
[Windows Mobile] programatix:
I've been trying to save the main config.txt to unicode using notepad (save as) but the result still ASCII. Would it be better to detect whether it's unicode or ASCII and maintain it during config.txt generation?
[Windows Mobile] cac2us:
EDITPAD

Try This.

It works for me...
[Windows Mobile] airxtreme:
If the kernel is a native 6.5 the kitchen wouldn't recmod anything.
[Windows Mobile] Novek:
Thanks airxtreme

Even thought I haven't got an error while building a ROM with the concurr thingy, I'm now building a new one just like the last, but without that exact Package... I'll post if it helps or not...
[Windows Mobile] airxtreme:
The only difference between the old base kitchen folder and the new one is the HTCRT_devices.ini that in my one is updated. Maybe the new one has issues so if anybody is having problems with flashed roms please try looking if the values for your devices are identical to a htcrt_devices.ini used in another kitchen for your device that works.
[Windows Mobile] ivanmmj:
I have an even newer ini if you want it... I updated it myself before you released your updated version so you might need to merge some info.

Anyhoo, I hope you saw my post in the last page. :p

EDIT: Also, does the kitchen automatically run "bigstorage" for those devices that support it?
[Windows Mobile] Novek:
Streaming_SDK_2_7_19182725_00
Streaming_SDK_2_7_19182725_00_0414
TaskBarIconMgr_2_11_0_0
TaskBarIconMgr_2_11_0_0_0414
Teeter_2_0_19193924_00
Warning: Overwriting 'HTC_teeter.png'
Teeter_2_0_19193924_00_0414
Text_Selection_1_0_19202229_00
Text_Selection_1_0_19202229_00_0414
TimeZoneAutoFix_1_0_19203033_00
TimeZoneAutoFix_1_0_19203033_00_0414
USB_To_PC_Pop_Up_2_3_19192730_12
Warning: Overwriting 'HTC_usb_to_pc.png'
USB_To_PC_Pop_Up_2_3_19192730_12_0414
USSD_Service_4_35_0_0
USSD_Service_4_35_0_0_0414
VBookmarkMgr_1_0_19202626_00
VBookmarkMgr_1_0_19202626_00_0414
Voice_Recorder_1_10_19193928_2
Warning: Overwriting 'HTC_voice_recorder.png'
Voice_Recorder_1_10_19193928_2_0414
Volume_Control_2_2_19203625_20
Volume_Control_2_2_19203625_20_0414
Wi-FiWizard_1_24_1_0
Wi-FiWizard_1_24_1_0_0414
WiFiSettings_1_2_5_1
Warning: Overwriting 'HTC_wifi.png'
WiFiSettings_1_2_5_1_0414
WLANSettings_2_7_10_0
WLANSettings_2_7_10_0_0414
YouTube_2_6_19202631_00
Warning: Overwriting 'HTC_youtube.png'
YouTube_2_6_19202631_00_0414
zlibce_m_1_2_3_1
zlibce_m_1_2_3_1_0414
zzz_feROM_version_pkg
... done!

Finalizing and optimizing ROM structure...
... done!

Memory Map...
SLOT 0: 0x02000000 - 0x017e0000 (END: 0x00060000, 0 MODULES)
0x02000000 - 0x01fc0000 - ROM 0
0x01f80000 - 0x017e0000 - ROM 1
SLOT 1: 0x04000000 - 0x02021000 (END: 0x02020000, 239 MODULES)
SLOT 60: 0x7a000000 - 0x787b0000 (END: 0x78020000, 92 MODULES)
SLOT 61: 0x7c000000 - 0x7a020000 (END: 0x7a020000, 205 MODULES)

RAM IMAGE: 0x80000000 - 0x803b7dcc

RAM: 0x803b8000 - 0x80498000 - Used for kernel modules
0x80498000 - 0x83000000 - 43 MB free
... done!

Donations...
If you're using one of my tools and feel a need to support development
and/or buy me a drink, please feel free to send a donation through PayPal.

Created link in the root of the kitchen.
Updating all files with add2*:
Inserting XIP
Getting IMGFS from NB
Generating IMGFS from DUMP
And putting IMGFS into NB
Generating NBH
Cleaning again
DONE! Now you can flash!

/edit

I also get this when making the nbh:

ROM build process started...
Ceating temporary unsigned ROM file...
Writing ROM header...
OS is 0x400
Writing ROM contents:
OS.nb: 100%
Preparing destination...
Preparing ROM signer...
Signing ROM and copying it to destination...
Maximal chunk size is 64 Kb
DONE: All seems to be ok!
[Windows Mobile] airxtreme:
Yes, I saw it and I was looking right now: the Opal has an option to remove the -uldr switch from implantxip (that avoids uldr removal, right?) while the hermes has actually no switch to remove the -PP switch or using osnbtool.

I don't know how big storage works but there's a -bigstoragemove switch in imgfstonb. Is that it?
[Windows Mobile] airxtreme:
Since I have no rhodium to test I have actually no idea.
[Windows Mobile] Novek:
Seems like non of my ROM's for Rhodium get's past the 1st bootscreen... Even when I just puts together the stock ROM I imported without modifications... :(
[Windows Mobile] hartv427:
I am also having the same trouble with my Rhodium_W the next thing I plan to try is replacing the os.nb.payload with one from a known working kitchen ... I'ts a long shot but may be worth a try
[Windows Mobile] ivanmmj:
Opal sounds correct. I should build a ROM myself and have the Opal users try it.

As far as the Hermes goes, are you saying that it doesn't have ANY pagepool changing attached to it?

I'm trying to figure out the same. Is the switch on in the kitchen?

If it's nk based, then I'll take care of that on my end. (Still researching.)
[Windows Mobile] ivanmmj:
I did some research and found out that the bigstorage hack would have to be done on my end. With that, I have a question:

Can you only have the nk.exe in the nk folder? Or does the kitchen take all the files within that nk folder? (If it takes every file, I can use that to create "bigstorage" xip's since the file that needs to be edited is also in the xip.)
[Windows Mobile] variosteph:
2. changing all ext to leo doesnt work, you have to try one after one...

i asked the same question a while ago:

Originally Posted by daxy View Post

You have to be careful with using a complete EXT tree from LEO. Not all packages are usable on other platforms. I can imagine if you use the complete LEO tree, some packages actually might break your ROM. For example the LongPressEndKey (there it is again) is device specific and the LEO version doesn't work on Rhodium. Also the camera package didn't work for me. I haven't tried using the complete EXT tree from LEO, only some packages however it didn't work for me. Since then I'm only upgrading the packages I want to.

steph
[Windows Mobile] Irishpride:
I apologize if this has been asked here, but is there a tutorial for this kitchen?
[Windows Mobile] hartv427:
V1.05

Good news after many trial and errors. For anyone having trouble building a bootable Rom from this kitchen I have a solution that is working for me. My device is a Raphael_C from Verizon (CDMA)

1) extract Kitchen v1.05.zip to C:

2) put your RUU_signed.nbh in C:\Kitchen v1.05

3) extract the rom

4) Copy wince.nls from Sources/SYS/common/WinCENLS_WWE

5) Past it into your OEMXIPKernel

That's it boots without fail :D

I'm sure the will also work for my Rhodium_W but need to test it

Why this works, I don't know for sure but it does :)
[Windows Mobile] {SBR}_L3GION:
while cooking a ROM the kitchen stops responding and I have to close it and then Platform rebuilder throws an error.
[Windows Mobile] hartv427:
Working with my Rhodium_W now have it booting but have had the same problem as you almost have it finalized but the here is what i have so far the problem is in the EXT Packages I rebuilt them with "EXT_PAckages_rebuilder.exe" and the error stops for me then take OperatorPkg out of oem do the same with it rename it to ZZZ_something and put that in EXT and cook that
[Windows Mobile] {SBR}_L3GION:
Im not using many Rhodium packages Im using the latest Topaz S2 packages mainly I will try your suggestion with the operatorpkg.
[Windows Mobile] qball1616:
wow i had no idea...thank you for the info
[Windows Mobile] {SBR}_L3GION:
I keep getting an error that I have an xip or oem error that has something to do with modules. I have already disabled concurrence manager idk what else is the issue.
[Windows Mobile] programatix:
Thanks, I'll try tonight.
[Windows Mobile] airxtreme:
If I had a confirmation that unicode only would work it would be better because if it doesn't then I'll have to put a warning when unicode config files are detected to avoid this issue happening again.
[Windows Mobile] programatix:
Ok, will try to confirm it tonight whether HTC Autorun would be able to process the fully unicode config.txt.

Thanks.
[Windows Mobile] airxtreme:
Don't all the stock themes except classic blue come in their own package? If you want classic blue deleted too I need to know what files have to be deleted since some stuff is shared among other themes.
[Windows Mobile] Xinot:
Nope, nothing seems to help... cpu usage always jumps to 50% when i open project and do nothing more. With or without AV running etc.:confused:

Well, it's time to re-install my windows anyways so let's see how it goes after that. ;)
[Windows Mobile] airxtreme:
I have found a very interesting switch while looking in the imgfstonb sources, a switch called "-superstorage" that is supposed to overwrite the EXT partition so you can use the ext partition as user space. Anybody knows if this works on any phone (where "works" = overwrites it where possible and doesn't mess up everything in other cases)?
[Windows Mobile] BeeGee_Tokyo:
How do I enable the switch?

If I know, I can test it on Topaz.
[Windows Mobile] Xinot:
Fresh W7 Pro install and high cpu usage is gone! ;)

Now i never know why this happened... Well, now i can cook new rom's superfast again. It was kinda slow when cpu usage was 50-100% and memory usage something like over 500Mb already before i start to build new rom.. :D
[Windows Mobile] programatix:
I can confirm that converting the main config.txt file to unicode solves the problem. However the size of the file double the original size.
[Windows Mobile] airxtreme:
Done

Fixed but you need to edit the "NBH Structure.xml" file and set includeinNBH flag on for the radio.

Just part of the registry tweaks I think, I had to rewrite all the UI for localization/xml/refresh and all the building to fix XP and temp folder issues

If you copy it properly probably nothing else.

I have added an option to use imgfstonb/implantxip for building, that should fix the issue.

I couldn't fix it yet in RC4 because I forgot but I'll see what can I do.

You have to add the switch to the cmd file on ervius kitchen but I already know it works on some devices, the problem is if it makes unbootable roms on some other devices.
[Windows Mobile] kane159:
C:\testkitchen_LEO\Temp\ROM Building\OS Sections\OS.nb" to "C:\testkitchen_LEO\Output\HTC Leo\RUU_Signed_0404.nbh

why?? the new tool just cut the os.nb to ruu_signed.nbh??

I cant flash with this nbh, it always give me error 280 ;(

do i need to rename it back to os.nb then make a new ruu_signed.nbh for it??
[Windows Mobile] cac2us:
Flashing Method

Are you using the ROM Update Ulillity? Or can you flash via SD Card?
[Windows Mobile] kane159:
ROM Update Ulillity
[Windows Mobile] airxtreme:
That only happens if you have no NBH structure folder and NBH structure file in your device profile folder. Are you sure you imported a rom properly?
[Windows Mobile] af974:
Any chance to test it on Kaiser with OsKitchen...i use only this Kitchen.

Glad to make guinea pig for testing.