Database Users

How to create a splash screen for Artemis, for a cooked ROM.

Right, all you smart guys/gals out there, here's a thinker....
According to this page, the .nb file for the Artemis Splash Screen should be 196,608 bytes in size.
If I create one and mix it with an OS using Dark Simpson's HTCRT though, I ALWAYS get "invalid file size". Conversely, I can disassemble and re-assemble the same ROM (including splash screen of the correct size) and it works....
.....could somebody please explain - for I'm a bear of simple brain - why my custom-made splash screen seemingly upsets the applecart?
I know it doesn't matter, but it'll stop me tearing my hear from my head...

Yes, I know you *could* use the Automated Tool which - by the way - is absolutely excellent.
But, what if you wanted to do the whole thing in one flash?
Here goes then:
1) The NBH Headertypes Wiki tells us that a splash screen needs to be 196,608 bytes, so
2) Download the attached zip file and extract the contents to a new folder.
3) Create a 96dpi, 240x320 bmp image for your splash screen. Call this whatever you like, and put the image in the folder you created in step 2) above.
4) If you have the NB Image Converter (I found it here, a nod to the authors.), run it. Select the .bmp image you saved in 2) above. [I've included it in my attachment for those that don't have it already] Save the file in your folder as an nb file.
5) Copy your nb file to a new file "splash2.002". Also in the zip file are 2 files named "splash2.001" and "splash2.003".
6) Run "GlueSplash.bat".
7) Voila! The created "MainSplash.nb" can be flashed in its own right - that would make you mad because you could much easier use the automated tool - or (more sensibly) mixed in with other nb files in a custom ROM.
If anybody spots anything inaccurate, mis-spelled or just plain mental, let me know. The usual "I accept no responsibility" Government Health Warning applies. If you're scared about flashing - don't.

andrew_green said:
Yes, I know you *could* use the Automated Tool which - by the way - is absolutely excellent.
But, what if you wanted to do the whole thing in one flash?
Here goes then:
1) The NBH Headertypes Wiki tells us that a splash screen needs to be 196,608 bytes, so
2) Download the attached zip file and extract the contents to a new folder.
3) Create a 96dpi, 240x320 bmp image for your splash screen. Call this whatever you like, and put the image in the folder you created in step 2) above.
4) If you have the NB Image Converter (I found it here, a nod to the authors.), run it. Select the .bmp image you saved in 2) above. [I've included it in my attachment for those that don't have it already] Save the file in your folder as an nb file.
5) Copy your nb file to a new file "splash2.002". Also in the zip file are 2 files named "splash2.001" and "splash2.002".
6) Run "GlueSplash.bat".
7) Voila! The created "MainSplash.bat" can be flashed in its own right - that would make you mad because you could much easier use the automated tool - or (more sensibly) mixed in with other nb files in a custom ROM.
If anybody spots anything inaccurate, mis-spelled or just plain mental, let me know. The usual "I accept no responsibility" Government Health Warning applies. If you're scared about flashing - don't.
Click to expand...
Click to collapse
Good one andrew! Shouldn't step 5 read - rename nb to "splash2.002".
And step 7 shouldn't it be mainsplash.nb rather than mainsplash.bat?
Better you change the title of the thread to the title of the second post

Yes, and Yes, and done.

To create working NB files just look at my updated splash screen tool
http://forum.xda-developers.com/showthread.php?t=317726
jvc

jcaron said:
To create working NB files just look at my updated splash screen tool
http://forum.xda-developers.com/showthread.php?t=317726
jvc
Click to expand...
Click to collapse
Hi there,
You'll note I already referenced this in my post, here:
andrew_green said:
Yes, I know you *could* use the Automated Tool which - by the way - is absolutely excellent.
Click to expand...
Click to collapse
Didn't mean to cause offence - wasn't aware the update existed.

andrew_green said:
...
Didn't mean to cause offence - wasn't aware the update existed.
Click to expand...
Click to collapse
No problem - the update was just build yesterday...

