Database Info

Little Help for First Time Cooker!

Hi There,
Ive been admiring the work of many here for a very long time.
I have owned a Blue Angel for about 18 months and a wizard since January.
The wizard has been flashed around 7 times in 4 weeks lol which is quite a bit for an HTC noob like me.
I have tried Orwells Rom (very stable for me) but then decided to upgrade to .mUn.'s rom as it was a newer version.
Unfortunately it wasnt quite as vanilla as I like.
Vanilla == No reg tweaks, No apps at all and no damned Cyberon!
Everytime I try to build myself a rom (tried Molski's kit and NotTooSmart's) I get a problem.
Dump decrypted NBA with Typhoon Tools
prepare_imgfs (with nosplit)
viewimgfs
hv > rgu
Added REGEDIT4 to the top line, saved as unicode, did everything correct as far as I know.
then back to hv's (yep right size, 750kb ish)
Then put it all back together. (incl the removal of bytes form initflashfiles.dat back to the first
1st Time with Molski's Kit = Booted fine, but would never load OS after a softreset
(few more attempts with the same kinda thing - failed )
Last time with NTS's kit = Stuck on the splash the IPL/SPL and would go no further.
Sorry for my ignorance, but what have I missed!
I hear about XIP sections and what have you, means very little to me!
I just want to build myself a rom on which I can mess around with :'(
Thanks Folks,
-Whiterat

When you remove the bytes from the front of the initfileflashes.dat file, what are you removing? It should just the FF, FE. Also, make sure you have English set in your regional and language options under the advanced tab.
If that fails, you may have a corrupt nk.nbf, since you've had BOTH kitchens fail. I would download a new ROM copy, dump and immediately rebuild and flash just to make sure you are properly going through that process. Then make one change at a time. It's time consuming I know, but you'll be wiser for the experience.
Peace,
JB

jwzg:
Thanks for taking the time to reply.
initflashfiles.dat should start with a ; (Since ; is used to remark lines) so I just remove back to that.
With regards to setting English, where abouts is the advanced tab? In what program even?
I did as you said with the nk.nbf and it goes on just fine without editting a thing
Its a pain testing these things, since I usually end up having to restore from SD which rewrites the extended rom, gsm, os, spash screen, htc screen,etc and then it takes ages for me to reflash my bits!
I can upload my rom if someone is willing to take a peek, see if I have missed something really obvious?

Too many files?
I had a similar issue (I think?) where everything seemed to work and the nk.nbf file was created OK. However there would be an error logged in the Windows Event Log about faulting an application. The resulting ROM image would install but I got a white screen following the reset (it made noises like it was working though). I followed the instructions for Molskis cooking tools to the letter and couldn't understand what the issue was I posted on here for some assistance but after I got no helpful replies I played around a bit more and realised the dump folder was slightly over 128MB (Size said less but I think it was over?). Anyway I removed some more files I didn't need and low and behold it all worked
I don't know what the absolute maximum size the dump folder can be, but I keep mine below 128,000,000 bytes....
HTH
Andy

ADB100 said:
...but I keep mine below 128,000,000 bytes....
HTH
Andy
Click to expand...
Click to collapse
Size on disk?

Whiterat said:
jwzg:
Thanks for taking the time to reply.
initflashfiles.dat should start with a ; (Since ; is used to remark lines) so I just remove back to that.
With regards to setting English, where abouts is the advanced tab? In what program even?
I did as you said with the nk.nbf and it goes on just fine without editting a thing
Its a pain testing these things, since I usually end up having to restore from SD which rewrites the extended rom, gsm, os, spash screen, htc screen,etc and then it takes ages for me to reflash my bits!
I can upload my rom if someone is willing to take a peek, see if I have missed something really obvious?
Click to expand...
Click to collapse
Not talking about that...
You have to open up initfileflashes.dat with a hex editor and remove the first two bytes (FF, FE). Then you can put the file back into the dump folder and build it.

jwzg said:
Size on disk?
Click to expand...
Click to collapse
The dump folder of the last one I cooked said:
Size: 121 MB (127,089,811 bytes)
Size on disk 131 MB (137,654,272 bytes)
And this worked fine, it was a re-heat of Faria's Real Thing ROM where I re-added VoIP & Windows Update (VoIP works but Windows Update won't and I can't figure out why - the application fails to connect to the MS site and won't close, but that's another story.......).
Andy

Yep I get that, I am a reverse engineer by trade so naturally I get what the manual had to say.
The limitation of imgfs is IF there are more than 1500 files being added to nk.nbf, the file size limitation also applies.
I am not adding any files to the dump, simply removing the cyberon stuff (and removing the microsoft callbacks, and sqm stuff)
Tried buling without removing sqm stuff and same thing.
I guess its just not going to be my thing

Here's what to do.
Delete the current 84000000-os.nb file in the ROMDUMP folder, then remake it. That should solve your problem. I forgot that I had the same problem.

Ahh I will give that a go
I was hoping to pick up a half broken wizard from ebay (broken digitiser/blocked/missing case/etc) and just use it as a tester, since I get alot of people whining when I am uncontactable for 90 mins
(About the right time to fiddle, flash and reinstall stuff)

Touch Software Collaboration

I wanted to get a thread dedicated to getting the applications out of the Touch .nb, and into the Wizard - and specifically the "cube" and "touch" functionality that is the trademark of the new phone.
Please save "oh, I'd like" or "oh, wow" stuff for other threads - this is a dev discussion.
Criteria: Working discussions on what's been done, what are we doing, and what could be done to get the excellent new features to work.
I hope that by sharing information - we can key in on the results much faster then everyone working on their own.

Software Packages
This post is a running list of applications, and their status:
Application............. .Status:
HTC Camera ............. .???
MediaHubMini ............. .???
QuickDial ............. .???
Streaming Media ............. .???
Streaming Player ............. .???
Cube ............. .French rom working, no WWE yet
Dialer Pad ............. .Done
Comm Manager ............. .Done
Today Home Theme ............. .Done
If someone can PM me who's current on this thread, I'll update the remaining items.
.

Kickoff Status
Here's what I've tried so far:
Using the 1413 as a base, I've taken and replaced the OEM folders from the touch build and replaced the 1413 folders -completly. This resulted in the phone self power cycling at the 3rd splash screen.
I've also taken the entire touch build, replaced the ROM contents with the one from 1413 (and I might have replaced the /SYS/OS folder as well - going off memory). This was the most successful, as I was able to boot the phone and get a lot of the touch's functionality. Issues were: SID Lock error, no "touch" function, and button mapping was wrong - only button 1 showed up on settings - buttons.

More info (a little)
Well, to follow up on my note in the other thread. I did pretty much what you did and ended up in the same place.
I did discover that the two other "raw" files in the original leak contained xip contents. I'm not sure why there are two of them, and they contain similar contents. I ran a build using the one I've labeled xip1 and it gave an error about missing build.rgu in buildos. I then ran a build using the one I labeled xip here (which has a build.rgu) and it built and booted, but worked essentially the same as when using an older wizard xip.
Anyway, time for bed now.
PS I tried to upload a zip of the two xip sections but it failed. Forum maintenance I suppose. Maybe I'll try again tomorrow if anyone seems interested.
Edit: Tried again to upload, failed.

I think we should start by the Dial Pad... I think it will be the easy thing to do.
Check this Hermes Rom:
http://wmblack.info/
and this:
http://www.4winmobile.com/forums/hermes-black-rom-support/9792-released-black-iv-shadow.html

Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.

anichillus said:
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
Click to expand...
Click to collapse
I also thought this... But now we have an official build from ms... I think it is a bit more stable than a ported version (if i'm wrong, please correct me).
@joaosousa:
I tried to port the Dialpad yesterday... But it seemed that I missed some needed files/registry hacks.... Still trying.
Vi

I also think we should keep the official build from ms... It's very stable...

any luck with touch dialer skin?

In all seriousness... the Today plug-ins for the HTC touch are fricking ugly.

Anything new in here?

joaosousa said:
Anything new in here?
Click to expand...
Click to collapse
Ya... I just flashed my wizard... Without the correct XIP partition -> stuck at 87% but bootloader works... so i think i'll get my wizard back
vi

omg... Hope all goes right with your wizard...

For those who want to play...
OK, for those who want to play with the Touch Rom, here's a rapidshare link to download a "working" nk.nbf. I've also included total commander, and a registry editor for those who might want to tinker with getting things to work.
The main issues are these:
1) Pull the sim card before flashing, or you won't be able to to get to the today screen.
2) Since the elf is only a one button machine, most of the buttons do nothing, including the power button. You'll have to take out the battery to turn it off. (Unless you can figure out the registry changes needed to make it work.)
3) Don't worry about setting your timezone in the initial screen. You can set it later from the settings menu.
4) Be ready to flash back from bootloader mode when you're done exploring!
5) I pulled adobe acrobat, catalog, autoupdate. Everything else is pretty much stock. So you can get a feel for what's included, and what you might want to pull for use in the Wizard!
This is OS only.
Have fun!
Rapidshare Link: http://rapidshare.com/files/36574080/TouchROM-nk.nbf.rar

