Does anyone know how to make custom roms for devices like the Excalibur or other Smartphones. I want to remove a lot of the clutter and add some applications of my own.
JAmerican
Not there yet AFAIK.
The closest I have gotten is extracting the rom components and mixing them. I took the HTC Splash, the HTC Radio, and the T-Mobile OS; made a custom ruu and flashed successfully. Now my Dash shows HTC Screen when it boots and I have the updated Radio. I managed to dump the T-Mobile OS, but haven't been able to rebuild. HTCRT by Dark Simpson will create the ruu_signed.nbh for use with the uspl though. NBHEXTRACT will break the nbh into its components. Tried the HYPERCORE tools, that's how I got the dump of the OS, but cannot do the xip parts with these tools for some reason. PKG Tool works. Have the OEM and SYS folders, but XIP comes up empty.
This is something I hope to see... I mean why even bother with getting the HTC unbranded version if we can remove all the clutter ourselves?
momentarylapseofreason said:
This is something I hope to see... I mean why even bother with getting the HTC unbranded version if we can remove all the clutter ourselves?
Click to expand...
Click to collapse
Bug fixes! Even if you build a custom rom, you would want to start with the latest available OS to get in on whatever bug fixes have been added. Then you would rip it apart and add/remove whatever you wanted. Sometimes the new OS would also have added/improved features, but the bug fixes is the main one.
mar11974 said:
The closest I have gotten is extracting the rom components and mixing them. I took the HTC Splash, the HTC Radio, and the T-Mobile OS; made a custom ruu and flashed successfully. Now my Dash shows HTC Screen when it boots and I have the updated Radio. I managed to dump the T-Mobile OS, but haven't been able to rebuild. HTCRT by Dark Simpson will create the ruu_signed.nbh for use with the uspl though. NBHEXTRACT will break the nbh into its components. Tried the HYPERCORE tools, that's how I got the dump of the OS, but cannot do the xip parts with these tools for some reason. PKG Tool works. Have the OEM and SYS folders, but XIP comes up empty.
Click to expand...
Click to collapse
Thanks for the insight. I reached as for as extracting the .NBH into .NB files with OS, GSM etc. How do you extract these. The PKG Tool didn't work for me and the Hypercore tools aren't working right either.
JAmerican
Hey all,
I was able to downgrade to WM5 and I am starting to understand a few things regarding ROM building but I still don't know how to edit the Windows.nb or OS.nb file. Can anyone offer suggestions. I am trying to optimize it so that there is less clutter.
JAmerican
I was able to extract the the OS.nb before and edit it, but unfortunately, it was not fully extracted as i was hoping, at first i thought i was able to fully extract it, but when i tried to reflash again the OS, it was flashed normally but not as functional as normal one, many were not included, the Start Menu seems to be incomplete, no keypad lock, no quickapp etc... so i came up with a conclusion that it was not fully extracted..even the initflashfiles.dat were not present on the dumped files, i thought that file was the only one missing and i tried to manually copy it from /Windows/ directory and put it on the dumped files folder..but it wasn't a success.
Anyone successful to fully extract the OS? I'm slowly compiling a kitchen for Excalibur and the full extraction of the OS is only the missing part of the kitchen and i'm stuck with it. Once it is up and found a solution, then we can come up with cooked roms for Excalibur.
da_mayhem said:
I was able to extract the the OS.nb before and edit it, but unfortunately, it was not fully extracted as i was hoping, at first i thought i was able to fully extract it, but when i tried to reflash again the OS, it was flashed normally but not as functional as normal one, many were not included, the Start Menu seems to be incomplete, no keypad lock, no quickapp etc... so i came up with a conclusion that it was not fully extracted..even the initflashfiles.dat were not present on the dumped files, i thought that file was the only one missing and i tried to manually copy it from /Windows/ directory and put it on the dumped files folder..but it wasn't a success.
Anyone successful to fully extract the OS? I'm slowly compiling a kitchen for Excalibur and the full extraction of the OS is only the missing part of the kitchen and i'm stuck with it. Once it is up and found a solution, then we can come up with cooked roms for Excalibur.
Click to expand...
Click to collapse
Cool. I went back to WM5 to see if it was more efficient but with all the lack of features (email instant search, alpha-dialing, file syncing, etc.) It was not worth it. I went back to WM6. I hope we can get some cook ROMS soon. I really want more usable RAM. Could you give me the exact steps you used to extract the ROM? I tried HyperCore but it doesn't work for me for some reason.
JAmerican
JAmerican said:
Cool. I went back to WM5 to see if it was more efficient but with all the lack of features (email instant search, alpha-dialing, file syncing, etc.) It was not worth it. I went back to WM6. I hope we can get some cook ROMS soon. I really want more usable RAM. Could you give me the exact steps you used to extract the ROM? I tried HyperCore but it doesn't work for me for some reason.
JAmerican
Click to expand...
Click to collapse
Try this mate:
Aserg's Imgfs Tools, attached on THIS thread
Place OS.nb on the same folder then execute !UI_wwe.cmd
Choose P - Unpack OS.nb <for Herald-Prophet> to dump-folder
the ROM will be dumped on the "dump" folder, but i don't think it's a complete dump, if there's anyone knows how to do the complete dump, please share
da_mayhem said:
Try this mate:
Aserg's Imgfs Tools, attached on THIS thread
Place OS.nb on the same folder then execute !UI_wwe.cmd
Choose P - Unpack OS.nb <for Herald-Prophet> to dump-folder
the ROM will be dumped on the "dump" folder, but i don't think it's a complete dump, if there's anyone knows how to do the complete dump, please share
Click to expand...
Click to collapse
Thanks for sharing! I was finally able to dump it. Now to see if I can mess around and get it to build! Wish me luck .
JAmerican
You can easily build it again, but the question again is, are the files on the dump folder complete? i wish you luck mate! keep us posted.
da_mayhem said:
You can easily build it again, but the question again is, are the files on the dump folder complete? i wish you luck mate! keep us posted.
Click to expand...
Click to collapse
I deleted some files from the ROM and rebuilt it but it was in .NBA format. I don't remember exactly what I did but I think I renamed the file to .NB and made a .NBH file out of it. Then Flashed my device. I got as far as the WM screen and was stuck there. I reflashed with the Standard WM6 ROM from T-Mobile. .
I'll try some more messing around. I really want to get some cooked roms for Smartphone edition.
JAmerican
Your right about files missing. I was able to extract the ROM and its packages and get two folders (ROM and SYS) along with other packages. The program I used (Package Tool) states that I am missing the following files:
[Missing Files]
SYS\MSXIPKernel
MODULE: busenum.dll
MODULE: cachefilt.dll
MODULE: certmod.dll
MODULE: coredll.dll
MODULE: device.exe
MODULE: devmgr.dll
MODULE: diskcache.dll
MODULE: encfilt.dll
MODULE: fatfsd.dll
MODULE: fatutil.dll
MODULE: filesys.exe
MODULE: fsdmgr.dll
MODULE: fsreplxfilt.dll
MODULE: hd.dll
MODULE: imgfs.dll
MODULE: mspart.dll
MODULE: osaxst0.dll
MODULE: pm.dll
MODULE: regenum.dll
SYS\WinCENLS_WWE
File: wince.nls
OEM\LangDB
File: initflashfiles.dat
File: mxip_lang.vol
OEM\OEMXIPKERNEL
File: boot.hv
File: boot.rgu
MODULE: cecompr.dll
MODULE: ceddk.dll
MODULE: HtcFsdspy.dll
File: mxip_initdb.vol
MODULE: nk.exe
MODULE: ONDisk.dll
and these files are in the Windows folder as well as other locations on my device. The only problem is that the device denies me access to these files. Is there a way to access these DLLs with a powerful file manager. I tried Resco and Total Commander to no avail. Anyway to trick the device into allowing me to copy these files?
Thanks.
JAmerican
I believe there is a need for a simple ROM cooking procedure on devices such as Excalibur and Vox. I'm thinking of a "Norton Ghost" procedure to backup and restore the entire OS and User Filesystem partitions.
The ROM cook procedure would then be something like this:
1. customize the device (all changes stored on device memory of course)
2. backup OS partition (using special USPL)
3. backup User File System (using special USPL)
And a user would just do this:
1. restore OS partition (using RUU)
2. restore User File System (using RUU)
3. personalize device
Does that sound acceptable?
Ok so I was able to extract the T-Mobile WM6 ROM, I was able to use the Package Tool to get it seperated into a SYS and OEM folder. I deleted things like Live Messenger and Windows Live. I put the updated version of Live Search in ROM. I only added one other application, CeleTask. I didn't want to put too much work into tweaking this thing and find it not working. I am downloading the CreateOS.exe and CreateROM.bat files and will try to compile this thing. Wish me luck.
JAmerican
jockyw2001 said:
I believe there is a need for a simple ROM cooking procedure on devices such as Excalibur and Vox. I'm thinking of a "Norton Ghost" procedure to backup and restore the entire OS and User Filesystem partitions.
The ROM cook procedure would then be something like this:
1. customize the device (all changes stored on device memory of course)
2. backup OS partition (using special USPL)
3. backup User File System (using special USPL)
And a user would just do this:
1. restore OS partition (using RUU)
2. restore User File System (using RUU)
3. personalize device
Does that sound acceptable?
Click to expand...
Click to collapse
Hey friend. I know this is not appropriate place to post this, but since you know my situation on the wifi of my phone. Would it be possible to put a working reverse flash of a tmobile dash onto mine and fix the wifi. I have tried everything. And you have been very helpful and it is much appreciated.
keep up the progress guys, i can't wait to try some of the cooked roms from users on this site
Good luck, i can't wait either....
Hey guys,
I used a tool to try and convert my unpacked ROM back to a packed (one folder ROM) and it deleted all my progress. Go figure. So I have to basically start all over again. This time though, instead of making all the changes. I am just going to remove like myFaves, update LiveSearch and add one of my own applications as well as one of my favorite applications and see if I can flash my Dash with it.
Somewhat but its my fault for not backing up.
JAmerican
Related
Hello all,
Can anyone please post ace_ddi.dll found in AKU3.3 to be used in WM6?
This DLL has been (will be) applied in the new WMXL.2, but I don't feel like flashing my highly tuned device once again, so I simply wish to add this DLL to fix video corruption with TCPMP and CorePlayer...
So, anyone, please? thanks
Same here. Would really appreciate if someone could upload this dll.
shandar said:
Same here. Would really appreciate if someone could upload this dll.
Click to expand...
Click to collapse
look... download an AKU 3.3 ROM from the Wiki and then extract it... use ROM Kitchen or whatever if you like, but either way, do it yourself... it's easy enough
Get a full backup first. I applied ace_ddi.dll form Cingular AKU 3.3 to my WM6 and bricked. Had to hard reset to fix. I'm checking for diffs between that and the HTC ROM now...
Ai, that sucks. How exactly did you extracted that file from AKU3.3? If I do a ROM dump, I get a subdirectory called ace_ddi.dll instead of a file. That subdir contains a bunch of files. I looked into those files, none of them seems to be containing binary data what would represent the original file (no DLL entry point found). the S00* files combined seems to be the size of the file needed though, are they encoded in a different format? how do I convert that into the file I need?
you need to have RecMod.exe in the same directory as viewimgfs.exe IIRC or the dlls won't be created from modules. If its there, the reconstructed dll will also be in the folder.
Ah, thanks a bunch, that worked. gonna try applying it (but after a backup as you sugested)
Well... Have to report that once I applied it, the system doesn't boot anymore, and indeed a hard reset is needed.
How did it got integrated into WMXL.2 ?
The dll from the HTC 3.3 dump is identical.
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
kyphur said:
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
Click to expand...
Click to collapse
This is true, you cant do anything to them once they are active, I was trying to do this yesterday.
kyphur said:
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
Click to expand...
Click to collapse
Can you confirm that with the WMXL.2 release TCPMP can make use of the ATI decoder without scrambling the screen?
It didn't fix it for me...
Heimiko said:
Can you confirm that with the WMXL.2 release TCPMP can make use of the ATI decoder without scrambling the screen?
Click to expand...
Click to collapse
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Sleuth255 said:
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Click to expand...
Click to collapse
the trick is ....just replace the dll not the whole module.
Thought I tried that and the resultant dll was 0 bytes ... Must've been something I did... I'll try again.
Sleuth255 said:
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Click to expand...
Click to collapse
try this; install developer certs and sign the DLL with the privileged certificate, no doubt it'll work after that post-install.
Got it to work this time. Subsequent imgfs dump showed the correct size for ace_ddi.dll. The only thing I did different was put the ace_ddi.dll file itself into the same directory as addfile.exe... hard to believe it was that though. New Os.nb flashed just fine & i've got improved ImageON performance. It still pixelates somewhat but at least it doesn't tear up the whole screen any more...
must be my quirky kitchen
edit: notes on ImageON pixelation: There's some good workarounds for this that still retain ImageON acceleration in the Coreplayer forums. apparently things work better in landscape mode....
more on this: I didn't test right. When I set up coreplayer correctly, ImageON was still experiencing the same issues. My 8525 also showed this same problem on WM6 with the replaced ace_ddi.dll from the Cingular AKU3.3 rom. However, when I flashed the AKU3.3 ROM back onto my 8525, the problem went away
Conclusion: it would appear that there's more to this fix than simply the newer ace_ddi.dll
need original ace_ddi.dll
Sleuth255 said:
Get a full backup first. I applied ace_ddi.dll form Cingular AKU 3.3 to my WM6 and bricked. Had to hard reset to fix. I'm checking for diffs between that and the HTC ROM now...
Click to expand...
Click to collapse
Hi! Can you give me the ace_ddi.dll from rom, please?
The Rom Koch at the moment does not support .nb files that have been created with tadzio's ImgFsTools as of now.
I've been wondering if we can perform the following steps to rebuild the .nb file using mamaich's old ImgFsTools.
If we can repack the dump into a rom that still has the 8Mb space in it, it should be possible for Rom Koch to open the file without problems. We can, after modifying that rom, repack it with the new ImgFsTools to shrink the files again.
I have been trying a couple of ways to do this, but run into some problems along the way. I've been digging in the forums to find out what I'm missing here, but can't seem to figure it out. I might be doing something totally obsolete here, but I've seem numerous posts of people trying to customize one of the precooked rom's with the Rom Koch, and didn't get anywhere.
First Try: Just unpack the .nb and repack.
Using the old ImgFsTools, I immediately get errors that there are invalid headers in the file doing the prepare command.
Second Try: First use NbSplit, then unpack and repack the payload.
This one neatly packs the payload again using the old toolkit, but after NbMerge on the files, the file is still small. So apparently it's not just the image file that has lost some size, because that is packed using the old tools, and should include the 8Mb free space. Seems like I'm mixing things up here, so have to try this another way.
Third Try: Same as above, but when repacking, use a different template.
I follow the steps that give me a smaller .nb file from the second try, but when repacking, I provide a both the old and new toolkit a template file of a fixed size rom. This packs the smaller rom data in a 67 Mb .nb file, so looks promising. Rom Koch still throws a DivideByZeroException though, so while I got (my test rom) the Black V2.0 rom in a 67Mb .nb file, that's not the problem.
Am I trying something remotely possible here, or should we just wait for an updated version of the Rom Koch to customize the precooked roms? Obviously, the new ImgFsTools do a lot more than just creating a smaller .bin file.
wait for koch v2.
It can be done and I've done it before using Jasjamming method.
Steps:
1. Prepare a good untouched version of any WM6 rom version ( No free space tweak by Tadzio's Toolchain) - Will be used as shell rom
2. Dump the WM Black 2.0 rom using Tadzio's toolchain only ---> Dump folder will be created: Do not delete
3. Use aWaiter and make imgfs_raw from the rom taken from no. 1 : Do not delete
4. Use normal imgfs tools to compile the dump directory using the imgfs_raw from no. 3 (Shell)
5. Make a new .nb file with the size of 67.7 MB.
actually guys... it's simple.
take an NB, split it into the dev data and the payload.
take the payload, and dump it... play with it, whatever, but remember to re-merge after you're done.
Olipro said:
actually guys... it's simple.
take an NB, split it into the dev data and the payload.
take the payload, and dump it... play with it, whatever, but remember to re-merge after you're done.
Click to expand...
Click to collapse
Sounds great, but I am waiting for Koch 2 that is even easier
Thanks guys, I guess I've been thinking too hard on this one.
Just wanted to try this to conveniently experiment with the precooked roms, but I guess convenient is when Rom Koch is upgraded...
I'll give the above suggestions a shot.
Hi, I'm preparing all you need to kook a italian rom by yourself...
in some minutes 1st part, with programs that you need to extract .nb files from .nbh, and reassemble .nbh as you like, how to dump a rom and how recompile it..
bye!!!
ok, the utilityes you need are:
*** all utilities are ready to download in the end of this post!!! ***
1) nbhtool_trin.rar
2) package_tool.rar
3) nbdumper.rar
4) bepe_kichen_trinity_ita_WM-6.1.rar
Code:
6.1 bepe_kitchen.rar
5) Flash_nbh.rar (included into kitchen!)
6) rgu to xml transform an rgu or a reg file into a provxml file!!
7) dsm patcher to update also the dsms files to respect the rom's os and build version
1) nbtool from dutty is usefull to decompile/recompile nbh , decompil enbh, choose nbh to decompile, you have 1 or more .nb files, windows.nb is that you need, the rom, you should find also:
radio.nb (radio)
first/second_splash.nb (the 2 images shown as splashscreens!!!)
ipl.nb (boot of trinity...)
spl.nb
and other that now I not remember...
................
to recompile the nbh file, just select that you need (os.nb, first.nb second.nb)
for my experiences, try first times only with os.nb, choose the file and compile the nbh files,your rom is ready to be flashed into device...
2) package tools analize the dumped os windows.nb and tell about sys and oem versions, more it creates packages of dumped rom, and insert all files into the 2 system directory "oem" and "sys" with button (menu) "build packages"
3) nbdumper from tadzio, it is the important tool togheter bepe kichen, with it you are able to dump "windows.nb"
put windows.nb into the folder, dos prompt and write:
nbdump windows.nb (then press enter...)
in few minutes you have inside also the directory named: windows.nb.dump, iside you can find all files that will be in rom on your device...
4) now open package tools by bepe, search this directory, and analize, after analizing, click on build packages...
after some time, you in "windows.nb.dump" directory have: sys and oem folders...
this is the real os...
now you neeedd xip directory...
copy windows.nb into the directory named:XIP_extract (that you can find in "bepe_kichen_trinity_ita" tool...
copy it into the directory, rename from windows.nb into "os.nb"
click on "Make_XIP.bat" and then you have "xip" folder...
copy xip folder into "rom" folder in of "bepe_kichen_trinity_ita", copy os.nb too into "rom" folder, so you have rom folder and inside:xip fiìolder and os.nb...
ok...
now, oem and sys folder obtained with package tools, copy them into "bepe_kichen_trinity_ita" tools, and you have:
oem, sys, tools, xip_extract and rom folders, and the exes...
now is ready...
you have to click on "buildos.exe" and the rom will be build, ok, now there is a new folder, "temp", now you have finished, only click on createrom.bat and in few seconds you can find into \temp\ folder a file named os-new.nb, this is the new rom, build .nbh with dutty nbtools, and can flash it on your device!!!
5) to flash put nbh created into folder:Flash_nbh, flash....
next, tools and howto: create extended_roms;create own splashscreens, adding own packages (the packages are additional programs... into I left yet 3/4 packages from mine!!).....
*******************************************************************
I must make all credits also to udK, that discovered with me the right way to kook roms...
and invite all people to make some dotations to him, for the hard work that he made to have a good italian rom to mount on our devices!!!
thanks friend...
*******************************************************************
I think is better to try with udk or lasagna roms to start, they are perfext and logically structured as bepe kichen wants!!!
bye!!!
****************************************************************************************
*
* P.S.: and finally I think that if you decide to use udk rom to make experiments, you have to donate him,
* and if uou want to use lasagna rom to learn to use bepe kichen, also you have to make donations to guybrush.
* they worked hard to translate the rom, you must donete to use theyr roms I think is the only think to do
* to tell them "thanks!!!", really...
*
****************************************************************************************
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 2:
how make own splashscreen!!!
just open an image or create one, with also paint;
make it 240x320 pixels, 240 in width, 320 in height...
save it as bmp, with 24 bits...
open it with nb_image_converter
convert to "nb"
save it as first and second.nb...
now, if you don't have windows.nb use dutty's nbtools to extract from rom, reuse nbtools to compile nbh, add
in os: windows.nb
in "first splash" the file first.nb
in "second splash" the file second.nb...
compile nbh file and flash into ppc, when you finish, you can see you freferred splash screens!!
next:
create a package and/or translate the exe/mui files in your language with resource hacker!!!
try to open an exe, or first a mui files if there is into the package!!
you can see:
icon (you are able to change it , but is not important for us!!)
dialog, you can move the object inside them, rename or translate strings and other...
string table, here you can change, translate in your language tje strings of mui/exe!!!
and other, but for modify translate this basts!!
see later!!! bye!!!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 3:
for mui:
if you have traslated them, you have also to rename: exaple, if therer is amui xxx_409.mui, in english of couse, and you stranslated it into italian, you hace also to rename it by xxx_409.mui to xxx_410.mui!!!
and for italians mui you can use the ones from tynh wm6 Italian rom!!!
and also initflashfiles.dat must be traslate...:
and also rgu files:example:
string: "programs" must became "programmi"
string: "my pictures" must became "immagini"
etc.etc.
howto: CREATE A PACKAGE!!!
ok, download theese utility:
wince cab manager from here:
http://www.ocpsoftware.com/
(full funcional trial for 15 days!!!)
and my utility: packages creator (a little tools of mine!! )
from here:
-------------------------------------------------------------------------------
UPPED:
(new version... bugs solved... option improved!!!)
now in bilingual ITA/ENG, and with more option to personalyze your new packages!!
new beta with more and more options to create initflashfiles.txt...
flag:"simulate folder names" on wince cab manager and put reg file into package folder you choice...
example: "...\trypackage\windows\batterystatus\batterystatus.exe"
you have to put reg file into "...\trypackage\to-import.reg" ok???
and here the new beta of package creator!!!
Hi all, from a Bennec83's Idea I released this last version that works with cab analyzer, and make packages from cab files automatically...
*******************************Re-reupped 1st good working release!!! 4.1 *********************
-------------------------------------------------------------------------------
ok!!!!
P.S.: if th bepe kichen shows an error during the kook operation, it will be becouse there is another file (duplicate file) yet present in rom, delete it from other subfolder, not in the package just inserted...
next appointmant to create own extended_rom!!! and some triks on registry (modifing rgu files!!!)
see you!!!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
lesson 4 playing with extended rom:
howto: create and use extended roms...
ok, have to download the utility htc_extended_rom_editor
I think is all.... (for now!!!)
your knowledge about roms, its components, how to dump, build, add packages are full... rests to edit rgu and provxml...
but in next days....
bye bey and good experiments!!!
*********************************************************************************
*********************************** ******************************
*********************************** UPDATES ******************************
new version of buildos+packagetools, some imporvements, and context menu on packages to enable/disable them by default!!
new version of buildos, now:
1) xip porting for os ber updating;
2) updater for Rom Creation Date;
3) Updater for Rom version at Boot screen!!!
enjoy!!!
improved some context menus on selected package.....
xip porting for OS version and Rom's Date creations Updater!!
new version of package creator, to have own directory where place shortcuts, and some minor bugs solved
here: and added links in initflashfiles.txt for .htm files for "Help"!!!
P.S.: I need beta testing for my apps, becouse, I go on programming and there are allwais same bung into...
bye!!! ( a big thanks to guybrush and udk for testing and support, but specially to Vibranze for testing package creator!!!)
*********************************************************************************
Traduzione in italiano della guida del Kitchen
Lavori in corso..
ervius said:
Hi, I'm preparing all you need to kook a italian rom by yourself...
in some minutes 1st part, with programs that you need to extract .nb files from .nbh, and reassemble .nbh as you like, how to dump a rom and how recompile it..
bye!!!
Click to expand...
Click to collapse
thanx, let's start cook togheter
--reserved for packages--
I only hope that my 3d iwill be usefull to be better, and share togheter a lot of packages for our trinity devices!!
see lather...
I love you.
This is what I searched for long time.
Two question.
1) What difference there is between this and Orginiale Bepe ROM kitchen form Hermes.
2) Can I use all ROM that i Want to start the cooking?
....
3) This is possible some mirror not rapidshare? (for example www.divshare.com)
Grazie mille.
Viva il P3600.
cicciocant said:
I love you.
This is what I searched for long time.
Two question.
1) What difference there is between this and Orginiale Bepe ROM kitchen form Hermes.
2) Can I use all ROM that i Want to start the cooking?
Grazie mille.
Viva il P3600.
Click to expand...
Click to collapse
1) infinite greetings to bepe for the beautifull tool...
the kichen is the same, only you have os and xip for trinity (after you extrapolated oem-sys folders and xip!!!)
2) you can use all roms you want, also in other languages, but only if they , after you dumped and analyzed with bepe package tools, and have oem and sys folders (and xip folder...), but if you try with roms that have missed files, you must try to insert them into oem or sys dolder, you, after use bepe package tools must see only "oem" and "sys" folder, nothing else, to know that the rom is really ok..., in other case the rom was built in confused mode or with other utilities, that I consider oldier...
bye!!!
and my final point is also share a lot of packages....
for now I think it's all, but in few days I explain also howto build packages and other....
see you!!
ervius, very good tutorial i think it'll be useful not only for italian people but for everyone who want learn how to cook their own rom. Just a tip...be careful, read everything and try to understand how these tools works and check everything before try to flash your device.
Guybrush said:
ervius, very good tutorial i think it'll be useful not only for italian people but for everyone who want learn how to cook their own rom. Just a tip...be careful, read everything and try to understand how these tools works and check everything before try to flash your device.
Click to expand...
Click to collapse
yes... by attentions, use the tools at own risk, and specially use them with "brain"!!!
bye!!
Thanks ervius! you are truly "mythical". I`ll read all with much attention tomorrow, now i`m seat in one park bench to 5 meters from the sea.....
Hi...... morf3o.
added lesson 2 (how to create/modify images and create your splashscreens at ppc boot!!!)
at first post!!
see you later to build our first package!!!
I tried this tools with Lasagna 205 ROM.
I arrived to package tools
When I press "Build Packages" I've this error:
Code:
Syntax error map.txt:
tom
tom is the last lin of map.txt.
Can i delete it witouth problem?
At the end I've also the OEM and SYS directory but there are also three file out all directory:
Recorder.exe
Voice Recorder (link)
Recorder.exe.0410.mui
It's ok?
One Advice.
To arrive at DUMP directory and afther to OEM and SYS I found more easy and fast this way:
http://forum.xda-developers.com/showthread.php?t=316940
Thanks 1000!
cicciocant said:
I tried this tools with Lasagna 205 ROM.
I arrived to package tools
When I press "Build Packages" I've this error:
Code:
Syntax error map.txt:
tom
tom is the last lin of map.txt.
Can i delete it witouth problem?
At the end I've also the OEM and SYS directory but there are also three file out all directory:
Recorder.exe
Voice Recorder (link)
Recorder.exe.0410.mui
It's ok?
One Advice.
To arrive at DUMP directory and afther to OEM and SYS I found more easy and fast this way:
http://forum.xda-developers.com/showthread.php?t=316940
Thanks 1000!
Click to expand...
Click to collapse
so, you have to install also java virtual machine... with this utilities in not necessary...
thanks ciccio but i'd like to continue with bepe's kichen, do you like use it??
ok...
3 files are out, put them into \oem\oemapps\ directory, so you now have only oem and sys directory, then... extract xip etc... etc...
ok!!!
thank's for your answers.
I like also Bepe's Kitchen. GO ON!
For the Syntyax error?
I've to delete "tom" at the end of map.txt?
cicciocant said:
thank's for your answers.
I like also Bepe's Kitchen. GO ON!
For the Syntyax error?
I've to delete "tom" at the end of map.txt?
Click to expand...
Click to collapse
I don't have your error, but if finally you have oem and sys folders, then it works well...
but you can try to delete and post if it work...
bye!!
Sorry for my newbie question...
In my understanding all this tools are working with ROM files you already found "somewhere".
What I want to do first is getting a working ROM out of a Trinty device. E.g. I have a german Vodafone device with the Vodafone custom ROM. I simply want to "copy" this ROM on my Harddisk. No changes. I only want to be able to flash it back if I want to, to have the device in the same state it is now.
Which tool do I have to use?
What do I have to do?
Check this article
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Ciao
A question ervius:
we suppose that I succeed to modify/create my first ROM, exists a way in order to test it without flash on my device? A way for being sure that if I flash, i do not burn my trinity....
Thanks........ morf3o.
morf3o said:
exists a way in order to test it
Click to expand...
Click to collapse
The only way is flash your trinity and hope
claros said:
Check this article
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
Ciao
Click to expand...
Click to collapse
Thanks... that is what I was looking for. I found this (http://www.modaco.com/Paul-s-guide-to-backin-t255090.html) in the meantime. But the two guides differ: Paul says, that I only need the Part02.raw file. Why?
saminegm said:
Thanks... that is what I was looking for. I found this (http://www.modaco.com/Paul-s-guide-to-backin-t255090.html) in the meantime. But the two guides differ: Paul says, that I only need the Part02.raw file. Why?
Click to expand...
Click to collapse
Your OS is in part2, first two parts are the XIP partition aka your boot sector.
Ciao
Hi all
I'm cooking my own rom using Core Pro Kitchen, so far it's going OK.
I read most of this forum and the WiKi, but still have a couple of questions
first:
Do we really need .rgu files in imgfs? AFAIK they are only used to build .hv files.
I tried to delete theese from \temp\dump before creating OS.nb (after running BuildOS), and the ROM works, at least I don't see any drawbacks.
second:
I'm cooking my own custom package into the rom and need all the files in it to be impossible to modify/delete. All files in the package have +r +s +h attributes set, but I'm sill able to modify them on device.
It seems like the modified file is created "above" the ROM one (sort of copy-on-write), because when I use TotalCommander to delete it, it just reverts to the original file from ROM. Is there anyway to make a file completely unmodifiable? Put it in XIP? do I have to rebuild any of three .dsm files in XIP if add my file there?
The file is about 1-2kb
Any ideas?
Thanks, Serge
russian version can be found on:
http://asusmobile.ru/board/viewtopic.php?t=7816
version 080302_1843
This is english translated version of tool for editing of P525 ROM made by Anper.
Sorry for not so quite good english.
Additionally attached utilities for preparing of GIF "AsusP525GIFConverterByMrToto.zip"
About util KitchenNB0.exe:
Warranty: not any, only can say, that not especially include any harmful code to that utility. And before new version posting was firmware changes in mine PPC that made by that util.
don't known if that util works on other models (don't have it), it's tested only on my own ASUS P525. Flashing was made only thru USBloader.exe (don't knew how - read asusmobile.ru or anywhere in other places).
On mine device installed unchanged bootloader from WM6 official.
On WM5 was tested process completion on pc, but without real tests on pocket.
That Utility allow process images ROMGalaxy.NB0 and Galaxy.NB0
(Advised to use ROMGalaxy.NB0 (withiut bootloader), as more safe variant for Your device).
That images can be got by decoding of Galaxy.cap (decode can be done from that util).
First part of tool allow split to parts, and correcterrors in CHS, cut off bootloader, unpack galaxy.cap to ROMGalaxy.nb0 (used data from tool made by Ingvarr).
Second part allow you process IMGFS partition (partition that contain main
software). In that part partition IMGFS can be extracted to file. Get from that DUMP (in future You can do anything you want with that). After that combine DUMP to IMGFS and at the end combine and recalculate checksum of NB0.
splitting and combining functions of IMGFS to DUMP and back executed by Tadzio made utilities. But so they is made for HTC devices, so I'm correct that accordely to ASUS specific. That functions is called from mine tool (execute bat files is not necessary). Correction may be done by pressing button CORRECTION. ROM size is REALLY CHANGED WITH DECREASING OF nb0 image and accordely to size User storage INCREASED - checked (by recompressing of misar firmwares and by other firmwares corrections).
Checksum calculating made is done by tool, but algorhitm is taken from Ingvarr tools (slightly modified to this tool, that does not create all of file image in memory, but recalculate by chunks).
Process ROMs can in different directories, for no all in one place files garbage.
To flash ready file I'm advise thru bootloader and exactly ROMGalaxy.NB0 (without bootloader). Existence of bootloader you can check in first part of tool.
In that complect persist other tools, needed for coocing your rom.
But accordely to them - you must teach it yourself. I'm don't made that.
Also added in third part possibility to change any of parameters in XIP part of ROM (for correct processing parameters must be changed in order: firstly unpacking, changing, packing, and combining NB0).
Work examples:
1. Open NB0, if that not persist - make it from galaxy.nb0 (by cutting off of bootloader) or from galaxy.cap.
2. If that is homemade firmware, possible will be CHS error in MBR. Correct that by pressing button CORRECT MBR. (Why error persist? - Possible our firmware makers ignore that, or firmware was combined by utilities from Tadzio or other that was not adopted for ASUS (also possible CHS not so sensitive)).
Also may appear message about file size differences with sum of sizes of all partitions - it's not harmful - in most cases simple ignore that.
3. Next is Operations with IMGFS tab. In that part can simple do next processes in shown order. Get IMGFS, Create DUMP, edit DUMP as you wish, from DUMP create IMGFS, combine NB0 new and it's all, can flash. For checking you may open newly created NB0 in first part of tool.
4. Flashing may be done by USBLoader.exe.
Another example - correction and optimization of firmware size:
Shortly about compression:
I'm has provided an opportunity to combine IMGFS.new from DUMP with LZX compression (greatest, but slower starting) and XPR.
Choose by pressing needed button. At once want to warn you about not all firmwares have library with compression LZX, accordely to that after flashing, it will not run further to blue screen.
If you have not broke bootloader, this all is reperable (Many peoples through it passed).
Well, like everything, write at a forum.
And a long life for yoursdevices.
P.S. if you found translation errors - please PM to me.
20080303
Translation fixes, exe packed in own archieve as mainly only it changed
1. unpack kitchen ASUS_P525_NB0_Kitchen.zip
2. place ASUS_P525_NB0_Kitchen.exe from exe.zip to directory from 1.
Thanks DaLiV.
Thanks anper.
Great tools.
Wait for Eng version for a long time.
vivi
thanks anper & Daliv
great tools, Great work!
updated translation.
thanks!
Thanks DaLiV, anper!!
Have been looking for the English version!!
gabz
nice. looks interesting.
will give it a try.
but will it work using wm6/wm6.1 as base ROMs?
cheers!
ericjm said:
nice. looks interesting.
will give it a try.
but will it work using wm6/wm6.1 as base ROMs?
cheers!
Click to expand...
Click to collapse
tool work with WM5, WM6, WM6.1 only for ASUS P525.
anper said:
tool work with WM5, WM6, WM6.1 only for ASUS P525.
Click to expand...
Click to collapse
sweeeeet!
thanks for this one anper (and DaLiV for the english translation!)
can't wait!
How
How can we add additional OEM packages into our rom using this kitchen?
as in all other roms ... split by packages by other tools, if you want, but to that tool return ready dump directory
sorry
DaLiV said:
as in all other roms ... split by packages by other tools, if you want, but to that tool return ready dump directory
Click to expand...
Click to collapse
Sorry, But I cannot understand what you mean. Could you please elaborate?
search forum for tool like "buildos+packagetools" or "dmp2pkg" - then edit packages and after that make conversion back packages to dump
Sweet kitchen
Just letting everyone know that this kitchen can also be used for Dell Axim X51's - I have
For X51 users, make sure you don't click "Repair CHS" - it's for ASUS PDAs only and will result in a bricked ROM
btw You can also use recookstruct as well to sort the dump into packages, you may have to get rid of some entries in "HKEY_LOCAL_MACHINE\System\Inbox\Settings\WelcomeEmail\Templates\ServiceTemplates" because recookstruct can't parse the "®" symbol sometimes found in the key
(Only works with IMGFS, not XIP)