I’ve recently had the “pleasure” of updating my phone via the infamous NSU. I was really scared of bricking my phone and I made sure I followed the instructions EXACTLY as specified by the NSU. Even though I was precise, there were problems. I mean, the f/w update went well, but the hard disk got corrupted. That meant transferring nearly 2 gigs of songs, re-creating the playlists, installing all the apps and so on.

The main cause of concern in the entire update process is said the be the cable and the connector. Loose connector/bad cable == bricked phone in most of the cases. Another reason why people have ended up with bricked phones is due to small things like for example, they tend to forget to change the profile to the General Mode. So if you think about it, the problem lies with people and the hardware. The software looks like its inherently bug-free, right?

WRONG!

If you look at post here on HowardForums, Nokia says that they haven’t released any updates for the N93 because of “issues with the NSU” which results in bricked N93s.

So in a process which can be described as: Phone -> Cable -> NSU software, not one of these components can be called reliable. So a user can end up with a bricked phone and not know the exact reason as to why it was bricked. A user CAN ensure that the settings in the phone are correct, he CAN ensure that the cable is good and the connectors are not loose, but there is NO way a user can safeguard against bugs in a software he knows nothing about.

This entire process is just too risky for a normal user. I depend on my phone for my day-to-day activities. I cannot imagine the effects of a bricked phone, considering I don’t have a backup phone these days.

I think Nokia should just allow users to download the firmware files and then move them via BT/IR/usb to the phone. Design a symbian updater that works on the phone itself which can change the profiles and settings as it is run, eliminating majority of the issues that lead to bricked phones.

Or if they won’t us to have the the firmware, at the very least,  enable FOTA updates.

I’ve been working on creating a comprehensive list of freeware applications for S60 3rd edition phones. The list has gotten pretty big now and I try to update it as frequently as I possibly can. So if you have any suggestions or if you want an application to be added to the list, do leave me a comment or send me an email.

Member rivvah from HowardForums has posted a comprehensive list of s60v3 product codes for various Series60 3rd edition phone models. For example, my N91’s code is:

N91 RM-43
0535291: English, Chinese

The part “RM-43″ can be obtained by pressing *#0000# on your S60 phone. The number “0535291″ can be found under the battery. The languages can be found in the Menu under Tools->Settings->Phone-> General.

This guide serves as a great resource for people who buy unlocked phones from retailers which sell imported phones. It allows a person to verify if the phone given to him has the correct firmware or if its firmware has been changed/modified. For example, A Nokia E50 RM-170 with a product code of 0534465 must be an Indian BLACK edition. So if you find a phone with that product code, but different languages in it, you can be sure its firmware has been modified. Please do note that though the list is fairly extensive, it is not complete. The N91 code I posted above is not on that list. However, it is a great resource, definitely bookmarked for future use.

The Nokia E50 blog has posted live pics of the recently released E50 Metal Black Edition. The phone looks amazing! I’m seriously considering buying one for myself. Black really looks good on the E50.

I’ve just noticed that s60.com has a downloads section on their page that lets you view applications compatible with your s60 phone. A good idea, its something that I’ve been working towards as well. The list shows you shareware and freeware apps.