yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] tobbbie:
1.3.216 observations

My observations with the new version:

GUI is refreshed while the build is running - nothing can be done however during build run.

I noticed that the step "preprocessing" is now 1:20 minute (CPU busy) while it was just 2 seconds in 1.3.199. I have not seen anything obvious in the settings - is there anything to switch off? IMGFS build is the same time as before. Total time is up from 2 minutes to 3:20 minutes due to that :-(

Also I have seen some Russian letters written when starting a build on the top of the window when deleting the old temp-folder (I have delete in background de-activated). I guess it says "deleting" \temp... where the "deleting" part is in Russian.

The provxml sequence is not listed correctly - I had reported this sometime back. It is not done by the .sof order only but mxipcold (.sof order) first, then other mxip_* (.sof order) and finally mxipupdate (.sof order) - at least if you have no OEM add-on which intercepts this or adds its own logic (like htcinit.dll). I have supplied tracing methods to prove that here.

I noticed that the treatment of the "merge packages" had changed already some time ago (did not follow up on my reported error). Not sure how the rgu merge is done now, but it seems there is no more a .provxml merge but all provxml are kept intact to make sure that the original treatment on the device is kept (MS native or OEM altered) - thanks for this!

One question regarding XIP optimization: 1.3.199 had the option "remove dll gap if possible" on the normal build page - now on XIP page. Additionally there is remove dll gap in slot 0.

Where are these possible unused memory areas (slot 0 and XIP RAM?) and how much can be reclaimed? Which is the gain for each of these options - more modules in slot 0 and more available RAM?

If I do not rebuild the XIP (but use the template) could not the slot 0 related setting still have to be treated (this was my guess with the old settings setup)? I have no deep understanding of the relocation, so please don't flame me here.

I noticed that such optimized XIPs do sometimes not work on larger IMGFS, sometimes I also had to remove the module compression from the XIP parts to have larger builds boot.

No problems if you keep "do not move RAM start and nk RW sections" obviously :-)
[Windows Mobile] -=Barin=-:
@tobbie

My timing results (HTC HD2 ROM Building):

-------------------- TIMING ------------------------
Porting/Rebuilding XIP 00:00:02
Correcting template 00:00:00
Preprocessing 00:00:03
Registry 00:00:01
Metadata 00:00:00
Postprocessing 00:00:00
Relocating/Writing modules 00:00:02
Copying files 00:00:00
Merging/Writing dsm 00:00:00
Building IMGFS partition file (XPH) 00:00:03
Building ROM file 00:00:01
Net time 00:00:17
Total time 00:00:25
----------------------------------------------------
PACKAGES 398
MODULES 646
FILES 7120
----------------------------------------------------
[Windows Mobile] tobbbie:
Adding a dummy.dll entry to all lists does not help either here - will revert to the old version for now.
[Windows Mobile] tobbbie:
What is supposed to happen in the "preprocessing" phase? It is strange to see that all the imageinfo.bin are inspected and then all the modules sections.

Why is that triggered and how can I switch this off?

Do you need more symptoms (did you look at the procmon trace in my initial post)?

I noticed that the various lists dealing with modules treatment seem to be handled only AFTER the strange behavior, so I have no more clue what else to do.

I could not check on the 1.4.205 as I missed that one and it is not available for download anymore - but on the 1.4.206 it always happens. Getting back to 1.3.199 everything is back to normal. I would like to stay on the latest version and not be stuck on 1.3.199 for unknown reasons.
[Windows Mobile] tobbbie:
Wake up - new version available in the first posts - see topic title.

---------- Post added at 04:35 PM ---------- Previous post was at 03:50 PM ----------

Sad to notice that still the "preprocessing" part is lasting "forever" (4:08) and hogs the CPU 100%. I am willing to assist in the debugging if you care for my symptoms - was ignored for 1.4.206.

Must go back to 1.3.199 - sigh... - where the same kitchen takes 3 seconds for the pre-processing part. Mind that the IMGFS creation takes just 1:30 so the wasted time in preprocessing is really a "forever".

Kitchen can be made available if you need that.

---------- Post added at 04:58 PM ---------- Previous post was at 04:35 PM ----------

My latest Hurricane Kitchen (removed temp) - just unpack, double-click the OSBuilder.osb and push the button to create the build. Share is here:

http://www.mediafire.com/?a5o619j9ot2zk

---------- Post added at 05:09 PM ---------- Previous post was at 04:58 PM ----------

1.3.199 timings on my old PC:

