ace_ddi.dll from AKU3.3 for WM6 - 8525, TyTN, MDA Vario II, JasJam ROM Development

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?

Related

problem during cooking lvsw 0320

i have cooked successfully more than 10 roms, WWE vesion to CHS vesion, they all work fine.
but when i want to cook a new rom based on LVSW 0320 vesion, i failed. i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
sorry for post this new thread but i have posted under lvsw's thread and no one answer me.
can anyone help me plz, i really like this ROM.
thanks in advance.
i had the same problem... then i came up with a briliant solutiion
you know the user.hv and initdata can be edited without any probs..also this version of the rom deploys the ext rom aswell.. so what i did was i edited config.txt and added a cab with the HKLM etc regs that go into default.hv into the dump folder and generated a rom with that cab inside..
and VOILA... now i have a custom rom with all my settings... i figured this way out after hours of frustratingly trying to edit the default.hv
hope this helps
zohaer21 said:
i had the same problem... then i came up with a briliant solutiion
you know the user.hv and initdata can be edited without any probs..also this version of the rom deploys the ext rom aswell.. so what i did was i edited config.txt and added a cab with the HKLM etc regs that go into default.hv into the dump folder and generated a rom with that cab inside..
and VOILA... now i have a custom rom with all my settings... i figured this way out after hours of frustratingly trying to edit the default.hv
hope this helps
Click to expand...
Click to collapse
thank u, i have tried ur solution, but there is a big problem, .cab file doesn't support chinese caracter, so edit default.hv is the only way.
dont know if this would help you but take a lot here :
www.asukal.jp/hv_rom/hive2.txt
or simply use Make_HV, found it in the development & hacking thread.
First covert the hv file to rgu (which is simply REGEDIT4 Format) then make changes and convert it back.
qooqoo said:
i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
Click to expand...
Click to collapse
This is my little surprise
qooqoo said:
thank u, i have tried ur solution, but there is a big problem, .cab file doesn't support chinese caracter, so edit default.hv is the only way.
Click to expand...
Click to collapse
You don't need a .cab for this. The program that goes through Config.txt can handle XML files with registry settings directly. So, grab any of the .xml files listed in Config.txt as a template for your own .xml file. Then just add your new .xml file plus a line in Config.txt referencing this new file, and you're all set.
There's another solution which I found much more convenient: use bepe's Rom Kitchen, and import whatever ROM you want. If I'm not mistaken, it's even available bundled with a Chinese ROM already. There you can edit the .rgu files from which the Registry will be created. This eliminates the need to read any of the .hv files. Worked very well for me! Also, since bepe's kitchen recreates the packet structure of the ROM, it's so much easier to understand which files and registry entries have a dependency or belong together. Highly recommended!
Cheers
Daniel
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
weird suprise
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
Why would that be a surprise? Is there more to this than meets the eye?
dutty said:
weird suprise
Click to expand...
Click to collapse
Indeed, I've been hitting my head against it for some days now...
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
himan,give us a solution plz, it is a so good rom, but i can't add anything i want.
tadzio said:
grab any of the .xml files listed in Config.txt as a template for your own .xml file. Then just add your new .xml file plus a line in Config.txt referencing this new file, and you're all set.
Click to expand...
Click to collapse
thk u but i don't know how to edit a xml file, any suggestion?
tadzio said:
There's another solution which I found much more convenient: use bepe's Rom Kitchen, and import whatever ROM you want.
Click to expand...
Click to collapse
it is for CHT but not for CHS, there is a lot of CHT roms yet, cooked or offcial, but there isn't a official rom in CHS, a just want to convert 0320 vesion to CHS vesion.
I will be watching this thread.
Waiting for good news.
qooqoo said:
i have cooked successfully more than 10 roms, WWE vesion to CHS vesion, they all work fine.
but when i want to cook a new rom based on LVSW 0320 vesion, i failed. i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
sorry for post this new thread but i have posted under lvsw's thread and no one answer me.
can anyone help me plz, i really like this ROM.
thanks in advance.
Click to expand...
Click to collapse
I have the same problem...the LVSW 0313 version was fine...then the new LVSW 0320 won't boot..stopped at the subsplash screen...it is strange that the default.hv is there but doesn't seem to booting the file.
qooqoo said:
thk u but i don't know how to edit a xml file, any suggestion?
Click to expand...
Click to collapse
Any Unicode-capable editor will do. Personally, I use UltraEdit.
Cheers
Daniel
Please don't take offense, but I'm starting to think you got the ROM as it is..."protected" that's why all the customizations are done via AutoRun.exe and xml files.
i found that lvsw 0325 edition can be edit.
qooqoo said:
i found that lvsw 0325 edition can be edit.
Click to expand...
Click to collapse
Yes, 0320 can't be edited. But 0325 could. But you can't use the regular tools..you have to use the "more Storage" tool, then just manually copy the "default.hv" and "user.hv" from the "dump" folder, use the regular tool and covert it to .reg. Then you make modifications to the registry file, convert it back to .hv and copy them back to the "dump" folder..you can add files by just copying files into the "dump" folder..after you are all done with it, just continue with the "more storage" tool to make your new-os.nb

