Boot Loop/Black Screen Nokia N950 - maemo.org

dattelfisch | # 1 | 2019-06-06, 01:01 | Report

Hello,

Unfortunetely my N950 doesn't boot up. I tried reflashing with every available firmware.

The current firmware is: "DFL_61_HARMATTAN_40.2012.21-3_PR_RM680".

I'm also able to reflash the kernel and mount rootfs. No existing /var/malf (therefore not the MALF-problem)
But nothing helps!

Current state:
After plugging in the battery the device starts up showing the NOKIA-Logo but then the screen turns black and after while the display turns out (but the device is still running).

Maybe there is an expert who can help me with this.
Please.

Last edited by dattelfisch; 2019-06-06 at 01:47.

The Following 2 Users Say Thank You to dattelfisch For This Useful Post:
imaginaryenemy, juiceme

Halftux | # 2 | 2019-06-06, 09:36 | Report

Have you tried to disable the watchdog with the flasher?
Don't know if all flags from N900 flasher are the same for N9/N950.

This could prevent a boot loop:

Code:

--set-rd-flag=no-lifegard-reset

These could be also interesting:

no-omap-wd
no-ext-wd

http://wiki.maemo.org/R%2526D_mode

The Following 4 Users Say Thank You to Halftux For This Useful Post:
dattelfisch, imaginaryenemy, juiceme, peterleinchen

aspergerguy | # 3 | 2019-06-06, 12:14 | Report

Originally Posted by dattelfisch View Post

Unfortunetely my N950 doesn't boot up. I tried reflashing with every available firmware.

That statement worried me as just flashing once with "DFL_61_HARMATTAN_40.2012.21-3_PR_RM680" was quite enough as that firmware was hard enough to source.

With regards to trying R&D mode, enable with:

HTML Code:

--enable-rd-mode --set-rd-flags=no-lifeguard-reset

and disable with:

HTML Code:

--disable-rd-mode

In what state of charge is BL-4D battery as at least can be charged outside device if necessary rather than using flasher?

Last edited by aspergerguy; 2019-06-06 at 12:23. Reason: Addition

The Following 5 Users Say Thank You to aspergerguy For This Useful Post:
dattelfisch, Halftux, imaginaryenemy, juiceme, peterleinchen

peterleinchen | # 4 | 2019-06-06, 13:18 | Report

State of battery?
flasher -i
should show you / and probably charge also, but maybe you need to give full flash command (kernel is enough) to charge, there is a dedicated thread here on tmo.

Do you have also the eMMC image? Then at least worth atry is full flash eMMC and firmware wiping all.

The Following 3 Users Say Thank You to peterleinchen For This Useful Post:
dattelfisch, Halftux, juiceme

dattelfisch | # 5 | 2019-06-06, 15:57 | Report

Originally Posted by Halftux View Post

Have you tried to disable the watchdog with the flasher?
Don't know if all flags from N900 flasher are the same for N9/N950.

This could prevent a boot loop:

Code:

--set-rd-flag=no-lifegard-reset

These could be also interesting:

no-omap-wd
no-ext-wd

http://wiki.maemo.org/R%2526D_mode

Unfortunetely, the flags didn't solve the problem. I concatenated them, too, like:

Code:

flasher -F img.bin --set-rd-flag=no-lifeguard-reset,no-omap-wd,no-ext-wd

Originally Posted by aspergerguy View Post

That statement worried me as just flashing once with "DFL_61_HARMATTAN_40.2012.21-3_PR_RM680" was quite enough as that firmware was hard enough to source.

With regards to trying R&D mode, enable with:

HTML Code:

--enable-rd-mode --set-rd-flags=no-lifeguard-reset

and disable with:

HTML Code:

--disable-rd-mode

In what state of charge is BL-4D battery as at least can be charged outside device if necessary rather than using flasher?

The first command changed nothing but the second one let's it vibrate again and the notification-LED is fading instead of switching from on to off. But then the phone powers off. That's a little success I think.

Originally Posted by peterleinchen View Post

State of battery?
flasher -i
should show you / and probably charge also, but maybe you need to give full flash command (kernel is enough) to charge, there is a dedicated thread here on tmo.

Do you have also the eMMC image? Then at least worth atry is full flash eMMC and firmware wiping all.

Yes, I'm using the eMMC image from "Win_OCF_02-6_RM680-RM680-OEM1.exe".

Code:

flasher -i

doesn't show the charge but by flashing with:

Code:

flasher -F img.bin --enable-rd-mode --set-rd-flags=no-lifeguard-reset

Code:

flasher -f -F img.bin --erase-user-data=secure

Code:

