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

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

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

@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?

That's a different thing

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

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!

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"

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

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

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?