Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, it seems that you managed to get it working at least once, as this attempt you got into the device just fine:

root@garp-Lenovo-B590:/home/garp# ssh -i my_n9_identity root@192.168.2.15
The authenticity of host '192.168.2.15 (192.168.2.15)' can't be established.
RSA key fingerprint is 69:d6:c2:2a:ad:3d:b8:63:8b:a3:3d:b1:38:2c:06:9c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.2.15' (RSA) to the list of known hosts.
************************************************** ******
* Welcome to RM-696 ubiboot-02 maintanance console *
************************************************** ******

~ # apt-get update
-sh: apt-get: not found
~ #

Only, there's no command "apt-get" in ubiboot maintanance console as it is not a debian distribution, so naturally the command fails :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks! Could you give me a command it makes sense to test!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

well, "mount" for example... or "ls -l /"

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme Thanks, it works!

Another Q due to this http://talk.maemo.org/showpost.php?p...postcount=1076

Does it mean installing new Sailfish version (ex. r4) in 7 partitions N9 don't need to delete all in Sailfish partition, make tar --numeric-owner -xf etc with new tar.bz2 file (and change config.conf) and start all over again in Sailfish, but only copy new version of bzImage file into Sailfish /boot/ and new version of modules folder to lib/modules in Sailfish partition and change ubiboot.conf?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That's a different thing :D

In the post you are quoting, @max83 asked about using a self-compiled new kernel with an existing Sailfish installation.
Answer to that is, yes, just put modules and kernel to ALT_OS partition (normally the mmcblk0p4 partition) and make a new kernel menu line to "Sailfish" section in ubiboot.conf.

