Related
Anyone on here know how to Extract a CAB file from a ROM/Extended ROM? ive been trying to find something about this on here and cant seem to find anything that pertains to it. there are several programs that are included in roms and extended roms that i have and i wold like to be able to put them on my 8125 with the ROM i have now. Thanks in Advance!
Corey
If you already have a cabfile that resides in the extended rom the process is quite easy... just use total commander and copy the file from there to a place on your device where you can later use it...
If you don't have a cabfile but just a program, say arcsoft mms composer that's already integrated into the rom, the process gets a little more complicated, but not impossible. You will, however, need to know all the files that the program uses, dll's, imagefiles, exe's and registry posts, copy them from rom to your windows pc and from there use a program like ce cab manager to create a cabfile for it (if you want. you can merely transer all the files and registry posts to your current rom without creating a cab)
_Nomad_ said:
If you already have a cabfile that resides in the extended rom the process is quite easy... just use total commander and copy the file from there to a place on your device where you can later use it...
If you don't have a cabfile but just a program, say arcsoft mms composer that's already integrated into the rom, the process gets a little more complicated, but not impossible. You will, however, need to know all the files that the program uses, dll's, imagefiles, exe's and registry posts, copy them from rom to your windows pc and from there use a program like ce cab manager to create a cabfile for it.
Click to expand...
Click to collapse
cool, thanks for the info, what program do i need to use to unpack the NBF so i can access the files? I tried to use the one in the wiki (typho5) but i cant seem to get it to work.
for dumping rom's read through this thread
You'll probably want to read it all and I'm sure that it wont make that much sense to begin with but it'll come to you
For converting a nbf to nb files use:
Code:
typho5.exe -x nk.nbf
typho5.exe -x nk.nbf does NOT make it a .nba file!
It extracts the contents of the rom (OS, Extended Rom, Radio, Splash Screen, IPL/SPL) into .nb files.
The Extended Rom file can be opened with WinImage.
Molski
Thanks...i just checked out that thread..looks like ive got some studying ahead of me lol thanks for the help.
thanks Molski, you must have posted that just after i read the post above yours lol. thanks for the info i have another question for you here though. http://forum.xda-developers.com/showthread.php?t=291847 As smart as you guys are im sure theres a reason you havent done it though
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
Going through some posts in the blackstone forum I discovered an interesting thread by Sir.B...
He talked about an old trick used for older devices to fit WM6 onto them with the side effect that load times of applications is much faster and tried this on his Blackstone.
I just gave it a try and it's impressive. So far I only tried it on HTC Album and Navigon Mobile Navigator 7:
HTC Album now loads in about 1 sec (previously about 4-5 sec)
Navigon MN 7 loads in about 2 sec (previously about 6-9 sec)
Seems to work flawless on any WM Device ;-)
I'm loving it!!!
Many thanks to Sir.B and everyone else at XDA-DEV!
I attached version 1.1 (which worked fine for me); 1.0 can be found on the original post.
Here's the quote and the link to the original post...
Sir.B said:
this is an old trick that was/is used for older devices to fit WinMo 6 on them
but a side effect is faster application load times
i figured i'd try it on the Blackstone and difference is noticeable
HTCAlbum loads in about 1 Second, before it took about 4
so i'm sharing this with anyone who is interested
The batch file is kept as simple as possible for everyone's ease of use
but this is pretty advanced tweaking, so all common warnings apply
and/or
if you are not comfortable with getting files from/to your PocketPC
and/or
can't figure out how to extract this zip and read the "read me.txt"
and/or
don't know what “any key” is DO NOT TRY THIS!
(read the forum and the wiki a bit more, and you'll gain the knowledge)
Version History:
v 1.0 - initial release
v 1.1 - no icon compression switch added to the batch, for more general compatability
to get you started
a short list of EXEs that i have UPXed and work well for me
AdobeReaderLE.exe
ASyncKiller.exe
BCR.exe
Camera.exe
FMRadio.exe
GoogleMaps.exe
HTCAlbum.exe
iContact.exe
KeePassPPC.exe
kinoma.exe
Labyrinth.exe
LongPressEndKeyApp.exe
MP3Trimmer.exe
MusicID.exe
Opera9.exe
OperaL.exe
QuickGPS.exe
RSSHub.exe
s2p.exe
s2u2 Settings.exe
s2v.exe
StreamingPlayer.exe
TomTom Navigator.exe
USBtoPC.exe
WMRegOptimizer.exe
YotaCenter.exe
YotaCenterUpdater.exe
YouTube.exe
and here is a list of things NOT to compress
manila.exe
cprog.exe
thumbCal.exe
calculator.exe
wt5jetpr.exe
any DLL
Please share your findings so that others can benefit from it
(SEARCH this thread for your application name or EXE filename)
note: you'll have to repeat this proses after upgrading your applications
thanks to;
edhaas - for the original simple to use batch file More info in this THREAD
UPX Team - a lot of technical info on the Website
kwbr - for a great ROM
and especially XDA-DEVELOPERS as a whole
Click to expand...
Click to collapse
LINK
amazing!! It works! Thanks very much.
I tryed successful SecondToday.exe , iDialer.exe , Destinator.exe
this looks quite interesting..will try it with all my programs after i backup the exe files
Giannis86 said:
this looks quite interesting..will try it with all my programs after i backup the exe files
Click to expand...
Click to collapse
It backs up the exes automatically. I did it on my device, Didn't notice any difference. Then again, it might be because my rom is already fast
List of EXEs that WORK / DON'T WORK
sosimple said:
amazing!! It works! Thanks very much.
I tryed successful SecondToday.exe , iDialer.exe , Destinator.exe
Click to expand...
Click to collapse
I guess we should start a list with Applications that work / don't work.
EXEs that WORK
AdobeReaderLE.exe
ASyncKiller.exe
BCR.exe
Camera.exe
Destinator.exe
FMRadio.exe
GoogleMaps.exe
HTCAlbum.exe
iContact.exe
iDialer.exe
KeePassPPC.exe
kinoma.exe
Labyrinth.exe
LongPressEndKeyApp.exe
MobileNavigator.exe (Navigon MN7)
MP3Trimmer.exe
MusicID.exe
Opera9.exe
OperaL.exe
QuickGPS.exe
RSSHub.exe
s2p.exe
s2u2 Settings.exe
s2v.exe
SecondToday.exe
StreamingPlayer.exe
TomTom Navigator.exe
USBtoPC.exe
WMRegOptimizer.exe
YotaCenter.exe
YotaCenterUpdater.exe
YouTube.exe
and here is a list of things NOT to compress
manila.exe
cprog.exe
thumbCal.exe
calculator.exe
wt5jetpr.exe
any DLL
...to be continued
I compressed with the above methode 105 .exe files of the windows folder (of a htc diamond). I compressed every exe file that i found in windows. I deleted all that had 0 kb file size as probably those files does not compressed corectly or something is wrong. So the exe files that left, was 105 exe files. I puted all those to windows folder ,overwriting the originals . I saved 15 Mb or more of space, the phone was extremely fast ,but cant run manila. I try to find which of the files must changed to the originals to run manila. I am sure it must be 2 or 3 files , but how can i find which 2-3 of the 105 files must be changed?
If i make it , i will give the full list of files that can be changed to earn max space and max speed
I compressed 104 files of windows folder without problem!
So i found the file that caused problem and manila didn't start. It was _mpman.exe By changing all the 104 others , no problem until now. I giving all the list with the 104 files of window folder of a diamond running manila 2.0.3 if anyone else want to try. Here is the list :
catalog.exe
CommManagerLink.exe
LaunchMSItem.exe
MobileCalculator.exe
tdsserver.exe
WelcomeCenter.exe
AdvancedConfig.exe
__cusTSKTEMP.exe
_mp07.exe
_mp08.exe
AdvancedNetwork.exe
AlbumSearcher.exe
ArcMC.exe
arinvalid.exe
AudioBooster.exe
AudioManager_Eng.exe
AutoAttribute.exe
AutoFormatMoviNAND.exe
AutoRun.exe
AutoShortcut.exe
Biotouch.exe
btdwake.exe
BTFtpClient.exe
btlauncher.exe
btrenamedir.exe
CheckAutoRun.exe
ClearStorage.exe
CommManager.exe
ConfigureDevice.exe
ConnectionSetup.exe
ConnectionSetupAuto.exe
DataDisconnect.exe
DeviceInfo.exe
EndKey.exe
EngInfo.exe
eT9MyWords.exe
FaxView.exe
felvop.exe
FieldTest.exe
FMRadio.exe
GAlarmWakeup.exe
HACSetting.exe
HTCMessage.exe
HTCStartUp.exe
HTCUSBToPCPopUp.exe
IA_Zip.exe
JBlend_AMS.exe
JBlend_VM.exe
KeyLock.exe
Labyrinth.exe
LongPressEndKeyApp.exe
ManilaActivateToday.exe
ManualFormatMoviNAND.exe
MicrophoneAGC.exe
MP3Trimmer.exe
NewMailAccount.exe
OneNoteMobile.exe
PhoneAgent.exe
PlayShow.exe
Powerexe.exe
PowerOffWarning.exe
ppt.exe
pword.exe
pxl.exe
QuickGPS.exe
Recorder.exe
Redial.exe
RegistryCSPTool.exe
remote.exe
RUpdate.exe
saplaywm.exe
SAPSettings.exe
sdpready.exe
SignatureReplace.exe
SIM_MGR.exe
SIMLock.exe
SIPGT_app.exe
startkey2.exe
StartUPBioTouch.exe
STK_UIPPC.exe
StopEvtSnd.exe
StorageLow.exe
StreamingPlayer.exe
TaskManagerApp.exe
TaskManagerLite.exe
TFSettings.exe
TmAppLauncher.exe
Transport.exe
USBtoPC.exe
VCDaemon.exe
VocabSetting.exe
VoiceCommander.exe
voicemail.exe
VTKey.exe
wcsan.exe
WLANSettings.exe
WLMImageUpdate.exe
WLMLauncher.exe
WLMMessenger.exe
WLMSetup.exe
WMADBG.exe
xT9Settings.exe
YouTube.exe
ZipView.exe
This works really well on my Verizon TP, but when I did it on all the .exe's in the Windows directory, it messed up the HTC volume control program. I'm not sure which .exe it was but afterwards, when I hit the volume up/down hard keys, only the Windows volume pop-up would come up. I've had to do a hard reset to get it back.
I agree that a list of .exe's that it works well on would be really helpful.
My 2 cents
Hi, I think it's a bit useless to do all exe files: If you compress a 16 Kb exe file to 12 Kb the loading time will not make a huge difference. Also, after two or three reads from the storage memory the program should actually be cached in memory assuming that you have made the cache performance tweaks. Furthermore this seems only sensible for exes that you use often; why would you want to do "ClearStorage.exe" which basically does the hard-reset from the control panel?
The big performance gain and space safe comes from large exe files that are cut to about 1/3 in size. Here it does make a huge difference. I am currently trying and running:
Opera9.exe and OperaL.exe << Edited after comments of PierreDiamond which is very right to leave the Pre alone.
Googlemaps.exe
HTCAlbum.exe
Camera.exe
HTC_GPStool.exe
TomTomNavigator.exe
ScummVM*.exe
The biggest effects were seen with Opera (6MB), Tomtom (7MB) and ScummVM (4.5 MB)(!!! : -) ). For Camera.exe and HTC_Album.exe I am not 100% confident that I am going to keep these. The speed gain is very little, and it does seem to affect the Manilla stability a little bit when more stuff is running. However I am not sure whether this is fully related to compressing the programs. So for now I am still trying.
Another thing I noticed is that it does not like exe programs which are still linking to outside files / sources such as 3.5 Net. An example of this is the Lightsaber program (Saber.exe).
I tried with some prog (MP3Trimmer, Powerpoint, Opera, Acrobat Reader)
Works great! But NOT for Opera! Because there's a OperaPre which launch Opera after SoftReset while Boot... and it seems to be, that the driver for decompress needs much time to load and needs additional RAM when its needed while boot. I had a CPU consumption around 6 % more.
Also - never pack something which is started automatically after soft reset. The other programms like Acrobat Reader or Powerpoint - everthing's fine and are really a little bit faster to start and less need in main storage.
Thanks for this Tweak
Pierre
dlee83 said:
This works really well on my Verizon TP, but when I did it on all the .exe's in the Windows directory, it messed up the HTC volume control program. I'm not sure which .exe it was but afterwards, when I hit the volume up/down hard keys, only the Windows volume pop-up would come up. I've had to do a hard reset to get it back.
Click to expand...
Click to collapse
Why did you do a hard reset? Squeezer makes a backup of the original file in the folder "2_Backup". Therefore you could just copy those back to the device.
maybe I better ask this question here:
i tried this method and copied the file in to the windows folter with total commander - over active-sync I could not overwrite the files. But now even less space is available..
aand.. when i copied all the files it asked me only about 5 times if i wanted to overwrite this file... so my explanation is that these are files which are stored in the rom.. so they got not overwritten but only doubled...
is this possible? and what can I do about it?
=> the problem is of course the data-memory and not the programm-memory
=> it really seems that the files are doubled...
the part of compressing exe at the PC gone well but i can't copy/paste the compressed exe back at touch pro , original files place is windows...i think this folder is a ROM folder...help.....please...
chaelli said:
maybe I better ask this question here:
i tried this method and copied the file in to the windows folter with total commander - over active-sync I could not overwrite the files. But now even less space is available..
aand.. when i copied all the files it asked me only about 5 times if i wanted to overwrite this file... so my explanation is that these are files which are stored in the rom.. so they got not overwritten but only doubled...
is this possible? and what can I do about it?
=> the problem is of course the data-memory and not the programm-memory
=> it really seems that the files are doubled...
Click to expand...
Click to collapse
massoh said:
the part of compressing exe at the PC gone well but i can't copy/paste the compressed exe back at touch pro , original files place is windows...i think this folder is a ROM folder...help.....please...
Click to expand...
Click to collapse
It should work with Total Commander. The files should not be doubled, but overwritten. Therefore overall storage (data memory) should decrease.
If I'm not mistaken (please correct me If I am) ROM storage for extended ROM etc. and data memory (flash chip) / programm memory (RAM) is separated. (?)
you can copy the apps with activesync but if you wanna put them back into the windows folder then your going to need totalcommander
I did copy it with total commander.. and it only overwrote about 5 exe files.. the others where doubled (I tested it - I deleted one of the exe files... and when the list reloaded the file was there again - but there was no error)..
do I have to use special settings in total commander?
Any chance to improve the tool so it has a list of known-NOT-to-work-after-compression EXEs?
It would be more foolproof as it would skip the problematic files automatically.
Edit: actually I might do it myself, I know how I can code this.
That would be a great addition!
snark_be said:
Any chance to improve the tool so it has a list of known-NOT-to-work-after-compression EXEs?
It would be more foolproof as it would skip the problematic files automatically.
Edit: actually I might do it myself, I know how I can code this.
Click to expand...
Click to collapse
snark_be said:
Any chance to improve the tool so it has a list of known-NOT-to-work-after-compression EXEs?
It would be more foolproof as it would skip the problematic files automatically.
Edit: actually I might do it myself, I know how I can code this.
Click to expand...
Click to collapse
yes please, when you are done
share with everyone this great addition
it would be a great help for many people
but who is going to maintain that list across so many ROMs and versions?
chaelli said:
I did copy it with total commander.. and it only overwrote about 5 exe files.. the others where doubled (I tested it - I deleted one of the exe files... and when the list reloaded the file was there again - but there was no error)..
do I have to use special settings in total commander?
Click to expand...
Click to collapse
Same here. I've actually lost some space, after copying the compressed .exe files to Windows dir using Total Commander. The file sizes of new files are correct and smaller than before...
It seems like it keeps backup copies of the replaced files somewhere?
I’ve started cooking my own ROM’s only a week ago. I wanted to share my experiences here as it’s not as easy as it seems Well, with the right settings, tools, references, etc it makes it easier though. So this is my sharing back to the community, my tutorial/reference guide on how to cook a ROM.
The result of my days of hard work is named DaxyROM and can be found here.
If you want to start cooking, be prepared to read a lot and spent a lot of time trying your home cooked meals. But when it boots and works as expected, you’ll enjoy all the time spent.
There are 3 steps I’d like to discuss in the following 3 posts:
1) Basic ROM extraction and cooking
2) Adding / Removing programs
3) Upgrading your XIP/SYS (aka install new OS version)
First of all get to know what you’re dealing with. Understand what SYS/EXT/OEM/ROM/XIP is ‘cause at the end of the week you can’t think of anything else. Good source here.
1 Basic ROM extraction and cooking
I’ll be using the Ervius Visual Kitchen and the official WM6.5 ROM from HTC to start with.
* Download Ervius Visual Kitchen. Always use the latest version.
* Download WM6.5 ROM’s from HTC
* Download CustomRUU.exe
Preparing the kitchen:
Extract Visual Kitchen (VK) to C:\Kitchen (will be refered to as Kitchen now)
Create a directory in the Kitchen named RomDump
Open the WM6.5 HTC ROM .exe file with Winzip
Extract the file named RUU_signed.nbh to the RomDump directory
Now open the Kitchen (erviuskitchen.exe). Ignore the warning messages
Click on the bottom left button named “Dump nbh/nb/payload”
Open the RUU_signed.nbh file and wait till it’s completed.
Enter the Kitchen\RomDump\dump directory
Move all files to Kitchen directory
There seems to be an issue with kitchen_build_rom.bat while building your ROM.
Modify your kitchen_build_rom.bat file from this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
if not "%errorlevel%"=="0" goto error
To this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
REM **************** if not "%errorlevel%"=="0" goto error
You’re now ready to go.
Built your first ROM – The Visual Kitchen Basics:
Click on the pull-down menu next to RHODIUM and select RHODIUM
Ignore the messages. You’ll see the screen building now
Fill in the name of your ROM at the ROM ver. Field
Check the “Real WM 6.5 AKU” field
Click on the “Other” button
Change the –PP value from 6 to 18 and click on the Close button
Save the settings: hit the “Save ROM” button. Filename must end with extension .erv.
You’re ready to hit the Create ROM button
Wait till it finishes
Now open the Kitchen\RELEASE_Rhodium directory
Copy the CustomRUU.exe to this directory and run it
You’re now running the HTC WM 6.5 ROM rebuilded by yourself
Right now your kitchen is ready to use and you can modify it as much as you like.
Part 2: Adding / Removing programs
Right now we know that the kitchen works. We have rebuiled the official version and it boots up fine. Make sure to test your extracted ROM works otherwise you will loose a lot of time. Now it's time to make changes. Keep in mind that the following is what I've teached myself and that there might be better methods in adding/removing packages.
The easiest is removing packages. Just double-click on the package and it won't be included. If you want it back, just double-click again and it's back in. Easy as that.
Keep in mind that you can't remove OEM packages and that if you're removing packages from the SYS you have to be carefull as you might run the risk you remove a core application and that Windows won't boot anymore. You can however safely remove packages like LiveSearch, MSTag, OneNote, etc without any problems.
The EXT directory is where all packages reside. This directory is devided in 2 sub-directories. One for Rhodium specific packages and one for Shared platforms. By default all applications are in the Rhodium directory but you might want to change this manually to Shared if you're planning on building for multiple platforms. For now we'll keep them in the Rhodium directory.
You need to either find EXT packages online, or you need to convert CAB files to EXT packages. That is basically it.
I've found a lot of new EXT files here: http://www.everythingdiamond.info/showthread.php?t=94. You can download new EXT folders and copy them into the VK\EXT\Rhodium\<built>\Rhodium_External_Packages directory. Now load VK and Load your previous saved config. Scroll down the list and you will see your new package. This package is not yet included in the Kitchen. This is useful if you're upgrading packages so you'll know which one is new and which one is old.
If you're upgrading packages, keep in mind that some do depend on each other. For example Manila heavily depends on all kinds of other packages. When you're upgrading one, upgrade the others as well unless you're certain there are no dependances. You'll find out when your upgrading. Make sure to safe your work very often so you can always revert back to your previous situation.
As I mentioned you can also convert CAB's to EXT. This can be done using the package-creator from Ervius. TotalFire Package Converter does the job as well, but I haven't used it yet.
Download your application as cab file. Open the package converter, open the cab file and it converts to an EXT directory. This EXT directory can be copied into the kitchen again.
Adding your own EXT is more complicated. For example if you want to create a package which holds all your registry tweaks.
You can either download this file and change the .reg file, or you can take the hard way and learn by using this tutorial: http://www.mediafire.com/file/j15nqfzkwz5/CreatingOEM.zip
Both are written by user kwbr. See here for more info: http://forum.xda-developers.com/showthread.php?t=480714.
I believe this concludes this section. You should be able to add and remove packages right now. Next stop, installing a different Windows build.
Please sent me feedback on how to improve my posts.
Part 3: Upgrading your XIP/SYS (aka install new OS version)
It's time for the last part of my Tutorial. This time I will explain how to upgrade your XIP/SYS.
First you need to find your new XIP/SYS. I get mine WM 6.5.1 at http://forum.xda-developers.com/showthread.php?t=544445 but there are probably more sources.
First you need to know what to get. If I'm taking the above URL as example, there are several files.
The first one you need is the XIP/SYS one. This however is the OS for a screen resolution of 480x600 (The Touch Pro2 has a screen resolution of 480x800). You still need this file as it the the base OS combined with the (wrong) resolution files. That's why you need the 2nd file named "0409 USA English United States (Includes COMMON DPI, required for others)" as well. This is the english version for all resolutions.
The first file you can just extract in your SYS directory. It will create a new directory with the new build number and a directory named Shared.
The Shared directory you need to move to your ROM directory. This means you end up with a new build number in the Shared directory.
Now we just need to make sure the resolution files are copied. This means you need to copy a list of directories. At first create a directory named SYS\<build>\dpi_192_resh_480_resv_800. Just extract the complete 0409 Language file into a temp directory and the create the following directory structure by moving directories:
Code:
SYS\<build>\dpi_192_resh_480_resv_800\0409\Base_Lang_0409_DPI_192_RESH_480_RESV_800
SYS\<build>\dpi_192_resh_480_resv_800\0409\Themes_Lang_0409_DPI_192_RESH_480_RESV_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\base_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\MediaOS_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\Phone_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\Redist_dpi_192_resh_480_resv_800
This concludes the SYS, now the XIP.
The zip file you downloaded also contains a directory named "MSXIPKernel".
Extract this directory to your ROM\Shared\<build> directory.
Now go into the directory ROM\Rhodium.
Inside the builds you can find the OEMXipKernel which are basically the device specific drivers.
Usually these drivers don't change, unless you are upgrading the OEMXipKernel using a newly released ROM from HTC.
For now you have to copy the original build directory over to the new directory and you're done.
Right now your OS is ready to cook:
Open your Kitchen
Open your saved configuration file
Change the XIP and SYS versions (top right) to the new build version
Hit the Create ROM button
You're all set
After creating your new SYS, I suggest changing some default values. For example changing Unsigned Themes/CAB Policies:
Open the file named OEM\Rhodium\0409\Operator Pkg\mxipupdate_oemoperators_100.provxml
Find the section <!--337.01_SecurityPolicy-->
Add the following lines:
Code:
<parm name="4101" value="8" />
<parm name="4102" value="1" />
<parm name="4122" value="1" />
<parm name="4103" value="16" />
<parm name="4097" value="1" />
Save the file
Cook your ROM
Basically this means:
ID 4101: Unsigned CABS Policy = 8
ID 4102: Unsigned Applications Policy = 1
ID 4122: Unsigned Prompt Policy = 1
ID 4103: Unsigned CABS Policy = 16
ID 4097: Unsigned Prompt Policy = 1
Now you won't get warnings if you install unsigned applications etc.
One last thing to keep in mind. Don't forget to grab a new version of the OEM directory once it gets released by HTC.
I've ran into a situation where ActiveSync ran out of memory and a new OEM fixed this.
Thanks
Ervius: Big thanks to Ervius for his great Kitchen and Package creator: http://forum.xda-developers.com/showthread.php?t=469420
Da_G: For providing the latest WM builds: http://forum.xda-developers.com/showthread.php?t=544445
hilaireg: For providing his tuturial which was my starting point: http://forum.xda-developers.com/showthread.php?t=521632
kwbr: For his tutorial on creating applications: http://forum.xda-developers.com/showthread.php?t=480714
Everyone I forgot to add. Make yourself known and I'll add you of course!
This concludes my Tutorial. I hope you find it useful. Please feel free to provide feedback so I can adjust the tutorial or provide answers.
Eventually I may try cooking my own ROM.
Not because I can't find any good roms out there.
But just for the simple fact that I want to learn how to do it.
Thanks for taking the time to write this all up.
Just what I was looking for. I have been searching and reading and searching and reading but not getting anywhere. After following your post I've dissasembled a ROM, renamed it, and then reassembled it.
Now I was just following a recipe and didn't understand everything that happened (what is the -PP value and why am I changing it?) but I'm finally making some progress. Looking forward to your upcoming posts.
BTW, I just used the official TMo US 6.1 ROM that CDGuider dumped and made available. It'll do while I'm learning but I'm really waiting for the Official TMo US 6.5 to be released so I can use it as the main ingredient.
S
sleonard said:
Just what I was looking for. I have been searching and reading and searching and reading but not getting anywhere. After following your post I've dissasembled a ROM, renamed it, and then reassembled it.
Now I was just following a recipe and didn't understand everything that happened (what is the -PP value and why am I changing it?) but I'm finally making some progress. Looking forward to your upcoming posts.
BTW, I just used the official TMo US 6.1 ROM that CDGuider dumped and made available. It'll do while I'm learning but I'm really waiting for the Official TMo US 6.5 to be released so I can use it as the main ingredient.
S
Click to expand...
Click to collapse
Let me know if I missed something. I had to do it from the top of my head so if I forgot to add an action, let me know and I'll add it.
PS, the -PP allows you to change the PagePool size (sort of swapfile for WM).
Some people set it to 0, some to 12-18. I found 18 to be working fine. I must admit that I have too little knowledge to truly understand the PP stuff to come to a clear correct value (I believe it's questionable, the values).
If anyone disagrees, let me know
This is a great post.
I've subscribed because I'm really interested in learning and once I've ran through it myself will reference it on my site for all to use.
Well done you, supply and demand.
Daxy, On Tuesday I get my Pro2 and begin to try. Thanks for a great post!!!!!!!!!!!!!
I download the files of 23069, for example, where should I hold?
Xip and sys...
Awesome Information!! Thanks a lot and I appriciate it because rarely people share knowledge!
Thanks for the clear tutorial! Looking forward to future updates!
really excited to start making my own roms...
thank you for taking the time and making this
hopefully in the future ill be able to contribute to the community...
my touch pro2 could use some of my own flavor lol
thanx for the effort ...
gonna read thru it when i am more awake ... lol ... this seem to be what i am looking for ... wanna cook my own rom but proper info is few and far between for the rhodium ... unless i waslooking in the wrong places ... hehehe
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Thanks all for your kind words.
I've updated Post 2: Adding / Removing programs
Hope you like it. Please let me know if anything is missing.
Next post will be regarding using a new version of Windows, where to place files etc. This one should be up in a couple of days.
eddy16112 said:
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Click to expand...
Click to collapse
Customized ROMs are protected. You cant dump them. You can only dump official ROMs.
eddy16112 said:
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Click to expand...
Click to collapse
ai6908 said:
Customized ROMs are protected. You cant dump them. You can only dump official ROMs.
Click to expand...
Click to collapse
Correct! even if the customized rom was unprotected you still would not be able to rebuild a rom off of it because of the loss of rgu's and dsm's in the origional building process. would be very difficult.. best thing to do is ask for the kitchen files from the chef and hope they can share.
edit: one thing you can do is use an app called rom imaged editor and open the nbh with that, you can grab individual files out, even protected roms you can.. then you can add things on your own.
I've changed the topic to My first Rhodium ROM. Though it would sound better.
joshkoss said:
edit: one thing you can do is use an app called rom imaged editor and open the nbh with that, you can grab individual files out, even protected roms you can.. then you can add things on your own.
Click to expand...
Click to collapse
I have extracted files from kooked roms no biggie. saves time from flashing for sure...
I have tried to extract all files from kooked rom too, and it seems to work. but might be able to use some dll files.
Everytime I build the ROM (rebuilding the stock rom, not config changes) towards the end the kitchen gives me a runtime error, I have tried on a 64-bit vista and 32-bit XP.
After reviewing the log it appears that the problem is:
Executing: kitchen_build_rom.bat.....
ERROR! (errorlevel: 1)
ERROR executing: kitchen_build_rom.bat
ERROR!!!
Wait some seconds...
No ''SVN'' folders present...
Hi..i've already search for a topic regarding to this, and most of the findings only talks about how to edit it or combine it and such that it will be installed automatically.However, my main question is that how would i make/create a cab file for applications which had been installed into the phone?as there are some application which i had updated it through the phone and it will take some time if i intended to install it back in case i've formatted my phone. So any help would be appreciated and if there's somewhere it had been discussed before please show me the way..thank you
Anyone? Need some help here. Thank you.
It's not completely impossible, but very impractical.
To "cab" (to make it a verb) something, you'd need to know every single file the program uses (sometimes, applications install dll's into the windows folder) and every registry key as well. You'd have to gather all these files and then create a new cab and import them to the proper paths.
I believe SKTools has an option to view what files a program uses.
It's next to impossible for applications that are installed through an installation DLL in the cab - it's hard to track what exactly changes when you install these apps.
Best way to do it though - find the original cab. You could try to combine cabs, but it'd get messy, best use an automatic cab installer then.
Thank you
Thank you for the reply. From ur opinion it is indeed difficult to find the changes made especially with the updates involved. Thank again.
Well it is really simple, just have to know if it has any keys in the registry, what dependencies it has like any dll or other things and then you use visual studio and make a smart device cab ant put in there the files in the folders needed, the shortcut and the key registry you compile the cab and in less then a minute you have a cab