We have moved to a new Sailfish OS Forum. Please start new discussions there.

Recovery mode - possible bug

asked 2015-06-15 21:43:55 +0300

simo gravatar image

updated 2015-06-16 00:22:26 +0300

I was trying to help a friend to recover a phone booting only to background after updating to Recovery mode worked, so first we tried option 5 which did run through but didn't help. Then via option 4 (Shell) we tried to backup data before reset, but mounting the memory card failed after commands

mkdir -p /mysd
mkdir -p /myhome
mount /dev/mmcblk1p1 /mysd

The card in phone was normal MicroSDHC 8GB. I advised my friend to contact care, but I wanted to write here too to confirm if there's something changed in the mounting steps or if the latest upgrade has a new bug on this.

SD card is confirmed to work on PC, and confirmed to be formatted to fat32.

Screenshot of recovery shell after testing mounting both to "mysd" and "tmp": image

Additionally, in the beginning we also checked btrfs fi show which showed both enough of storage space and allocation space free, so I have no idea why the update didn't go through in the first place.

edit retag flag offensive close delete



What was the error ? Commands are correct - assuming you have formatted (FAT?) the SD card and it 'works' You are using the '-p' option, which isnt necessary, but also shouldnt matter.

Nieldk ( 2015-06-15 22:04:12 +0300 )edit

/ # mount: mounting /dev/mmcblk1p1 on /mysd failed: No such file or directory sh: mount:: not found

Card is not self formatted, should be shipped preformatted with the FAT32 file system

simo ( 2015-06-15 22:49:58 +0300 )edit

Is developer mode enabled ? If so, you could try to copy the data from the phone, using ssh. I understand, that you cant get a working GUI. But the phone might still accept connections (I have this issue quite often = every update on one phone).

Use scp from linuc (or winscp from windows) to copy files from the phone to the computer.

In linux, on the linux box, commandline,you can use scp like this:

$ mkdir backup
$ scp -r nemo@your.phone.ip.address:/home/nemo/* ./backup/


$ scp -r nemo@* ./backup/

That will copy all content of the home folder to backup folder on desktop PC.

Nieldk ( 2015-06-15 23:09:02 +0300 )edit

unfortunately developer mode is not enabled on my friends phone :( He'll probably keep that enabled after this, now that it seems that he's about the loose all data if care (or us here) can't help to get the card mounted. Thanks for those lines anyway.

simo ( 2015-06-15 23:13:16 +0300 )edit

You can also try to mount the sdcard in an exisiting folder (It seems the /mysd wasnt created from your output), for example try to mount it to /tmp

Nieldk ( 2015-06-15 23:39:31 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2015-06-16 02:54:35 +0300

simo gravatar image

updated 2015-07-13 14:42:17 +0300

"bug" in documentation... fixed with mount /dev/mmcblk1 /mysd (dropping "p1" from the end)

SD card got mounted, personal data copied to card via Recovery shell, and this phone got a successful reset. It remains unsolved what caused the phone to boot without GUI, but that's another question, already asked.

Suggested fix: Edit the Zendesk documentation with correct command for mounting the SD card in Recovery shell

Update: Looking forward for closing this question, but the suggested fix (above) is yet to be edited to https://jolla.zendesk.com/hc/en-us/articles/204709607-How-do-I-use-the-Recovery-Mode- (if there are no other answers offered)

edit flag offensive delete publish link more


I got myself a backround brick Jolla after the update too. In my case the mounting worked with the "p1".. Dunno what are the differences with the devices then..

Pikku-Y ( 2015-06-17 16:52:05 +0300 )edit

Thanks. If the name varies, I guess the guide can be updated with instructions how to check the correct command. We went to /dev folder to check, no ..p1 there.

simo ( 2015-06-17 19:19:27 +0300 )edit

Whether you need the "p1" or not depends on how the card is formatted. "pX" indicates a partition, while its absence means that your filesystem — in case there really is one — starts probably from the very beginnig of the block device. There's no partition table that could tell if there is even supposed to be a filesystem on the card. Hence the absence of a partition notation. Both ways are valid I guess, but using a partition table is more common (and correct) from what I can tell.

Okw ( 2015-07-13 18:47:37 +0300 )edit

Thanks for clarification @Okw - While there are cards using partitions and cards without partition table, the zendesk document should cover these both cases

simo ( 2015-07-13 19:13:59 +0300 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2015-06-15 21:43:55 +0300

Seen: 422 times

Last updated: Jul 13 '15