maemo.org - Talk - Is it possible to revive this N950?

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

- Nokia N9 / N950 (https://talk.maemo.org/forumdisplay.php?f=51)

- - Is it possible to revive this N950? (https://talk.maemo.org/showthread.php?t=101140)

Re: Is it possible to revive this N950?

@Maemish: I've mirrored most harmattan sites, so search files and hashing them is easy now.
I has been given today emmc.bin file with:
10110330dc3f46ae6d538627b7e57fbcbda7a45b emmc.bin (sha1)
09dcf0ef8e83dc410e8f1a13b2d16715 emmc.bin (md5)
Not sure if it's file I've requested, and sender is also unsure of original name ;-)

But I'm worried I got bigger problem:

Quote:

sudo flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_RM680-OEM1-916_ARM.bin -F emmc.bin -f --no-preserve **SI
Smartcard authentication starts
ERROR:pam_pkcs11.c:252: Error setting configuration parameters
[sudo] password for badpixel:
flasher 3.12.1 (Oct 5 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.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 002, device address 033.
Device identifier: 357881040025571 (SN: N/A)
Found device RM-680, hardware revision 1124
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_3.2012.02-6_PR_RM680
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 11105 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 002, device address 034.
Device identifier: 357881040025571 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-680 rev. 1124
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_RM680
Image moslo not present
Image tar skipped
Image config skipped
Charging battery, 10 % battery level (11 % required). Ctrl-c to exit
Battery level 11 %, continuing.

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 ]
[_] cmt-mcusw [finishing 0 % 6008 / 6008 kB 3066 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 90 / 90 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2495 kB/s]
[_] rootfs [finishing 100 % 32768 / 762871 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 % 6008 / 6008 kB 3066 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 90 / 90 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2495 kB/s]
[f] rootfs [finishing 0 % 32768 / 762871 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/sudmmctXQ150/internal0p2'
mmc: Could not remove mount directory /tmp/sudmmctXQ150/mnt: No such file or directory
[Pipe 5] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

Re: Is it possible to revive this N950?

But I still do wonder if it's really related to cooked mmc and not messed partition table.

anyone knows how to restore original table and got correct mappings?

I's black n950 / RM680 in generally good condition (it got dent on case and volume buttons[very hard to press, but I guess I could buy casing cheaply from somebody with broken screen). I really loved my N9 and would like to adopt this phone too...

Re: Is it possible to revive this N950?

BTW, battery level drops to 5% from 11% after flash attempt. Is it possible that voltage drop from nearly-dead battery causes that?

Re: Is it possible to revive this N950?

What about open_kernel/ubiboot and specially MOSLO(all links are dead) for N950? (can I used files dedicated for N9, or special builds are needed?)

about restoring parition table, as I understand sfdisk can be used from host device. Am I right?

Re: Is it possible to revive this N950?

So I guess my mmc is cooked too and heating anything inside using soldering hot air pump would not fix it easily?

Quote:

[ 4.573364] mmc_queue_do_make_request process file-storage (pid 218), read to sector 0, sectors 8
[ 5.276947] mmcblk0: error -110 transferring data, sector 0, nr 8, card status 0x0
[ 5.278961] mmcblk0: error -110 sending stop command, response 0x0, card status 0x0
[ 5.286712] end_request: I/O error, dev mmcblk0, sector 0
[ 5.292053] Buffer I/O error on device mmcblk0, logical block 0
[ 5.298614] mmc_queue_do_make_request process file-storage (pid 218), read to sector 0, sectors 8
[ 6.006286] mmcblk0: error -110 transferring data, sector 0, nr 8, card status 0x0
[ 6.008300] mmcblk0: error -110 sending stop command, response 0x0, card status 0x0

Quote:

[ 8.926147] mmcblk0: error -110 transferring data, sector 31047552, nr 8, card status 0x0
[ 8.928802] mmcblk0: error -110 sending stop command, response 0x0, card status 0x0
[ 8.936553] end_request: I/O error, dev mmcblk0, sector 31047552
[ 8.942504] Buffer I/O error on device mmcblk0, logical block 3880944
[ 9.648834] mmcblk0: error -110 transferring data, sector 31047552, nr 8, card status 0x0
[ 9.651550] mmcblk0: error -110 sending stop command, response 0x0, card status 0x0
[ 9.659179] end_request: I/O error, dev mmcblk0, sector 31047552
[ 9.665161] Buffer I/O error on device mmcblk0, logical block 3880944

Quote:

# cat /dev/mmcblk0
cat: read error: Input/output error

Quote:

dd if=/dev/zero of=/dev/mmcblk0
dd: writing '/dev/mmcblk0': Input/output error
1+0 records in
0+0 records out
0 bytes (0B) copied, 0.728272 seconds, 0B/s

Re: Is it possible to revive this N950?

If anybody is willing to donate or sell for cheap n950 with broken screen, then I would be more than happy.

I also do wonder how much it would cost to solder bigger eMMC, and what's the upper limit(I guess that 256GB would work too, but what about bigger ones?)

Re: Is it possible to revive this N950?

Quote:

Originally Posted by badpixel (Post 1571348)

It's definitely not there. I've mirrored all n9/n950/n900 sites some, and it's not there too.
Even google doesn't have any links to source. Web Archive also.

So it's lost in the Web, but as we saw, there are still n950's owner that got it mirrored, so can upload it somewhere.

You might have caught me during a server reboot, but my blog is definitely still there. Try again: https://dt.iki.fi/nokia-n9-resurrect

Quote:

Originally Posted by badpixel (Post 1571360)

BTW, battery level drops to 5% from 11% after flash attempt. Is it possible that voltage drop from nearly-dead battery causes that?

That sounds like the battery is in extremely bad shape. In my experience, this can grow so bad that the device becomes unusable until you remove (not an option in a phone I guess) or replace the battery.

Re: Is it possible to revive this N950?

I have understood never to try flashing with empty battery 'cause it may cause bad problems. So first thing before anything else would be fixing that.

Re: Is it possible to revive this N950?

It's not a battery problem, because it works over cable in Ubiboot rescue mode for long time, but cannot write anything to eMMC.
So resoldering eMMC(hard or impossible part) or finding N950 with broken screen(which is unavaible to buy, so such n950 is only useful for parts only) is probably the only option.
Because My n950 is generally in good shape, but got dent over power buttons(making them unclickable), it's probably smart to find n950 in perfect condition, but with broken screen(because happily mine is in good shape, from what I saw in Ubiboot green terminal ;-)