Database Users

Cooking rom from a .bin RomFile

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'' !!

HOWTO Rebuild own ROM with kitchen?

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.

My Kitchen

My Kitchen:
http://rapidshare.com/files/146609696/kitchen.rar.html

Hi SHAYDER,
thanks for this great kitchen
now we need an good documentation (like this thread)
and an example rom for extract, change and rebuild...
-bl4ckb1rd

bl4ckb1rd said:
Hi SHAYDER,
thanks for this great kitchen
now we need an good documentation (like this thread)
and an example rom for extract, change and rebuild...
-bl4ckb1rd
Click to expand...
Click to collapse
He already did...
My imgfs.bin and os.nb.payload needed to replace any XIP on any ROM.(It is templates)
My Kitchen.
http://rapidshare.com/files/140893825/Kichen.zip.html
To build ROM:
1) Put "OEM" and "SYS" folders to "Build" folder. (dont delete any existing files)
2) Run Rom.bat Then put "1" then "8" then "0"
3) When running "BuildOS" Put 'Play' button.
To Extract ROM:
1) Put "RUU_Signed.nbh" to "Extract" Folder
2) Run Rom.bat Then put "2"
3) When running "Package Tool", File->Open and put way "...\Extract\dump"
Click to expand...
Click to collapse

[HOWTO] Completely restore your device to its original condition (warranty coverage)

FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!​
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Code:
00_GSM.nb
01_IPL.nb
02_SPL.nb
03_MainSplash.bmp
03_MainSplash.nb
04_OS.nb
Copy 02_SPL.nb and 03_MainSplash.nb to C:\HTCRomTool and 04_OS.nb to C:\XIPPORT
ok, now we have official SPL and MainSplash ready to use but we need the OS too
To obtain exactly the original OS we need to modify some registry keys inside "boot.hv" according to our language.
This file is located in the XIP section, so we should extract the xip files from 04_OS.nb, modify boot.hv and re-inject the xip in the os.
Don't worry, we have another solution because we already have the original xip obtained from dump process ([email protected]'s wiki)
The XIP section is Part01.raw
Copy Part01.raw to C:\XIPPORT and rename it to "xip_out.bin"
Run xipport.exe, change the offset to "00313800", the filename to "04_OS.nb" (see pic01 at the end of post for detail) and press "write xip_out.bin to:"
This tool write the xip section (xip_out.bin) in the OS (04_OS.nb) at the specified address (00313800).
Now we have 04_OS.nb with our original XIP
Rename 04_OS.nb to OS.nb and copy it to C:\tadzio
Copy imgfs_raw_data.bin obtained from dump process to C:\tadzio
Open a command prompt, go in C:\tadzio and type this command:
Code:
C:\tadzio>imgfstonb imgfs_raw_data.bin os.nb os-new.nb -bigstoragemove
This tool recostructs the OS (os-new.nb) from our dumped image (imgfs_raw_data.bin)
Now we need to patch the size of OS-new.nb, to do this type this command:
Code:
C:\tadzio>bPatch.exe -1 0xFF 0x632D000 OS-new.nb
The size of patched file must be 99.1 MB (103,993,344 bytes)
Ok, our OS is ready to use!
Copy OS-new.nb to C:\HTCRomTool and run "htcrt.exe"
This tool creates and signes a .nbh file from a .nb file. I suggest you to create 2 .nbh, one for OS and Spalsh (eg. OS.nbh)
and one for SPL (eg. SPL.nbh).
Select "ROM builder" tab and fill the fields like screenshots at the end of post:
OS.nbh (see pic02 for detail)
SPL.nbh (see pic03 for detail)
Press "Build!", type the filename without extension and press "Save"
Flash OS.nbh first so if something wrong in the image and the device don't boot you'll be able to flash any other ROM; while, if it boots ok, then flash the SPL.nbh.
Copy OS.nbh to C:\RomUpdate, rename it to ruu_signed.nbh, run "ROMUpdateUtility.exe" and follow the instructions
At this point we have flashed OS and Splash, if its all ok and the device boot right, then you can flash SPL
Delete ruu_signed.nbh, copy SPL.nbh to C:\RomUpdate, rename it to ruu_signed.nbh and run "ROMUpdateUtility.exe"
That's all!! Now you have completely restored your device to its original condition.
I've tested this procedure, worked fine for me and i hope for you too
.
.
.
bye all
.
.
.

isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....

avathar behemoth said:
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
Click to expand...
Click to collapse
i've tried to play around this few time ago with no succes
I've configured wifi interface card throw registry hack, it appears in the network adapter list, but when i turn on wifi nothing happens...

