yashsingh1/xdaforums huggingface dataset:
[Omnia II ROM Development] ckirkp79:
I was looking right at those keys and I totally missed the <!-- at the beginning of yours. And it isn't in mine lol. So I am adding them now. I can't believe my eyes just passed over it. Awesome. I am so close I can smell the rom.

Have you checked it out what I linked on here? I had my screen duplicate again. I think it was after I sent a text and clicked power off button to exit and the screen did it again. Next time I'm taking picture so you can see it. Heck it's prob doing it in the rom i linked as well:(
[Omnia II ROM Development] amdzero:
I haven't check it yet, I can check it tomorrow maybe, I'll have to backup my current rom first.

Cooking a rom can be quite addicting, especially when you are flashing 10 times a day just to make sure that one registry entry comes out right!
[Omnia II ROM Development] ckirkp79:
It is very addicting. What do you use to backup your roms? I'll be at the 10 times a day stage here shortly when I get time to. I started over and just edited the init.dat files and started deleting vz junk off it. I'm trying to see how much space I can add to the memory.

Speaking of memory-any pointers on what I can delete (i know i can delete the bloat) but what about the extra icons they have showing for the different programs? I seen 3 or 4 sets of different styles. I'm going to try it anyways first saving a copy somewhere because deleting stuff sure does take a long time lol.
[Omnia II ROM Development] amdzero:
Well, I'm pretty sure the large icons with "Icon_" infront is for the cube program. So if you removed cube, remove those large icons. Also there is icons for email, but the samsung email program isn't installed either.

I use SPB backup to backup all my contacts/emails. I've been using Microsoft MyPhone lately as it's fast and free, just doesn't sync email. SPB backup is reasonable and I've owned it for many years. There is also Resco backup, but I haven't tried it.

If you just want contacts/emails, there is PIM backup from dotfred and it's free

http://www.dotfred.net/

I was using XDA_UC for a while, but gaveup because everytime I cooked it in, the data connection had to be manually set up.
[Omnia II ROM Development] ckirkp79:
ok so i cooked a rom. ran into a chomemanager.exe error everytime the phone restarts. Is there anyways to manually fix this problem in the phone and then just dump the rom so I can run build os again and share this rom?

I've freed up quite a bit of space and I didn't even realize it until i checked the memory on the phone.
[Omnia II ROM Development] amdzero:
That would require a lot of work, infact what you are asking to do is essentially...

replace the check engine light that keeps coming on in your car, take the car apart down to the frame, put it back into the assembly plant, and re assemble it using the factory machines.

Well you could just replace the check engine light in your car and call it good, or go to the factory and make sure the check engine light is good.

The only way you would want to do the former is if you lost the plans to build the car in the first place.

So back to ROM building...

It would be easier/faster/more efficient/practical to fix the problem in your kitchen and then build the ROM.

chomemanager is an OEM program that was added. It is not part of the standard Windows Mobile SYS

The only files that are associated with it are:

CHomeManager.lnk

CHomeManager.exe

DisplaySetupEmail.exe

just take out CHomeManager.exe and the .lnk and see what happens. I don't know what DisplaySetupEmail.exe is but I'm betting you could lose that as well.

BTW I have both of those files in my ROM (Base and Lite version) and have experienced no crashes or faults.
[Omnia II ROM Development] ckirkp79:
Had a good laugh about the car..you are absolutely right.

I guess I deleted them accidently and the chomemanager.exe error popped up. I will start back at the bottom again and take my time this time. It runs good, but I am sure nobody wants to see that error message pop up everytime they restart their phone.

I just need to figure out a system. My kitchen is cluttered lol. Thought it was going to stay organized but building roms take a lot of time.

I just need to figure out what I can and can't delete and go from there...

It makes it hard because when you type in say for instance a program you want to delete...some of the files brought up have the name of the program in it. Then you have files that don't have the name in it.

I wish i had a good example for you but I am not at my computer right now to look at the files.

How do you get your lite roms so lite? I removed stuff off the current one I am using but the free memory is still only 237. Which was better than my previous of 180 lol.
[Omnia II ROM Development] amdzero:
its a give and take, I ended up having over 330MB free one time; but there was a lot of functionallity lost, namely the ability to make phone calls!

What good is a cool phone that can do everything but make a call?

so I ended up putting a lot back in, and it was a long time before I "perfected" my lite rom. It could still use some tweaking I'm sure, so it will never be "perfect".

attached is a list of all my files in the OEMApps folder for my Lite rom.
[Omnia II ROM Development] ckirkp79:
I don't think I can ever get a perfect rom built but hey as long as it works *and makes phone calls lol* then close to perfect I'll settle for :)

