[KITCHEN] OS Builder V1.4.236 FULL (01.12.2012) - pro wm/wp7 kitchen by barin

tobbbie · Mar 13, 2012

When dumping the ROM, it seems that the partitions are correctly identified and output to disk. No matter which way you do that step - how big is that XIP (2.bin for OS Builder here) file on your disk?

Speculations:

you may have an Antivirus SW that blocks access to *.bin files: check if you can hex-read the output 2.bin file
The author of the ROM may have manipulated the partition table for the ROM. Not sure if this has adverse effects on the funciton of the ROM (I guess no), but it would prevent dumping the ROM easily. It has usually the ULDR, the XIP and the IMGFS (eventually EXT). When dumping the os.nb, which are the sizes of these?

For sure you do not come to the real dump part of the actions yet. The XIP dump creates the ROM directory, while the IMGFS dump creates the OEM and SYS (and XCONT for what cannot be put there).

If any of the usual protection schemes are in the ROM (Farmer Ted has mentioned a few) you will not be able to re-cook anyway. There are some ways around the missing packages (recently I saw a tool here to re-create the packages, but never tried it out) but you cannot work around the missing .reloc sections if it applies to ALL modules.

Get to the author - really the best solution. Give him the credits he deserves if you publish a ROM based on his - naturally. My ROMs have a credit list that goes back to actions of 2007 - however I cook for real old stuff

Edit: Could you upload the .nbh somewhere (mediafire is a good place) - I could try to get it dumped and see what the problem is.

Farmer Ted · Mar 13, 2012

Digistras said:
How can I know weather is protected or not? Anyway to find out?

Look in the windows folder, and see if it has all the .dsm's and .rgu's. If there are only a couple of each, then they've been stripped out during the build, and you won't be able to recreate all of the packages in a dump.

Digistras · Mar 14, 2012

Thanks for your reply tobbbie

how big is that XIP (2.bin for OS Builder here) file on your disk?

The 2.bin file is 3.75MB in size. Illustration as shown:

you may have an Antivirus SW that blocks access to *.bin files: check if you can hex-read the output 2.bin file

I used Xvi32 to to open 2.bin and was able to do so as shown below:

The author of the ROM may have manipulated the partition table for the ROM. Not sure if this has adverse effects on the funciton of the ROM (I guess no), but it would prevent dumping the ROM easily. It has usually the ULDR, the XIP and the IMGFS (eventually EXT). When dumping the os.nb, which are the sizes of these?

Not sure what you mean by ULDR. Maybe you can explain it? When dumping os.nb, the dump did not complete as it encountered errors about the 2.bin file being in use which is the same error that I posted in my earlier post. I only managed to see 2.bin and XIP.bin after the error came out and both are 3.75MB in size.

Edit: Could you upload the .nbh somewhere (mediafire is a good place) - I could try to get it dumped and see what the problem is.

Uploaded to MediaFire. Link as below:

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

tobbbie · Mar 14, 2012

Sizes look reasonable, it seems OSB is doing something on 2.bin to create xip.bin or vice-versa before dumping the content. Is there a difference between these two?

The ULDR is not required for any cooking actions and can be ignored or even minimized or deleted in a final build. It was planned as part of a FW Update process over the air - or later automatic push installations. Afaik this was never used, though.

I can look after the .nbh only later today.

Mind that before OSB there were dedicated tools for all the steps of action:
- decrypt the .nbh
- dissect the resulting .nb in its parts (ULDR, XIP, IMGFS, others)
- dump the XIP
- dump the IMGFS
- build the packages from the dumps

So if OSB does not get further at step 2 - why not try others? It will be much more difficult though to set up the right kitchen structure then and as a newcomer you will most probably fail in that attempt.
If you could stay within the OSB workflow you have a chance - otherwise, good luck!

To get some basic idea about cooking, look in my signature and follow the link to the Beginners guide

Digistras · Mar 14, 2012

I'm not sure if there is any difference between 2.bin and XIP.bin but both file size are the same though.

Thanks for taking the time to help me look at the .nbh. Hopefully it can tell you something.

I did try OsKitchen before coming to OS Builder. I believe OsKitchen is going through the same process.

I've taken a look at the Beginners Guide and kind of understand the architecture but will still need to read up more. Thanks for the guide.

tobbbie · Mar 15, 2012

I had the same problems in dumping the .nbh with OSB. It seems that not all exceptions are caught the right way and the resulting error message is misleading. I have decomposed the .nbh with DaG's nbimagetool and then dumped the imgfs with OSB. The resulting content is (as expected) free of any packages so you cannot re-cook this.
Added: you can see this yourself with the ROM loaded as the windows directory had no *.dsm and *.rgu files.

I have not further done anything to the XIP. ULDR is already only a dummy one (124k).
Please contact the author of the ROM if he is willing to share the kitchen with you.

Digistras · Mar 15, 2012

Hey tobbbie

Thanks for helping me to confirm that the IMGFS is not able to be dumped.

