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)
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
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've deleted this, because there is another thread which give you full informations and include this thread, check: http://forum.xda-developers.com/showthread.php?t=388666
please admin delete this thread
great share its right much appreciated here
rocking! thanx! I might just use this thing afterall. one question: is the size of the nb0 the same as the original 5.1 for the wizard? I found that using the 57mb nbo didn't allow me to have as much room, while not increasing storage space. I believe the original nb0 is 58.+ mb. which allows for almost 2mb more for things like live and MSVC.
Thanx for porting and posting the kitchen. if I use it for the next one the creds will for sure be yours.
Thansk a lot!
You rock Itsright!
Finally what we were expecting from your hands!
Thanks for sharing your [email protected]!
Now, let's play!
Take care!
Awesome.
Once I get to play with and test this I will consider posting my "latest and greatest"
its right said:
hi guys,
many of users asked me before to release my kitchen, then i said i will release for own using not for public, so i decided to remove all my stuff (to save my work) and share what i did for xip ported (especially) and driver modules are relocated all of these at the best ways (no hacking at all).
you will find xip folder in ROM, all of these are useless, what ever you change will not effect , so just play with OEM and SYS.
if all happy with this thing, i will continue porting and sharing.
Download: http://rapidshare.com/files/110524485/19209_Kitchen_wizard.rar
please if you want to use, give some credits.
enjoy.
Click to expand...
Click to collapse
It's Right,
Great Job!!
Now this definitely deserves a sticky guys! I will try your newest rom out and then I will look into using this for my own special brand.
Thank you so much,
Damn!
This thing is FREAKING HUGE!
I had a whole bunch of stuff that I got into the 19199 port I've been using as a base, but I got in IMMEDIATE trouble with this one as soon as I started cooking.
The 64MB wall is made out of granite, and you just can't get beyond it. Well, I've got a problem trying to stay under it now.
What accounts for these huge changes? Were the '199 version's components compressed or something where this one is not?
I don't know why the difference is so large, but it is......
Ok, I'll update that comment - There has to be some sort of duplication of files and space consumed in this one.
I stripped damn near everything I usually stick in the ROM - I mean everything - and I still wound up with a file that was too big and wouldn't flash!
I even went so far as to go back and "squeeze" things that hadn't been squeezed in the base ROM in an attempt to make it fit, and still no-go.
To give you an idea of what's in there that fails, I literally have the Kaiser Comm MAnager, a little BT utility (about 20kb), Total Commander, MMS, 1 Calc and a couple of other small apps in the ROM. It builds far too big and won't flash.
If this is the base that you're using for the TNT series there's no way in hell you could possibly get that set of apps in there unless there's just a huge amount of cruft being left in the kitchen.
Would love to work with it but can't with this as a base.... almost nothing will fit
what is the nb0 size? I use a 19209=with what used to be 57mb then used a 59mb from Faria's kitchen... i kept getting the imfg error if I added too much stuff, so I got rid of WML to make room for stuff. You can also upx the entertainmet (games) and you can change the graphics in photoshop so they take up less space.
I also had errors when I was screwing around with some reg settings... so maybe that could be an issue with some packages.
try to add one package at a time to see which package is screwing things up..
I haven't downloaded it yet. ;aybe when I get home.
I'm in a middle of flashing my first real tentative...
I was playing around and after adding my stuff, I got 61MB which is really big
I do not know about duplication but with a OS near to 60mb, maybe it's coming with most stuff inside!
I'm now trying with much less apps. Just what I consider essential. Let's see...
I also tried to dump and then repack a new NB but didn't have luck...
still on the road....
cheers
Can anybody post a mirror for this kitchen? Rapidshare being gay today.....
so I downloaded it, and have to say I don't have much use for it. maybe backup sys files in case I screw something up. the NB0 is 57mb which meand you can not cram much stuff in it. it will build, but not flash well. I would recomend using the original nb0 or Faria's 318 which is about 2 mb bigger.
S.V.I said:
so I downloaded it, and have to say I don't have much use for it. maybe backup sys files in case I screw something up. the NB0 is 57mb which meand you can not cram much stuff in it. it will build, but not flash well. I would recomend using the original nb0 or Faria's 318 which is about 2 mb bigger.
Click to expand...
Click to collapse
amm... i think the tools chefs are using are not suitable for the nb file.
amm... i will think again to release the whole kitchen i used, the nb file i edited to give the advantages of bepe tools for porting xip and locating modules without any action by the chef, just copy and past then cook with no worries about locating and porting.
if i decided to release that, i need some time to give a good guide for the chefs .
Wise man....
By doing this way, chances to have good final results increases!
Take your time!
its right said:
amm... i think the tools chefs are using are not suitable for the nb file.
amm... i will think again to release the whole kitchen i used, the nb file i edited to give the advantages of bepe tools for porting xip and locating modules without any action by the chef, just copy and past then cook with no worries about locating and porting.
if i decided to release that, i need some time to give a good guide for the chefs .
Click to expand...
Click to collapse
i will open new thread to give all details with the kitchen i'm using, but i need some time .
(EDIT: Apologies, the thread title should have stated this is relevant to the market(s))
I'm considering creating a series of applications, some of which contain a database of images thus making the final apk size quite large.
Does large file sizes for reference programs (when the user knows there will be a large amount of data involved) put them off downloading it or do people prefer having things pulled from a host? (or even having a small app size but then asking the user to install xx MB to there SD card?)
I suppose the best option would be to have an option for both.. but just want to know what other dev's have done in this situation.
(P.S - First post.. lurked here for a while but mainly been at modaco )
Whats puts me off is when I want to buy a program and I know I will not be able to test it within 15 minutes because of the extra files needed after the install.
I'm not paying for something I can't test out, blame stupid Google for their 15 minutes refund policy.
i don't really like large size file
why not pull the images from the interweb when the app opens?
Sent from my SAMSUNG-SGH-I897 using XDA App
It depends on what you mean by "large."
I don't want to spend time downloading an app that is a few hundred megs.
If it is only a few megs, I don't think of it as large though.
I'll also add that I don't want to download an app to find that I have to download more things to use it. If it is pulling data from a host, I don't want to experience any delays at all.
Thanks for the responses but I think I ended up answering my own question in the first post - have the option for both.
The best option from a dev point of view is downloading the extra files first, then the reliability and speed of hosting isn't as much of an issue as people won't need to access these on demand.
As I'm typing this post a 4th option has also become apparent - download all the text data in the beginning and for each entry you can pull the image manually.
Some of the apps are most useful on the go (Think: Wine lists/database), making using their mobile data compulsory would put people off I think.
Thanks for the advice
P.S By large I mean less than 70mb, which I'd say is quite large for a phone app)