[ROM Building] Hermes Kitchen v1.0 - 18 August 2007

I have learnt so much from this site that I want to give back what I've learnt to the community.
I have put together the tools made by the brilliant minds here, I won't name all cause there are just too many. This is a Kitchen that I put together on how I would take apart a ROM and then fiddle around with it and then put it back to flash to my device. Its nothing brilliant, but it does the job just alright.
Thank you to bepe, core kitchen, CUSTEL for teaching me, Olipro, and a lot more i can't think of at the moment.
http://rapidshare.com/files/49695507/Hermes_Kitchen_v1.0.exe.html
Here is what's in the .exe file:
1.0 .nbh to .nb
2.0 Dump .nb
3.0 Packaging Dumped .nb
4.0 Extracting XIP from .nb
5.0 BuildOS and CreateROM
5.1 Edit initflashfiles.dat
6.0 Build Ext_Rom
7.0 Splashscreen viewer
8.0 .nb to RUU_signed.nbh
9.0 RUUWrapper v7
Tools
I've used this technique to take apart ROMs from Schaps, Sleuth, Faria, Custel, Dutty and more. Black version 3.0 and below can be used. But for higher black versions, JJ deletes the .rgus and therefore its difficult to rebuild with the missing .rgus. I don't blame JJ cause he works really hard on His BlACK Roms and someone comes and takes it apart and edits it and puts it up as his own. But all the chefs have worked endless hours and continue to work on them. So with this tool, maybe you guys can stop asking for so much from the chefs and do it yourselves...
Just try this out. Its nice. There is a step by step also with pictures.
Take care.
its good but how to dump nb in the cmd screen it has nba
jdac21 said:
its good but how to dump nb in the cmd screen it has nba
Click to expand...
Click to collapse
Did you read the .doc file? Just change the whole file name from Windows.nb or OS.nb to nk.nba. First you have to set to show file extensions on your windows explorer.
Good. work.
Can you adapt for trinity?
I think you just have to change the utility for flash.
I am sorry man. I have no idea how the trinity works. I dont have one. I just have a hermes. Hoping to get a kaiser soon. If it ever gets launched!
Is there anyway (i know there is, i have done it!) you can get your bat files to delete the temp/un-needed files, im running throught your kitchen now, it seems pretty good, apate from the fact that there is loads of temp files and directories.
yor bat files can be set so that when they finish the operation, they delete what the user dont need
(i can do this but it is your kitchen, so i posted to see if you would do it!)
also when you say to run the package tool, and replace and missing files, i have just dumped a ROM and i am missing:
[Missing Files]
SYS\AUTOUPDATE
MODULE: autoupdate.exe
MODULE: autoupdatecpl.cpl
SYS\SQM
MODULE: sqmce.dll
MODULE: sqmconn.dll
MODULE: sqmdata.dll
MODULE: sqmevent.exe
MODULE: sqmsvc.dll
MODULE: uptimesqm.exe
OEM\OEMOPERATORS
File: Dopod_Black.tsk
File: P_Sound_Dopod_WWE_0713.CAB
File: PreConfig.txt
SYS\Autoupdate_Lang_0409
MODULE: AutoUpdateRes_wpc.exe.0409.mui
OEM\OEMAPPS
File: ClearVue PDF.lnk
File: WTCVPDFV.exe
File: WTCVPDFV.htm
File: WTCVTime.dll
File: WTPDFRdr.dll
where can i find these files?
bennec83
p.s. using NBHExtract to dump the nbh is much faster than the method you have here (im just thinking coz u said you have a really slow laptop!)
The missing files usually would be next to the OEM and SYS folder when you use the PKGtool. Also, i have no idea how to make the .bat file. If you know, you can do it for me and maybe i can include it? Cause this is how i do it. And i took this all from tools i found all over the whole XDA-dev site. I'm no genius in this programming scene. Just know enough to get by.
bernardryan said:
The missing files usually would be next to the OEM and SYS folder when you use the PKGtool. Also, i have no idea how to make the .bat file. If you know, you can do it for me and maybe i can include it? Cause this is how i do it. And i took this all from tools i found all over the whole XDA-dev site. I'm no genius in this programming scene. Just know enough to get by.
Click to expand...
Click to collapse
ill make new or edit the ones you have that way ther is not so much un-needed files left over. i will also send you a replacement for your first folder, it is much faster, also i may have an improvement for the dump step too.
ill PM my things to you as i make them and you can see if they meet your requirements.
bennec83
can you give details on the extrom?
i want to install a CAB (only one) and set a default theme
thanks
really help full for a new comer's like me ill give a try right now in my HTC 8525
bennec83 said:
can you give details on the extrom?
i want to install a CAB (only one) and set a default theme
thanks
Click to expand...
Click to collapse
Hey bro, I dont get what you mean?
I have the folder in there. And i have an example of all the stuff thats in the extended ROM. If i'm not mistaken, type this in the config.txt or preconfig.txt depending which you are using.
EXEC:\Windows\cusTSK.exe \Windows\bennec83.tsk
CAB: \Extended_ROM\bennec83.CAB
Remember to save it as read only. All files in the extended ROM beforeusing the HTC Extended ROM.exe must be READONLY!...
The file you sent to me is good. But dutty's way is fine and its not a matter of fast or not. Its a matter of user friendly. Your way, aka pof's tool is good. I've used it before. But then have to explain to some noobs how to drag and drop the file onto the DRAG HERE.bat... get what i mean? Thanx again.
Any other way to improve this? I am trying to make it as fool-proof as possible.
bernardryan said:
Hey bro, I dont get what you mean?
I have the folder in there. And i have an example of all the stuff thats in the extended ROM. If i'm not mistaken, type this in the config.txt or preconfig.txt depending which you are using.
EXEC:\Windows\cusTSK.exe \Windows\bennec83.tsk
CAB: \Extended_ROM\bennec83.CAB
Remember to save it as read only. All files in the extended ROM beforeusing the HTC Extended ROM.exe must be READONLY!...
The file you sent to me is good. But dutty's way is fine and its not a matter of fast or not. Its a matter of user friendly. Your way, aka pof's tool is good. I've used it before. But then have to explain to some noobs how to drag and drop the file onto the DRAG HERE.bat... get what i mean? Thanx again.
Any other way to improve this? I am trying to make it as fool-proof as possible.
Click to expand...
Click to collapse
Thanks for the EXTROM stuff, the config.txt and perconfig.txt actually go into the extrom dont they? whats the difference between the 2?
(Change the name from "Drag Here" To "Click Here" and it is friendlier as you have to load no software, jus put the nub into the same folder and click! )
Okay bro.
So, config.txt in OEM/OEMAPPS is for you to execute whatever you want without an Extended_ROM. You must have Config.txt and AutoRun.exe in the same folder. Some ppl don't like it this way. As it wastes precious space. So they use a different method. They use the Extended_ROM to store their stuff and settings and then while rebooting from a HR, they tap into the Extended ROM and get the stuff.
So for extended ROM, you need the 2 files, PreAutorun.exe and Preconfig.txt. The exe file is to run the preconfig.txt. So in the Preconfig.txt, lets say for example there is this in there:
SHOW:\Extended_ROM\MSFT_Logo.bmp
LOCK:Enabled
;EXEC:\Windows\cusTSK.exe \Windows\Black Vista.tsk
EXEC:\Windows\SetHSDPA.exe /Enable
XML: \Windows\Settings.xml
Hide:Enabled
EXEC:\Extended_ROM\AutoRun.exe
LOCKisabled
RST: Reset
So what this does is executes the HSDPA settings, and an .xml file which has some tweaks like the GLYPH and Page settings ****. And then it executes the AutoRUN.exe in the ExtendedROM. So now in your extended ROM, you should have the config.txt and AutoRUN. Autorun points to config.txt and PreAutorun.exe points to Preconfig.txt. So now in your Config.txt which is in your extended ROM might look sometihng like this:
SHOW:\Extended_ROM\MSFT_Logo.bmp
LOCK:Enabled
CAB: \Extended_ROM\ITS1027_FixActivesyncWlan.CAB
CAB: \Extended_ROM\1 Signed_Dpdcert_222.cab
CAB: \Extended_ROM\2 05_NetWiz-ExtUp-V12b.cab
;CAB: \Extended_ROM\3 RescoExplorerEn_p.ARM.CAB
;CAB: \Extended_ROM\4 FtpAddinEn_p.ARM.CAB
;CAB: \Extended_ROM\5 RegistryEn_p.ARM.CAB
;CAB: \Extended_ROM\6 Levels.cab
;CAB: \Extended_ROM\7 enAlarmPPC v3.3.1.CAB
;CAB: \Extended_ROM\8 UTAv3.cab
CAB: \Extended_ROM\9 WM6_Sound_Scheme.CAB
LOCKisabled
RST: Reset
I hope this helps, Take care.
bernardryan said:
JJ deletes the .rgus and therefore its difficult to rebuild with the missing .rgus. I don't blame JJ cause he works really hard on His BlACK Roms and someone comes and takes it apart and edits it and puts it up as his own. .
Click to expand...
Click to collapse
Hi bern,
congrats on your rom building package.
in regards to the rgu's i delete them to save around 1.5mb of storage space. if someone wants them a PM is all they need to do, no one has asked so far.
Ooo.. i didn't know that. I thought you actually needed them to get the ROM running. Sorry dude. But then again when you hit buildOS and CreateROm, i think after that, you can delete all the .rgus right? Not sure tho... anyway... Will keep that in mind the next time i wanna take your ROM apart and edit it. I stopped using your ROM at Black v2.5 (Which to me was by far the best).
Take care JJ,
We miss you around here. Got your imate yet? or your Kaiser?
bennec83 said:
Thanks for the EXTROM stuff, the config.txt and perconfig.txt actually go into the extrom dont they? whats the difference between the 2?
Click to expand...
Click to collapse
i don't know if this will help you: what I do is have one config.txt in \windows cooked in ROM that looks like:
LOCK:Enabled
CFG: \Extended_ROM\Config.txt
LOCKisabled
RST: Reset
and than the second config.txt in ExtROM which is similar to the above (does all the customisations, settings and progs, etc)
In fact if u look in \windows for mxipupdate_zzPIED_101.provxml it should be pretty self explanatory how the process is triggered. All actions & names of .txt's are defined there.
In my case see enclosed.
hope it is useful for u,
cheers dan
Hi,
this is a nice guide, thanks.
MfG
S64

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

