I need a few volunteers to test out a new kitchen setup for the new 318 rom that was just released.
It has massive room for additional programs to be installed - possibly greater than the 1413 build. See this post for what I got to fit.
It still needs the comm manager fixed - as it has the 8 button that just came out that doesn't have all the setting options. I may just go back to the 10 button for now.
Let me know and i'll PM you the link. I don't want to release this until a few others have tried it.
link please
okay, thanks to eveyrone who PM'd me. I'll reply with the download link shortly.
FYI I reverted it back to the 10 button black comm manager. Future cookers can do whatever they want.
whoo! Matt I just paid 99 bucks for a 8525! lol.
Madcap180 said:
whoo! Matt I just paid 99 bucks for a 8525! lol.
Click to expand...
Click to collapse
Nice!
I'm afraid to look at them, since I think I finally have this one "just right".
psh I didnt care, I went to cingular website and saw a refurbished one for 99 bucks and said to my newphew 'u need a cell phone? and added a line to my plan.. ahha.
Sorry guys, my wifi died at the end of the upload. I'm reloading from my desktop, not too much longer...
I swapped the comm manager back to the 10 button, but I didn't get all registry settings in. Here's the .rgu - please replace the one under /SYS/Custom Tweaks...
Okay, PM's sent. Whoohoo!
I missed one more reg setting - the .rgu should take care of it now. See post 8
Here's the last release of Live from mUn's base...
edited....
Having Audio Manager and WMP together (is looks like anyway) is causing a conflict. When you try and select a ring tone, it won't close, won't play, and from then on the phone won't open. Removing Audio Manager and trying again...
Edit: No luck. Something else is preventing the the phone settings from changing/playing ringtones. Going back to the basics...
Replaced the phone set from a working build, testing now...
Implus refuses to build, even if it's the only thing checked in the kitchen, it kicks out the following error:
Implus 4.35 Error, last status: "Processing: OEM\IM_PPC"
The file 'temp\dump\Setup.dll' already exists.
check your SYS or OEM folder for that duplicate file
That occurs when a file already exists is another package
raventec said:
Implus refuses to build, even if it's the only thing checked in the kitchen, it kicks out the following error:
Implus 4.35 Error, last status: "Processing: OEM\IM_PPC"
The file 'temp\dump\Setup.dll' already exists.
Click to expand...
Click to collapse
Not sure who offered that package up, I never tried to use it.
I'll just pull it from the final package.
Thanks
Edit: unless there's an easy fix
There's a setup.dll in the SYS\1-Calc folder, it's not a show stopper anyhow
instead of ringing, my phone vibrates instead even though I haven't set it to vibrate. Must be related to the phone problem you posted earlier.
raventec said:
There's a setup.dll in the SYS\1-Calc folder, it's not a show stopper anyhow
instead of ringing, my phone vibrates instead even though I haven't set it to vibrate. Must be related to the phone problem you posted earlier.
Click to expand...
Click to collapse
I'm gonna flash with no OEM packs, and if that doesn't fly, bring back over my older 318 /SYS components until I find the offending part. The ones I would have assumed causing the issue didn't pan out.
Running out of steam, might have to crash for a few...
Edit: Not the OEM packs, it's gotta be the SYS/ROM. Probably a corruption from the decompile of the original rom. Now the fun begins...
Edit: Getting warmer, it's somewhere between .ROM and OEMAPPS...
Edit: Between FWUPDATE and NetCF, not including Metadata...
Edit: Missing dll in MediaOS called xmeevtsnd.dll. very, very strange... final fix test flashing now... *yawn*
Edit: That was it!
It's too bad there's not good (if any) error checking when dumping ROM's I can see that being a bugger. Don't forget to sleep sometime
Noticed one small thing, PocketRAR shows up in both programs and programs/accessories. easy enough to fix, just listing it for completeness.
This ROM flies!
FIX: Here's the dll folder that needs to go into /SYS/MediaOS.
Testing the duplicate RAR entry now.
Related
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)
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 )
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
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.
When I put m2d onto my elfin, I had no problems, except when i go to the weather tab. It simply says "unable to retrieve data for selected city" even though I didnt select one and i cant click on "add location" in the menu.
Any ideas of how I can get around this and actually add a location?
cris_rowlands said:
When I put m2d onto my elfin, I had no problems, except when i go to the weather tab. It simply says "unable to retrieve data for selected city" even though I didnt select one and i cant click on "add location" in the menu.
Any ideas of how I can get around this and actually add a location?
Click to expand...
Click to collapse
What version of m2d do u use? do u have custom cities added?
Im not sure what version of M2D it is, because it was included in the ROM that I put on. It was THIS ROM.
I have tried with and without custom cities.
As well as the manilla2d.exe that comes with the custom cities fix,
but it crashed whenever I went onto the weather tab ¬_¬ when using the custom fix .exe
Can I assume that you read this ?
http://forum.xda-developers.com/showthread.php?t=439399
Yes Ive tried that out.
But im not trying to add a custom place to the list, im just trying to choose a place from the list to begin with.
Cris,
Have you checked out the Rom thread to see if its a rom issue, or pm the chef for advice. Might be worth trying a reflash though.
not being able to use the weather is a small thing, but its annoyed me enough that im giving in. im gonna do a hard reset and then if that doesnt work, ill re-flash.
lol, ok let me know how you got on
Well, Ive done a hard reset as I said I would.
It worked fine.
But then, being the ideot that I am, I mucked it up again
I tried what is on THIS thread, which is a tut on how to add custom locations.
When I tried it out, it said it couldnt download the information for this location, and It also wont let me remove the location, or add another.
If i use the manilla.exe from the thread I linked to, it just closes M2D whenever i open the weather page & just goes to "tap here to start manilla 2D"
Ultimately what I want to know, is where is the information stored that tells M2D which locations are actually being used? If i could edit this, I wouldnt have to hard reset again, or loose the weather function.
Did you just edit the xml file or go the whole hog as per scotchua's thread?
i only edited the xml.
plus, removing my custom location didnt help either.
cris_rowlands said:
i only edited the xml.
plus, removing my custom location didnt help either.
Click to expand...
Click to collapse
Ok give me your location, and ill edit the xml file for you. Then you can just use t.c as usual to overwrite. Is the weather with normal cities working now at the moment?
well, i have got it working, as of about 5am this morning.
and ive also found that the settings of what locations are to be user are in the registry at:
HKEY_LOCAL_MACHINE>software>htc>manilla2d>weather:
then its goes into folders counting up in numbers for the different locations you use :3
Nice one Cris, give urself a pat on the back
*pats self on back*
*slaps self round the face*
now, whenever i go onto the messaging tab, M2D freezes and I have to soft reset my elf ¬_¬
WILL THERE EVER BE A TIME WHEN MY PHONE WORKS ENTIRELY??
:'(
lol man thats heavy, have you altered anyhting else at all, any manila files? play with the reg? Have you posted anything in that particular rom section?
sadly the ROMs creator doesnt reply much, and everyone else simply comments on things they want from the creator ¬_¬
and the only things ive changed is add a custom location to the weather, chance the location of a couple of images on the home tab (the clock basically) ive edited which tabs are enabled or disabled..
plus ive played about with the image files :/
ive edited some of them, or used files from other themes and copied them across to the windows directory using total commander, because manilla 2d customizer never works on my phone, no matter what rom im using (another problem :/ )
but yeh, when i searched for any issues other people have had with the messages tab crashing, the only thing i read about was someone who had trouble copying the files. and ive had an error at one point.
(i have re-coppied my haxord image files across withe no problem since mind)
so yeh, im a bit lost as to what it could be
mmm werid man... i hate saying it, but you considered flashing a different rom? Kinda defeatist (which is why i hate sayin it) but i cant understand what your doing wrong (if anything)
thing is, i dont really look through my texts that much, so having it disabled isnt a big loss. I might remove the email tab too, as thats prety much unused too.
it just would have been nice for it to work
plus, its so satisfying scrolling across when you have more tabs :3
also, i must add that im not gonna change this ROM for AGES :O
its the quickest ROM i have ever used, and ive used plenty
plus, i had been trying to create a theme and then i randomly came across this ROM and saw in the screenshots, the exact image of what i wanted my theme to be like, so stopped making the theme and downloaded the rom.
now my phone is made of sexy
>