Looks like I have ALOT of reading to do. Thanx 4 the text doc on your apps.
[Omnia II ROM Development] ckirkp79:
I need your help again. I was wanting to do a rom based on 21903 and i thought since it is the same as the 21889 that I would just be able to copy and paste files over from sys and xip. However I keep running into problems. BuildOS keeps popping up saying files are missing left and right even though the files are there. Am I missing something? What are the ways to use the different sys files to create 21903, 21904 and the others?
[Omnia II ROM Development] amdzero:
copy sys over is fine, but xip you must port with is a multistep procedure.

Try to copy over just sys and let me know if there are problems. If it cooks fine, I'll show you how to port a xip.
[Omnia II ROM Development] ckirkp79:
Ok when I do copy over the sys files I usually get the "this file.img" exists already error. I even tried deleting contents of old sys and moving new sys folder and something always comes up with error saying "this file exists already" I'll try it again and I'll let you know what the error is..but I would clear one error by deleting the duplicate and then another one would show up.
[Omnia II ROM Development] amdzero:
try a program called winmerge. Its free on sourceforge. This is an invaluable tool for porting sys and xip, or to find differeneces.

The program can show differences in files or folders. I usually compare new and old sys and use the program to copy over from one side to the other so I only copy over the newer files. Saves a little time, but can save a whole lot of sanity.

http://winmerge.org/
[Omnia II ROM Development] ckirkp79:
Ok I downloaded that program. I sure hope it works out I tried a duplicate file finder and that was a disaster lol. Thank you. I didn't think I would have to go through all this using the same com as before..I can't wait to start working on the newer builds once i get this figured out:)
[Omnia II ROM Development] ckirkp79:
I have no idea what to do with winmerge or where to even begin. I keep running into errors with buildos.

I'll copy and paste every file from 21903 (sys) and after I finish doing that and run buildrom then buildos pops up...it will get stuck saying "certain file already exists" or can't find "baselang409 file" even though it is there.

Very confused. Is there an easier way to move 21903 over to the dc23 kitchen?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ok so I tinkered around, made a new folder called 21903...I copied everything over from DC23 to 21903 except the SYS folder. I created a new SYS folder...and from the 21903 build I copied and pasted every file. Now I didn't add the old SYS stuff except the .ROM and the .VM because I remember you telling me I needed that. I ran buildos with an error (i was hoping no errors would pop up) it says: The File 'temp\dump\atcmdint.dll\imageinfo.bin' already exists. Well I was hoping that would work. guess not now.
[Omnia II ROM Development] amdzero:
This is because of the file already existing in OEM\OEMDrivers.

Delete these folders from sys and rebuild:

BTDUN

GPSID

WinCENLS
[Omnia II ROM Development] amdzero:
New guide is up!
[Omnia II ROM Development] ckirkp79:
u r awesome. thank u
[Omnia II ROM Development] ckirkp79:
followed your guide for porting sys and it flashed successfully! Now I am getting ready to port the xip. Thank you for writing the new guide. It was extremely helpful!

________________

followed the guide for xip porting and when I clicked buildrom, buildos shows up well it pops up with an error saying "could not find file 'Rom\XIP\Boot.rgu.'

Help!

______________________

copied over the boot.rgu file from dc23 over to new build and then it popped up with error in building default hv and user hv. I don't know where it went wrong. when i put the one file into the dump.exe at the end it came up with a stopped working error and I waited for it to say close and I closed it..but it built the files that you shown on the walkthrough. I'm copying and pasting files that are in the dc23 xip folder over to the new one and so far still not working.
[Omnia II ROM Development] ckirkp79:
here is the log file from when I tried to build my rom.
[Omnia II ROM Development] amdzero:
What it is telling you is there is a boot.rgu file that is missing. It is located in:

ROM\XIP

