Database Info

Restore Internet Calling in Faria's WM6 ROM?

I have been attempting to add Interenet Calling to Faria's WM6 ROM by adding the necessary files and registry changes and re-cooking the ROM but I am getting nowhere fast. I have managed to add some files to the original ROM, make a couple of registry changes fine and change some settings in the initflashfiles.dat file to remove some shortcuts I don't want and I can get this to work fine, however re-adding the IP Phone stuff is a bit more of a task.......
I have extracted the files (or modules) from the MB ROM and added the regsistry changes and the ROM cooks just fine. When I flash the Wizard though it completes sucessfully and then reboots. I get the 1st splash screen but then when the 2nd splashscreen should appear I get a white screen. The Wizard is working as I can hear the bleep when it asks you to 'tap the screen to set up the device'. It also powers on and off OK, but I only ever get this white screen.
I have tried this about 4 times now and I am convinced the registry changes and required files are correct, but each time I get this white screen. Any ideas?
Andy

http://forum.xda-developers.com/showthread.php?t=290786
Read this... especially towards the end.

trojan9x said:
http://forum.xda-developers.com/showthread.php?t=290786
Read this... especially towards the end.
Click to expand...
Click to collapse
Already read it..... I can get Internet Calling back if I launch the VoIP.CAB that is included in that thread after installation, however I want these to be integrated into the ROM like they were originally (Faria has removed them). As I said I have had some sucess with adding other files and other registry changes it is just this bit that I am stuck on.
I did manage to get a bit further but ended up with a corrupt Today screen, no idea what happened there though
Andy

What are you stuck on?... you said you didn't have it, but now you said you can get internet calling... what exactly are you trying to do?

Faria has said that his rom takes up almost the entire space alotted. Have you tried removing some files from the rom to clear up room for the VoIP files?

trojan9x said:
What are you stuck on?... you said you didn't have it, but now you said you can get internet calling... what exactly are you trying to do?
Click to expand...
Click to collapse
I want to restore the Internet Calling option in Faria's WM6 ROM - pretty simple to understand really
I can add it manually via the VoIP.cab file but this obviously takes up RAM and can be removed via 'Remove Programs'. I would like to add the files that are missing and make the necessary registry changes then re-cook the ROM. I would prefer to keep Faria's base ROM.
I haven't tried removing anything from Faria's ROM so far, I didn't realise it was near the limit - I thought we had 128MB to play with on the Wizard, are we near that already?
Andy

Listen.. that cab only does registry fixes and puts in the NECESSARY files for the current voip functionality. it does not install anything that is not needed. Extract the cab and look at the xml file. it will tell you exactly what it does...Pretty simple concept

trojan9x said:
Listen.. that cab only does registry fixes and puts in the NECESSARY files for the current voip functionality. it does not install anything that is not needed. Extract the cab and look at the xml file. it will tell you exactly what it does...Pretty simple concept
Click to expand...
Click to collapse
Yep, already done that, hence my original post.....
I have added the necessary registry changes/additions and proof-read them several times, however once the ROM is cooked and installed the thing reboots, I get the 1st splash screen OK, then the white screen when the 2nd splash screen should appear and that's it.
I will have a look at how bloated the DUMP directory is with the additional files in there and see if I am going over 128MB.
Andy

The DUMP folder is apparently 122MB (128,512,401 Bytes) but is taking up 132MB (139,141,120) on the disk on my PC. Does anyone know if this is too big? If it is what is safe to remove?
Thanks
Andy

Done it.......
If anyone is interested I managed to get Internet Calling back into Faria's ROM.....
What I did originally was correct, however the file (or modules) that are needed for Internet Calling total about 3.5MB, which I think was slightly too much and would make the ROM bigger than 128MB (I think Faria must have realised this when developing his ROM and removed them to save space). I have been through the installed applications and files and have removed some stuff that I don't use. I then re-built the ROM and low and behold it worked first time and Internet Calling is now an option...
It still doesn't work however but that is just because it needs a provisioning XML file from a provider. Hopefully when WM6 devices appear we will be able to extract a provisioning XML file and dig deeper........
And no, the ROM is not available since this is Faria's work and not mine.
Andy

