Related
Hello all,
Can anyone please post ace_ddi.dll found in AKU3.3 to be used in WM6?
This DLL has been (will be) applied in the new WMXL.2, but I don't feel like flashing my highly tuned device once again, so I simply wish to add this DLL to fix video corruption with TCPMP and CorePlayer...
So, anyone, please? thanks
Same here. Would really appreciate if someone could upload this dll.
shandar said:
Same here. Would really appreciate if someone could upload this dll.
Click to expand...
Click to collapse
look... download an AKU 3.3 ROM from the Wiki and then extract it... use ROM Kitchen or whatever if you like, but either way, do it yourself... it's easy enough
Get a full backup first. I applied ace_ddi.dll form Cingular AKU 3.3 to my WM6 and bricked. Had to hard reset to fix. I'm checking for diffs between that and the HTC ROM now...
Ai, that sucks. How exactly did you extracted that file from AKU3.3? If I do a ROM dump, I get a subdirectory called ace_ddi.dll instead of a file. That subdir contains a bunch of files. I looked into those files, none of them seems to be containing binary data what would represent the original file (no DLL entry point found). the S00* files combined seems to be the size of the file needed though, are they encoded in a different format? how do I convert that into the file I need?
you need to have RecMod.exe in the same directory as viewimgfs.exe IIRC or the dlls won't be created from modules. If its there, the reconstructed dll will also be in the folder.
Ah, thanks a bunch, that worked. gonna try applying it (but after a backup as you sugested)
Well... Have to report that once I applied it, the system doesn't boot anymore, and indeed a hard reset is needed.
How did it got integrated into WMXL.2 ?
The dll from the HTC 3.3 dump is identical.
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
kyphur said:
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
Click to expand...
Click to collapse
This is true, you cant do anything to them once they are active, I was trying to do this yesterday.
kyphur said:
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
Click to expand...
Click to collapse
Can you confirm that with the WMXL.2 release TCPMP can make use of the ATI decoder without scrambling the screen?
It didn't fix it for me...
Heimiko said:
Can you confirm that with the WMXL.2 release TCPMP can make use of the ATI decoder without scrambling the screen?
Click to expand...
Click to collapse
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Sleuth255 said:
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Click to expand...
Click to collapse
the trick is ....just replace the dll not the whole module.
Thought I tried that and the resultant dll was 0 bytes ... Must've been something I did... I'll try again.
Sleuth255 said:
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Click to expand...
Click to collapse
try this; install developer certs and sign the DLL with the privileged certificate, no doubt it'll work after that post-install.
Got it to work this time. Subsequent imgfs dump showed the correct size for ace_ddi.dll. The only thing I did different was put the ace_ddi.dll file itself into the same directory as addfile.exe... hard to believe it was that though. New Os.nb flashed just fine & i've got improved ImageON performance. It still pixelates somewhat but at least it doesn't tear up the whole screen any more...
must be my quirky kitchen
edit: notes on ImageON pixelation: There's some good workarounds for this that still retain ImageON acceleration in the Coreplayer forums. apparently things work better in landscape mode....
more on this: I didn't test right. When I set up coreplayer correctly, ImageON was still experiencing the same issues. My 8525 also showed this same problem on WM6 with the replaced ace_ddi.dll from the Cingular AKU3.3 rom. However, when I flashed the AKU3.3 ROM back onto my 8525, the problem went away
Conclusion: it would appear that there's more to this fix than simply the newer ace_ddi.dll
need original ace_ddi.dll
Sleuth255 said:
Get a full backup first. I applied ace_ddi.dll form Cingular AKU 3.3 to my WM6 and bricked. Had to hard reset to fix. I'm checking for diffs between that and the HTC ROM now...
Click to expand...
Click to collapse
Hi! Can you give me the ace_ddi.dll from rom, please?
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 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
(the steps below are so easy. please do not ask me to send you the rom unless you upload it to an unlimited server for other x04ht users. thanks.)
having been fighting with the dumped rom for two weeks, i finally could rebuild x04ht rom from dumped raw files. i thought i should share my experience with other x04ht users although it is nothing really special. general guides say, "just put raw files into the baserom folder with a base rom and run the kitchen", but this does not work.
see here if you do not know how to dump roms.
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
assume you know how to use kaiser kitchen and dos commands and already have part0x.raw files and RUU_signed.nbh.
RUU_signed.nbh of cht rom recommended.
1) put Part01.raw, Part02.raw and RUU_signed.nbh in BaseROM folder
2) run !BEGIN.cmd and choose 1 to extract shipped rom
3) when it's done, you see temp, oem, rom and sys folders in the kitchen
4) delete oem, rom and sys folders because you don't need them now
5) copy XIPPort.exe to temp folder
6) copy Part01.raw to temp folder
7) rename Part01.raw to xip.bin
8) run XIPPort.exe
9) click "dump xip.bin" and you will see OUT folder now
10) there is boot.rgu in OUT\FILES. copy it to your desktop or somewhere
11) click "build xip_out.bin"
12) change the first box from 00310000 to 00320000, and the second from nk.nb to OS.NB.Payload
13) click "write xip_out.bin"
14) open command prompt and go to temp folder
15) type "..\TOOLS\NBMerge -kaiser os.nb" in command prompt
16) when NBMerge is done, close command prompt
17) copy os.nb to your desktop or somewhere
18) delete temp folder
19) run !BEGIN.cmd and choose 2 to extract dumped rom
20) when it's done, you see temp, oem, rom and sys folders in the kitchen
21) copy boot.rgu to rom\xip folder and replace OS.NB in rom folder by the one you created above
22) your kitchen is ready to use
does anyone hep me upload the rebuilt rom?? thanks.
qt
qtotter said:
having been fighting with the dumped rom for two weeks, i finally could rebuild x04ht rom from dumped raw files. i thought i should share my experience with other x04ht users although it is nothing really special.
see here if you do not know how to dump roms.
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
first of all, i used kaiser kitchen. what you need is Part01.raw, Part02.raw and RUU_Signed.nbh (i used the htc shipped wwe rom.) general guides say, "just put all these files into the baserom folder and run the kitchen", but this does not work.
second step is just usual. run the kitchen to extract oem, sys and rom. after this step, you will have OS.NB in the "rom" folder. you need to change this file to make the kitchen work. you need to make OS.NB.Payload from OS.NB. to do so, just execute "NBSplit.exe -kaiser OS.NB"
now, you need XIPPort.exe, Part01.raw and OS.NB.Payload. copy OS.NB.Payload and Part01.raw to the folder where you have XIPPort.exe, and rename Part01.raw to xip_out.bin. run XIPPort.exe. you will see two boxes on the bottom. change the first box from 00310000 to 00320000, and the second box from nk.nb to OS.NB.Payload. finally, click "write xip_out.bin", and you have a new OS.NB.Payload.
you will make a new os.nb from this OS.NB.Payload by "NBMerge -kaiser os.nb"
just replace os.nb in the kitchen "rom" folder by this new os.nb. and now you can start cooking a rom.
does anyone hep me upload the rebuilt rom?? thanks.
qt
Click to expand...
Click to collapse
Hello qt
ohisashiburi... you can upload the rom to my server. no limitations.
How do you solve the Smail! problem? MMS lite craps itself every now and then.
I am using 2 touch pro since July, so I have no idea what SB uses for
their Smail. The old softbank mail app doesnt work anymore..
aquasesh said:
Hello qt
ohisashiburi... you can upload the rom to my server. no limitations.
How do you solve the Smail! problem? MMS lite craps itself every now and then.
I am using 2 touch pro since July, so I have no idea what SB uses for
their Smail. The old softbank mail app doesnt work anymore..
Click to expand...
Click to collapse
address of your server? thanks.
x04ht has Arcsoft's mms client for smail (softbank mms), which is integrated into wm messaging and much faster/better than access' slow mms client provided at sb's x series site. there must be some trick with it (maybe, checking language/locale setting or certificate), and it did not run on wwe rom. been preoccupied with dumped rom reconstruction, i haven't had much time to play with this program yet.
this x04ht rom has many japanese apps and 411 muis, and am sure many can play with it to make our sb devices working better!
qt
qtotter said:
having been fighting with the dumped rom for two weeks, i finally could rebuild x04ht rom from dumped raw files. i thought i should share my experience with other x04ht users although it is nothing really special.
see here if you do not know how to dump roms.
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
first of all, i used kaiser kitchen. what you need is Part01.raw, Part02.raw and RUU_Signed.nbh (i used the htc shipped cht rom.) general guides say, "just put all these files into the baserom folder and run the kitchen", but this does not work.
second step is just usual. run the kitchen to extract oem, sys and rom. after this step, you will have OS.NB in the "rom" folder. you need to change this file to make the kitchen work. you need to make OS.NB.Payload from OS.NB. to do so, just execute "NBSplit.exe -kaiser OS.NB"
now, you need XIPPort.exe, Part01.raw and OS.NB.Payload. copy OS.NB.Payload and Part01.raw to the folder where you have XIPPort.exe, and rename Part01.raw to xip_out.bin. run XIPPort.exe. you will see two boxes on the bottom. change the first box from 00310000 to 00320000, and the second box from nk.nb to OS.NB.Payload. finally, click "write xip_out.bin", and you have a new OS.NB.Payload.
you will make a new os.nb from this OS.NB.Payload by "NBMerge -kaiser os.nb"
just replace os.nb in the kitchen "rom" folder by this new os.nb. and now you can start cooking a rom.
does anyone hep me upload the rebuilt rom?? thanks.
qt
Click to expand...
Click to collapse
Hey,
Thanks for the info, but I tried, and couldn't get it to work.
First step, you said that it doesn't work, so what was that works? the second and third that makes it work???
The second step, where did you have to put the Split? because just clicking it will not make it run... and so it is with the third step too
Thanks
Harry8521 said:
Hey,
Thanks for the info, but I tried, and couldn't get it to work.
First step, you said that it doesn't work, so what was that works? the second and third that makes it work???
The second step, where did you have to put the Split? because just clicking it will not make it run... and so it is with the third step too
Thanks
Click to expand...
Click to collapse
i wrote a step by step guide in the first post. check it out.
qtotter said:
i wrote a step by step guide in the first post. check it out.
Click to expand...
Click to collapse
Thanks!! I'll try it out.
助かりました
i need your X04HT rom ,please help me .
my msn is
[email protected]
yorosikune
qtotter said:
i wrote a step by step guide in the first post. check it out.
Click to expand...
Click to collapse
qtotter san,
can you send the X04HT ROM to me,
Thank you very much
my email: [email protected]
I need your X04HT rom... plz...
plz send to my msn.
my msn : [email protected]
thanks.
lanpililg said:
i need your X04HT rom ,please help me .
my msn is
[email protected]
yorosikune
Click to expand...
Click to collapse
esc166 said:
I need your X04HT rom... plz...
plz send to my msn.
my msn : [email protected]
thanks.
Click to expand...
Click to collapse
ylyu said:
can you send the X04HT ROM to me,
Thank you very much
my email: [email protected]
Click to expand...
Click to collapse
are you 3 joking?
http://rapidshare.com/files/173269516/RUU_X04HT_1.73.762.15_no_radio.zip
Kevbodian said:
are you 3 joking?
http://rapidshare.com/files/173269516/RUU_X04HT_1.73.762.15_no_radio.zip
Click to expand...
Click to collapse
Hi Kevbodian
this Zip file is CRC error.
Any chance for a reupload?
Cheers
Sebastian
Sebaschan said:
Any chance for a reupload?
Cheers
Sebastian
Click to expand...
Click to collapse
i have the file Original_X05HT_ROM_081207.rar
Its not X04HT
ROM Development
hi people... im keen on developing ROMs.. and i searched all over XDA and found this to be the nearest one... can somebody direct me to the right forum or give me an explanation on how to do it?? thank you and i have the kitchen downloaded
well, i tried asking people here but seems like no one is interested to answer my questions please i've searched on google yahoo microsoft, xda...etc you name it. i just couldn't get the answers to this question...
does anyone know how to create .nbh file from 4 raw files that i have dumped from my diamond?
if anyone wants to make me a nbh file(i doubt it....) or take a look at my dumped file, i have post them up in mediafire
part1
http://www.mediafire.com/?1wxm1zdj6tv
part2
http://www.mediafire.com/?nbnl2wytxd0
I rebuilt a ROM from your dumped raws.
You can do it yourself though with the kitchen from my sig.
Don't forget to place a donor os.nb.payload in the casserole folder, or any 2.0 version DIAMIMG.nbh in the "source" folder.
are you going to post that rom up anywhere?
I will post it up for you tomorrow.
Can't do it now since I don't have a windows workstation at home to rebuild it.
Do you want the broken-out version (sys, xip, oem) or nbh?
if i can get nbh file, that will be great thank you so much!!!
did you create nbh files from my raw files? or did you use wwe nbh files? just curious