yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] mac_es:
From dos prompt, if you want to try only implantxip you can:

1) copy your os.nb.payload, xip.bin (from temp folder) and implantxip to a directory.

2) open a command prompt and run implantxip writing:

implantxip -xip xip.bin -payload os.nb.payload -imgstart 0 -uldr tryremove
[Windows Mobile] bobsbbq:
OK so I found out you don't use the brackets,

C:\Users\Bob\Downloads\visualkitchen_v_9_6_only_exe_+_Tools_folder\TOOLS>impl

xip -XIP xip.bin -PAYLOAD os.nb.payload -imgstart 0 -uldr tryremove

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00020000

ROM Block is : 00000800

ImgStart MIN Val. SETTED - ULDR REMOVING...

....................................

Preparing payload to be resized.....

....................................

Before:

XIP.BIN Target: size :0053FFFF

ULRD in Payload Start:00001000 Size:0031EFFF End:0031FFFF

XIP in Payload Start:00320000 Size:0053FFFF End:0085FFFF

IMG in Payload Start:00860000 Size:0001FFFF End:0087FFFF

FAT in Payload Start:00880000 Size:1CF5FFFF End:1D7DFFFF

After:

XIP.BIN Target: size :0053FFFF

ULRD in Payload Start:00000000 Size:00000000 End:00000000

XIP in Payload Start:00001000 Size:0055EFFF End:0055FFFF

IMG in Payload Start:00560000 Size:0001FFFF End:0057FFFF

FAT in Payload Start:00580000 Size:1CF5FFFF End:1D4DFFFF

Payload resized and XIP Inserted into: os.nb.payload

C:\Users\Bob\Downloads\visualkitchen_v_9_6_only_exe_+_Tools_folder\TOOLS>

Now I will see if it boots?
[Windows Mobile] ervius:
My idea:

maybe only roms with:

ROM BLOCK=10000

and

BLOCKS=800

are able to boot with ULDR Removed!

can someone confirm???
[Windows Mobile] mac_es:
Hello,

Sorry I can't flash now my phone, though I haven't any advantage as I have reduced the ulrd before... Or I'm missing something in cutting ulrd?
[Windows Mobile] bobsbbq:
No mine did not work the first time no boot stuck at the HSPL screen with upgrade ROM error.

Trying now to make with -imgstart 00330000 -uldr

My original XIP starts at 00320000 so this is what I get:

C:\Users\Bob\Downloads\wm6.5-fuze-touchpro-kitchen-21234-wwe-v1(2)\dump\Tools>im

plantxip -xip xip.bin -payload os.nb.payload -imgstart 00330000 -uldr

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00020000

ROM Block is : 00000800

IMG Min Value : 00330000 - ULDR Reducing...

....................................

Preparing payload to be resized.....

....................................

Before:

XIP.BIN Target: size :0053FFFF

ULRD in Payload Start:00001000 Size:0031EFFF End:0031FFFF

XIP in Payload Start:00320000 Size:0053FFFF End:0085FFFF

IMG in Payload Start:00860000 Size:0001FFFF End:0087FFFF

FAT in Payload Start:00880000 Size:1CF5FFFF End:1D7DFFFF

After:

XIP.BIN Target: size :0053FFFF

ULRD in Payload Start:00001000 Size:0001EFFF End:0001FFFF

XIP in Payload Start:00020000 Size:0053FFFF End:0055FFFF

IMG in Payload Start:00560000 Size:0001FFFF End:0057FFFF

FAT in Payload Start:00580000 Size:1CF5FFFF End:1D4DFFFF

Payload resized and XIP Inserted into: os.nb.payload

C:\Users\Bob\Downloads\wm6.5-fuze-touchpro-kitchen-21234-wwe-v1(2)\dump\Tools>

EDIT: Ok this above seems to work and os.nb.payload was reduced in size and booted without problem. But it seems it will not boot with the uldr totally removed using the -uldr 0 tryremove command.
[Windows Mobile] ervius:
I was wrong:

maybe only roms with:

XIP BLOCK==00010000

and

ROM BLOCK=00000200

are able to boot with ULDR Removed!!!!!
[Windows Mobile] ervius:
I've seen that you choiced 330000 as img minimum value, it does'n match with ROM Block multiplicator 0x20000, so, I fixed my implantxip to advices if choiced min.img value doesn't match with rom block:

here:
[Windows Mobile] bobsbbq:
Well I really didn't know what to use, I saw on the other post where the XIP start value was 310000 you suggested 320000. So I just added the same amount. Should I use a different value? Advise if I should try again and what value to use?

