Re: Introducing ubiboot N9 (multiboot OS loader)
 

Well, it is fairly deep AFAIK. Unfortunately not all the components are open source, if it only was so life would be all daisies :)

For example, the SMS-extended-character handling bug in "/usr/lib/libsms.so.0.0.0", which causes device to trash the received SMS message without a trace even when it had correctly acknowledged the receiving to RAN.
(A bug that I call absolutely critical as it breaks the (un-)deniability of messaging...)

Now install and uninstall wont close all apps!

Thanks, you solve this major bugs

@juiceme, i think you should open a new thread for this bugs fix

Re: Introducing ubiboot N9 (multiboot OS loader)
 

If you decide it's necessary, can you plz share the link here, TIA.

Re: Introducing ubiboot N9 (multiboot OS loader)
 

I made a new thread about it; http://talk.maemo.org/showthread.php?t=91825

Re: Introducing ubiboot N9 (multiboot OS loader)
 

@juiceme
"Back-to-back flashing is performed by first flashing the device like in "normal closed mode flashing", both emmc and rootfs. Then, immediately flashing the device again, now with an Open Mode kernel, without letting the device to boot up between the two flashing rounds."

I use Windows:
Will the device automatically boot up after first normal mode flashing? Meaning does I need to do something to avoid this?

Re: Introducing ubiboot N9 (multiboot OS loader)
 

You must not give thr '-R' parameter.
And you must not unplug USB.
And you must not wait too long between those two flasher commands (else the device leaves flashing mode on itself and reboots).

That's all.

--
for point 3 you may prepare the command oflline (device not plugged), press Enter and use command repetition (up and down arrows) afterwards ...

Re: Introducing ubiboot N9 (multiboot OS loader)
 

[QUOTE=peterleinchen;1387511]You must not give thr '-R' parameter.
And you must not unplug USB.
And you must not wait too long between those two flasher commands (else the device leaves flashing mode on itself and reboots).

That's all.
--
for point 3 you may prepare the command oflline (device not plugged), press Enter and use command repetition (up and down arrows) afterwards ...[/QUOTE

Does this look OK?
accli -I says = open
uname -r says however 2.6.32.54-dfl61-20121301:confused:

C:\Programmer\nokia\Flasher>flasher.exe -a DFL61_HARMATTAN_40.2012.21-3.340.04.1
_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin -k zImage_2.6.32.54-openmode_l2fix
--flash-only=kernel --suppress-warranty-warning -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan

Picked ape-algo from a FIASCO file
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 95 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2712 / 2712 kB 2051 kB/s]
Updating SW release
Success

C:\Programmer\nokia\Flasher>

Re: Introducing ubiboot N9 (multiboot OS loader)
 

If you used the "standard" L2fixed kernel or any minimally modified open mode kernel that is OK.
The reason the kernel id string is same is because the kernel module interface has been kept same as the original. (so you do not need to install new modules with the kernel)

if you are in doubt, do a "dmesg | head" and look for the kernel compile stamp. If you see my name there it is OK :D

Re: Introducing ubiboot N9 (multiboot OS loader)
 

Thanks! (juice@alaspin) behind version - correct?:)