Edit: New version available! Compatible with Kaiser, Titan, Artemis, Hermes etc.
New version 2.1rc2! This is a major upgrade to version 2.0 (and a bugfix to 2.1rc1). The ImgfsTools now support generating ROMs for Kaiser, Hermes, Titan, Artemis and probably quite some more. All Hermes-specific code was replaced with code working for all devices
The new version is attached to this post.
These are the screenshots of the original version. Have a look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a completely unmodified LVSW edition WM6. It usually has 47 MByte Storage....
What happened? Well, the IMGFS partition (a.k.a. OS.nb) has 8 MByte free space. Until now it was not possible to shrink the IMGFS partiton and enlarge Storage in return, so that space was wasted.
This has changed - now also on the Kaiser!
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size. The result is what you see above.
This is an excerpt from the ReadMe file from the new version 2.1rc2:
ImgFS Tools Version 2
================================================================
(Current version: 2.1rc2)
What it is
==========
These little programs help you with cooking your own ROM. They allow you to unpack an OS.nb file into individual files as you'd find them on your device, and to re-pack them into a new OS.nb which you can flash to your device. Of course, betweem unpacking and re-packing, you'll want to add/modify/remove some of them.
The tools are enhanced versions of mamaich's imgfs_tools - a huge Thank You goes to mamaich for creating them, and also for releasing the source code!
The most significant enhancement is that the IMGFS inside the generated OS.nb is no longer of fixed size, but is as small as possible. This means: the more of the unpacked files you remove before re-packing, the smaller it'll get and consequently the bigger your Storage memory will become. Also, the tools are no longer device-specific and should also work other devices than the Hermes.
*** WARNING: ***
Before you flash a ROM created with these tools, make sure you know how to recover from a non-booting ROM! For Hermes and Kaiser, you should install a HardSPL before you use these tools! I accept no responsibility for bricked devices!
Supported devices
=================
These tools have been tested on HTC devices only, and are known to work on Hermes, Kaiser, Titan and Artemis. Other devices were not tested and may or may not work.
If you want to try, I will gladly support you. However, I cannot accept responsibility for bricked devices!
How it works
============
On a high level, this is the chain of actions needed to unpack OS.nb:
RUU-signed.nbh ---(*NBHExtract)---> OS.nb ---(NBSplit)---> OS.nb.payload -->
--(ImgfsFromNb)---> imgfs.bin ---(ImgfsToDump)---> 'dump' directory
At that stage, you will want to edit the 'dump' directory. I recommend using bepe's excellent *Package Tool for this.
The reverse process is:
'dump' directory ---(ImgfsFromDump)---> imgfs-new.bin ---(ImgfsToNb)--->
OS-new.nb.payload ---(NBMerge)---> OS-new.nb ---(*NBHGen)--->
RUU-signed-new.nbh
(The tools marked with '*' are not part of the ImgfsTools, but are also available for free from xda-developers.com. There is also one additional tool, NBInfo, in this package.)
Version History
===============
2007-10-17 2.1rc2
ROMs generated by 2.1RC1 would not boot if created with a certain combination of parameters. Fixed.
2007-10-14 2.1RC1
Major overhaul:
- All Hermes-specific assumptions (like the sector size being always 0x200) are now gone.
- "conservative" mode added to ImgfsToNb and NBMerge
- on devices that have only two MSFLSH flash regions, ImgfsToNb overwrote a few bytes in the XIP section, causing unpredictable results. This was fixed.
- Removed "-emu" support from NBSplit and NBMerge, as this didn't work with WM6 emulator images.
2007-03-18 2.0 RC 2
All tools now linked statically to the MS runtime library, no longer needs DLL. No other changes.
2007-03-18 2.0 RC 1
Initial Release. Starting with version 2 to not collide with mamaich's version numbers.
===================
Enjoy!
Cheers
tadzio
Great job tadzio,
Looking forward to this new tool.
tadzio said:
Have a look:
This is a completely unmodified LVSW edition WM6. It usually has 47 MByte Storage....
What happened? Well, the IMGFS partition (a.k.a. OS.nb) has 8 MByte free space. Until now it was not possible to shrink the IMGFS partiton and enlarge Storage in return, so that space was wasted.
This has just changed!
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size. The result is what you see above.
This currently runs on my TyTN with boot loader 1.10 OliPro. I haven't had a chance to test it with other configurations, but I see no reason why it shouldn't work.
I do not plan to offer any cooked ROMs myself, as there are many excellent chefs in this forum already. But I would think a new approach to ROM cooking may emerge: make a ROM as small as at all possible, removing anything that users may not want, and turn every removed feature into a .cab that users can install to Storage (bepe's excellent Package Tool makes this very simple!). This will give maximum flexibility without wasting any memory.
Give me one more day to write up the documentation, and then I'll upload the new Imgs Tools version.
Cheers
Daniel
Click to expand...
Click to collapse
sounds great man,
once your instructions are posted I will use this technique for Black version 1.2.
Well Done,
Cheers,
Well done man
Waiting for your great work....
tadzio said:
Have a look:
This is a completely unmodified LVSW edition WM6. It usually has 47 MByte Storage....
What happened? Well, the IMGFS partition (a.k.a. OS.nb) has 8 MByte free space. Until now it was not possible to shrink the IMGFS partiton and enlarge Storage in return, so that space was wasted.
This has just changed!
I modified mamaich's ImgfsTools so that they now create the smallest possible OS.nb from a 'dump' directory, and also write the partition table and MSFLSH header matching the new size. The result is what you see above.
This currently runs on my TyTN with boot loader 1.10 OliPro. I haven't had a chance to test it with other configurations, but I see no reason why it shouldn't work.
I do not plan to offer any cooked ROMs myself, as there are many excellent chefs in this forum already. But I would think a new approach to ROM cooking may emerge: make a ROM as small as at all possible, removing anything that users may not want, and turn every removed feature into a .cab that users can install to Storage (bepe's excellent Package Tool makes this very simple!). This will give maximum flexibility without wasting any memory.
Give me one more day to write up the documentation, and then I'll upload the new Imgs Tools version.
Cheers
Daniel
Click to expand...
Click to collapse
Brilliant! Truly BRILLIANT!
good job!!!!
That would be great findings for upcoming roms. For curiosity sake, are there any initials for increasing phone storage from extended rom. Cheers.
That's just great... We're all going to run for the smallest ROM possible ! Even maybe strip out Windows Media Player (We all use other players...) and some of the useless aplications (Who uses Solitaire or Bubble Breaker ?)
who uses Solitaire or Bubble Breaker
Hey. Don't knock it till you've tried it!
But I still wouldn't mind if it was in a .cab
Good job buddy... Looking for your good news.
I just added ImgfsTools2.zip to the first post of this thread.
Disclaimer: I only tested this with my Hermes. Please be careful if you use it with other devices. Oh, and it can't hurt to be careful even with a Hermes!
Feedback welcome! If you run into any problems with these tools, please post in this thread!
Enjoy!
Daniel
Am I right that embedding things into the ROM makes them run slightly faster? Some things that everyone will use would be better off kept into the ROM in that case, which would bring in the disagreement of what everyone thinks should be included. It would be very intresting to see if someone can build a completely pure OS though.
Percz said:
Am I right that embedding things into the ROM makes them run slightly faster?
Click to expand...
Click to collapse
Glad you asked.
If by "things" you mean applications, the opposite is true.
As code cannot be executed directly from NAND flash, everything has to be copied to RAM before execution (the term XIP - eXecute In Place - is misleading here. There is no true XIP in a Hermes). Some executables and DLLs are stored as "modules" in ROM, i.e. already prepared to be copied "as is" to RAM. Moving these from ROM modules to normal files in Storage will indeed make them load slower, although once loaded execution will be the same speed.
However, applications are not stored as modules. Even in ROM they are normal files, and speed-wise it makes absolutely no difference if they are loaded from ROM or Storage into RAM.
But there is one more important aspect: the size of the Windows directory. Even Microsoft admits that having 1800 files in one directory slows the device down significantly. And unfortunately, all files in IMGFS are in the Windows directory (with initflashfiles.dat, you can only copy them elsewhere, not move them).
So, if we manage to remove as many files and apps as possible from the ROM (and hence the Windows directory), and package them into .cabs in a way that they get installed into directories other than Windows, I would think we would see some increase in speed, since accessing the Windows directory would be quite a bit faster - and I guess the OS accesses that directory rather often.
At the moment, this is only theory. I haven't tried to prove it yet.
Cheers
Daniel
Great work, i'm looking forward to new roms being cooked with more storage.
sounds like this is what the chefs need
kjs30 said:
Great work, i'm looking forward to new roms being cooked with more storage.
sounds like this is what the chefs need
Click to expand...
Click to collapse
this chef has strapped this carving knife to his waist.
Alcibiade said:
That's just great... We're all going to run for the smallest ROM possible ! Even maybe strip out Windows Media Player (We all use other players...) and some of the useless aplications (Who uses Solitaire or Bubble Breaker ?)
Click to expand...
Click to collapse
Leave few things in there. whats the point of having all that memory with nothing in it. I love bubble breaker.
Also as mentioned it would be great if we can merge ExtRom into main memory.
Nice work!
I'm happy your modified OS.nb boots for everyone
piopawlu said:
I'm happy your modified OS.nb boots for everyone
Click to expand...
Click to collapse
And thanks again for pointing me to the right place (the partition table). Without your help it'd probably have taken me a lot longer!
Cheers
Daniel
rv1nd said:
Leave few things in there. whats the point of having all that memory with nothing in it. I love bubble breaker.
Click to expand...
Click to collapse
The point is that you can decide what you want to put in there without having to cook your own ROM.
Also as mentioned it would be great if we can merge ExtRom into main memory.
Nice work!
Click to expand...
Click to collapse
I'm thinking about that. Should be do-able.
Cheers
Daniel
Related
The following is what I did to make this ROM flash by romupdate:
I'm at the moment still searching for the right hex address but when I replace the whole header of NBH file then I can flash it.
The only think is that the size of the storage in OS is then small.
Think with me to solve this issue.
I'm not familiar with hexediting file (i can do only if someone tell me how), but i need find way for flash rom < 50 Mb.
I'll try to ask in my gang
Can you tell me exactly what byte you changed and with which byte?
So this actually causes the size of the Storage to shrink? You no longer get the 60mb free that you did from doing it through the sd card?
Yes this is the problem.
The hex address that I change is 0x163 in NBH file.
At the moment our goal is to find a way around this storage limitation.
ivanmmj said:
So this actually causes the size of the Storage to shrink? You no longer get the 60mb free that you did from doing it through the sd card?
Click to expand...
Click to collapse
We could try tom's methode (change pagepool by activesync) but WM6.1 is not realy the OS to do that.
What I mean is:
1. Change the hex value in NBH.
2. Flash it.
3. Use tom's method but change the hex value of 0x163 address
But the issue is WM6.1
NikMel said:
We could try tom's methode (change pagepool by activesync) but WM6.1 is not realy the OS to do that.
What I mean is:
1. Change the hex value in NBH.
2. Flash it.
3. Use tom's method but change the hex value of 0x163 address
But the issue is WM6.1
Click to expand...
Click to collapse
The Pagepool would only touch the Program Memory, not the storage memory.
We have to bypass the flasher's size requirement check.
What I mean by tom's method is that we change the hex value in NBH file then flash it. After that try to change the hex value using tom's method.
tom changes pagepool by activesync and we can change the size of storage by activesync.
NikMel said:
What I mean by tom's method is that we change the hex value in NBH file then flash it. After that try to change the hex value using tom's method.
tom changes pagepool by activesync and we can change the size of storage by activesync.
Click to expand...
Click to collapse
hmm... interesting theory... Sounds promising!
EDIT: Just thought of something. Once it gets flash into the device it's no longer an NBH... it's more like a os.nb then... the hex value wouldn't exit there, then, would it?
We need to dump a ROM that's has not been modified and one that has and look at not only the os.nb but ALL of the files that the phone dumps. If you can flash by sd, you can do that. If not, then we'll have to install a ROM that's just big enough to pass the limit and one that's much bigger.
Actually increased storage isn't everything (though nice).. The less amount of files in the OS image the faster the ROM works. There is lot's of files in ROMs most people don't use. Even things like simply html based help files etc.. If this limit can be breached ROMs can be faster or filled with more stuff without comprimizing storage size.
I myself want to replace my Artemis this year and am tempted for the Kaiser, if only those videodrivers get fixed. Till then there is no capable replacement..
sparcle said:
Actually increased storage isn't everything (though nice).. The less amount of files in the OS image the faster the ROM works. There is lot's of files in ROMs most people don't use. Even things like simply html based help files etc.. If this limit can be breached ROMs can be faster or filled with more stuff without comprimizing storage size.
I myself want to replace my Artemis this year and am tempted for the Kaiser, if only those videodrivers get fixed. Till then there is no capable replacement..
Click to expand...
Click to collapse
I know. That's why I make small clean ROMs only, but I figured that I might as well find a way around the limit since I loose so much empty space in my ROMs.
We have to figure out a way get the RUUupdateUtil to ignore that address... What was it originally and what did you change it to?
Storage Memory Reduced
Hi... I don´t know if this is the correct place to ask next question but I haven't found where to put it, so, I hope you can help me with this matter:
I have a Gigabyte GSmart i350 (256MB rom, 64MB ram, wm6) and storage capacity showed only 142.24MB, do you know if it is normal to be reduced that capacity?... I know 256MB on real store is 244MB, but it seems to be extremely reduced ... by the way, on a different topic, how could I start a Thread on this forum?... Thanks in advance...
Xilsoh said:
Hi... I don´t know if this is the correct place to ask next question but I haven't found where to put it, so, I hope you can help me with this matter:
I have a Gigabyte GSmart i350 (256MB rom, 64MB ram, wm6) and storage capacity showed only 142.24MB, do you know if it is normal to be reduced that capacity?... I know 256MB on real store is 244MB, but it seems to be extremely reduced ... by the way, on a different topic, how could I start a Thread on this forum?... Thanks in advance...
Click to expand...
Click to collapse
That's not an Artemis, in fact I don't even know if it's an HTC phone. But as far as space goes, out of that 244mb, you have all the stuff that the manufacturer puts in there and then there's the OS and other stuff stored in it. Most phones have a shared memory for all storage, both your storage and system files. That DOES seem kind of low, though. You'll have to find a forum dedicated to that particular phone, though. Do you know who manufactures it? (Or does Gigabyte itself make it?)
NikMel said:
...
What I mean is:
1. Change the hex value in NBH.
2. Flash it.
3. Use tom's method but change the hex value of 0x163 address
...
Click to expand...
Click to collapse
It's a good idea, but with a problem...
tom's method rewrite an address in flash, this address is the same in OS.nb, so we can change pagepool size or in os.nb or on-the-fly with tom's method...
changes in nbh files have different results, becouse nbh is a compressed file that could include too much info that are written in flash... In this case, the address 0x163 is only for ruu, but not really written directly in flash...
we must know where is storage this value in flash!!!
cesconoa said:
It's a good idea, but with a problem...
tom's method rewrite an address in flash, this address is the same in OS.nb, so we can change pagepool size or in os.nb or on-the-fly with tom's method...
changes in nbh files have different results, becouse nbh is a compressed file that could include too much info that are written in flash... In this case, the address 0x163 is only for ruu, but not really written directly in flash...
we must know where is storage this value in flash!!!
Click to expand...
Click to collapse
In fact, i've tried another thing:
creating an nbh file with only os, at address 0x162-0x163 correspond values D4 02
creating an nbh file with radio, splash and os, the values D4 02 don't correspond to address 0x162-0x163 but they are in address 0x16A-0x16B
It means this part of nbh informs ruu.exe what (and where) is included in the file, but how ruu.exe processes this info is not clear...
cesconoa said:
In fact, i've tried another thing:
creating an nbh file with only os, at address 0x162-0x163 correspond values D4 02
creating an nbh file with radio, splash and os, the values D4 02 don't correspond to address 0x162-0x163 but they are in address 0x16A-0x16B
It means this part of nbh informs ruu.exe what (and where) is included in the file, but how ruu.exe processes this info is not clear...
Click to expand...
Click to collapse
We have to modify how the RUUUpdateUtility acts after checking that memory address. I've been trying to track the file through a debugger but thus far have had no luck.
Waiting RUU solution, i flashed using Cesconoa method HERE, that solved problem for SD flashing not running with slow SD.
Not the best i could obtain, but it's good result.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Without AS and My Mobilier (for shoot) Program memory is 28 Mb
I think easy obtain 70 Mb for storage (i don't cleaned very well)
bigix1,
WM5torage has no effect on flashing by SDcard.
This software changes application layer settings. SDcard flashing is a lower level access then wm5torage.
bigix1 said:
Waiting RUU solution, i flashed using Cesconoa method HERE, that solved problem for SD flashing not running with slow SD.
Not the best i could obtain, but it's good result.
Without AS and My Mobilier (for shoot) Program memory is 28 Mb
I think easy obtain 70 Mb for storage (i don't cleaned very well)
Click to expand...
Click to collapse
I try to be more clear:
with most popular SD card we are not able to flash from SD: they are too great and for this slow to go on (probabily need more energy).
WM5Torage is used to create partition on SD from PC.
With a little partition (i used 1 Gb Sd for make 2 partition 100/900 mb) we are able to flash from SD. With single partition 1 Gb i'm not able to do it.
I have a 2GB sdcard High speed (not a SDHC) 2gb partition and it works.
bigix1 said:
I try to be more clear:
with most popular SD card we are not able to flash from SD: they are too great and for this slow to go on (probabily need more energy).
WM5Torage is used to create partition on SD from PC.
With a little partition (i used 1 Gb Sd for make 2 partition 100/900 mb) we are able to flash from SD. With single partition 1 Gb i'm not able to do it.
Click to expand...
Click to collapse
Placeholder for the [mu] kitchen.
DOs and DON'Ts:
DON'T:
1: DON'T ask about vista support. I'm seriously allergic to that expression. Use WinXP SP2/3 and be happy.
2: If it doesn't suit your needs, don't b**** about it and just use another one.
DOs: if you like it, say thanks.
CONSTRUCTIVE criticism/suggestions: more than welcome via PM.
^.^
### Here's the link (lzma)##############
# http://www.mediafire.com/?oufm4oq9t2v #
##############################
### Here's the link (tar+bzip2)#########
# http://www.mediafire.com/?u4tj1jsnuzt #
#############################
1: .net framework 2.0 at least needed.
2: ms vb runtimes recommended.
3: BEST uncompress with 7zip (or any app supporting lzma) / WinRAR/WinZIP to c:\
4; there is no "readme", so place your RUU_signed.nbh (and Part*.raw) into the "source" folder in the kitchen,.
5: although I tried coding it as noob-proof as possible, the kitchen DOES require some minimal knowledge about the cooking/rebuilding process.
I DON'T intend to spoon-feed you, so if you want additional features, you need to seriously catch up on some reading.
This kitchen DOES need further/extended testing, but I decided to release it after several successful tests on 2 different systems.
Nethertheless, I CAN'T possibly account for the heterogeny of every system in the wild...
I could TRY coding the "perfect" kitchen, but that would be utterly pointless, since experienced chefs use their own kitchen/or don't use frontends.
6: last but not least: even though a cooking process might've been completed, give a few seconds till you move to the next step. HDD/IO bottlenecks tend to do strange things.
^.^
The mirror/kitchen link MAY be inaccessible at times. If you REALLY need access to anything hosted, leave me a PM.
I'll provide you with another (temporary) link.
# # #
20090110 edit
Will be uploading an updated version of the kitchen maybe next week.
# # #
Pre-applaud and Pre-thanking
Thank you...................................
Thanks Cyphol.
I will of course give credit where credit is due.
What's taking me so long is that I'm trying to make the batch as easy to read as possible, all the while trying to give as much control as possible over the entire cooking process.
It should RATHER be "noob-proof".
I don't think I will finish it today, because I only have a windows box at work to test it on.
@ home I'm all unix.
^.^
adwinp said:
Thanks Cyphol.
I will of course give credit where credit is due.
What's taking me so long is that I'm trying to make the batch as easy to read as possible, all the while trying to give as much control as possible over the entire cooking process.
It should RATHER be "noob-proof".
I don't think I will finish it today, because I only have a windows box at work to test it on.
@ home I'm all unix.
^.^
Click to expand...
Click to collapse
(pre)Thanks for sharing a probably great and useful tool !
I think it will be a great kitchen because adwinp is a very hardworking man and he reads and searches a lot.
Thanks Cyphol.
I'm honoured. Though I learned a lot from you guys.
I'm nearly done with the batch file. I'll finish and test it tomorrow.
I tried giving the end user as much control as possible, even though using just one batch.
We'll see if it works.
DOS batch coding sux.
Bash rulez.
^.^
.. [reserved] .. for private use.
The [mu] ROM is coming next.
(It might take some time for me to release a ROM worth sharing with the community. I may want to wait for the next official ROM update since I'm not really satisfied with the 1.93 base).
PLEASE DON'T ask when it might be available.
^.^
Although I respect bepe's and dutty's (DP) great work, I stick with Wally regarding protecting the ROM against disasm/copying.
Meaning: No copying protections. Feel free to do with it as you please.
I won't say thanks for this kind of Kitchen. WHAT HAVE YOU DONE???
I only want to say MARVELOUS! NICE AND CLEAN! CONGRATULATIONS.
Thanks Cyphol!
The real thanks goes to the authors of the various tools this kitchen serves as a frontend to.
I doubt this is bug-free, but I hope it will be a contribution of some sort to the community I have learned so much from.
Maybe somebody will do a much better job than I did.
Sorry,
but WinRAR says the archive is destroyed.
scorpio16v said:
[...]WinRAR says the archive is destroyed.
Click to expand...
Click to collapse
Re-download and make sure your browser doesn't screw with the file extension, it's .tbz2 (tar+bzip2) otherwise your unpacker might have issues reading it.
The Archive is fine, and adwinp: the kitchen looks extremely sexy. I'm completely new to cooking and just trying it because I want a proper JVM, but I've looked at the other kitchens, and this one is the nicest so far.
If your ROM is as hot as the kitchen, I might have found myself a new base rom
cptsunshine said:
.... otherwise your unpacker might have issues reading it.
The Archive is fine...
Click to expand...
Click to collapse
You're right.
Was my WinRAR version.
Sorry for the rumour.
scorpio16v said:
You're right.
Was my WinRAR version.
Sorry for the rumour.
Click to expand...
Click to collapse
Use 7zip for any of the archive versions.
It's a fast and free archive manager, supporting lzma.
You can still uncompress the .tbz2 archive with 7zip/winrar/winzip.
Hi adwinp,
Great tool !
Thank you very much for sharing this tool !!!
I've tried it to rebuild a .nbh with some dump files associated with a RUU_signed.nbh from a stock HTC ROM.
After the first steps, all is OK (my casserole seems to smell good ) until the Build step...
I got an abort 'BuildOS.exe ....'
any idea ?
Could you post a screenshot?
Gimme a link to the stock ROM (or tell me what version it is) and I'll check it out.
OS conflict ?
Hi adwinp,
And thanks for your reply.
So, here is what I've done :
1. Copy my 4 Part0*.raw files in y=the \source folder
2. Copy the stock RUU_signed.nbh in the same folder
Notes :
> Dump files are the parts of a french ROM from Bouygues provider avalaible here : http://dl.free.fr/rkxdkK3bp
> RUU_signed.nbh file becomes from an official HTC ROM 1.37.406.1 avalaible here : http://www.4shared.com/file/5430812...io_Signed_Diamond_5226a2509_1002503_Ship.html
3. Launch mu.bat
4. select "a" to Accept
5. select "r" to Rebuilt
6. select "d" to leave it Dirty
7. select "z" to extract OS from base (OK, new folder 'casserole' with the OS.nb file)
8. select "g" to extract system files (OK, new folder 'imgfs_e' in the casserole)
9. select "y" to extract core files (OK, new folder 'xip_e' in the casserole)
10. select "p" to concatenate system (it seems good)
11. select "o" to rebuild the base...
And then, the error message :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, I've tried to use the other method with Diamond Kitchen, and I got exactly the same error when building the OS...
plus another message :
Even if I don't really know how the BuildOS step proceeded, it seems there is an OS incompatibility or conflict, right ?
I'll try to rebuild your ROM later.
A quick question though: do you have NET Framework >= 2.0 installed?
adwinp said:
I'll try to rebuild your ROM later.
A quick question though: do you have NET Framework >= 2.0 installed?
Click to expand...
Click to collapse
A quick answer though: .NET framework 3.5
Cheer,
Hello,
@ MonteCristoffOn, you've installed Microsoft Visual C + + 2008 Redistributable Package Download
Tis My turn to give back to the XDA community..
First i would like to thank:
Abusalza
CRC
Anryl
Veyka,
tai_SW
Zocster for his mirrors
Jerpelea
Kareem
PhamQuang
Assasinslament and the Tyre Kitchen
Starbase for his oem's
You will need to install .net 3.5 and Microsoft Visual 2008
My Kitchen tools as of 09/19/2008 HERE
PS: kitchen does not contain ROM And SYS folders, you can download them from post 2.
Rom Creation steps:
Your completed kitchen folder should have:
SYS Folder (Download from post 2)
OEM Folder (Included in kitchen on post 1)
ROM Folder (Download from post 2)
Tools Folder (Included in kitchen on post 1)
.BAT file for running build os (Included in kitchen on post 1)
- Edit: mxipupdate_zzPIED_100.provxml in OEM\OEMVERSION folder to put rom information.
- Edit: initflashfiles.dat in OEM_Lang_0409 folder to set directory structures and some shortcuts and folders.
- To set your custom boot screen replace: SYS\Base_Lang_0409_DPI_96_RESH_240_RESV_320\welcomehead.96.png
- To set background set SYS\base_dpi_96_resh_240_resv_320\Default_stwater_240_320.gif
- To Create Final Rom!! - After all oem's are added into oem folder run BuildNB.bat in kitchen folder.
- To set rom date:
Hex Edit os-new.nb file before creating nbh and search 2007 in nb file and set according date in first two places that come up.
Sys and ROM is your build for Windows Mobile. Technicall you can mix different rom and sys folders, I.E. ROm from 19213 and SYS from 20753. OEM is the drivers and various add ons.
Separate Items to add to sys folder can grab here: CLICKY
.net 3.5
Office
Various other goodies
Useful Links:
Link for Module and exe information
This thread is for noob chef's such as myself.
If you want to learn how to cook please feel free to ask questions, and I will do my best to help.
+ Que PPC said:
Where to place what.... first we need to know some things...
if you get the 21807... you'll get two folders... ROM and SYS
Inside the ROM Folder:
Here you will find three files os.nb.payload, ROMhdr.bin and xip.bin this three files are the Kernel but compressed.
you will got a folder called XIP, inside you will get three more OEMXIPKernel this folder has the HERMES specific modules that makes run the OS.
you will find the MSXIPkernel the second part of the build that heps the kernel to boot but specilized on the OS, not the Device, and finally... the MSxipkernel... nobodys knows why this should be inserted too, cause the carrier by this feature must update the OS but they just make new complete upgrades.
Inside the SYS Folder
The SYS is the OS... i mean all the programs updated for every build I mean... all the apps that is needed to boot and run some other apps that exist in this folder here you will find MODULES and FILES... but
How can you difference a module from a file... easy... module is a .dll or an .exe or some images but transformed to files like S000 or similar names, why to convert a file to a Module..? thats because the modules exist cause they are stored in other partition of the NAND memory of our devices... to run faster and get some more RAM or storage to dispose.
in some posts before this I wrote one, where we have said wich folders from the SYS can be deleted and dont makes issues at boot. check it!
!!!!THE KITCHEN!!!!
Where to place what?????
When you DL the kitchen you must to unrar it to a folder in C:
I use this address
C:\Hermes 21222\ here all the kitchen tools and folders
So how does your kitchen must be like... see this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
a little big to have all the deph on words...
When to use OEM and when to use EXT:
OK, the OEM folder wil be processed always! so here you will add the changes that you wish to the UI of the OS... some drivers... and the addons... this cant be skiped!
the EXT folder always will be processed but:
WHe you set on the .bat file Premium... Basic... Vanilla... all the ext packages must to have this files inside "_only_Premium" "_only_Basic" "_only_Vanilla" and the kitchen will recognize wich apps must be on Basic Premiun or Vanilla if you palce two or three files... you indicates to the Kitchen that the app must be installed on whatever build you will do.
This file can be created like this:
Make a new txt file and name it as you wish "_only_XXXXX" (XXX for the build flavor you want) inside you must to type the word "TRUE" without the quotes of course.... then save it... and erase its file extension it will say are you sure! the file could be inservible or something like that.
How to control the initial customization or setup to run the cabs:
well, if you go to this address
C:\HERMES_21222\OEM\COMMON
you will find this folder "OEMOPERATORS" inside you will find all the cabs taht will be installed after the first boot or HR, how to change them?
easy... as the SD config... there is a file called config.txt so... change the values or add a new one with the new cab you wish to install.
Insert inside the folder OEMOPERATORS the cab you want and make it HIDE on file properties to hide it on the windows folder
how to change the default cantact manager?
well the contact manager we use in this Kitchen is stored on the EXT packages find it... and change the "_only_premium" file to "_skip" and this contact manager shouldnt be installed... but remmember to add the default one in OEM or EXT, this depends on wich you find or you can made from a cab to OEM or from the OEM to EXT, there are tools that can help you make this and some tutorials here on XDA that teachs you how to do it...
The sip can be changed too in EXT just found the skin there ina folder and change the file to _skip and add your new sip collor... or get another sip and add it as EXT or OEM.
If everything is ok... run the .bat and wait a little.
I hope this can helps you. if yoou have more Q's ask here please.
+ que ppc
Click to expand...
Click to collapse
Sys, OEM, and XIP' Updated 01-18-09
Sys, OEM, and XIP's below are working and for the most part have been tested by me. (no gaurantee's though )
XIP: (bigstorage)
20753_XIP 09/19/2008
20755-XIP 09/29/2008
20758-XIP 10/18
To Make XIP/ROM Non-BigStorage or Real BigStorage:
Copy this over existing rom folder CLICKY
OEM Folder: (Updated 01-18-09)
Take Your Pick! HERE
Various Kitchen utilities for use:
see HERE
Various OEM add ins:
HERE thanks to starbase
SYS:
Choose and download HERE Updted 01-18-09
Complete Kitchens!! ready to go! updated 6-5-09
Complete Kitchens (Everything included, and ready to go)
Use at your own risk, it was restored from my hard drive.
21222 6.5 kitchen HERE
21728 SYS_XIP ported for hermes friends
21234_SYS_XIP_RTM Dumped and ported for hermes peoples
21806 SYS_XIP hexed to show 21807 by me
Sweet can't wait to try it out and I'm sure I'll have a few questions here and there haha
MrDSL said:
Sweet can't wait to try it out and I'm sure I'll have a few questions here and there haha
Click to expand...
Click to collapse
Hey Hey man. it's the only way to learn. I'm the "noob" chef and i'll learn ya all i know.
This is a news!
Cool guys
Update 09/19
Updated posts 1, and 2, should be able to get a functional build out of these tools.. i'll be uploading more sys and xip for you guys to play around with later on post 2. Keep me bookmarked!
Looks like you been busy!!
And no one seem to complaint about not getting mirrors, until someone asks I won't be making any! Is that cool?
Fantastic! Your giving me the itch to try my hand at cooking!
yea dude, my way is the noob way.. i'm telling you, it is better if you learn the manual way of cooking but i've designed this so you can drop files, edit specific points, and the run .bat and whammo you have a rom.
You da man Josh! Thanks for sharing the kitchen.
I think i can live with 4share, just hate rapid share LOL
Bugs Fixed
Reuploaded Sys 20753, bugs fixed in post 2
Normal storage roms
hi can we make normal storage roms with this kitchen if so how thanx very much keep up the gud work.
ngagephone said:
hi can we make normal storage roms with this kitchen if so how thanx very much keep up the gud work.
Click to expand...
Click to collapse
I will upload to post 2 somthing to copy to rom folder to make rom non big storage. gimme 5 mins
ok thanx just downloaded oem rar and it wont extract says its corrupt.
ngagephone said:
ok thanx just downloaded oem rar and it wont extract says its corrupt.
Click to expand...
Click to collapse
I just downloaded myself and extracted fine..
may need to put at root c:\ directory to extract due to file paths being too long.
hi sorry but were do i put the sys folder and the rom and oem folders thanx in advance.
ngagephone said:
hi can we make normal storage roms with this kitchen if so how thanx very much keep up the gud work.
Click to expand...
Click to collapse
Thanks for the comment man, Uploaded your request on post2 Just extract and copy over existing files in xip/rom folder. should work fine.
ngagephone said:
hi sorry but were do i put the sys folder and the rom and oem folders thanx in advance.
Click to expand...
Click to collapse
1 Kitchen folder is were everything goes.
REQUIRED
Kitchen folder should have:
SYS
OEM
ROM
Tools
.BAT file for running build os
Sys and ROM is your build for Windows Mobile. Technicall you can mix different rom and sys folders, I.E. ROm from 19213 and SYS from 20753. OEM is the drivers and various add ons.
Edit:: Kitchen attached on post 1 comes with working oem folder already.
Please keep the questions coming as i can add to post 1 and 2 to better explain the process. Also anything i can do to help, let me know.
ok so say i download a oem app extract it do i just put it in the oem folder and say i wish to remove net 3.5 would i just delete the folder out of the sys folder thanx.
APP made by Jason (|Jason8|)
Donate to Him!
CAB Converter v0.0.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
v0.0.1
Very basic right now
Can only be installed to Local disk. Do not try installing anywhere except the default location
Can only perform CAB > OEM and CAB > EXT
Features:
Add cabs from different directories
Able to choose EXT and OEM output
CAB > OEM
CAB > EXT
OEM > EXT (Coming soon)
Suggestions:
Resizing the app (Coming soon)
Skinnable
Compile the files into 1 executable
Description:
racer7 said:
It's finished! I've got a GUI made that utilizes existing command line tools to allow a user to freely convert CABs to OEM and EXT files!
As you can see, it's a simple GUI. However, it becomes quite powerful once you use it. The user can click and drag CABs into the listbox and they will be automatically added. Select the CABs you want to convert by clicking on them and highlighting them.
There is a library file that is needed in order to run it called COMDLG32.ocx. This is installed when the self-extracting archive is finished. That's what the batch file and library dialog that pops up is all about. Nothing to worry about.
There are no checks to see if the conversions have been successful, so that will still need to be done manually by the user. I hope to figure out a way to tell if they were successful or not eventually.
As for comments, questions, or suggestions, feel free to make them!
(By the way, I couldn't have started this project without Kraize bugging me to make his life easier. So thank Kraize, too.)
Click to expand...
Click to collapse
Kraize said:
Anyone willing to use cab2oem and EXT_PAckages_rebuilder.exe and create a GUI where a user can: select which cabs/packages he wants to convert, allow cab to oem, oem to ext, and cab to ext. It should be able to allow you to pick the input and output directory. It needs to be able to pick multiple cabs from different directories. I suck at graphics, so if someone could make a concept. This would be a great tool for rom cookers. Da_G had directed me to make batch files, but I was having problems with those not working with all cabs so I thought of and idea and hope could make it possible.
Click to expand...
Click to collapse
+1 for this! I'm sick of having to CAB2NEWKITCHEN all my cabs each time I add a new one.
Any chance the cabs you're running into an issue with are missing the setup.xml Kraize? They're the only cabs I haven't been able to convert to a package.
By the way, great work with the batch files. Cheers.
EDIT: I could probably do a concept design too but I'm leaving work soon so it'll have to wait until later unless someone beats me to the punch.
dickenz said:
+1 for this! I'm sick of having to CAB2NEWKITCHEN all my cabs each time I add a new one.
Any chance the cabs you're running into an issue with are missing the setup.xml Kraize? They're the only cabs I haven't been able to convert to a package.
By the way, great work with the batch files. Cheers.
EDIT: I could probably do a concept design too but I'm leaving work soon so it'll have to wait until later unless someone beats me to the punch.
Click to expand...
Click to collapse
Yes. Me and Jason were having problems with the ones without setup.xml files lol. But I think that's a fault of Cab2oem, but I'm not totally sure. Maybe someone more intelligent could clue us in.
The worst part was when it said there was no _setup.xml and it STILL said it couldn't convert due to a missing _setup.xml!
Anyways, working on this in VB6 (stfu, i'm a noob)
Should be able to post something up shortly!
racer7 said:
The worst part was when it said there was no _setup.xml and it STILL said it couldn't convert due to a missing _setup.xml!
Anyways, working on this in VB6 (stfu, i'm a noob)
Should be able to post something up shortly!
Click to expand...
Click to collapse
Go jason go!
I asked Chainfire, but this doesn't float his boat nor is it his cup of tea.
It's finished! I've got a GUI made that utilizes existing command line tools to allow a user to freely convert CABs to OEM and EXT files!
As you can see, it's a simple GUI. However, it becomes quite powerful once you use it. The user can click and drag CABs into the listbox and they will be automatically added. Select the CABs you want to convert by clicking on them and highlighting them.
There is a library file that is needed in order to run it called COMDLG32.ocx. This is installed when the self-extracting archive is finished. That's what the batch file and library dialog that pops up is all about. Nothing to worry about.
There are no checks to see if the conversions have been successful, so that will still need to be done manually by the user. I hope to figure out a way to tell if they were successful or not eventually.
As for comments, questions, or suggestions, feel free to make them!
(By the way, I couldn't have started this project without Kraize bugging me to make his life easier. So thank Kraize, too.)
Good stuff
Btw guys, I suggest you wait a while (say 5-6mins) before clicking OK in the message box if you have 100+ cab files. There are still some cab files that will not convert because they do not have a _setup.xml file We need to contact the dev of cab2oem and see what we can do about that.
Kraize said:
Btw guys, I suggest you wait a while (say 5-6mins) before clicking OK in the message box if you have 100+ cab files. There are still some cab files that will not convert because they do not have a _setup.xml file We need to contact the dev of cab2oem and see what we can do about that.
Click to expand...
Click to collapse
Its not just cabs that dont have _setup.xml, have had a few where in the conversion I get no app.dat or app.reg, look in the files folder and right at the top is the bloomin _setup.xml!!
B4PJS said:
Its not just cabs that dont have _setup.xml, have had a few where in the conversion I get no app.dat or app.reg, look in the files folder and right at the top is the bloomin _setup.xml!!
Click to expand...
Click to collapse
Aye. If you run that cab manually through the converters, it still won't convert. It's a problem with the converters, unfortunately. Well, to be fair, it's probably a problem with the CAB file's _setup.xml, because I'm pretty darn sure that the converter can find it if it's there.
When I get bored tonight, I'll take a look at it and see what's different between the CAB files that work and the CAB files that don't.
Bah! seems like god is playing with me..all my cabs converted...somehow o.o, I had to do a few manually, but they converted.
EDIT: These are the ones that didn't convert via the gui.
AE button plus
all programs v4.1 [3 icons]
batteryguard
beejive_fix
butler
changescreen
cleanRAM
conduits pocket player
Enhanced touch response
EzInput
G-Alarm
G-Alarm voice
Google Translator
G-Trigger
iContact
iFonz2
LenngySh_SQLCEMobile
Light audio Boost
mobile battery discharger
mobliza
netcallerv4
nuelightv3
opera v9.7 b1
remotetracker
reSTART
S2U2 v1.62
SASHIMI
Sensor Scroll
SIP Selector v3
SMS Nuke
SpaceTime
SportyPal
SSMaHo
Start button hook
touch response
touchlFLO detacher
WeatherMaster v2.2
WiFiMonster v1.0.33.66
Wizcode Defragment Mobile
lmao nice job. Added to collection.
I thought I was the only one to still use VB6. VB6 FTW!!!
Bah. Jason! Get you're lazy ass to work!
No one uses this? I surely thought this was bound to be a great idea :|
Kraize said:
No one uses this? I surely thought this was bound to be a great idea :|
Click to expand...
Click to collapse
I'm using it haha and it works flawlessly
bram_smulders said:
I'm using it haha and it works flawlessly
Click to expand...
Click to collapse
Really? For all your cabs? For me it seemed that way, but then I got an error with platformbuilder.exe and it put my rom on hold
Its not working for me but that may be because I'm on windows 7..I'm not sure yet..
thx,
just what i needed for fingermenu and fingerkeyboard.
cheers
EDIT:worked fine, time to optimize the OEM (remove QVGA files, etc)
Great tool to custom cook your own rom with app you want.... thanx a lot..
Kraize said:
Really? For all your cabs? For me it seemed that way, but then I got an error with platformbuilder.exe and it put my rom on hold
Click to expand...
Click to collapse
Till now everything works great, but i've convertet 10 cabs or so, and everything did it well.
MrDSL said:
Its not working for me but that may be because I'm on windows 7..I'm not sure yet..
Click to expand...
Click to collapse
I'm cooking on win7 build 7232 64 bit and nog problems in using this tool.
Gr. Bram
Maybe a mod can make me a Favor and add more post to this thread if needed that will be great appreciated.
I will apreciate all the support from every people that use this kitchen in hermes to allow people get the info as clearly that a noob can install this wonderfull kitchen.
!!!!!!!!!!!!!!!!English is not my native lang, so grammar could be wrong!!!!!!!!!!!!!!!
First of all...
You will need to upgrade your .net to the latest 3.5 version and install Microsoft Visual 2008 redist DL it here
Refeer to this threads to get more info.
Thanks to Hilaireg that allows me to use his tuto as base: Dude you're da man!
http://forum.xda-developers.com/showthread.php?t=521632&page=1
Thanks to Da_G to teach me on this new location of the ervius kitchen and many more important info: Man you rules!
http://forum.xda-developers.com/showthread.php?t=474406
You can get the kitchen that works for me here...
http://rapidshare.com/files/252095433/new_visualkitchen_v_1_4_only_exe___Tools_folder_dsm_editor.rar
And the Updates can be found here:
http://forum.xda-developers.com/showthread.php?t=469420
Thanks Ervius you brings a revolution here on XDA (new 10.6 allow pkg update!!! OMG this is incredible!!! no more flash NOR and NAND unlocked to store and change SYS and XIP!!!)
thanks to BEPE too, to get this to work... This three guys maybe gonna rules the world!!!
!!Starting on!!
Inspecting the Facility
This is the kitchen root preview: as we can saw in c:\XDA
Yes unrar it on C: and call it XDA to avoid the large name issues at CMD!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-----------------------------------------------------------------------------
EXT Folder
The External packages (EXT) folder is divided into Device Specific folders and a Shared folder.
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders and a Common folder.
ººOperating System Build Version Specific folders are typically used for files (packages) that should only be applied to a specific build (version) of Operating System
ººThe Common folder is typically used for files (packages) that can be installed on any Operating System build version.
-----------------------------------------------------------------------------
OEM Folder
The OEM folder can contain multiple Device Specific folders.
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
-Each Device Specific folder is further divided into Locale Specific folders and a Common folder.
ººThe Common folder is typically used for files (packages) that can be installed in any locale – not specific to a language.
ººLocale Specific folders are typically used for files (packages) that should only be applied to a specific locale.
-----------------------------------------------------------------------------
ROM Folder
The ROM folder is divided into Device Specific folders and a Shared folder.
*The Shared folder is typically used for kernel system files that are compatible amongst devices. (MSXIPKERNEL folder)
*Device Specific folders are typically used for kernel system files that should only be applied to a specific type of the device. (OEMXIPKERNEL folder)
-The Shared folder is further divided into Operating System Build Version Specific folders.
ººOperating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders.
ººOperating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-----------------------------------------------------------------------------
SYS Folder
The system (SYS) folder is divided into Operating System Build Version Specific folders.
*The Build Version Specific folders will often contain files (packages) specific to the device DPI (Dot Per Inch) and Horizontal/Vertical display size.
-Each Operating System Build Version Specific folder is further divided into a ROM DPI, ROM Resolution, and Shared folder – providing a significant amount of flexibility during ROM compilation.
ººThe ROM DPI, ROM Resolution, and Shared folders are further divided into Locale Specific folders and a Common folder.
···The Common folder is typically used for system files (packages) that can be installed in any locale – not specific to a language.
···Locale Specific folders are typically used for system files (packages) that should only be applied to a specific locale – for example, 0409 (English).
Continue...
!!!!!Setting up the ROM and SYS!!!!!
First of all:
As we most know there is a NATIVE NK from Da_G but even if I try to get it working as is... i cant... so Utak3r has been edited the OEMXIPKERNEL and its so good. Thanks man this is Great!!!
get it here http://forum.xda-developers.com/showthread.php?t=527454&page=4
This is just the XIP port... for 21815 build but as we must know:
OEMXIPKERNEL is the Kernel part that is device specific designed for... so we just gonna use this folder and of course... the "Romhdr.bin" and "os.nb.payload"
(so with this info we have the part of the kernel for every build we think to make) keep this files safe cause we gonna use it always. the xip.bin is not needed cause is not the meaning of this tutorial to port the XIP... so the kitchen wil ask for the file, instead that we dont want to port, so use the xip.bin that is on the build 23001 check the pic bellow.
The MSXIPKERNEL is the build OS specific kernel part... so...
The kitchen will takes the OEMXIPKERNEL (the native NK by Utak3r) and the MSXIPKERNEL for the build to be compiled, and we could have the kernel complete.
The MSXIPKERNELLTK folder (Logo Tool Kit) Is not needed, it has just a .DSM that allows the carrier to make important fixes and upgrades to thir ROMs (But even they didnt use it) so we dont need it anymore.
Well... we gonna set the kitchen with the BUILD 23001 so download the Port from TAI_Sw thanks a lot man! it was a great suport you had to all of us here!!
http://forum.xda-developers.com/showthread.php?t=531819
Unrar ir to a diferent folder cause we need to set this as a base...
I will use my kitchen as a base to reference... but first i will show you all the folders in SYS that has the 23001... so lets see what we got!
Folder missing!
get it here post #14: http://forum.xda-developers.com/showthread.php?t=531819&page=2
BTW: the adobeflash_Lang_0804 is not our lang so delet it too and replace it with the match lang.
And we need too the MSXIPKERNEL from this build check it on the pic
At this point we must to have this things
1.- Native OEMXIPKERNEL folder from Utak3er
2.- Native os.nb.payload file from Utak3er
3.- Native romhdr.bin file from Utak3er
4.- MSXIPKERNEL folder from Tai's 23001
5.- Xip.bin file from Tai's 23001
6.- SYS folders from Tai's 23001
7.- Ervius kitchen from my RS upload on first post
WHERE TO PLACE WHAT???!!!!
Pay attention on the place you put folders the name of the tree folder will gives you the correct place, so in the pics bellow i set at ""LEFT"" how it should be at finish and in the ""RIGHT"" the tree only for reference.
NOTE: if you see a folder on the original build ported address that you have miss to organize please ask or read again and see the pictures again. (I dont know what does the folders are for, well... maybe lots of them i knew, some others i dont...)
FIRST!!!! ROM
Set romhdr.bin, os.nb.payload and xip.bin
Set OEMXIPKERNEL
Set MSXIPKERNEL
Time to sleep tomorrow this continue...
Continue...
Second SYS!!!!!!
check the tree always you dont need to create folders I already did it!!! just paste the folders on that folders... questions at the end please
Note!!!!! In Newer Kitchens... 1.7 to date, the .VM folder must be set on the following address: """C:\<YourkitchenNAme>\OEM\<YourdeviceNAME>"""" i dont know why newer kitchens cant found the .VM folder inside the common shared sys folder... Kepp it in mind!!!
Continue... next post
Continue...
Third EXT!!!!!!!!!!!!!
Fourth OEM!!!!!!!!!!
Certainly, the kitchen ask for the OEM_LANG_0409 package and i thing all the others so... paste the whole OEM to this kitchen from the josh's kitchen.
(NOTE: For other devices.... That folders OEMDRIVERS OEMoperatorspkg,OEM LANG, can get that folders if you dump a stcok rom that is the most recommended if not... you can download a kitchen for your device that kitchen must have this folders)
Setting the .bat file for Hermes device!!!!!!!
If you make an update from the kitchen i posted(10.4) so you must to edit the .bat file as follow...
Lemme introduce y'all the quote of the guy who make this posible... (pp change) you can get from this quote the lines.
BY Utak3r:
For all those who can't get pp right:
Edit your TOOLS\kitchen_build_rom.bat and find the line with implantxip and replace it with those two lines:
..\TOOLS\osnbtool -ap xip.bin %pp%MB -y
..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -imgstart %imgstart% -%uldr% -%nocert%
Of course you have to have osnbtool.exe in your tools directory
Click to expand...
Click to collapse
To end this process lets copy the osnbtoll.exe to tools as follow
And we are good to go!!!!
WHOOO HOOOO!!!!!!!!!!!! we finish!!!!!!!!! its already set! so this is the kitchen UI, if everything was ok the kitchen launch without troubles if you saw an error check the folders it says (SVN folders don cause troubles at starting the build proces) SO just set the device, XIP, SYS EXT and OEM and select the apps to be installed or not clickng double. HAPPY COOKING GUYS!!!!
BTW i edit the build_rom.bat in the tools folder to make it for Hermes there is an option to set the ULDR but i cant figured out how to use it on hermes... the UI may change on every update so...
try it at your OWN risk IM not responsible for damages to your device
If you dont know what are you doing first ask to the bigger senior members that creates this before do anything... with this changes i made everything works fine.
If you cant even reading to understand this download the complete kitchen here:
http://rapidshare.com/files/253466344/XDA.rar
YOUR NOOB CHEF + QUE PPC
Want to donate for some pills? I will be very thankfull cause this headache is killing me.
BUILDS ported for this kitchen
"""WELL THIS IS THE POST FOR MY PORTED BUILDS"""
WM6.5
My Complete Kitchen 1.4
.23001 Kitchen
My Complete Kitchen 1.6
.23004 Kitchen
Mirror 2share
Thanks to TWOPUMPCHUMP at Kaiser
.23004 SYS MSXIPKernel
.21921 SYS MSXIPKernel
Thanks to Cofeelb for the Resize fix
.21925 SYS MSXIPKernel (Please test the rom is beta buggy hopes this works fine)
Thanks to Da_G
.23008 SYS MSXIPKernel
21828 From TOPAZ Cingular thread.
.21828 SYS MSXIPKERNEL
WM6.5.X
My Full Kitchen 1.6 Mirion B1 (the ext pkg for WOWHD is corrupted, delete it)
23034 Mirion_B1 at Rapidshare
23034 Mirion_B1 at Megaupload
Mirror 2Share
Mirror 4Share
My Full Kitchen 1.6 Mirion B4 (It has many more tools on the folder Mytools check it out!!! ready to mke a MirionB4 just load the ROM)
23053 build - Rapidshare
Ported builds Thanks to the xda-devs, xbeta, and htcpedia teams
23022 for EVK
23028 for EVK
23064 For hermes EVKMsxipkernel-23064
Inside the txt is the real link
COM5 .23504 SYS WWE+ESN+MSXIPKernel
"""Mirrors thanks to nurkamol"""
Im calling all who knows how this works to make it update constantly
Im calling to all members to read first very well ask so much more and try this paciently before do anything or ask things described above.
Thanks to all.
Last Full Kitchen 1.8.2 21609 6.5.1
Thanks to all for upgrade my ROMS
WORKING!!!! Package Repository EXT or OEM
!!!!!!!!!THE PACKAGE REPOSITORY POST!!!!!!!!!
Many Times we can xpend hours searching for EXT or OEM packages for QVGA that works with WM6.5 or 6.1, Well this post is to fill it with them just to get them fast enough to have time for sleep
If you want to share some packages... please you can post your package with a simple screenshot of the app, OS Compatible, and a lil description, I cant post warez so... if you think it is... dont even post it its better you pm me and investigate the source, I would like to post only the thested and working packages for QVGA and works for Hermes.
Thanks Guys, this space is for all of us and to offer a source even if many people has their own hosting accounts, are places where the google cant reach easily.
Keep it up!!!!
Thanks to Josh the Mod to add this!
This is the latest +Que Kitchen it has two builds from HTC Branch
Part1
Part2
Part3
play safe
Nice1
Excellent work Amigo
Now that I'm going down the road of trying to cook my own ROMS this will be invaluable.
Anything special we need to do to Maximize Program memory?
MystaMagoo said:
Anything special we need to do to Maximize Program memory?
Click to expand...
Click to collapse
Reedit resources in dlls and muis, turn off unused drivers and services, reedit all the pngs and bmps, lots of work in rgus, remove honeycomb... that's in short
utak3r said:
Reedit resources in dlls and muis, turn off unused drivers and services, reedit all the pngs and bmps, lots of work in rgus, remove honeycomb... that's in short
Click to expand...
Click to collapse
MystaMagoo said:
Click to expand...
Click to collapse
hahahahaha^^
wow Thanx QuePPC this is a GREAT job
Even if I red all the info on that threads
i cant understand the way to set this kitchen to work! hahaha so hopefully all the chefs here turns to this awsome to get this thing working! its naked! but i will continue this...! keep in touch!!!
Its truth we must to edit the images on the wm6.5 to a simplest img... when I edit them to a high def or prettier the ram decrease considerably.
BTW wich modules and dlls can deleted.. processes and so much more it could be great to know... in devices with large RAM and ROM the WM6.5 is simply awsome. 128/256.
good job with this. i seem to have everything set up properly now other than the SYS. a little more info on what goes where would be handy. my first thoughts on this kitchen are that its too complicated to set up but im still looking forward to trying this out. i got some good ideas for my next rom and i intend to do it with this dispite having my current kitchen set up perfectly just for the challenge
very good man,thank u very much,this is really helpful!
Yes FCW i will do it right now so stay on touch!
@fcw
I will set the ROM and the sys and from OEM and EXT i took josh's kitchen packages to make it easier.
@ thanks coffee i will do my best here.
UPDATE post #2 stay on touch...!!!
what does no SVN folders present mean? i think i have the kitchen set up properly, it shows all my packages in the ext rom oem and sys folders but when i try to create the rom it comes up with that
No problem with that...
I dont know what are the svn folders for but i think they gonna surprise us with something about it... cause the new 10.6 is ready for PKG update!
But your rom finish or not?
Finished
More little things to go but with this all did... you can experiment so more! ah dont change the ULDR cause this kitchen version and our os.nb.payload is not ready to do it... or it is? ask before do it please.
BTW the kitchen makes XIP PORTS and thake the OEMXIPKERNEL ported and MSXIPKERNEL PORTED to the right place just make your new folders for new builds!
Happy cooking guys!!!!
If some links or images goes down pm me or ask here for the fix...