Symbian-Developers
Symbian S60 V5/3/Legacy => S60v3 Forum => Topic started by: lampadinac on June 07, 2014, 12:32:42 pm
-
Hy.
I hope this is the right section in order to ask my question.
after a backup of all the contents of the phone I did a firmware update via NSU seemed to be proceeding nomally but at about 30% of the procedure the transfer remain 'blocked everything with the white screen. I tried in vain attempts to restore without success. The product code seems to be 0587783 (RM-573) and the firmware version is the 21.005. I then tried to do the 'update with Phoenix with software update and refurbish the answer is' always an error message that says that the firmware I'm trying to update the 21 005 is older than the one currently on your phone
" The flashing failed. Do you want to retry the flashing?
HRESULT 0x84210027 (-2078212057)
Firmware: Firmware updating failed. Error 0x8401227A - Flash: Phone reported
that it does not allow to flash SW becasue it is older than existing." .
It seems as if for some reason the phone will not accept anymore update because the updates the new firmware version (21 005) is older than the one installed on the phone. From information found on the web to me is that on that type of apparatus the 21 005 is the last and most updated firmware avalaible.
Can I do something to revitalize it? And reload the backup.
At the moment the phone is stuck with white screen and normally does not turn on anymore. Phoenix as Dead phone in refurbish turn on the white screen restarts and initializes it as to flash it but then hangs with the error message mentioned earlier.
I also tried the NSS but it always fails and does not identify the phone. In the case of NSS I get the feeling that the problem is the not appropriate driver.
How do I solve the problem ?
Thank you and have you a good day.
-
When you use Dead phone USB flashing and start the flash, when it tells you to press power on the phone, don't do it.
Instead, remove the battery, insert the USB cable, start the flash and when it tells you to insert the USB cable and press power, just insert your battery and press the OK button.
-
Hy Matthew,
tks for your quick answer. I have tried your suggestion but it is doing exactly the same with the same error message.
Any other suggestion to try ?
Tks
-
Could you please post screenshots of your flashing files (folder, detail view) and the error message from Phoenix?
Also, what is your PC's operating system?
-
Hy Matthew,
operating system Windows 7 Enterprise 32 bit.
Attached the 3 screenshots.
Tks
-
Is your phone really off? You shouldn't get an error like that in dead USB mode... Could you please expand the dialogue box in the third screenshot?
EDIT: Typos
-
Hy Matthew,
This is all the log of the dialog box and the 2 screenshot after a part of the log
"Flashing started
Creating product data items list
Product data items list created
Backup not required
Flashing phone
Initializing
Scanning image files...
Waiting for USB device...
Loading secondary boot code: 14976 bytes
Secondary boot loaded
Loading update server code: 2273314 bytes
Update server loaded
Asic CMT: Verifying communication to device...
Asic CMT: Verifying communication to device...
Error ADL Loader: Phone reported Downgrade not possible. Flash a newer SW version
Protocol 1: Error during Negotiation. Unable to flash.
Unable to flash phone 0x8401227A
Starting to recover the phone
Recovering phone
Initializing
Cannot perform recover from error: 0x8401227A, ADL_LDR_DOWNGRADE_NOT_POSSIBLE_ERROR
ERROR: Unable to recover the product
ERROR: Product recovery failed
Unable to set the phone to flash mode. Unable to flash."
Tks
-
Hi Matthew,
i have tried again but now i have a different output screenshot.
May be the battery is fully discharged ? Can i attach the power supply ?
One time appear an error to load the driver "Nokia USB flashing Parent".
Attached the 2 new screenshot.
Tks
-
i wonder if NSU caused the problem when it was used to flash.
Are there any other phones' folders in the \\products\ directory on your PC?
Did you change anything in the Options menu before flashing?
Also, could you post screen captures in the image format rather than as PDFs in the future, please? PDF images don't scale very well on my phones.
Thank you :)
-
Hy Matthew,
in \\products\ directory there is just one forlder RM-573 with the files in the screen capture.
I did not change anything in Options menu because i know that downgrade is not possible.
Will be a pleasure for me next time to send you screen capture in jpg or doc extension or if you prefer in other format. Please let know which is preferable for you.
Any suggestion. My wife is very upset about this problem on her phone. She likes very much that phone and she doesn't want to replace it.
An information that may be useful. I think originally the phone had another product code because was TIM branded.
This may cause this problem ?
Tks
-
.jpg would be perfect - thank you :)
i looked up your product code in Nokia Care Suite and your v21.005 firmware is correct so i am as baffled as you are.
What is the product code under the battery?
Which version of Phoenix are you using and is it the cracked or original version?
-
Hy Matthew,
the product code under the battery is 0591004.
I tryed 3 version of Phoenix ( 2 new cracked 1 older original ) with the same result.
At the moment a cracked version at the file attached.
Tks
-
Your product code came back 20.007 so you certainly didn't downgrade.
i wonder if this is possibly because you flashed a vanilla firmware to a SIM-locked device. You might be in need of a flashing box to fix your device at this point, but since you are already bricked you might as well try flashing the original files. Move your existing files to another folder and download these:
http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/2/--FID--A0A22BTCABTNN/--LID--FiRe1297189417100/85EF7CD1_RM573_0591004_20.007_006.vpl (save this as RM573_0591004_20.007_006.vpl)
http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/2/--FID--A0A22LRCHSNHQ/--LID--FiRe1297189427976/50BE2235_RM573_0591004_20.007_006.dcp (save this as RM573_0591004_20.007_006.dcp)
http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/2/--FID--A0A22PCURNUYA/--LID--FiRe1297189429112/E6E67204_RM573_0591004_20.007_006.spr (save this as RM573_0591004_20.007_006.spr)
http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/2/--FID--A0A22OIOSOWOH/--LID--FiRe1297189430210/A53AB6F2_RM573_0591004_20.007_006_signature.bin (save this as RM573_0591004_20.007_006_signature.bin)
http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2010/1/--FID--A0A22GPCLNFNH/--LID--FiRe1263552236490/rm573_ENO_RoW_PI224_2009wk53v0.010.a.fpsx
http://nds2.fds-fire.nokia.com/p/d/fds_fire/mupd/rm573_20.007_prd_core.fpsx
http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2010/2/--FID--A0A22HEUHMLNO/--LID--FiRe1265538805894/rm573_20.007_prd_v26_01_euro4.fpsx
http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/2/--FID--A0A22LCUJCHMS/--LID--FiRe1297189418223/C92F89F3_rm573_20.007_prd_v205_05_TIM_IT.fpsx (save this as rm573_20.007_prd_v205_05_TIM_IT.fpsx)
http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/2/--FID--A0A22AGTOTQKW/--LID--FiRe1297189419383/C02BDA0C_RM573_20.007_003_U205.uda.fpsx (save this as RM573_20.007_003_U205.uda.fpsx)
i don't know if you did this before you installed Phoenix 2012.04, but you might want to uninstall everything Nokia (including Fuse drivers and PL-2303 USB-to-Serial), reboot and then install it all again (Nokia Suite/Care Suite 5.0/Phoenix (i suggest trying with 2011.46 first and if it doesn't work you can "update" to 2012.04 and try again). Go with Dead phone USB/Refurbish.
If it still doesn't work, a flashing box is your only way to get the phone back.
-
Hy Matthew,
thanks a lot for your help.
I fixed the problem with BB5 Easy Service Tool.
But at the end i have preferred to flash back again the firmware with Phoenix 2011\46.
Regards
-
Hy Matthew,
just one more aspect that looks like is happened after the reflashing but should be perhaps an hardware problem.
The key "P" of the keyboard doesn' t work anymore. My wife tells that before it was working.
My opinion is that's an HW problem of the keyboard and could be a coincidence happened during my job on the phone.
I'm really afraid to open the phone in order to fix the "P" key ( also if it is located at the peripheral top left corner of the keyboard ).
Do you have HW experience ? Which is your suggestion ?
Anyway there is another way with a virtual keyboard or other solution to enter the "P" character on the text ?.
Tks
My experience tells me " don't do it ! "
-
The key "P" of the keyboard doesn' t work anymore. My wife tells that before it was working.
Hello :)
Which firmware are you running right now? Is it the original or the "updated" one?
If you flashed an alternative firmware with a different keymap, the keyboard could go kaput (i have done it before :P).
Is 'P' the only trouble spot? Does the miniscule/majuscule work? What about a secondary function (if applicable)?
Does every other key work 100% correctly?
-
Hy Matthew,
i run the most updated original firmware (20.007) downloaded from the links indicated previously and related to the product code (0591004) on the label under the battery.
The " P" key looks like is the only one not working. Secondary function is working and shift miniscule/majuscule is working.
The error may be happenet during a previous update tentative with a different product code (0587783 21.005 firmware).
But anyway with the rigth firmware i could have the rirth keymap.
I don't think keymap is an urecoverable damage and just with "P" key ?
I have seen that Phoenix service software has some test function for keypad etc- Can i use it ?
Or can i do some other test ?
Tks
-
i meant 'Do the miniscule/majuscule/secondary function of the P button work?
On these two keyboard phones, P has no secondary function so i would only have to check p, P. Is it working in 3rd party apps? Have you tried checking it in a virtual keymapping app?
As far as the Phoenix keyboard tool - i've not used it before (i didn't even know about it). i will try that to see what it does, now :)
Have you tried flashing the phone again? i would try another Refurbish, if you have not already.
-
If you don't already have such an app -
[attachment deleted by admin]
-
Hy Matthew,
i tryed and cap, secondary function (is ' key) and p in third party software doesn't work. I have tryed a refurbish.
Unfortunately i don't know how is happened but i think that there is the " P " key broken !
I would like to load a virtual keyboard in order to try it to see if she can use in this way but i am not able to sign both of the two applications in the link.
I forgot it. There is a simple way to do it ?
Tks
-
i thought one of them didn't require a hacked installserver... My mistake. You can hack the device to install it following the tutorial here:
http://sdf.allstarsoftware.co.uk/s60v3-modding/(tutorial)-hacking-s60v3/
-
Hy Matthew,
tks a lot it's an important feature in order to install other applications.
I install the virtual keyboard but anyway there no way to have the " p " because if i have understood well you can remap the key but in order to program the new key for the character you can do only pressing it in a new position. I didn't find another way to select "p".
May be there is but i didn't find.
Any suggestion ?
-
i'm sorry, mate - the whole point of the app was to use as a test for your 'P' key's funtionality. We got our answer.
This is the point where, if it was my phone, i would gently (:D) strike the device as a last-hope effort to "unstick" the key. If it did not work, i would begin disassembling the phone to inspect the hardware a bit more in-depth and test any faulty circuit if possible - but i have tools and a spot of experience (plus a rather care-free attitude toward tech surgery and hardware modification).
The keys hold a semi-conductor which provides enough continuity to complete a circuit at each button and it isn't uncommon for just enough insulation in the form of dust, lint or dirt get under the key and render it ineffective. Sometimes, a tap can dislodge the obstruction, but it is generally an issue requiring the removal of the keymat and a bit of air to clean. i like to use a shop vacuum with a bristle attachment to more thoroughly clean the main board and components when i go to the trouble of taking the device apart.
If you aren't confident to try it, you can see if there are any disassembly/reassembly tutorials on YouTube or take it to a Nokia Care centre.
-
Try this site for service diagrams/schematics: http://www.cpkb.org/wiki/Nokia_6760_6790_Slide_service_manual_and_schematic_download
-
Hy Matthew,
tks for the help. I have downloaded schematics and service manual and i tryed to clean the "p" key but it is always broken. I have seen on the schematics that the they is in a matrix ( raws and columns ) with other keys that are working well and now i will try to disassemble entirly the keypad in order to check the trace connections. Should be the only hw problem.
-
Hy Matthew,
i fix the problem. It was an inductor labelled L2486 to be soldered.
My wife is happy !! But she says always that the "P" key was working before the software upgrade !!
Should be a coincidence !!!
Tks for your help.
-
Wow! You really got to dive deep into the phone!
Nice job and i'm glad you (and your wife) got the phone back in good working order :)
Thank you for posting progress reports and the resolution, mate - i appreciate that ;)
-
Hi Matthew,
it's a pleasure.
Tks for your help.