-------------------- TIMING ------------------------
Porting/Rebuilding XIP 00:00:05
Correcting template 00:00:00
Preprocessing 00:00:13
Registry 00:00:05
Metadata 00:00:00
Postprocessing 00:00:00
Relocating/Writing modules 00:00:08
Copying files 00:00:00
Merging/Writing dsm 00:00:00
Building IMGFS partition file (LZX) 00:01:33
Building ROM file 00:00:01
Net time 00:02:09
Total time 00:02:29
----------------------------------------------------
PACKAGES 138
MODULES 399
FILES 953
----------------------------------------------------
[Windows Mobile] tobbbie:
I could not reproduce the problem on my company laptop. So it seems to be problem with my home PC only - however repeatable as described.

This should make debugging possible - will get you updated once tracked down.
[Windows Mobile] ultrashot:
How many cores do you have on your home PC?
[Windows Mobile] tobbbie:
It is an old Pentium IV 2.6 GHz Single Core with 2GB RAM - even older than the smartphones I cook for. You have changed the threading to get the GUI more responsive - an unwanted side effect?
[Windows Mobile] ceesheim:
ok here comes a real quick awnser :

GET A NEW PC :D
[Windows Mobile] tobbbie:
Why should I do that? I neither need 3 D games nor any other new fancy stuff. Browsing and Office is fast enough as well - runs nicely with 2GB RAM and good old XP.

So still old PC and still old phones :-) I will rather buy a new phone (or a tablet maybe...) than a new PC.
[Windows Mobile] ultrashot:
Sort of. Probably we'll fix, er, remake some things for you, but I can't guarantee that.
[Windows Mobile] tobbbie:
Thanks for taking care!

If you can rearrange your framework to cope well with single CPU cores would not only benefit for me - but all others who just silently sit and wait. Not sure how big the community of cooks still is - but I am really happy that OS Builder can still reliably create builds for the good old Typhoon, Hurricane and Tornado.

I have done all I wanted for my taste on these (even SDHC luckily works on Typhoon and Hurricane - Tornado already discovered earlier) - so I could also get along if you keep it like it is now, if your efforts are too high for your taste. Just notify in your Release Notes that optimal performance can only be achieved with x(?)-core CPUs.
[Windows Mobile] WhiteTrap:
Hello, I've tried to extract the IMGFS from the stock HTC Mazaa ROM that is around.

I used FFUPartTool 1.3.1 with the -extimfs parameter to create the IMGFS. But then when I try to open it in OSBuilder 1.4.209 (in Dump Tool mode) with Open IMGFS partition file, I get this error:

Reading IMGFS:

Invalid block signature

Any idea of what the problem could be?

Moreover, why don't you realease the source code? That would make life easier for the rest of us :)

Thanks for the great tool!
[Windows Mobile] tobbbie:
Can't you use OSB for the whole workflow of dumping?

In which format is the stock ROM delivered?

---------- Post added at 11:05 PM ---------- Previous post was at 11:02 PM ----------

For WP7 related queries on OS Builder, please move over to: http://xdaforums.com/showthread.php?t=1330850
[Windows Mobile] WhiteTrap:
It's in FFU format and OSB doesn't support them. I've fixed removing from the EXE itself the exception giving the problem, and now things work fine. Pretty raw method but gets the work done.

Thanks!
[Windows Mobile] Eshine:
Prompt error in the production of Titan rom

v1.4 209Prompt error in the production of Titan rom
[Windows Mobile] tobbbie:
The WM7 thread is this: http://xdaforums.com/showthread.php?t=1330850
[Windows Mobile] ultrashot:
Looks like you are building WMSTORE rom using D000FF config...
[Windows Mobile] Tachi91:
never mind
[Windows Mobile] lixiangna:
1.4.209-wm6.5

wm6.5

The new version of the program(OSBuilderSetup1.4.209-FULL)

Is easy to make a mistake

Resco_Explorer_v8.10___我的注册表.lnk(34#"\Windows\Explorer.exe" 0x0020,"\"

)

PocketMusicBundle_v5.3.5___Directory of all documents **.EQF

Automatic close the program

