maemo.org - Talk - Flashing problem 2017

maemo.org - Talk (https://talk.maemo.org/index.php)

- MeeGo / Harmattan (https://talk.maemo.org/forumdisplay.php?f=45)

- - Flashing problem 2017 (https://talk.maemo.org/showthread.php?t=100009)

Re: Flashing problem 2017

Quote:

Originally Posted by enes (Post 1537769)

It vibrates and the led is on but then it turns of itself.

When the LED goes off, unplug the charger and plug it back in. The cycle will repeat and each time the battery gets a few drops of power before it switches off. After doing that many times, those drops add up enough for the phone to stay on and start charging properly. I have rescued mine from a deep discharge a few times like that.

Be warned, it may take a whole day of plugging and unplugging. I can only do it at work :)

Re: Flashing problem 2017

I will try that later, but i think it had to be caused by something else since the problem occured when the original battery was in use.

Meanwhile, i've tried the solution that you proposed in #6 reply, and this is the result:

HTML Code:

D:\Documents\Desktop>c:



C:\>cd "Program Files\Nokia\Flasher"



C:\Program Files\Nokia\Flasher>flasher -i

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.



Suitable USB interface (bootloader/phonet) not found, waiting...

Found device RM-696, hardware revision 1603

NOLO version 2.3.6

Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.341.2_PR_341

Success



C:\Program Files\Nokia\Flasher>flasher -f -F 05E93654_DFL61_HARMATTAN_40.2012.21

-3.341.2_PR_LEGACY_341_ARM_RM-696_PRD_signed.bin --erase-user-data=secure -F nom

aps.bin --erase-mmc=secure

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.



Suitable USB interface (bootloader/phonet) not found, waiting...

Found device RM-696, hardware revision 1603

NOLO version 2.3.6

Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.341.2_PR_341

Sending ape-algo image (7103 kB)...

100% (7103 of 7103 kB, avg. 18354 kB/s)

Suitable USB interface (phonet) not found, waiting...

Ping attempt 1 (250 ms)

Server application: 1.7.2

Found product RM-696 rev. 1603

Server implements softupd protocol version 1.8

Warning: user data may reside on MMC. In that case the MMC is unnecessarily eras

ed twice.

Charging battery, 10 % battery level (11 % required). Ctrl-c to exit

Battery level 11 %, continuing.

Erasing, this may take a while.

Erase done.



Battery level 15 %, continuing.

Erasing, this may take a while.

Erase done.

Image SW version DFL61_HARMATTAN_40.2012.21-3.341.2_PR_341

Image moslo not present

Image tar skipped

Image config skipped



Battery level 20 %, continuing.



    image        [state    progress         transfer     flash speed]

---------------------------------------------------------------------

[x] cert-sw      [finished   100 %       1 /       1 kB      NA     ]

[ ] cmt-2nd      [pending      0 %       0 /       0 kB      NA     ]

[ ] cmt-algo     [pending      0 %       0 /       0 kB      NA     ]

[ ] cmt-mcusw    [pending      0 %       0 /       0 kB      NA     ]

[x] xloader      [finished   100 %      23 /      23 kB      NA     ]

[x] secondary    [finished   100 %      94 /      94 kB      NA     ]

[ ] kernel       [pending      0 %       0 /       0 kB      NA     ]

[ ] rootfs       [pending      0 %       0 /       0 kB      NA     ]

[ ] mmc          [pending      0 %       0 /       0 kB      NA     ]

ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error



    image        [state    progress         transfer     flash speed]

---------------------------------------------------------------------

[x] cert-sw      [finished   100 %       1 /       1 kB      NA     ]

[x] cmt-2nd      [finished   100 %      95 /      95 kB      NA     ]

[x] cmt-algo     [finished   100 %     789 /     789 kB      NA     ]

[x] cmt-mcusw    [finished   100 %    6050 /    6050 kB    3091 kB/s]

[x] xloader      [finished   100 %      23 /      23 kB      NA     ]

[x] secondary    [finished   100 %      94 /      94 kB      NA     ]

[x] kernel       [finished   100 %    2714 /    2714 kB    2594 kB/s]

[f] rootfs       [pending      0 %       0 / 1170273 kB      NA     ]

[-] mmc          [pending      0 %       0 /       0 kB      NA     ]

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

mmc: sfdisk returned status 1

mmc: Could not exec 'tune2fs -L rootfs /tmp/sudmmc27XRNw/internal0p2'

mmc: Could not remove mount directory /tmp/sudmmc27XRNw/mnt: No such file or dir

ectory

[Pipe   5] Finishing in error state with status 1

========================================



ERROR: Failed to flash images



C:\Program Files\Nokia\Flasher>

Re: Flashing problem 2017

That was helpful to a degree, at some point did you ever try installing Nitdroid?

Could you run this command and see what errors it elicits?

HTML Code:

flasher -F 05E93654_DFL61_HARMATTAN_40.2012.21

-3.341.2_PR_LEGACY_341_ARM_RM-696_PRD_signed.bin -f --no-preserve

Unfortunately it does now point towards HW problem upon flash memory which is not what you wanted to hear as here:http://talk.maemo.org/showpost.php?p...7&postcount=23

Re: Flashing problem 2017

HTML Code:

C:\Program Files\Nokia\Flasher>flasher -F 05E93654_DFL61_HARMATTAN_40.2012.21-3.

341.2_PR_LEGACY_341_ARM_RM-696_PRD_signed.bin -f --no-preserve

flasher 3.12.1 (Oct  6 2011) Harmattan

Warning: --no-preserve is not recommended, instead use erase commands

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. 1603

Server implements softupd protocol version 1.8

Image SW version DFL61_HARMATTAN_40.2012.21-3.341.2_PR_341

Image moslo not present

Image mmc not present

Image tar skipped

Image config skipped



Battery level 97 %, continuing.



    image        [state    progress         transfer     flash speed]

---------------------------------------------------------------------

[x] cert-sw      [finished   100 %       1 /       1 kB      NA     ]

[ ] cmt-2nd      [pending      0 %       0 /       0 kB      NA     ]

[ ] cmt-algo     [pending      0 %       0 /       0 kB      NA     ]

[ ] cmt-mcusw    [pending      0 %       0 /       0 kB      NA     ]

[x] xloader      [finished   100 %      23 /      23 kB      NA     ]

[x] secondary    [finished   100 %      94 /      94 kB      NA     ]

[ ] kernel       [pending      0 %       0 /       0 kB      NA     ]

[ ] rootfs       [pending      0 %       0 /       0 kB      NA     ]

ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error



    image        [state    progress         transfer     flash speed]

---------------------------------------------------------------------

[x] cert-sw      [finished   100 %       1 /       1 kB      NA     ]

[x] cmt-2nd      [finished   100 %      95 /      95 kB      NA     ]

[x] cmt-algo     [finished   100 %     789 /     789 kB      NA     ]

[x] cmt-mcusw    [finished   100 %    6050 /    6050 kB    3197 kB/s]

[x] xloader      [finished   100 %      23 /      23 kB      NA     ]

[x] secondary    [finished   100 %      94 /      94 kB      NA     ]

[x] kernel       [finished   100 %    2714 /    2714 kB    1927 kB/s]

[f] rootfs       [pending      0 %       0 / 1170273 kB      NA     ]

Fetching error list:

========================================

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

bb5_rdc_cert_read failed

bb5_rdc_cert_read failed

mmc: sfdisk returned status 1

mmc: Could not exec 'tune2fs -L rootfs /tmp/sudmmcUnnbkk/internal0p2'

mmc: Could not remove mount directory /tmp/sudmmcUnnbkk/mnt: No such file or dir

ectory

[Pipe   4] Finishing in error state with status 1

========================================



ERROR: Failed to flash images



C:\Program Files\Nokia\Flasher>

I've never tried anything like that, thats why i'm so surprised since i haven't mess with the system at all, at least i don't remember doing that. So it is not possible to erase the whole system from n9 and just install a new one?

Addition: Now, when i turn on my n9 it shows the warning about modified software and the led (camera flash) on the back of the case is red.

Re: Flashing problem 2017

Sorry to say but this looks like a faulty eMMC (hardware).

Or to give you some hope maybe a faulty download. Did you check the md5sum of downloaded image file?

Re: Flashing problem 2017

I didn't, can you please tell me how to do it?

Re: Flashing problem 2017

Quote:

Originally Posted by enes (Post 1537810)

I didn't, can you please tell me how to do it?

It would seem from zxcvbnm3230's site (Silma's Lair: https://silma.tk/soft/) that for 341 md5: 6086C4A2847969D223A9C9DB1AFF5168

You would need something like Md5Checker or Little MD-5-Creator for Windows.

Re: Flashing problem 2017

Quote:

Originally Posted by enes (Post 1537810)

I didn't, can you please tell me how to do it?

linux
md5sum FILENAME

windows
fciv FILENAME (md is default)
you can also.configure the.command md5sum as.a.symmink to fciv with mklink...

Re: Flashing problem 2017

I've checked it and it shows the exact same result as the one that aspergerguy gave me, which is :6086C4A2847969D223A9C9DB1AFF5168.

Re: Flashing problem 2017

Then.... :(

Last chances (but not much hope, near zero):
try different USB port (on desktops not a front port), not via a hub
try different cable
try different operating system
try different computer

That sometimes helped in earlier flashing times.
That