Really close up! De tres tres pres!
20091226
20091225
20091218
20091216
20091205
20091204
20091201
Fixing a Nokia XM 5800 which has lost the calendar display on the home page
Several users of the Nokia XpressMusic 5800 have had the problem where, on the home screen of the phone, suddenly, for no apparent reason, the calendar doesn't show up anymore... and furthermore, it's not even listed in the list of available home screen apps in the configuration of the phone.
This bug is due to a corrupted system file : c:\private\10202BE9\persists\10275102.cre
Unfortunately, as this is a system file, it's not possible to delete it as a normal user. You need to circumvent Symbian OS's file system protection.
This isn't hard.
But this means DOES require that you hack your phone.
First, you need to generate a CERT and a KEY for your phone (based on the IMEI) using the site here : http://www.s60certkey.com/ . This process is simple... but it takes about 24H to get the certs. Be patient.
Then, with this key, and the tool(SignTool2.2) provided on that same site, you will have to sign the phone hacking application called HelloOX2 which you can get from here : http://helloox2.com/ (you can get a signed version there, but you have to pay for it).
Run HelloOX2 and follow the instructions. Then run the newly installed ROMPatcher (installed by HelloOX2). Select all and set to automatic. Reboot your phone.
Now you can install one of the various filesystem viewers around (Y-Browser - http://www.drjukka.com/YBrowser.html - is available for free and is quite good, but I've just discovered Swiss Manager Pro from - http://cellphonesoft.com/ - which for a small price is fantastic).
With those tools, you can easily navigate to c:\private\10202BE9\persists\ and delete the file 10275102.cre... after which you reboot your phone (simple turn off then on) and you are set.
Of course, if Nokia would just go ahead and FIX the damn bug by writing a small app that deleted that file on reboot (I haven't seen negative effects of having deleted it myself)... this hacking wouldn't be required. This has been reported by many users on the forums, as well as directly to Nokia support. Since OS version 10.x of the XM 5800. We've had updates to 20.x, 30.x and now 31.0.101... still not fixed. What are they waiting for?
Gilles.
This bug is due to a corrupted system file : c:\private\10202BE9\persists\10275102.cre
Unfortunately, as this is a system file, it's not possible to delete it as a normal user. You need to circumvent Symbian OS's file system protection.
This isn't hard.
But this means DOES require that you hack your phone.
First, you need to generate a CERT and a KEY for your phone (based on the IMEI) using the site here : http://www.s60certkey.com/ . This process is simple... but it takes about 24H to get the certs. Be patient.
Then, with this key, and the tool(SignTool2.2) provided on that same site, you will have to sign the phone hacking application called HelloOX2 which you can get from here : http://helloox2.com/ (you can get a signed version there, but you have to pay for it).
Run HelloOX2 and follow the instructions. Then run the newly installed ROMPatcher (installed by HelloOX2). Select all and set to automatic. Reboot your phone.
Now you can install one of the various filesystem viewers around (Y-Browser - http://www.drjukka.com/YBrowser.html - is available for free and is quite good, but I've just discovered Swiss Manager Pro from - http://cellphonesoft.com/ - which for a small price is fantastic).
With those tools, you can easily navigate to c:\private\10202BE9\persists\ and delete the file 10275102.cre... after which you reboot your phone (simple turn off then on) and you are set.
Of course, if Nokia would just go ahead and FIX the damn bug by writing a small app that deleted that file on reboot (I haven't seen negative effects of having deleted it myself)... this hacking wouldn't be required. This has been reported by many users on the forums, as well as directly to Nokia support. Since OS version 10.x of the XM 5800. We've had updates to 20.x, 30.x and now 31.0.101... still not fixed. What are they waiting for?
Gilles.
Inscription à :
Articles (Atom)