Looking forward to the next more perfect
[Windows Mobile] HD2Owner:
thread updated. leave barin a thanks please if you use the kitchen.
[Windows Mobile] kunc002:
Please help.:(

View attachment 1610816
[Windows Mobile] Zen3515:
does it supported Nokia Lumia 900

WP7.8
[Windows Mobile] HD2Owner:
that's the wrong question. the right question would be:

is there a unlocked bootloader for l900.

the answer is no. so unsigned custom roms for it make no sense.

but it would for sure work to build a rom for that device.
[Windows Mobile] Zen3515:
I'd asked right question.

My friend he has ATF-Nitro so that tool unlock my bootloader.
[Windows Mobile] HD2Owner:
obviously you didn't check out lumia 900 dev forum (me neither because i don't have a lumia)... :p

http://xdaforums.com/showthread.php?t=2392493

so go ahead and build your personal rom with osbuilder or flash the one from the link.
[Windows Mobile] jackrabbit72380:
I try to day to dump my own rom I cooked that I have dumped countless times but now I cant... I dumped but when I create packages I get this error.

Creating packages...The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

it stops on ...

OEM\NOKIA_RM823_AdditionalEmailAccounts_Lang_0409\EmailAccountDisplayStrings.dll.0409.mui

I buld this rom and update now my update is not booting due to error and I try and use my backup and I cant because of this. =(

this rom is flashable and works yet I cant dump it.
[Windows Mobile] RustInPeace:
Hi, try to put the rom you want to dump in a directory with a short name that is located at the root of one of your hard drive, for exemple d:\rom\romfile and then dump it.

actually if the path is too long ( drive lenght + directories lenght + filename lenght + all separators (/) > 260 ) this error occurs, it's operating system related (all windows i guess)
[Windows Mobile] _Madmatt:
Every package I click the thing asks me to CREATE that file. But somewhere there must already be such a file, because there are links in my StartMenu...

For example, the Adobe PDF package, when I click "Edit initflashfiles.dat" it asks to create that file. When I say "yes" the file is empty. But however, without that file there already is a link in my Start Menu.

So, there must be another place where there is "Copy a link in the start menu". That place I want to edit.
[Windows Mobile] Skrobel:
The stock packages have reference to their links in the whole main intflashfiles.dat, so you should search for the Adobe link in there.
[Windows Mobile] _Madmatt:
I was searching for the same in SYS packages. But there they are in the Provxml files... Probably osKitchen converts it automatically. :)

Thanks anyway!
[Windows Mobile] AndrewSh:
You're looking in the wrong place. Normally stock initflashfiles.dat is in OEM_Lang_XXXX.

Listen, the process is the following - you dump the original rom. Then you replace SYS and XIP. Then you build your new rom.

But no-one will create custom Startmenu icons for you. When you do like I said - you will get a copy of your original rom but with updated build.

If you want some kinda customization - you should do something manually - create initfashfiles.txt to the packages you want, or edit basic initflashfiles.dat, or edit some provxml, or create your own ones.
[Windows Mobile] tobbbie:
In the search for variable module mapping options I have come across this kitchen and it looks very promising. I noticed however that some of the more interesting insight options are "not available in the public version" - so I wonder if these options are existing at all and if (and how) I can get access to such a version to play with?

My intention is the following:

I cook (well, more reuse an old kitchen) for the Tornado (yes, a 2006 device...) and want to port this result to an even older device (Hurricane). In the process of porting XIP from Tornado WM6 to an oder WM6 Hurricane build and rebuilding the ROM I came across a strange behavior of - I suspect the ddi.dll module:

When re-assembling the WM6 Hurricane (an original wm2k3 device) ROM behavior is normal, i.e. the screen updates regarding GUI elements is as expected. Just dump the ROM and rebuild it, no remapping.