Here's a question to those who have tried it so far: has anyone seen it working, or know which application controls the 'cube' function? Is it the biotouch app?

edhaas said:
OK, for those who want to play with the Touch Rom, here's a rapidshare link to download a "working" nk.nbf. I've also included total commander, and a registry editor for those who might want to tinker with getting things to work.
The main issues are these:
1) Pull the sim card before flashing, or you won't be able to to get to the today screen.
2) Since the elf is only a one button machine, most of the buttons do nothing, including the power button. You'll have to take out the battery to turn it off. (Unless you can figure out the registry changes needed to make it work.)
3) Don't worry about setting your timezone in the initial screen. You can set it later from the settings menu.
4) Be ready to flash back from bootloader mode when you're done exploring!
5) I pulled adobe acrobat, catalog, autoupdate. Everything else is pretty much stock. So you can get a feel for what's included, and what you might want to pull for use in the Wizard!
This is OS only.
Have fun!
Rapidshare Link: http://rapidshare.com/files/36574080/TouchROM-nk.nbf.rar
Click to expand...
Click to collapse
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??

anichillus said:
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
Click to expand...
Click to collapse
Yes, understood. I think the fact that it works just as well with either XIP just shows how similar the two machines actually are. Either that, or whoever "leaked" the rom included an appropriate XIP on purpose.

