Esato Mobile
Sony Ericsson / Sony : Symbian phones : Images behind the preference icons
> New Topic
> Reply
< Esato Forum Index > Sony Ericsson / Sony > Symbian phones > Images behind the preference icons Bookmark topic
Page <  12

mixin Posts: > 500

a .mbm file is a collection of more than one BITMAP image in one single file. if you open the .mbm in the viewer on your p800, youll see that it is animated.... now if you could get some software that extracted the images, you can change one, and recompile it... then see what happens
--
Posted: 2003-08-15 10:20:00
Edit : Quote

mixin Posts: > 500

http://homepages.nildram.co.uk/~nicko/5icons.htm
any help?
--
Posted: 2003-08-15 10:28:00
Edit : Quote

kitp800 Posts: 221

nice one MixiN,

all we need now is that file manager that can ignore/bypass the Read only markers.


I'm using Colours Schemes by Psiloc as a theme editor and this adjusts all the default colours on the P800 indivually to my own spec.
I'm guessing that however it does it, it changes one of the .MBM files on the Z:\
If this is the case then it is possible to change the data on the ROM drives. Now, how do we get Psiloc to write a prog for changing the images on the P800??? Would this allow us to add an image behind the applications list aswell as the preference icons???
--
Posted: 2003-08-18 01:52:22
Edit : Quote

ShaneMcFarland Posts: 142

The color schemes can be replaced manually by replacing the file C:\system\data\colorscm.dat It is NOT on a ROM drive.
--
Posted: 2003-08-18 01:58:50
Edit : Quote

kitp800 Posts: 221

Shame,

does anybosy else have any ideas on how we can get around the Read Only problem?
--
Posted: 2003-08-18 02:09:30
Edit : Quote

Loa Posts: 31

Listen, gents, it's not going to work. While A: and Z: are not real ROM drives in that they can be written to when installing new firmware, as far as writing from the phone is concerned, it is truly read only.

SE have done this for some very sensible reasons:

- You get a backup if you f**k up your phone and need to start afresh
- You are protected from viruses which try to alter the base OS

Including certain types of memory to which the device cannot write is a common practice in mobile and embedded devices where you want an incorruptible fall-back.

The only way that I can see this idea working would be either to hack your own firmware and write that to the phone (probably not the easiest option), or put together some sort of hack which redirects any calls to these files to another location. The second option should be doable if someone understands how the OS accesses these files, but it is seriously low-level work!
--
Posted: 2003-08-18 02:16:28
Edit : Quote

cheese on beans on Posts: 49

sorry to interupt you guys but which app are you using to browse your 'A' and 'Z' drives?

[ This Message was edited by: cheese on beans on on 2003-08-18 08:45 ]
--
Posted: 2003-08-18 09:45:01
Edit : Quote

jpaul_martinez Posts: 162

i made a new flipkeypad.mbm using asobe photoshop and saving it a s a .bmp, then i converted it to a .mbm using a program like XNVIEW, but like everyone said, i cant get it back into the z:/system/apps/flipkeypad/flipkeypad.mbm, i was wondering what if you copied all the files into c:/custom/system/apps? you think theres any way around this?
--
Posted: 2003-08-18 12:36:35
Edit : Quote
Page <  12

New Topic   Reply
Forum Index

Esato home