After a remapping with wmreloc (g'reloc creates non booting ROMs), the scrollbars "gap" space is filled with random garbage when scrolling. No other side effects, but this is annoying and I have no clue how to resolve this.

I noticed there is an option to supply a list of modules that should not be mapped. Is this existing - and does it work?

The ddi.dll that is used for the Hurricane WM6 ROM is coming from the Elf (not sure if patched or not) and my simple idea to replace it by the Tornado ddi.dll module was not successful.

Any help?
[Windows Mobile] Skrobel:
Well, as for the functions "not available in public version", this is simple. You need to donate to get the "full" version.

As for me, I really would like to donate not only to receive full verions of the kitchen, but I just think it's a brilliant tool and the work deserves a little something in return. However there seems to be a problem to donate via Paypal. I found some post dtd. 05/2010 where Barin said this is not possible to receive money via Paypal in Russia. And the other systems he proposed are quite expensive (the provisions killing the donation ;) ).

So if somebody of you knows a better way to donate to the kitchen Authors, it would be a good idea to describe it here or in the first post.
[Windows Mobile] tobbbie:
I expected that a donation would reveal the enhanced version - and I would not mind doing so. I don't see an indication at PayPal that it would not work in Russia though. I also established (but never used so far) an account at moneybookers, probably this could work?
[Windows Mobile] _Madmatt:
How much should I donate at least to get full version?
[Windows Mobile] tobbbie:
Has anyone experience with the http://www.wmtransfer.com/ already? Looks serious and seems popular in the eastern world. What about overhead charges to fill a purse for Euros?
[Windows Mobile] boggsie:
There is a completely trustworthy fellow that has both PayPal and WebMoney accounts and will turn your PayPal to him into WebMoney to Barin.

I've done it, it works perfect and you get the full version from Barin as a courtesy in return for your contribution.

If you're serious, just PM Barin here on XDA and ask him about it.

From his post over at AsusMobile.

Best regards,

-boggsie
[Windows Mobile] pinuzzzooo:
Hi guys. i have tried to cook for my HTC POLARIS, but i have one problem. How switch from 6.1 to 6.5 kernel??? With other Kitchen all is fine and i build a rom with 6.5 NK.exe, but here when i cook my rom, my phone stucks in splash screen. I've tried to manually switch the nk.exe in oemxipkernel root, but the kitchen doesn't recognised the 6.5 nk.exe. I know that probably my device doesn't supported, but my hope is that i don't cook very well.....bye
[Windows Mobile] _Madmatt:
Have you tried to set the NK version in the kitchen manually to 6.5 instead of auto-detect? :)
[Windows Mobile] pinuzzzooo:
Yes, MadMatt, i tried it...
[Windows Mobile] _Madmatt:
And you are sure you're using the right NK.exe? I think you should search for another NK.exe ;) HTC Polaris, isn't it? I'll take a look ;)
[Windows Mobile] pinuzzzooo:
Yes I'm sure...and it works with other kitchen...
[Windows Mobile] _Madmatt:
And you're sure you have replaced you nk.exe folder here?

"YOURPATH\Dump\ROM\XIP\OEMXIPKernel"?

Afther doing so, go to Settings => XIP => Select the Port option => OEM XIP: XIP from template and MS XIP: File Donor\XIP.bin

Good luck :)
[Windows Mobile] pinuzzzooo:
Oh yes...that's all set as default in os builder. Just one question: In the donor folder i put in the msxipkernel and the xip.bin from the new build that i've to ported (in my case 21854 from official Mega)
[Windows Mobile] _Madmatt:
That's it ;) Now you're talking about a donor XIP.BIN I remember I had to build a new XIP.BIN to get it working ;)

You can use this tool to build your XIP.bin. Afther building your XIP.bin, copy (or move) it to your Donor folder and build your ROM in OSBuilder. Let me know how this worked out!

For me it worked fine to update my build 23103 to 23152 on my Photon.
[Windows Mobile] pinuzzzooo:
This is new for me...thank you so much for your help...I post it the result tomorrow...Bye
[Windows Mobile] pinuzzzooo:
I've tried many times and the tool report me this error

Can not open romhdr.bin

I put it in its folder, but when i execute the batch file, the tool says "Can not open romhdr.bin", and delete that file...HELP...:D
[Windows Mobile] _Madmatt:
Okay, delete it all :p And now extract again the ZIP with the tool in an empty folder. Now read the readme file, which says that you should go over each file that's in it. Put all the files they ask for in the right folder.

Then you should run the BuildXIP.exe file and not the batch file ;)

Good luck
[Windows Mobile] pinuzzzooo:
Nothing, i'm very unlucky...:(

Edit: Same Error, "Can not open romhdr.bin"

Edit 2: I've created the new xip with this tool, but the rom stucks always at splash screen

Any idea?
[Windows Mobile] _Madmatt:
If you created the XIP.bin like described in the read me file, it should work. So the only thing I can think of is a wrong nk.exe or another package that's not working. But as you only replaced the nk that will be the problem ;) You can try building a XIP.bin with the old nk.exe using the tool. If that works, nk.exe is the problem.
[Windows Mobile] pinuzzzooo:
Mmmm, are the same package that i used with EVK Kitchen...I'll try without replacing the nk.exe...write you later...:D

