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
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.
Hi there,
Here is a command line tool that can extract and rebuild a flash.bin file for the LG KS20.
First, the options available :
Code:
LGFlashMuncher.exe [options] path [output]
EXTRACT Options ---(at least one option required)-----------------------------
-r : extract Raw data
-h : extract header
-m : extract MBR
-p : extract partitions
-t : trim extracted partitions
-l : output layout informations to file 'flash.xml'
-o : output OS.nb compatible file
output : path to output directory (must exists)
CREATE Options ---(all options required)-------------------------------------
-c file : create new flash.bin outputed to 'file'
(MBR and fat partition are taken from original flash.bin)
-e file : use 'file' for header
-0 file : use 'file' for partition 0 (boot)
-1 file : use 'file' for partition 1 (rawfs)
-2 file : use 'file' for partition 2 (imgfs)
COMMON Option ---------------------------------------------------------------
path : path to flash.bin file
Next, how to extract data from a flash.bin to a directory named output :
Code:
LGFlashMuncher.exe -htmlp FLASH.bin output
How to rebuild a new flash.bin :
Code:
LGFlashMuncher.exe -c newflash.bin -e header.bin -0 part_0_BOOT.bin -1 part_1_RAWFS.bin -2 part_2_IMGFS.bin FLASH.bin
(This rebuild process requires an existing flash.bin file)
At the moment, this tool use the partition layout and the empty fat32 (last partition) found in the original flash.bin file. The next step will be rebuild the partition layout.
I've made some test with this tool, but I cannot be sure it will work in all situations. Spocky had a preview of this tool a couple of days ago, and he successfully built a french 10G and a french 10A : I'm sure he will soon share his knowledge...
Very Nice job !
Thank.
Très bon travail MisterJP.
Merci.
Does this mean we can flash the files we extract with pdocread? (part00.raw, etc)
I think that for the moment only part02.raw
@+
dorik2k said:
Does this mean we can flash the files we extract with pdocread? (part00.raw, etc)
Click to expand...
Click to collapse
If the generated files are image of your phone partitions, then I guess it's possible if you respect the partitions order.
Hi, misterjp
In your LGFlashMuncher.exe there is an option:
-o : output OS.nb compatible file
I am just wondering is it FLASH.bin to OS.nb?
And is there any way to convert OS.nb back to FLASH.bin?
The reason that i want to do that is because in that case, i can convert a OS.nb which hv a larger partition table to Flash.bin for cooking
Thx in advance
Hi raykisi,
Sorry, but this tool is not able at this time to re-build an Flash.bin from an OS.nb file. It was just a test option while I was testing my code.
I'm planning on updating this tool, but it takes time and I don't have many these days.
JP.
o...gd to hear that you are going to update this tool, we would wait, take you time. And thx for your great work
Hey, sorry about the question.. i know i'm such a noob, but i'm brazilian and my "english understanding" is kind of weak sometimes.. So...
Is there any way to extract the Flash.bin and others of my current ROM? I mean, the actual ROM of my phone?
I'm asking this because here in Brazil we have the MS25/MS20.. A kind of KS20 without 3G, wifi, and front camera devices.. but same processor and same everithing else.. so, I think LG BRASIL will not provide the roms so early, but the v10a are full of bugs! Also i can`t flash with a KS20 rom, because that missing devices and because my operator phone frequency is 850 MHz (VIVO).
well, someone have an idea? Or a link? Or a read recomendation?
Brazilian people are really needing help with this, and we are getting tired to search with no answers..
Thank`s a lot!
Hi,
I am trying to extract image from a WM6.1 ROM emulator and from a tutorial I can see the following emu option :
NBsplit -emu PPC_USA.BIN
I dont' understand because I only have the following ones when launching NBSplit :
NBSplit 2.1rc2
Wrong or missing parameters.
Usage: NBSplit.exe -hermes|-kaiser|-titan|-acer|-wizard|-athena|-sp
|-data <number> -extra <number> <filename.nb>
Generates <filename.nb.payload> and <filename.nb.extra> from <filename.nb>
<filename.nb> will NOT get overwritten.
There is no -emu, so I tried with a -SP and now I get PPC_USA.BIN.extra and PPC_USA.BIN.payload but then when I try this
ImgfsFromNb.exe PPC_USA.BIN.payload IMGFS.BIN
I get Input file 'PPC_USA.BIN.payload' has no valid boot sector! Aborting.
How can I extract image from my ROM emulator ?
Yo must download ROM DONALDS and use their tools to dump, with -emu, in the new NBSPLIT -emu doesn't work.... sorry my bad english
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?