Develop Bugs

Custom Smartphone ROMS

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

Asus P525 NB0 Kitchen by Anper

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)

Emulated Windows Mobile 6 ROM Dumping

Hi,
My first post here, hope to don't broke any Forum Rule.
I'm running an emulation of Windows Mobile 6 (SDK) taken from Microsoft,
and I've the necessity to study and extract system dlls (such as for PDB)
and looking for certain Undocumented Functions.
My question is, Is possible/necessary to make a dump of this Emulated WM6?
If yes can you please point my to the right links and threads?
Regards,
Giuseppe

Hi,
How can I extract DLLs and other resources from PPC_ITA_GSM_VR.BIN ?
I've tried with splitrom.pl but does not recognizes that format ( hash MD5 does not match)
I've also seen that there is another Suite of Tools ImageFsToolKit I've to use it? if yes can you point me how?
Hope in a Reply
Have a Nice Day,
Giuseppe

Check out this Emulator Kitchen thread

Many thanks for your precious help!
I've runned 1_UnpackEmuROM.cmd and the process worked correctly
\OEM
\SYS
\ROM
Now my question is, every dll have a directory that contains imageinfo.bin and various S00x files, which tool I've to use to assemblate it in the final DLL?
I've also seen a little bug into BuildOS.exe, the crash is caused by a not Catched Exception, precisely is caused from an unhandles System.IO.DirectoryNotFoundException all you have to do to avoid that is to implement a try/catch block for this exception
Regards,
Giuseppe

Download the attachment
Unpack that
Place the folder of the dll (or exe) in the unpacked one. Note: The folder, not just the files.
Run ReversRecMode.bat
Look into the folder

It worked!
Many thanks!

Modification of the On the Road panel for X2

Hi guys, i tried to modified the mui file for the italian language as in the beta panel downloadable from the SE site i found lots of translation errors. I was able to modifiy it with Res Hacker then put back on the cab file. The problem is when i install the panel it says the panel cannot be install because the program dones't have a digital signature with a realible certificate.
And if i install the original and then substitute the mui file in the folder, when i launch the panel it apears in English. Is there a solution for this and be able to make run the modified panel? Sorry guys this is all my knowledge, i'm not able to program or doing more difficult things. Just wanted to try some modifications by myself.
Sorry i forgot to say that it runs on my X1. And the original panel perfectly runs without the activeX or other X2 stuff. Just the translation is terrible

Nobody knows if there is a way to sign the file, as it seems ResHack removes some something on the file when i modify it

Use any signer for wm All work )

Hi, I'm not sure if it works with .mui files, but you can try using this package, which helped me translate some .dll files recently:
http://forum.xda-developers.com/showthread.php?t=432041
It contains Reshack and two small tools for unsigning and signing files.
However, the certificates of the included file have expired so you will have to replace them with the ones from this .zip archive:
http://forum.xda-developers.com/showpost.php?p=5312209&postcount=37
Please note that you might have to do your work all over again with a fresh unsigned file. I don't think you can re-sign a file without unsigning it before.

Vote the next osKitchen feature #1

