Related
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
hey folks,
i have been investigating a rom by i-do
the main rom in it is NK.bin
any idea as to how i can decompile it????
i am a complete n00b at this so it would be great if someone could guide me
thanks
search for mamaich imgfs tools, then do:
prepare_imgfs.exe nk.bin
viewimgfs imgfs_raw_data.bin
pof said:
search for mamaich imgfs tools, then do:
prepare_imgfs.exe nk.bin
viewimgfs imgfs_raw_data.bin
Click to expand...
Click to collapse
ok thanks
i was able to create imgfs_raw_data.bin and imgfs_removed_data.bin
but when i run viewimgfs imgfs_raw_data. bin it creates dump_Memorymap.txt which is empty but no dump folder is made....
any ideas as to what i am doing wrong????
sorry don't know about the exact rom format u have, i suggest trying to use prepare_imgfs with '-acer' or '-nosplit', if that doesn't help, try to use the new tadzio tools.
pof said:
sorry don't know about the exact rom format u have, i suggest trying to use prepare_imgfs with '-acer' or '-nosplit', if that doesn't help, try to use the new tadzio tools.
Click to expand...
Click to collapse
did that....but still no luck....thanks anyway
Hi , last version of buildos+package tools....
try 4.2b3 version now.....
Last version 29.04.2008
http://rapidshare.com/files/111296473/kitchen.zip
improved real xipporting with buildxip.exe...
how it works...
dump xip.bin from same or other device; so you have xip\ folder annd romhdr.bin.
copy xip\ folder just created into my buildos by clicking on:"New Xip"
and then by pressing on: "port it" and selecting all xip->same or different device xip, you finally have new xip build ported into my kitchen, ready to be builded into "out.bin" by buildxip executed by all "CREATE_ROM_xxx.bat" files building new rom.
Code:
this last version has also load/save config, so you can preconfigure from
ultralight to full rom, load a config file and only by a click you have the
preferred rom to build, so you can publish in a bit all kind of roms you want!!!
this tool goes into kitchen or bepe's WM 6.1 one, or WM 6.1 of mine...
try it and post new bat and \TOOLS utils to extrac xip from other devices to make better it..
and also bat and \TOOLS utils to extract os.nb from other devices....
(I think the bats have to named like: "EXTRACT_DUMP.......bat" example: Extract_dump_from_kaiser; extract_Dump_from_hermes ecc... )
ervius said:
Hi , last version of buildos+package tools....
added:
to extract xip for non trinity roms, at dump\ analyzing... it execute a bat file...
all bat files to extract xip are stored into \TOOLS folder, and must have a name that starts with: "XIP_extract" example: XIP_extract_From_hermes.bat; XIP_extract_from_trinity.bat ecc....
try it... obviously there are a lot of devices, you can try for yours and post the bat to make bettere xip extracting of buildos , inside \tools folder, yet XIP_extract_from trinity.bat and XIP_extract_from_kaiser.bat
TODO:
extract from os.nb by other devices from executing others bat like xip extracting...
bye!
download here:
http://rapidshare.com/files/103757462/buildos_3.9b3.rar
try it and post new bat and \TOOLS utils to extrac xip from other devices to make better it..
and also bat and \TOOLS utils to extract os.nb from other devices....
(I think the bats have to named like: "EXTRACT_DUMP.......bat" example: Extract_dump_from_kaiser; extract_Dump_from_hermes ecc... )
Click to expand...
Click to collapse
Can you give us a description of your cooking?
cyron_at said:
Can you give us a description of your cooking?
Click to expand...
Click to collapse
to dump an nb file....
it need \dump folder and os.nb
outside folder.... open package tools.... and can rebuild oem\ and sys\
if you want you can insert also \xip folder using inside \tools bats....
choicing what device is from the os.nb and choice the right bat included, listed into a form with a max of 16 radiobutton to choice bat....
to build rom:
only open buildos choice rom dumped (oem\ sys\ xip\)
and it rebuild \dump folder, then, by executing a bat (that you can change to your use (also this can be implemented: more bats to have multidevices rombuilder....) and finally you have new os.nb or executing also ruu_updates_rom, the windoe to flash new ruu_signed).....
bye!
ervius said:
to dump an nb file....
it need \dump folder and os.nb
outside folder.... open package tools.... and can rebuild oem\ and sys\
if you want you can insert also \xip folder using inside \tools bats....
choicing what device is from the os.nb and choice the right bat included, listed into a form with a max of 16 radiobutton to choice bat....
to build rom:
only open buildos choice rom dumped (oem\ sys\ xip\)
and it rebuild \dump folder, then, by executing a bat (that you can change to your use (also this can be implemented: more bats to have multidevices rombuilder....) and finally you have new os.nb or executing also ruu_updates_rom, the windoe to flash new ruu_signed).....
bye!
Click to expand...
Click to collapse
...it need \dump folder and os.nb
-> which means I should extract rom?
--> How can I do this?
---> I am using the tools of RomDonald. Is this ok?
From the tool:
1.) Open: There I select my \Dump\folder
2.) How can I rebuild oem/sys?
Questions over questions...
Would you be so kind and make a few screen-shots?
I would be veryyyyyy happy!
Thx,
Chris
cyron_at said:
...it need \dump folder and os.nb
-> which means I should extract rom?
--> How can I do this?
---> I am using the tools of RomDonald. Is this ok?
From the tool:
1.) Open: There I select my \Dump\folder
2.) How can I rebuild oem/sys?
Questions over questions...
Would you be so kind and make a few screen-shots?
I would be veryyyyyy happy!
Thx,
Chris
Click to expand...
Click to collapse
read also this 3d...
http://forum.xda-developers.com/showthread.php?t=320504
Once XIP is extracted, what exactly gets done to port the XIP to trinity?
Thank ERVIUS
Very good tools ...
4.0b1 is borning, what about???
now:
1) it can dump os.nb from different devices (kaiser / hermes/trinity for now!) executing differents bat made just to dump them...
2) extract xip from different devices (kaiser/hermes/trinity for now!) by executing different bats made just to extract them...
3) build os (for trinity/hermews also ruu_signed.nbh) for different devices (kaiser/hermes/trinity for now)
I think tomorrow, ops today in the afternoon, I'll post it....
what I need???
that someone make some bats to dump/build os.nb for other devices, and bats to extract xip from other devices....
bye!!!
Build Packages,..
Hello!
There is an "error" while building packages:
When I say: Do not import XIP..-> There is no XIP folder in the rom -> Load rom does not work
When I say yes & import from trinty there is an error message :-(
However the XIP folder will be created. But the boot.rgu ... is not the boot.rgu from the origial rom. What must I do now?????
Any idea?
Thx
cyron_at said:
Hello!
There is an "error" while building packages:
When I say: Do not import XIP..-> There is no XIP folder in the rom -> Load rom does not work
When I say yes & import from trinty there is an error message :-(
However the XIP folder will be created. But the boot.rgu ... is not the boot.rgu from the origial rom. What must I do now?????
Any idea?
Thx
Click to expand...
Click to collapse
yes, wait the 4.0b1....
and test that one....
ervius said:
yes, wait the 4.0b1....
and test that one....
Click to expand...
Click to collapse
Sure! When do you think will the release be published?
cyron_at said:
Sure! When do you think will the release be published?
Click to expand...
Click to collapse
some minutes, I'm upping 19209 Italian kitchen that contains buildos-packagetools 4.0b1!!!
ervius said:
some minutes, I'm upping 19209 Italian kitchen that contains buildos-packagetools 4.0b1!!!
Click to expand...
Click to collapse
Thanks Ervius... Great News!!! i will test it tonight.
axl79 said:
Thanks Ervius... Great News!!! i will test it tonight.
Click to expand...
Click to collapse
yes...
if I'll able to upload it....
some connectivity problems.....
buildos is online.... version 4.0b2.....
to insert imto kitchen...
bye!
ervius said:
buildos is online.... version 4.0b2.....
to insert imto kitchen...
bye!
Click to expand...
Click to collapse
added v2 version of 4.0b1, some bugs solved on CREATE_ROM_***.bat executing...
ervius said:
added v2 version of 4.0b1, some bugs solved on CREATE_ROM_***.bat executing...
Click to expand...
Click to collapse
Thank you.. Really nice tool! Trying tonight!
hey ervius I can use this tools to build a 19209 rom? Are you going to release your versions?
GDT said:
hey ervius I can use this tools to build a 19209 rom? Are you going to release your versions?
Click to expand...
Click to collapse
yes, you can, I posted kitchen until this afternoon, and don't know if I'll post the 19209 rom...
version 3 in 1st post...
some improvements, soved other little bugs, added "execute CREATE_ROM_***.bat" flag by default and context menu to delete files on "search duplicete files" into rgu editor...
bye!
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