Related
I had a hard time to upgrade and modify my xda2 so I decided to make a small tutorial for everyone with the information’s I found on the forum. It’s not perfect but it could help.
Thank's to every one who made all this possible!!
Before starting I recommend every one to make a back-up of your rom
http://forum.xda-developers.com/viewtopic.php?t=4608
1- Extended Rom:
Your XDA2 has an Invisible Extended Rom in the device containing the operator’s configuration files and software.
Modifying it will allow you to customize the boot image and to choose the programs you wish to install during the setup of the device.
To show the extended rom on your device your need to apply this small hack and then open your file explorer:
http://www.ppcw.net/index.php?itemid=1638
2- Files contained in the Extend Rom:
Broadcast_WWE.sa.CAB:
Seems to only set the CellBroadcast setting to enabled or disabled. (I guess this refers to the Reception of News via SMS by selecting channels of interested. Quite expensive I think and only interesting for phones that do not have any other capabilities of receiving and displaying information).
T-Mobile NL sets it on, with O2 it's switched off.
CallerIDRC11_WWE_1.5.sa.CAB:
Installs the CallerID application from IA Style and the Photo Contacts extension. There are other programs that are able to provide this functionality but I use it.
CameraRC131_WWE_1.5.sa.CAB:
The camera application for taking pictures and recording videos. AFAIK there is currently no alternative to this one, you should leave it in your ROM.
GPRSMonitor_WWE.sa.CAB:
Includes the GPRS Monitor from SPB Soft. Very useful I would recommend it unless you aren't going to use GPRS anyway.
MIDI56.sa.CAB:
RingTone plugin player. Allow you to play back RingTones in the following formats: mid,3gp,mp4. Also seems to register the audio/midi MIME type for playback of midi files directly from Internet Explorer.
By default the XDA can play back only wav and wma audio files (AFAIK)
MMS1507_WWE.sa.CAB:
Installs the Arcsoft MMS application for composing and sending MMS messages.
VideoMMS.sa.CAB (not contained in Qtek):
Installs the "Video MMS.exe" file into the Windows folder. When you start it you are in camera mode immediately and after you have recorded a picture or video you get into MMS composition mode.
This seems to be just an easier way to compose MMS messages since the main MMS Application (see above) is already able to compose MMS messages.
OEM_AKU1_WWE_4AP.sa.CAB (named OEM_4AP_WWE.CAB in Qtek ROM)
Installs the following files: GPRSAuthentication.exe, BTSetting.exe, STK.exe and WModem.exe
I am not sure if these are customized versions or if the normal ROM doesn't contain them. Well perhaps not because these are specific to the Phone edition so they can't be present in the main ROM, maybe they are contained in the Radio ROM, but probably they are only contained here, meaning you shouldn't remove this cab file.
OEM_WWE_03120301.sa.CAB (named OEM_WWE_03122301.sa.CAB in Qtek ROM)
Installs files for Bluetooth: AudioGW.dll, BthASPlugIn.dll, rilgsm.dll, Serial3.dll and Wavedev.dll. Also contains the new feature of mapping a (dynamic) serial port for BT.
I think you should not remove it.
TM_phone_class10.CAB (not contained in Qtek):
Installs several registry settings regarding phone functionality. (See my other post regarding this topic: http://forum.xda-developers.com/viewtopic.php?t=5539)
TMCOMREG.sa.CAB (not contained in Qtek):
Contains some of the settings contained in the previous one anyway. I'm not sure if it does anything else but I don't think so.
TMD_AP_NL.sa.CAB (not contained in Qtek):
Implements several settings specific to T-Mobile (NL): Restricts video types for MMS. Adds connection and gateway settings for MMS connection via T-Mobile NL. Adds a T-Mobile profile to GPRS Monitor.
I would not install this cab unless you live in NL!
TMD_NL.sa.CAB (not contained in Qtek):
Sets the HKEY_LOCAL_MACHINE\SOFTWARE\OEM\3rdversion\MSYSTEM1 value to the provider name.
Not required!
TMDNLCustomize.sa.CAB (not contained in Qtek):
Adjusts all the "theming" stuff: Changes colors, installs Today-theme, installs T-Mobile Dialpad, sets T-Mobile ringtone.
If you don't like you xda2 look like a pink pig you should leave this out.
(You can extract single items from the cab file if you like)
t-mobile_shortcuts_only(UK).PPC2002_ARM.CAB (not contained in Qtek):
Contains some strange things that seem to me rather useless: "WebDisplayText t-zones", "T-Mobile Resetter.exe", "T-Mobile PIE Launcher.exe", "TMobileWebToday.dll", "T-Mobile Homepage Plugin".
I wouldn't install this one!
Version_AKU1.sa.CAB (Version_AKU1_160.sa.CAB in Qtek):
Seems to only set the version number of the extended ROM in the registry.
3- Modifying and editing your Extended Rom:
Most of the latest XDA2 have a write protected Extended Rom
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
or
http://www.clubimate.com/Support/ruu113sku1.zip
2) Simply unpack the complete T-Mobile Rom update file (it's a zipped EXE) into a folder.
There you will find these 6 files:
- HimaClearJumpCode.exe
- HimaGetDeviceData.exe
- HimaUpgradeUt.exe
- ms_.nbf <----- this is the file which holds Ext Rom!
- NK.nbf (main rom)
- Radio_.nbf (radio rom)
3) Delete the other *.nbf files to prevent updating the full XDA2/MDA2 rom. You only need "ms_.nbf" and the "*.exe" files!
4) Now modify the ms_.nbf with the tool softworkz kindly provided.
http://wiki.xda-developers.com/wiki/ER2003Edit
5) After this, install the modified ext-rom to your XDA2/MDA2 by starting "HimaUpgradeUt.exe" and follow the instructions!
6) If you get a country code error during the install you will need to modify the country code included in the ms_.nbf file
- Download xda2nbftool
http://forum.xda-developers.com/viewtopic.php?t=5563
- Put xda2nbftool.exe in the same folder as your ms_.nbf file
- Run xda2nbftool.exe from Command Prompt and type the following command
xda2nbftool.exe -so O2 -v ms_.nbf
Replace O2 by your operator’s name (ex: orange, O2 etc)
It should now work!
cheers,
Yann
nice one Yann
Thanks
I had a go at doing the "if your extended rom is protected"
I down loaded the file
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
and accidentally ran it.... I know I was stupid... I now have an I-Mate instead of a XDA - O2. Please help can I get the O2 back is there a programme that does the same as the one I just have used. It has changed every thing the radio stack, the other bits of software, I am just pleased it still works of calls.
I couldn’t find the indivuiual HimaUpgradeUt.exe programme any ware.
Please help I am really stuck at the minute!!
The bit I didn’t understand was the bit about unpack the exe. Which I now understand how to do. Although I have upgraded to Rom 1.52.00wwe, radio version 1.06.01, I can haply say I have the original O2 rom back in place with additional programmes installed in the Ex-Rom. I had a fair bit of space so I popped some music files in as well!!!!
Thanks for all the help!!!!
thanks yann for the perfect summary
as newby i needed something clear like this to dare my first rom changes, and i successfully did!
it would be even more perfect if also somehow the program settings/passwords could be cooked in/restored from the extended rom. i searched the forum but could not find any hints.
Are there methods for this ?
Perhaps a silly question, but I'm fairly conservative when it comes to messing around with my device.
How do you find out or know if your Ext ROM is write protected or not? I know that I can add applications to my Ext ROM and it does not seem like I should be able to do that if it's write protected, but then again I'm not sure if this matters.
Ed
ed, if you can copy files to your ext-rom via activesync, it is per definition not write-protected.
your not that conservative, because you already run a tool or edited the registry to be able to see the ext-rom
ronald,
Well I guess you are right I do like to play around, as I get more comfortable doing so. It is this Forum, guys like you, and some other forums that have made this possible for me to do. For some reason I'm more comfortable in general hacking around a desktop pc than a PPC.
I thought my Ext ROM must not be write protected. When I deleted the TMD files, described here as useless, I got the message that they were read only, but they did go away from the Ext ROM Folder. I do not notice a big difference, however, nor did it free up that much memory. I was thinking that I might need to do more then this. Do I?
So basically, if my Ext ROM is not right protected, and I have been already loading programs into the Ext ROM, I’m pretty much at the place people are trying to get with the Ext ROM Cook ER...Edit. Is that correct or am I missing something here?
Ed
Ed,
I do not like flashing rom (or bios) on either my desktop or PDA (if not absolute sure to fix bugs). However flashing the PDA's ext-rom can basically not screw up the PDA because you don't touch the OS, so I flashed the ext-rom to get familiar with the PDA flashing in general (and also to have a restore of my standard used software after a hard-reset).
About your ext-rom; I do not recognise your situation. I would say if it is read-only the file will not disappear (like with my PDA).
I did notice while editing the ext-rom file for flashing that the file is fixed ~16MB, regardless of which cab's are included or deleted.
Maybe this is the same effect that you see when deleting the file in the ext-rom ???????? (although I can imagine both effects have no relation)
ronald
Camera Programs
Okay,
I made a custom ROM with the following programs:
CAB: \Extended_ROM\CameraRC131_WWE_1.5.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MMS1507_WWE.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_WWE.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
Awesome, alot less bloat, but.... Camera doesn't work.. Application says Camera is not a valid Pocket PC application. :: grumble ::
Did I miss something?? Camera.exe is there, but doesn't work
Brandon
My Ext ROM is not write protected, and I'm able to run applications in the EXT ROM Folder. I deleted the 2 TMD and the T-Mobile cab files, but I have not nticed a big difference, nor is my GPRS back to always on, which it should be now.
Perhaps the device requires another hard reset without these cab files in place prior to the changes taking actual effect. Does anyone know if my assumption is accurate about the required hard reset?
Ed
what dictates if the ExtROM is write protected or not? is it the version? or the hardware itself? or a mix of the version with the OS checks?
cuz i believe the ROM version is dictated by the version_AKU1.sa.cab. does that mean we can hack the cab (or use a diff version) to disable the write protection?
i'm using a himalaya btw.
I have a question or two.
I'd also like to know if it is possible to modify CAB files so they install an application and then also put in your purchased key or serial depending on the application so it's already registered to yourself. It seems like it must be possible because the GPRS Monitor on the T-Mobile Extended ROM is already Registered when you try and register it yet I was under the impression it normally has to have a key entered to turn it into the full version with no limits.
This would be great if this was possible, if it's a key file then it's simple to copy it over but how about automatic registry entries? Are these done similar to Windows .reg files? Does anyone have any info if a .reg file can be make and run from the Extended ROM to make changes to the registry? This would also allow me to key in a few other things I'd like presetup.
Is there a way to see what registry changes a CAB file makes other than from purchasing MagicCAB? Is there a free program like this? It seems like a reasonable program from the info but I don't want to spend 10 dollars on a program I might only use once or twice.
Acutally, one more while I'm here. Does anyone have a CAB installation version of CabInstl which puts a shortcut in the Programs or an easy way for me to make that? I've set it up so it will copy the EXE in manually along with a shortcut but I've yet to try it. I think it should work OK I imagine, just might be neater and have an uninstall if it's in a CAB format?
Can you delete files from the extended ROM script? Just so I can clear out a few folders of things I don't want in there when I do a hard reset?
Thanks for all your help. I'm looking forward to making a super kick ass Extended ROM for myself, I'm half way there
Updating the indirect way
Had a few problems with the updating process... and thought i would explain how I got around them!
First I updated to the standard 16007DE ROM
Then I installed the Extended Rom Viewer, and then because it is protected, i copied the contents to my HDD.
Then i tried to open the Rom update from T-mobile with the Extended ROM editor, but kept on getting file access errors The only one i could open was the NL 13006 version. So I changed the splash screen, deleted the origianl contents, and then inserted the contents from my updated original Extended ROM, as well as a few other bits that i could find, IE the extended ROM viewer. It is updating at the moment, So I hope it all works.
I have a few questions though!
Does anyone know a way in which I can automatically install a few themes, and a few ringtones? I have a few MIDI files that i want to be installed into the windows\rings folder, and the themes need to go in a folder called themes in My Documents. I also wanted to ask if there is a way to extract the CAB from another program, for instance Voice Commander. It is an MSI, but only works in windows!!!
Any help would be greatly appreciated...
Greets from Hannover, Germany
Juggs :?
Is this going to work:
- Download ER2003Edit
- Download the O2 XDA2 ROM 1.60.50
- Download the T-Mobile MDA2 ROM 1.60.36
- Remove O2 apps i don't want to use
- Add applications from T-mobile rom which i want to use
- Change ROM provider from O2 rom to to T-Mobile
- Save new O2 ROM and upgrade
But... I want to add custom ring tones to contacts, and if possible also want to add custom picture. Also my camera must be able to work. Which software do i need for this?
Because.. All i want to upgrade is today theme to O2's and also the software to 1.60.50... Does the O2 rom also has an "TMDNLCustomize.sa.CAB" ?
Greek full support language for qtek 2020
Hello,
this is a very intresting site!
Can anyone tell me is exist & where can i dinf an extended rom for qtek 2020 with full support of greek language?
Also there any newer version than the 1.66.00 wwe extended1.66.130 radio 1.10.00 wihich my qtek 2020 has??
best regards
george
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
Click to expand...
Click to collapse
2 questions for you,
1. how do i know whether my rom is the editable 1 or the non editable one?
2. I tried option A, just mergly adding the CAB files into the EXTROM but... when the hard reset was perform it did not install the CAB files i added in? what could be the prob i know there is a "autorun.exe" in it but i dunno whether will it affect the process. I also notice a "config.txt" in the extrom, tried editing it but it seems that nothing happen
Reason for adding the cab files is because i was using a 1.72.00 rom with radio stack 1.12 but intend to change it to radio stack 1.14 and also try cooking up my own rom in the ktchen but after doin so its like nothing happen. need some advice for cooking roms in the kitchen been searching the forum... found a few but its all talking about Linux platform.
Hi Kelvin,
1)
The way to know if your rom is not writ protected is if you see a folder called extended_rom in the root of XDAII and if you can add files in it.
If not, there’s a nice tool to make the extended_rom visible and to make it writable.
http://forum.xda-developers.com/viewtopic.php?t=8422&highlight=extended+rom+hide
2) The config.txt is made to lunch the programs in the extended rom when you hard reset the XDA or when it starts for the first time.
You just need to put the cab files in your extended_rom folder and edit the config.txt this way:
Exemple:
I added the cab file vxIPConfig.ppc3_arm.CAB in the folder extended_rom
and added this line in config.txt
CAB: \Extended_ROM\vxIPConfig.ppc3_arm.CAB
Cheers,
Yann
hi yann,
i tried doing that way as i figured out that config is like a startup "prg" to actually start the programs installing when hard reset is performed. But the thing is i cannot make the programs i added in the install after the hard reset is perform. I don't know why but the rest of the cab files can be done. Do adding of all this cab files into the ROM consider cooking ROM??? not really fimilar with the terms of cooking ROM unless that is the way.
A better way (??)
Why would one want to do this?
1. Extended ROM is (as ITSME has pointed out) a Disk on Chip.
1a. It is totally lockable/unlockable -- and can be deleted/added to if one wants to, as long as one understands a few basic things.
2. When the device is hard resetted, after booting is complete, one automatically runs the CAB files in Extended ROM that "localize" the device in accordance with the Carrier's wishes. This is a good thing, and a bad thing... especially if the SW they install is Caller ID, for example, that eats memory and battery performance. But it is a needed thing for the most part in my opinion.
BUT.....
What if you could do the following:
1. Delete your entire extended Rom (ITSME has shown this to be possible)
2. Take the extended ROM files "as is" from all of the carriers out there -- kind of like ala carte menu choices -- and place them somewhere where upon your choosing, could be installed immediately at one's whim (even with the same parameters and running as if they were still came from the Extended ROM)
3. Never have to worry about flashing your device again, unless there is a significant OS reason to do so.
4. Forget using tools one doesn't need to use.
5. Tweaking a config.txt file -- why bother if ya don't have to.
Sound Good????
In my opinion, the only real reason we have many people out there playing around with flashing ROMS is that they want a "perfectly customized device" every time they hard reset. The REAL, Operating System upgrades and Radio stack upgrades are not needed as often and people are willing to wait until their device OEM gets around to the upgrading themselves.
Bottom line: Hard Reset, install your own programs to your liking, and have your device almost as if you never resetted it up and running in a matter of minutes (2 or 3, not 30) with no risk at all to your ROMS.
If this is what people REALLY would rather have, instead of flashing extended ROMS and risking killing their machines....
In a day or two, I will have a (very) little app made that can do this, and show you the "secret" (though I think this is not a secret -- but could be wrong) do doing this.
This post is sent out to "test the water" on this app/solution I will provide.
((no charge))
Feel free to comment, so I can see if people want it or not -- so I will know if to bother making (have made) /telling how to do this.
Plus, also feel free to comment if my thinking here is completely from Mars
Excellent idea. Just a simple list of cab files with location, check box to select and parameters if required is all thats needed inmo. You could then store the cab where you want, SD or Extrom, and then after a hard reset just run the app to execute the select cab's
Can't wait, certainly prevent all those deep despare moments when it doesn't go smoothly and you think you've trashed you device !!!
Victor...
Give us the application then....
Smiles.
got to have it made first....
Ok, here is the deal: I don't have time today to test all of the in's and out's of this -- but by leveraging the power of this forum, I think it will quickly be all figured out and expanded upon.
1. Most people don't know that if you place a directory called "2577" on an SD Card and place in it a file called "Autorun.exe", the file will run when you place the card in the slot of your device. This works for smartphones, XDA2's and Ipaq's (so I am guessing that it is a WIN CE thing).
2. If you could develop an app whose sole purpose was to execute the cab files in the directory (easy to make, for a dev), you could autoload apps at will.
This means that after a hard reset, if your Ext ROM was empty, you could basically mimmick the loading of the stuff when and how you want to -- without cooking an External ROM.
This leaves tons of possibilities
1. using the EXT ROM area for storage that will not go away on Hard Resets and is larger than the normal persistent storage on our devices.
2. using the EXT ROM area for "private storage" that can be hidden with ITSME's tools.
3. using the SD Card to not only load your preferred files, but also (if someone is really clever and can figure this out) your connection settings and what ever other REG settings you feel like.
I HAVE FOUND ONE "CATCH" HERE...
The autorun.exe will execute upon card removal too, so one will have to probably rename the file while in the device or the directory name to "2577XX" so it will not run again.
if you let your mind wander a bit -- the possibilities are endless here
but again, I have not tested out all of the possibilities nor tested it for problem situations -- so that is where the power of the forum comes in. Seems easy to experiment without nuke-ing your device.
I am going to erase my EXT ROM, make my own version of what I want on the SD card, and use the EXT ROM for storing stuff I don't want to lose ever.
By all means... comment, take this idea and run with it.
I am going to have a little app made that will run all cabs in the 2577 directory in a few days -- but I am dependent upon a DEV resource so the delivery time of this "5 minute application" is not 100% known.
Enjoy!!
It's a great idea. I do like it very much. I will try to play with the concept. But, let me ask you where to get 'Autorun.exe' and comand line for this program.
Thanks,
Ah! I think I understand now. "Autorun.exe" can be any executable program, just name it "Autorun.exe". Right?
It work like a charm. I copy a program "Autoconfig.exe" and rename it to "Autorun.exe". Then move it to dir "2577". When I insert SD card into the socket, it stand still, nothing happen. But when I turn off and then on, it execute the said program. Then I Off and On for second time, it won't execute, which is correct. It will execute the program again if I take the SD out from the socket.
I can then play a lot of things with it.
Thanks, Victor
you are right.. any EXE program can be renamed autorunexe. I have not got all the permutations worked out yet as to what can or cannot be done yet, but if time allows I will do more research.
I am expecting my little EXE to be finished today, where it's sole purpose will be to run all CAB files in the directory.
When done, then I will post it here.
If anyone has ideas as to how to re-do the connections / reg settings and place them in a CAB file, like the OEMs do, then you can comletely customize evrything at will, with a power-on.
For portugal here are the configs, in a .cab for each portughese mobile operator.
These were made by www.qtek.com.pt
http://www.enev.pt/ppcforum/index.php?act=ST&f=37&t=1492&s=2a02c5df8d4b65cf66ca27e0aadc4817
(portughese language forum, but if interested in any info send me a PM)
how autorun works
when you insert the sdcard the autorun.exe is copied to \windows, and executed as '\windows\autorun.exe install'
when you remove the sdcard, '\windows\autorun.exe uninstall' is executed, and then autorun.exe is deleted from \windows.
So then, in theory, if you manually delete this file before removing the SD card -- it would not run again then, right?
Trying to think of ways to automate the entire Hard Reset issue -- select your Extended ROM programs / settings you want -- and then plug and play. Changing EXT ROMS made to be as simple as selecting which SD card to install after Hard Reset.
Plus, if the last thing you did before the Hard Reset was to perform a backup to a secure area (like the now empty EXT ROM area), you could also have the autorun program look for the back up and do a restore. May be easier than trying to place all settings into CABS and you benefit from having your data again after a Hard Reset -- all in a few sinple steps.
That is the whole purpose of my activities / efforts here. I hard reset at least 2 times a week (I have special reasons for this).
obviously -- some of the ideas presented up to now are simply brainstorming the possibilities. hope to come up with the right and complete idea soon and have it made here. Then post it here for all.
hey,
i want to remove the pre installed programs (like O2 Media plus...)
how to i "edit" the rom? so after HR, it wont be installed automatically?
actually, cab must be located in the "hidden" partition
how do i enter to hidden partition?
i entered the hidden storage,
buy i dont see there all the o2 programs... where are they?
again, i am searching for the installation files,
so when i will delete them,
a HR wont installed them..
If possible, I would suggest a hardreset. After the hardreset, you will came to small window saying that some software will be installed in 3...2...1 seconds (e.g. the screen you see just after the security option setup after the hardreset). When you see this screen (you have 3 seconds to re-act), soft reset the unit. Now, your unit will be customization free (e.g no customized software installed).
As you said you have already entered the EXT Rom, you can now choose which software you would like to install. If you don't know what they heck they are, just install it and see if there is any difference. Worse case, hardreset your unit again, take a bit of trial and error.
i dont see the 3 2 1 window
are you sure it is on the atom? i hear it on the jam, akaWM2003... and in WM5 it isn't...
The Software in the O2 Atom is in the ROM itself.
therefore you can not remote all of the O2 software....
Nadavi. 8)
Hi brothers
Its not good to enter hidden partetion,
I did all these things too... I also wanted to install some programs to main memory, but main memory is very small in atom it just 43 mb storage.
so i unlocked hidden partetion and delete all inside hidden part...
the result is camera and media plus, fm radio skins are corupted.
then i tried without delete anything, there left some space about 9mb,
And also camera getting problems....
So its better to leaave all in main memory, if you dont want see preinstall programs, enter windows directory start menu througj file explora and delete shortcuts.
Its good idea to by 2gb mini sd and have fun with free space
thank you. hope these information helps you.
hey,
i agree with you 100%,
but the reason i want to uninstall them, is not to save space (i already have the 2gb card). i simply dont want the progams on my device... each of the programs adds a little something to the registry, and god know where else..
Is there a good Samaritan out there who can explain to me exactly how the program is installed and how does one go about editing the Registry of the TyTN. I have bought Nokia HS-12W BT stereo phones and have added in Sleuth's anti-skip modification. All works well except that I do not get stereo. I must modify the Registry according to Sleuth's working model, and need to do the Registry mods.
Please help!
I am sure there are other newbie's who are also keen to learn new tricks.
Which problem are you exactly having? Just install the cab file, run the program and browse the registry to the place you want to modify, add or delete a key. Tap on the key or screen to do this.
You have to copy the cab file to your Hermes first. When I install cabs, I either send them to myself as email attachments or I use activesync explorer mode. Alternatively, if you can find the site using Pocket Internet Explorer (PIE) then you can download the cab directly. Once the cab is on your Hermes, then tap to install.
There is an alternative way to install apps on WM and that's with a windows based installer. If the file isn't a cab, then you'll need to connect up your hermes with its USB cable, wait for activesync to connect then run the installer on your PC. The installer itself will send the cab file over for immediate installation.
If you're familiar with the Windows registry you'll have no problems understanding the WM registry. When you change a value, make sure you power off with the power button to reset & make the change active, otherwise your registry setting might not "stick". Some registry values take effect immediately but I always power cycle after making a change just to be sure.
Installing PHMRegEdit
Hi
Could you please attache the CAB file.
I have load the file and the file is PHMRegEdit.msi
Thanks
I was wondering "which" .cab to copy over for the AT&T Tilt 8925. I did try the Stngr_ARM and it did install. However, I can not expand the registery top folders or export the registery.
Thank you in advance
OK, figured it out.
regedit.Mrln_ARM
did the trick
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.