| Author |
Images behind the preference icons |
Loa
Joined: May 28, 2003
Posts: 31
From: France
PM |
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! | |
|
cheese on beans on
Joined: Jul 31, 2003
Posts: 49
PM, WWW
|
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 ] |
jpaul_martinez
Joined: Aug 12, 2003
Posts: 162
PM |
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?
[addsig] | |
|
Access the forum with a mobile phone via esato.mobi
|
Posted: 2003-08-18 02:16