jcaron said:
No problem - the update was just build yesterday...
Click to expand...
Click to collapse
Dude, I downloaded the revised tool and triedit for a splash I know works - the resultant nb file is 150k, therefore would require the 'glue' routine to be run before it could be cooked in [to a working nbh file]. From your (obviously intimate) knowledge of your program - is this what it does before flashing? Just curious really...
EDIT: ? don't know what I did the first time - used the file suggested below by Mechsle...got the right result....apols to JC.

andrew_green said:
Dude, I downloaded the revised tool and triedit for a splash I know works - the resultant nb file is 150k, therefore would require the 'glue' routine to be run before it could be cooked in [to a working nbh file]. From your (obviously intimate) knowledge of your program - is this what it does before flashing? Just curious really...
Click to expand...
Click to collapse
Hey dude
It came 192kb for me - what image did you try? - i used xda orbit one you sent me.

meschle said:
Hey dude
It came 192kb for me - what image did you try? - i used xda orbit one you sent me.
Click to expand...
Click to collapse
Duude :-D
I'll give that one a go - I used the er. 'football' one... (Not that I'm embarrassed to name the team but they're singularly embarrassing at the moment...)
[Tottenham Hotspur]
DOH!
EDIT: It worked - Christ knows what I did the first time.
Sorry JC...I take it all back....

Thats why it not work - you use spurs bmp

meschle said:
Thats why it not work - you use spurs bmp
Click to expand...
Click to collapse
Please tell me you're not a (cough) Gooner (splutter)...

andrew_green said:
Please tell me you're not a (cough) Gooner (splutter)...
Click to expand...
Click to collapse
I support Leeds United - certainly wouldnt put them on my startup

it good, thx

Creating a Kitchen

Hi there,
I'm pretty experienced with rom cooking, but need a bit of direction from the pros here in a project I'm working on.
I have a working WM6 rom that I'm looking to make a kitchen for in order to more efficiently customize the rom.
I've decoded the rom to nba/fat format (my device uses nba/nbf format) and dumped the imgfs to a dump folder without any issues and can edit the rom that way, but I'm looking to make a kitchen.
I've used bepe's package tool to convert my dump into OEM & SYS folders without any problems. I now just need to be pointed in the right direction on how to rebuild these packages back into a working nba/fat file.
I've tried putting the OS & SYS directories in an existing kitchen like the bepe/helmi/scoter kitchens and using the imgfs tools there building the packages back into a rom. The rom builds successfully but then won't boot past the initial splash screen after flashing it.
Is there something else I need to do? Is it possible Bepe's package tool isn't properly building the packages?
Any help is appreciated. Thanks for everything each of you does to help the community

anyone?

I'm no expert, but everytime I've tried to dump a rom then rebuild it and flash it, it freezes at the 2nd splash screen. I never could get it to work, then I read somewhere that if the RGU files are missing then it would fail to boot, and sure enough on every rom I tried to dump, the RGUs were gone
My advice would be to build your rom with an existing kitchen. Collect all the packages you can find, build the ones you can't. Save all your custom graphics, themes, sounds, ringtones. Export all the registry keys for the programs you have on your phone now and use them to tweak your packages. It really won't take you much longer than if you were able to use the one you dumped. Before you know it, the kitchen you put together will be so much better than the ROM you dumped that you'll forget all about it!
My kitchen is a work in progress, but right now it's SO close to the way I want it that I can do Hard Resets without a thought as the only thing that needs to be done afterwards is restore my contacts!
All my connection settings are there, all of the buttons are set the way I like, all the colors, graphics, themes...everything! I've even set up an extrended rom with custom cabs I put together with all my commerical software with the Registration keys built-in.
I can't recommend a kitchen since I haven't used them all, but I started with Octaivio's with a 1437 build rom, now I've replaced that base rom with the 1908 build one from his latest kitchen and it's worked fine. The reason I used Octaivio is because he used Pbar as a taskmanager instead of that awful useless HTC x button (remnants of it still pop up when switching from portrait to landscape and vice versa).