EDIT: Ok guys, i think that i solved, this is the way, my way. I've recompiled a new xip.bin with the tool posted by Madmatt same post ago. It's very simple, you have just to read the readme.txt in each folder to build it (the xip). I put it in my Kitchen "DONOR" folder and in my Kitchen "ROM" folder. Then i've execute OS builder and i'm gone to setting>xip>port oem xip and selected file xip.bin in rom folder; then i'm gone to setting>build dump and rom>while assembling use xip>xip.bin in rom folder. I've refreshed the kitchen and in the log on the right side the kitchen has autodetected the new 6.5 Kernel. IT WORKS. After build my custom rom, i've replaced the file "rom.tpl" in "ROM" folder with a new "rom.tpl" created in temp folder and i've restored the kitchen default setting. Works AGAIN...Thanks you so much MADMATT, without sharing your preciuos help i think that i never understand the right way...:D
[Windows Mobile] alexander555:
Which Source ROM work?

Hi,

i've tested the dump functionality with an custom "energy Rom" an the dump process don't work correctly. I don't get the correct package structure. If i try the same steps with the orginal HTC Rom the dump process works fine.

Can someone exlplain this? Thx
[Windows Mobile] Skrobel:
Well, custom ROMs are protected against recooking by means of deletion of all the dsm/initflashfiles/app.* files that could be used to determine particular packages structure. All you can do with a custom ROM is making so called flat dump (just extracting the files from the image without creating the structure and without XIP region).

Basically only stock ROMs are fully dumpable.
[Windows Mobile] mac_es:
Or you can set in XIP:

Rebuild from xip files and in Build section set to rebuild the xip also... it seems to work though I haven't flashed it (I'm porting my actual kitchen...). It detects the new cecompr.dll and nk.exe

I have some questions: :rolleyes:

1) Ok, to get a "similar" ROM from prb I should check strip de Relock section and ULDR to empty, no?

2) What are L modules?

3) There is some reason to want some module in slot 0? Since Wm5 I haven't find any module that requires actively been in slot0...

4) The dll gap in slot 0 is used for? I mean, it is there for some reason no?

5)Also, there is a way into adding several packages at one time? I mean, I want to add all the SYS and I don't want to go one by one..

6) In the manual it says that it is not supported to put packages out of OEM/SYS and warns about unpredictive results but in the video manual it uses EXT folder. Which one is correct?

7) There is any utility when dumping the rom to split de inittflashfiles.dat into initflashfiles.txt files?

8) There is a way to modify nk.exe to change the version and date info

cheers
[Windows Mobile] Farmer Ted:
L modules get loaded low in slot 0-you want to avoid this in most cases. So, it's better to check the 'split L modules' box, it will save a ton of virtual memory in all the slots. I don't think you want any modules loaded low; there are maybe 50 in the Sys alone, and they can eat up 5-10 MB of virtual memory. If you want more info on low modules, try googling "loadmodulelow"; there's an msdn article on modules that need to be loaded low in slot 0. Most do not. The only file I have that loads low is rsaenh.dll. There's a line in the boot.rgu that tells the loader to load it low. If you convert it to a module and have it split, then the device won't boot. I believe that PRB splits the modules by default, but OSB gives you a choice.

The modules loaded in the high section of slot 0 are normal. You get this in all roms-this is the read-write code section from dll's, which has to go in slot 0. Only the read-only sections are mapped to slots 1, 61 and 60. The read-write section is normally pretty small; most are just 4 kb, which is the page size. If you like to convert files to modules in your packages, this is the one thing you want to check. I had a few dll's in Resco Audio Recorder that had huge read-write sections. There were two modules that took up 2 MB of virtual memory in slot 0, and it had bad effects on some of my processes. So, I had to leave the dll's as files, although the phone recorder loads more slowly that way.

Stripping the reloc sections is an option; you can also build all dsm's to one to get a rom closer to what PRB builds. Personally, one of the things that attracted me to this kitchen was the option to build unprotected roms. I just cook for myself, and having an unprotected .nbh file is an excellent way to back up the kitchen. I really have not noticed any loss in performance because of the extra files in windows (maybe 300 dsm's and rgus's), and I seriously doubt that having that last S000x file in each module slows things down in any measurable way.

Have the dll gap removed; I haven't checked the difference in the xip map, but I suspect is saves you a nano-fart of RAM.

Do other kitchens split the .dat file into .txt files? I don't think this one will do it.
[Windows Mobile] mwalt2:
OSKitchen by airxtreme does this (well, it breaks initflashfiles.dat into app.dat's since it uses EXT and is PRB based). I actually dump all ROMs with OSKitchen and then covert the EXT to OEM and use it in OSBuilder since the OEMs will then contain the proper initflashfiles.txt and mui's (I only cook WWE for myself).