did you use the files i posted in the wifi thread? (posted the tnetw 1251 driver and a file from the extended rom of the artemis... wifinit.exe) but kudos to you for getting a device listed in the pharos (though i looked with task manager i think in a previous rom i flashed and i saw wifi.dll or something loaded at the list of pharos devices)

poldo964 said:
FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!​
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Click to expand...
Click to collapse
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.

wittanny said:
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
Click to expand...
Click to collapse
oops! sorry

hi
i have not imgfs_raw_data.bin ????

when i run the romupdateutility i get error "invalid vendor id"
please help

lindows said:
when i run the romupdateutility i get error "invalid vendor id"
please help
Click to expand...
Click to collapse
you need HardSPL to flash a NON official ROM

well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?

fmulinacci said:
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
Click to expand...
Click to collapse
are you italian?

poldo964 said:
are you italian?
Click to expand...
Click to collapse
yes, why? do I write english so bad ?
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers

fmulinacci said:
yes, why? do I write english so bad ?
Click to expand...
Click to collapse
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
Click to expand...
Click to collapse
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu

poldo964 said:
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
Click to expand...
Click to collapse
ok, I got it....however my Pharos was French (a great deal, about 150€ at FNAC in Geneva...I could not let it on the shelf), and I did not back it up before upgrading....let us hope in 1 year nothing bad will happen ;-)

Hi all,
I'm looking for the official french version. Could anyone share it or tell me where i could DL it?
Thanks all.

[Q] Convert .NBH to .BIN

i know this has been asked many times over...
but my searching has failed in successfully giving me an answer.
in my searching i have found these programs...
BinTools
ImgfsTools 2.1rc2
NBHextract
nbImageTool-ver-point-four
xidump_v1.0_beta
i was successfully able to convert the .nbh to a .nb
but cant seem to convert the .nb to a .bin
BinTools. requires the 'offset' and 'partbytes' to convert .nb to .bin. i couldnt find what those were for the Rhodium.
ImgfsTools. will create a imgfs.bin but it is empty, 0 KB.
NBHextract. will successfully create a .nb from a .nbh.
nbImageTool. i cant seem to get to work. just gives me 'error 5'.
xidump. will dump the .nbh. but not into a .bin.
so. my question.
how can i successfully convert a .nbh to a .bin for use with WM 6.5 Pro Emulator?
looking to use emulator for custom Rhodium roms.
thanks.
sh4d0w86.

You need a CMD window and a map with Bepe tools.
Put the following files in the map and browse with the CMD Window to that location.
nbsplit.exe
ImgfsFromNb.exe
Plus the os.nb
In the CMD window you give the following commands.
nbsplit -kaiser os.nb os.nb.payload
imgfsfromnb os.nb.payload imgfs.bin
Hope this helps

Laurentius26 said:
You need a CMD window and a map with Bepe tools.
Put the following files in the map and browse with the CMD Window to that location.
nbsplit.exe
ImgfsFromNb.exe
Plus the os.nb
In the CMD window you give the following commands.
nbsplit -kaiser os.nb os.nb.payload
imgfsfromnb os.nb.payload imgfs.bin
Hope this helps
Click to expand...
Click to collapse
thank you. that did indeed work.
hadnt been typing '-kaiser'.
unfortunately. though.
the WinMo 6.5 Emulator doesnt recognize the file as a .bin.
dang.
any ideas?
and thanks again.
sh4d0w86.

sh4d0w86 said:
thank you. that did indeed work.
hadnt been typing '-kaiser'.
unfortunately. though.
the WinMo 6.5 Emulator doesnt recognize the file as a .bin.
dang.
any ideas?
and thanks again.
sh4d0w86.
Click to expand...
Click to collapse
emulator bin is not the same as the imgfs.bin....

ai6908 said:
emulator bin is not the same as the imgfs.bin....
Click to expand...
Click to collapse
is there a tool to create an emulator bin?
sh4d0w86.

sh4d0w86 said:
is there a tool to create an emulator bin?
sh4d0w86.
Click to expand...
Click to collapse
Hi sh4d0w86
Have a look here. You should follow the 1st link there and read through the entire thread.
Regards!

I have tried many times, but not.Encountered the same problem.

kokotas said:
Hi sh4d0w86
Have a look here. You should follow the 1st link there and read through the entire thread.
Regards!
Click to expand...
Click to collapse
awesome. thank you. i will look into it.
sh4d0w86.