What you'll need:
CAB editor, such as OCP WinCE CAB Manager
Madkat's WM2k3 Boot Image Tool (attached)
Adobe Photoshop or other image editor
a compatible HTC device such as the Magician or Blue Angel
Summary:
Customized SplashX.nb files to be installed in \Windows directory of your device
Included:
Customizable Splash2.psd file for use with Adobe Photoshop
Steps:
1. Change the Splash2.psd file as necessary, then save a 24-bit BMP file called Splash2.bmp.
2. Use Madkat's Tool to convert the BMP file to an NB file.
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
4. Save the CAB file and run it on your device!
Magician devices have only one splash screen, and it must be saved as Splash2.nb.
Blue Angel devices have two splash screens, Splash1.nb and Splash2.nb. Use the above steps to incorporate both splash screens as necessary.
Splash screens will be retained even after a hard reset, so use this after the Anansky's Big Storage hack, or if you just want to personalize your device, such as in the unfortunate event that it's lost or stolen - unless they know this trick, they won't be able to get rid of it!
Have fun!
Thanks mate works like a dream!!
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
PS. I've have both tools on my pc and can repost them, but they are from this site!
hshortt said:
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
Click to expand...
Click to collapse
Tried that way myself a while ago but for some reason it refused to work for me? (could of been the fact i used a file called XDA2_bootimage_changer.CAB)?? anyway now I can use self contained cabs so I make some splash's for my friends
PS. I've have both tools on my pc and can repost them, but they are from this site!
it must be me, but what cab file are we using here ?
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
Click to expand...
Click to collapse
:?: :idea: :!: :?:
DOH! I forgot to include the file. It's there now in the top post.
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
well, i'm using resco file explorer. i'm choosing on my pc to send the file to windows directory. he ask's me if i wanna overwrite it, i click yes and then it's done. i'm reloading, but still qtek logo on the screen(( what am i doing wrong?
ps. i tried to use WinCE CAB Manager but i didn't figured out how to use the program....
update:
oh, i needed to use a different file...
thanks guys! well done)
my version (unfortunatelly understandble only for russian speaking users) but maybe somebody will like it)
http://zhgun.ru/pics/i/draw/jamming_.jpg
http://rapidshare.de/files/2112736/jamming.cab.html
hshortt said:
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
PS. I've have both tools on my pc and can repost them, but they are from this site!
Click to expand...
Click to collapse
hi, can't seem to download the attachments, could you repost them?
If you don't like Bill's Stuff...
I wonder if anyone can put some help my way.....
I used the xda2 image changer before and I had custom images on my XDA2.
I use this and all I get is a black screen on startup. If I open the .nb file with the converter it shows as it should. (this same .nb works on my XDA2!)
I now have a plain black boot up screen!!
DOH!!!!
Any ideas......?
THanks
First i had the t-mobile splash... wich i didn't like.
Now, whatever bootsplash cab i make, or download here.. after running it, my bootscreen stays blank ( as in black ).
oh well... its an improvement over t-mobile pink
( or is it because i'm running an ancient rom : 1.01.00 WWE ?, only have the device for 3 days... will be upgrading this weekend tho )
Here are my 2 favourites Splashscreens.
The blue one ist for the silver Magician, the darker one is for the new O2 XDA mini (black edition).
Hi I've editted the o2 logo here's the jpg file
I tried to upload the psd so you can edit it but it doesn't work, to bad!
Step-by-step making your own splashscreen
Guys,
Simpler than this you will not find.
Goto
http://pocketpcdubai.infopop.cc/groupee/forums/a/tpc/f/582600994/m/138105069
and find everything you need to know.
It worked perfectly for me...
Excellent information, real easy to do
this is mine:
Awesome...
I saw this before, but I have just tried it... and it is really cool 8) ... it gives the device a whole new look...
thanks BTT
My way to splash changer.
Hi,
I thanks to BTT for Splash Changer how to. But it is troublesome to everytime run WinCE cab manager in order to put Splash2.nb to the .cab file.
I try to remove Splash2.nb from the .cab file (and renamed the .cab to splash_changer.cab). Afterthat, put the Splash2.nb manually to \windows on PPC. Voila....., no need to everytime run WinCE cab manager!!!!!
Process:
1. Edit .bmp file to your like (Must be 240x320 pixels, 24bit).
2. Use nb_image_converter_859_418 to convert .bmp file to .nb, and change the .nb file to Splash2.nb.
3. Put Splash2.nb file directly to your \windows on PPC. You can do activesync and explore it.
4. Put splash_changer.cab to \temp for you to easier found it.
5. Run file explorer on PPC, and tap on splash_changer.cab.
6. Done! You can check by soft reset the PPC.
Hope it is helpful!
Regards,
Arto.
can it work on normal pocket pc?
can it work on normal pocket pc? (x50v)
Re: can it work on normal pocket pc?
avi9899 said:
can it work on normal pocket pc? (x50v)
Click to expand...
Click to collapse
No idea....
Regards,
Arto.
Hello all,
I have a SDA and I am trying to personally customize a WM6 rom based off of Nitrogenious (v5...by the way, great version, thanks!!) WM6 but I cannot find any detailed information on adding files (cab or exe...moreso cab files) to the ROM. I have found Molski's Devpack by Duke for dumping/rebuilding ROM (Great pdf guide and awesome tools!!).
I am needing the detail to actually add files (exe or cab) for customizing this ROM (i.e. what is the process in obtaining the .dll or other related files and where do I add the extracted files...Which files do I actually use after extraction? And do I create another folder and just place them in the dump directory? What do I do? Here is an example: I am wanting to add the HTC File Manager 1.41 cab file to the ROM and I need to know which files to use and where to place them.
I believe I have all the necessary tools: Molskis DevPack and WinCE Cab Manager, I just need a little guidance/assistance.
Any help would be greatly appreciated!!
Thanks again and thanks for this great forum!!
vjgrace
The title says everything.
Only thing with WinCE Cab Manager is that I installed it and after a reboot it says that my trial is over - darn i havent started it before in my life in my computer and it says that trial is over
Damn.
Are there any alternatives or where could i get a working version? (version lower than 2.0 eg: 1.1)
I use Pocket PC Installation Creator, it's not free but a hell of a lot cheaper then WinCE Cab manager (http://www.aperitto.com/index.php)
Or if you are handy with making .inf files and using cabwiz try the utils in the zip: MSCEInf.exe to extract contents from a cab (including .inf file) and cabwiz.exe to make cab from .inf file
You can edit the inf or use it as an example for your own inf and than use cabwiz to make new cab. Disadvantage is that it is a lot of work if you have cabs with a lot of registry keys and files
good luck
Can anybody explain me how to make a self-extracting cab file, and what software to use?
What i'm trying to do is this:
I want to CAB some translated Manila files and put them into the \Internal Storage\Backup and Restore\Cab\ directory of my Diamond, so that i can have the files automatically extracted to the devices map \Windows\ after a hard reset.
Thanks & best regards
You can use WinCE CAB Manager. There is a free test version aviable. It can create cabs easy.
or QuickCAB
I am learning how to cook a Kaiser 6.5 Rom using osKitchen and just wanted confirmation that I am doing this right.
Any help / advice / redirection will be appreciated.
Thanks for reading.
---------------------------
Using htcRIE_0.5.0.12, I have dumped the XIP from WM 6.1 Rom (RUU_Kaiser_O2_UK_3.29.206.0) and get the following output:
XIP
-OEM
--LangDB
--OEMXIPKernel
-SYS
--MSXIPKernel
--MSXIPKernelLTK
--WinCENLS_WWE
1) LangDB is an empty folder with only a dsm file inside. Hence I have excluded this folder from my kitchen.
2) In OEMXIPKernel I have replaced cecompr.dll with the contained in Post 9 of this thread (http://forum.xda-developers.com/showthread.php?t=438676) that supports LZX compression. I have also deleted nk.exe folder to use the one contained in osKitchen (modified to work with 6.5 kernel). Should all other files / folders in OEMXIPKernel including boot.hv and boot.rgu be left untouched or is there scope for modification / tweaking?
3) MSXIPKernel - Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). I have deleted mem card encription mencfilt.dll since I read that it is safe to do so.
(a) do I need to edit the dsm file to remove reference to mencfilt.dll or does Bepe's package rebuilder automatically create new dsm files?
(b) since the file size of modules in donor and source MSXIPKernel are different, do I need to manually reallocate the addresses of each module or is that automatically done during the cooking process?
4) MSXIPKernelLTK - Same again. Deleted this folder and simply replaced with the one contained in 6.5 SYS package (build 28205). This folder only contains a dsm file so I guess no reallocation is required.
5) WinCENLS_WWE - With this one I am not sure. Initially I thought of deleting this as well since it is contained in 6.5 SYS package. But elsewhere it was suggesting that this is not allowed since the Rom may not boot. OndraSter suggested that I transfer the wince.nls file into OEMXIPKernel and delete the WinCENLS_WWE folder. If i did this then
(a) do I need to edit the dsm file in OEMXIPKernel folder to add reference to wince.nls?
(b) should I delete the WinCENLS_WWE folder from 6.5 SYS folder to avoid duplication (although file sizes are different)?
Anyone willing to spare some time to help please?
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box . 2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
4)This is correct.
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Thanks for responding to the distress signal.
Quetzecotyl said:
Not sure why you are using ROM Editor to do this; it would be so much easier just to use osKitchen or Ervius and dump that ROM, then all you'd have to do is copy/paste. I'm also learning, but I'll answer what I know.
Click to expand...
Click to collapse
I use the ROM editor since I get an error whilst using osKitchen to extract RUU_signed. Infact there is also a warning that pops-up explaining that this utility in osKitchen is awaiting a rewrite and to expect failures.
Quetzecotyl said:
1)I do the same. Almost all chefs delete almost all the .dsm/package.ini files in their kitchen folder before cooking with osKitchen or Ervius's VK. I don't know why it is possible to cook without them, but it's easier then maintaining them and saves a tiny bit of space. It is also why almost all cooked ROMs are not able to be dumped as per OEM ROMs--the file associations and shadows are gone (which is what the .dsm/package.ini files provide).
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
2)Let me preface by saying that ideally, you shouldn't be touching anything in the OEM/MS kernel. 1st q: If you are using osKitchen, why are you doing this? It can compress with XPR or LZK out-of-box .
Click to expand...
Click to collapse
I was getting errors with osKitchen when using the original 6.1 cecompr.dll. It is only when I replaced it with the version in the referenced post that the errors disappeared.
Quetzecotyl said:
2nd q: The nk.exe is modified to use more RAM, not to work with WM 6.5. Kaiser doesn't have a native WM 6.5 nk.exe, so chefs use an older 6.1 nk.exe from a released ROM and patch it to use more memory if they want.
Click to expand...
Click to collapse
Thanks for the clarification .
Quetzecotyl said:
3)I've never deleted that, but this is otherwise correct. (a) You could use DSM editor and remove that one file association yourself. (b) Automatic, as I've never reallocated anything in the kernel and my ROMs cook perfectly.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
4)This is correct.
Click to expand...
Click to collapse
Thanks. This is solved .
Quetzecotyl said:
Last one I don't know. I've never done any of that and my ROMs cook/work fine. If I did what OndraSter recommended, I still wouldn't do either (a) or (b) because I don't think it matters to the kitchen script--he would have probably told you to do that as well.
Click to expand...
Click to collapse
When I dump the 6.1 ROM, wince is part of the XIP. The recent 6.5 releases (28008 and 28205) contain wince as a SYS package in folder WinCENLS_WWE. This is what confuses me - is wince device specific or is it build specific .
If I place the wince from 6.1 ROM in OEMXIPKernel and also select the one in 28205 SYS as an ingredient, then either I am duplicating (and possibly creating a conflict since the file sizes are different) or the kitchen script is smart enough to ignore one of these?
This has also been discussed at http://www.everythingdiamond.info/showthread.php?t=444&page=46 but without any strong conclusion.
Has anyone else experimented with wince?
OK, about WinCE--I wanted to make sure, but skimming through my build logs for a time, I don't think I've ever had that in my SYS. WinCE must be device specific because it is part of the OEMXipKernel, and I've used the same one (ie, OEMXipKernel) maybe 30+ times and can not recall ever seeing a wince.nls in my SYS updates. I've only cooked the 21xxx and 23xxx WM6.5 COM branches, but I can't help but think that the WinCE in your SYS update comes from the device the SYS dumpers used. If I were you, my first go around I would exclude it and use the one from your OEMXip. If for some reason your ROM doesn't boot (it could be so many other things), try replacing your wince.nls with the one from your SYS update (highly doubt this).
BTW, I recommend using Ervius for dumping, as it has never given me any issues.
I think what you say seems logical. I will give it a try and feedback how it went. Thanks once again.
If you dump it via my kitchen and put name Kaiser, it should autogenerate all Sources folder with OEM, original SYS and put NK and XIP on right places actually. (I tried it on newer version of Kaiser's ROM when I was making this dumper so it should work fine.)
And if you restart kitchen, it will load all things automatically (or I hope so, I haven't tried the new UI yet, I'm still at the old one since I actually prefer it...)
I get an error when dumping using your kitchen. I have posted the exception text in your thread.
ps: This is sorted. My RUU_Signed.nbh was not in root of osKitchen dir but a different dir where I place my ROMs.