Donation on it's way.
[Windows Mobile] uhery:
maybe noob question!

... three tests ... same rom ....

1.

command:

implantxip -xip xip.bin -payload OS.nb.payload -imgstart 0 -uldr

- boot: ok

- nbh size: 65.3 mb

- log:

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00020000

ROM Block is : 00000200

ImgStart MIN Val. SETTED - ULDR Reducing...
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target: size :0025FFFF
ULRD in Payload Start:00000400 Size:0031FBFF End:0031FFFF
XIP in Payload Start:00320000 Size:002FFFFF End:0061FFFF
IMG in Payload Start:00620000 Size:0001FFFF End:0063FFFF
FAT in Payload Start:00640000 Size:06EBFFFF End:074FFFFF
After:
XIP.BIN Target: size :0025FFFF
ULRD in Payload Start:00000400 Size:0001FBFF End:0001FFFF
XIP in Payload Start:00020000 Size:0025FFFF End:0027FFFF
IMG in Payload Start:00280000 Size:0001FFFF End:0029FFFF
FAT in Payload Start:002A0000 Size:06EBFFFF End:0715FFFF

Payload resized and XIP Inserted into: OS.nb.payload

- values immediatly after flash:

storage

total 46.25

in use 3.11

free 43.14

program

total 48.96

in use 23.68

free 25.28

2.

command:

implantxip -xip xip.bin -payload OS.nb.payload -imgstart 0 -uldr [COLOR="red"]tryremove[/COLOR]

- boot: ok

- nbh size: 65.3 mb

- log:

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00020000

ROM Block is : 00000200

ImgStart MIN Val. SETTED - ULDR REMOVING...
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target: size :0025FFFF
ULRD in Payload Start:00000400 Size:0031FBFF End:0031FFFF
XIP in Payload Start:00320000 Size:002FFFFF End:0061FFFF
IMG in Payload Start:00620000 Size:0001FFFF End:0063FFFF
FAT in Payload Start:00640000 Size:06EBFFFF End:074FFFFF
After:
XIP.BIN Target: size :0025FFFF
[COLOR="red"]ULRD in Payload Start:00000000 Size:00000000 End:00000000[/COLOR]
XIP in Payload Start:00000400 Size:0027FBFF End:0027FFFF
IMG in Payload Start:00280000 Size:0001FFFF End:0029FFFF
FAT in Payload Start:002A0000 Size:06EBFFFF End:0715FFFF

Payload resized and XIP Inserted into: OS.nb.payload

- values immediatly after flash:

storage

total 46.25

in use 3.51

free 42.74

program

total 48.96

in use 23.82

free 25.14

3.

"old" xipimplant

- boot: ok

- nbh size: 61.4 mb

- log:

Implantxip by ervius!!! (Fixed!)

ROM Block is: 00000200

XIP Start at: 00320000
XIP size is : 002FFFFF
XIP Ends at : 0061FFFF
IMG Start at: 00620000

XIP Inserted into: OS.nb.payload

- value immediatly after flash :eek: :

storage

total 46.25

in use 3.51

free 42.74

program

total 48.96

in use 23.76

free 25.20

.... but .... i don't understand ... where is the "real" difference? :confused:
[Windows Mobile] anryl:
..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -imgstart 340000 -uldr tryremove

KAISER OK :cool:
[Windows Mobile] mac_es:
So, why remove uldr? I'm missing something? ¿?¿?
[Windows Mobile] bobsbbq:
Thanks it works ok with 00340000. I'm going to try one more time with the revomed uldr

EDIT: Nope the remove uldr does not work on the Blackstone 0x800 block
[Windows Mobile] ervius:
if you reduce uldr , xip starts at 10000 or 20000, if you remove uldr xip starts at 400 or 1000 (if rom is 200 block, 200*2=400, if is 0x800 block, it starts at 0x800*2=1000)

now, if xip is a little shortrer, it can ends also 1 ROM block (0x10000 or 0x20000) previous:

10000-400 bytes shorter (around 63 Kb shorter!)

or

20000-1000 bytes shorter (124 Kb shorter)

So img start could be 0x30000 instead of 0x320000 for example, but usually, seems to be same thing, removing/reducing ULDR part, all depends of just created xip-size by platformrebuilder while it works ;)

