Related
I want to write make my application package a part of existing ROM and wants wheneever set hard set it installed (Dont want to burn ROM for each type of machine)
OR
once my program intsalled in memory, hard reset should not disturb it and will remain at machine startup
any luck?
Thanks,
Khurram
Hi Khurram!
There is a relatively simple solution to keeping your program after hard reset, without adding it to ROM and re flashing the device.
Most devices have either extended ROM, or better yet a file store, which is not erased by hard reset, but can be freely written to. (I think extended ROM needs unlocking before you can write to it).
Here's how to make your program restore it self automatically after hard reset: In the file store create a directory named 2577. In that directory place a file called autorun.exe
The system will launch autorun.exe automatically after hard reset, so you can write one to do what ever you need (install programs, restore settings etc.)
I'm not sure about the extended ROM, but I believe the procedure is similar.
P.S. You should ask technical questions like this in development and hacking forum.
Good luck!
levenum, Thanks a lot for the help , i will try and let you know. one thing the "2577" should be created how (any help will be appreciated) and will that folder and file also store at storage "E ROM" or will have to cook ROM for this.
also , any disadvantage of it as compare to Cooking a ROM
Regards
Khurram
In order:
2577 is an ordinary folder which you create just like any folder. (2577 is the processor type) The system simply knows to look for autorun.exe in that folder.
I don't know about E ROM, sorry.
The disadvantages of using file store (that I can think of) is the fact that the user can easily delete the content if he chooses to. Also most WM5 devices don't have "file store".
But if that is not a problem for you, the great advantage of it, is that you can replace any file, using just the explorer which means you can quickly test and modify your app without cooking ROM and re flashing.
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
hello
i need to add a username into the registies for a number of devices i'm flashing. Unfortunatly the usernames all need to be different i.e. PDA001, PDA002 and so on...
I've created a number of different cab files each for a different device that will add the username in.
So is it possible to run the cab file off the storage card as part of the hard reset process. i've updated the SD card with the file Username.cab which is the name of all the cab file, then added "CAB: \Storage Card\Extended_ROM\Username.cab" in to config.txt which is in the Extended ROM. i tested it but it didn't work.
Has anyone got any ideas
Or may be have a shortcut to the cab file added into start up. Would that work?
I'd suggest that you instead edit an existing (or relatively insignificant) CAB file (that you'd probably have no use for anyway) with the registry entries/additions so that its guaranteed to be included when you do the Extended ROM customization.
Did you ensure that you copied all the files from an original extended ROM correctly (before making your modifications)?
The thing is I have around 250+ device which need flashing with the same image and as all the devices will require a different Username adding into the registies I 'll need to run an external cab file, a cab file which will be different for all the devices and it's best to run it from the SD card.
I tried to adding a cab file into the Extended ROM which will install a shortcut into the startup folder the shortcut is to the cab file on the storage card. But for some reason it didn't run.
I have a couple of SD cards with an image of my Extended rom on so if anything goes wrong i have the backups.
Whats wrong with having the 'end-user' maually execute the .CAB file?
Why don't you simply customise one PDA (the way you wan't with your preconfigured settings) (minus the user/device name), then do an entire backup using SPB BACKUP (onto a SD Card). You can then restore this image on all 250+ devices (sounds time-consuming,but it really isn't).
All the end user had to do, is to manually execute your .CAB file when they are issued the units.
This is your true answer (in my opinion):
http://www.spbsoftwarehouse.com/products/backup/?en
RE: Whats wrong with having the 'end-user' maually execute the .CAB file?
Basically the devices are used by Market research interviewers who work for us, most of whom are not familier with the devices and are not computer litterate. I'm responsible for a small support team and also the development of the devices. The software we use is already extremley simple and all they need to do is click a buttom "Connect" if the username is not already inserted they get a box "Logon Failed, please check the following details are correct." and a username and password box is displayed and they simply need to type in the id number from the sticker on the back of the pda (like PDA001).
We have just had a large project in feild and over the period we have around 200+ user. Around 50% of the call we took, at some point they had problems entering the username. As much as SPB backup would be of use, if they can't already do a simply thing like type in PDA123, asking them to do this seem like asking alot and would probabily cause more issues.
We already have all the other information in the registries for this application and the username is the only thing which isn't consistant through out.
Do you know if it would be possible to prompt them to run the cab from the sd card which enters the username into the registires on startup?
Nunwood PDA said:
Do you know if it would be possible to prompt them to run the cab from the sd card which enters the username into the registires on startup?
Click to expand...
Click to collapse
Sure it is possible. Did you already try placing a shortcut to the .CAB in "Windows\StartUp" ?. Likewise, you can easily create another script that deletes that shortcut (to ensure that its only used once).
Please keep us posted, on your developments.
Nokia 3650 said:
Sure it is possible. Did you already try placing a shortcut to the .CAB in "Windows\StartUp" ?.
Click to expand...
Click to collapse
Yeah, it didn't do anything. I had a cab file in the extended ROM which placed the shortcut in the dir. \Windows\startup\. For some reason nothing happened, but when I navigate to the .cab file it ran without any problems.
When you say create another scipt, how would I go about doing that? If i had an .exe it could act as a link to the cab on the SD card. i'm not familier with this kind of method. But I think that would solve the problem.
The location of the .cab is: \Storage Card\Help\UserName.cab
Thanks for the exact location. I'm just compiling something for you in visio Studio 2005, that will execute the .CAB file when run at automatically from startup (it'll do this only once).
After searching for hours on all the files, procedures, etc. on the subject, here's a quick guide for the n00b's out there that want to do this... Some information i will be repeating from other places on the internet.
----------------------------------
The following Files are needed (search the forums and google to locate)
1. CheetahUnlocker.rar (http://forum.xda-developers.com/showthread.php?t=334100)
2. Treo750_OS5_2_19199WWE_STD.rar
3. Treo750Radio1.54.07.00.rar
4. RUUWrapper.zip
OK.. Now here we go
unrar the first file 'cheetahunlocker' and basically follow the instructions from the above #1 link. Two things to note: Ignore any images for Hermes and you must have .net 2.0 framework installed on the device.
when you run the unlocker, the first one worked fine for me, the second process didn't work, but that doesn't matter. also watch the screen for the unit to ask you about opening files. if you don't do it, it can time out and then you'll have to start over.
Now here is the fun part.
1. Unzip the RUUwrapper file to it's own folder.
2. unrar the CHEEIMG.nbh file from Treo750_OS5_2_19199WWE_STD.rar into the same directory of the RUUwrapper files
3. rename the CHEEIMG.nbh file to CHEEIMG_FW.nbh
4. run the RUUWrapper.exe file and it will flash the rom of the unit to WM61. **remember to watch the screen for prompting of opening files at the beginning.
5. Done with WM61. Now for the radio update. It's basically the same process as above.
6. unrar the CHEEIMG.nbh file from Treo750Radio1.54.07.00.rar and put it into the RUUwrapper directory like before.
7. rename the CHEEIMG.nbh file to CHEEIMG_FW.nbh (delete the old one first)
8. Run the RUUwapper.exe file again to flash (this time) the radio to the unit. **remember to watch the screen for prompting of opening files at the beginning.
9. All Done.
----------------------
It worked fine for me with the Treo 750 and the AT&T network..
Main places i got information from were:
http://forum.xda-developers.com/showthread.php?t=365873&page=9
http://forum.xda-developers.com/showthread.php?t=334100
Your method above just helped me escape a bootloader loop which was (apparently created) by trying to load a different custom rom after having installed hardSPL. The only precautionary measure I took was to place only one image (the same OS & Radio you used) into the RUUWrapper folder at a time and it loaded right up. Still checking and testing some things out because the bootup isn't exactly smooth as silk, and the old "TREO750-1.13-CNG" still shows up under About->Phone->Software Version, but all firmware references reflect the updates. MTTY was ineffective in my particular situation.
Now for testing the radio for reliability and battery drain,etc...
Thanks for the heads-up!
Witch one is the correct selection (see attachment)
Anybody? at least tell me where I can find information about RUUWrapper.
Well I clicked Force use safe SSPL and clicked through and I got a error message saying that it could not communicate with the 750 Error 246 check usb connection?
I read that Vista had some issues with usb connections and to download and use VistaRUU usb drivers, I installed it according to the description, still error 246 and sometimes error 202?
Any ideas?
honestly i don't remember seeing that screen you are getting. it looks like the software isn't detecting the rom you have on your phone, in which case i would use the autodetect.
Hello Eric,
If I use autodetect it says it can not detect what version I'm using "Recomend using Safe SSPL"
This was the ONLY process that worked for me. However, I did not use the Cheetah unlocker, it is unfriendly with my Vista USB connection. I used magic unlocker and then your instructions and now I running on WM 6.1..
Thanks.. great work!!
I wonder - do you have Voice Command anymore?
Just curious - I lost Voice Command when I did this upgrade. Sure, the OS runs nice, seems a little faster, but I sure do miss Voice command. I am running AT&T's Treo 750, which had Voice Command on it. Some people, on some websites, like TreoCentral said there was a 'lite' version, which did not have Voice Command, but I installed this version: Treo750_OS5_2_19199WWE_STD.rar, and that seems like the right one.
So, I wonder - do you have Voice Command anymore?
As I know it is the normal version's bug (missing the voice command).
I completed set 1, no success!
When u say add to directory what do you mean?
missing the voice command？ Oh my...
egiblock said:
After searching for hours on all the files, procedures, etc. on the subject, here's a quick guide for the n00b's out there that want to do this... Some information i will be repeating from other places on the internet.
----------------------------------
The following Files are needed (search the forums and google to locate)
1. CheetahUnlocker.rar (http://forum.xda-developers.com/showthread.php?t=334100)
2. Treo750_OS5_2_19199WWE_STD.rar
3. Treo750Radio1.54.07.00.rar
4. RUUWrapper.zip
OK.. Now here we go
unrar the first file 'cheetahunlocker' and basically follow the instructions from the above #1 link. Two things to note: Ignore any images for Hermes and you must have .net 2.0 framework installed on the device.
when you run the unlocker, the first one worked fine for me, the second process didn't work, but that doesn't matter. also watch the screen for the unit to ask you about opening files. if you don't do it, it can time out and then you'll have to start over.
Now here is the fun part.
1. Unzip the RUUwrapper file to it's own folder.
2. unrar the CHEEIMG.nbh file from Treo750_OS5_2_19199WWE_STD.rar into the same directory of the RUUwrapper files
3. rename the CHEEIMG.nbh file to CHEEIMG_FW.nbh
4. run the RUUWrapper.exe file and it will flash the rom of the unit to WM61. **remember to watch the screen for prompting of opening files at the beginning.
5. Done with WM61. Now for the radio update. It's basically the same process as above.
6. unrar the CHEEIMG.nbh file from Treo750Radio1.54.07.00.rar and put it into the RUUwrapper directory like before.
7. rename the CHEEIMG.nbh file to CHEEIMG_FW.nbh (delete the old one first)
8. Run the RUUwapper.exe file again to flash (this time) the radio to the unit. **remember to watch the screen for prompting of opening files at the beginning.
9. All Done.
----------------------
It worked fine for me with the Treo 750 and the AT&T network..
Main places i got information from were:
http://forum.xda-developers.com/showthread.php?t=365873&page=9
http://forum.xda-developers.com/showthread.php?t=334100
Click to expand...
Click to collapse
This is great and it worked for me so I'm including the files here.
WM 6.1 does have some things that need to be debuged.
I havent tried WM 6.0 but from what I read on here it seems that 6.0 is more stable.
Does any one know if this route will work for WM 6.0?
If so does any one know which file do you download?
Will this set up work with WM 6.0?
http://omnifusionhosting.net/treo750/
http://forum.ppcwarez.org/viewtopic.php?f=221&t=41062
Well, WM6.0 is more stable, for one thing I had a faster battery drain with WM6.1 than I did with 6.0.
As mentioned earlier, some missing stuff like voice command, but one thing I thought wouldn't be there was messaging. For some reason that Messaging is half annoying me.
While I'm at it, anyone know how to backup SMS messages? That Messaging app is just keeping them to itself.
I know there are other methods out there for achieving the same thing. And I have touched on a few "after thoughts" in the actual process of loading the image to the phone. If these can be confirmed, please feel free to update these instructions. After browsing many, many pages in forum after forum I was unsuccessful in finding anything detailed enough from start to finish. So I decided to write this up!
These instructions work for anyone who rooted using the "UnrEVOked" method such as that given at HTCEvoHacks.com. I have not tested these instructions with any other root method out there.
With a bit of practice, this method can be mastered and done in about 20 minutes (depending on how long you spend creating your splash image in PhotoShop)
For the sake of these instructions, all references and instructions dealing with PhotoShop are assuming you are using PhotoShop CS5. Commands may be slightly different on older versions of PhotoShop, so it may take a few extra clicks to find what you're looking for.
1. You can download custom boot images from the web, or create your own in PhotoShop using ANY sort of photo, graphics, text, or combination. You MUST make sure that the image size is set as the same for the EVO's screen resolution (480x800). For this reason, I would double check any image file you try to use prior to converting it for use with your phone.
2. Open your image file in Photoshop and make whatever tweaks or enhancements you like. Remember to "flatten" the image prior to saving it out if you have multiple layers in your file. You can use the next step to re-size the image first if you like, but depending on your current settings in PS it should not matter.
3. Right click the file window (the one that contains your image) and set the "Image Size" settings to a width of 480, and the height to 800. These measurements MUST be in pixels as well. If you have the "Constrain Proportions" box checked, you may not be able to tweak these individually without affecting the other. So uncheck that box and change the size settings. Click ok to close the box and the image will re-size within Photoshop.
4. After you have finished creating your custom image, flattening the image, and resizing it to fit on your phone's screen, it is time to save the file. Navigate to the "file" menu and click "save as". Here, you can choose where to save it, name it, and choose the file format. It's probably easier to go ahead and save it as "splash" now, so that you wont have to rename it later. Either way, this file MUST be named "splash" when we are in the final stages. Save it as the "BMP" format, and you will get a pop-up window for the BMP options. "File Format" should be set to Windows... and choose the depth option of 24 Bit. The "compress" and "Flip row order" boxes should be unchecked, and you do not need to go into any advanced settings. Once you have saved the file, You can close PhotoShop.
Now the File needs to be converted from the BMP format into an IMG file. This is so that the boot loader in your phone will see it when you flash it to your phone.
There are a few conversion tools out there, but I have found Splash Screen Creator to be the EASIEST way to convert the file with a few clicks.
The link to download this small program is here... http://www.addictivetips.com/?attachment_id=43073 ... and it is FREE!!! (I did not create this program)
1. Download the .zip package from the link above.
2. Extract the files. I found that creating a folder on my desktop to secure these files (and these files only) to be less of a headache.
3. After you have extracted the files, you are ready to convert your "splash.bmp" file. You MUST move this file into the same directory that you unzipped the Splash Screen Creator to. It will only find the bmp file in the same directory, which is why having its own folder is easier. Move your "splash.bmp" file to the same folder and open "RUN THIS ONE". This will open the program in a command prompt.
4. Choose option 1 to convert your existing .bmp file into the required .img file. The next option will ask if you would like to flash the file to your phone. This option is not necessary for these instructions, but I have read of others being successful. You can try this option, but if it fails, go on to the remaining steps.
5. Go ahead and close the program by pressing another key to exit. You should see your new "Splash.img" file in this same directory. Rename this as "splash1.img"
Now that I think of it, naming the BMP file to "splash1" prior to converting to the .img format may solve the error when trying to flash the file to the phone
within Splash Screen Creator. The img file MUST be name "splash1" prior to updating it in the boot loader in the next steps so it makes sense that the program would come up with an error at this point. I have not tested this theory at this time, but you are welcome to. If someone does test this, please update these instructions
to save from many unnecessary steps below!
Your next steps require access to your original "PC36IMG.zip" file that you used during your root process. If you do not have your original "PC36IMG.zip" file, you
can try to download one here... http://forum.xda-developers.com/showpost.php?p=8913849&postcount=156 ... I have not tested this file yet, but worth a shot if you dont have it.
1. Make a COPY of your "PC36IMG.zip" file and move it to your directory where you have worked with the custom splash files. This saves from getting confused between files and flashing the wrong one to your phone. You're also making a copy so that your original "PC36IMG.zip" file is NOT altered.
2. DO NOT unzip the file! Simply drag your "splash1.img" file over to your zipped "PC36IMG.zip" folder and copy it in there. If you get a prompt to overwrite an existing "splash" file, go ahead. Afterall, you are working with a copy of the PC36IMG.zip.
3. After you have added the "splash1.img" file into the "PC36IMG.zip" folder, you can now move the zipped folder over to your sd card. Make sure that it is the ONLY copy on your sd card, and that you have not placed it in any other directories. BOOT LOADER WILL NOT FIND IT IF IT IS IN ANOTHER FOLDER!!!
4. AT THIS POINT YOU WANT TO BE SURE YOU HAVE BACKED UP YOUR ROM!!!! YOU WILL LOSE YOUR CURRENT ROM AND DATA AFTER THE NEXT STEP!!!!
5. Reboot the phone into Boot loader by holding the volume down button and pressing power. The boot loader will find your "PC36IMG.zip" and ask you if you want to update. Press the volume up button to say YES! Grab a coffee, chug a beer, or take a piss, cause this step takes a few minutes.
6. Once the boot loader has finished it's update, reboot your phone. it will now display your new custom splash screen!!! (but you're not done yet)
Because you updated your "PC36IMG.zip" files in the boot loader, you have in effect re-flashed the stock rom (rooted of course) back to your phone.
Allow a few minutes for your phone to boot up, log into your g-mail account (so that you have access to the market), and download Rom Manager (or your favorite backup manager), and restore back to your rom!
Like I said before, I have only done this on the HTC EVO that has been rooted using UnrEVOked through the process explained on HTCEVOHacks.com. I have no idea if this process will work with other configurations, and I accept no responsibility for the outcome of your actions!!!!
cool bro thanks
Thanks very helpful