how can i modify registry keys such as htccpl in any rom kitchen? possible at all? or are they always related to the htccpl.cpl in the windows folder? how to modify that one then?
i just can't modify or delete them in neokit.
cheers.
chriskay said:
how can i modify registry keys such as htccpl in any rom kitchen? possible at all? or are they always related to the htccpl.cpl in the windows folder? how to modify that one then?
i just can't modify or delete them in neokit.
cheers.
Click to expand...
Click to collapse
Some in reg, some in provxml Check your PM for more detail, friend !
yeah, thanks, mate! i found all entries i need in those provxml files! great stuff!!
now i am almost done with all modifications reverting everything back to "original".
any ideas how to change "hidden" status of a single file? i want to make the templates for notes and office visible.
cheers!
chriskay said:
yeah, thanks, mate! i found all entries i need in those provxml files! great stuff!!
now i am almost done with all modifications reverting everything back to "original".
any ideas how to change "hidden" status of a single file? i want to make the templates for notes and office visible.
cheers!
Click to expand...
Click to collapse
I'm not sure what you are talking about, but I do like the word "original".... If you are done, is it worth sharing?
well, as i stated in cloudyfa's thread, i am not a friend of too heavily customized roms even though most of them look pretty cool. everyone is individual and has a different taste. therefore i really liked korand's contribution. unfortunately there were still some minor flaws, such as an incorrect wm6 sound scheme (as i believe), which i could not figure out to fix.
but with cloudyfa's rom providing wpa2 and showing no signs of bugs so far, i just could not resist making my own close-to-originally-offical wm6.1 rom, because no-one seemed to respond to my appeal of making a truely clean version. so i took the challenge myself... and it was quite some lesson and a lot of fun, however, i still do not consider myself a rom cook (yet).
and "yes", i will share it if cloudyfa does not mind and if i will not encounter any problems while testing my "creation" at the moment. i only need to figure something out about user customization. maybe you have an idea since i could not find anything specific on my question:
if uc is enabled, will it still be possible to run autorun from extended rom even though it would be redundant? because there is still the registry key set for autorun destination on extended rom. or can i delete it? or should i leave it for some kind of "dual autorun mode" ?
cheerio.
chriskay said:
well, as i stated in cloudyfa's thread, i am not a friend of too heavily customized roms even though most of them look pretty cool. everyone is individual and has a different taste. therefore i really liked korand's contribution. unfortunately there were still some minor flaws, such as an incorrect wm6 sound scheme (as i believe), which i could not figure out to fix.
but with cloudyfa's rom providing wpa2 and showing no signs of bugs so far, i just could not resist making my own close-to-originally-offical wm6.1 rom, because no-one seemed to respond to my appeal of making a truely clean version. so i took the challenge myself... and it was quite some lesson and a lot of fun, however, i still do not consider myself a rom cook (yet).
and "yes", i will share it if cloudyda does not mind and if i will not encounter any problems while testing my "creation" at the moment. i only need to figure something out about user customization. maybe you have an idea since i could not find anything specific on my question:
if uc is enabled, will it still be possible to run autorun from extended rom even though it would be redundant? because there is still the registry key set for autorun destination on extended rom. or can i delete it? or should i leave it for some kind of "dual autorun mode" ?
cheerio.
Click to expand...
Click to collapse
yups, you can still run some application from extende rom.
At windows folder, you will find config.txt . You have to give some command on it.
The command there, is just a RST ( Reset ) . But If you give a command first, it will install some cabs. It all command from AutoRun
This is some command
LOCK: Enable
CAB: \Extended_ROM\TCPMP.CAB
CAB: \Extended_ROM\Cabs\ABCD.CAB
LOCK: Disabled
RST: Reset
the command will install TCPMP.cab and ABCD.cab
share at XDA is always a good one.
With Cloudyfas ROM, there is a provxml file that sets the keys for AutoRun to somewhere in the windows directory. You will have to remove/alter that for autorun from the storage card.
The point of AutoRun is to allow you to install cabs etc before the user can really use the ROM. UC is to provide users with a faster way to set up the ROM. The two can and should co exist.
so if i got it correctly: putting the common command lines of the extended rom autorun PLUS the command lines of sdautorun into this single config.txt file would make the device boot and install from both locations one by one?
so, what are your recommendations about the registry key:
[HKEY_LOCAL_MACHINE\Comm]
"TurnRadioFlag"=dword:0
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
leave it or kill it??
edit: decided to remove it due to its complete redundancy. it is uc already... now i am close to finishing.
edited edit: put it back in. i think it won't hurt and maybe someone still needs it.
cheerio.
One of Cloudyfas ProvXML files overwrites that, so it is completely redundant!
It's called mxipupdate_zz_oemoperators_102_CheckAutorun.provxml
You can look at it and see what it does.
The two AutoRun files (SDConfig.txt and Config.txt) are separate files that run independently. The point of UC is User Customization. All you need to do is make sure SDAutoRun.exe is in \Windows and that the last line of your config.txt file is
Code:
EXEC:\Windows\SDAutoRun.exe
That is all that is needed for it to run.
ok. removed the redundant entries. i was just thinking there might be some way of a "dual boot". but actually this is rubbish. so i leave it as uc as it is.
The point of UC is that the two are seperate. Everything can be achieved with just one of the two systems, but with UC, you (the chef) can install cabs, and the user can install tweaks etc.
Related
Well, there you have it... that's the question, and the answer is obvious.
However, the caveat is not...
Does AEButton save your changes to the registry, or to a DLL?
Can someone tell me how I would go about cooking my personalizations into my ROM?
yes, you need to get the OEM package for it though. I have a lot of packages, but no aebutton.
you can one of two things....
1. learn how to create your own packages. there are a few tutorals here on xda.
2. send me the app and seriall number for activation and I will put one together for ya.
email is codyppc at gmail dot com
Cody,
thanks for answering, but i think you misunderstood...
I need some help figuring out how to make an OEM that will also set up all of my current button associations. I'm not sure if there's a DLL I need to pull off my phone and overwrite in the cab, or if there are registry entries I need to add to an RGU... I'm hoping someone has that info.
Any help?
badutahboy said:
Cody,
thanks for answering, but i think you misunderstood...
I need some help figuring out how to make an OEM that will also set up all of my current button associations. I'm not sure if there's a DLL I need to pull off my phone and overwrite in the cab, or if there are registry entries I need to add to an RGU... I'm hoping someone has that info.
Any help?
Click to expand...
Click to collapse
The easy way to find your answer is to use a registry compare program... Export your current registry, then change all the button assignments you want changed and then export the registry again. have the program compare the 2..... here's the registry program that I use to compare with... works great.... You should see the differences real easy if they are saved in the registry.....
azclown said:
The easy way to find your answer is to use a registry compare program... Export your current registry, then change all the button assignments you want changed and then export the registry again. have the program compare the 2..... here's the registry program that I use to compare with... works great.... You should see the differences real easy if they are saved in the registry.....
Click to expand...
Click to collapse
Thanks. I'll give your program a try.. I've been using windiff, and haven't been able to decipher the gobbledy-gook to figure out which registry entries are changed.
Here is a working AEButtons Plus OEM.
once you try user customization, you will love the flexibility in it. If a new program comes out, you can just uninstall your current version. Or, when you reflash you can just edit your SDconfig.txt
When you cook programs into the rom, you are stuck with that version
1999TL said:
once you try user customization, you will love the flexibility in it. If a new program comes out, you can just uninstall your current version. Or, when you reflash you can just edit your SDconfig.txt
When you cook programs into the rom, you are stuck with that version
Click to expand...
Click to collapse
Can you tell me how to set up AE button with user customization?
LOL. I forgot about that. yOu have to use the hide and unhide function in UC. It is posted in the UC thread. I'm laughing b/c i just remembered AE button plus gave me the hardest time at first, until I found out about the hide and unhide.
When you install AE button plus, it pulls you up to the program menu screen. That will just freeze User customization. So you have to be in unlock mode. I actually just install AE button plus and .net 3.5 upon start of UC, then I lock the phone and let it do the rest.
AE Button Plus stores its config in AEBPlus.cfg. This stores the button config as well as your registration data. That file needs to be in the same directory the rest of your AE Button plus files are.
EDIT: I have attached the OEM I use for mine. It has my AEBPlus.cfg in it which you will want to overwrite with yours. Otherwise, you will have my config as well as my serial # which is only good for my device.
Thanks guys! you're all awesome.. thanks for the help..
I'm going to try to cook AE into my next rom.. with that success, I think I'm only 1-2 steps away from having PERFECTION on my phone... haha
Now introducing... the HyperCore Athena ROM Kitchen!
First, though, props to anchillus and his HyperCore kitchen. I took it, and made a few small modifications so that it's built for the Athena instead.
Feature Highlight:
Since this is a full-blown ROM kitchen, you can tweak your own ROM however you like. You can do anything that you've seen other people do with their ROMs! All that customizability is at your disposal.
Prepopulated with Windows Mobile 6.1 from the HTC Diamond (5.2.19915).
Prepopulated with applications from the HTC X7501, HTC X7510, and HTC Diamond.
Pictures are not being posted because you already know what Windows Mobile looks like - it's up to you to make it look pretty.
Installation:
Unzip. The "Core" folder goes in as C:\Core. The "HyperCore" folder can go wherever you like; the default HyperCore installer puts it on your desktop.
If you're on SPL 1.2, you'll need to copy an SPL 1.2 OS.nb on top of HyperCore\Build\ROM\OS.nb.
Instructions:
If you want to get your hands dirty right away without reading through the HyperCore instructions, here's the extremely quick version (if you already know how to handle a ROM kitchen):
Make changes in HyperCore\Build. SYS contains the base Windows Mobile 6.1 files, while OEM contains folders that HTC or you provide.
Once you've tweaked SYS and OEM to your heart's content, under HyperCore\Panel\Build, run BuildOS. You'll need to run [1] and [2] to build OS.nb in HyperCore\Build, and then [3] to convert OS.nb to RUU_signed.nbh.
Flash your ROM onto your phone.
...
...
Profit! (j/k)
If you encounter the endless customization loop problem, edit HyperCore\Build\OEM\OEM_Lang_0409\initflashfiles.dat, then find and remove the section for AutoRun.
Known issues/concerns:
The XIP is the XIP from AP 5.0 beta (build 19588.1.1.4, which was from the Sony X1 Xperia ROM). I've tried to generate a matching XIP for the ROM, but it won't boot. Anybody around here know how to create a good XIP?
There seem to be some issues with the Bluetooth OBEX service not being able to start. That's true of this ROM as well. It's able to send files to a PC without a problem, but it can't receive files (although it can copy them).
Even though screen rotation works both in the operating system and in HTC Album, HTC Album's screen rotation has the chance to screw up the operating system's screen rotation. A workaround is to use an application that can restart services (such as the FdcSoft Task Manager) to restart HTC Sensor Service (Athena).
Although the phone skin does work on 128 and 96 dpi, the speed dial application can act flaky and start drawing itself off-screen, which can trigger an error. One workaround is to dial a single number, then rotate the screen, which forces a redraw, after which it functions properly.
The VGA HTC Home plugin could be in slightly better shape. The TabSetting registry entry doesn't seem to work (or at least nobody's responded to me here yet), and the Profile tab shows a keyboard vibration option that, naturally, doesn't work.
The enlarged start menu has some icon overlap on 128 dpi.
The nifty System Status popup on 96 dpi seems to trigger just to the left of the connectivity indicator, while not triggering on the connectivity or signal strength indicators. It does work, just a little strangely on the other dpi settings.
Sym-A now generates the _ character instead of the $ character.
During phone calls, the number keypad is active instead of the alphabetic keyboard.
NOTE:
Much as with Athena Project Kitchen, this ROM kitchen is not to be used for releasing ROMs. It's for personal use only. We really don't need twenty-billion ROMs flooding this forum from everybody who wants that one little tweak.
Exceptions can be made for people who have demonstrated a solid history of producing ROMs. Ask if you feel like you have a strong case for why your ROMs need this kitchen. The current exception list: irus.
Download links:
Megaupload
RapidShare
Other file sharing site suggestions welcome.
Fixes/patches:
Attached to this post. Replace:
HyperCore\Tools\RUU\Athena_RUU.exe with the one from Athena_RUU.zip
Core\ACK\Settings.txt (Updated: July 20, 2008)
I'll be adding additional information to the next few posts over the next several days as time permits (and questions pop up).
P.S. The restriction about personal use isn't about elitism. It's about keeping the forum organized. I just don't want to see every other thread in the forum being a ROM release thread, and there's no reason to make sergiopi's job harder by making him keep track of dozens of minimally different ROMs.
Additional OEMs
NOTE: If you're add OEM packages with modules, you will want to run G'Reloc in your HyperCore\Build directory before you run BuildOS.
HTC EzInput 1.5.31226.0/HTC XT9 1.5.31232.0:
A keyboard designed for use with fingers. There are two large button keyboards (portrait and landscape versions), along with a phone keypad keyboard. The portrait/landscape keyboards swap automatically with the screen orientation. Only works properly in 192 dpi.
Megaupload
HTC LongPressEndKey 1.1.33562.2:
A nifty quick menu program that provides a number of convenient functions. A little less useful on the Athena due to, well, the lack of an end key, but potentially useful regardless. Not tested in other resolutions yet, but likely only works properly in 192 dpi.
Megaupload
Microsoft .NET Compact Framework 3.5.7283.00:
Required for running .NET Compact Framework programs. Meant to replace SYS\NetCF.
Megaupload
WkTask 1.1.7.3c:
A task manager that alters the taskbar to function more like that in traditional Windows, in addition to providing a battery bar and task launcher.
Megaupload
If you would like to change your extended ROM to add packages there for automated installation upon hard reset, you can use the extended ROM editor. You can then convert that with Dutty's NBH tool (available in the kitchen in HyperCore\Tools\Convert) and reflash.
Kitchen Tweaks/Suggestions
Additional OEM Packages:
It's quite possible to find OEM packages out there for quite a bit of software, in order to save yourself time in making your own. If you can't find one, though, there are a number of links on how to assemble your own OEM package - for example, there's a wiki article about making your own OEM package, which also has a bunch of links to existing OEM packages. Just be aware that most of the OEM packages you'll find out there are designed for 96 dpi, and thus may not work on the Athena the way you might expect - the Spb applications are a pretty good example of these, as they come with separate VGA resources.
Package Recommendations:
If you're going to make registry changes, it's usually a good idea to make a custom EM package to contain them. I would recommend using the UUID ffffffff-ffff-ffff-ffff-ffffffffffff, as that will force it to be the last registry file processed (ensuring that your registry entries "win" over those in any other OEM packages).
Package Dependencies:
PACKAGE_Diamond_Album_HTC_ALL can't function properly without PACKAGE_Diamond_HTCGesture, PACKAGE_Diamond_SensorSDK, and X7510_GSensor
PACKAGE_Diamond_VolumeControl depends upon resources in Diamond_LargeTitleBar
RealVGA_DPI_96 depends upon the *_DPI_96 directories in SYS
RealVGA_DPI_128 depends upon the *_DPI_128 directories in SYS
X7510_AudioManager refers to X7510_AudioBooster (menu option)
X7510_TouchFlo depends upon PACKAGE_Diamond_SmartTouch
PROVXML Changes:
If you want to change how your ROM thinks of itself, change HyperCore\Build\OEM\OEMVERSION\mxipupdate_OEMVERSION_100.provxml. ROMVersion is currently set to "Athena_6.1", but feel free to change that to whatever you like.
Registry Changes:
Here's a starter list of potential registry changes.
Code:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Cache"="\MicroDrive\Internet Explorer\Cache"
"History"="\MicroDrive\Internet Explorer\History"
Move your Pocket IE cache and history to your MicroDrive.
Code:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"MaxConnectionsPerServer"=dword:00000008
Increase the number of simultaneous connections Pocket IE makes to servers to 8.
Code:
[HKLM\Comm\Security\LASSD\AE\{50C13377-C66D-400C-889E-C316FC4AB374}]
"AEFrequencyType"=dword:00000002
Prevent Windows Mobile from screen-locking while plugged in.
Code:
[HKLM\Software\Microsoft\Internet Explorer\Navigation]
"4-Way Nav"=dword:00000000
Have Pocket IE-based widgets scroll by screen, not by link.
Code:
[HKLM\Software\Microsoft\Today\Items\"Wireless"]
"Flags"=dword:00000000
"Options"=dword:00000000
"DLL"="netui.dll"
"Order"=dword:00000000
"Enabled"=dword:00000001
"Type"=dword:00000004
Enable the Today Screen Wireless plugin.
Code:
[HKLM\System\CurrentControlSet\Control\Power]
"WakeupPowerOff"=dword:0000003c
Go back to sleep faster when auto-waking (60 seconds).
Code:
[HKLM\System\GDI\GLYPHCACHE]
"limit"=dword:00008000
Increase the graphical caching. A good size has not yet been determined, although this is the value often recommended for QVGA devices (a VGA device likely needs more).
Code:
[HKLM\System\GDI\SYSFNT]
"CS"=dword:00001000
Increase font caching.
Code:
[HKLM\System\GWE]
"Animate"=dword:00000000
Disable window animation.
Code:
[HKLM\System\GWE\Menu]
"AniType"=dword:00000000
Disable Start Menu animation.
Kitchen History
To be filled in.
Good work!
But...the xip version is after 5.2.thisisxipver and system build is there (Build xxxxx.x.x.x)
You have got a little error
michyprima said:
Good work!
But...the xip version is after 5.2.thisisxipver and system build is there (Build xxxxx.x.x.x)
You have got a little error
Click to expand...
Click to collapse
That's the thing, though - it doesn't matter much to me that it displays the XIP/system version there. Now, if other people care enough to go and change that, it's entirely up to them.
Sogarth said:
That's the thing, though - it doesn't matter much to me that it displays the XIP/system version there. Now, if other people care enough to go and change that, it's entirely up to them.
Click to expand...
Click to collapse
okey...
But...i have my kitchen because previously there arent one...
I can download it for oem packages...
XIP and SYS porting Guide
http://forum.xda-developers.com/showthread.php?t=379598
Here a tutorial and many info... from ababrekar, witha a pictorial guided step by step to download
Sogarth,
Thanks for introducing this kitchen
When I unzipped the download, I had more than 4000 error displayed. Could I ignore them?
Also, you mentioned that for spl1.2, I need to replace the os.nb in the HyperCore\Build\ROM\ directory. But I found that directory to be empty to start with. Is there supposed to be an spl3.5 os.nb there already?
Is this base ROM the same as the one we have been testing in the base wm6.1 thread?
sergiopi said:
http://forum.xda-developers.com/showthread.php?t=379598
Here a tutorial and many info... from ababrekar, witha a pictorial guided step by step to download
Click to expand...
Click to collapse
xipport is old...i use dump rom and build xip by bepe... + ervius pkgtools&buildos
been waiting for a good kitchen for ages. thanks a lot. what build is actually included?
rory
Nice job sogarth, I was looking foward to this all week. i will be giving this a try today
eaglesteve said:
Sogarth,
Thanks for introducing this kitchen
When I unzipped the download, I had more than 4000 error displayed. Could I ignore them?
Also, you mentioned that for spl1.2, I need to replace the os.nb in the HyperCore\Build\ROM\ directory. But I found that directory to be empty to start with. Is there supposed to be an spl3.5 os.nb there already?
Is this base ROM the same as the one we have been testing in the base wm6.1 thread?
Click to expand...
Click to collapse
i am having the same problem is anyone else having this problem
irus said:
i am having the same problem is anyone else having this problem
Click to expand...
Click to collapse
Yep , same here!
michyprima said:
xipport is old...i use dump rom and build xip by bepe... + ervius pkgtools&buildos
Click to expand...
Click to collapse
That's exactly why I haven't linked the first post only but the THREAD address, 24 pages of Q&A, links and files
I have the same problems with sogarth kitchen, the file could be corrupted
Blah. I guess that's what I get for using 7-zip + .zip + BZIP to try and keep everything uber-small. I'll rezip everything and re-upload. *sigh*
works for me if you open in the latest 7zip beta proper, rather than right click and extract here.
Sogarth said:
Blah. I guess that's what I get for using 7-zip + .zip + BZIP to try and keep everything uber-small. I'll rezip everything and re-upload. *sigh*
Click to expand...
Click to collapse
Megaupload kitchen re-uploaded. Rapidshare kitchen in progress.
fards said:
works for me if you open in the latest 7zip beta proper, rather than right click and extract here.
Click to expand...
Click to collapse
I'm pretty sure it works for 7-zip - I think it just doesn't work for non-7-zip .zip supporting programs.
Sogarth said:
I'm pretty sure it works for 7-zip - I think it just doesn't work for non-7-zip .zip supporting programs.
Click to expand...
Click to collapse
well it's about time they started using proper software then
Okay I have flashed my telus titan many times using the usb method and the flash card method (prefered) now I would like to learn the kitchen method, which I understand I can modify to include the programs I have to load after I do the flash. I get the buildnb and then selecting the programs I like, what I would like to know is if I want to add my tomtom 7 to the build is this possible. plus some other games that I have. What folder to I add these files to? If there is already a discussion about this could you send me a link.
Cheers
I'm not sure how buildnb works, but I'm more familiar with BuildOS from ppckitchen.org and with that, all you do is copy the stuff you find into a folder and BuildOS loads it in as part of it's stuff you can pick from. I would give it a try and see if it's better/worse/indifferent for you. And the guys at ppcgeeks.com are always posting stuff about the kitchen and custom roms. I don't see much here about the kitchen, it's mostly about custom roms.
jc, the kitchen is quite easy to use. But you cannot just dump programs into it and have them available to select from buildnb. The programs that you have will most likely be in the form of a cab. For use in a kitchen the programs need to be in the form of an OEM. There are tools available to OEMize a cab. Just do a search here and you wiull find the tools you need. Then just dump the OEMs into the existing OEM folder inside the kitchen and then when you run the kitchen the programs will be there for you to select. They will install with the ROM, not after it.
You do have other options if you dont want to OEMize your cabs. You can search for Alex's OEMs at ppcgeeks. There are hundreds of premade OEMs for you to select from.
Another alternative is to keep your cabs and just use UC to automatically install them immediately after you install your new rom. This is the preferred method for most of us now as it leads to less problems and allows for programs to be uninstalled at a later date which OEMs will not allow.
Sleuth255 has an excellent tutorial about how to automatically install all your favorite cabs using UC. Search for it and you wont go wrong.
All you need to do is find OEM packages for the programs you want. If you use DCD's kitchen just add them to the OEM folder. If you use PPC Kitchen just add them to the User OEM folder. Then just select them once you run Build OS.
I'm not sure how buildnb works, but I'm more familiar with BuildOS from ppckitchen.org and with that, all you do is copy the stuff you find into a folder and BuildOS loads it in as part of it's stuff you can pick from. I would give it a try and see if it's better/worse/indifferent for you. And the guys at ppcgeeks.com are always posting stuff about the kitchen and custom roms. I don't see much here about the kitchen, it's mostly about custom roms.
Click to expand...
Click to collapse
Hate to break it to you, but this uses BuildOS too, just a different version. Buildnb is just a batch file that g'reloc's and calls BuildOS among other things after BuildOS is run.
I'm trying to learn this stuff too.
Here's some of the stuff that I've found:
OEM Tutorial Thread:
http://forum.xda-developers.com/showthread.php?t=347361
there's more links at the bottom of the 1st post in the thread
Here's the link to packages - say for Kaiser - So I don't know if they can be used on Titan? Anyone knowledgeable please chime in.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_software_recs
??? All the links on Alex's thread seem to be Kaiser based - how much of this is applicable to the Titan and/or other devices?
I agree that ppcgeeks is a good resource too.
DCD's kitchens seems to be fairly easy to do a build. I'm still learning what I want, which versions to include, what everything that's there does, etc...
In theory it seems simple, I'm not finding the learning curve to be all that easy though. A lot of trial and error. But that's part of the challenge, I suppose.
It would be nice if the people with a lot of experience would chime in with tips, links, and comments that would help gather the information into one place for those of us that are learning - maybe I need to go hunt through the wiki's some more, IDK. But sometimes it seems the more threads I read the more confused I get.
My opinion to all of you...and again..this is just MY opinion...take it or leave it...
Build the rom using the kitchen as is with no added personal OEM's. Install all programs/applications/tweaks after flashing either manually, or much easier by UC.
I've converted a few so far, and they haven't turned back. OEM's can be so messy, and can be a HUGE pain in the ass if you need to uninstall/troubleshoot any problems.
My advice would be to read the entire thread on UC, as well as the threads in the Titan Upgrading forum pertaining to UC (I know I've talked about it quite a bit, as well as many others).
Sound good to me. I'm not one who likes to reinvent the wheel if I don't have to, but I am willing to go through a little extra pain to get what I want. If I can get the same results through UC vs. OEM'ing CABs, I'm game. The OEM'ing of CABs so far for me has been a real pain in the arse.
I will do some more reading on UC since I haven't totally gotten the results from that yet that I want. I'm sure my minor problem with the UC cfg file is not unique.
What about adding some of the nueTools into the DCD roms? Reading the text in the included files - some of them can only be rom'd like the ext'd rom utility. Looking that over, I haven't figured out, with any reasonable confidence, how to add this to DCD's roms. I have searched some, but not extensively on this one yet.
Since i'm not going to cook just yet for the Pro, nor am i helping out any specific crew Over At the Pro (SPC crew will come over to Pro someday anyway).
I have decided to make a OEMMORT Packages Repository.
For those that want to cook with the utmost optimized packages for their Pro.
OEM PACKS
To use these Optimized Packages to Cook (specifically with Touch Pro In Mind), you always need the the MortScript Base.
So if you use more or less packages the RFO.mscr & CLASC.mscr need to be adjusted appropriately to correspond with the correct File Operations.
Mort Script 4.112.b7
AdobePDF_2_5_103401_01
IA_ZIP_1_21_18171328_1
More coming eventually.
Explanations
If you do see the Logic and and improvements this adds to cooking control and performance enhancement, then don't forget to mention the SPC-MORT-COOKING Style, Wax in Wax Out
Any Comments, Opinions, Ideas or Questions welcome.
TNX to the rest of the bengalih for some pointers & SPC crew for testing and helping out.
And thanx of course to MORT.
Don't Know MortScript? Shame on you. (neither do i)
Donny Bahama's easy to carry Mortscript Manual in HTML:
http://forum.xda-developers.com/atta...9&d=1214102654
excellent stuff
Hi Noonski... Very interesting concept.. Great Works! Cheerz..
would it be possible to put the cab files from UC all into 1 zip file to save space ?
da_jojo said:
would it be possible to put the cab files from UC all into 1 zip file to save space ?
Click to expand...
Click to collapse
ExactMundo.
If you'd make the cab files into OEM packages first.
I have a WNDWS.zip
PRGF.ZIP
and a MYDOCS.zip
But even that would not be needed as one zip file should be able to do it.
As long as the Makedir command is used in a Mortscript before the Zip is extracted for folders that do not exist unless you have the complete folder structure in the zip files.
Unless you mean the Cabs from the UC on your SD card.
But even then you could also only extract just a cab at a time.
So i'm not sure you meant the ROM Autorun Cabs or the SD UC cabs?
Also unzipping the files instead of having them in Rom, or making the links with a script removes that darned ROM Read File Protection.
yes yes yes that is what i mean exactly my friend
i mean both ... it would save space on the storagecard as well as remove this freaking writeprotect on the dirs. dir structure in the zip file would be the best option i think as it copies 1 on 1 without setting userrights.
this writeprotect option is set on a hidden part of the systemflashdrive. in the mft i think. strange thing is that i got acces to my windows folder through activesync and it doesnt work on vista mobile device center.. frankly i have no idea what i did but it seems something in the pc as it works on my xp machine and not on vista. i didnt change anything yet on the phone itself relating to this.
pocketcommander www.totalcommander.com is able to ignore or overwrite the writeprotected files in windows dir so there must be a sollution to this.
i dont have the proper tools to do all this stuff but it would be the fastest way to extract all files from all cabs one need into one zip file and let mortscript handle the unpacking and settings of the registry. this way theres no need for autorun cabs merely the UC SD installer. maybe someone can make an nice logo for the custom uc installer.
da_jojo said:
yes yes yes that is what i mean exactly my friend
i mean both ... it would save space on the storagecard as well as remove this freaking writeprotect on the dirs. dir structure in the zip file would be the best option i think as it copies 1 on 1 without setting userrights.
this writeprotect option is set on a hidden part of the systemflashdrive. in the mft i think. strange thing is that i got acces to my windows folder through activesync and it doesnt work on vista mobile device center.. frankly i have no idea what i did but it seems something in the pc as it works on my xp machine and not on vista. i didnt change anything yet on the phone itself relating to this.
pocketcommander www.totalcommander.com is able to ignore or overwrite the writeprotected files in windows dir so there must be a sollution to this.
i dont have the proper tools to do all this stuff but it would be the fastest way to extract all files from all cabs one need into one zip file and let mortscript handle the unpacking and settings of the registry. this way theres no need for autorun cabs merely the UC SD installer. maybe someone can make an nice logo for the custom uc installer.
Click to expand...
Click to collapse
I think for that for the SD Autorun UC solutions there are already a few good solutions around some even supporting Mortscript.
And they all are pretty user friendly to.
Depending on what a user wants and knows, using mortscript being cooked in just gives them more freedom to play around customizing a cooked rom.
But it would need more hand work using your method, but it is possible of course.
It boils down to, do you like making Mortscripts to change registry settings or do you prefer making PROVXML files?
And not everyone is into decompiling cab files to make them fit their exact requirements.
But there's only one rule, Copy the Script to device memory and a folder name tat does not contain a space in it's path. And then run the script.
As the Exec: command from autorun doesn't like that.
But mostly the main way i use it is for the Cooked Autorun part.
I control when the Welcome wizard is run, Before Autorun or after the boot.
I can remove the extra parts of the Networkwizardauto.exe files and also run the networkwizard when i want during the process.
All i need to ad to my process is to open the Locale Preferences dialog during this process and then finish it of with Syncrotime. (or asking for the choice if you want threaded SMS on or not, the possibilities are plenty)
Put all the Setting up your device options after each other for those users that don't have the know how of how to use UC to setup their personal settings.
I even delete the back up files for the one App that i only get installed correctly through a cab file
DelTree( "\Windows\AppMgr\SRS Labs SRS WOW HD" )
So i hope that those that cook or customize and want even more control and detail into what happens can appreciate this.
I know i'll keep using this, and adjusting all my OEM packages to it. Because i have experienced the overall speed improvements in the Rom because of it.
I'm not a Pro in Mortscript and myself i only use the fairly simple commands.
i see.. thnx for explaning
it would be far simpeler using the xmlprov
unless one requires the extra functionality of mort script
the SRS wow HD is a driver enhancement so it needs the system to detach the driver which is only possible with the installer . hence cab files work good cause the're installed by the windowsinstaller which can temp disable the driver.
Instead of MortScript, there is a Yonsm's CeleCmd that perform roughly the same thing.
Check it out!
http://www.yonsm.net/read.php?329
V
vibranze said:
Instead of MortScript, there is a Yonsm's CeleCmd that perform roughly the same thing.
Check it out!
http://www.yonsm.net/read.php?329
V
Click to expand...
Click to collapse
Hey Vibranze, Long time no See.
Would you mind translating
Mort has a bigger fanbase here on XDA.
Yeah, long time no see How are you?
I really not used to your new avatar, without the cigarette it's not like you at all hehe
Actually you can try to download it and check out the sample, it's very easy to understand. I attached here for you
Anyway, here is the translated page by Google.
V
Noonski said:
Hey Vibranze, Long time no See.
Would you mind translating
Mort has a bigger fanbase here on XDA.
Click to expand...
Click to collapse
Explanations
What Does RFO.mscr do?
What Does CLASC.mscr do?
Which Packages Contain Modules and Why?
There's Files Missing from the Packages?
What Does RFO.mscr Do?
Well this script is copied to the regular Start up Folder in Windows.
I use short file names because as much as possible for anything that goes into Windows folder and have no other use being in the Windows folder then being copied by initflashfiles to another folder.
RFO.mscr basicly is the only file i use an initflasfiles.txt for (goes to \Windows\StartUp\ReplaceFileOperations.mscr)
Because after that it takes over the File Operations of the Default build in initflashfiles method.
Why?
Well You don't need actual shortcut files present in ROM to make them.
Code:
CreateShortcut("\Windows\StartUpDisabled\btdwake.lnk","\Windows\btdwake.exe")
in the RFO i don't put that much actual File Operations.
Only the ones that might be useful.
(Why start up WiFiInit.exe during autorun, if it's only useful after the Autorun reBoot?)
Code:
CreateShortcut("\Windows\StartUp\WiFiInit.lnk","\Windows\WiFiInit.exe")
I basicly set up the Second mortscript that will run after the Autorun reboot.
And i make sure the script is not to short. A script that is to short might actually copy the second script so fast into the autorun folder that it will actually be run immediately at during Autorun.
And i make sure the script deletes itself
Code:
RegDeleteKey( "HKLM" , "Services\SqmUpload" , TRUE , TRUE )
RegDelete( "HKLM" , "init" , "Launch99" )
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "system", FALSE)
CreateShortcut("\Windows\StartUp\WiFiInit.lnk","\Windows\WiFiInit.exe")
Copy( "\Windows\CLASC.mscr", "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
Delete( "\Windows\StartUp\ReplaceFileOperations.mscr" )
So you can choose during which Boot you want to do what.
But it's better to do it after the first Reboot in case there is no Autorun installation and the phone reboots before finishing the RFO script.
So the Yummy goes to the CLASC.mscr.
What Does CLASC.mscr Do?
Well this does the actuall JuJu...
It takes over the Job of AutoAttribute.exe, so that can be kicked out of the Rom.
Code:
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "system", FALSE)
It Takes over the Job of AutoShortcut.exe and initflashfiles.
(less autoshortcut.provxml files in the final rom for the people to lazy to put these into a .rgu file for correct cleanliness)
Also Autoshortcut.exe is set up to run and check the regsitry at every Boot up, so out with this nonsense.
Code:
MkDir("\Windows\Start Menu\Programs\Office")
CreateShortcut("\Windows\Start Menu\Programs\Office\Adobe Reader.lnk","\Windows\AdobeReaderLE.exe")
And eventually it run some Post Stuff to make setting up the device easier at first boot.
Code:
Run("\Windows\ConnectionSetup.exe")
Delete( "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
Message("Thank you for installing A SPC Optimized Rom. ","Installation Finished")
Also sometimes people encounter a registry setting that does not get applied directly because of .rgu or .provxml conflict.
So instead of making a new EXTRA .provxml file to fix this.
The registry setting can be added to a file that is already there.
Code:
RegWriteString ("HKLM", "Software\Microsoft\MediaPlayer\Skins", "DefaultPortraitSkin", "\Storage Card\My Documents\Windows Media Skins\Mono SPC\portrait-htc-touch.skn")
RegWriteString ("HKLM", "Software\Microsoft\MediaPlayer\Skins", "DefaultLandscapeSkin", "\Storage Card\My Documents\Windows Media Skins\Mono SPC\landscape-htc-touch.skn")
Or create a new start up script that runs at every start up when you have these annoying Registry settings that for some reason like to reset to a specific default value.
Code:
WriteFile("\Windows\StartUp\FixRightSFTKey.mscr", 'RegWriteString("HKCU", "Software\Microsoft\Today\Keys\113", "Open", "\Windows\Submenus\Contacts.mbi")^NL^RegWriteString("HKCU", "Software\Microsoft\Today\Keys\113", "Default", "Contacts")')
Less headaches going trough all the files finding the conflicts, as you now have a sure fire hit to get the registry right.
And we all know that eventually you will stumble upon the rgu or provxml file that is causing Havoc. But at least you don't have to stay awake pounding your head to find them.
Which Packages Contain Modules and Why?
Well the ones that do have Modules instead of regular files most propalby..
Work as a Module.
Show improved starting up of the application
Can be made into a module to start with (not all files like this)
Show improved handling speed or usage performance.
So when you do find Modulated files in the packages, these have been tested and found worth modulating.
These days most of the kitchen's have G'Reloc.exe build into the cooking process.
So the chance of Modules overlapping a specific memory allocation/space is fixed.
Some kitchens also offer this functionality to Make Modules of files.
But in some Junior Cheffs cases, that usually will result in (nice term coming) OverModulating.
If the kitchen you are using does not run G'Reloc.exe automatically please do so manually when cooking packages with modules.
I have tried making some OEMs myself from Cabs (with some success).
I was wondering 2 things.
Does anyone know of anywhere that OEMs are downloadable. I am looking for programs like:
S2P
S2V
S2U2
TouchFlo
iContact
LiveSearch
Opera Mini
Mortscript
Weather Panel
Today Agenda
UL
I am thinking that my problems stem from the final stage
"The next window that appears, known as the 'initflashfiles tab' is for executable and help file links. Select which files you want your links and the folders to place them. Select and apply for each link and when finished, click done to proceed."
Can anyone explain this a little clearer? Do I actually have to do anything in this screen? I would love to be able to cook my own ROMS to make it easier to get my phone where I want it after a hard reset.
Also does anyone know if you can alter the OEMs and cook them. For example, could I replace the default themes in Weather Panel with the Diamond ones so that I do not have to copy from the card when resetting?
Sorry for all the questions but I recently did my first flash and now have the bug and it takes me ages to install everything every time i do it.
I get all mines from ppcgeeks some work with dcd some don't.
I use the UC option in the kitchen and use the OEMizer to create the info for it to install the CABs you want. They must be on your SD Card but it works great. It will also copy files from the SD Card to Main Memory as well. It is supposed to be able to make registry changes to but I never got that to work with just editing the provisional.xml file. OEMizer is great for several settings any ways and you will have your own personal OEM to put in the kitchen to bake.
PPC GEEKS oem.rar for the easy out way or if you are into learnning any of it oemizer works pretty good to.
I have use some on this post.
He does take request.
http://forum.ppcgeeks.com/showthread.php?t=25696
Wow, thanks for that last one, I will post some of my requests on there as well. Can't wait to get cooking!
Here are some I have made......