Nice,
I’m new to this and the only thing that I need from WM6 is the “Internet Calling”
I have no ides how to make the voip work. But I fond this at Microsoft.
http://msdn2.microsoft.com/en-us/library/ms898226.aspx
I really would like to test this with my “asterisk server” (http://www.asterisk.org/)
/joad

Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6

joad said:
Nice,
I’m new to this and the only thing that I need from WM6 is the “Internet Calling”
I have no ides how to make the voip work. But I fond this at Microsoft.
http://msdn2.microsoft.com/en-us/library/ms898226.aspx
I really would like to test this with my “asterisk server” (http://www.asterisk.org/)
/joad
Click to expand...
Click to collapse
I have exactly the same intentions, joad. I've got wm6 on my O2 XDA mini so I can try and connect to my Asterisk server as well!
Let's hope his eventually works.
N

joad said:
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
Click to expand...
Click to collapse
You need to add the following files into the ROM (the 1st 3 are actually modules and are in directories with the same name):
dnsapi.dll
rtcdll.dll
voipphonecanvas.dll
ipdialplan.xml
ringback.wma
You also need to add the registry entries to the default.hv and user.hv that are contained in the '_setup.xml' file from the VoIP.CAB file (or extract them from another ROM that already contains Internet Calling).
HTH
Andy

joad said:
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
Click to expand...
Click to collapse
Joad,
I agree with you. The 3.5 Mb footprint is inflated.
It's only 1.75 MB (remember if you are using recmod when you are unpacking the ROM with viewimgfs, you have two copies of the files that are stored as modules: the module version and a file copy!.
--eluth.

eluth, I knew that somebody out there would have done the right job. Congratulation! Would you mind making your rom available to us?
Thank you
Gio2003

Pleaaaaaaaaaaaaase !!!!!!
There are so many people wanting to do this now - and I have a MAJOR need for this on a Hermes -- I have a solid SIP provider and can get to it with my other apps but integration I can't test ---
I am trying soooo hard to pin this down. I have not found a single ROM yet that has the "complete" add-in of what you mention here.
It would be GREATLY APPRECIATED.
Thanks
gio2003 said:
eluth, I knew that somebody out there would have done the right job. Congratulation! Would you mind making your rom available to us?
Thank you
Gio2003
Click to expand...
Click to collapse

ckolibab said:
There are so many people wanting to do this now - and I have a MAJOR need for this on a Hermes -- I have a solid SIP provider and can get to it with my other apps but integration I can't test ---
I am trying soooo hard to pin this down. I have not found a single ROM yet that has the "complete" add-in of what you mention here.
It would be GREATLY APPRECIATED.
Thanks
Click to expand...
Click to collapse
This .CAB worked on my Wizard with Faria's WM6 real thing ROM that had the VoIP stuff removed:
http://forum.xda-developers.com/showpost.php?p=1147821&postcount=138
I then added the files and registry settings back and re-cooked the ROM.
HTH
Andy

Post install script

Is there instructions on creating a post-flash (or hard reset) install script? I'd like to have it run the cingular WAP cab, and maybe a couple others. I think I've been all over, but haven't seen anything...
Thanks!

Also - does anyone have a package or cab for camera 3.3???

Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.

JoelC said:
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
Click to expand...
Click to collapse
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!

mattk_r said:
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
Click to expand...
Click to collapse
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"

notyourdaddy said:
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
Click to expand...
Click to collapse
I just found this link that has an extended rom in it. It makes a lot of sense, especially the txt file that directs the installation and then initiates a reset. Getting warmer!
http://forum.xda-developers.com/showthread.php?t=309922

So here's what I'm thinking - just initial thoughts:
Have a folder with the base applications that are used every time like AutoRun.exe.
The user places the cab(s) in the "add files to ext rom" folder.
They run an exe that reads the directory file contents, verifies file type, copies the files to the extended rom folder, and displays the list. I'd write it in VB, since I'm most comfortable with file system operations in that language...
They change the list based on the order they want them installed using up and down arrows to sort priority.
The click OK, and it creates the config.txt file, including all necessary commands such as reset and whatnot.
That way when they build, it's all good to go.
Any thoughts?

Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy

Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best

JoelC said:
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
Click to expand...
Click to collapse
That's really good info, because I'm climbing the learning curve as fast as I can here to get a good grasp on what the extended rom is, as well as how to use it. I appreciate the conditional warnings... better to know ahead of time than find out following a problem.
I'd rather use the true extended rom (as I understand it anyway), so I don't loose any additional space for the BuildOS programs. That is, assuming the extended rom is a seperate memory location than the base...
In another thread, someone is going to post that tool. I'm really interested in how it works.
If I can get all the concepts together, I hope to get a solid tool that will improve functionality in the ROM, without adding complexity or trouble... and I greatly appreciate the help!

Interesting thread...guys, you just gave me some new ideas.
Before that...there's one thing that's bothering me...
Can we use ExtendedRom on a G4 or not...lol I thought not, until me an Boto made a clean one from a G4 ExtRom and when Boto flashed it it worked , and he has a G4. Why we always say that we don't use an Extended Rom for G4 users ?
Normaly, a G4 should/would brick when flashing IPL/SPL not Extended Rom, am I right ?
We are shrinking the OS space to integrate features of the ExtendedRom in order to all people use it but is it that true ?
Ok, now back to my idea .. I want that in my next rom to include an extended rom, of course and make it that way so when you first start your PDA, it will act like when installing windows on the PC , asking you which apps or what options you want to use. I think i can manage to do that...still the question remains ...will G4 users be able to use it ?

Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!

JoelC said:
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
Click to expand...
Click to collapse
I took the Ext Rom from the Wizard Love Rom and i edited the config.txt and deleted cabs ...that's it

Well, if it flashed OK... sounds like it might be usable after all But tell me, is Boto's G4 CID locked or unlocked? It's all very uncertain, but some of the G4 posts lead me to believe this may make a difference

ADB100 said:
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Click to expand...
Click to collapse
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.

wizzzard said:
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
Click to expand...
Click to collapse
Thanks for that but it isn't what I was really after.... I am just trying to automate everything. I have flashed my ROM that many times recently and going through the install of TomTom each time is a bit of a pain. I have got a couple of .CABs in the Extended ROM OK and these work fine, I just thought it would be nice if I could get TomTom in there as well.
Andy

I didn't want this to turn into a "how-to" thread, but I'm still scratching for hard info on the extended rom, and as many questions out there, it might be a good one to clarify some details...
As I understand it now, there's two forms of "extended ROM":
1. The true extended rom "similar to the radio ROM"
There is some "trigger" that runs the contents of the extended rom, such as AutoRun.exe?
2. The 'psuedo' extended rom that is basically a post install script to run cabs.
The contents of the folder under windows are run from a trigger that resides in the startup folder - similar to a runonce in Windows on first boot?
Does this sound close?
Also, where does the 'true' extended rom reside? Does it use the portion of memory reserved for the OS, or is there another portion just for it? (so if by adding applications to the extended rom, your available storage memory will remain unchanged - less the installed application?)
I'm presuming then by the 'psuedo' extended rom, that it does consume ROM space, but simplifies post-flash cab installations - assuming you follow the rules...
From what I see, by using the 'psuedo' ER, you waste space by keeping the installation files in addition to the installed application files.
If I'm wasting space and time by asking these questions and you know of a good extended rom tutorial, please direct me to it. I have spend some time tonight searching, but a definitive guide still eludes me... Thanks!

Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).

mfrazzz said:
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
Click to expand...
Click to collapse
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.

mattk_r said:
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
Click to expand...
Click to collapse
Yeah, never figured out why that one was never made a sticky. I just know to go look at Faria's sig and it (and a few other good links) are in there

Yikes!!!

Okay,
I have had my wizard for about a year now and in that time have flashed countless ROMs without any major problems, but yesterday I came as close as I ever have to bricking my device, and the crazy thing is that I have no idea why. I am hoping that the "real men of genius" here can help me figure out what the freak happened, or specifically what I probably did wrong
Before anyone asks, yes my phone is SIM and CID unlocked and it is a G3.
I recently moved from Core 2.0n to mfrazzz XDA Mobile 6. I really liked it but with mattr_k's easy kitchen and stripped down base I figured I could play with it a little to get some more of the apps and settings I like in it from the get go, and save the space without the ones I don't. I had been playing around with the core kitchen and the first kitchen mattk_r upped so I had a pretty good idea of what to do.
here is what happened as best as I can remember ( I should have taken notes as it was happening but I was too freaked out!)
I created the OEM directory and copied the reg tweaks and packages that I wanted from Pandora's Box (v2). I ran Build OS and selected all and it completed without problem. I ran createROM.bat and no problems there. I went into flashing, built the nbf and flashed. The flash went fine with no hang ups.
When the device restarted after flashing it went to the first splash screen and then stayed white. I left it this way for 10 minutes and then it was still like this I tried a soft reset. It reset fine but stayed white. I then tried flashing back to the original mfrazzz ROM but when it got to 95% the flash tool errored out and closed. The phone was stuck with the progress bar at 95%.
I freaked out a little and then rembered that I still had a copy of wizard love on this computer so I put it in bootloader mode and then flashed that. That got the phone back up. I then tried reflashing my "cooked" ROM. It loaded this time, but the today screen was a white background and some of the today plugins were extremely distorted and it just wasn't right.
I reflashed wizard love, and then reflashed the mfrazzz's original XDA Mobile. My phone is now fine.
Any ideas on what the heck happened.

Just guessing here....did you messed with the splash screens ?

anichillus said:
Just guessing here....did you messed with the splash screens ?
Click to expand...
Click to collapse
Not on purpose, followed the steps above as far as I can recall.

You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking

When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
If you only did the OS, what is the size of your nk.nbf? If its too big it wouldn't have flashed.
BTW: Welcome to the world of rom cooking... I've scared myself a few times

ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!

When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
mattk_r said:
ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!
Click to expand...
Click to collapse
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!

boto said:
You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking
Click to expand...
Click to collapse
well it would definitely be a tragicomedy!! or perhaps a nail biting thriller! I wanted to give as much detail as possible since I hate it when someone posts, "I bricked my device, what happened?!?!?! PLEASE HELP!!!!"

dcdivenut said:
When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!
Click to expand...
Click to collapse
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.

mattk_r said:
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.
Click to expand...
Click to collapse
I don't think I entered WWE for language, but I did everything else, and didn't do anything extra. That is something to try...

UPDATE!!
I am not sure that something as simple as typing WWE in the language field is what made the difference but I did and it worked. On my home computer I redownloaded the kitchen, base and OEM packages.
I first flashed it with nothing added to the OEM folder and it worked
Then I added to the OEM folder and that worked.
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Any help from the pros in getting this up woudl be awesome! Hopefully others will be able to use them as well.

dcdivenut said:
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Click to expand...
Click to collapse
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .

mfrazzz said:
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .
Click to expand...
Click to collapse
SWEET!
Soft key - Check
Time Sync - Check
I found this in the .rgu file in the x-mfrazzz apps. is this for the softkey app or something else?
[HKEY_LOCAL_MACHINE\Services\Stk_service]
"Dll"="\\windows\\STK_Service.dll"
"Description"="STK Service"
"DisplayName"="STK Service"
"Context"=dword:00000001
"Keep"=dword:00000001
"Order"=dword:00000005
"Index"=dword:00000005
Windows Live search - In your OEM folder there are two folders, WindowsLive and WindowsLive_DPI_96. These are both currently also in the SYS folder of mattr_k's base so wouldn't this throw an error? I know I am missing something stupid here.
Ring tones - Is there anyway I can build mp3's into the ROM? I tried placing them in the x-mfrazzz settings folder in my SYS but that didn't work, even though they get built into the windows directory. I looked in the .rgu and there doesn;t seem to be anything about where to place these
PHMReg Edit - I thought I remembered you saying something about being able to export reg settings in the correct format. I was playing around with this and the closest thing I could find was backup. That created a .rbk file but I get gibberish in notepad when I try to open it. My thought process here was to use get all the reg setting the way I want, export them, get them into a .rgu file and then build them in. Any ideas?
How do I get it so that ini_tray.lnk is not automatically in startup?.

Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?

dcdivenut said:
Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?
Click to expand...
Click to collapse
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)

