Related
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
I had asked a while ago about some devs making a unifed method of storing the config of their apps in a uniform matter for backing that info up between resets, It wasn't well received
So I then thought, well, if they couldn't/wouldn't/shouldn't do that, what if we could figure out where each app saved its config, and then backup that app by app. I also saw how AppToDate used XML files in a dir to configure how/where to update those 3rd party apps.
Therefore I wrote a backup/restore app that uses individual ini files to define what files or regkeys a specific app uses, and then copy/export that to a storage card, so that info can be restored after a hard reset or flash. The app is almost completely automatic, in that it just goes though the ini files present and backups or restores what is in the ini file. If you want another app, create a new ini. do not want an app backed up or restored, just remove or delete the ini.
Now I want to point out that this is still in development, I have little to no error checking in place, so much of my code works due to magic... (i.e., I know what goes where so I don't intentionally insert bad data and it only restores what it has copied, so the data going in, is the same as what came out).
It does work, however.
I wanted the app do do a few things:
* to run start to finish unattended... start the restore and it just runs, with no questions asked.
* the backup needs to be able to run on command from start to finish, with no questions asked. (for scheduling purposes)
* the config ini for apps need to be simple to read/edit, so user community can post/share them, or be created by the original app devs
The app is basically a few MortScripts... a backup script, a restore script, and a next to pointless menu app. I'm considering another script to enable/disable/Import specific ini files, without having to move them around manually...
The reg export/import is done with DotFred TaskManager.EXE, which is a great utility BTW. At least until I can find a better way... I keep hoping Mort will finish that regimport.exe and add export to it as well hint, hint.
just extract the zip and place the folder of files on your storage card, \storage card\UCMe2\.
You will need to have mortcript.exe registered so the scripts will run when selected (just click it once and it will do that).
If you need to make shortcuts, put extract Zip of EXEs into the same folder as the script files, then you can make shortcuts to the EXEs
Suggestions are always welcome. Share your ini files if you make them.
The ini files are fairly straightforward.
[UCMe2]
appname = (descriptive Name)
subdir = (subfolder name)
RestoreOnly = 0/1 (1 = do not back up this app)
Validate = <fullpath\file> or Regkey HKLM,Software\appname\key (the comma in the reg key is important to restore)
[regkey]
key1="HKEY_CURRENT_USER\Software\AppName\etc"
key2="HKEY_LOCAL_MACHINE\Software\AppName\etc"
[Files]
backupFilename.ext=Fullpath to sourcefilename.ext
anotherbackupFilename.ext=Fullpath to sourcefilename.ext
andanotherFilename.ext=Fullpath to sourcefilename.ext
Click to expand...
Click to collapse
2 of the optional fields from above:
RestoreOnly = 0/1 (1 = do not back up this app)
Validate = (full path or reg key)
are fields to control the backup/restore behavior. RestoreOnly is for some apps or values that are static and do not need to be repeatedly backed up. Validate is a parameter that would require a condition to be met before restoring the settings. Why apply the settings for PocketBreeze or G-Alarm, if it isn't installed yet.
rilphone2.ini
[UCMe2]
appname=Rilphone2
subdir=Rilphone2
[regkey]
key1=HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL
[Files]
rilphone2.dll=\WINDOWS\rilphone2.dll
Click to expand...
Click to collapse
HTCTaskmanager.ini
[UCMe2]
appname=HTCTaskManager
subdir=HTCTaskManager
[regkey]
key1=HKEY_CURRENT_USER\Software\HTC\TaskManager
Click to expand...
Click to collapse
PocketBreeze.ini
[UCMe2]
appname=PocketBreeze
subdir=PocketBreeze
Validate = HKLM,Software\Apps\SBSH.net PocketBreeze
[regkey]
key1=HKEY_CURRENT_USER\Software\SBSH\PocketBreeze
Click to expand...
Click to collapse
This is a great idea, I was just thinking of putting something together like this myself! Looking forward to seeing your progress on this.
Nice idea, but...
Isn't that what (a portion of ) Sashimi does?
I love the fucntionality, just want to understand how duffert you intend it to be from Sashimi.
Thanks
Juju
I'm controlling what gets backed up and restored via a collection of ini files. 1 ini file for each program or settings that you want to backup/restore.
there is a lot of clicking around in sashimi to configure a new reg or to add a new file to the backup/restore and a lot to remove that file or setting.
If someone has a file or reg value for an app and you want to save your value/file for the same app, you have either to create your own or copy and edit it manually for your values... then if you have to edit or change the value, you have to do it again.
The ini files tell it what to backup or restore, it grabs those values or files live and saves them, so you could have live or scheduled backups.
Someone makes an ini file to backup X app all they have to do is share that ini file and you put in your ini folder and now you will be backup up that data
I'm about to reflash my phone so this tool is going through its first live fire excercise.
I have made a bunch of ini files to capture the settings for what I think are important for me... hopefully they will work as intended but that is more a measure of the content of the backup, rather that the effectiveness of the tool that did it
I have attached a bunch of the INI files I made to produce my backup... Is GoogleMap's settings/config in those dat files in \Appdata\ ??
G-Profile.OK
GPSTuner.OK
TouchFloDetacher.OK
Rilphone2..OK
PocketBreeze.OK
GCz.OK
SMSPresets.OK
HWButtons.OK
HTCTaskManager.OK
G-Alarm.OK
Inbox.OK
Exchange.OK
Today..OK
TouchResponse.OK
BluetoothHeadset..OK
Owner...OK
Notifications...OK
Manila.OK
GoogleMaps........OK
Backup Complete
Click to expand...
Click to collapse
This worked so well, it is scary.... muhahahahaha.
1 note... the rilphone2.ini shouldn't be used between ROMs. Apparently, there were some changes between the ROMs (I just flashed a new ROM before restoring) that didn't like some of the data in the REG key that restored and I couldn't get a data session active... But that is an INI file issue, not a script issue. That is the same issue as why restoring a backup (any backup) between ROMs is tricky at best.
I'm dropping this thread and using the one here:
http://forum.xda-developers.com/showthread.php?t=491175
Mods can delete this one if they choose to.
Hi all!
This in my first thread in this forum
As in the title, I'd like to ask you if there's a way to merge mmssms.db files in a single file. I do a lot of backups and programs like MyBackup overwrite them everytime, furthermore I can't let other people to read them. I don't think is impossibile, in fact there's a script to merge iPhone's sms. Thanks a lot in advance!!
Nobody can help me?
the mmssms.db is a SQLite Database. Google for "merge SQLite databases" and
you will find some results. It seems to be possible, although I can't tell you exactly
how to do it, because I don't know anything about SQLite databases.
But I can imagine opening one database and then copy the content of the other
databases and attach it to the first one should be a possible solution.
I've already googled, and found anything good. I can't edit an SQL database via command line (SQLite is almost textual), and most little graphical editors are very limited. That's because I decided to write here
Looking for the same. How to compile mmssms.db files?
I'm trying to do the same thing has anyone found a decent solution?
SMS Backup & Restore lets me save it as XML on the sd card, then restore nandroid to a rom with other SMS and use SMS Backup again there, it adds to the existing XML file on your sd card.. so that would work, but I was hoping for something quicker than having to restore 6 different nandroids run a program and then go back.
I feel like there must be a way to just add the contents of one mmssms.db to another but not sure what software would allow me to do that.
I have extracted 6 different mmssms.db files from my nandroid backups and have them sitting in a folder now.... hmm what next
Found an Online solution?
I found an online solution: https://smsmerge.homedns.org/
The PHP source is here: https://smsmerge.homedns.org/?source=1
I haven't tried it because I'm not a fan of online tools for such personal data so I am waiting for an offline solution.
Ideas:
-Maybe an APK that can seek out *.db files and merge them, possibly seeking out NANDROID backups.
-Otherwise a bash script will do too.
Anyone want to take a swing at this?
I'm willing to collaborate
I know it's been a couple of months,
but has a solution been found???
i use sqlitespy to merge my htc sense mmssms.db file with cm mmssms.db file
first open the new db file (in my case cm file)
then open the old db file with file>attach database
then if your case is same with me you can use the sql script below to insert your db file to the new one (my case old file:leedroid 3.3 htc sense new file cm10.1 vj mod)
if your case is different you have to edit the sql script in order to match the tables columns in each file (a little sql knowledge needed)
Code:
insert into main.sms(_id,thread_id,address,person,date,protocol,read,status,type,reply_path_present,subject,body,service_center,locked,error_code,seen) SELECT _id,thread_id,address,person,date,protocol,read,status,type,reply_path_present,subject,body,service_center,locked,error_code,seen FROM mmssms.sms;
insert into main.addr select * from mmssms.addr;
insert into main.canonical_addresses select * from mmssms.canonical_addresses;
insert into main.part select _id,mid,seq,ct,name,chset,cd,fn,cid,cl,ctt_s,ctt_t,_data,text from mmssms.part;
insert into main.pdu (_id,thread_id,date,msg_box,read,m_id,sub,sub_cs,ct_t,ct_l,exp,m_cls,m_type,v,m_size,pri,rr,rpt_a,resp_st,st,tr_id,retr_st,retr_txt,retr_txt_cs,read_status,ct_cls,resp_txt,d_tm,d_rpt,locked,seen) select _id,thread_id,date,msg_box,read,m_id,sub,sub_cs,ct_t,ct_l,exp,m_cls,m_type,v,m_size,pri,rr,rpt_a,resp_st,st,tr_id,retr_st,retr_txt,retr_txt_cs,read_status,ct_cls,resp_txt,d_tm,d_rpt,locked,seen from mmssms.pdu;
insert into main.threads (_id,date,message_count,recipient_ids,snippet,snippet_cs,read,type,error,has_attachment) select _id,date,message_count,recipient_ids,snippet,snippet_cs,read,type,error,has_attachment from mmssms.threads;
insert into main.words select * from mmssms.words;
hope this helps others that forget to backup sms using a third party app.
Hello, does anyone have a backup copy of the stock /data/local.prop file? I followed the root steps exactly as listed: http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ . However the file I created, /data/local.prop.bak, is no longer present. I expected that file to remain in /data, but it seems to have been automatically deleted.
I would like to retain a copy of the stock /data/local.prop so I can un-root my D3 if necssary. Thanks!
I downloaded the /system dump posted elsewhere on this forum and I also found what was supposed to be a full / dump.
http://www.droidforums.net/forum/droid-3-hacks/162386-droid-3-dump.html
That dump does not contain /data unfortunately.
local.prop is erased and rebuilt on every reboot. Just delete it and it'll re-populate with default values. Or leave it there.. and it'll re-populate with default values.
Excellent, good to know. I must have missed that piece of info somewhere along the way.
Hi everyone,
recently I decided to increase the strength of notification LED, by editing
Code:
/system/sys/class/leds/amber/pwm_coefficient
and
Code:
/system/sys/class/leds/green/pwm_coefficient
values from 5 to 250.
The problem is, whenever I edit those files and save changes upon exiting text editor - changes are not being saved, and I see that only when I open the file again and see the starting value of 5.
I am on Lolipop 5.0.1 GPe, rooted, busybox and I was mounting /system, rw thru Terminal Emulator, 3rd party apps and fx Explorer's built-in solution.
Any help would be much appreciated.
voolandis said:
Hi everyone,
recently I decided to increase the strength of notification LED, by editing
Code:
/system/sys/class/leds/amber/pwm_coefficient
and
Code:
/system/sys/class/leds/green/pwm_coefficient
values from 5 to 250.
The problem is, whenever I edit those files and save changes upon exiting text editor - changes are not being saved, and I see that only when I open the file again and see the starting value of 5.
I am on Lolipop 5.0.1 GPe, rooted, busybox and I was mounting /system, rw thru Terminal Emulator, 3rd party apps and fx Explorer's built-in solution.
Any help would be much appreciated.
Click to expand...
Click to collapse
/system in write protected by the kernel so you must use a custom kernel with /system write permission (unsecured kernel) or push your modified files from a custom recovery.
Btw modifying /system files will probably prevent you to install future ota updates.
@alray
It there any workarount for upcoming OTAs, I don't think update procedure going to change that much to prevent us from cracking-up them files?
Also, any recomandation for kernel in this case?
voolandis said:
@alray
It there any workarount for upcoming OTAs,
Click to expand...
Click to collapse
Going back to 100% stock rom (/system)
Also, any recomandation for kernel in this case?
Click to expand...
Click to collapse
Every kernel that have /system write protection disabled
ElementalX will do the job