you need to port over you xip again, when you drag n drop xip.bin onto dump.exe, these files are automatically created for you.

Start over with the xip and see what happens. If you need help with a particular build of WinMo, just tell me the version and I'll see if I can zip it up and post it here.
[Omnia II ROM Development] ckirkp79:
tried it twice on 21904 but no success. I did everything listed but it never builds the boot.rgu.

plus it gives me the cannot build default hv or user hv error as well?
[Omnia II ROM Development] amdzero:
it won't build the .hv because of the missing boot.rgu

Attached is the XIP for 23904. Just erase the contents of your current ROM folder and use these files...
[Omnia II ROM Development] ckirkp79:
thank you. do you think all of the diff builds are going to do this?

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

Well now I am having issues with Buildos. When I click Buildrom...Windows error comes up saying "BuildOs has stopped working...windows is checking for a solution to the problem".

WTH, it worked earlier this morning, then I have unsuccessfully tried five times to build a rom and boom this happens. I restored my computer, didn't fix it. I extracted the rom to get new files...didn't fix it. I don't know what exactly is going on...but the error keeps coming up.

Is there something going on with Buildos that I am unaware of? Is there a way around this?

Sorry to bother ya, but I've done a search for Buildos has stopped working and I don't get anything off google.
[Omnia II ROM Development] amdzero:
do a search for folders inside of folders.

I know it sounds strange but every folder must have a DSM file in it reguardless of its contents. Also Subfolders need to have imageinfo.bin or the program will fail.

You say it stops working, at what point, before the BuildOS screen shows up or after you press play?
[Omnia II ROM Development] ckirkp79:
BuildOS Play screen never shows up. When I click buildrom..it's usually 30 seconds after then i receive the BuildOs has stopped working error. I will check the folders out and see what is going on. Who knows what I may have missed.

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

ok, i checked out the folders and when I ran a search under oem apps, for .rgu-nothing shows up in the search window. But when I scroll down the .rgu file is there? It should've shown up. I dunno what crazy stuff is going on with my computer.

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

Well I clicked BuildRom and now everything works. I honestly have no clue what is going on...i was using winrar but I stopped using it again and went back to using 7zip. My laptop is weird. But the play screen came up so all is well...for now:)

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

Buildos is only working under the stock dc23 rom. As soon as I copy and paste contents into the 21904 folder and create sysold and sys..and add files from 21904 sys...buildos won't work. I'm trying 21905 and see if it does it to that. Don't really know what else to do:(
[Omnia II ROM Development] amdzero:
This is odd, and hard to fix as I cannot see what you are doing.

are you using winmerge to copy the files over?
[Omnia II ROM Development] ckirkp79:
no, not using winmerge..i don't even know how to use winmerge to copy files from that program over to the folder:( That prob is my whole prob. it worked fine yest morning and ever since last night issues.

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

even using winmerge, I don't know what I should be looking for. after I copied right and left...buildos doesn't work. i feel hopeless now when it comes to doing this.
[Omnia II ROM Development] amdzero:
Every chef goes through this time don't dispair.

I've started over many times in the beginning.

Here is what I used to do and should work for you.

Make a running list of the folders in SYSOLD

then make one for SYS (the new 21904)

Then delete the folders in SYSOLD that also exist in SYS.

(basically you are removing the older folders from SYSOLD and replacing them with the new ones from your 21904 SYS)

See if that works, remember to use the original metadata, .vm and .rom folders.

