Related
Hi,
I write some code that can modify the ROMs, it can save your time to add and delete files by hand.
RomMaster V2.0 Beta
Usage: RomMaster [options] imagefile
-d[m] <dfile> - delete file
replace file/module together with -a option
'm' delete module, deleting module isn't suggested
-a[c] <afile> - add file into the rom
'c' means use compress(need CECompressv4.dll)
-o <ofile> - output imagefile name
-v <0~9> - print info, 0 detail, 9 only show errors, default is 5
-w <5> - 5 is 2005, default is 2003&SE
-x - only save XIP(OS) data
-s <0x...> - Fix XIP start address(Hex)
-e <0x...> - Fix XIP end address(Hex)
In replace mode, 'c'&'m' is useless
It is now 2.0 Bata Release.
You can delete file/modules you don’t like from the ROM.
RomMaster –d “filename” –o “newROMname” “ROMname”
You can add files into the ROM.
RomMaster –a “newfilename” –o “newROMname” “ROMname”
You can replace file in the ROM
RomMaster –d “filename” –a “newfilename” –o “newROMname” “ROMname”
“newfile”’s size should be the same or small than the file you want to replace, new file will occupy the same space as the old one.
I test some ROM in my SP; include SDA, Dopod 575 & 585. I only tested one 2005 ROM. Replace module may don’t work, I am still working on it.
Before you burn the image generated by the tool, make sure you finish follow step:
1. RomMaster –o “TestROM” “SrcROM”
2. Do binary compare “SrcROM” with “TestROM”
a) If they are 100% same, I think you can safely use this tool.
b) If they are 99% same, you should be careful, make sure you only burn the OS part. Because some ROM are modified by someone before, there are maybe some useless data in the ROM, only burn the OS part won’t damage your SP.
c) Else, the “SrcROM” may contain some unknown structure or data, the “TestROM” may won’t work, don’t try burning it into you SP. If you want to modify it, tell me where I can find the ROM, if I am free, I can give some help.
3. I only tested one 2005 ROM, its structure isn’t very correct, and I think that ROM is extracted form emulation ROM. So if 2005 ROM isn’t 100% same, don’t try and be careful even they are 100% same.
This is great!!!
Going to try it!
ncruz,
I'll wait for your experience, cause if this is working we can all save space by directly burning upgraded cameras etc into the rom. will save me at least 1MB ram or storage.
The tools sounds great gmap.
There already exists MKROM tool - http://www.xs4all.nl/~itsme/projects/xda/romtools.html
it is 100% working with WM2003/2003SE devices. But it is rather inconvenient.
I'll test your "-w 5" option on a real device. Real WM5 device has one XIP kernel section with only few modules and about 1Mb free space. All other data is kept in IMGFS partition, I'm currently working on a tool that would work with it.
And one question. When you add new files to ROM, do you add them to a new XIP or extend the existing XIP? And when you delete modules, do you reuse the freed space after adding new ones?
mamaich said:
There already exists MKROM tool - http://www.xs4all.nl/~itsme/projects/xda/romtools.html
it is 100% working with WM2003/2003SE devices. But it is rather inconvenient.
I'll test your "-w 5" option on a real device. Real WM5 device has one XIP kernel section with only few modules and about 1Mb free space. All other data is kept in IMGFS partition, I'm currently working on a tool that would work with it.
And one question. When you add new files to ROM, do you add them to a new XIP or extend the existing XIP? And when you delete modules, do you reuse the freed space after adding new ones?
Click to expand...
Click to collapse
That's great if we can modify IMGFS partition I am waiting for it.
I know that tool and i don't know how it works. I made this tool only for interesting.
You can find XIP chain in 2003 ROM, by XIP chain, you can know the address and length of each XIP section. I will scan the hole XIP region before inserting the new file to reduce memory fragment. When a module is deleted, its space will be freed and reused when adding files. I freed about 6M space in my own ROM by deleteing the useless files, and add about 5M files into it, it works OK.
It seems 2005 don't have XIP chain information in the ROM, i only test one 2005 ROM, and i didn't find the XIP chain info. If your 2005 ROM don't have XIP chain info too, you should modify ROMHDR.physlast to a correct value by hand. Because if i can't find the XIP chian info, I use ROMHDR.physlast to decide the end address of XIP. Or, there are almost no space for you to add new file. My 2005 ROM physlast=0x8c253278, and only about 78732 bytes free before 0x8c253278.
I update the the tool V2.2 , fixed a bug when deeling with MDA(818) ROM.
gmap said:
That's great if we can modify IMGFS partition I am waiting for it.
Click to expand...
Click to collapse
I've PMed you a test version. I'll make it available to public later.
... If your 2005 ROM don't have XIP chain info too, you should modify ROMHDR.physlast to a correct value by hand.
Click to expand...
Click to collapse
My ROM has all needed info, I had to extract everything from rom image after 1C0000 address to a separate file and gave it to your tool. It is working perfectly. I've managed to delete and add a new file to ROM. I have not tested "-dm" option. It seems that all modules/files in XIP section of WM5 are uncompressed. I'm using BlueAngel's WM5 ROM. Later I'll try to replace boot.hv file with my own version.
Can you add a switch to your program "-s bytes" so that it woud skip the given number of bytes from file start, so it would be possible to work directly on NBA files with header?
gmap, can you tell me what file i can use this with? Is it for nbk or nba files? Thanks
I'm not able to edit the xip sextion ...
i've tried your tool on 1.60c.07CHS rom for xdaII :
RomMaster.exe -w 5 -x -o test.bin nk.nba
result :
[Info] It is a common ROM.
[Error] File is damaged, end address small than start address.
[Error] File is damaged, end address small than start address.
RomMaster.exe -w 5 -x -o test.bin imgfs_raw_data.bin (created with mamaich's tool)
result :
[Info] It is a common ROM.
[Error] Load nb00 failed.
RomMaster.exe -w 5 -x -o test.bin img.bin (created by nba part 1C0000 to end)
result :
[Info] It is a common ROM.
[Error] File is damaged, end address small than start address.
[Error] File is damaged, end address small than start address.
How to save the XIP section ?
TofClock said:
RomMaster.exe -w 5 -x -o test.bin imgfs_raw_data.bin (created with mamaich's tool)
Click to expand...
Click to collapse
This would not work. My tool works with IMGFS and you need to edit XIP
and ... how to edit XIP ?
mamaich said:
My ROM has all needed info, I had to extract everything from rom image after 1C0000 address to a separate file and gave it to your tool. It is working perfectly. I've managed to delete and add a new file to ROM. I have not tested "-dm" option. It seems that all modules/files in XIP section of WM5 are uncompressed. I'm using BlueAngel's WM5 ROM. Later I'll try to replace boot.hv file with my own version.
Can you add a switch to your program "-s bytes" so that it woud skip the given number of bytes from file start, so it would be possible to work directly on NBA files with header?
Click to expand...
Click to collapse
mamaich, or anyone else, what did you use to extract after 1C0000?
splitrom?
any help would be greatly appreciated.
Russ
Wow , just an hex-editor like winhex or edithexa
i tried that w/xvi32, and it didn't seem to work. I guess I'll try again
Thx gmap for this great tool. 8)
Recently I want to replace the TureFFS.dll at the XIP area of Wizard OS ROM.
ftp://xda:[email protected]/Uploads/HTC_Wizard/Roms/Qtek/Qtek_9100_1_6_7_ENG__OS_ONLY.zip
I type the following command and it says that it cannot replace the file.
Code:
D:\>RomMaster.exe -d TrueFFS.dll -a TrueFFS.dll -w 5 -o new.nba os.nba
[Info] It is a common ROM.
[Warning] o32_rom(0x8c268ef8)'s o32_data at 0x00000000 is zero.
[Warning] Found dif-referenced region [OLD] Address=0x8c1e1290 Length=0x00000800 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c1e1290 Length=0x00000800 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x8c1fe538 Length=0x00000600 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c1fe538 Length=0x00000600 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x8c211018 Length=0x00000a00 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c211018 Length=0x00000a00 ObjectType=0x00008000
[Warning] Memory Block(0x8c101000,0x8c1510ac) overlap with Block(0x8c10288c,0x8c1028b8).
[Error] You want to get an object whose size is 108, but it is 112. RomOffset=0x8c268e00
[Error] Could not replace 'TrueFFS.dll' with 'TrueFFS.dll'.
However, I can successfully replace the boot.hv file. Do you know why?
ahlok_hk said:
Thx gmap for this great tool. 8)
Recently I want to replace the TureFFS.dll at the XIP area of Wizard OS ROM.
ftp://xda:[email protected]/Uploads/HTC_Wizard/Roms/Qtek/Qtek_9100_1_6_7_ENG__OS_ONLY.zip
I type the following command and it says that it cannot replace the file.
Code:
D:\>RomMaster.exe -d TrueFFS.dll -a TrueFFS.dll -w 5 -o new.nba os.nba
[Info] It is a common ROM.
[Warning] o32_rom(0x8c268ef8)'s o32_data at 0x00000000 is zero.
[Warning] Found dif-referenced region [OLD] Address=0x8c1e1290 Length=0x00000800 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c1e1290 Length=0x00000800 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x8c1fe538 Length=0x00000600 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c1fe538 Length=0x00000600 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x8c211018 Length=0x00000a00 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c211018 Length=0x00000a00 ObjectType=0x00008000
[Warning] Memory Block(0x8c101000,0x8c1510ac) overlap with Block(0x8c10288c,0x8c1028b8).
[Error] You want to get an object whose size is 108, but it is 112. RomOffset=0x8c268e00
[Error] Could not replace 'TrueFFS.dll' with 'TrueFFS.dll'.
However, I can successfully replace the boot.hv file. Do you know why?
Click to expand...
Click to collapse
In replace mode, new file should not biger than old file. So, you should delete old 'TrueFFS.dll' first, then add the new one(You can delete some file next to 'TrueFFS.dll' to get free space or move it to a big free space, then modify the file size and related infomation of 'TrueFFS.dll' by hand to make it bigger). Replacing module isn't stable, I confused by some of the module data. If you want to replace a module, it may not work. I haven't find a way that can be used to calculate all of the data.
gmap said:
In replace mode, new file should not biger than old file. So, you should delete old 'TrueFFS.dll' first, then add the new one(You can delete some file next to 'TrueFFS.dll' to get free space or move it to a big free space, then modify the file size and related infomation of 'TrueFFS.dll' by hand to make it bigger). Replacing module isn't stable, I confused by some of the module data. If you want to replace a module, it may not work. I haven't find a way that can be used to calculate all of the data.
Click to expand...
Click to collapse
Thx for your explanation. Actually the new file is smaller than the one being replaced. And I just found that I can only delete those non-module files while all modules could not be deleted.
Thx again. Hope to see new version if you have time to find out how to calculate the data. :wink:
How can i extract a kernel file (kbbdrv.dll)?
thanks
dherrero said:
How can i extract a kernel file (kbbdrv.dll)?
thanks
Click to expand...
Click to collapse
dumprom tool
But if you'll extract this or any other XIP DLL and then readd it to the same, or any other ROM it would not work.
Hello,
I have a Apache Rom,
I would like to delete nk.exe are replace it.
iv tryed:
rommaster -w 5 -d nk.exe nk.nba
also
rommaster -w 5 -d nk.exe -a nk.exe nk.nba
keeps telling me i can delete that file.
just to let you know: if i use dumprom i get the boot partition files (containing nk.exe) and if i use imgfs i get all the os files (not containing nk.exe)
Any help would be great thanks
you cannot delete nk.exe, and you should not even need to do that.
How to:
1. Extract Polaris_Kitchen and put it in C:\ , so we will be C:\Polaris_Kitchen
2. In Polaris_Kitchen\TOOLS\Polaris.htcrtproj set:
VersionId
LanguageId
3. Put your packages inside OEM
4. Execute BuildOS and select/deselect packages that want to include in your ROM then start it and at the end of his work close it.
5. Execute Build ROM.bat
6. Please Wait
7. That's all, inside FLASH directory will be a RUU_signed.nbh ready to flash!
General information:
OEM: HTC Polaris 3.13.405.0
SYS: HTC Polaris WWE 3.13.405.0 - (Build 19965.1.2.3)
Useful Links
Polaris Hard SPL v2
Polaris CustomRUU
Custom Splash Screen
Thanks to:
bepe for his BuildOS
Dark Simpson for his HTC ROM Tool
misar for G'Reloc
Olipro for his Hard-SPL
tadzio for ImgFS Tools
Changelog:
Code:
What's new in v1.4?
[+] Updated the kitchen to Official HTC ROM
[+] Updated OS CE 5.2.19965 (Build 19965.1.2.3)
What's new in v1.3?
[+] Updated OS CE 5.2.19214 (Build 19214.1.0.4)
What's new in v1.2?
[+] Updated OS CE 5.2.19209 (Build 19209.1.0.2)
[+] Updated OEM part - Polaris CHT 1.52.753.3
[!] Fixed Ringtone Settings problem
[!] Fixed USB to PC, now it's in Connections
[!] XIP rebuild
What's new in v1.1?
[+] New SYS part from AT&T Kaiser ROM (Build 19209.1.0.2)
[+] Updated to .NET 3.5 Compact Framework
[+] Voice Command 1.6.19209
[!] Fixed small issue in the Kitchen
Download:
Polaris Kitchen v1.4
Password: Polaris_Kitchen_v1.4
Download Improved "Build Rom.bat":
Build ROM.zip (thanks to worstenbrood)
Note: I improved "Build Rom.bat" a bit so you can use the kitchen from ANY directory, not only C:\Polaris_Kitchen, adjust the 2 environment variables at the beginning (set version_id=... and set language_id=...) to your needs and execute buildos.exe, then "Build Rom.bat".
Download base ROM in other languages:
FRA
GER
NLD
ITA
NOR
PTG
SPA
RUS
How to extract and reconstruct OEM and SYS parts:
P.S.: OEM part must be an Polaris OEM, not from other devices!
1. To extract .nbh files you need NBHextract.
Put your .nbh file and nbhextract.exe into a directory
From prompt commands: nbhextract file_name.nbh
Delete all extracted files except xx_OS.nb
Rename xx_OS.nb in OS.nb
2. To extract OS.nb files you need ImgFS Tools (v2.1rc2)
Extract all files inside the zip into the same OS.nb directory and from prompt commands:
nbsplit -kaiser OS.nb
imgfsfromnb OS.nb.payload imgfs.bin
imgfstodump imgfs.bin
We have dumped the ROM and than we need reconstruct OEM and SYS parts, to make this need PKG Tool.
This step it's very simple, open the dump directory with PKG Tool than Tools -> Build Packages
Ok now we have OEM and SYS parts.
!! Remember, use only OEM part from Polaris ROM don't use from other device or your ROM don't boot. !!
How to create a package from a .cab
There is a very very powerful tool to do this, Ervius Package Creator (EPC).
1. Download latest version of EPC from his thread.
2. Select your ROM Language.
3. Select Package's group.
4. Click on Open Cab File than select your cab.
5. Copy the directory created inside your OEM directory.
5. Done!
Thanks to my friend Ervius for this awesome tool
hi friend, I'm happy to see that works go on, and with a fantistik kitchen....
I think so, people will be able to eat somethings good!!!!!
Thanks for all work i'll try it for the next flash
Hi UDK, I always attend to taste your rom on my polaris
Yes thanks man a good explanation to cook a rom i was waiting for this
Hi Udk i'ts to make wwe version?
Do you also have an tutorial for how to make WM 6.1 Translate to Dutch or any other language ?
HTC Touch Dual Dialer for Touch Cruise
Hello,
the touch cruise dialer satisfy me not. I saw the dialer in Youch dual and it's much better.
Can I replace mine for touch dual dialer? What should I do to replace?
PS: I thought there is a .cab with dialer, I should just luanch it and it will remove the previous one himself, but I cannot find such a .cab. Help.
Another question, if I finally replace my dialer with another one - will the view of "Calls list" be replaced with the new one? I wish it will.
infido said:
Hi Udk i'ts to make wwe version?
Click to expand...
Click to collapse
Yes it's WWE.
lexi1986 said:
Do you also have an tutorial for how to make WM 6.1 Translate to Dutch or any other language ?
Click to expand...
Click to collapse
Need only to change OEM (Polaris OEM) and SYS (Kaiser SYS) from a Dutch ROM.
Can you explain me What i must do to get the KAISER NLD SYS en what the POLARIS OEM is ?? I have download the WM 6.1 Dutch but it's an .NBH file for the Kaiser. I hope you can help.
lexi1986 said:
Can you explain me What i must do to get the KAISER NLD SYS en what the POLARIS OEM is ?? I have download the WM 6.1 Dutch but it's an .NBH file for the Kaiser. I hope you can help.
Click to expand...
Click to collapse
First all you need an Official Polaris Dutch ROM (find it here) to extract OEM part only.
To extract .nbh files you need NBHextract.
To extract OS.nb files you need ImgFS Tools
nbsplit -kaiser OS.nb
imgfsfromnb OS.nb.payload imgfs.bin
imgfstodump imgfs.bin
To reconstruct OEM and SYS parts you need PKG Tool
Remember, OEM from Polaris and SYS from Kaiser, don't mix them!
Then put your OEM and SYS in C:\Polaris_Kitchen (delete existing).
Open ROM\XIP\boot.rgu and change:
[HKEY_LOCAL_MACHINE\MUI]
"SysLang"=dword:409
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:409
to
[HKEY_LOCAL_MACHINE\MUI]
"SysLang"=dword:413
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:413
save and exit.
That's all.
Thanks i will try youre great.
DONE: now i have to wait for the Polaris Kitchen youre great i hope this work. The Download link is availible tonight ?
Edit: Nevermind there are online great work
Cant download Part1 or 2 "This file is currently set to private. This error has been forwarded to MediaFire's development team" came up
lexi1986 said:
Thanks i will try youre great.
Click to expand...
Click to collapse
Try, it's not difficult
omaga said:
Cant download Part1 or 2 "This file is currently set to private. This error has been forwarded to MediaFire's development team" came up
Click to expand...
Click to collapse
part1 and part2 are now online!
Have fun
Thank you UdK!
very fantastic UDK
moderator... Sticky thread???
I get an Error: The File temp\packages\75bcd9fa-30b9-8705-5d86-11acd2e2c1b1.dsm already exists
after that the BuildOS stops.
Edit: After closing BuildOS the file Buildrom.bat is busy with things maybe it's going to be ok.
I have got a .nbh file now i going to flash and look if it is working.
Edit: Flashing has worked but my phone is hanging on boot any idea ???
If BuildOS returns error close it and then close prompt commands, don't flash the .nbh.
I will fix this, If buildos returns error automatically stops all others tools.
Hello my friends !
I search how cooking rom from a bin file of 32M !
I know how do it from a nbh file or nb file, but i don't knwo how to do from a bin file !
Which tool using ?
Great Thanks !!!!
you need imgfstools2 to extract the bin / recreate a nbh
Thanks for you fast answer !
So i will re-tets with imgfs2rc2, but i think that i don't function
I re-test !!!
from the readme
ReadMe said:
On a high level, this is the chain of actions needed to unpack OS.nb:
RUU-signed.nbh ---(*NBHExtract)---> OS.nb ---(NBSplit)---> OS.nb.payload -->
--(ImgfsFromNb)---> imgfs.bin ---(ImgfsToDump)---> 'dump' directory
Here you'll edit the 'dump' directory. I recommend using bepe's excellent *Package Tool for this.
The reverse process is:
'dump' directory ---(ImgfsFromDump)---> imgfs-new.bin ---(ImgfsToNb)--->
OS-new.nb.payload ---(NBMerge)---> OS-new.nb ---(*NBHGen)--->
RUU-signed-new.nbh
(The tools marked with '*' are not part of the ImgfsTools, but are also available for free from xda-developers.com. There is also one additional tool, NBInfo, in this package.)
Click to expand...
Click to collapse
With imgfs 2.1 RC, I use :
imgfstodump winceimg.bin
And i result :
"Cannot map file winceimg"
Nixeus said:
With imgfs 2.1 RC, I use :
imgfstodump winceimg.bin
And i result :
"Cannot map file winceimg"
Click to expand...
Click to collapse
sorry i just knew what tools to use - im sure someone else can help you further though.
I will continue to investigate !!!
thanks'' !!
Hello,
I want to cook my own ROM. After I read many many sites at this forum, I found a 'polaris kitchen 1.3' that seems to be good for me.
I want to use the original WM6.1 O2-ROM as base for my 'new' ROM.
My target is the original ROM without some progs (O2 specific) an also without tomtom, 'Erste Schritte' (First Steps) and opera.
I want to add MyMobiler, and some other cabs. Also, I want to make some registry corrections.
These steps I made:
1. Extract the Updatefile with 7Zip and got the neccassary file 'RUU_signed.nbh' as I understand correctly.
2. Extract the 'RUU_signed.nbh' with this command
Code:
NBHextract.exe RUU_signed.nbh
Now, I have these files
- '00_Unknown.nb', <== Radiofile (Thanx to ianl8888)
- '01_SPL.nb', <== ???
- '02_MainSplash.bmp', <== O2 BootSplashScreen Bitmap
- '02_MainSplash.nb' <== ???
- '03_OS.nb' <== OS file which we need to split
Question1: Do I need only the '03_OS.nb'? What do i need the other files for?
3. I used this command to split the nb-File '03_OS.nb'
Code:
NBSplit.exe -kaiser 03_OS.nb
I got this:
- '03_OS.nb.payload'
- '03_OS.nb.extra'
Question2: Is it OK to use the parameter -kaiser? Remember, I will create a orbit2/polaris ROM
Question3: What are this files for?
4. now I used this command
Code:
imgfsfromnb 03_OS.nb.payload imgfs.bin
to build the 'imgfs.bin' file
5. with the following command I've created a 'dump' folder
Code:
imgfstodump imgfs.bin
This dump folder include many subfolders and files
6. I start the package tool 'PKGTool.exe' an selected the dump-Folder
The output:
Code:
[Selected Path]
C:\Extracted ROM\dump
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.19965.1203
OEM: 3.13.0.0
OEM: 0.0.1.0
SYS: 5.2.19958.1200
NET: 2.0.7045.0
OEM: 29.6.31301.207
OEM: 29.3.31301.207
[Language]
0407 - German (Germany)
[DPI]
96
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=OEM_UpdateCert
CN=O2___102
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
3346da5d-3675-4a67-925e-75f623184bda.dsm
98af2d70-895d-99af-0ffc-ede71fc1186d.dsm
75bcb9fa-30b9-8705-5d86-11acd2e2c1b1.dsm
Question4: Everything OK till now?
7. Now I've selected 'tool' - 'build packages'
Inside the dump folder, I've only two subfolder 'SYS' and 'OEM'
Maybe this is the next step ... (Thanx to ianl8888)
8. Now we must dump the 'xip.bin' with this command:
Code:
RomMaster.exe 03_OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
Question5: What to do next?
Hi,
that is exactly the same I wanna do. After you have the SYS and OEM folder the next would be to re-create the ROM folder for your kitchen. We need a new XIP. That is the point where I don't know how to continue. I have already tested to replace the original SYS and OEM with those versions I build via dumping the new O2 Germany ROM. But after trying to rebuild and flashing the ROM with the kitchen the ROM won't boot.
Therefore I asked the chefs at http://forum.xda-developers.com/showthread.php?p=2657634 to help me.
Hopefully we can take a step further.
Tom
I have already managed to build a new german rom based on the
O2 GER 3.13 released some days ago and I used the XIP 20743 from
Shayders thread to build. Had no errors in cooking but I did not
flash yet because of maybe wrong location of XIP files in the ROM.
But I have another problem with HTC ROM Tool when trying to cook
the radio 1.59.42.15 (or any other) in the ROM. The tool always states:
"The size of this file is greater than default. Do you want to assign this file?"
I said yes and it builds the rom but now I don't know if it would work
because of the warning. I tried different radio.nb files and all of them
are 17MB and all of them give the error in HTC ROM Tool when assigning
them... Is this normal?
Olioaglio
Orbitter2 said:
Hello,
6. I start the package tool 'PKGTool.exe' an selected the dump-Folder
The output:
Code:
[Selected Path]
C:\Extracted ROM\dump
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.19965.1203
OEM: 3.13.0.0
OEM: 0.0.1.0
SYS: 5.2.19958.1200
NET: 2.0.7045.0
OEM: 29.6.31301.207
OEM: 29.3.31301.207
[Language]
0407 - German (Germany)
[DPI]
96
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=OEM_UpdateCert
CN=O2___102
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
3346da5d-3675-4a67-925e-75f623184bda.dsm
98af2d70-895d-99af-0ffc-ede71fc1186d.dsm
75bcb9fa-30b9-8705-5d86-11acd2e2c1b1.dsm
Question4: Everything OK till now?
7. Now I've selected 'tool' - 'build packages'
Inside the dump folder, I've only two subfolder 'SYS' and 'OEM'
Question5: What to do next?
Question6: Should I copy these folder to the kitchen?
Click to expand...
Click to collapse
I don't know how to proceed yet with the "re-building stage", but I think you are still 3 steps short of this, anyway:
we need the XIP.BIN file to use the XIPPORT.exe tool on for XIP Files\Modules. The XIP build no. I have extracted is 19965, but we are already at 20753 for the device-independent MS files
I do NOT yet know how to extract the XIP.BIN file for this. I have successfully extracted it from an Eten temp.dat file (nbh equivalent) but not for HTC ROM files.
So I think we need to do steps 7,8,9 (xip.bin, xipport, \out) yet. How to extract xip.bin ??
Then re-build with edits (whole new ball game)
Some ROM chefs (eg. Ervius, swtos, cs) are generous enough to help, I hope, as they have in the past.
ianl8888 said:
I do NOT yet know how to extract the XIP.BIN file for this. I have successfully extracted it from an Eten temp.dat file (nbh equivalent) but not for HTC ROM files.
So I think we need to do steps 7,8,9 (xip.bin, xipport, \out) yet. How to extract xip.bin ??
Then re-build with edits (whole new ball game)
Some ROM chefs (eg. Ervius, swtos, cs) are generous enough to help, I hope, as they have in the past.
Click to expand...
Click to collapse
OK, later edit:
I've figured out how to dump xip.bin
RomMaster.exe OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
But now, when attempting "make pkgs", XIPPort.exe falls over with "could not load file or assembly" errors these tools are so prone to. A path problem (I think) that continually drives me up the wall. We need the "packages" from XIP.BIN to know which files are the OEM drivers etc specific to the Polaris.
So I'm at steps 7, 8 and 8.5 ... it's like pulling teeth
BTW, 00_unknown.nb is the radio file.
ianl8888 said:
I have successfully extracted it from an Eten temp.dat file
Click to expand...
Click to collapse
I already thought I knew your nickname from somewhere .
ianl8888 said:
OK, later edit:
I've figured out how to dump xip.bin
RomMaster.exe OS.nb.payload -w 5 -b 0x00310000 -x -o xip.bin
[The syntax recorded in the how-to page had left out the suffix "payload" ]
So I have a XIP.BIN about 3.3Mb which XIPPort.exe has dumped into \Out\Files & \Out\Modules
Click to expand...
Click to collapse
Seems to be step 8, thank you! If we are sure that this is the right way, I will insert this step8 into the first post.
But where can I find 'RomMaster.exe'? I've only the beta without the command '-b'.
BTW, 00_unknown.nb is the radio file.
Click to expand...
Click to collapse
I already inserted this into #1
I did it the following way and created a new rom without glitches.
Though don't know if it works because I don't dare to flash it
Thanks, I see that you provided a new XIP in packages
20753 in your new thread. So I decided to use this one with your kitchen and I would breakdown the
steps now with which I built my ROM. Could you
please confirm if I have done right?
1. Download and unrar Shayder kitchen with included (3,8MB) os.nb.payload and imgfs.bin (4,0KB)
http://forum.xda-developers.com/showthread.php?t=421444
(Post #8 in the thread)
2. Download and XIP 20753 from the new thread.
http://forum.xda-developers.com/showthread.php?t=427730
3. Put the extracted SYS and OEM folder from
dumped and packaged ROM of you choice into the Build folder
of the Shayder Kitchen.
4. Put the extracted MSXIPKernel and MSXIPKernelLTK
folder from Shayders XIP 20753 into the SYS folder which
was before copied into the Build Folder.
5. Start ROM.bat in the kitchen
6. Select "1 - Build"
7. Select "1+2+3+4+5" in the next screen
8. Select "0" to let it run
9. Click the green button in the Build tool
10. Close Build tool when run ready
11. Wait to finish the nbh and enjoy!
I did so and got the ruu_signed.nbh file
ready to flash... think no need to XIPport etc.
but in fact I don't know exactly as I didn't flash my rom
Olioaglio
Olioaglio said:
I did it the following way and created a new rom without glitches.
Though don't know if it works because I don't dare to flash it
Thanks, I see that you provided a new XIP in packages
20753 in your new thread. So I decided to use this one with your kitchen and I would breakdown the
steps now with which I built my ROM. Could you
please confirm if I have done right?
1. Download and unrar Shayder kitchen with included (3,8MB) os.nb.payload and imgfs.bin (4,0KB)
http://forum.xda-developers.com/showthread.php?t=421444
(Post #8 in the thread)
2. Download and XIP 20753 from the new thread.
http://forum.xda-developers.com/showthread.php?t=427730
3. Put the extracted SYS and OEM folder from
dumped and packaged ROM of you choice into the Build folder
of the Shayder Kitchen.
4. Put the extracted MSXIPKernel and MSXIPKernelLTK
folder from Shayders XIP 20753 into the SYS folder which
was before copied into the Build Folder.
5. Start ROM.bat in the kitchen
6. Select "1 - Build"
7. Select "1+2+3+4+5" in the next screen
8. Select "0" to let it run
9. Click the green button in the Build tool
10. Close Build tool when run ready
11. Wait to finish the nbh and enjoy!
I did so and got the ruu_signed.nbh file
ready to flash... think no need to XIPport etc.
but in fact I don't know exactly as I didn't flash my rom
Olioaglio
Click to expand...
Click to collapse
I also did it this way. You're right, there is a ruu_signed.nbh after all that staff has finished. But the after flashing this ROM image to the orbit it won't boot. The splash screen is shown but nothing else happens.
I think this is caused by the XIP part.
Tom
tomduke99 said:
. But the after flashing this ROM image to the orbit it won't boot. The splash screen is shown but nothing else happens.
I think this is caused by the XIP part.
Tom
Click to expand...
Click to collapse
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Orbitter2 said:
Seems to be step 8, thank you! If we are sure that this is the right way, I will insert this step8 into the first post.
But where can I find 'RomMaster.exe'? I've only the beta without the command '-b'.
Click to expand...
Click to collapse
1) Of course I'm not yet sure that this is the right direction. But I do know that if we want to upgrade the XIP build we have to sort the \OEM and \SYS "packages" from xip.bin. These directories contain OEM drivers specific to the device (here, Polaris)
Still cannot get XIPPort.exe to "make pkgs" although it works with an Eten X500 ROM
2) rommaster.exe is found (from my memory only) in any one of the Polaris or Kaiser kitchen files. It is a very old file, though - Nov 25, 2005. You can also find it in Shayder's kitchen on the front page of this sub-forum
Perhaps there's a later version of a "rommaster.exe" somewhere ?
Olioaglio said:
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Click to expand...
Click to collapse
If you are too unsure to test with flashing (I thought that was what HardSPL was for !!) then try to extract your own RUU_signed.nbh in full and see what you get.
ianl8888 said:
1) Of course I'm not yet sure that this is the right direction. But I do know that if we want to upgrade the XIP build we have to sort the \OEM and \SYS "packages" from xip.bin. These directories contain OEM drivers specific to the device (here, Polaris)
Still cannot get XIPPort.exe to "make pkgs" although it works with an Eten X500 ROM
Click to expand...
Click to collapse
later edit: I have XIPPort.exe "making pkgs" now. XIPPort needs to be in its own folder ( ?? )with the support dll's etc.
So now I'm at Step 9 (the unknown) with \OEM and \SYS "packages" for editing.
The base ROM I'm trying to edit is the recent release of the official HTC WM6.1 Polaris ROM. This ROM is not protected by "all-commands-to-one" etc and so is fully extractable and editable if I can figure out how.
I think the next step (likely 10 or 12 sub-steps in there) is to understand the DSM's, RGU's, HV boot files etc. There is a tool XIPAddrTools available on this sub-forum that I have some hope for in helping here
I am trying to do two things with this ROM:
1) replace the XIP device-independent files with an upgraded set (build 1995 to build 2073)
2) remove all the crap that HTC and other ROM cooks put into it - like Cube, Home, Office etc etc
In other words, I'm trying for a WM6.1, recent XIP build, very clean ROM
Maybe ...
ianl8888 said:
I think the next step (likely 10 or 12 sub-steps in there) is to understand the DSM's, RGU's, HV boot files etc. There is a tool XIPAddrTools available on this sub-forum that I have some hope for in helping here
Click to expand...
Click to collapse
There is a very useful "sticky" thread on some of this, started by udK.
Olioaglio said:
OK, what about the 20743 version as os.nb.payload version
as downloadable in Shayders XIP 20743 thread:
http://forum.xda-developers.com/showthread.php?t=424655
(the rapidshare link). This one does not have to be copied
into the SYS folder, but copied directly into the ROM folder.
I created a rom with this one with Polaris Kitchen 1.3.
Don't know if this would boot (didn't flash it either).
Click to expand...
Click to collapse
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
tomduke99 said:
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
Click to expand...
Click to collapse
My version attached. If someone wants to try...
It's a german light version of O2 3.13.207.0 ROM
without Cube, TTN, Opera, useless stuff.
With XIP 20743 cooked in as os.nb.payload with
Polaris Kitchen V1.3
No radio included. You will most likely have to flash
1.59.42.15 manually after installation of the rom.
Olio v1 GER (Rapidshare link)
Olioaglio
If been testing around with this thread and this one and made a successful rom, some how the xip files needs to be extracted, 3,4 MB is little low, cause the one i got was 3.8 MB.
I used buildos+package_tools-2.7.exe to build my package and htcrt.exe to build the rom. (i change model from KAIS***** to POLA***** to get working and flash able rom)
I will experiment more cause i need to convert raw dump to original rom for warranty
tomduke99 said:
I just tested without any modifications of XIP. I used the original XIP (os.nb.payload, imgfs.bin) delivered within the Kitchen. Only copied the SYS and OEM from the O2 ROM to the kitchen and tried to build a ROM. Result is a non booting ruu_signed.nbh.
Tom
Click to expand...
Click to collapse
Yes, the various Registry addresses change as the XIP build changes so we need to understand RGU's, DSM's etc. The uDk sticky is helpful
Because the kitchens require a "template" to re-build a ROM, I still believe that the most thorough method is to use the just-released WWE WM6.1 HTC ROM as this template. Extract it all, replace the XIP device-independent filesystem with a newer build, remove all the stuff you don't want from \OEM "packages" and re-compile.
This is struggle street maybe, but this jigsaw is a challenge.
I've downloaded a newer version from Shayder's kitchen (found here: http://forum.xda-developers.com/showthread.php?t=427962). There is another os.nb.payload template. With this version of the kitchen I was able to produce a working ruu_signed.nbh with the SYS and OEM folder from the new German O2 ROM. Encouraged by this result I then tried to change the Kernel parts from XIP 20753 and replace NETCF2 with NETCF3.5 - Result: working ROM with NetCF3.5. Many thanks to all guys helping me especially those who have developed Kitchen's, Tools etc.
At this point I have OS version CE OS 5.2.20753 but the Build is still 19965.1.2.3. Therefore the next step should be replacing the SYS parts with its equivalents from a newer Build.
Questions about this:
1. Can I use a SYS folder from another (newer) ROM without modifications?
2. How to build a ROM with German localization? Shall I only copy the language specific folders from the original ROM to the SYS-part of the new ROM?
3. Are there some other stuff? What about Registry settings for different languages?
....
I read so many threads but I'm still not sure what to do next.
Thanks.
Tom
tomduke99 said:
I've downloaded a newer version from Shayder's kitchen (found here: http://forum.xda-developers.com/showthread.php?t=427962). There is another os.nb.payload template. With this version of the kitchen I was able to produce a working ruu_signed.nbh with the SYS and OEM folder from the new German O2 ROM. Encouraged by this result I then tried to change the Kernel parts from XIP 20753 and replace NETCF2 with NETCF3.5 - Result: working ROM with NetCF3.5. Many thanks to all guys helping me especially those who have developed Kitchen's, Tools etc.
Tom
Click to expand...
Click to collapse
Yes, that's real progress.
BUT - list step-by-step exactly how you did it, please
This is the problem - many posts about being successful, very few listing the detail.
Hello FHM and the rest of the board members,
Could you please help me to backup my original ROM? It is a Swisscom version of S740. Maybe I need it later again... or others are interested in.
Regards
Semmelknoedel
Hey,
I have the HTC Rose from Swisscom too, please tell me if you manage to backup the rom and flash the 6.5 rom.
Thanks in advance!!!
Sadly I can't help you with your question as I'm interested in doing it too... sorry...
Dumping ROM From phone .
here is a thread on dumping rom's from a phone http://forum.xda-developers.com/showthread.php?t=616995
and some more (Dumping a rom) http://forum.xda-developers.com/showthread.php?t=334680
good read (the tools you nead) http://www.xs4all.nl/~itsme/projects/xda/tools.html
and to reconstructed the dumped rom http://forum.xda-developers.com/showthread.php?t=337066
please read the thread's , it should work on the rose to .
need a little more help
Hi ceesheim,
Posting the necessary links was very helpful for me. I was able to dump the ROM from my SwissCom S740. Now I have got the 4 RAW files.
I'm following the instruction written by dj13241. Now i faced a problem on step: "rebuild a flashable ROM from a dump" at topic 3 (Insert XIP (Part01.raw) into new-os.nb.payload). As I executed the command for the first time cmd was asking for admin-rights. OK. I have opened cmd as admin. Now I have inserted the command: implantxip Part01.raw new-os.nb.payload
An Error was shown in cmd "xip file not specified". What did I wrong? Please see also the attached snapshot.
Thanks in advance.
Semmelknoedel
First rename part01.raw to xip.bin.
Then the correct command is:
insertxip -xip xip.bin -payload new-os.nb.paylod
Thanks FHM for answering. But it doesn't work. I'm using a insertxip.bat copied from "new_visualkitchen_v_1_8_1_only_exe_+_Tools_folder".
Content of this bat-file:
@echo off
rem echo Processing "%1"
implantxip -xip XIP_new_ported\xip.bin -payload ..\ROM\%1\OS.nb.payload
after execution of the command you mentiond in thread before, I get this error message:
Implantxip & Payload Resizer v. 1.1 by ervius!!!
PAYLOAD: ..\ROM\-xip\OS.nb.payload not found!
XIP not Inserted!
Based on the bat-file I have inserted the folder "XIP_new_ported" and "ROM->-xip".
Where is the mistake I made?
Hi Weezphili,
here are the addresses you need:
Swisscom ROM for the Rose:
3.12M (0x31f000) Part00
3.25M (0x340000) Part01
80.38M (0x5060000) Part02
122.50M (0x7a80000) Part03
Semmelknoedel said:
Thanks FHM for answering. But it doesn't work. I'm using a insertxip.bat copied from "new_visualkitchen_v_1_8_1_only_exe_+_Tools_folder".
Content of this bat-file:
@echo off
rem echo Processing "%1"
implantxip -xip XIP_new_ported\xip.bin -payload ..\ROM\%1\OS.nb.payload
after execution of the command you mentiond in thread before, I get this error message:
Implantxip & Payload Resizer v. 1.1 by ervius!!!
PAYLOAD: ..\ROM\-xip\OS.nb.payload not found!
XIP not Inserted!
Based on the bat-file I have inserted the folder "XIP_new_ported" and "ROM->-xip".
Where is the mistake I made?
Click to expand...
Click to collapse
did you do this ?
"Extract XIP (Part00 and Part01 ... You will need bepe's dumpxip.exe from ervius visual kitchen):
1) Make sure there is not an XIP folder (if so, rename it) and run dumpxip Part00.raw
2) Rename XIP folder to XIP_00 (ren XIP XIP_00)
3) Make sure there is not an XIP folder (if so, rename it) and run dumpxip Part01.raw
4) Rename XIP folder to XIP_01 (ren XIP XIP_01)"
You don't need to dump the part01.raw. It's the XIP, all you need to is to rename it to xip.bin!
Put the xip.bin and the os.nb.payload (or whatever the name is you have) in the same folder as implantxip.exe!
Open an elevated CMD (Windows key + R then type in cmd) switch to the folder with the exe, bin and payload file with:
cd C:\yourfolder
then type in what I wrote above! Done
frauhottelmann said:
You don't need to dump the part01.raw. It's the XIP, all you need to is to rename it to xip.bin!
Put the xip.bin and the os.nb.payload (or whatever the name is you have) in the same folder as implantxip.exe!
Open an elevated CMD (Windows key + R then type in cmd) switch to the folder with the exe, bin and payload file with:
cd C:\yourfolder
then type in what I wrote above! Done
Click to expand...
Click to collapse
This is done, but another question: you command is "insertxip -xip xip.bin -payload new-os.nb.paylod" but there are xip.bin and the os.nb.payload and implantxip.exe and insertxip.bat in that folder. After execution of your command the same error like before:
Implantxip & Payload Resizer v. 1.1 by ervius!!!
XIP: XIP_new_ported\xip.bin not found!
XIP not Inserted!
E:\Test>
mmh... strange!
Don't use the bat any more. Just use my command, it's the same thing, it just works
Otherwise upload the the files (raws) and I'll do it for you!
frauhottelmann said:
Don't use the bat any more. Just use my command, it's the same thing, it just works
Otherwise upload the the files (raws) and I'll do it for you!
Click to expand...
Click to collapse
You are right, the problem is the bat-file. But I couldn't find a insertxip.exe
Do you have one for me?
Uuuuups did I wrote insertxip?? My bad. I meant implantxip
Sorry
frauhottelmann said:
Uuuuups did I wrote insertxip?? My bad. I meant implantxip
Sorry
Click to expand...
Click to collapse
And also at the end of the command insertxip -xip xip.bin -payload new-os.nb.paylod -> the "a" is missing
Now it works with this command:
implantxip -xip xip.bin -payload os.nb.payload
Thanks for your help. I'm going to go the next steps...
Problems with final steps
As described in dj13241's thread the final steps are:
- Merge os-new.nb.payload into os-new.nb (nbmerge -kaiser os-new.nb)
- Create os-new.nbh nbhutil, Select "Touch_Pro2" under "Target Device", change RHOD*** to RHOD500, click the ... box next to OS, and select new-os.nb, click Build NBH and select where to save NBH file.
... I don't want build a ROM for Touch Pro 2 What do I have to select in the dropdown list or shall I use FHM's Vox Rose Kitchen 2.0?
Thanks for you help.
Yes, lol my fault again. That happens when I use my laptop keyboard, I mistype a lot...
Get the TOOLs part of my kitchen then in the tools folder open the HTC ROM Tool (htcrt.exe) choose the Diamond and change DIAM***** to ROSE1000 under OS select your os-new.nb and click on build to make a nbh that you can flash.
EDIT: nbmerge -kaiser os-new.nb is the right step
frauhottelmann said:
Get the TOOLs part of my kitchen then in the tools folder open the HTC ROM Tool (htcrt.exe) choose the Diamond and change DIAM***** to ROSE1000 under OS select your os-new.nb and click on build to make a nbh that you can flash.
EDIT: nbmerge -kaiser os-new.nb is the right step
Click to expand...
Click to collapse
But there is no os-new.nb. If you read the dj13241's thread and you are looking for os-new.nb you only find it at the end of his instruction. So I guess that it is the os.nb i have extracted with command nbhextract RUU_Signed.nbh
By the way: the RUU_Signed.nbh I use is from Blackstone.. is this ok or not?
HTC ROM Tool (htcrt.exe)
FHM, what can you tell me about the SPL, Splash and Radio contents? Will this not be part of my original ROM I try to build? I think a Radio is necessary, do I also have to dump it from Rose?
...a lot of work. Thank god it's holiday...
you made only the rom ( no spl , radio , splash ) .
if you flash your new build rom you keep your old splash and your old radio (they are still on the phone ).
no need to dump them .
only when you flash a new radio or splash you could dump the old first .