What you are talking about here, I suppose, is having 2 different Sailfish versions on the device at the same time, on different partitions?
And the answer to that, too is "of course it is possible" :)
If you want to do that, you need of course partitions for both your installations, and the preparation is similar as for ALT_OS, untarring the images to partitions and then making ubiboot configuration entries for the partitions.
(Additionally, you could change the menu graphics (boot icons) so that you'd have for example "sailfish r3" and "sailfish r4" in your top menu...)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

No then I didn't made it clear. I only have and want to have ONE Sailfish partition together with one Nemo, Harmattan, Nitdroid, Firefox. I only talk about when install new version ex. Sailfish r4 instead of Sailfish r3!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, then you only need to replace the current SailfishOS r3 with r4, right?
Here's one way of doing it, altough there are many possibilities:

• get the filesystem image, for example vgrade-sailfish_r4.tar.bz2
• unpack the archive with bunzip2 to get the tar archive vgrade-sailfish_r4.tar (or if using windows use 7-zip or whatever similar tool?)
• copy the tarfile image somewhere on your N9, for example to your MyDocs/
• go to Harmattan console, and go to root with "devel-su"
• mount your ALT_OS partition with command "mount /dev/mmcblk0p4 /mnt" (now I am assuming your ALT_OS is partition 4...)
• check that you have the correct partition mounted: "ls -l /mnt" (you should see the SailfishOS partition, I assume you know what it looks like)
• delete all files from there with command "rm -rf /mnt"
• check again with command "ls -l /mnt", it should be empty now
• untar the new r4 files there with command "tar -xvf /home/user/MyDocs/vgrade-sailfish_r4.tar --numeric-owner -C /mnt"
• check that all is in order there with "ls -l /mnt"
• sync and umount; "sync ; umount /mnt"

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK yes, thanks that's the way I do it now and then will do in future!:)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hi,

I'm following the excellent guides at http://wiki.maemo.org/Ubiboot and http://wiki.maemo.org/Sailfish but I've run into an issue with the Ubiboot-02 flash step:

root@fejd-tower:/home/fejd/n9_flash/059H2M6_RM-696 NDT 64GB ROW BLACK# flasher -a main.bin -k zImage_2.6.32.54-ubiboot-02_301013 --flash-only=kernel -f -R
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Picked ape-algo from a FIASCO file
Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 001, device address 033.
Device identifier: 357923041815376 (SN: N/A)
Found device RM-696, hardware revision 1501
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 24987 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 001, device address 034.
Device identifier: 357923041815376 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8
Image SW version <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 93 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[ ] kernel [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]
---------------------------------------------------------------------
[f] kernel [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
Image too big to fit partition: image 219776+11952768 bytes
[Pipe 0] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

The only error indicators I see are:
"ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error"
and:
Image too big to fit partition: image 219776+11952768 bytes

Has anyone else run into this or know what the problem could be? Googling the SU_GET_UPDATE_STATUS_REQ error code leads me to a few reported N900 bugs where discussions seem to point to corrupted FAT. I did the first flash step with "sudo flasher -F <yourmainfirmware.bin> -f", so I didn't flash the eMMC, nor did I do the "Zeroize Method". Would any of those methods help?

Some other deviations I did from the guide:
- I couldn't download the Firefox OS files, but I believe there's still a preint file for it
- I didn't push zImage.pr13 since it says it's not recommended
- I didn't unpack Nemo directly after flashing MOSLO - there was a reboot in between (i.e. I re-ran the MOSLO flash and then unpacked Nemo into Alt_OS).

Re: Introducing ubiboot N9 (multiboot OS loader)
 

The ubiboot image is very large; about 12M in compressed form, true, that is because it includes the root filesystem of the repair mode in the kernel image.
However I have not ever seen that it would be too big to be flashed to the kernel MTD partition.

Would it be possible that your kernel partition is smaller than on other devices? I believe that even on MTD there is some flash filesystem that removes damaged flash blocks from use, maybe your kernel partition has been reduced in size?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Could be, I suspect the flash is damaged, it kind of makes sense now with the issues I've had previously with lost data and settings. Here's the output from sfdisk:
~ # /sbin/sfdisk -l

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1632511 1632496 52239872 c W95 FAT32 (LBA)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 1632512 1760511 128000 4096000 83 Linux
start: (c,h,s) expected (1023,3,16) found (1023,63,32)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)

Disk /dev/dm-0: 0 cylinders, 0 heads, 0 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/dm-0: unrecognized partition table type
No partitions found

Should I repartition it? I'd have to say I've never done that but there's a thread on the topic here that looks helpful:
http://talk.maemo.org/showthread.php?t=91914

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Could be, I suspect the flash is damaged, it kind of makes sense now with the issues I've had previously with lost data and settings. How do I see the size of the kernel MTD partition? df shows me:

~ # df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 3.9G 1.8G 1.9G 49% /
devtmpfs 10.0M 252.0K 9.8M 2% /dev
tmpfs 4.0M 88.0K 3.9M 2% /tmp
tmpfs 512.0K 160.0K 352.0K 31% /var/run
none 10.0M 252.0K 9.8M 2% /dev
tmpfs 64.0M 436.0K 63.6M 1% /dev/shm
/dev/mmcblk0p3 2.0G 1.1G 790.6M 59% /home
/dev/mmcblk0p1 49.8G 14.5G 35.3G 29% /home/user/MyDocs
aegisfs 3.9G 1.8G 1.9G 49% /var/run/applauncherd
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.odnp-fpcd/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.odnp/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.positioningd/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/private
aegisfs 3.9G 1.8G 1.9G 49% /var/cache/timed/aegis
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.slpgwd/layer
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.mms/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.facebook/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.signon/private
aegisfs 3.9G 1.8G 1.9G 49% /etc/ssl/certs
/dev/mapper/signonfs 6.8M 41.0K 6.4M 1% /home/user/.signon/signonfs-mnt

Here's the output from sfdisk:
~ # /sbin/sfdisk -l

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1632511 1632496 52239872 c W95 FAT32 (LBA)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 1632512 1760511 128000 4096000 83 Linux
start: (c,h,s) expected (1023,3,16) found (1023,63,32)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)

Disk /dev/dm-0: 0 cylinders, 0 heads, 0 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/dm-0: unrecognized partition table type
No partitions found

Should I repartition it? I'd have to say I've never done that but there's a thread on the topic here that looks helpful:
http://talk.maemo.org/showthread.php?t=91914

Re: Introducing ubiboot N9 (multiboot OS loader)
 

By the way forgot, is there anything to do with the problem in Harmattan OS in second device?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Probably yes, the N9 device is pretty forgiving in that respect, it can usually be fixed without reflash just by replacing/fixing the thing that's broken in the first place... however to know what exactly to fix is more difficult :D

Usually people just are impatient with that, and do a reflash, as that will always fix it.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