Could you zip up the contents of your kitchen and pm me a link so I can take a look/test it for ya?
[Omnia II ROM Development] ckirkp79:
I will do what ya wrote down...and hopefully it will work again. I can zip up the contents of my kitchen and pm the link to ya. I forwarn ya though it's prob gonna look a mess lol
[Omnia II ROM Development] ckirkp79:
Just waiting for 4shared to upload my kitchen. I did what you wrote down earlier and still no avail:( buildos stopped working error.
[Omnia II ROM Development] ckirkp79:
did u get my pm with the link? You may have got it twice because it acted like it didn't send and it's not in my sent folder on here. If you didn't get it, I'll post it on here.
[Omnia II ROM Development] amdzero:
Okay, I'm d/l right now, soooo...

Does BuildOS work now or not?
[Omnia II ROM Development] ckirkp79:
no it don't work now. As soon as I change sys to sysold and create new folder as sys..buildos quits working.
[Omnia II ROM Development] amdzero:
Okay my friend, I see what is the problem.

you can erase option.xml and option_1.xml or you can fix them

Real Quick, option.xml is a file (could be named anything, even silly.xml) that gets parsed by BuildOS during load. If you open the file in notepad++ (my prefered text viewer) it will show you what its all about.

I usually copy an xml and change it from there, instead of creating the new one (because xml can be finicky).

in your option.xml you have the following listed:

<Item name="IRDA" group="Hidden" checked="True">
<Guid type="p">855d4be3-261f-4d7b-8378-951b0ab78d77</Guid>
<OEMDate>5/31/2008</OEMDate>
<AppVersion>19208</AppVersion>
<ButtonType>Hidden</ButtonType>
<OEMAuthor>PPCKitchen.org</OEMAuthor>
<Require>9a6a05e1-cfde-4d32-9a82-85052c4d9de7</Require>
<NeededForFeature>IrDA</NeededForFeature>
</Item>

-IRDA is the name listed in BuildOS when it loads

-Hidden is the section that it is grouped under

-True is to make the check box ticked bydefault

-855d4be3-261f-4d7b-8378-951b0ab78d77 is the unique identifier listed for that program/folder. In IRDA you will find two files, 855d4be3-261f-4d7b-8378-951b0ab78d77.rgu and 855d4be3-261f-4d7b-8378-951b0ab78d77.dsm

the .rgu is for registry entries that will be added when compacting all the .rgu in to .hv (registry to hive)

those are the main items, of course if you know the requirements for this program/folder you can list it under Require

So basically since you erased IRDA from your SYS folder, BuildOS cannot find the 855d4be3-261f-4d7b-8378-951b0ab78d77 that is listed. so to fix it you can either you can just erase the option.xml or fix it, by erasing the portions that are not used. do a search for the unique identifiers in your cabs, or remember which folders you erased out of the 21904 sys and remove it from option.xml

easy fix, HOURS of frustration, trust me I've been there.
[Omnia II ROM Development] ckirkp79:
LOL. No way. I have been working on this since this morning manually going through and copy pasting and seeing if buildos hangs. I had almost got down to the bottom with no hanging. I am glad you found my problem. I sort of figured it had to be something simple. Thank you so much for looking into it. I feel so relieved now. I use notepad ++ too! I love that program. It makes editing so much simpler than reg notepad.

Well I feel better now...and I was really close to completely restoring my computer and trying again ha ha.Thank goodness I didn't.

Sweet. 21904 will be underway now:)
[Omnia II ROM Development] amdzero:
Awesome, oh btw 21905 is already leaked.

http://joojoobee666.ppckitchen.org/Kitchens/21905/

although you don't have to use this new version, since you are still at the beginning stages it might be beneficial to you. There are rarely ground breaking fixes/additions to each build.
[Omnia II ROM Development] ckirkp79:
can i just erase both option.xml? do i really need it for rom to work?
[Omnia II ROM Development] ckirkp79:
yeah i have 21905 on computer lol. i was going to move to that if i not get 21904 working. thnx

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

Now I gotta figure out this porting xip ordeal. Hopefully I can get it going good now:) Gonna port the xip and then once I get that done successfully then I am going to go through and edit it all:)

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

Ok so I tried to port xip...and the dump.exe gave me a stopped working error, but the files were copied over. So I am going to give it a try and see if I done it right. I followed guide all way thru.

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

yup got an error. this time in buildos it saying: The file 'temp\dump\packageinfoapi.dll\imageinfo.bin' already exists. hmmm i think i may have found an easy solution. that stopped on sys\fwupdate. I copied over the dummy fwupdate and dummy sqm but left the reg versions. ok. gonna erase and try again. i'll let u know.

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

next error in buildos : Could not find file 'ROM\XIP\boot.rgu. why would it not be in there?

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

The rom you uploaded for me worked:) Least that is one great thing :)
[Omnia II ROM Development] amdzero:
yup, they are just there so you have options. Basically if you had a Lite rom and a full rom, you could use these to have options...

Say one rom you want Remote desktop in, and the other you didn't, you could use them so you have the option to check/uncheck when running BuildOS.