mfrazzz said:
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)
Click to expand...
Click to collapse
Cool, will check when I get home, any thought on post above?

Hmmmmmm...
Seems to me your mind was on your woman and not your Wizard... just a thought,ehehe!
Congrats bro!

My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...

Madcap180 said:
My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...
Click to expand...
Click to collapse
dc just got engaged.....

Congrats DC ... if you ever need someone to pick the lock on that ball and chain, let me know...j/k

v2.0 Integrating Touch Files into 318 Kitchen [kitchen updated 7/9/07 @ 21:37 PST]

I need some help debugging the kitchen with the touchflo files.
For those who are sent the new kitchen; as you test and find solutions, please post what you did.
I wanted a sperate thread for just these specific objecives.
Here is the objectives:
To retain the ability to build a ROM with or without TouchFlo
To have only ONE seperate camera package that will work in any configuration
To allow portions of the touch software to work seperately should TouchFlo not be installed
I know there are other threads dedicated to debugging the touch software, however this is targeted at just the kitchen integration.
Current issues (v2):
Streaming Media isn't showing up in Programs, won't open.
Speed Dial hasn't been confirmed working or not.
No images for Beam - still need pictures!!!
Windows Live won't connect. Cab fixes issue. Need to find missing entries
Black Keyboard doesn't show numbers across top row. Need to find setting.
The power button will put phone into "standby" mode (basically screen and Wifi off), but won't power down.

