Cook a rom for Vox (pb : initflashfiles.dat) - Upgrading, Modifying and Unlocking

Hi,
I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).
I would understand all steps of cooking, i have already made this :
1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)
2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)
3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe
4 - Move dump files in OEM/SYS folders with PKGTool
If i understood well, i must extract XIP from Windows.nb, before cook.
I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?
Thanks.
And sorry for my poor english.

fireburned said:
Hi,
I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).
I would understand all steps of cooking, i have already made this :
1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)
2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)
3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe
4 - Move dump files in OEM/SYS folders with PKGTool
If i understood well, i must extract XIP from Windows.nb, before cook.
I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?
Thanks.
And sorry for my poor english.
Click to expand...
Click to collapse
have u try msflshtool

Thanks for this idea.
I test it, with this command :
msflshtool.exe Windows.nb -d
I obtain 3 files :
- Windows.nb.part0
- Windows.nb.part1
- Windows.nb.part2
Here is the part info :
Code:
***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end
What is the newt step ?
Thanks you.

fireburned said:
Thanks for this idea.
I test it, with this command :
msflshtool.exe Windows.nb -d
I obtain 3 files :
- Windows.nb.part0
- Windows.nb.part1
- Windows.nb.part2
Here is the part info :
Code:
***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end
What is the newt step ?
Thanks you.
Click to expand...
Click to collapse
usually it is in part0 or part1 ... use xipport to see which have the boot.hv & boot.rgu ... u only need those files ... around 20-40Kb files
Then u can put it in ROM folder in ur Kitchen

Thank you cruzzmz for your replies
I used XIPort to extract Windows.nb.part0/Windows.nb.part1.
I obtain this :
Code:
Windows.nb.part0
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
boot.hv
boot.hv.imageinfo.txt
ceconfig.h
ceconfig.h.imageinfo.txt
default.hv
default.hv.imageinfo.txt
initobj.dat
initobj.dat.imageinfo.txt
user.hv
user.hv.imageinfo.txt
\MODULES
busenum.dll
cecompr.dll
ceddk.dll
cereg.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
imgfs.dll
mmtimer.dll
mspart.dll
nk.exe
OMAP850_SDHC.dll
ONDisk.dll
packageinfoapi.dll
pm.dll
ramdisk.dll
rawfs.dll
regenum.dll
romfilter.dll
sdbus.dll
sdmemory.dll
serial.dll
uldrui.dll
updateapp.exe
busenum.dll.txt
cecompr.dll.txt
ceddk.dll.txt
cereg.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
imgfs.dll.txt
mmtimer.dll.txt
mspart.dll.txt
nk.exe.txt
OMAP850_SDHC.dll.txt
ONDisk.dll.txt
packageinfoapi.dll.txt
pm.dll.txt
ramdisk.dll.txt
rawfs.dll.txt
regenum.dll.txt
romfilter.dll.txt
sdbus.dll.txt
sdmemory.dll.txt
serial.dll.txt
uldrui.dll.txt
updateapp.exe.txt
Windows.nb.part1
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm.imageinfo.txt
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm.imageinfo.txt
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu.imageinfo.txt
boot.hv
boot.hv.imageinfo.txt
boot.rgu
boot.rgu.imageinfo.txt
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm.imageinfo.txt
initflashfiles.dat
initflashfiles.dat.imageinfo.txt
mxip_initdb.vol
mxip_initdb.vol.imageinfo.txt
mxip_lang.vol
mxip_lang.vol.imageinfo.txt
wince.nls
wince.nls.imageinfo.txt
\MODULES
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
busenum.dll.txt
cachefilt.dll.txt
cecompr.dll.txt
ceddk.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
fsreplxfilt.dll.txt
hd.dll.txt
HtcFsdspy.dll.txt
imgfs.dll.txt
mspart.dll.txt
nk.exe.txt
ONDisk.dll.txt
osaxst0.dll.txt
pm.dll.txt
ps2fatutil.dll.txt
regenum.dll.txt
The good files are in Windows.nb.part1 ?
Next step : copy boot.hv/boot.rgu in ROM/XIP folder ?
Thank you very much !