flasher -f -F img.bin -F emmc.bin --flash-only-mmc

Code:

flasher -F img.bin --disable-rd-mode

Code:

flasher -F img.bin --reboot

it shows "Battery level 96%, continuing."

The battery seems to be okay and kernel reflashing didn't help.
The screen keeps being turned out.

Last edited by dattelfisch; 2019-06-06 at 16:21. Reason: error

The Following 3 Users Say Thank You to dattelfisch For This Useful Post:
Halftux, juiceme, peterleinchen

Halftux | # 6 | 2019-06-06, 16:21 | Report

Have you tried to boot the rescue image with the flasher?
Does it stay on or does it reboot or switch off too?
Maybe with the rescue image you could look in some log files or check the data structure. Or install manually a package which gives you more log file output.

The Following 4 Users Say Thank You to Halftux For This Useful Post:
dattelfisch, imaginaryenemy, juiceme, peterleinchen

dattelfisch | # 7 | 2019-06-06, 16:25 | Report

Originally Posted by Halftux View Post

Have you tried to boot the rescue image with the flasher?
Does it stay on or does it reboot or switch off too?
Maybe with the rescue image you could look in some log files or check the data structure. Or install manually a package which gives you more log file output.

Thank you for your answer.

Firstly, I tried using Windows 7, but then I switched to the rescue image.
It doesn't reboot. When turning on the phone by power switch the nokia logo pops up in white screen, then the display turns black and after a while completely out.

Do you know which files could be useful? I'm able to look into the rootfs, that's no problem at all.

PS:
Maybe it could be useful to know which device I'm using.
It's "RM-680, hardware revision 0322" and it's a black 64GB device.

I found this thread where someone seems to have a similar problem:
https://talk.maemo.org/showthread.php?t=90868

But It's not very helpful.

Last edited by dattelfisch; 2019-06-06 at 17:00. Reason: error

The Following 2 Users Say Thank You to dattelfisch For This Useful Post:
imaginaryenemy, juiceme

mankir | # 8 | 2019-06-06, 16:50 | Report

unfortunately i never owned a n950, as it was the device i ever wanted. try df -h, lsusb or dmesg and check the partitions, clear the tmp-dirs and lock-files. put watchdogs on default, cold-flash the newest image. just suggestions...

The Following 3 Users Say Thank You to mankir For This Useful Post:
dattelfisch, imaginaryenemy, juiceme

dattelfisch | # 9 | 2019-06-06, 17:30 | Report

Originally Posted by mankir View Post

unfortunately i never owned a n950, as it was the device i ever wanted. try df -h, lsusb or dmesg and check the partitions, clear the tmp-dirs and lock-files. put watchdogs on default, cold-flash the newest image. just suggestions...

df -h, lsusb, or dmesg can't be used.
After flashing ubiboot using:

Code:

flasher -k zImage_2.6.32.54-ubiboot-02_301013 -l -b

I'm able to mount the N950-partitions and network device (usb) turns up but

Code:

telnet IP

says: "telnet: Unable to connect to remote host: Connection refused"

The tmp- and lock-dirs are already empty.

Watchdogs set to default by using:

Code:

flasher -F img.bin --clear-rd--flags:no-lifeguard-reset,no-omap-wd,no-ext-wd

Cold flash by using:

Code:

flasher -c -F img.bin -F emmc.bin

fails because of this error:
"ERROR: You have to supply 2nd image for RM-680:0322
ERROR: Cold flashing failed"

PS:
I've tried the newest ubiboot ("zImage_2.6.32.54-ubiboot-02_23032018"), too but it doesn't make any difference.
Maybe the N950 can't be accessed via serial console over USB?

Last edited by dattelfisch; 2019-06-06 at 18:01.

The Following 2 Users Say Thank You to dattelfisch For This Useful Post:
imaginaryenemy, juiceme

Halftux | # 10 | 2019-06-06, 19:38 | Report

Originally Posted by dattelfisch View Post

Do you know which files could be useful? I'm able to look into the rootfs, that's no problem at all.

/var/log/syslog

could be useful. It is a logfile from the standard installed simple-syslog-daemon.

Better would be to install klogd and sysklogd from developer mode. Maybe klogd is enough and would be easier(no need to remove simple-syslog-daemon).
But as you can't install on the mounted partition, they need to be extracted and I don't know if something like this is possible because of this aegis thing. Which also stopped me to work more with harmattan.

Edit: Maybe open-mode kernel could be of help.

Last edited by Halftux; 2019-06-06 at 19:45.

The Following 3 Users Say Thank You to Halftux For This Useful Post:
dattelfisch, imaginaryenemy, juiceme