I used ImgfsFromNb.exe to dump IMGFS and the generated output is 0 bytes.

How are the *.dsm and *.rgu files created?

Also, I saw this on your beginners guide:

"OEM parts stay usually unchanged through all cooking and porting activities, so that also means that a WM5 device will keep all the OEM parts even if the OS version is WM6.5. OEM parts are in both, the XIP (nk.exe and some OEM modules) and the IMGFS. You will especially not gain any advantage of the enhanced memory allocation scheme if your device does not have a native 6.5 kernel (nk.exe)."

Does it mean that I can just use the IMGFS and XIP of official ROM (WM 6.5) and use it on this cooked ROM (WM 6.5.5)?

I also saw this: http://xdaforums.com/showthread.php?t=320504&page=49

but I'm missing the buildos+packagetools2.0b1.exe (link dead) as it contains 319'880 buildos+package_tools-2.0b1.exe. Not sure if that method works though.

Do you happen to have it?

tobbbie · Mar 15, 2012

Digistras said:
How are the *.dsm and *.rgu files created?

The are not created, they are there from the start. A package is defined by a set of files and related production configuration files - the dsm and rgu. The DSM (Device Side Manifest) are used to set properties of the files/modules when the IMGFS is constructed and the RGU (Registry Update) are used to update the registry with relevant settings. Each package has a unique GUID identifying it.
The DSM and RGU are not needed on the device but they are mandatory if you want to go back and re-cook. No way to recover this with a sane outlook to success. Hence stripping these in the cooking process "protects" the ROM.

Digistras said:
Does it mean that I can just use the IMGFS and XIP of official ROM (WM 6.5) and use it on this cooked ROM (WM 6.5.5)?

This is the basic idea. You have the OEM parts of your device and replace the XIP and SYS with that of a "donor". It is however not simple copy as several hooks need to link together in the right way. OS Builder has dedicated supporting tools and procedures for XIP and SYS porting.

Digistras said:
Do you happen to have it?

No, sorry.

Sad for you is that you cannot use the ROM in question as your base. If you want to start cooking, get your shipped ROM, dump it and try to re-cook it. If you get that mastered, then you can think of XIP and SYS porting.

Digistras · Mar 15, 2012

I've dump the .nbh using DaG's nbimagetool and then using the same tool to dump os.nb which then IMGFS can be seen and is 127MB in size.

Below are the steps that I have done:

1. Dumped .nbh using DaG's nbimagetool.

2. Used DaG's nbimagetool again to dump os.nb and imgfs.bin and xip.bin was extracted. File sizes are as shown:

3. Dump imgfs.bin using ImgfsToDump.exe (with cecompr_nt.dll). I followed the instructions and tools from http://wiki.allshadow.com/index.php/ROMs_For_Dummies:_Part_Two#Converting_to_ROM_dump

As you can see that after dumping the imgfs.bin, a dump folder and memory map is created.

So from here, is there anyway that I can package the dump folder to create a .nbh with the proper imgfs.bin and xip.bin so that OsKitchen is able to load? Not sure if I'm on to something here though.

tobbbie · Mar 15, 2012

Why do you want to continue here? The IMGFS (and the XIP most probably as well) does not have package information left. You cannot alter anything of the content in the way any kitchen works.

Stop with this protected ROM and pick up your actions with a shipped ROM where the packages are still intact or with a kitchen of that ROM where the packages are still there.

There is no magic or other tooling that will bring you back the packages. There is also no other kitchen that can do anything with this ROM.

Digistras · Mar 16, 2012

I'm not sure if I understand this correctly. By "Package Information", do u mean the *.dsm and *.rgu files?

tobbbie · Mar 16, 2012

Exactly - if they are not there then you cannot cook - so easy. Cooking is basically just a selected set of packages + some tweaks + some own packages if you are able to do that (not hard actually).
Get ahead of dumping a shipped ROM, then you see how that works.

Digistras · Mar 16, 2012

I have a shipped ROM that is on WM6.5 for HTC Mega that is with all the HTC packages and a cooked ROM that is on WM6.5.5 also for the HTC Mega but is a clean base ROM.

So from the shipped ROM of WM6.5, is there anyway I can upgrade it to WM6.5.5 from there?

If not, anyway I can build a WM6.5.5 with HTC Packages of the extracted WM6.5 shipped ROM?

tobbbie · Mar 16, 2012

You can re-combine packages from these sources - provided that the packages are there. Suggested sequence:

dump the shipped ROM
re-cook it without changing anything (this will be hard enough for a start). Only this way you can make sure that not something from the later SYS/XIP porting prevents your device from booting.
Kick out some OEM packages to get used to the cooking
dump the 6.5.5 ROM and make sure that it delivers also the package information
Port the XIP only and see if the build from 2/3.) still boots (6.5.5 XIP should be rather identical to 6.5)
Port the SYS

This looks easy but it will take you some weeks and a lot of reading around. I cannot continue to spoon-feed you with all such basic things of cooking - make some own experience now... and good luck doing so!

Digistras · Mar 16, 2012