And another question, i have "missing files" when i use PKGTool :
Code:
[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
It's a problem ?

fireburned said:
And another question, i have "missing files" when i use PKGTool :
Code:
[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
It's a problem ?
Click to expand...
Click to collapse
dont think it is a problem as long as when u do buildOS u dont get any error (hint: if there is error check the temp folder open log.txt)

I created a *.bat file wich does this :
1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"
2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :
Code:
boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)
3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS
4- move Temp\Imgfs\OEM and SYS in root kitchen directory
My problem :
* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."
I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?
Thanks you.

Help me please... I tried... But i'm blocked...

fireburned said:
I created a *.bat file wich does this :
1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"
2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :
Code:
boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)
3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS
4- move Temp\Imgfs\OEM and SYS in root kitchen directory
My problem :
* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."
I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?
Thanks you.
Click to expand...
Click to collapse
I dont seem to hv that file on my ROM\XIP folder, maybe u can try deleting all files inside XIP except for boot.hv & boot.rgu
then try buildOS again
BTW what is the size of both files?

I deleted all files in XIP folder, except boot.hv/boot.rgu
boot.hv = 40 Ko
boot.rgu = 27 Ko
Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."
When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.
An idea ?

fireburned said:
I deleted all files in XIP folder, except boot.hv/boot.rgu
boot.hv = 40 Ko
boot.rgu = 27 Ko
Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."
When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.
An idea ?
Click to expand...
Click to collapse
dunno if this can help
If you did something like the following sequence:
typho5 -x nk.nbf
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
Then the initflashfiles.dat should definitely be in the 'dump' folder.
Did you remember the -nosplit option for prepare_imgfs.exe?
Edit: Just a thought. The initflashfiles.dat is hidden plus the .dat extension is normally used by system files, so could it be something so simple as the fact that your explorer is not showing hidden and/or system files?
Click to expand...
Click to collapse
seems like the initflashfiles.dat is in the dump folder after u do a viewimgfs

You can put initflashfile.dat inside imgfs (for example OEM/OEM_LANG_XXX) and delete it from XIP.
Buildos.exe from Bepe search initflashfiles.dat insiede IMGFS:

cruzzmz : I tried your solution
Code:
typho5 -x nk.nbf
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
But, in dump folder, i haven't initflashfiles.dat
I tested several solutions, and each time, initflashfiles.dat is in my XIP folder.
cicciocant : I tried to put initflashfiles.dat in dump folder, and run PKGTool, but file is not copy to OEM_Lang_XXXX folder (missing dsm ???), and BuildOS fails, with same error.
I tested to put initflashfiles.dat in OEM_Lang_XXXX manualy, and i have an other error when i try to BuildOS : "initflashfiles.dat is a directory not a file! copying the File!!!"
In my XIP folder, i have :
Code:
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
boot.hv
boot.rgu
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
initflashfiles.dat
mxip_initdb.vol
mxip_lang.vol
wince.nls
An idea ?
And thanks for your help.

seems like my rom that i cooked doesnt have initflashfiles.dat in the XIP folder.
Maybe you can try ask around in hypercore kitchen thread

Thanks cruzzmz, i posted my question.

Related

a problem with dumprom and HTC (Windows Mobile 6 Extract)

HI
i downloaded WM6CB and extract it now i have 2 nbf file
nk.nbf 64MB Size
ms.nbf 10MB Size (Empty_Extended_rom)
i want to extract these
I tested dumprom.exe and HTC64 Extended ROM Tool.exe but i can't extract these
if i use dumprom then i can't extract it when i use HTC64 and i use dumprom with nk.fat file argument then i can extract some files and get this error
Code:
9073265c - 907338b6 L0000125a o32 region_2 rva=00042000 vsize=000027f0 real=01f9
2000 psize=0000125a f=40002040 for coredll.dll
907338b8 - 907351b9 L00001901 filedata boot.hv
907351bc - 907380a4 L00002ee8 filedata default.hv
907380a4 - 907380a4 L00000000 rom_00 end
907380a4 - 9443fc00 unknown
i used this arguments
For NBF File
dumprom nk.nbf -d mydirectory\
dumprom -5 nk.nbf -d mydirectory\
For FAT File
dumprom -5 nk.fat -d mydirectory\
dumprom nk.fat -d mydirectory\
And I can't Extract Empty Rom with this way
I want to extract windows mobile 6
Please help me for further information
Thanks
Regards