Erase them if you don't plan on using this feature.
[Omnia II ROM Development] amdzero:
if you get any errors in dump.exe it means that it will not finish dumping the xip.bin that you have created. It takes practice but you'll get it eventually. BTW it took me 3 tries while writing the sys/xip guide LOL!
[Omnia II ROM Development] ckirkp79:
quick question...when you go into system to look at the version number...is it supposed to match the build you used? Mine is not showing as 21904. The device id is showing 21889 and the windows mobile is showing 23515. I never really noticed if it did show the build numbers correctly before.

If it supposed to, how do i go about changing it?
[Omnia II ROM Development] amdzero:
are you looking at samsung version or system->about ?

they should match.
[Omnia II ROM Development] ckirkp79:
it's under settings/advanced settings/system/version/device and that says 21889

under version/windows mobile/ it says 23515 lol.

both are from samsung settings menu. I haven't modified this rom yet to show ms settings.
[Omnia II ROM Development] ckirkp79:
Got an update now. I did some modding on 21904 this morning...and under ms settings and about...windows version still says 23515 but shows this: (21904....)

But my device id still showing 21889. hmm

Another issue is whenever I click reply for text message it doesn't do anything now? My searching on here doesn't bring results...

I was able to clear out alot of the junk..making a base rom with 194mb free and 80 something mb ram free. took transcriber off and opera and all the vz junk. Made a new welcomehead (it's slick as hell) and I gotta figure out how to get the start button at top to point to start menu. I'm trying to learn this all on my own but could really use the pointer on how to get the reply button for texting to work again..and how to get the right build number to show. It's almost ready for release once I go through it and fix the stuff up:)
[Omnia II ROM Development] amdzero:
The version number in the samsung settings won't be right, infact they rarely are. Only an official update (or hacking the version yourself) will change that.

the system/about settings have two numbers. One is for sys and the other is for xip (I keep forgetting which is which). They are not really all that important, what is more important is that your ROM is functional.

Does the reply not work for sms/mms/email or just sms?

Can you open a new email? I'm only asking as I've seen this issue before with messaging, it was related to a certain file/folder in the sys folder.
[Omnia II ROM Development] ckirkp79:
tapping on message won't open it either. i bet i deleted something silly from sys folder. Is it bad that when I am deleting stuff off the rom, I do a search for as an example...under the 21904 folder I search for msn live and whatever it brings up from any folder I delete it lol.

can't try email out either because I destroyed the data connection on it too, lol.

I went through and just messed it all up:) I am going to redo everything but even before I messed it all up...with just a standard 21904 rom...i couldn't reply to anything or open text messages..I have to hit new under menu:(

But good thing is..I made a really slick welcomehead..it's clear as day. I should show you the picture..better than my last one! I'll upload here in a few min.
[Omnia II ROM Development] amdzero:
Now THAT is a welcome screen!

I'm working on a fix for email/data connection, I've had this problem before, it is related to something in

Shell

(text open/reply)

and one of these:

Redist_Lang_0409 and/or Redist _Lang_0409_DPI_192

(data)
[Omnia II ROM Development] ckirkp79:
thank you man! I found mass backgrounds that are super sweet. do you want me to zip them up for you so you can have some wicked cool background too?

Thanks for looking into the problem. I've been all over xda...i should search modaco as well about the issue with the data and texting.
[Omnia II ROM Development] amdzero:
I've searched before and haven't found anything, I have fixed it in the past by coping over the older (stock) shell and res folders and it seems to work.

Sure zip away my friend!
[Omnia II ROM Development] ckirkp79:
ok so the two folders you mentioned above are the ones that I should keep from dc23 then?

zipping wallpapers up 4 u now
[Omnia II ROM Development] amdzero:
yes that and shell from dc23 (until I can narrow it down to a file or setting).

Try it and see.
[Omnia II ROM Development] ckirkp79:
worked perfect. texts send out, and data is working. However..and I don't know if this pertains to shell or not...my welcome screen did not show up and it's slow...i'm going to look into it and see if I can figure it out...but texting ain't no issue anymore. thank goodness lol
[Omnia II ROM Development] amdzero:
welcome screen? you mean the one that says tap here for windows on initial boot? or your cool welcomehead didn't display?