318
I'll be glad to test. I was working on a 318 Kitchen but didn't get very far.

Too many Duplicate files.
Going back to work on my own kitchen I was much further along than what you have here.
My suggestions:
1) You should at start by deleting duplicate files. I can build a rom and flash it with my kitchen, I can't build with yours w/o getting one dup file error after another.
Please update, I will try to devote some time to your kitchen.
Thanks

NP. I'll update shortly.

My Files
I deleted dup files in my kitchen but I think I deleted one to many, now I can build, and I can flash using shelltool but it gets stuck at splash screen. Damm where did I go wrong??? I feel like a dumbass!

Hopefully this one will work a bit better. another 30 mintues till it's up.
The boot issue is probably related to the files in the OEMAPPS folder. There are some dll's in there that I found are super sensitive to this build - too bad I wasn't more careful in documenting what they were.

Documenting.
Started documenting now! Too much going on now not to, especially after my last mistake.

Test
So have you actualy built and started testing a rom with your kitchen?

I've been doing that for days... but I've tried a number of different combinations and this one seems most promising - though by no means is it ready. 1413 has by far been the easiest, but I still believe the 318 is the best choice.
I'm gonna be out until Monday night, so this is my last attempt for a few days

I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.

Whiterat said:
I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.
Click to expand...
Click to collapse
If you could, it would be much appreciated. Anything to help get closer to a fully functioning setup

