Related
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?
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.
Hello gents,
I have Toshiba G810 device, and i want to know for possibility for extracting rom file add/delete files from rom.
is there specific tool for that any where??
I have the original rom file Dssu.exe updater for pc.
Is it possible to extract rom file from it?
Thanks is advance,
Ran.
use osnbtool 1.54
osnbtool -sp flash.bin
osnbtool -sp flash.bin.BIN.NB0
osnbtool -d flash.bin.BIN.NB0.OS.NB 2 imgfs.bin
then you can dump it
ferryboat said:
use osnbtool 1.54
osnbtool -sp flash.bin
osnbtool -sp flash.bin.BIN.NB0
osnbtool -d flash.bin.BIN.NB0.OS.NB 2 imgfs.bin
then you can dump it
Click to expand...
Click to collapse
Sorry, but what is the next step? and How to make it black to flash.bin file? or other the way to flash the devise? waiting..
: depack rom
osnbtool -sp flash.bin
osnbtool -sp flash.bin.BIN.NB0
osnbtool -d flash.bin.BIN.NB0.OS.NB 1 xip.bin
osnbtool -d flash.bin.BIN.NB0.OS.NB 2 imgfs.bin
: ... (imgfstodump.exe imgfs.bin)
:get imgfs.new；xip_out.bin
: repack rom
osnbtool -c flash.bin.BIN.NB0.OS.NB 1 xip_out.bin
osnbtool -c flash.bin.BIN.NB0.OS.NB.NEW 2 imgfs.new
osnbtool -extra flash.bin.BIN.NB0.OS.NB.NEW.NEW
osnbtool -2bin flash.bin.BIN.NB0.OS.NB.NEW.NEW.EXA 0x141400 -cutheader
copy /b/y flash.bin.header+flash.bin.BIN.NB0.OS.NB.NEW.NEW.EXA.BIN flash.new.bin
osnbtool -fixbinheader flash.new.bin
It can get a flash.new.FIX.bin，rename it to flash.bin to use.
The attachment is the last version of osnbtool,password for RAR is： pdaclan.com
I want to modify a rom, could you kindly guide me how to edit dumped rom sections that I dumped using the tool you recommended.. And which sections contain what kind of information.
Driver G810 Toshiba
Hi All
Plz help me ineed driver G810
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?
GUIDE
Post 1: nbhTool
Post 2: nbTools
Post 3: binTools
----------------------------------------------------------------
nbhTool 0.2 beta with SOURCE
AKA: Old nbh tools does not support new WP7 HTC device any more, so i made a new tool - nbhTool.
UPDATE 0.2 beta: 11.10.05
fixed some bugs
open source!!!!!
maybe someone can make a GUI one!
==================================================
UPDATE 0.1 beta: 11.09.22
added nbh split to nbhMerge so rename it to nbhTool
script now support '#' to make a note and Blank lines won't be error
added some functions
fix some bug
NOTE: it won't support script file of last version, just split a nbh file and you'll get a new scrpit.
Usage:
#Merge a nbh file use Script file:
nbhTool <Script>
e.g. nbhTool Mozart.txt
#Split a nbh file and create a Script file:
nbhTool -split <nbhFile> <Script>
e.g. nbhTool -split RUU.nbh Mozart.txt
NOW: i think it'll support all HTC WP7 Device, i test it with HTC HD7 & HTC Mozart Mango shipped Rom.
This tool is compiled by MinGW, so it can run without any runtime lib.Just test it and have fun, if any bugs just pm me.
nbTools - Split & Merge OS.NB Tools
nbSplit 0.2 beta - Split OS.NB File
if you used htcRIE to split a os.nb, i will tell you this tool is working in a different way.it just get BIN files only without addon bits from os.nb, so it only works with our tools to modify.
you can use this tool to get BIN Files from os.nb
USAGE:
nbSplit <OS.NB File>
Example:
nbSplit os.nb
Changelog:
0.1 beta first release version
0.2 beta fix a bug on split imgfs partition
Note:
this tool is only supported Roms of the 1st generation HTC WP7 Device and HTC HD2.
Tips:
just Drop the os.nb to nbSplit.exe can split os.nb directly.
nbSplit 0.2beta.zip
--------------------------------------------------
BINInsert 0.2 alpha - Insert BIN Files to OS.NB
Now it works, but not full functions, only support partitions below:
LOGO, BLDR, DPP, SLDR1, SLDR2, NK, IMGFS
Info:
For BINInsert 0.2 alpha
solved imgfs.bin file size must < 313.25M and i found a bug of nbSplit!
i will update BINInsert & nbSplit when i go back home tonight!
Still waiting someone who knows os.nb format well to help me solve my last 2 problem:
1.how to rebuild the last 2 blocks of IMGFS partition
2.how to rebuild the block right after LOG blocks in partition start
but tools can be used now, i just want my tool better
For HD2
maybe it'll work but not test now, some bits is different, so i'm not sure!
USAGE:
BINInsert -L <LOGO.BIN File> <OS.NB File> <New OS.NB File>
BINInsert -B <BLDR.BIN File> <OS.NB File> <New OS.NB File>
BINInsert -D <DPP.BIN File> <OS.NB File> <New OS.NB File>
BINInsert -S1 <SLDR1.BIN File> <OS.NB File> <New OS.NB File>
BINInsert -S2 <SLDR2.BIN File> <OS.NB File> <New OS.NB File>
BINInsert -N <NK.BIN File> <OS.NB File> <New OS.NB File>
BINInsert -I <IMGFS.BIN File> <OS.NB File> <New OS.NB File>
Example:
BINInsert -L LOGO.BIN OS.NB OS-new.NB
BINInsert -N NK.BIN OS.NB OS-new.NB
BINInsert -I IMGFS.bin OS.NB OS-new.NB
Changelog:
0.1 beta - first release version
0.2 beta - add DPP & IMGFS partition insert functions
BINInsert 0.2alpha.zip
WPBinaryTool 0.6.0
This place for my test version of windows phone binary tool:
I don't test the insert function, but it SHOULD work.
Use it on your own risk.
Feed back: [email protected]
Supported:
SLDR1
SLDR2
LOGO
Transfer these binary files to sth you can edit.
decompress logo will extract two bitmap image file.
decompress sldr will extract the binary file with witch you can use xidump to dump & pack.
Usage:
WPBinaryTool [-d(ecompress)|-c(ompress)|-i(nsert)] [-l(ogo)|-s(rpx)] <INPUT-FILENAME> (<INPUT-FILENAME-2>) <OUTPUT-FILENAME>
if you want to (de)compress logo/insert binary file to NB file, you should input two INPUT-FILENAME
Samples:
WPBinaryTool -d -l Logo.bin logo.bmp charge.bmp
WPBinaryTool -c -l logo.bmp charge.bmp Logo.bin
WPBinaryTool -d -s SLDR1.bin SLDR1.uncompr.bin
WPBinaryTool -c -s SLDR1.uncompr.bin SLDR1.bin
WPBinaryTool -i -l Logo.bin os.nb os.out.nb
Note:
Take your own risk to do all these things.
ChangeLog:
0.6.0 add insert function, add support of complex bitmap picture.
0.5.2 fix bmp header "84-03" issue, now will read in the right way;
0.5.1 initial release;
well done,thx for sharing
Nice work!~thanks a lot
Nice work!
Waiting for other device support.
Schubert OK
Hi!
You make my day,
So long I'm searching for way to rebuild my nbh files to create my own costum roms.
now I'm able to make costum roms too.
Flashed back a Schubert original 1.54 rom & installed HSPL
extract a 5.66.09.21a radio.nb from ansars costum radio rom
with hex editor i found out which CID's and languages ansar used
merg it back with your tool and try to flash it.
it works perfect.
thanks
Very glad this is working for you.
Now,we are trying to spend our spare time to do something funny~
Hope u can find more sweeties here next week~
UPDATE: 11.09.22
added nbh split to nbhMerge so rename it to nbhTool
script now support '#' to make a note and Blank lines won't be error
added some functions
fix some bug
NOTE: it won't support script file of last version, just split a nbh file and you'll get a new scrpit.
Usage:
#Merge a nbh file use Script file:
nbhTool <Script>
e.g. nbhTool Mozart.txt
#Split a nbh file and create a Script file:
nbhTool -split <nbhFile> <Script>
e.g. nbhTool -split RUU.nbh Mozart.txt
NOW: i think it'll support all HTC WP7 Device, i test it with HTC HD7 & HTC Mozart Mango shipped Rom.
Great work mate
works great for my hd7 kitchen
cheers
nice work！
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
hoping a GUI
btxakita said:
This place for my test version of windows phone binary tool:
maybe you can't use this tool for now
because our new tool "nbsplit" and "nbmerge" is not ready yet
but if you know how these things work, you can try it yourself.
Supported:
SLDR1
SLDR2
LOGO
Transfer these binary files to sth you can edit.
decompress logo will extract two bitmap image file.
decompress sldr will extract the binary file with witch you can use xidump to dump & pack.
Usage:
WPBinaryTool [-d(ecompress)|-c(ompress)] [-l(ogo)|-s(rpx)] <inputfilename> <outputfilename>
if you want to (de)compress logo part, you should input two bmp filename
Samples:
WPBinaryTool -d -l Logo.bin logo.bmp charge.bmp
WPBinaryTool -c -l logo.bmp charge.bmp Logo.bin
WPBinaryTool -d -s SLDR1.bin SLDR1.uncompr.bin
WPBinaryTool -c -s SLDR1.uncompr.bin SLDR1.bin
Note:
Take your own risk to do all these things.
Click to expand...
Click to collapse
Hi,
I was able to decompress de logo and charge.bmp, edited both BMP with GIMP2.0 but when I start compress WPBinaryTool crashes.
If I do not make any changes to the bmp files WPBinaryTool works.
Anyone else tried this?
Thanks for the tool.
dotcompt said:
Hi,
I was able to decompress de logo and charge.bmp, edited both BMP with GIMP2.0 but when I start compress WPBinaryTool crashes.
If I do not make any changes to the bmp files WPBinaryTool works.
Anyone else tried this?
Thanks for the tool.
Click to expand...
Click to collapse
Simple way is: Edit logo.bmp file which was generated when you decompress. Eg: Open that logo.bmp by paint application, then edit it.
Great work! Thanks for that!
But I'm looking for a way to "implant" my newly made LOGO.bin (with my own Logo's in it) into os.nb...How can I achieve that?
Thanks!
dotcompt said:
Hi,
I was able to decompress de logo and charge.bmp, edited both BMP with GIMP2.0 but when I start compress WPBinaryTool crashes.
If I do not make any changes to the bmp files WPBinaryTool works.
Anyone else tried this?
Thanks for the tool.
Click to expand...
Click to collapse
you can send your bmp file to my email [email protected]
those crash is caused by the deference between Windows Bitmap Image format and your GIMP2.0.
It works with GIMP. But when you save it, you have to choose "Advanced Options" and then you have to choose "24 Bit", because Windows Phone 7 needs this setting. But I haven't found a way to implant the selfmade LOGO.bin into my os.nb...
-WP7User- said:
It works with GIMP. But when you save it, you have to choose "Advanced Options" and then you have to choose "24 Bit", because Windows Phone 7 needs this setting. But I haven't found a way to implant the selfmade LOGO.bin into my os.nb...
Click to expand...
Click to collapse
we are working on this - nbMerge.i got crazy on LOG Blocks of os.nb. if someone know os.nb format well, just pm me, i think exchange information can make our project moves faster!
btxakita said:
you can send your bmp file to my email [email protected]
those crash is caused by the deference between Windows Bitmap Image format and your GIMP2.0.
Click to expand...
Click to collapse
Thanks mate but I finally made it. The trick is using Paint and simple graphics otherwise WPBinaryTool will go out of memory
dotcompt said:
Thanks mate but I finally made it. The trick is using Paint and simple graphics otherwise WPBinaryTool will go out of memory
Click to expand...
Click to collapse
Yeah... just a simple graphic.
Update & Open Source, so maybe someone can make a GUI one!