Related
i wonder if this is possible,
to remove useless ROM files from windows folder? i found a lot of dog barking multimedia crap, i estimated it to be around 9MB ????
is this possible ????
i tried the raw rom editor tool on another thread but it didnt work on the new rom for jasjar
thanks
yes. cook your own rom as well explained in earlier posts.
->convert the nkf files
->dump the extracted fat file
*rid out the junk properly, rgu dsm hv _...
-<compile digged out dump
-<reconvert to nkf
*flash
*have many precious megs free :roll: [/b]
tryed so but failed as the new rom was not supported
tryed so but failed as the new rom was not supported by the buildimgfs.exe tool , neither did the delfile.exe tool did work also :?
any other ways to cook rom ?
any way to delete files directly from the installed rom ????
many thanks
What did you try because cooking a universal rom does.
make_imgfs.exe dumps the splitted binary rom file. It can dump the .bin file you splitted using prepare_imgfs.exe.
Buildimgfs on the other hand rebuilds the dump directory to the binary rom file.
I suppose you do something wrong.
2 success , 2 failure
i did make_imgfs.exe : successfully .
then prepare_imgfs.exe. : successfully
but Buildimgfs : failed,
and delfile.exe also failed ...
the programer said these might not support the new rom.
i donno wat to do now ???
many thans
the os image is compressed so you might not be able to gain as much storage as u think... however if you do then let us know as well
Where...
Where this the earlier post????
Gracias...
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?
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
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
Hi
Can anybody telll me how to get the coredll.dll from an image. I have downloaded ExcaliburKitchen and copied the RUU_signed.nbh into the Source folder. I then use the batch file to dump the os. The coredll isn't in the os dumped files. I have looked around the forums and it appears you have to do something else to dump the coredll.dll (I found some examples using rommaster but they didn't appear to work).
Thanks
Matt
toxicated101 said:
Hi
Can anybody telll me how to get the coredll.dll from an image. I have downloaded ExcaliburKitchen and copied the RUU_signed.nbh into the Source folder. I then use the batch file to dump the os. The coredll isn't in the os dumped files. I have looked around the forums and it appears you have to do something else to dump the coredll.dll (I found some examples using rommaster but they didn't appear to work).
Thanks
Matt
Click to expand...
Click to collapse
you cant see it from the OS dump cos it isnt there. you have to dump xip.bin and get the coredll.dll cos its part of XIP
Maybe a stupid question, where is the xip.bin and how do you dump it?
Problem solved
Hi
I found Extract_XIP.rar which allowed me to extract the files I needed from the OS.nb. Thanks for your help.
Matt