OK thanks reflash back to closed mode -- no-preserve?:(

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Just take backups before you do that and you'll be okay.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Ups back-up in Ubiboot how: Still reserved empty screen for Farfary's Backupmenu?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well no, I meant just the regular Harmattan backups, and be sure to transfer the backup archive to your PC. And also back up all your stuff on MyDocs if you'd want to wipe the device.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Regular Harmattan backups? To me it's the one in settings and farfary's Backupmenu and last one can't be used with Ubiboot?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, there are basically 2 kinds of backups you can take off Harmattan.

The first type is the normal backup via the "settings -> backup" menu. This creates backup of your settings, messages, notes, whatever application data you have (or most of it) and the result is a new subdirectoty under MyDocs/.backups/ which contains 7 zipfiles and a metadata file.
This backup does not contain your applications, so to reinstall those you need to either reload from store or save the DEB's when you install applications.

The second type of backup is the type taken with BackupMenu or ubiboot maintanance console, which is a snapshot of the filesystem state at the moment it was taken.
This type saves the state exactly as it is, which is a problem if your state is not correct (like on your N9), as if you restore this kind of backup to your device after a reflash, you will get the device back in the (broken/faulty) state it was before :D:D

So, if you have a device in a broken/faulty state, you do not want to use the second type of backup.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks, that's what I thought! How to use maintenance console for Backup, can't see it from README?
OK need to flash back to closed mode or no-preserve BUT that will destroy my 5 partitions plus one extended and reduce it to 3 standard, correct?

EDIT: Reason why can't download from Store in Sailfish OS could that be same error in Harmattan OS as with Microsoft Exchange not working?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I believe you missed this ?

--
what I would try is to fully backup (partitioning wise) my working device, then flash there the rootfs, copy that rootfs (p2) via 'dd' to the other device, test. If not working try once more also with /home (p3). Maybe you will loose partitiong table on working device, but this could be restored easily/manually.
If successful restore the working device.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Could be, I suspect the flash is damaged, it kind of makes sense now with the issues I've had previously with lost data and settings. How do I see the size of the kernel MTD partition? df shows me:

~ # df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 3.9G 1.8G 1.9G 49% /
devtmpfs 10.0M 252.0K 9.8M 2% /dev
tmpfs 4.0M 88.0K 3.9M 2% /tmp
tmpfs 512.0K 160.0K 352.0K 31% /var/run
none 10.0M 252.0K 9.8M 2% /dev
tmpfs 64.0M 436.0K 63.6M 1% /dev/shm
/dev/mmcblk0p3 2.0G 1.1G 790.6M 59% /home
/dev/mmcblk0p1 49.8G 14.5G 35.3G 29% /home/user/MyDocs
aegisfs 3.9G 1.8G 1.9G 49% /var/run/applauncherd
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.odnp-fpcd/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.odnp/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.positioningd/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/private
aegisfs 3.9G 1.8G 1.9G 49% /var/cache/timed/aegis
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.slpgwd/layer
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.mms/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.facebook/private
aegisfs 3.9G 1.8G 1.9G 49% /home/user/.signon/private
aegisfs 3.9G 1.8G 1.9G 49% /etc/ssl/certs
/dev/mapper/signonfs 6.8M 41.0K 6.4M 1% /home/user/.signon/signonfs-mnt

Here's the output from sfdisk:
~ # /sbin/sfdisk -l

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1632511 1632496 52239872 c W95 FAT32 (LBA)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 1632512 1760511 128000 4096000 83 Linux
start: (c,h,s) expected (1023,3,16) found (1023,63,32)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)

Disk /dev/dm-0: 0 cylinders, 0 heads, 0 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/dm-0: unrecognized partition table type
No partitions found

Should I repartition it? I'd have to say I've never done that but there's a thread on the topic here that looks helpful:
http://talk.maemo.org/showthread.php?t=91914

Re: Introducing ubiboot N9 (multiboot OS loader)
 

How do I verify the size of the kernel partition? I've run sfdisk and it shows me:

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1632511 1632496 52239872 c W95 FAT32 (LBA)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 83 Linux
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 1632512 1760511 128000 4096000 83 Linux
start: (c,h,s) expected (1023,3,16) found (1023,63,32)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)

This is right after flashing MOSLO and trying to flash ubiboot. If the flash is damaged, would it help to run a disk check and mark the sectors, then flash again?

p.s. Is there any way to format the output to make it more readable? d.s.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Kernel is not flashed on your mmcblk0 flash, there's a differnt flash filesystem on the device that consists of the parts of device which hold for example the factory calibration data.

The location for kernel is the MTD2 partition of the system NAND.
You can get some information with mtdinfo command, for example on my device it says:

~ # /usr/sbin/mtdinfo -m 2
mtd2
Name: kernel
Type: nand
Eraseblock size: 262144 bytes, 256.0 KiB
Amount of eraseblocks: 64 (16777216 bytes, 16.0 MiB)
Minimum input/output unit size: 4096 bytes
Sub-page size: 1024 bytes
OOB size: 128 bytes
Character device major/minor: 90:4
Bad blocks are allowed: true
Device is writable: true

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Looks same on my device.
Had only info from
cat /proc/mtd
which did not reveal size of blocks.
But neither commands will tell us if / how many blocks are 'burnt'?

[OT]sfdisk -d /dev/mmcblk0
will show output more readable[/OT]

Re: Introducing ubiboot N9 (multiboot OS loader)
 