Ok, so i tested the oem folder from the reTouched Beta thing. I included everything in there but my problem is that TouchFLO does not function the way it is supposed to. With what you guys are doing, have you verified that TouchFLO even operates correctly?

I thnk the touch flo isn't all its cracked up to be..I ran the reTouch wasn't a fan..its not as fast as any rom..only thing I like is the dialer and the cube

I actually have a good feeling about it. I ran the french rom for a couple days - and other than not knowing most of what it said (glad I know the OS and took 2 years of french in high school) I was very pleased with the performance. Specifically the speed at which the screen "rotated", responsiveness, and how quickly the contacts scrolled on the screen was impressive. Enough to keep me interested well into the night

so matt, think you can make a cab from it? the cube that is lol.

Here you go:
http://rapidshare.com/files/40068930/OEM.rar
Click to expand...
Click to collapse
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)

Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
So if what you are saying is true I should be able to create cabs from the correct?

AFAIK It wont be possible due to the touch driver not being replacable, you might be able to rename touch.dll and then update the registry entry.

cleaning up
Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!

hanzieman said:
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!
Click to expand...
Click to collapse
For what I see whiterat folder are some reg tweaks that you'll probably use anyways, and as far as folders to remove it might be less of a hassle to simply add the packages that you use that are not there.

This ROM problem is driving me mad!!!