joemanb said:
I'm no expert, but everytime I've tried to dump a rom then rebuild it and flash it, it freezes at the 2nd splash screen. I never could get it to work, then I read somewhere that if the RGU files are missing then it would fail to boot, and sure enough on every rom I tried to dump, the RGUs were gone
Click to expand...
Click to collapse
I can easily dump a rom, change it, rebuild it and use it successfully. That's not my issue. And, by the way, you were given misinformation about the rgu's. The rgu files are supplementary registry files that are merged into the main hives for each specific package, to make the registry entries modular. Even if you were to delete some rgu files, your device would still boot but wouldn't have the desired behavior for the packages you installed as some registry entries would be missing
My advice would be to build your rom with an existing kitchen. Collect all the packages you can find, build the ones you can't. Save all your custom graphics, themes, sounds, ringtones.
Click to expand...
Click to collapse
There are still a number of devices where no kitchen exists--mine is one of them, and honestly I'm not looking to use someone else's--I'd prefer to make my own
I just need someone to tell me what needs to be done to convert the OEM & SYS directories generated by bepe's package tool back to a working rom.
Steps I'm attempting now:
1) Dump original rom to dump folder
2) Run Bepe's package tool to make SYS & OEM folders.
3) Add modules
4) Run G'Reloc to fix overlapping modules.
5) I run BuildOS which makes the dump in the temp folder from the SYS & OEM folders.
6) I copy the original rom's fat(nba) to a temp folder
7) I dump imgfs from fat(nba) to imgfs bin file in temp folder with prepare_imgfs.exe
8) I merge the dump back into imgfs bin file with buildimgfs.exe
9) I put imgfs back into the fat(nba) with make_imgfs.exe
10) I convert nba back to nbf to flash
11) I flash the rom successfully.
12) Doesn't get past splash screen
Can anyone tell me what I'm missing or what could be making this non-bootable?
Thanks.

So its not the RGUs..
Please, if you figure this out, post the solution. When I ran into this, I searched all over the forum for a solution and found at least 2 or 3 other posts with this problem, but never a response.
Good Luck

have you modified the Iniflashfile.txt? thats the step most leave out and then it wont boot past the second splash screen

austinsnyc said:
have you modified the Iniflashfile.txt? thats the step most leave out and then it wont boot past the second splash screen
Click to expand...
Click to collapse
No, at this point I'm not trying to change the initflash so I haven't modified it. I know that when the time comes to change it I'll need to do the hex edit thing for the first 2 bytes, the unicode and the last line empty,. etc.
Also I'm not even getting to the 2nd splash. I'm not getting off the initial splash screen.
I'm thinking at this point the imgfs isn't getting put back together properly.
There have got to be some old pros who can tell me what I'm doing wrong.

I think I found part of the problem. In step 5, CreateOS.exe is doing something wrong with the hives. After running it, default.hv which is 770K+ in sys/metadata goes down to like 42K.
Anyone know why this is happening?

source said:
I can easily dump a rom, change it, rebuild it and use it successfully. That's not my issue. And, by the way, you were given misinformation about the rgu's. The rgu files are supplementary registry files that are merged into the main hives for each specific package, to make the registry entries modular. Even if you were to delete some rgu files, your device would still boot but wouldn't have the desired behavior for the packages you installed as some registry entries would be missing
There are still a number of devices where no kitchen exists--mine is one of them, and honestly I'm not looking to use someone else's--I'd prefer to make my own
I just need someone to tell me what needs to be done to convert the OEM & SYS directories generated by bepe's package tool back to a working rom.
Steps I'm attempting now:
1) Dump original rom to dump folder
2) Run Bepe's package tool to make SYS & OEM folders.
3) Add modules
4) Run G'Reloc to fix overlapping modules.
5) I run BuildOS which makes the dump in the temp folder from the SYS & OEM folders.
Click to expand...
Click to collapse
At this point I think that you have the XIP extracted already, in order to create valid boot.rgu
6) I copy the original rom's fat(nba) to a temp folder
7) I dump imgfs from fat(nba) to imgfs bin file in temp folder with prepare_imgfs.exe
8) I merge the dump back into imgfs bin file with buildimgfs.exe
9) I put imgfs back into the fat(nba) with make_imgfs.exe
10) I convert nba back to nbf to flash
11) I flash the rom successfully.
12) Doesn't get past splash screen
Can anyone tell me what I'm missing or what could be making this non-bootable?
Thanks.
Click to expand...
Click to collapse
It's a suggestion, but i think you're missing the .rgu files.
Of course, those are not needed when flashing, but when BuildOS creates the default.hv and user.hv...these 2 being invalid, the OS can't boot.
Probably Bepe can clear you better on that one.
Cheers !