20924, Sys and Xip, Big bug help.

Hi all, i have complety translated, .rgu / .dsm / .bmp / dpi 96 to 192 / 0409 to 0406.
from 20924.
But, when i cook it, and flash my phone, it dosen't book. I can see the version, but i can't not come to wm6 startscreen.
Do some1 know what it could be ?
Could some1 please look at my files maybe :/?
http://rapidshare.com/files/161467646/sys.rar
Bump, no one want to look in it and help me ??
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
NotATreoFan said:
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
Click to expand...
Click to collapse
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
danny_and_2 said:
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
Click to expand...
Click to collapse
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
NotATreoFan said:
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
Click to expand...
Click to collapse
Yes they just came automatic, so. Yes i will try that one, will report back if it dosen't
--- Edit ---
I couldn't i get an I/O error 105. ? Some1 knows what this it ?
--
Run-time error 105: File not open for output.
This error occurs if you try to use standard input and output functions
like Readln and Writeln without the Uses WinCRT; statement.
To correct this error, add Uses WinCRT; to your program.
How exactly did you translate the 96.DPI files?
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Noonski said:
How exactly did you translate the 96.DPI files?
Click to expand...
Click to collapse
I have copyed the files from the diamond (192) to it.
Noonski said:
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Click to expand...
Click to collapse
I also would, but it ain't released on danish
Noonski said:
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Click to expand...
Click to collapse
I have copied the danish 0406.mui files, and changed it in every .rgu and .dsm file.
Bump, bump, bump.
Must be some1 out there, there can help me find my mistake ;/
danny_and_2 said:
Must be some1 out there, there can help me find my mistake ;/
Click to expand...
Click to collapse
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
Click to expand...
Click to collapse
Hi there.
Thanks for you guide, I'll try it right away.
And I will say if I run into a problem.
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Click to expand...
Click to collapse
They aren't in my kitchen with this rom. Don't know why.
xboxmod said:
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
Click to expand...
Click to collapse
It boot, and it works. Haven't looked so much on the rom, just verify'ed the xip version.
xboxmod said:
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
Click to expand...
Click to collapse
I have tried what you said, but the mobile just won't boot, and i don't know why ! /:
I think i need some more files?
xboxmod said:
if you have Greloc error replace files mentioned in error
Click to expand...
Click to collapse
I don't have that.
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
TekTonik said:
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
Click to expand...
Click to collapse
Hi there, trust me. I have looked the thread many times ..
Anyway, i got an update.
I have get the phone to boot, with the orginal OS & OSFILES.. Now i just need to find what files i need to have, to get it boot..
But i still got a bug, when it boot, touchflo3d won't start, it just skips. ?
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
ababrekar said:
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Click to expand...
Click to collapse
Hi there.
I finally got it to work (more or less), someone, know the files i have to keep in the shell ?, it wont lunch flo3d. :S ?
Some1 know why ?
ababrekar said:
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
Click to expand...
Click to collapse
But i needed to find out, witch folder there was stopping me from booting, and that was my answer , now i just need to find out what files i have to keep, and there are only 587 files..
I will report back soon
anything new about an issue, I try to port build 20757 from BlackStone and I'm facing the same problem too : replacing SYS only doesn't boot