Uni Rom kitchen problem

after I've edit the rom of Wm6 , it'll auto off at slashscreen after flash
please correct me if anything wrong ..
here's my steps :
HTC64 Extended ROM Tool , decode the rom and then...
prepare_imgfs.exe nk.fat -nosplit
viewimgfs imgfs_raw_data.bin
BuildImgfs
set _FLATRELEASEDIR=.
rgucomp -o dump\default.hv -nologo > default.rgu
rgucomp -o dump\user.hv -nologo > user.hv
then I've added other wince.nls and fonts in "dump" directory .
and edit default.rgu , user.hv by ultraedit . added "REGEDIT4" at the first line , added some lines on initflashfiles.dat.
then repack :
copy default.rgu boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
attrib -s -r -h dump\default.hv
copy boot.hv dump\default.hv
attrib -s -r -h dump\user.hv
copy user.hv dump\user.hv
BuildImgfs
make_imgfs nk.fat -nosplit
use HTC64 Extended ROM Tool encode again . and flash .
any problems in these step ? Please correct me , Thanks alot !!
Building roms
Hi,
Ha... here you are,
will try this tomorrow.
Leo
Leies said:
after I've edit the rom of Wm6 , it'll auto off at slashscreen after flash
please correct me if anything wrong ..
here's my steps :
HTC64 Extended ROM Tool , decode the rom and then...
prepare_imgfs.exe nk.fat -nosplit
viewimgfs imgfs_raw_data.bin
BuildImgfs
set _FLATRELEASEDIR=.
rgucomp -o dump\default.hv -nologo > default.rgu
rgucomp -o dump\user.hv -nologo > user.hv
then I've added other wince.nls and fonts in "dump" directory .
and edit default.rgu , user.hv by ultraedit . added "REGEDIT4" at the first line , added some lines on initflashfiles.dat.
then repack :
copy default.rgu boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
attrib -s -r -h dump\default.hv
copy boot.hv dump\default.hv
attrib -s -r -h dump\user.hv
copy user.hv dump\user.hv
BuildImgfs
make_imgfs nk.fat -nosplit
use HTC64 Extended ROM Tool encode again . and flash .
any problems in these step ? Please correct me , Thanks alot !!
Click to expand...
Click to collapse

Is there som cookers here?

In the past I cooked some ROM for my old device Trinity P3600 like this:
http://forum.xda-developers.com/showthread.php?t=367317
Now I want to buy an excalibur and i want to try to cook a ROM for this device.
is there any body with wich I can exchange ideas and experiences?
for examples. How can I extract the XIP in this device?
There is already some cooked rom for this device?
I'm tryng to port the last Vox ROM (ake 0.4.4) in the excalibur.
Some cookers come here?
Ok.
I discovered something
For extract IMGFS:
With NBHTool extract Windows.nb afther with Tadzio tool:
Code:
rename windows.nb os.nb
copy Os.nb Os.nb.payload
ImgfsFromNb os.nb.payload imgfs.bin
ImgfsToDump imgfs.bin
For extract XIP:
Code:
RomMaster os.nb -v 0 -w 5 -b 0x00217800 -x -o xip.bin
mk xip
dumprom xip.bin -5 -d XIP >NUL
Someone interested?

(UPDATED 14/04) Hermes Kitchen Build 19209