bye!
[Windows Mobile] mac_es:
Ok, I understand now. But why the xip size differs from uldr removing and uldr reducing? If you make xip starts at 400 but you make a bigger it ends at same position. No?

In post 984 (http://xdaforums.com/showpost.php?p=3831448&postcount=984) I wrote an example

Also note the crash of xipporterex
[Windows Mobile] ervius:
you didn't understand well.....

all rom parts have to respect ROM BLOCK MULTIPLIER, so, or img starts at 300000, or 320000 or 340000 (or 300000, 0r 310000, or 320000 if rom block is 0x10000), so, if you remove uldr and xip staarts at 400 instead of 10000, and the xip size is just bigger to be inserted beetween 400 to 30000, I have to add some free spaces at xip end, to insert it beetween 400 and 320000 ofsets, if it is little shorter and can be inserted between 400 and 300000, I have to add some few free space to reallign it until 300000, it's clearer now???
[Windows Mobile] mac_es:
ok, it is clear now!
[Windows Mobile] ervius:
but, maybe I have to insert another check into uldr remover part, I can check if is possible to delete instead of insert some free space to reallign xip size ; good idea, thanks, When I have some time, I'll update the implantxip :)
[Windows Mobile] anryl:
9.6

..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -imgstart 0 -uldr

working KAISER :cool:
[Windows Mobile] mac_es:
Great! :) If you could look into xipporterex (ROM Tools) to avoid the crash whith uldr cutted it would be great, too :P

This kitchen is getting better and better
[Windows Mobile] ironeagle:
implantxip -xip xip.bin -payload OS.nb.payload -imgstart 0 -uldr tryremove

or

implantxip -xip xip.bin -payload OS.nb.payload -imgstart 360000 -uldr tryremove

couldn't boot my jade after uldr removal.. works well without tryremove..
[Windows Mobile] ervius:
implantxip for max xip-size reducer on uldr remover (-imgstart 0 -uldr tryremove commands!)

here:

report if works well or not!!!

bye!
[Windows Mobile] mac_es:
It looks well

Implantxip & Payload Resizer by ervius!!!

BLOCKS SIZE IS: 00020000

ROM Block is : 00000200

ImgStart MIN Val. SETTED - ULDR REMOVING...
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target Size: 00265C48 AdjSize: 0027FFFF

ULRD in Payload Start:00000400 Size:0001FBFF End:0001FFFF
XIP in Payload Start:00020000 Size:0027FFFF End:0029FFFF
IMG in Payload Start:002A0000 Size:0001FFFF End:002BFFFF
FAT in Payload Start:002C0000 Size:0F7BFFFF End:0FA7FFFF
After:
XIP.BIN Target Size: 00265C48 AdjSize: 0027FBFF

ULRD in Payload Start:00000000 Size:00000000 End:00000000
XIP in Payload Start:00000400 Size:0027FBFF End:0027FFFF
IMG in Payload Start:00280000 Size:0001FFFF End:0029FFFF
FAT in Payload Start:002A0000 Size:0F7BFFFF End:0FA5FFFF

Payload resized and XIP Inserted into: os.nb.payload

I will try to flash it but it will not be soon...
[Windows Mobile] uhery:
uff ....you are always in the right!!! :p

nbh using old xipimplant was 69.0 mb :D

... i'm wrong to write ... but the other values are true ... no more free space! :(

but maybe my problem ... i'll try again whit another rom ... and ... the new version! :)

bye!
[Windows Mobile] ervius:
strange, free space depens also by the nbh size flashed on, somewhere some free space more you have to see..... ;)

btw. at first post the version 9.6 within the last implantxip "Max XIP reducer"!!!

bye!
[Windows Mobile] Da_G:
Hi erv, new implantxip is working great here, all functions tested, 100%!

Bug report re: add2config.txt

Because this file is in packagename\files, ends up in final ROM image, can it be moved to just packagename\ so that it won't end up in final rom? all other app.dat app.reg etc. goes here, makes sense, thanks :)
[Windows Mobile] ervius:
isn't a bug, I know.....

but I check if is possible to insert into only packagename folder near app.dat and app.reg ;)

bye!
[Windows Mobile] Mach2003:
Fantastic!

Hermes200

Xip/Sys 20931

Preparing payload to be resized.....

....................................

Before:

XIP.BIN Target: size :002BFFFF

ULRD in Payload Start:00000400 Size:0031FBFF End:0031FFFF

XIP in Payload Start:00320000 Size:002FFFFF End:0061FFFF

IMG in Payload Start:00620000 Size:0001FFFF End:0063FFFF

FAT in Payload Start:00640000 Size:0F7BFFFF End:0FDFFFFF

After:

XIP.BIN Target: size :002BFFFF

ULRD in Payload Start:00000400 Size:0001FBFF End:0001FFFF

XIP in Payload Start:00020000 Size:002BFFFF End:002DFFFF

IMG in Payload Start:002E0000 Size:0001FFFF End:002FFFFF

FAT in Payload Start:00300000 Size:0F7BFFFF End:0FABFFFF

Payload resized and XIP Inserted into: OS.nb.payload

Storage: Total 76.40mb, Ine Use: 4.86mb, Free 71.54mb
[Windows Mobile] RoryB:
I continue to show my ignorance.

Does this mean there may be a way to take the space used by the extendedROM and use it for storage or program memory?

It seems people still have problems with battery drain when they mess with the extended ROM.
[Windows Mobile] ervius:
ok!!!!!

version 9.7 at 1st post, all updated, implantxip, and visualkitchen modified to accept both "add2config.txt" stored inside or outside "packagename\files\" folder!!! ;)

enjoy!!!!! :)

bye!
[Windows Mobile] ciccione:
[HELP] build_rom.bat crash (bepe kitchen)

[ENG]

I made some 'progress and my rom is taking shape.

One problem, however, stopped me:

build_rom.bat crashes and brings me the following error:

ROM Kitchen Executable has stopped working.

I do not understand if my problem is the kitchen or if it is a problem of windows.

First of all, I have already managed to create a file 2 times .nbh flashabile (and running).

Build_rom.bat I happened to run it several times by test days ago, and the error above gave me yet another time when the second DOS window.

I solved with a system restore, but now I do not want to repeat it. I would like to understand what is wrong.

Using the kitchen Bepe with Windos Vista on C: \

Please Help.

(Erviuuuuuussss....?!)

-------------------

[ITA]

Ho fatto un po' di progressi e la mia rom stà prendendo forma.

Un problema però mi blocca:

build_rom.bat crasha e mi riporta il seguente errore:

ROM Kitchen Executable ha smesso di funzionare.

Non capisco se il mio problema dipende dalla cucina o se è un problema di windows.

Premetto che sono già riuscito a creare 2 volte un file .nbh flashabile (e funzionante).

Build_rom.bat mi è capitato di lanciarlo più volte facendo delle prove giorni addietro, e l'errore riportato sopra me l'ha dato anche un'altra volta all'apertura della seconda finestra DOS.

Ho risolto con un ripristino di sistema, ma adesso non vorrei ripeterlo. Mi piacerebbe capire cos'è che non và.
[Windows Mobile] ervius:
your problem is platformrebuilder, and that you say about:

second dos prompt (?????), 5 packages into xip (?????), suggest to me that maybe you don't use my visualkitchen.

bye!
[Windows Mobile] ervius:
this argument is oldiest, on trinity an year ago, we delete 10 Mb of extended rom to insert all of them into main storage memory, you have to fix some a dll or an exd I don't remember inside xip, then you can have all Mb of extendedrom into rom, but search "bigstorage" on this forum to see if there is something about your device!

bye!
[Windows Mobile] ervius:
did you try 9.7 visualkitchen version???

works well with add2config.txt near app.reg (app.dat) and no more into \files\ folders???

bye!
[Windows Mobile] Da_G:
Hi erv :)

With 9.7, works great:

works perfect with add2config.txt near app.reg app.dat :)
[Windows Mobile] ironeagle:
Uldr removal is not compatible for HTC Touch 3G (jade). Couldn't boot if "tryremove" option is used.
[Windows Mobile] ironeagle:
do we need to change any boot.rgu partition table entries?. thanks.

[HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable]

"01"="FATFS"

"04"="FATFS"

"06"="FATFS"

"07"="NTFS"

"0B"="FATFS"

"0C"="FATFS"

"0E"="FATFS"

"0F"="FATFS"

"20"="BOOT"

"21"="BINFS"

"22"="RAWFS"

"23"="RAWFS"

"25"="IMGFS"

"26"="BINARY"
[Windows Mobile] ironeagle:
got the ans :) they are just flags.. not the start offsets..
[Windows Mobile] anryl:
9.7

KAISER

..\TOOLS\implantxip -xip xip.bin -payload OS.nb.payload -imgstart 0 -uldr
*** OK TO USE the resizing and shrinking uldr

** NOT WORKING **
-xip xip.bin -payload OS.nb.payload -imgstart 0 -uldr tryremove
-xip xip.bin -payload OS.nb.payload -imgstart 340000 -uldr tryremove
** NOT WORKING **

thnx again :cool:
[Windows Mobile] ciccione:
Thanks Ervius, and yes i don't use your visualkitchen (sorry) but bepe kitchen.

How can i solve my problem with platformrebuilder?
[Windows Mobile] barbapappa_86:
Hi,

i have a problem. I can´t dump a stock HD ROM with this tool. It just hangs. Any one got a solution to this?
[Windows Mobile] ervius:
the link for that rom?
[Windows Mobile] barbapappa_86:
Dont have a link to it as i got it from HTC´s own site. I could upload the .nbh-file for you if you like?
[Windows Mobile] ervius:
yes, tanks, also only in mp, so I can check better way it cannot be dumped!.
[Windows Mobile] barbapappa_86:
Will give you the link when i come home from work..
[Windows Mobile] ervius:
at 1st post last implantxip.

added:

Pagepool patcher

pagepool changer

Nocert patcher!!!!!

for help:

implantxip

or

implantxip /h

bye!
[Windows Mobile] Mach2003:
I am wondering about the reported FAT size and ending address:

Shouldn't the ending be:

FAT in Payload Start:00300000 Size:0FAFFFFF End:0FDFFFFF
[Windows Mobile] ervius:
no, for me are all rights the values: I never touch the fat size, so, only start and end have to be moved, like:

(FAT start before: ) 0x640000+(sixe-size is same!) 0xF7BFFFF=(end before: ) FDFFFFF (right value!)

(FAT start After::: ) 0x300000+(sixe-size is same!) 0xF7BFFFF=(end after::: ) FABFFFF (RIGHT VALUE!)

so, all seems to be right!
[Windows Mobile] robekia1:
please help

it is not working with GENE, the generated rom is not booting
[Windows Mobile] ervius:
I cannot help, I don't have a Gene, give me some info more, implantxip screen, what kind of Rom file are in use, send me payload file ecc...

maybe is a compressed xip, so you have to use implnatxip, compress xip and reuse implantxip to reinsert the compressed xip into payload (it's only an idea!)

bye!
[Windows Mobile] barbapappa_86:
Tried to dump the stock WWE 1.57 from WIKI and it still froze. :(

EDIT: Think that it´s me doh. I´m a complete noob at this but i just cant figure out what i´m doing wrong..
[Windows Mobile] ervius:
give me the link, I can try to dump and check.
[Windows Mobile] ironeagle:
implantxip -xip xip.bin -payload OS.nb.payload -imgstart 0 -uldr

ROMs with above payload.. eats up battery so quickly..
[Windows Mobile] ervius:
seems to be strange, use other tool and compare.
[Windows Mobile] akty123:
unable to download

hi!thanks for the execellent tools!!but i can't open

sendspace

.please upload on rapidshare!!!!!!:D:D:D
[Windows Mobile] barbapappa_86:
SWE .nbh-file:

http://www.mediafire.com/?sharekey=aecf8e700073c75100d27174b47c665795e9f739ed04da5cb8eada0a1ae8665a

WWE 1.57:

http://rapidshare.com/files/2268132...7.831.1_Radio_52.64.25.34_1.14.25.24_Ship.exe
[Windows Mobile] mac_es:
Hi ervius,

Now that you are doing patches into nk.exe, could it be possible to add a command to modify date and version?

If so, we could change the version/date in the batch. It had happened twice to forgot to change OEMVERSION or nk.exe or both... :p

thank you
[Windows Mobile] Krzysiec:
Is it confirmed that newest implantxip drains battery much faster ? Just asking, because of few posts earlier someone told about this :)
[Windows Mobile] ervius:
I don't think! use uldr reducer without problem from months
[Windows Mobile] Da_G:
I too have not had a problem with ULDR reducing causing battery drain - the ULDR is only loaded in very special circumstances (I have started a new thread in this forum documenting this) - I can't think of any reason that reducing it would cause this issue.
[Windows Mobile] ironeagle:
Below is what i did..

1) Port xip for jade using Xipporter in Ervius Kitchen

2) Copy orig jade payload and ported XIP to TOOLS DIR in Ervius Kitchen

3) Run "implantxip -xip xip.bin -payload OS.nb.payload -imgstart 0 -uldr"

4) Payload reduced by Half.

5) Cook using jadekitchen

6) Flash the ROM

