Active Topics

 


Reply
Thread Tools
Posts: 131 | Thanked: 22 times | Joined on Sep 2012 @ India
#51
Originally Posted by neel.basu View Post
But I don't see any hint to track. Now I've started to think, its a hardware issue. and The problem is there is no way to make sure. where the problem is. as bootloader can pick up my imei correctly. and I can see it in /proc/cmdline.
As I said I also got exactly same issue but after flashing chinese cmt only my phone shows IMEI and works sometimes (50% of times)
So I don't think issues is with hardware.
 
Posts: 131 | Thanked: 22 times | Joined on Sep 2012 @ India
#52
Originally Posted by Hurrian View Post
I think that at some point, firmware versions have been mismatched on-device.

Using the PR_LEGACY 006 firmware, add "--flash-only=rootfs" to the end of that command line, and on the second run to flash the eMMC, remember to have "--flash-only=emmc".

Don't reboot yet.

Now download the PR1.3 PR_LEGACY 280 rootfs, and "--flash-only=cmt-mcusw".

You should now have a device with PR1.3 006 on the APU, and PR1.3 280 on the MCU (and the MCU's swcert should match with the MCU firmware)

(IIRC mismatching APU and MCU firmware is allowed. In case you get a MALF, flash the PR1.3 Open Mode kernel and follow these instructions)
Many Thanks for reply.
Can you please explain "Now download the PR1.3 PR_LEGACY 280 rootfs"

I could not understand what rootfs is? Or is it just typo?
Do you mean to download this file?
Dfl61 Harmattan 40.2012.21-3.280.04.1 Pr Legacy 280 Arm Rm-696 Prd Signed.bin

Is file is from same product code which is mentioned at back of SIM tray?

I got following error

c:\Program Files\Nokia\Flasher>flasher -f -F main_ce40.bin --flash-only=cmt-mcusw
flasher 3.12.1 (Oct 6 2011) Harmattan
ERROR: Valid --flash-only options: nolo,kernel,moslo,initfs,rootfs,cmt,mmc,tar
ERROR: Error processing option
So I used cmt option as specified in fflashing post, but I got following error.
c:\Program Files\Nokia\Flasher>flasher -f -F main_ce40.bin --flash-only=cmt
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_001
Image cert-sw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 66 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[_] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3315 kB/s]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[f] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3315 kB/s]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Update content failed to verify against cert: SW certificate not updated
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Update content failed to verify against cert: SW certificate not updated
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
MTC_NOS_READY not received
MTC_NOS_READY not received
MTC_NOS_READY not received
CMT RFS failed
[Pipe 2] Finishing in error state with status 1
========================================

ERROR: Failed to flash images
Then I tried chinese cmt and it was finishing at 75% for cmt-mcusw before giving following error.

c:\Program Files\Nokia\Flasher>flasher -f -F main_ch.bin --flash-only=cmt
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_003
Image cert-sw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 69 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[_] cmt-mcusw [finishing 75 % 6050 / 6050 kB 3465 kB/s]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[f] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3465 kB/s]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
MTC_POWER_OFF not received
CMT RFS failed
[Pipe 2] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

Last edited by suyog; 2013-05-14 at 21:39.
 
Posts: 1,225 | Thanked: 1,905 times | Joined on Feb 2011 @ Quezon City, Philippines
#53
That's quite the odd problem.

Your device has PR 003 firmware and has Chinese CMT firmware.

And flasher -i shows all the information properly, yet Harmattan can't seem to talk to the BB5?

At this point I'd be inclined to install the Chinese firmware to match, but the Chinese firmware sucks. (Don't do it yet!)

Perhaps other forum members can get your 003 firmware device talking to your CMT.
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
 
Posts: 131 | Thanked: 22 times | Joined on Sep 2012 @ India
#54
Originally Posted by Hurrian View Post
That's quite the odd problem.

Your device has PR 003 firmware and has Chinese CMT firmware.

And flasher -i shows all the information properly, yet Harmattan can't seem to talk to the BB5?

At this point I'd be inclined to install the Chinese firmware to match, but the Chinese firmware sucks. (Don't do it yet!)

Perhaps other forum members can get your 003 firmware device talking to your CMT.
Many Thanks for reply.
After this recent cmt flash , error showed as as shown in log but earlier cmt only flash with chinese fw used to give success. i am not sure if this means anything.
Also I noted very strange thing. When I don't put SIM in tray or put phone in flight mode , it shows IMEI in About->settings
But as soon as i put SIM card it disappears.

Earlier when chinese fw smt flash used to be successful, it used to work 50% of times and then suddenly lose network.
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#55
Have you tried it with another simcard, does the behaviour change?
 
Posts: 131 | Thanked: 22 times | Joined on Sep 2012 @ India
#56
Originally Posted by juiceme View Post
Have you tried it with another simcard, does the behaviour change?
Yes, I tried with 3 different SIM cards from 3 operators and still same issue.
 
Posts: 32 | Thanked: 7 times | Joined on Apr 2013
#57
Originally Posted by Hurrian View Post
I think that at some point, firmware versions have been mismatched on-device.

Using the PR_LEGACY 006 firmware, add "--flash-only=rootfs" to the end of that command line, and on the second run to flash the eMMC, remember to have "--flash-only=emmc".

Don't reboot yet.

Now download the PR1.3 PR_LEGACY 280 rootfs, and "--flash-only=cmt-mcusw".

You should now have a device with PR1.3 006 on the APU, and PR1.3 280 on the MCU (and the MCU's swcert should match with the MCU firmware)

(IIRC mismatching APU and MCU firmware is allowed. In case you get a MALF, flash the PR1.3 Open Mode kernel and follow these instructions)
What I am fearing is.flasher -i is reporting I've 006. Now If I flush CMT with 280 and that doesn't work, wouldn't it block downgrading CMT in future ?

So is there any way to know which version cmt is running ? (If cmt and rootfs run two different versions)
 
Posts: 131 | Thanked: 22 times | Joined on Sep 2012 @ India
#58
Yes, I would also like to know if there is any way to find these base software details currently being used on phone.

Anyone?
 
Posts: 32 | Thanked: 7 times | Joined on Apr 2013
#59
well what version its using you can find with flasher. But as Some people mentioned above CMT may have a different version. The question is How to know what version CMT is using.Is there a way to raw read cmt or mcusw ?
 
Posts: 131 | Thanked: 22 times | Joined on Sep 2012 @ India
#60
Originally Posted by neel.basu View Post
well what version its using you can find with flasher. But as Some people mentioned above CMT may have a different version. The question is How to know what version CMT is using.Is there a way to raw read cmt or mcusw ?
I am also talking about same , I meant base software = cmt etc.
 
Reply


 
Forum Jump


All times are GMT. The time now is 05:08.