System files - Tilt, TyTN II, MDA Vario III General

Ok, I understand that the Tilt/Kaiser/8925/etc... doesn't have an extended ROM area like the 8525 and 6700, correct?
Either way, there are "system" files I'd like to remove. (bloatware) I've tried changing the read-only and system attributes, but it does no good. Anyone have any ideas? Has anyone created an unlock yet?

http://forum.xda-developers.com/forumdisplay.php?f=378

Related

Modded Cappackage.pxp Files

So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
EDITED 12-30-2007: Note - this altered cappackage.pxp file is based off the "leaked" ATT WM6 ROM.
abs99 said:
So I thought it would be worthwhile to create a thread focusing on modified "cappackage.pxp" files. These are the files which control the default carrier specific configurations. In my case, I am running the Aussie "Three" WM6 OS, however I wanted some, but not all, of the ATT customizations. For example, I wanted the proxy tool, the logos and the certs . . . Attached is a modified version of the ATT cappackage.pxp file. I had difficulty configuring WindowsMobileLive.cab and the HTC task manager to automatically install as part of this new file so I will post those cab files as well for convenience (for those who may want it).
If you have a customized cappackage.pxp, please post it in this thread and describe how it has been modified so everyone can decide which they may want to use.
Here are the changes I made to the cappackage.pxp file. Note, all of these .cab files should be possible to install directly simply by extracting from original ATT WM6 cappackage.pxp in case you happen to need one of them:
delete getgood.cab
delete getmail.cab
delete realplayer.cab
delete getmobitv.cab
delete cmradio.cab
delete attmallandmusic.cab
delete musicid.cab
delete jarguarrm.cab
delete gettelenav.cab
alter "Att_Settings.prov.xml" to remove messaging and Windows Mobile Live registry customizations
add install of new devstate.dll (exists in 3AUS cappackage.pxp and also in ROW 2.23 cappackage.pxp)
ABS
Click to expand...
Click to collapse
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?
john_99 said:
Thanks, any idea if we can add another carrier in the carrier_db file that isn't there?
Click to expand...
Click to collapse
I honestly do not know. Sorry. You might ask Olipro as he seems to be very knowledgeable.
abs99, what tool did you use to repackage your PXP file. I've tried several archive tools to .ZIP and rename, but no joy. I've looked, but can't find any info on PXP file creation. Surely, I'm missing something simple here.
TIA
I found that "winrar" can handle the files without a problem. I had also noticed that the date stamps were the same for all the files in the original package, so I also use a tool called "stamp it" to set all the dates on all the files in the new package to the same original date.
thanks. I found that 7-zip is working too.
Now, the next step, I'm trying to mod the capdata.xml file and for whatever reason the device will not recognize it after my mods.
Here's my version of an ATT config file:
Code:
<?xml version="1.0" encoding="utf-8" ?>
- <Varnish xmlns="http://www.ephox.com/product/editliveforxml/document/Untitled20062026011007629">
<Version />
<Notes />
<UpgradePath>always|</UpgradePath>
- <PolA>
- <Certificates>
<File>CingularCert.prov.xml</File>
</Certificates>
- <Certificates>
<File>Class3_PCA_G2_v2.xml</File>
</Certificates>
- <Certificates>
<File>entrust_gssl_ca.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA1024RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>RSA2048RootCA.prov.xml</File>
</Certificates>
- <Certificates>
<File>VeriSign_C3_PCA_G3v2.prov.xml</File>
</Certificates>
- <Ringtone>
<File>AT&T Tone.wav</File>
</Ringtone>
- <ProvXML>
<File>ATT_Settings.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>MSFPHeartbeat.prov.xml</File>
</ProvXML>
- <ProvXML>
<File>ResetRequired.prov.xml</File>
</ProvXML>
- <InstallApp>
<File>WindowsLive.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Theme.CAB</File>
</InstallApp>
- <InstallApp>
<File>ProxyManager.CAB</File>
</InstallApp>
- <InstallApp>
<File>ATT_Content.cab</File>
</InstallApp>
- <ExtractZip>
<From>DevState.zip</From>
<To>\Windows</To>
</ExtractZip>
</PolA>
- <Welcome>
<WaitImage>E_PolishImage.bmp</WaitImage>
</Welcome>
- <Sweatshop>
<AccountName>GEN</AccountName>
<VarnishName>ENG</VarnishName>
<BuildName>005</BuildName>
<User>[email protected]</User>
<Environment>Sweatshop QA Staging</Environment>
<CoreVersion>1.9.9</CoreVersion>
<Treo750Version>3.0.0</Treo750Version>
<DateStamp>Wed Aug 22 6:10:15 PDT 2007</DateStamp>
</Sweatshop>
</Varnish>
Any thoughts? This is just a basic mod and plan to get more detailed configs in there once I figure out what I'm doing wrong.
TIA
The issue with this file may be that editor you are using is adding "white space". I found that some editors caused this to occur. I ended up the file in notepad to avoid the problem as it was a real mess to deal with any other way. You should open the original unedited file and your new edited file in notepad and compare both. For whatever reason, the OS does not like to deal with a properly formatted .xml file!
Thanks mate, the white space and file size were the culprit. Was trying to cheat and use MS xmlnotepad - very easy to use, but it added the whitespace as it made it pretty to look at. I also was trying to cram too much into my archive; the extracted archives need to fit in the 8.4mb along with the archive itself.
Attached is a custom CapPackage.PXP with the following (based from ATT 2.25 ROW, CapPackage.PXP):
ATT Theme
Regional Settings: US, - 5 EST
ExtROM mount and rename
Custom ringtone
Custom Sounds Settings
Delete poutlook.lnk from startup
Set Hello to ATT
Disable CAB security policy
Removed all ATT applications (CV, real, win live, etc)
TODO: Incorporate RegHacks of additional settings customization and tweaks (lots of typing...), right now I install and merge the apps I want after initial setup completes.
Cheers
HOW TO
***always a good idea to backup existing files before attempting any modification***
1. mount your extended rom (search for the cabs and instructions on this site)
2. copy the CapPackage.PXP from ExtendedROM\Partition to your PC
3. extract the contents to a folder named CapPackage on your PC (any ZIP compliant archive tool will do)
4. remove/add the *signed* cab files your desire (unsigned cab files simply get passed over)
5. open capdata.xml in epcEDIT or notepad.
6. add/remove the configuration information as desired - this is where some trial and error comes in trying to determine what commands control what function.
7. ZIP (no other archive format seems to work) the CapPackage folder to CapPackage.PXP (or rename .zip to .pxp).
8. copy to ExtendedROM and hardreset.
TODO:
-Hope to be able to post a list of commands for the XML to enable configure of most if not all device "settings"
-Hope to figure out a way to get unsigned cabs to install (present workaround is a zip extract and registry commands if the app isn't too complex (e.g. lots and lots of typing required)
--Not sure yet if reg hack setting "HKLM\Security\Policies\Policies' valuename '0000101a' to dword:1" will resolve this during initial setup
Okay, after getting my questions about how this all works and saves the space on the phone, I took the plunge and upgraded from 2.23ROW to 2.25ATT. Went smooth as butter, and I have a "decrapified" phone with the official, supported ATT release (just in case I have any problems and need support).
Of course, being a hacker, now I'm totally intrigued by this cappackage customization, and want to play with it myself. So, Tim et. al., two questions:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.
microsoft word has a wonderful xml file editor. rather than try and keep everything straight in that jumbled up mess you get out of notepad or some other editor, word indents all the xml, and makes it look like it should. it was a snap to edit. I used Winrar and opened the PXP file. I never extracted the contents. Just the capdata file. I edited it, and then put the edited version back into winrar. using winrar I deleted the files I didn't want. saved the archive and moved it back to the device.
dwallersv said:
Does the capdata.xml file have to match the contents of the archive? Or, if something's missing, it's just ignored? I'd like to be able to delete some more stuff and remake the PXP file without having to hassle with the XML file and run into the problems you have (workable, but I just don't want to waste time on whitespace issues if I don't have to).
Does the carrierDB file need to stay in the extended ROM for any reason after install and setup? I'd like to archive it on my PC, and delete it from the extrom so I can use that space for general storage.
Click to expand...
Click to collapse
1. The XML will bypass anything it can't actually do.
2. I have tried it both ways and feel like I've had no issues, but I have seen some reports of strange behavior without it. I currently have it in my ExtROM since I hard reset my device often as I test apps and config settings. If you don't hard reset very often then once the device is hard reset you may delete and gain an additional 1.45mb.
The thing I intend to work on next is creating a provisioning XML to call an external XML (outside of the cappackage). I'm hoping this way I will be able to strip even more out of the cappackage (literally everything but the capdata.xml) and hav an on the fly configuration capability and call installations and configuration from the SD card. Haven't had much time to play with it though.
Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).
Hmm, I can't seem to find the original thread either. Really just registry entries, but the cab's make it easier.
See attached...
Run each in order, then soft reset
Cheers
FYI: You can use my cappackage (see pg 1) as a starting/reference point for building the extROM mount into the initial config process after hard reset...
Try this. ...............
sodak said:
Can someone help point me in the right direction to get start loading the cappackage. I can't seem to find how to mount the extended ROM. I did a search for it and everything that came up didn't explain it (or at least I didn't understand it if it did).
Click to expand...
Click to collapse
Thanks to both of you for the quick response
I don't know whether it is because of this or because of something else. But I started modding this CapPackage file, and all of a sudden my treo just started acting weird. I had to hard reset it several times throughout the day. Then I upgraded to the 2.25 WM6. And that is where **** really hit the fan (I upgraded and put my own CapPackage version in it). And after that I've had nothing but trouble. Soft resets didn't work anymore, it just crashed on the boot screen. Hard resets work, but really slow, takes about 20min. So now I'm re-upgrading to 2.25 and just leaving that CapPackage file alone for now .
The tale away message: Don mess with this unless you know what you're doing, which isn't me
-Robert

Extended ROM keeps corrupting!

I just can't seem to make an extended ROM that won't get corrupted.
As far as I can tell, I am following Faria's tutorial properly. I have tried 2 ways, and I get the same result both ways.
1. Empty out the 9b000000-Extension.nb that I extracted (5MB) and then drag & drop my own files into it using WinImage.
2. Downloaded the blank 10MB extended ROM image, then drag & drop my own files into it using WinImage.
Both ways, if I don't let the customization run, it looks fine in Total Commander. If I do a hard reset and clear everything, then let the customization run, it stops on the second CAB. I hit reset and then look at the extended_rom in Total Commander. It will now be corrupted with lots of folders with funny characters for filenames and several files missing.
I tried a 3rd way and got better results:
- Took extracted 9b000000-Extension.nb and renamed all my CABs to match the names of the existing CABs so I don't have to change config.txt. I replaced 4 of the maybe 40 files. I drag & dropped and when it asked me if I wanted to replace, I clicked "Yes".
This method gets about 90% of the way through, but locks up just the same. I hit reset, go into Total Commander, and see now the extended_rom is completely corrupt again.
I have gone through this dozens of times. I tried flashing the ext rom alone, I tried flashing it together with the OS, together with a splash screen. No better results either way. I have gone over the Faria document several times and can't see what I'm doing wrong.
No one has any jewels of wisdom for me?
did you make sure all your files are set to read only? When you drop the files I think they default to read-only turned off. I forgot this a few times when doing my extended rom and the same thing happened to me. Rightclick on the file, choose properties, check read only (you can select all files and do it in one shot).
BTW: Winimage is the only program I've found for modding that's payware, when trial period expires you have to pay, here's a freeware image editor! the only difference is that it doesn't support long filenames. Just make sure you use 8.3 filenames!
You mean set them to read-only within WinImage? For some reason I missed that, I do have them read-only as far as Explorer is concerned, but I didn't realize they need to be set to read-only within WinImage. I'll give that a shot. Thanks!

Windows directory is READ ONLY. fixable?

hello folks,
I'm running a TILT with HTC ROM.
I am trying to make some changes to system files located in the
windows directory. attributes are read only and I cannot find a
way to make changes to that. I've searched the forum but didn't
find anything. if anyone knows of a way to delete/change the read only
attribute on winmo 5 windows directory please point me in the right
direction.
thanks!
If the items you are trying to modify are built into the rom, you can see them but they can not be modified.
The items specifically i'm trying to modify are
the 0_in and 0_out files with in the windows directory
that are used for keyboard sliding sounds. i've read
previously about people using customer slide sounds
and just replacing the ones inside the directory with
the newly formed files.
I asked the question more generically incase anyone
else wanted information on the same subject for
different reasons.
update: Changed rom files!
I was doing some digging and I figured out how to
change over files that are baked onto the rom.
I did so by using Totalcommander. which is a shareware
file system. says it also has a built in reg editor
but ive yet to figure out how to open that
feature...if anyone else uses totalcommander
let me know how to start its regediting functions.
I havnet used total commander in a while, but i believe its in a directory "//" with no name.
GinjiVitis said:
The items specifically i'm trying to modify are
the 0_in and 0_out files with in the windows directory
that are used for keyboard sliding sounds. i've read
previously about people using customer slide sounds
and just replacing the ones inside the directory with
the newly formed files.
Click to expand...
Click to collapse
Two thoughts - I've got a control panel for the sliding sounds where I can change the sound associate with the slider. Is that not working?
Are you trying to replace the files using File Explorer or something like Total Commander? FE won't do it, but TC or one of the extended file explorers should. Note that you won't really be replacing a file in ROM, and if you ever delete the one you add the one in ROM will "magically" reappear.
If you want to overwrite files in the Windows directory, Resco File Explorer does this beautifully!
Fin
bump...im having trouble editing files on my phone from activesync and i want to know how i can disable the "read only" on these files...can anyone help?
Use total commander
Click on the file properties and uncheck "read only".
Edit or overwrite them

Deleting system files

Does anyone know how to delete system files out of the \windows folder? there is a bunch of junk in there and I'd like to get rid of a lot of it. I have tried using a program called total commander that you can change the file properties and it just reverts right bak... any help would be great.
C-kim-571 said:
Does anyone know how to delete system files out of the \windows folder? there is a bunch of junk in there and I'd like to get rid of a lot of it. I have tried using a program called total commander that you can change the file properties and it just reverts right bak... any help would be great.
Click to expand...
Click to collapse
Unless these were installed manually then you can't get rid of them as they are in the ROM (Read-Only Memory). The only way you can remove them is to re-flash without the files in the ROM image. Are you sure you don't need them?
rom != storage
the system files in \windows are in the os rom part which is never
something you can overwrite unless you are building a rom
freeing up space in the rom don't add space to storage
it just mean you have a device which don't use all the space
it could in the read only memory
this does not give you more space or speed up your device
unless the program is auto run and take up temp storage
and application memory
C-kim-571 said:
Does anyone know how to delete system files out of the \windows folder? there is a bunch of junk in there and I'd like to get rid of a lot of it. I have tried using a program called total commander that you can change the file properties and it just reverts right bak... any help would be great.
Click to expand...
Click to collapse
Go to Windows,tap menu,tap show all files,scroll until you find the file/s you want to delete. This is very time consuming, but if you have patience and perseverence give it a try.

Moving icons to different folders ?

I have ATT Tilt with TPC's stocklike rom, and whenever I go into file explorer and move files in Windows/Start Menu into a different folder, such as a Start Menu subfolder, my phone seems to not understand the change in the filepath, as shortcuts and icons stop working and eventually a hard reset occurs. So I assume in order to organise my icons, I will have to edit the filepaths in registry? Could somebody please point me to where and how to do this, or to a program which will facilitate the changes I desire to make? Im sorry if its a noob question, I have looked around the registry a bit and only managed to become confused and frustrated. Any help will be greatly appreciated.
please describe your intent a bit more precisely...
what i understand is that you simply want to organize the icons/links in your start menu into subfolders...is this a correct understanding?
if so, then you must first understand that files already present in the "\Windows\Start Menu" folder are actually "links", or shortcuts. you can freely move these files into subfolders rooted at "\Windows\Start Menu".
if you are moving the actual program files that these shortcuts point to, then that will cause all sorts of problems, such as what you describe as "shortcuts and icons stop working".
so the idea is to move existing shortcut files as you see fit. if one or more programs/applications don't appear in the start menu, first create a shortcut file to the said applications. leave the application files where they are and place the newly created shortcut in the "\Windows\Start Menu" folder or one of its subfolders to your liking.
i suggest "total commander" to perform advanced file and folder manipulation. it will also allow creating shortcut files as well as editing the paths stored in shortcut files (if i remember correctly).
finally, the device should NEVER hard reset on its own, even for pretty big screw ups with moving files around. most program files will be unmovable with the regular file explorer anyway. so, the operating system effectively protects and prevents major f-ups anyway.
if you are using one of TPC's WM6.5.x ROMs, you will read in the FAQs for nearly all WM6.5.x ROMs that the ONLY known and reported reason for the device to hard reset on its own when using one of these ROMs is if you did not flash a "stock ROM" first before flashing said ROM.
hope this helps...
Thanks a whole bunch!!
Moving my icons into subfolders was exactly what I was talking about. I hahd thought that that rom was the one 6.5 rom that you didnt have to flash stock first, but I was wrong. Flashed stock then flashed back to the rom & radio and it worked like a charm. Cant believe I missed such a simple step, but definitely a big thanks for your help and knowledge!!

Categories

Resources