4. dump the 6.5.5 ROM and make sure that it delivers also the package information

This would require the *.dsm and *.rgu files right? So I can't use the ROM that I posted for you earlier?

5. Port the XIP only and see if the build from 2/3.) still boots (6.5.5 XIP should be rather identical to 6.5)

There is a possibility that it might fail due to the difference in version? (WM6.5 vs WM6.5.5)

AndrewSh · Mar 17, 2012

I doubt that you will get bootable rom using 6.5.5 xip with 6.5 SYS and vice versa.
These two branches have different GWES, so coredll and other things might not fit.

I don't see any benefit using someone's custom rom as a source. The sequence of the activity is following:
1. Dump stock rom for your device
2. Download SYS & XIP archive from the builds thread.
3. Put XIP to DONOR folder of your kitchen (subfolder should be named as the build number - XXXXX)
4. Replace stock SYS from SYS folder to SYS/SYS_YYYYY (where YYYYY is a number of your stock build)
5. Put downloaded SYS to SYS/SYS_XXXXX folder
6. Adjust settings of OsBuilder - to port XIP etc.
7. Cook

It's a general tip. Without details.

tobbbie · Mar 17, 2012

AndrewSh said:
3. Put XIP to DONOR folder of your kitchen (subfolder should be named as the build number - XXXXX)
4. Replace stock SYS from SYS folder to SYS/SYS_YYYYY (where YYYYY is a number of your stock build)
5. Put downloaded SYS to SYS/SYS_XXXXX folder

Are you using a multi-build setup in your cooking? I tried to but it did not port the XIP correctly (despite all paths are setup correct) - it failed getting the OEM-XIP from the original ROM\XIP folder - is there a trick?
I used the Russian Multibuild manual (Google translated) and I am quite sure I did all as outlined there.

As I have my Tornado and Hurricane Kitchen all on WM6, WM61 and WM65, it would save some space (and effort) if I have the OEM parts identical - at least for the latter two where I have them truly identical.
Some parts are different in the OEM regarding the treatment of settings and the .xml panels on smartphone between WM6 and WM61 and up - is there an option to link such differences also the the branches of the Multibuild environment?

One caveat with XIP porting from donor is that the DSM compression settings are not used from the DONOR but the original - had reported this but nothing public has changed.

Digistras · Mar 17, 2012

AndrewSh said:
I doubt that you will get bootable rom using 6.5.5 xip with 6.5 SYS and vice versa.
These two branches have different GWES, so coredll and other things might not fit.

I don't see any benefit using someone's custom rom as a source. The sequence of the activity is following:
1. Dump stock rom for your device
2. Download SYS & XIP archive from the builds thread.
3. Put XIP to DONOR folder of your kitchen (subfolder should be named as the build number - XXXXX)
4. Replace stock SYS from SYS folder to SYS/SYS_YYYYY (where YYYYY is a number of your stock build)
5. Put downloaded SYS to SYS/SYS_XXXXX folder
6. Adjust settings of OsBuilder - to port XIP etc.
7. Cook

It's a general tip. Without details.

Hi AndrewSh,

Thanks for the steps. I don't see any mentioning about the custom ROM that I have for WM6.5.5 in the steps. So are those steps only for WM 6.5 or using WM6.5 XIP and SYS porting over to WM6.5.5?

AndrewSh · Mar 17, 2012

tobbbie said:
Are you using a multi-build setup in your cooking? I tried to but it did not port the XIP correctly (despite all paths are setup correct) - it failed getting the OEM-XIP from the original ROM\XIP folder - is there a trick?
I used the Russian Multibuild manual (Google translated) and I am quite sure I did all as outlined there.....

Yes I use it multibuild. And also I used it multibuild for my old Asus P525 which is native WM6.0 device...
Normally I don't remember any tricks.... It always worked for me well.... And the biggest **** - I did not read the Russian manual (don't tell Barin - he will kill me) - I only often translated changelogs when Barin was busy...
So for my old Asus - I pointed to rebuild new XIP using OEMXIP from template and MSXIP from DONOR. For Leo - from packages in DONOR folder and packages in ROM/XIP folder.... Actually - w/o issues....

Digistras said:
I don't see any mentioning about the custom ROM that I have for WM6.5.5 in the steps. So are those steps only for WM 6.5 or using WM6.5 XIP and SYS porting over to WM6.5.5?

No, these steps are universal.
You take the latest STOCK rom for your device, dump it and use as OEM and XIP source.
Than you grab the any MS build archive (containing SYS and XIP packages) and create your kitchen.
No customs! Because normally customs are stripped and protected - you won't be able to correctly dump them.

Digistras · Mar 17, 2012

I have a custom ROM that is on WM6.5.5 for my HTC Mega and I'm able to dump the IMGFS.bin. Can I use the extracted contents and build my own custom ROM?

I also have the XIP.bin for the custom ROM.

[KITCHEN] OS Builder V1.4.236 FULL (01.12.2012) - pro wm/wp7 kitchen by barin

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts