After having successfully set up my Splashscreen with nbimg and rom tool i now tried to achieve the same goal by using the build-in nbh-creator of nbimg.
i derived the device information from the ini-file of the rom tool. those informations had lead me to success before.
using this info, the resulting nbh did not differ in size but was, when checking it with a hex/text editor, different in some parts. compared to the rom-tools output. Apart from a file comment inside the file i could not identify the exact differences.

Since everything looked pretty decent i decided to flash the nbh. unfortunately a blank screen was what the device woke up with, no pretty splash, just a white splash with nothing on it.

i then reflashed my rom-tool generated splash. the white stayed.
i then flashed a stock rom. the white was gone and the stock splash was there.
i then flashed my rom-tool generated splash again. the white returned. WTF?!

so i somehow managed to rip me off a chance to exchange the stock splash for a decent one. how? is nbimg at fault? are my params at fault?
I used these: "nbimg -w 480 -h 800 -p 18402 -s -D PB8110000 -S 64 -T 0x600 -F filename.bmp"
The padding is the calculated one to get my bmp up to required 786432 bytes length. i assume the deviceID is correct and so is the chunksize and the splash type.
could anyone help and point out a possible cause for this mess? i'd like to get my splash back in and also i would like to write down a little pretty guide to use only nbimg without the rom tool.
thanks guys.

Hi,

the only thing I can see in your parameters is different to mine is the size (p). At your it's p 18402, at me it's p 18400. The other what is importantly you make the .bmp image as 24bit.
Hope it's help you. Please let me know if it works now.

nbimg -p 18400 -w 480 -h 800 -F Imagename.bmp -T 0x600 -S 64 -D PB8110000

non-working nb file PROBLEM SOLVED

---

sure mate. the padding will defo be different as you certainly use a different bmp picture. i am very astonished that my padding is so close to your padding even.
The other difference is, if you didnt forget to type it in your post, the "-s" argument, which defines the Smartphone format.
did u use that when creating your nbh?

and on the other hand: my bitmap works for sure. it did work in the first attempt when i created the nbh with the rom tool. it only doesnt work anymore since i involved the nbimg nbh function. since i created an nbh with that and flashed that one i cannot flash a custom splash anymore. only the stock one works.
weird isnt it?

[EDIT]
I tested nbimg last night again with some combinations of arguments. while doing so i noticed that suddenly the conversion of the bmp to the nb does not work anymore. the very same bmp i used with the first go.
i then fetched that bmp from a backup location on a different disk because i thought maybe it got corrupted.
same stuff. parameters set as in my guide on the first go, bitmap corrupted when i converse it backwards now. always the rightmost 20 pixels are swithched over to the left side of the bmp. really weird as i did exactly the same steps as first time. and i did it about a hundred times, i also tried various other arguments, i tried to create the nbh with nbimg etc....

[EDIT 02]
PROBLEM SOLVED.
Reason for corruption: Signature.
Reason for bad flash ((no new splash installable after flash, white screen): wrong padding size.

Explanation:
NBIMG can add a smartphone signature if -s is set. if this is not set it does not set no signature but it sets a "HTC Splashscreen signature".

Assuming the LEO is a smartphone, i set this argument. when i did the first go, i obviously forgot (yes, for real!) to set that option but i did not forget to set it when i tried it again afterwards (i wasn't drunk anymore).

when i looked at the two different nbh-files (the working one i did when i made my first attempt and the new one i did today) with a hex-compare-tool (UltraCompare) i found the reason for the mentioned pixelswitch right away. The Smartphone Signature is added right at the beginning of the nbh. The HTC Splashscreen Signature is located at the very bottom.
Seing this, i noticed that the actual data shifted by the size of the signature, which means the offset of the picture data is wrong when using the -s argument. until then, i didn't notice the filesize difference yet.
So i redid the nbh file today without the smartphone signature, did a hash-check and was horrified to still see different hashes. so i compared them again with UltraCompare and found - nothing of any use.
Only then i checked the filesize and guess what?! the HTC Splashscreen Signature is exactly two bytes longer!!!

So this is why everyone else used 18400 for padding when i used 18402 for the shorter Smartphone Signature (obviously when doing this first i not only forgot the -s argument but also got the padding wrong, i presume i copied the commandline from this thread instead of creating my own. I think i was very drunk then).

This brings me to one more question: why was i thinking that i need to calculate my padding value myself when it seems to be the same for everyone?
Does NBIMG reduce the bitmap-size to a standard-value when converting it? It looks like.
That would imply that we don't need to make such a big fuss about the padding value.
I re-did the guide. Please do not use version 1.1 as it contains the wrong commandline. Version 1.2 contains correct info now.

@Sneakyghost: the '-s' flag is only for use in old non-touchscreen phones (example: htc vox, htc wings...). Now we call everything a "smartphone", but HTC made a difference between "smartphones" and "PocketPC phones" a few years ago when I wrote this tool In modern phones, like HTC Leo, you should not use the '-s' flag.

Thank you POF. This clarifies a few things actually.
Why don't you update Post 1 with some of these Infos? I think it'd save quite some folks quite some hassle.
I have read about similar problems like mine in a few places and i think if someone points out the missing info it does help a lot since many people don't manage to figure themselves.

Somehow i got this odd feeling that i am moving in a very old thread which hardly anyone still sees. Somehow i feel like there must be more advanced/better/easier methods to generate a Splashscreen somewhere on the forums.
Should i be bothered to keep investigating the mysteries of NBIMG?

If there is better ways which everyone is using nowadays please just someone put a link in here so people get redirected before they start messing here (like me )

[EDIT]
Today i checked the nbh-function of NBimg again and it worked flawless this time (mind the -s argument!).
I attached a new guide which does the trick without using the HTC Rom Tool. Only downside i could discover so far: you can't set an individual String for "version" and no Language setting either with NBimg. Doesn't really matter cuz the only moment one can see that is just before the flash in the RUU. Only cosmetical.

Thanks for the nice guide, works like a treat!

"DON'T PANIC" splashscreen

---

I'm failing to use Ubuntu terminal in order to do this...

bla@bla bla:~$ nbimg.exe -F splash1.bmp -n
nbimg.exe: command not found
bla@bla bla:~$ nbimg -F splash1.bmp -n
nbimg: command not found

that is the splash screen i want:
"DON'T PANIC"

mind to help?

This works awesome! Thank you

Hi there. I need some help because everytime I try to run nbimg.exe on windows 7 it just opens up and closes immediately... Sorry if I'm making a mistake somewhere, noob at creating splash screens lol.
PLEASE HELP
Thanks!
EDIT:
Never mind. Lol got it to work in CMD...

Originally Posted by Badwolve1

can't get it to work on win 7 Pro, build 7600 32bit

Error, Appcrash 01

Had that, too. Using v1.1 AND v1.0 on Windows 7 64bit. My command:

nbimg -F splash.bmp

Problemsignatur:
  Problemereignisname:	APPCRASH
  Anwendungsname:	nbimg.exe
  Anwendungsversion:	0.0.0.0
  Anwendungszeitstempel:	487234d9
  Fehlermodulname:	nbimg.exe
  Fehlermodulversion:	0.0.0.0
  Fehlermodulzeitstempel:	487234d9
  Ausnahmecode:	c0000005
  Ausnahmeoffset:	000015f8
  Betriebsystemversion:	6.1.7601.2.1.0.256.48
  Gebietsschema-ID:	1031
  Zusatzinformation 1:	0a9e
  Zusatzinformation 2:	0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:	0a9e
  Zusatzinformation 4:	0a9e372d3b4ad19135b953a78882e789

However, a "splash.bmp.nb" file was generated.