its right said:
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
Click to expand...
Click to collapse
Fully Touch Rom. But it has been restructured to fit inside the partition settings of the Wizard.

mattk_r said:
Here's a question to those who have tried it so far: has anyone seen it working, or know which application controls the 'cube' function? Is it the biotouch app?
Click to expand...
Click to collapse
For me it didn't work. Did you notice a kind of "klick" every 2 - 5 seconds? it sounds like if the speaker are turnend on and off...
Vi

its right said:
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
Click to expand...
Click to collapse
The SYS and OEM folders from Touch, the ROM folder from 1413 (going off assumption here - correct me if I'm wrong )

ROM Kitchen - SYS and OEM interchangeable?

Sorry if this is another noobish question, but since I've been experimenting with cooking in the CORE Kitchen lately, I was wondering, are the files in the SYS and OEM parts of the kitchen interchangeable? I've been recently trying to use the ingenetic's rom to install the basic options that I would like (I don't use bt, so most of those features aren't needed), and noticed that some information appears to be in the SYS folder by default when dumping the rom.
an example would be something like the comm manager, which appears to already have some files in the SYS folder, but there was an htc option to click off on build os, since i think the oem package had it listed (part of the oem package download in the same thread as the kitchen). also the files for office appear to be pre-existing in the sys folder, so was wondering if the build os checkbox meant anything...
I've tried cooking roms with the options checked off and on and haven't noticed any differences, because the roms usually ended up being built and flashable, but the roms always came out screwed up. (office shortcuts would not appear, although they could be run from the \windows directory or an option to put the date information on 1 line didn't work).
I'll probably try to figure out how to use faria's kitchen and try to make the same mods, since it looks like the cookers themselves seem to have been using that kitchen for their original builds...

One thing you will find out is all the kitchens (at the lowest levels) are basically the same since they all use the same set of tools. Where the differences come is just layouts (and even then, they are still all pretty close. Core Kitchen is probably the one that is the most different, and thats just because its been laid out very logically (and not just hacked together IMO) and scripts and shortcuts setup to make it all look and feel like a nice organized set of tools. I've been using Core Kitchen mainly since Crossbow Reloaded 1.7 and I really like the layout and all. But definetly try other kitchens so you can see how they all came from the same roots (and you start to realize how this all fits together).
As for OEM and SYS... Well SYS is supposed to be what the base rom is. And OEM is the add on packages. But different cookers do things differently. I'll admit that I get sloppy sometimes and will drag stuff out of SYS and into OEM if I'm completely changing it, or sometime I edit stuff directly in SYS and maybe make rgu or initflashfile stuff for it over in OEM (so yeah, anyone dumping my roms may find some odd things in odd places. Sorry, it makes sense for me at the time I worked on it, and some of it is tricks / techniques that I've seen in Faria's stuff).
So yeah, I guess you could say OEM and SYS are interchangable. In my ROM Windows LIve stuff is in OEM since it was brought from elsewhere (but then Office was brought from elsewhere but I left it in SYS as I had issues when I tried to move it).
Good luck!

lol...coincidentally the base roms i was using look like they were from you...both your tweaked version of the base wm6 from ingenetics and xm6. maybe that's what causing all these error messages to popup when i try to buildos. says it already has files here and there.
if you have experience with core kitchen, would you know if i can still flash the file that is created, even if the error message pops up? the error that i usually get in buildos is that the file already exist elsewhere (though i need to play with a bit more to figure why, since i can't find the file in more than one location when i do a search). not sure if buildos finishes its build or it just stops (the included tutorial says to try to fix the error and not continue flashing...but just curious).
anyway, it looks like there was another version of the base ingenetics rom in the forum posting, so I'm gonna try tossing that into the core kitchen to see if i get the same errors in trying to cook it.
thx for the comments.

First of all, i want to say thanks mfrazzz for the nice words...i apreciate it !
Second ...if it gives you any error then the product is corrupted, that is very easy to understand...Because when Build OS encountered an error it stopped and won't go trough with the whole process. So if any errors, abort and check the log and fix what can be fixed.

monkey_knight said:
lol...coincidentally the base roms i was using look like they were from you...both your tweaked version of the base wm6 from ingenetics and xm6. maybe that's what causing all these error messages to popup when i try to buildos. says it already has files here and there.
Click to expand...
Click to collapse
Yeah, if it says that the file is already there, then you have to stop and find out where the duplicates are. Most likely there are files in OEM and in SYS with the same name. You then have to figure out which you want and remove the other (or rename it and then in initflashfile.txt change the name back to what you want when you move it to a different directory).
But if you get errors, (duplicate files, hive not created) or the like, you have to stop! You can't move on as things didn't complete.
If you want a clean version, then use the Ingenetics base and the packages that matt put together. Thats all made to work together. If you start with my base, then you have to keep moving forward from there, and I threw XM6 and the first version of Ingenetics together in a matter of hours so they are not laid out very well. Part of what I want to do with this next XM6 is take my time and do this one right (but I was trying to get that base out to the masses and get a better working Crossbow Reloaded 1.7 type rom on it, and wasn't thinking of people using it to start their own cooking with either of them ).

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.