[KITCHEN] OS Builder V1.4.236 FULL (01.12.2012) - pro wm/wp7 kitchen by barin
- Thread starter HD2Owner
- Start date
Also thought that it could be that. But I'm still having 10GB left, so that should be more then enhough? Or not?
EDIT: It works now! Don't know what exactly did the thing change it's mind
Another little question. In the NBH settings form, the Radio, RadioCust, PrimarySplash, CONF, UnknownSplash1 and UnknownSplash2 are all unchecked. Does this mean that my Radio is not included in the ROM and I won't be able to make calls?
Last edited:
Am I the only one with questions using this kitchen? Anyway, next
I yesterday built my first ROM using this one, but when I try to start phone I get a error report (which I can send or not send to MS). Is this a problem with the Radio or is this a missing package? Or something else?
So, I cannot start my phone and can't get any messages or phone calls....
Because I'm on stock ROM now, I want to fix this ASAP.
I yesterday built my first ROM using this one, but when I try to start phone I get a error report (which I can send or not send to MS). Is this a problem with the Radio or is this a missing package? Or something else?
So, I cannot start my phone and can't get any messages or phone calls....
Because I'm on stock ROM now, I want to fix this ASAP.
I think you should write which program caused this error. I often had errors from services.exe ("The program services.exe made an exception. blablablala") during startup. But it was only on close-to-stock ROM with 21877 build. When I changed to 21913 it stopped. Soe I guess the cause can be in many different places. I would look among SYS packages first. But can also be any of the programs (but only the ones that start together with the system).
Please write something more (phone model, build no, and what is the basis for your ROM - dump or building from scratch). Is you took a stock ROM dump as the basis I guess you have to modify one thing after another flashing each time and then you will know exactly what caused this error...
Please write something more (phone model, build no, and what is the basis for your ROM - dump or building from scratch). Is you took a stock ROM dump as the basis I guess you have to modify one thing after another flashing each time and then you will know exactly what caused this error...
Okay, I'm sorry that I had not given that info.
The device is a HTC HD Mini, with build 23103. My basis was a dump from a stock ROM (RUU_NLD_1.36.404.1_blablabla.exe). I get the problem when I hit my Talk-button Or when I try to start my phone in CommManager.
But I can't get it, with osKitchen I have not had this problem, and for now I'm only disabling some packages...
The device is a HTC HD Mini, with build 23103. My basis was a dump from a stock ROM (RUU_NLD_1.36.404.1_blablabla.exe). I get the problem when I hit my Talk-button
Or when I try to start my phone in CommManager. But I can't get it, with osKitchen I have not had this problem, and for now I'm only disabling some packages...
I'll try that tonight! Thanks for the hint, hope it works. But then, what package (that isn't included) should be re-added? I can't imagine it's CoPilot...
take a look at the packages.sof/cif tips in post 2.
this problems can be caused by build order of packages.
this problems can be caused by build order of packages.
This kitchen looks really good and much easier to use than any other. Unfortunately, I've got a problem with it. I'd like to customize one ROM which I like (only add some more stuff I use and remove what I don't use), so I made a dump from nbh, but when I try to open the dump folder in os builder mode, I get an error: "SYS: Metadata package not found". What do I have to do to be able to customize a complete ROM? BTW it's Blackstone Cloudy 0.4 WM 6.1 + Sense 2.5.
Thanks in advance.
Thanks in advance.
Never mind... I have no experiences with building a ROM so I better start with a stock ROM first Thanks
Thanks
this kitchen is showing you the problem. that's one of many benefits.
import metadata package from the same build you want to cook in.
then edit/reorder packages.sof/cif with built in editors.
if you don't have cooking experience, you better start off with a stock rom.
this kitchen doesn't make you a experienced chef. you have to learn with it and gain experience.
the best practice for me was to build hybrid roms for the x1i with packets from hd2 (was not released yet at the given time).
i saw so many errors myself and flashed my devices hundreds of times.
i like to share my experiences with everyone. feel free to ask if you have any questions.
but remember:
if you have problems, they are caused by your work in the kitchen and not the kitchen itself.
don't blame the kitchen for errors first. my rom is working very well (many others are successfully using it too).
btw:
when i ported my evk/prb based kitchen to osbuilder structure, osbuilder was showing me dozens of problems that i had to fix (evk showed no problems at all).
it's always better to know the problems and to fix them. i don't really like the fact that they where simply ignored by prb-based kitchens.
import metadata package from the same build you want to cook in.
then edit/reorder packages.sof/cif with built in editors.
if you don't have cooking experience, you better start off with a stock rom.
this kitchen doesn't make you a experienced chef. you have to learn with it and gain experience.
the best practice for me was to build hybrid roms for the x1i with packets from hd2 (was not released yet at the given time).
i saw so many errors myself and flashed my devices hundreds of times.
i like to share my experiences with everyone. feel free to ask if you have any questions.
but remember:
if you have problems, they are caused by your work in the kitchen and not the kitchen itself.
don't blame the kitchen for errors first. my rom is working very well (many others are successfully using it too).
btw:
when i ported my evk/prb based kitchen to osbuilder structure, osbuilder was showing me dozens of problems that i had to fix (evk showed no problems at all).
it's always better to know the problems and to fix them. i don't really like the fact that they where simply ignored by prb-based kitchens.
Last edited:
You're damn right!
In case of Rhodium the 2.07 European stock ROM was the worst that I ever had on my device. But it was enough to dump it with OSBuilder and rebuild without any changes and the ROM was better already (by means of memory management)!
Then I started to play with XIP optimization (I read whole thread of manual XIP porting but I'm not really a computer guy so I couldn't understand everything) and I was surprised with the XIP porting tool. No more memory region calculation when you want to remove a file/package from XIP! It's just enough to uncheck it from the XIP tab in Settings, and click "Port XIP" and the tool will assemble the XIP for you!
My good friend Jackos says you should always have control on the memory allocation. But before I can learn everything about it, I can use a good OSBuilder.
The Registry tool is awesome. When it detects error, it indicates in which file the error is, and what kind of error and even the line number. So if anybody of you have problems with registry compili (building .hv files), please go to Additional Tools -> registy preview! This tool will show you what is the problem.
Additionally for every value it also shows which files in which packages changed this value. So if you ever cook your reg tweak which doesn't seem to work after you flash a ROM, go to Registry preview, navigate to the tweaked value, and you will see which package overwrites your changes!
BTW. I think the kitchen installer have errors. I wanted to install the kitchen on my laptop and I already had .NET Framework 4 installed, but the installer hasn't detected it and required to install .NET v3.5, so I had to install .NET v3.5, install the OSBuilder, and then install .NET v4. Could you guys confirm or deny?
In case of Rhodium the 2.07 European stock ROM was the worst that I ever had on my device. But it was enough to dump it with OSBuilder and rebuild without any changes and the ROM was better already (by means of memory management)!
Then I started to play with XIP optimization (I read whole thread of manual XIP porting but I'm not really a computer guy so I couldn't understand everything) and I was surprised with the XIP porting tool. No more memory region calculation when you want to remove a file/package from XIP! It's just enough to uncheck it from the XIP tab in Settings, and click "Port XIP" and the tool will assemble the XIP for you!
My good friend Jackos says you should always have control on the memory allocation. But before I can learn everything about it, I can use a good OSBuilder.
The Registry tool is awesome. When it detects error, it indicates in which file the error is, and what kind of error and even the line number. So if anybody of you have problems with registry compili (building .hv files), please go to Additional Tools -> registy preview! This tool will show you what is the problem.
Additionally for every value it also shows which files in which packages changed this value. So if you ever cook your reg tweak which doesn't seem to work after you flash a ROM, go to Registry preview, navigate to the tweaked value, and you will see which package overwrites your changes!
BTW. I think the kitchen installer have errors. I wanted to install the kitchen on my laptop and I already had .NET Framework 4 installed, but the installer hasn't detected it and required to install .NET v3.5, so I had to install .NET v3.5, install the OSBuilder, and then install .NET v4. Could you guys confirm or deny?
Another question How can I change the place where files are being copied to? Because now my Start Menu is a mess and I want to get some .lnk files into folders that are created in initflash.
In osKitchen I have a app.dat file for each package that I can modify very easy, but I can't seem to find them here...
How can I change the place where files are being copied to? Because now my Start Menu is a mess and I want to get some .lnk files into folders that are created in initflash. In osKitchen I have a app.dat file for each package that I can modify very easy, but I can't seem to find them here...
_Madmatt, initflashfiles.txt in OEM package = app.dat in EXT package. Is that what you wanted to know? Or I misunderstood your question?
I think you misunderstood. I can find the initflashfiles.dat file, but in OsKitchen, there are app.dat files foreach EXT package you have. So, let's say Office for example. In the Office's app.dat I can see every file that will be copied to let Office work. For example, it will copy the .lnk file to \Windows\Start Menu\Office\.
That's fine automatically, but ActiveSync for example, is just in \Windows\Start Menu and I want it to be in \Windows\Start Menu\Extras. In osKitchen it was just a matter of editing one single line... Now I can't find that line
Besides of the "central" initflashfiles.dat file from Base_Lang package there are individual initflashfiles.txt in every OEM package which is an equivalent of the app.dat from EXT.
EDIT: in attachment I present a sample package of HD2 Proximity Sensor Screen Off... I think it's self-explanatory.
EDIT: in attachment I present a sample package of HD2 Proximity Sensor Screen Off... I think it's self-explanatory.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
29Official XDA OSBuilder kitchen thread (developed by Barin)
this thread is dedicated to discussions related windows mobile
Official XDA OSBuilder 7 kitchen thread (developed by Barin)
this thread is dedicated to discussions/info related to windows phone 7
I'm honored to be allowed to officially announce/present/support osbuilder here in xda forums by barin. thank you.
this is a new kitchen (not based on old platform rebuilder) developed by asusmobile.ru member barin and tested by many others (mentioned below) including myself.
ultrashot is also developing some parts of osbuilder (custom imgfsfromdump with advanced parameter support for example).
"One word: SUPERIOR!" hd2owner
OS Builder V1.4.236 FULL (01.12.2012) - 3962+ downloads
OS Builder V1.4.235 FULL (25.11.2012) - 271 downloads (20590)
OS Builder V1.4.234 FULL (22.11.2012) - 91 downloads
OS Builder V1.4.223 FULL (02.10.2012) - 931 downloads
OS Builder V1.4.209 FULL (19.05.2012) - 2155 downloads
OS Builder V1.4.206 FULL (21.04.2012) - 531 downloads
OS Builder V1.4.205 FULL (16.04.2012) - 199 downloads
OS Builder V1.3.199 FULL (09.12.2011) - 4792 downloads
OS Builder V1.3.189 FULL (08.11.2011) - 1762 downloads
OS Builder V1.3.187 FULL (03.11.2011) - 159 downloads
OS Builder V1.3.163 FULL (29.09.2011) - 2183 downloads
OS Builder V1.2.157 FULL (20.09.2011) - 257 downloads
OS Builder V1.2.153 FULL (15.09.2011) - 157 downloads
OS Builder V1.2.148 FULL (04.09.2011) - 558 downloads
OS Builder V1.2.143 FULL (28.08.2011) - 412 downloads
OS Builder V1.2.140 FULL (21.08.2011) - 229 downloads
OS Builder V1.2.133 FULL (11.08.2011) - 337 downloads
OS Builder V1.2.124 FULL (28.07.2011) - 423 downloads
OS Builder V1.2.116 FULL (27.06.2011) - 1716 downloads
OS Builder V1.2.111 LE (08.06.2011) - 518 downloads
OS Builder V1.2.107 LE (05.03.2011) - 970 downloads
OS Builder V1.2.101 LE (21.02.2011) - 582 downloads
OS Builder V1.2.99 LE (19.02.2011) - 213 downloads
OS Builder V1.2.89 LE (31.12.2010) - 1244 downloads
Total osbuilder downloads on xda: 24552+
ATTENTION!
SINCE VERSION 1.2.81 (06.12.2010) OSBuilder IS DEPENDENT OF .NET FRAMEWORK 4 (runtime version not lower than 4.0.30319). Get .NET framework 4 here
DOWNLOAD (latest public osbuilder version by barin): OSBuilderSetup1.4.236-FULL.zip
OSBUILDER LATEST CHANGELOGS ->POST 3 & POST 4
NEW XPH COMPRESSION METHOD FROM WP7 MANGO
Since 1.2.153 we have possibility to use xph compression from wp7 mango (patched by ultrashot).
only usable on armv7 devices!! don't use xph on older arm devices! it won't work.
if you have a armv7 device and want to try xph->ultrashot's patched mango cecompr.dll thread
If someone wants to donate and help the project, take a look at the original thread on asusmobile.ru and the thread on mobileunderground.info
Many thanks to those, who helped to test osbuilder:
Alexx~, AndrewSh, greench, Lost_Angel, Vladimir1973
Special thanks to yad for the important and necessary information on relocation.
ENORMOUS thanks to alexx~ for many ideas and concepts, for THAT NOT VALUED! aid during the testing, and it is simple for the human support from the beginning also to the end of writing program.
Basic purpose of osbuilder
-assembling flat dump from the packets
-assembling IMGFS
-assembling ROM-File (for supported devices)
-extract/dump ROM-File (for supported devices)
OSBuilder can build NB0, NB and NBH files and for supported devices it can change rom version, date and/or some other data.
Also many other functions are included (Manila other language exclusion for example), which can be useful during creation and assembling of dump and ROM.
Basic possibilities
1. The group of packets (4 types of groups, the level of the nesting of groups is theoretically not limited, packets they are grouped by simple haul) and mapping packets and groups in the form of the tree
2. Convenient contextual menu for the work with the packets.
3. Selection of language for the piercing (co-existence of packets for the different languages)
4. Possibility to introduce detailed description for the packets and the groups (with the selection of packet or group description it will be automatically mapped into specially [otvedennom] for this window)
5. Import of configuration from the files of option.xml and their subsequent removal.
6. Retention of the configuration on silence and of any quantity of the configurations
7. Editing of dsm, rgu, initflashfiles, provxml of packet directly from the program
8. Possibility of the connection of external editors for dsm, rgu, initflashfiles, provxml
9. The survey of the folder of packet directly from the program (on silence conductor is used, but the connection of another file- manager is also possible)
10. Editing of boot.rgu, packages.sof, packages.cif, defaultcerts.dat, oem.cer directly from the program.
11. Survey and the editing of the order of assembling the list (it edits packages.sof)
12. The preliminary survey of the list, which must come out after assembling with the indication as and how often changed each parameter, such as file of rgu made change and in what line of the file of rgu this parameter is contained.
13. The preliminary survey of the file of initflashfiles.dat, which must come out after assembling.
14. Removal of files from modules and imageinfo.txt
15. Sufficiently flexible tuning of the parameters of assembling.
16. Possibility of the call of external programs from the menu.
17. Automatic forming or correction .VM and .ROM according to the data from the template or the file XIP
18. Built-in mechanism of readdressing the modules (Reloc) of the received flat dump.
19. Assembling the file of division IMGFS 20. Assembling file ROM - size of nb0 (payload)
program-window:
Contextual menu of the packet Built-in editor OF DSM (title)
the built-in editor OF DSM (modules and files)
the built-in editor OF DSM (dependence) information about the module Menu of additional tools
the editor of packages.sof (cif) Preliminary survey of list cleaning the modules Readdressing modules (Reloc) Tuning (parameters of assembling)
Program (assembling the files of payload NBH) is successfully tested with following HTC-devices:
HTC blueAngel
HTC touch 2 (Mega)
HTC touch of 3450 & 3452 (Elf of & Elfin)
HTC touch Of diamond
HTC touch HD
HTC touch diamond 2
HTC max 4G HTC Of iolite
HTC HD2
HTC HD mini
HTC kovsky (SE X1)
HTC WhitestoneW
If you have precise information about the special features of a certain new device model (structure of divisions and FLASH of regions, the signs of the search for date and version into nk.exe, and also other special features, for example, necessary whether to prescribe somewhere into nk.exe the sizes of rom, region etc, then the support of this can be added into osbuilder.
As to gather the dump without the template i tried to make the process of editing and assembling far more convenient and more visual. the result is osbuilder.
If you have ideas for improvements, write them down here and barin will take a look at them.
Tutorial Videos:
01-DumpNBH.zip
02-Grouping.zip
Manual:
WWE Manual Download Link
Multibuild feature (use more than one sys build):
http://www.mobileunderground.info/showthread.php?t=12348&p=42486#post42486
Porting XIP:
http://www.mobileunderground.info/showthread.php?t=12348&p=38546#post38546
http://www.mobileunderground.info/showthread.php?t=12348&p=38615#post38615
http://www.mobileunderground.info/showthread.php?t=12348&p=38829#post38829
Setting Package Build Order:
http://www.mobileunderground.info/showthread.php?t=12348&p=38558#post38558
Exclude/Include specific packages:
http://www.mobileunderground.info/showthread.php?t=12348&p=38622#post38622
OEM creator for EXT to OEM Conversion (another tool by ultrashot coming soon):
http://www.mobileunderground.info/showthread.php?t=12348&p=38919#post38919
Getting Started:
http://www.mobileunderground.info/showthread.php?t=12348&p=38859#post38859
List of supporters (fullversion):
Code:Alexx ~, AndrewSh, HD2Owner, 3D MASTER, ash172, bitje, Elesvil, erickwill, Feropont, fq3803, Gangsta-P, Pgreench, GUG, Hellonasty, indagroove, Kristof Petho, LiquidStorm, mishok_006, mondi, Mor-Da, MorzeCBP, mwalt2, NarkoZ, NightOWL, Petrovych, rewwps, Satan!, serfer222, SergeyLAR, tian tian, ultrashot, usv, Hacker, Zloy Pryanik, Vladimir1973
Other great tools by barin:
OS Builder 7 (WP7 Kitchen)
LEO Advanced ROM Update Utility
Titan Advanced ROM Update Utility
Mozart Advanced ROM Update Utility
Blackstone Advanced ROM Update Utility
Topaz Advanced ROM Update Utility
Kovsky Advanced ROM Update Utility
Whitestone Advanced ROM Update Utility
HTC Splash Tool
My projects:
HD2O ROM Series
X1O ROM Series
HTC HD2 stock ROM overview thread
Latest Opera 9.70 thread
HD2 WP7 donation fund for da_g
HD2 haret/linux/android donation fund for devs (cotulla, dcordes, markinus, letama, netripper)
HD2 6.5.3 global bold font fix (by ultrashot)
HD2Owner's youtube channel