source said:
And, by the way, you were given misinformation about the rgu's.
Click to expand...
Click to collapse
Apparently not, after reading Anichillus' response (which agreed with mine) I converted the HVs to RGUs and it WORKS finally!
It's probably not a good idea to reject info out of hand like that..You almost had me convinced. Thankfully I always try to verify information before I accept it, or tell someone they're wrong, mistaken, or misinformed.
Thanks Anichillus!

EasyPortOven V2.2 [Updated May 11 2008]

This is a release for my ROM porting kitchen. It ports both XIP's and SYS folders. It currently supports the following:
Herald
Wizard
Prophet
Kaiser
Elf/Elfin
Hermes
Zinc
Athena
http://www.darthnet40.com/xda/ivanmmj/Kitchens/
(You will need 7-Zip to open the file.)
This is compatible with Bepe's extended kitchen, but I don't believe he ever released one for every device out there. It requires a ROM folder with an extracted XIP folder within it. Just download the Herald's and you'll see what I mean. The ONLY tested section has been the Herald section as that's the only device that I have.
If your device is compatible with Bepe's kitchen or my kitchen, it will automatically launch the kitchen right after.
Instructions:
Delete your old SYS folder
Place the SYS file you wish to port into Working_Folder
Place your xip.bin that you wish to port into the Prepare folder
*Note: Close the XIPPort program after pressing "Make Packages." The script will take over after that.
You should not have a Working_Folder with an OEM, SYS and XIP folder (and a Tools folder if you have Bepe's kitchen, even more if you have my kitchen.)
Double click on the RunMe file and choose your device.
For those who have a kitchen:
Place bepe's kitchen in the Working_Folder (so that OEM/SYS/ROM and other folders are right within Working_Folder.) Alternatively, you can place also place all the files into EasyBakeOven's folder. Allow the Working_Folder to override EasyBakeOven's Working_Folder. You will not loose any data but will bypass a few "info" scripts. This will not cause any problems.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
If you wish to know how to do this manually, head over to my HowTo thread.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Changelog
V2.2
Added Athena Compatibility
V2.1
Added Prophet Compatibility
Added Elfin/Elf Compatibility
Added Hermes Compatibility
Added Kaiser Compatibility
Added Zinc Compatibility
Added Atom Compatibility
V2
Added Wizard Compatibility
Rewrote script to add expandability
V1.5
XIP porting complete
V1
SYS porting complete

Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Welcome to EasyBakeOven!
Devices supported:
Herald/Atlas
Wizard
Note: Make sure that the XIP in your recieving folder has been extracted already (You should have a ROM folder with a XIP folder inside it.) This is not an issue if you're using Bepe's Extended 6.1 kitchen or my own JustClean EasyBakeOven.
Thank you's go to:
Bepe for his Extended kitchen and Herald/Atlas files
ababrekar for the elfin files
l3v5y and xvx45 for the Prophet files
character and ginminded for the Wizard files
Script for the Kaiser files
tjkhattak61 for the Atom Exec files
cruzzmz for the Zinc files
caxio for the Hermes files
irus for the Athena files
Click to expand...
Click to collapse

l3v5y said:
Woo! I've failed to find a link for this up till now, but now I can cook some new ROMS!!
One thing, the read me doesn't include some of the more reason compatibility improvements...
Click to expand...
Click to collapse
Noted. Thank you!

Has anyone found this even remotely useful? If not, I will not pursue adding more devices.

Has anyone found this even remotely useful? If not, I will not pursue adding more devices.
Click to expand...
Click to collapse
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...

l3v5y said:
I have! I've ported a Kaiser XIP and a Touch one to the Prophet! Problem is I couldn't find the latest builds so they where slightly out of date...
Click to expand...
Click to collapse
Just for being nice to me, here you go!
That's the newest official build. Be careful of anything "newer," they're fakes.
It's the one labeled 19213.7z
You'll need 7Zip to open the file. In it as the xip.bin and the SYS folders.

Yay!!!
Porting time!

I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?

I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work

Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.

Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!

l3v5y said:
I have one feature request!
Would it be possible to build a feature in that cleans out the folders before porting?
Click to expand...
Click to collapse
Already ahead of you. Today I noticed that I tend to leave a mess behind. lol I'll have it remove the files before replacing them, then I'll have it delete the extra files created during the process when it's done. (This part is already ready but I just haven't uploaded it. The removing the files before replacing them, I haven't done so, yet. Although this might not really be needed. Only the cleaning after part.)
...Maybe I don't know what you're talking about. lol
Explain it to me.

AssassinsLament said:
Great tool ivanmmj.... I have a few questions. I guess I don't fully understand the process.
I've been able to get the XIP folder, os.nb.payload and romhdr.bin files from a KAISER rom... plus I used the .VM and WinCENLS_WWE folders from a working HERMES rom, but I can't seem to get past the second boot screen. A question I had is... do we use the os.nb.payload and romhdr.bin we got from the KAISER? or do we use those from a working hermes rom? and the XIP directory, do we need to change anything in there? or is just extracting it out, enough to work?
Thanks in advance.
Click to expand...
Click to collapse
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.

xvx45 said:
I think I'll test later cause actually I'm in exam but I think it work, I'm on the same device as l3v5y so I'll make my test and maybe take to you Artemis files (my other phone)
Thank for your hard work
Click to expand...
Click to collapse
That would be more than welcomed especially since I'm gonna use my Herald cooking class and modify it to teach Artemis users, also.
ai6908 said:
Awesome tool, looks like a dummy can me even port ROM's will try it out sometime. Thanks bunches!
Click to expand...
Click to collapse
My hope is that it will allow just about anyone to port a ROM. ^_^

ivanmmj said:
You need the XIP folder, os.nb.payload and romhdr.bin of YOUR device and the xip.bin and SYS folder of the rom you want to port INTO your device. Which device do you have? Tell me and I'll "draw" a map of what goes where.
Click to expand...
Click to collapse
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.

AssassinsLament said:
Thanks for replying ivanmmj... I have a hermes, and I've been doing exactly that... my problem is when I go to build it, I get "An unhandled win32 exception occurred in buildxip.exe [2276]"
If I put in my older XIP build, buildxip works fine... so I'm lost now. Oh, and I'm trying to port the 19213 official att kaiser rom XIP.
Click to expand...
Click to collapse
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe

ivanmmj said:
You'll need:
OEM: hermes
ROM folder: Hermes (uncluding the XIP folder and all the other files)
SYS folder from kaiser (look for and remove MSkernel from this folder... I'm not 100% on that folder yet and future versions may handle that folder automatically)
Place the xip.bin from the kaiser into the prepare folder.
Now run the RunMe
Click to expand...
Click to collapse
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?

AssassinsLament said:
I really appreciate your help ivanmmj, same thing again. It chokes up on BuildXIP.exe ...I have BuildXIP version 0.53 if that makes any difference. I tried with two XIP versions... 19209 and 19900. I'm about to give up.
Oh and I have Visual Studio 2008 installed, so I don't think it would be the runtimes... would it?
Click to expand...
Click to collapse
It might be.... I'll have to do some research...

Ok, I even installed the vs2008 runtimes, same thing.. I found buildxip v.54, same thing... then i moved the whole ROM folder (new XIP) out and put in the old 19209 one and it ran... so maybe there's something wrong with 19213 with hermes? ok, I give up. Thanks for your help!!

19213 porting to elfin
i'm trying to port the 19213 to my elfin, and after porting when i use bepe's kitchen, it gets stuck at this screenshot. anybody help!!!

[Solved] Sys & XIP 24614 trouble

Greets all,
I decided to dive in and update my build, but have run across a problem which reading everything isnt making me get it. I downloaded the 24614 build from one of the posts extracted it and put the folders accordingly. I unzipped the xip.bin for the same build 24614 and put that in the same location like my working build of 21887 is for the TP2, now when I open EVK I can pull down the sys and it shows me both builds 21887 & 24614, but the XIP doesnt, it only shows me 21887. Most of the posts I read have explained how to get the structure and MSXIPkernel from the xip.bin, but I really havent seen anything about how to make EVK see the xip.
I have a TP2 as I said and the rom 2.07 is build 21887, and I was trying the new manila and for testing purposes I decided to update the build, but I have run into this problem. I really wanted to update to 23114 but at this point, I just want to know what I am doing wrong.

You dont need xip.bin if you are using EVK. Maybe thats what it is causing this error. Check to make sure you have the correct files in correct folders.

ai6908 said:
You dont need xip.bin if you are using EVK. Maybe thats what it is causing this error. Check to make sure you have the correct files in correct folders.
Click to expand...
Click to collapse
I do, I triple checked it. This is the file I downloaded from the Post Latest Sys thread: 24614_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409.7z. Installed the EVKTools app that someone made for use of the extra buttons, which then put most of the files accordingly, I then removed the files I didnt need the dpi files below 192, and ran the autorecmod program to recmod the files. Then once I knew the folders were in place, I started up EVK, from the pull down for sys selected 24614 enabled all the packages, it cooks fine, once flashed, the problem is the phone comes on, then instead of getting a boot screen it goes black then turns white and the progress bar appears, once the progress bar fills up, it doesnt continue it hangs, exactly the same way that if you dont rec mod the NTConfig.dll file, which I have already done.
So I can choose the 21887 xip and the 24614 under sys and it should work fine? Okay then I'm really at a loss cause thats exactly how I did it the first time and got the same thing.

Okay here is something that may help someone help me. I just took the MSXIPKernel and the Sys from the HD2 3.01 Rom which is Build 21895 just dropped it in and cooked it and the phone flashed and setup fine, I then took the OBOE 23113 MSXIPKernel and SYS replaced the 0804 with the 0409 from the 3.01 rom cooked it same thing locks up after the progress bar completes the first time. So what havent I done?

ok bud re read the tutorials... com2 6.5 xip wont works with com6.5.X sys

+ Que PPC said:
ok bud re read the tutorials... com2 6.5 xip wont works with com6.5.X sys
Click to expand...
Click to collapse
Ok, can you provide me a link that explains this? There are alot of links in the stickies that are dead links. they are pointing to everythingdiamond.com When I was trying to understand about the builds and com2 com3 com5 and what that all means and how to go to 6.5.x.

For the XIP part to show up correctly in EVK, you need the MSXIPKernel in the correct folder in EVK and you need the OEMXipKernel in the correct folder of EVK.
The MSXIPKernel part comes from the new download that you downloaded for example 24614.
The OEMXipKernel part comes from a stock ROM for your device and does not change very often, but everytime you get a new build, you must copy the OEMXipKernel part to the new build number.
So, what you would do is under the ROM\<DeviceName> folder, copy everything in the 21887 folder to a new folder named 24614. You will then have 2 folders under the ROM\<DeviceName> folder.
Folder Structure as follows
ROM
.....<DeviceName>
..............<Build Number>
........................OEMXipKernel
.....SHARED
..............<Build Number>
........................MSXIPKernel
Once you have your folder structure set up correctly, you will be able to select the build number in the XIP box. If the build number does not show up in the XIP dropdown box, then either you do not have the folder structure set up correctly or you need to exit EVK and re-start it so it can read the structure again.
Substitute the correct <DeviceName> and <Build Number> in the above example.
Your folder might look like this.
ROM
.....Rhodium
..............21887
........................OEMXipKernel
..............24614
........................OEMXipKernel
.....SHARED
..............21887
........................MSXIPKernel
..............24614
........................MSXIPKernel

AngelDeath said:
Ok, can you provide me a link that explains this? There are alot of links in the stickies that are dead links. they are pointing to everythingdiamond.com When I was trying to understand about the builds and com2 com3 com5 and what that all means and how to go to 6.5.x.
Click to expand...
Click to collapse
everythingdiamond.info is now mobileunderground.info. Anything that was once at everythingdiamond.info is now at mobileunderground.info -- post the dead links, and I will give you the current redirect.

AngelDeath said:
Ok, can you provide me a link that explains this? There are alot of links in the stickies that are dead links. they are pointing to everythingdiamond.com When I was trying to understand about the builds and com2 com3 com5 and what that all means and how to go to 6.5.x.
Click to expand...
Click to collapse
In case you having problems and would like to see something more explained here is a great tutorial with videos and everything
http://forum.xda-developers.com/showthread.php?t=669535

indagroove said:
everythingdiamond.info is now mobileunderground.info. Anything that was once at everythingdiamond.info is now at mobileunderground.info -- post the dead links, and I will give you the current redirect.
Click to expand...
Click to collapse
http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2
I know there is more, but this was the one I was trying to read last night.
rgb-rgb,
I just did what you told me and am cooking the rom as I type, If this works Thank you for explaining and showing this step, its the only step I seem not to have found, and the link above was dead, And he'll hopefully fix.
Thank you for not driving me crazy searching thru tut's for this step.
A Great big Thank you again rgb-rgb, it worked! Between you, aruppenthal, Indagroove, & reading, I have learned alot.

AngelDeath said:
http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2
I know there is more, but this was the one I was trying to read last night.
rgb-rgb,
I just did what you told me and am cooking the rom as I type, If this works Thank you for explaining and showing this step, its the only step I seem not to have found, and the link above was dead, And he'll hopefully fix.
Thank you for not driving me crazy searching thru tut's for this step.
A Great big Thank you again rgb-rgb, it worked! Between you, aruppenthal, Indagroove, & reading, I have learned alot.
Click to expand...
Click to collapse
Glad it worked, I had problems myself when starting and had to do a lot of research. I even wrote a PDF file to help others (and myself) some time ago. it is linked in the fist post of Da_G's thread. Just in case you want to check it out. Some of it is outdated now, but you will get the general idea from it.
http://forum.xda-developers.com/showthread.php?t=544445
Look at the top for rgb-rgb's guide.

Thank you again rgb-rgb,
Just downloaded it, and have it in a safe place

[solved] No Customisation + Welcome.exe [email protected]

Device flashes - Device boots - Device runs the Welcome.exe, but then no Customisation.
Iv recently added some EXT packages into my rom. i made them myself from .cab's with cab2ext. ive tested the .cab's before adding to my rom, they do work. but some programs that did work before adding the new EXT's now dont because of no customisation eg, Task Manager - the one on the today screen and also Windows Live. (iv only noticed these two at the moment but there will be more, to be honest i cant be arsed looking for programs that work or dont work when its quite obvious its because of no Customisation, if i fix that, they will work again.. simples )
Anyway...
I opened the new EXT packages ive added and checked all the files.. eg, .dat .reg and all "FILES" files, i even checked the .lnk's and all seems ok. i then checked them again.. yet everything still looks ok, but something is seriously f*cked!
Also another problem, a wierd one..
When i Soft-Reset/Restart the device, it boots up with the Welcome.exe again? (the Welcome.exe is meant to only run the once and then dissable )
Help? iv almost got my rom the way i want it - ive been working on this rom for 2months and i dont want to start building the rom from scratch...
..again! pmsl
Does anyone have any idea what is wrong, if this has happened to you, how did you fix it?
Thanks!
Rn

Check your runcc.lua, then the conf*.txt files you include in your rom, then all the commands you execute inside them.
One of these commands go wrong in your first boot and so you are stuck on customization.
If you use xda_uc or another user customization method, check those scripts as well.
It may happen, for example, if you try to install a cab and for some reason it fails.
If in your recent packages you overwrite one of your conf*.txt file, this could be the cause.
Ciao

...
cheers dude, thanks for your time and help, i think i understand what you meen..
[1)config*.txt <-- all config files are ok.]
[2)runcc <-- googled and i dont use]
[3)xda_uc <-- googled and i dont use]
raving_nanza said:
iv almost got my rom the way i want it - ive been working on this rom for 2months and i dont want to start building the rom from scratch.....again! pmsl
Click to expand...
Click to collapse
its ok claros, f*ck it dude, its the second time this problem has happened to me, it happened on my first rom too.. (2months ago.lol)
i litteraly started again from scratch (a nice clean slate) ill just start my rom again like i did then which will solve my problem.lol ive got all my programs and setting backed up (*in a messy folder of messy folders )
my new kitchen will basicly be up and running again by the end of the day, its my birthday on wednesday so i may as well set it as the rom date.lol
Raving_1337_Rom_V3 (Alpha)
Cheers anyway dude, muchly appreciated!
Rn
[changed title to solved, @claros]

