Ask / Submit

full phone backup guide

asked 2015-02-17 16:44:52 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2017-10-16 11:01:23 +0300

harry gravatar image

Hi, I am about to send Jolla phone to Care for repairs, so I have started looking at full device backups and surprisingly I haven't found a guide, only feature requests.

My intent is to create a list of things (mainly folders) to back up before doing a full reset while waiting Jolla to implement it as feature in the phone. I am confident this will help many people, myself included, to not miss/forget some to backup something making the restore impossible.

  1. Contacts-Calendar-SMS-pictures-video

use the Jolla backup to SD card feature

  1. Jolla native application settings

/home/nemo/.local/share/ (it requres developer mode)

  1. Android application data



  1. Android APK files


  1. wlan connections


See How-to: Copy Wi-fi connection settings to a new device

Any improvement is welcome :)

edit retag flag offensive close delete


  • /home/nemo/Downloads

  • to find (again) the installed software:
    -- /home/nemo/.config/lipstick/
    -- ssu lr (repository list)
    -- rpm -qa (all installed packages)

rudi ( 2015-02-17 17:09:20 +0300 )edit

my backup consists of creating a tar.gz archive of /home/nemo onto the sd card

till ( 2015-02-17 17:43:23 +0300 )edit

@till thanks. But what about restoring it? Has someone tried to restore it after a phone reset?

Moreover, a new update (U12) is about to come out, so I'll backup data on a phone with U11 and get back the phone when U12 will be out. May that cause issues?

Thank you ( 2015-02-20 17:03:32 +0300 )edit

To get a list of installed apps: ls /usr/share/applications/ > /path/to/softwarelist.txt

And to get a list of installed patches of patchmanager: ls /usr/share/patchmanager/patches > /path/to/patchlist.txt

Skillmon ( 2016-05-04 15:34:40 +0300 )edit

I did this on Jolla C, After restored the dd image on another Jolla C now i have no Wifi (No WLAN MAC-Address) Can it be solved somehow?