Came from official htc kaiser, based from pdacorner.v9 and tools from bepe (thanks for him)
OS 5.2.19209 Build 19209.1.0.2
Not included:
- OEMApps
- OEMOperators
You need Microsoft Visual C++ 2008 Redistributable Package to using this kitchen
Updated:
- Added os.nb.payload
- Added initflashfiles.dat
Download PART1
Download PART2
Donations are welcome
Finally, A Kitchen on 19209.
Really thanks abusalza for your enormous Gift
Pouvez-vous poster un autre lien de telechargement svp, je n'arrive pas a telechargder depuis megaupload.
merci!
An other link please, i can't download from megaupload.
Thanks!
Good show sir, id highly recommend everybody making thier own ROMs based on thier own needs. Freedom of choice is always best.
Awesome brother!!!
This 19209 is the best wm6.1 build...thanks!
Quick query for people....anybody getting unhandled exceptions in buildOS?
aswell as buildxip errors?
mrvanx said:
Quick query for people....anybody getting unhandled exceptions in buildOS?
aswell as buildxip errors?
Click to expand...
Click to collapse
yup.......
mrvanx said:
Quick query for people....anybody getting unhandled exceptions in buildOS?
aswell as buildxip errors?
Click to expand...
Click to collapse
yap, i get errors too
same here..
Ive narrowed it down to the OEM folder, however im not sure what the exact issue is. Ive just replaced the OEM stuff with my own from "V10 Roller". Remember to add os.nb.payload into theROM folder or you will get an error when the insert program is run.
Also getting exceptions, tried replacing the OEM folder with a known good one but it's still happening. Any suggestions?
caeci11ius said:
Also getting exceptions, tried replacing the OEM folder with a known good one but it's still happening. Any suggestions?
Click to expand...
Click to collapse
Well, I think I solved this problem.
mrvanx said:
Ive narrowed it down to the OEM folder, however im not sure what the exact issue is. Ive just replaced the OEM stuff with my own from "V10 Roller". Remember to add os.nb.payload into theROM folder or you will get an error when the insert program is run.
Click to expand...
Click to collapse
Thanks to mrvanx's hint, I compared each OEM directories with my old kitchen tools. Then I found some stuff is missing in 'OEM\OEM_Lang_0409' directory.
So I copied my old stuff into it, then Error was gone.
Edit:
Well, I found what the problem is. the 'initflashfiles.dat' is missing in 'OEM\OEM_Lang_0409' directory. If there is 'initflashfiles.dat' even if it is 0 bytes, then this problem is solved.
I dont want to sound dumb here, but where can i get the os.nb.payload file?
curveconcepts said:
I dont want to sound dumb here, but where can i get the os.nb.payload file?
Click to expand...
Click to collapse
Not a stupid question at all....
..download a known working rom based on 19209 (theres a few around)....to get os.nb.payload from it do these following things:
(using the programs in the TOOLS folder in this kitchen)
get the os.nb from the RUU_Signed.nbh file using nbhtool (in TOOLS/HTOOLS)
split the os.nb file into os.nb.payload and os.nb.extra using:
"nbsplit -hermes os.nb" on the command line. (the nbsplit.exe must be in the same dir as os.nb before you do it).
DONE.....slap os.nb.payload into the ROM folder when uve done it.
i've tried to updated my kitchen. fiuh... very hard work. my connection was bad. God help me
Help!
Hello!
Give me please - very confused: (
Downloading kitchen, treasure initflashfiles.dat in OEM_Lang_0409, taking the OS.NP.PAYLOAD from PDACorner V9, run BuildNB.bat
BuildOS compiles all successfully, but further writes:
ImgfsFromNb 2.1RC1
Sector size is 0x200 bytes
ImgFs partition starts at 0x00620000 and ends at 0x04080000
No IMGFS signature found. Exiting.
ImgfsFromDump 2.1rc2
Input file imgfs.bin cannot be opened. Exiting.
ImgfsToNb 2.1RC1
Using bigstoragemove mode
Input file imgfs-new.bin cannot be opened. Exiting.
NBMerge 2.1RC1
Could not open input file OS-new.nb.payload
What am I doing wrong? Give please!
Yet more problems. There seems to be issues with some of the programs in the kitchen. By replacing BuildOS with another version I had around I managed to get it to run and not throw exceptions (tried the other posted solutions but had no luck with them) but it seems another program is giving me issues now. Logs:
Creating 'dump' folder...
Done!
BUILDXIP 0.54 Copyright (c) 2007-2008 bepe 30 Jan 2008
Slot 0 Boundary: 0x01fa0000
Slot 1 Boundary: 0x03e33000
RAMStart: 0x802ac000
RAMFree: 0x802e6000 - 0x83a00000 L0371a000
KernelFlags: 0x00000000
FSRamPercent: 0x00000020
Done!
Copying OS.nb.payload...
1 file(s) copied.
The system cannot execute the specified program.
Could Not Find J:\kitchen\buildpkg.wrn
The system cannot execute the specified program.
ERROR! (errorlevel: 9020)
Press any key to continue . . .
Looking at the batch files, this would indicate me that "all_packages_to_one" and "insert" are having problems (these are the lines where "cannot execute" appears). I thought it might have been a problem with 7zip, which I used to extract the archive but WinRAR has the same issue. No idea what's going on here, it's a very odd problem...
baxxik said:
Hello!
Give me please - very confused: (
Downloading kitchen, treasure initflashfiles.dat in OEM_Lang_0409, taking the OS.NP.PAYLOAD from PDACorner V9, run BuildNB.bat
BuildOS compiles all successfully, but further writes:
ImgfsFromNb 2.1RC1
Sector size is 0x200 bytes
ImgFs partition starts at 0x00620000 and ends at 0x04080000
No IMGFS signature found. Exiting.
ImgfsFromDump 2.1rc2
Input file imgfs.bin cannot be opened. Exiting.
ImgfsToNb 2.1RC1
Using bigstoragemove mode
Input file imgfs-new.bin cannot be opened. Exiting.
NBMerge 2.1RC1
Could not open input file OS-new.nb.payload
What am I doing wrong? Give please!
Click to expand...
Click to collapse
Try a different os.nb.payload fromanother ROM. The one bundled with pandora beta 9 works fine.
caeci11ius said:
Yet more problems. There seems to be issues with some of the programs in the kitchen. By replacing BuildOS with another version I had around I managed to get it to run and not throw exceptions (tried the other posted solutions but had no luck with them) but it seems another program is giving me issues now. Logs:
Creating 'dump' folder...
Done!
BUILDXIP 0.54 Copyright (c) 2007-2008 bepe 30 Jan 2008
Slot 0 Boundary: 0x01fa0000
Slot 1 Boundary: 0x03e33000
RAMStart: 0x802ac000
RAMFree: 0x802e6000 - 0x83a00000 L0371a000
KernelFlags: 0x00000000
FSRamPercent: 0x00000020
Done!
Copying OS.nb.payload...
1 file(s) copied.
The system cannot execute the specified program.
Could Not Find J:\kitchen\buildpkg.wrn
The system cannot execute the specified program.
ERROR! (errorlevel: 9020)
Press any key to continue . . .
Looking at the batch files, this would indicate me that "all_packages_to_one" and "insert" are having problems (these are the lines where "cannot execute" appears). I thought it might have been a problem with 7zip, which I used to extract the archive but WinRAR has the same issue. No idea what's going on here, it's a very odd problem...
Click to expand...
Click to collapse
You can use Microsoft Visual C++ 2008 Redistributable Package.I had the same error end it solved it.

NBH to BIN

People. How to convert a rom on NBH format do BIN (to use with MS DEVICE EMULATOR)
Thank you.
Me Too!
Me too!
I searched more than a hour but i did not find anything!
marcello.mezzanotti said:
People. How to convert a rom on NBH format do BIN (to use with MS DEVICE EMULATOR)
Thank you.
Click to expand...
Click to collapse
If you want to dump a rom:
NBHextract (name of file).nbh
NBSplit -kaiser OS.nb
ImgfsFromNb OS.nb.payload imgfs.bin
ImgfsToDump imgfs.bin
If you want to dump an Artemis rom:
NBHExtract (name of file).nbh
ImgfsFromNb OS.nb imgfs.bin
ImgfsToDump imgfs.bin
and OK !!!
In MS Emulators only one bin file for device and other rezolution
http://img27.imageshack.us/img27/2963/50995977.jpg
And questions how to get bin file from nbh to run with Emulator?

Categories

Resources