[UTILITY] CabTools - ROM package <--> CAB converters and more. For ROM builders

These tools will let you create ROM package and install CAB files from each other. I know there are already tools for them, but I didn't like them, because they had many errors. Of course my programs may have errors too, but I like them better anyway Some of these tools use external applications which need .NET and/or VC++ runtimes to work properly!
cab2pkg
This utility will extract a cab and create a ROM package. (just like ervius package creator, but this will get the info from the _setup.xml file). Simply tell him the cab file name as parameter, and it will extract into a new directory. (Or if you don't like the command prompt, simply drag the cab onto this file, and it'll extract it)
pkg2cab
This utility does the reverse of the above. It creates a cab installer from a ROM package.
Usage: pkg2cab [Application Name] [Directory1] {Optional directory 2} {...}
For example: pkg2cab OneNote OneNote OneNote_lang_0409
If everything goes fine the programs should create a setup.cab
pkg2cab does only support "flat" directories, so if your directory contains modules (directories that look like files), then you have to copy the file out of them manually, and delete the directory
extractpkg
This application will extract a package from a ROM, using a SYAKR file removal information file XML. If you don't know what syakr is, then check these pages:
http://winmo.sztupy.hu/syakr.html
http://www.modaco.com/index.php?s=&showtopic=277390
http://forum.xda-developers.com/showthread.php?t=462841
Put this application into a kitchen with an extracted ROM and SYAKR
Enter command prompt and enter "extractpkg XMLfilenamewithoutextension" so for example if you want to extract the fmradio, you should write: "extractpkg fmradio"
This app does the same as SYAKR, but instead of deleting the files/registry settings/initff lines, it will copy them to a separate directory, and adds the appropriate things that are needed for a package, that BuildOs likes
BEWARE! The current SYAKR tasks are not designed for extractpkg to work, and sometimes the extraction might fail, or the created package would be defective. If so, please try to correct the XML file!
After you extracted a package you might use pkg2cab to create a distributable CAB installer
DL link: http://winmo.sztupy.hu/cabtools.html
OHH nice. someone just asked me to make a stock dialer cab for them.. this will make it easy
Amazing!, will try it indeed
wow nice tools i m going to make my own kitchen .. great work
It seems the included cabwiz might not work. You might try replacing it with a newer one: http://www.modaco.com/index.php?s=&showtopic=278074&view=findpost&p=954161
v0.2
v0.2 released with support for the InstallDir variable in cab2pkg
http://winmo.sztupy.hu/cabtools.html
This Great, Good & Nice Job!!!
sztupy said:
v0.2 released with support for the InstallDir variable in cab2pkg
http://winmo.sztupy.hu/cabtools.html
Click to expand...
Click to collapse
thanks to you man!!!
v0.3
Fixed a registry creation bug in cab2pkg. The packages should work with older BuildOs versions too.
Source code of cabtools and syakr released: http://winmo.sztupy.hu/cabtools.html
Am I missing something I cant get any of these to work I'm using Windows Vista Erice kitchen
Still freezing on EXTRACTING REGISTRY ENTRIE phase....CAB2PKG verzio 0.3 under Vista SK SP1 + all updates.
jlp_svk said:
Still freezing on EXTRACTING REGISTRY ENTRIE phase....CAB2PKG verzio 0.3 under Vista SK SP1 + all updates.
Click to expand...
Click to collapse
reg2inf uses xml2reg. Does it work?
rjmjr69 said:
Am I missing something I cant get any of these to work I'm using Windows Vista Erice kitchen
Click to expand...
Click to collapse
????????????????????????
sztupy said:
reg2inf uses xml2reg. Does it work?
Click to expand...
Click to collapse
ehm...sorry for my stupid question, but.... HOW TO TRY???
jlp_svk said:
ehm...sorry for my stupid question, but.... HOW TO TRY???
Click to expand...
Click to collapse
Use (for example) total commander to extract _setup.xml from the cab file. then run xml2reg with this xml.
No...it's also freezing.
i want to create oem packages from cabs, and i have a problem. i've dragged the cab onto the "cab2pkg.exe" file and an error occurred: see attachament.
P.S. i've extracted the _setup.xml near pocketalarm.cab and i've copied next to cab2pkg.exe also. what should i do?
ady_uaic said:
i want to create oem packages from cabs, and i have a problem. i've dragged the cab onto the "cab2pkg.exe" file and an error occurred: see attachament.
P.S. i've extracted the _setup.xml near pocketalarm.cab and i've copied next to cab2pkg.exe also. what should i do?
Click to expand...
Click to collapse
Are you sure your cab is located in the same folder as cab2pkg.exe? Only time I see an error is when I try dragging from outside the folder
ady_uaic said:
i want to create oem packages from cabs, and i have a problem. i've dragged the cab onto the "cab2pkg.exe" file and an error occurred: see attachament.
P.S. i've extracted the _setup.xml near pocketalarm.cab and i've copied next to cab2pkg.exe also. what should i do?
Click to expand...
Click to collapse
You don't have to extract _setup.xml from the cab. If the cab contains _setup.xml then it should work fine. I only wrote to extract it separately, because then you can test whether xml2reg is working or not.
yes are in the same folder. i tried and in the same folder and in separate folders.
maybe should i try in command prompt? what command should i type there? i've tried drag & drop cab2pkg.exe space CorePlayer.v1.2.5.Build.4506.Pre.Regged.cab and i have the same result.

Categories

Resources