(Done, now present in 1.31) Internal search system (search file names and file contents, edit the text files directly from the kitchen or launch an external editor)
Automatic localization (support for folder variables in initflashfiles.dat/app.dat to create entries valid for all languages (Done, now present in 1.31), using those variables during import to make ROM translation easier, automatic generation of new OEM_Lang_XXXX folders with a corrected initflashfiles.dat and renamed MUIs as soon as a compatible SYS is added, automatic fixing of all the packages' initflashfiles entries to match the new languages start menus, automatic package To CAB conversion to test all your packages on the phone (Done, now present in 1.32))
(Done, now present in 1.32) Total integrity check (checking the validity of every REG file and app.dat file, checking for broken module folders, checking for invalid SYS/OEM/EXT packages to reduce the hard to track ROM building issues to minimum)
Advanced file attribute management (setting the ROM file attributes according to the DSM file, adding an interface in dialog properties to change the DSM file list and applying file attributes automatically to the files that are not present in the DSM file list)
Internal ProvXML engine (much more accurate CAB to EXT conversion, provxml to REG and APP.DAT conversion)
Batch ROM import (adding long paths (up to 32000 characters) support to oskitchen to allow using the kitchen from any folder no matter where and adding a new internal tool that takes a folder of multilanguage ROMs of similar versions and builds a final Sources folder with all the localized files merged to start working on multilanguage ROMs much more easily)
EXT2 Package Replacement (an EXT format replacement that supports MNGE modules (no more module folders around) and folders with conditional names (for resolution, language, device, windows mobile builds, etc.) to make multidevice packages much easier))
Advanced ROM versioning (allow setting the version in the splash screen and in the RUU)
(Done, now present in 1.31) Manila management support (deleting unneeded localized manila files while building, adding a whitelist-based manila files compression to improve manila speed and free space on the ROM)
Improved UPX support (adding a file cache to remove the delays caused by the UPX compression during cooking process, switching UPX file selection to opt-in, UPXing all the files according to an online whitelist that can be updated/submitted from the kitchen)
Kitchen distribution tools (generating a XML file to allow changing the kitchen titlebar/about/help entries, to automatically load a selected device profile and to add an additional customizable tools menu, adding a "Temporary OS.NB" shrinking tool and a SYS cleanup tool to delete unneeded resolutions and languages)

I vote #9, then #5

so many great ideas .. can't we have all of them?
i guess you will work out on them sooner or later
thanks for all you effort

nosedive said:
so many great ideas .. can't we have all of them?
i guess you will work out on them sooner or later
thanks for all you effort
Click to expand...
Click to collapse
Exactly what I was thinking I love all of these ideas I love the direction this kitchen is heading great work airextreme!

if possible i'd vote for all as well
oh well let the voting begin

"Manila management support" would be great!!

I think you should include something to make different ROM Builds in one shot, to make all the .nbh files just by pushing the cook button once. (like a MaxSense version, CHT Version, Plain Version etc..) Also, an autimated compression + upload feature would be nice, too.

EcoROMchef said:
I think you should include something to make different ROM Builds in one shot, to make all the .nbh files just by pushing the cook button once. (like a MaxSense version, CHT Version, Plain Version etc..) Also, an autimated compression + upload feature would be nice, too.
Click to expand...
Click to collapse
Can it turn on my coffee maker in the morning as well?

WoZZeR999 said:
Can it turn on my coffee maker in the morning as well?
Click to expand...
Click to collapse
then it would have to be called the easy automated kitchen

I voted for deployment tools since I like control but would have also voted for integrity.
This seems like a better place to add other simple requests rather than in the kitchen thread here is a simple one
Add the full version number to "Help About".
I have 3 versions running and am current naming the folder to keep up with it.

OS kitchen
I will vote for #6 and #9

if wish a possibility to select back for easy folder structure (old kitchen). the separation for language, sys-versions, oem-versions ... is not realy nessassary (for me) and the overview of cooking would better.
integrating emulator/simulator for testing cooked rom.
you make very good job.

jjblaster3 said:
if possible i'd vote for all as well
oh well let the voting begin
Click to expand...
Click to collapse
I second the motion. All are great future additions. Good work Air.

Having recently moved form EVK to osK, the one thing I REALLY miss is the internal search...being able to search within files for a keyword...and being able to double click the file to open it from the kitchen...made tweaking sooooooo much easier.

the_scotsman said:
Having recently moved form EVK to osK, the one thing I REALLY miss is the internal search...being able to search within files for a keyword...and being able to double click the file to open it from the kitchen...made tweaking sooooooo much easier.
Click to expand...
Click to collapse
+1. I also miss that feature the most after making the shift to osK. Great job Air!

I Vote For the following:
#1
#3
#5
And thanks for this absolutly great Kitchen!

the_scotsman said:
Having recently moved form EVK to osK, the one thing I REALLY miss is the internal search...being able to search within files for a keyword...and being able to double click the file to open it from the kitchen...made tweaking sooooooo much easier.
Click to expand...
Click to collapse
hello,
i confirm with you. i use totalcommander and pspad for more comfort.
totalcommander is good for listing all files from kitchen-root (without directories) with sorting by filetypes and pspad for searching by keywords.

How about the ability to build a dumpable rom

hoho.hello every one!

Well, I really nead a good PROVXML parser/validator, because straight app.reg editing is inactual now.