Battery drains too quickly..

Guys anything i miss out?..

Thanks.
[Windows Mobile] msd24200:
any idea what this means i get it every time i try to dump a rom.

System.IO.FileNotFoundException: Could not find file 'C:\Documents and Settings\The Duncan's\Desktop\Ervius\TOOLS\RomSaved\romhdr.bin'.

File name: 'C:\Documents and Settings\The Duncan's\Desktop\Ervius\TOOLS\RomSaved\romhdr.bin'

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
[Windows Mobile] alncool:
Hi Ervius,

It seems that dump feathure has been broken on that last 9.7 version. I can't dump anymore an official nbh. It start dumping and then freeze the whole system (Diamond 2.03 rom).

Anybody has the same issue ?

I'm running on XP ... I did not have this issue on v9.6 ...

Thank you for that amazing kitchen ! I'll certainly donate soon *when i'll have a little more money*.

AlnCool.
[Windows Mobile] barbapappa_86:
I have this issue to. Have reported this to Ervius with the stock ROMS i tried to dump. Se post #1042
[Windows Mobile] bobsbbq:
Guys when you have a issue like this post a link to the ROM your trying to dump so he can try it. This will help him more.
[Windows Mobile] ervius:
no problem dumping a stok rom with 9.7 version.

try with folders without spaces, also if I never had problems with them.

and if you can post a link for a rom non dumpable, I will be happy to try, if cannot post, I don't have any problem to dump roms!
[Windows Mobile] jmckeejr:
Also trying to do this. Do you get same error, "Could not find project file"?

A search here led me to page 18 I think, which I just copied from there which looks a bit different than what you have.
[Windows Mobile] coolsac32:
did that work for you? if so could u post your .bat file? because i keep getting the rom project isnt found error. :mad:
[Windows Mobile] chanvi93:
Hello

Thanks Ervius for this great kitchen tools , i want only to add splash screen in .nbh final file but don't find the right command in kitchen_build_rom.bat , can some one help me PL

Regards
[Windows Mobile] chanvi93:
I had this problem also with Trinity (Dopod Asia or WWE official rom ) , but once you convert the .nbh file to OS.nb and Dump the OS.nb, it will work , hope can help you .
[Windows Mobile] barbapappa_86:
Posted links to download the ROMS i tried to dump on post #1042 :)
[Windows Mobile] ervius:
no problem dumping them with 9.7 version, btw I'm fixing the 9.8 version to be compatible with old style ROM BUilding, when ready, I'll post it! ;)
[Windows Mobile] barbapappa_86:
Sounds awesome!

I´m trying to build a nbh from some Raw-files. I put the 2 files in the RomSaved folder but i get an error message when i use the tool to convert it to a nbh-file.
[Windows Mobile] msd24200:
anyone else ever encounter this problem and possibly find a fix for it? this is my first rom cooking attempt and this error always pops up right at the end of creating the rom. :( im using windows xp
[Windows Mobile] makeveral:
the directory shouldnt have spaces like "Documents and Settings " put your files in C:\
[Windows Mobile] barbapappa_86:
Have problem to run the raw2nbh. It says something like; "an exception that couldn't be handled....". After the message it freezes at copying Xip.bin. This is the two raw-files i trying to convert:

http://www.megaupload.com/?d=JO6W2QK6

Anyone got a solution to this?
[Windows Mobile] mac_es:
Hi,

In the nbhutil line you should add a new parameter -i IDVALUEOFSPLASH splash.nb

An example:

First define some variables in the bat file. These are for trinity, take a look in nbhutil.xml for your device

set IPLIDVALUE=0x100
set SPLIDVALUE=0x200
set RADIOIDVALUE=0x300
set SPLASHIDVALUE=0x600
set SUBSPLASHIDVALUE=0x601

Then place the .nb files in tools folder or adapt the path in the line-

So here is a complete nbhutil line (ipl+spl+radio+splashes+os) remove the unwanted parts

..\tools\nbhutil -model %deviceid% -cid %CID% -ver %versionid% -lang %langid% -chunk %chunksize% -nogui -e -i %osidvalue% ..\temp\os-new.nb -i %splashidvalue% splash.nb -i %subsplashidvalue% subsplash.nb -i %splidvalue% spl.nb -i %radioidvalue% radio.nb -i %iplidvalue% ipl.nb -b RUU_signed_ipl_spl_radio_splash_os.nbh | ..\tools\mtee /+ ..\%LOG_FILE%