Nokia E62: Be aware of Product Code 0536911 (China Default) changes

[l0h]

Hi,

Just want to share with you an experience I got and may be forestall you from making the same mistake.

Here is my story...

Originally I had a Cingular branded (Product Code: 0530924) Nokia E62. Then I updated it to Rogers (Product Code: 0538175) and finally to US_Generic firmware (Product Code: 0524513). I did several upgrades... back and force, but finally ended up with US_Generic firmware as it was the best choice (no Java application issue, no Operator-specific modifications, etc.) and works just great.

So, two days ago I found a Product Code 0536911 which was described as "China Default". So, knowing that I always can return back to US_Generic firmware (all I need is to change a product code in NSS and then let NSU do it work), I did change the Produc Code to 0536911 and NSU successfully loaded "China Default" firmware to my phone. After playing with new firmware for about a 10 min., I realized that I do not see anything interesting in "China Default" firmware and decided that I want return back to “US_Generic” version.

So, I changed Product Code back to 0524513 and run NSU. Everything went OK until the final point... At that point I got a message that NSU "Failed to verify communication" with my Nokia. Needles to say, that I got a dead phone after that.

Well, I’ve already been in a "dead phone" situation before, so I knew how to proceed.
I run Phoenix and chose "Dead Phone" firmware update option. Then I told Phoenix to update firmware to “US_Generic”. Everything started OK, but at the final point I got again notification that communication with the phone was lost.

Here is the end of Phoenix log:
....
…
…
07:57:02 ThreadID: 0xB00 -Debug-Cmt->Programming: 93%
07:57:07 ThreadID: 0xB00 -Debug-Cmt->Programming: 94%
07:57:12 ThreadID: 0xB00 -Debug-Cmt->Programming: 95%
07:57:17 ThreadID: 0xB00 -Debug-Cmt->Programming: 96%
07:57:22 ThreadID: 0xB00 -Debug-Cmt->Programming: 97%
07:57:27 ThreadID: 0xB00 -Debug-Cmt->Programming: 98%
07:57:32 ThreadID: 0xB00 -Debug-Cmt->Programming: 99%
07:57:36 ThreadID: 0xB00 -Debug-Cmt->Programming: 100%
07:58:00 ThreadID: 0xB00 -Debug-Cmt->Sending reboot command for cmt
07:58:00 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 1 of 50
07:58:06 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 2 of 50
07:58:08 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 3 of 50
07:58:11 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 4 of 50
07:58:13 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 5 of 50
07:58:16 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 6 of 50
07:58:18 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 7 of 50
07:58:21 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 8 of 50
07:58:23 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 9 of 50
07:58:26 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 10 of 50
07:58:28 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 11 of 50
07:58:31 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 12 of 50
07:58:33 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 13 of 50
07:58:36 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 14 of 50
07:58:38 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 15 of 50
07:58:41 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 16 of 50
07:58:43 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 17 of 50
07:58:46 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 18 of 50
07:58:48 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 19 of 50
07:58:51 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 20 of 50
07:58:53 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 21 of 50
07:58:56 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 22 of 50
07:58:58 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 23 of 50
07:59:01 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 24 of 50
07:59:03 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 25 of 50
07:59:06 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 26 of 50
07:59:08 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 27 of 50
07:59:11 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 28 of 50
07:59:13 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 29 of 50
07:59:16 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 30 of 50
07:59:18 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 31 of 50
07:59:21 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 32 of 50
07:59:23 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 33 of 50
07:59:26 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 34 of 50
07:59:28 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 35 of 50
07:59:31 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 36 of 50
07:59:33 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 37 of 50
07:59:36 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 38 of 50
07:59:38 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 39 of 50
07:59:41 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 40 of 50
07:59:43 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 41 of 50
07:59:46 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 42 of 50
07:59:48 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 43 of 50
07:59:51 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 44 of 50
07:59:53 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 45 of 50
07:59:56 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 46 of 50
07:59:58 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 47 of 50
08:00:01 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 48 of 50
08:00:03 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 49 of 50
08:00:06 ThreadID: 0xB00 -Debug-Cmt->Trying to verify communication 50 of 50
08:00:06 ThreadID: 0xB00 -Debug-Cmt->Failed to verify communication.
08:41:38 ThreadID: 0xE94 -------FLS device not detected


Please notice, that two different applications (NSU and Phoenix) returned the same error.

So, what’s next? Well, I did try "Dead Phone" firmware update option for Rogers and Cingular firmwares, but I got exactly the same error at the end of Phoenix Programming: "Failed to verify communication". Just because of curiosity I tried "Dead phone" option with the same “China Default” firmware and Phoenix was able programming my dead phone successfully.

Wow! That was a relief… But that means I stuck again with “China Default” firmware. Well, at least at this point I had a working phone and I decided to try NSU to get back to US_Original firmware. I changed my Product Code to US_Generic version and run NSU…

Should I say how surprised I was when almost at the end of NSU firmware updating, I got _exactly_ the same message saying that NSU failed to communicate with my phone. It was especially interesting, that I did try that update using another computer (just to eliminate any possible problems with the original computer where I started my tests).

To make the long story short... I did return to “China Default” firmware (using Phoenix) again and tried NSU with Rogers and Cingular Product Codes. Both of them failed at the same point with the same error. But if I try NSU to update to the same “China Default” firmware, NSU works fine and update goes without any problems.

The bottom line is that today I'm stuck with "China Default" firmware (Product Code: 0536911) and I do not see any other way to be able get rid off it without using a hardware flashing device (like Jaff) or going to Nokia Service. I would leave it as a final solution in case I will not be able to fix the issue myself.

I hope it was helpful. I will appreciate any good technical thoughts (sorry, but no dilettante advices needed) on that matter.

Regards,
l0h

[heydi]

Your action is considered as downgrade, it will lead to a deap phone after flash. However, if you are lucky you can get your dead phone revived back to the original version in the NSC (provided that the NSC person didn't notice you had changed the product code before).

[da123]

Originally Posted by heydi

Your action is considered as downgrade, it will lead to a deap phone after flash. However, if you are lucky you can get your dead phone revived back to the original version in the NSC (provided that the NSC person didn't notice you had changed the product code before).

Why is it a downgrade? Both product codes show version 2.0618.06.17.

[tbo2k]

hi there,

to me happened the same when updating n73 from 2.0 default to 3.0 Music edition.
After a while when i looked closer, i saw that the device is in service mode (no background light). I removed all cables (power and usb), then removed the Acc and waited a minute. After that I reassambled the accu to the device and startet the phone again with 3 seconds on power. After that it worked normaly but it did non correctly applied the language settings (it used default englisch) like before. But everything else worked fine...

[boonkang]

Originally Posted by l0h

Hi,


The bottom line is that today I'm stuck with "China Default" firmware (Product Code: 0536911) and I do not see any other way to be able get rid off it without using a hardware flashing device (like Jaff) or going to Nokia Service. I would leave it as a final solution in case I will not be able to fix the issue myself.


Regards,
l0h

Thank you for shairng your experience.
Wonder any problem with the "China Default" firmware (Product Code: 0536911) ? I assume that beside being able to use chinese language (input and output) you can still use English on your cellphoen. So what is the problem ?