raving_nanza said:
its ok claros, f*ck it dude, its the second time this problem has happened to me, it happened on my first rom too.. (2months ago.lol)
Click to expand...
Click to collapse
This happened to me at least 20 times, or more
Let's check together what happen at first boot, if I'm wrong anybody else will correct me.
1) files are moved from \windows to other directory according to your app.dat / initflashfiles.dat.
2) .provxml files are parsed to change config values or filesystem
3) welcome is executed, but this command don't stop startup so:
3a) autorun.exe or runcc is executed too to customize rom: these package runs according to the commands inside various config*.txt files in oem packages or sometimes in ext packages
4) user configuration, usually included as a call inside one of conf*.txt files is executed. If you don't use xda_uc, user customization should follow the same syntax as autorun/runcc
5) Last conf*.txt file should include at least a
LOCK: Disabled and a reset
At this point you should have completed the welcome wizard. If not, and your calibration data is not in registry, your are prompted again with welcome wizard at second boot.
Common errors during boot sequence are:
- wince.nls is missing
- app.dat / initflashfiles.dat error, such as creating subfolders inside non existent folders or statements not in unicode format
- registry / provxml errors during setup of welcome.exe itself, for example you disable the whole welcome wizard but don't write calibration data into registry
- chain error inside conf*.txt files, such as config.txt calls config_operator.txt which call config.txt, generating a loop
- a cab or command inside a config*.txt files cannot be installed, for example for lack of space or a missing certificate
What I usually do in these cases is:
- check platformrebuild log file for errors
- save my last tmp/dump folder to check what is really inside the rom and what is really overwritten by what
- If you can connect by activesync to device before reboot, explore the device itself, it's processes and registry
- recompile the rom putting semaphores inside app.reg files, .provxml files, config*.txt file. I usually add an ext package to be included as the last one (ZZZ_Claros_Fix) where I put a special app.reg, a .provxml and a modified copy of config.txt, config_operator.txt, config_end.txt etc etc.. If you don't have a diamond, you can boot without sdcard to avoid any sd_config.txt error
Starting a new kitchen from scratch for me is at least 20 days of work, I'd spend a day more finding a solution
Ciao

claros said:
This happened to me at least 20 times, or more
Click to expand...
Click to collapse
A Mortscript called Autorun.exe
V2 working again, Cheers!
*i started setting up a new kitchen then thought f*ck that!
Rn

Are you saying that you were cooking in mortscript, and the autorun.exe file from the mortscript package over-wrote the one from your OEM package? I think that happened to me once a while ago. I just left out the one from mortscript; I've never needed it before, anyway.

...
yeah a mortscript called Autorun.exe over-wrote my OEM Autorun.exe
i deleted it the mortscript, everythings sound now