mtdinfo for partition 2 shows:

~ # /usr/sbin/mtdinfo -m 2
mtd2
Name: kernel
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 64 (8388608 bytes, 8.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 512 bytes
OOB size: 64 bytes
Character device major/minor: 90:4
Bad blocks are allowed: true
Device is writable: true

mtd_debug gives me:

~ # /usr/sbin/mtd_debug info /dev/mtd2
mtd.type = MTD_NANDFLASH
mtd.flags = MTD_CAP_NANDFLASH
mtd.size = 8388608 (8M)
mtd.erasesize = 131072 (128K)
mtd.writesize = 2048 (2K)
mtd.oobsize = 64
regions = 0

So it looks like the size is set to 8M. Is this a factory setting or is it set during flashing? Could it be a result of damaged sectors? I've flashed two different variants with the same result:
059H2M6_RM-696 NDT 64GB ROW BLACK
059L7N6_N9 RM-696 Country Variant Sweden SE Black 64GB

If I print the MTD info for Moslo, its size is set to 16M:

~ # /usr/sbin/mtd_debug info /dev/mtd5
mtd.type = MTD_NANDFLASH
mtd.flags = MTD_CAP_NANDFLASH
mtd.size = 16777216 (16M)
mtd.erasesize = 131072 (128K)
mtd.writesize = 2048 (2K)
mtd.oobsize = 64
regions = 0

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Hmm, I have exactly double sized mtd2 and mtd5.
So does not look like erase block problems.
Maybe HW revision?
What is yours? (lshal | grep hardware)

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I tried to apply the correct changes, but Nitdroid still does not boot. The last entries in the Ubiboot log say it correctly loaded the kernel; where would things be logged after that?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

When I run flasher, the hardware revision shows 1501:

Device identifier: 357923041815376 (SN: N/A)
Found device RM-696, hardware revision 1501

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Maybe juiceme (or rainisto?) can tell more?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Either in /var/log/syslog (same under nitdroid?) or just nowhere.

Is preinit_nitdroid executable? (was most common problem)
If so, you have all those echos as debug logging to see where it goes nuts...
--
send/post your preinit and tell once more where your rootfs and home and nitdroid partition/folder is

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thank you! Chmodding /sbin/preinit_nitdroid to 755 fixed the problem and now it boots fine!

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I have exactly the same version as you have, 1501, and that is the device I looked up the MTD2 information from.

On the kernel command line you can see the partition table of the MTD flash that is given by NOLO to the booting kernel. My line looks like this:

mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),1638 4k@3840k(kernel),2048k@20224k(log),469248k@22272k( var),32768k@491520k(moslo)

Does your device have a different line there? (you can see it by "cat /proc/cmdline")

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Just for completeness:
mine is 1601.
And cmdline looks exactly like juiceme's.

That is really strange!

--
also for completeness (to fetch more information):
your device is a 64GB?
the firmwares match your product code?
they are PR1.3 firmwares?
...?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Yes, I did not think about that but your PR level could actually matter
It's been so long since I had anything else than PR1.3 I cannot remember how it was (if I ever even looked, really), but in theory it is possible that the MTD assignments could be changed between the releases. For BOOT and CAL partitions I doubt it, but for the other ones, it is a possibility.

So, for completeness sake, please tell the variant and PR level.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

My cmdline looks a bit different:

mtdparts=omap2-onenand:512k(bootloader),1408k@512k(config),8192k@ 1920k(kernel),1024k@10112k(log),496768k@11136k(var ),16384k@507904k(moslo)

Yes, it's the 64GB version and in "About device" I see version:
PR1.3 (40.2012.21-3.339.2_PR_339)
If I pull out the SIM card and peek within, it says RM-696 and so I flashed this variant:
059L7N6_N9 RM-696 Country Variant Sweden SE Black 64GB
Before that I flashed:
059H2M6_RM-696 NDT 64GB ROW BLACK

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Did you flash only rootfs (firmware.bin)?
Or also eMMC ?

In latter case I am fully out of ideas. In first case it might be a try to flash both in one command!? [another wild guess]

btw: why did you voluntarily switched from ROW to country variant?
What is your product code?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

That is just crazy, I have no idea how and why your commandline defines the kernel partition as 8MB. I have never seen anything like that!

Probably @rainisto is the only one who could explain that...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You might be on to something there, I checked the SIM tray and it says 059J187, which is "059J187_RM-696 NDT NORTH EUROPE BLACK 64GB" (which I did not try to flash)! For some reason I thought the differences of the ROW/variant images were only the pre-loaded stuff, like maps, but it seems like there are more fundamental differences. Thanks, I'll try to flash it and see if it works better!