Okay. I have exhausted all possibilities that I can think of for this problem. The last few ROM's I've ported have been fine, except for one thing. After flashing (or hard reset) the ROM displays the splash screen and then goes to the welcome screen (displays welcomehead.96). However, when the LogoMsg.bmp popups up (the text that says, "The device is clearing the storage. Please wait.) it only displays for a few seconds then leaves. A few seconds later the tone that accompanies the "Tap screen to begin setting up your device" sounds. The words, "Tap screen..." do not show. However, a second or two later the tone sounds again, this time followed by the text, "Tap screen to begin...". From here everything in the ROM works fine. I just cannot figure that part out.
The LogoMsg.bmp is located in OEMDrivers, so I thought I might have accidentally removed something from the OEM folder. However, I have not found anything seemingly related. Also, I thought it might have been related to welcome.exe. Though, I've tried replacing it with an older version; still no luck. Unfortunately, I have tried so many things that I cannot remember exactly what all I have tried. I've re-ported XIP's (using Ervius' kitchen and by hand) and SYS's, as well as taking a fresh copy of my base OEM.
Essentially, I am asking if anyone has come across anything like this in your cooking, and if you have any tips. I would be more than happy to upload a copy of my ROM for you to test or upload my kitchen folders. I appreciate any help that anyone can provide.
EDIT: I'll try and upload a video later to show exactly what is happening.

Hi KMFM$
I use an official rom iolite ita for porting the xip e Sys to my kaiser. After cooking i have the same problem that you describe.
After 2 mounth there is some solution... i'm crazy for this problem
Bye
Daniele

i have the same issue when flashing any of the wm 6.5 ROM's. not sure what kitchen the chefs use but it doesnt seem to effect anything.

Well, I have yet to find a "solution" to this. However, I have just simply learn to deal with it. It does not effect the ROM in any noticeable way, and from what I've heard from other chef's, this is common in all new ROMs. Not sure what is going on in the ROM during that time frame, but again, it does not effect the standard operation of the ROM.

well dont sweat it then. yeah, i think its normal for 6.5

yep been a normal thing for all my 6.5's

hi KMFM$
the ROM is 6.1 or 6.5?

When it comes to porting it depends on build ver. ect ect. Its a big try and fail operation for moust of us when thing doesnt work as planned. But to get a true port you have to use m'relloc and manual change values in the modules, there is alot of guides on how to.
On dump of nbh in kitchen it unpacks diffrently (provider to provider or if its a "pure" HTC nbh), anyway the cue is that some of the chef`s use xip files in the ROM folder while other make mxipkernel + mxipkernelLTK in SYS and oemxipkernel in OEM then os.nb+ a folder named XIP in ROM and THAT contains boot.rgu I use the last method which for some reason works best for me.

- shifu - said:
hi KMFM$
the ROM is 6.1 or 6.5?
Click to expand...
Click to collapse
Both, actually. WM6.1 builds from about CE OS 5.2.20757+, I believe, have all given the "extra" notifier. Again, I'm over it. I've just accepted the extra tone and moved on. No big deal.