New Firmware Available (June 12th, 2018); Missing partition tool

[MikeC]

Looks like PC updated their support page, and added new firmware files. For linux users, it also looks like we'll be soon able to multi-boot android, Debian, and Sailfish on the same device. There are new versions of the linux flavors too, and updated flash tool. There soon will be an updated partition tool which in addition to creating scatter files, also selects the appropriate linux system files to match. Unfortunately, the partition tool link when selected gets you a page saying "coming soon". So close!

Good stuff, PC!

[update: looks like the link's been fixed]

[rubus-3.142]

you have not found it yet the support pages have been updated at:

http://support.planetcom.co.uk/index.php/L..._Flashing_Guide

There is now a little web based partition tool that lets you pick the OS or combination of OS you want and assign to buttons you hold on boot

http://support.planetcom.co.uk/partitionTool.html

Based on your answers & some logic in the web page then gives you the relevant scatter and image files.

If I select a Debian/Andorid Mix I get filenames like Gemini_WIFI_A46GB_L10GB_Multi_Boot.txt where the 46 and 10 are the memory I assign to each  O/S.  So i followed the flashing instructions including backing up the NVRAM  the tool crashed  out half way through, now whenever I try to re-flash using the dual boot scatter file or the AndoridOnly.txt scatter file I get an error "Invalid ROM or PMT Address". from the flash tool

The Gemini is bricked - boots and gets stuck at the first screen with no rotating planets and a penguin  then shows a Andorid character on it's side with an exclmation mark falsing "no command"

I am guessing I have somehow messed up the partitioning but how to reset it?   I read back the NVRAM again and the backup file is different to the original so possible this has also got corrupted?     googling for the error suggests formatting the device but I an not too keen.

[SNi]

I followed the instructions on the PC support page and went for the three-boot scenario (boot 1: Android, boot 2: Sailfish, boot 3: Debian) and the process ran through to completion. Achieved a partial success: Can boot "normally" into Android; can boot into recovery mode, can boot to Sailfish...

However when I try the boot 3 scenario ("Starting from a switched OFF Gemini, press the Esc (On) key to start the unit until the Gemini vibrates. Once you feel the vibration both Esc (On) key and silver right-end side button are pressed at the same time") I see the planet/tux screen, then it goes dark, then vibrates, then the planet/tux screen, then dark, then vibrates, then... endless repeat.

Haven't had much time in Sailfish (just really checked that I can boot into it), already a few issues... a) The screen starts off in the wrong orientation, but after a few minutes the rotation seems to kick in and it starts to switch... .  I have a voice mail, Sailfish recognizes it, but when I try to call to retrieve it says "No Network coverage."

[speculatrix]

I've now got triple boot. Getting into Debian was quite easy, but Sailfish was very tricky, and it took me four goes.
Turn off. I think I did by this way: Turn by on holding ESCape just long enough to start turning on. Then, when you feel the vibrate, hold the silver button and ESCape again just until the caps lock lights and quickly release otherwise you'll force it back off!

[speculatrix]

follow this link: https://www.oesf.org/forum/index.php?showforum=203
for Sailfish discussions

[racerx187]

The Gemini is bricked - boots and gets stuck at the first screen with no rotating planets and a penguin  then shows a Andorid character on it's side with an exclmation mark falsing "no command"

I am guessing I have somehow messed up the partitioning but how to reset it?   I read back the NVRAM again and the backup file is different to the original so possible this has also got corrupted?     googling for the error suggests formatting the device but I an not too keen.

I managed to get into this state too. I had to manually add each partition file from the base firmware folder.

I used this screen shot from their instructions as a cheatsheet to reflashing the correct partitions.

http://support.planetcom.co.uk/index.php/File:flash2.png

I used the Upgrade Firmware drop down when I did the complete re-flash.

No vibrations happened when you "brick" the unit, but the device seems to have the ability to be re-flashed even in this dead state by updating the prebootloader section.

I have a wifi only unit.

[SNi]

I've now got triple boot. Getting into Debian was quite easy, but Sailfish was very tricky, and it took me four goes.
Turn off. I think I did by this way: Turn by on holding ESCape just long enough to start turning on. Then, when you feel the vibrate, hold the silver button and ESCape again just until the caps lock lights and quickly release otherwise you'll force it back off!

Thanx for the tip, that did it, I now do have Boot 3 Debian! It's just rather fiddly and the PC instructions weren't real exact. When you Boot 2 you have to keep the silver button pressed; so I assumed that in Boot 3 you (similarly) had to keep both buttons held down (i.e. so I was turning the thing off!)

[GregG]

Am I right in thinking the Boot 3 option uses just the SD card? So I can have..

Boot 1 Android
Boot 2 Sailfish or blank
Boot 3 Linux

I hope to go Sailfish/UBport/KDE on Boot 1 in the end. But as this is my daily driver it does need to function fairly well for now.

[Adam Boardman]

For people having trouble getting to all four options due to holding keys for too long/not long enough, you only need to be holding the correct keys from the buzz to the planet'n'tux logo.
I try to keep this page up to date with the key combinations: Bootloader

Also just to point out that sailfish (+ other linux's in future) live on the 'linux' partition in sub folders (eg /.stowaways/sailfishos) This means that in the future we can install/remove alternate OS's without re-flashing by just dropping them in the stowaways folder and dd'ing the relevant kernel to one of the bootN partitions.