ExPLIT ( 2017-09-19 11:29:07 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2015-09-06 01:45:46 +0300

pan tau gravatar image

updated 2018-11-20 13:24:37 +0300

You will better need 32GB SD card - 14761836032 bytes (13.7GB) FREE (ext3 fs)

  • clear lock code in your phone settings (in case you need this backup to restore new device, same device should accept your code, but not tested to same device atm)

  • enter recovery mode (unplug usb, remove batt, hold volume down, plug batt, still hold volume down and power on)


howto connect to device in recovery mode:

mkdir -p /mnt/BackupCard
mount /dev/mmcblk1p1 /mnt/BackupCard/
dd if=/dev/mmcblk0p28 of=/mnt/BackupCard/jolla-fullBackup-p28.img

then you shoud see something like this:

28831711+0 records in
28831711+0 records out
14761836032 bytes (13.7GB) copied, 890.444682 seconds, 15.8MB/s

you can un-mount SDcard

umount /mnt/BackupCard/
  • exit recovery , disco usb, unplug batt

plug SDcard to the new device

  • enter recovery mode
mkdir -p /mnt/RestoreCard
mount /dev/mmcblk1p1 /mnt/RestoreCard/
dd if=/mnt/RestoreCard/jolla-fullBackup-p28.img of=/dev/mmcblk0p28
  • exit recovery

note: locking code is stored also on fs, passcode from old device will NOT work in new device!!! do not backup locked device, unlock both to be safe, if you restored new phone from locked phone YOU MUST DISABLE KEYLOCK BEFORE REBOOT! mount mmcblk0p28, disable passcode new

edit flag offensive delete publish link more


Hello! I wanted to move all data from my old Jolla phone with cracked screen, (bought in jan 2014, today running latest sailfish 2) to my new Jolla phone received today (with sailfish 2 preinstalled). I followed every step in this guide without mistakes(I'm qiute sure), and now my new jolla phone refuses to boot, gives the message "Filesystem recovery failed. Please seek service." In recovery mode both "1) Reset device to factory state" and "5) Try btrfs recovery if your device is in bootloop" doesn't solve the problem. It fails when trying to mount mmcblk0p28 and the the whole telnet sesssion are closed.

Running "btrfs check /dev/mmcblk0p28" in shell gives:

Check tree block failed, want=68201484288, have=0

Check tree block failed, want=68201484288, have=0

Check tree block failed, want=68201484288, have=0

Check tree block failed, want=68201484288, have=0

Check tree block failed, want=68201484288, have=0

read block failed check_tree_block

Couldn't read chunk root

Couldn't open file system

I find it a little bit strange that the jolla-fullBackup-p28.img file created from old jolla phone was only 4,1 GB in size when about 7,3 GB was allocated on the phone. The file system was balanced and without errors on old phone when I crated the image.

Can anyone please point me in the direction of a solution that doesn't involve sending it back to Jolla?

Is it today still not possible to make a full re-flash of Jolla phone?

Why are not the recovery partition(mmcblk0p28) working?

Old jolla with broken screen are still working fine of course. Is there a guide somewhere how to move everything completely?

Thanks in advance!


Carl ( 2015-12-23 00:42:48 +0300 )edit

Found my mistake... was using a FAT32 formatted SDCARD, which limits the stored file size to around 4GB.

Have now with an ext4 formatted card managed to copy the whole mmcblk0p28 partition from old jolla phone to the new jolla phone and it works fine =D

Carl ( 2015-12-23 03:34:31 +0300 )edit

Trying to mount an exFAT-formatted 64GB chip, I get:

mount: mounting /dev/mmcblk1p1 on /mysd failed: Invalid argument

The same SD chip in plain FAT format mounts, but gives me the 4GB file size limit. How did you get it to work?

Olle Jolle ( 2016-01-06 06:26:35 +0300 )edit

I did this phone procedure when changed my jolla.Fist I updated new phone to latest (same) firmware as old one. After restoring image to new phone i noticed that android and Warehouse sofware and settings do work well. Is there need restore Jolla backup (Backup.tar)?

jib ( 2016-05-23 13:55:30 +0300 )edit

If a requirement, it would be nice to say no FAT in the answer above, rather than discuss about it in the comments. I have a hard time recovering some files (notes, contacts, etc.) from a dd-ed image of the root directory.

NikosAlexandris ( 2017-06-13 12:47:30 +0300 )edit

answered 2015-02-18 05:05:01 +0300

foss4ever gravatar image

updated 2015-02-18 05:28:28 +0300

There is a thread already in Together that addresses this same topic: howto make a full backup of all user content (/home/nemo directories etc.). so this Q is mostly a duplicate of, which, among otheres, gives instructions on making such a (compressed) backup that e.g. @till pointed out in a comment above.

edit flag offensive delete publish link more



I'd say the other is the duplicate. This question started by providing a more complete answer that people can add to. The other question is also slightly more vague than this one. Just because one question came later than the other shouldn't always be the overriding factor. Instead, I'd say the clarity of a question, the relevancy of the discussions on the question and how easily it is to transfer info should be the bigger factors to decide which is the duplicate of the two. Just my 2 cents. :-)

avdwoude ( 2015-02-18 07:17:05 +0300 )edit

In my understanding the TJC forum policy is FILO (first-in-last-out) in regards to duplicate posts ;) If the original request/suggestion/issue-report is not clear or specific enough for your liking, the recommended way is to let members to edit/modify/enhance and comment in that make it better understood instead of posting duplicate questions.

foss4ever ( 2015-02-18 16:26:09 +0300 )edit

@jjaone Thanks, I did search for duplicates but didn't find them. I believe this is different because it's a wiki and is more a tutorial rather than a question.

Feel free to close this as duplicate, however. ( 2015-02-20 17:01:33 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2015-02-17 16:44:52 +0300

Seen: 5,353 times

Last updated: Nov 20 '18