Hi all, I'm doing some modifications to the ubports-installer in order to be able to manage user and system data backup and restore.

I have added a backup button on the install screen :

When you click on it you will have the following screen :

The installer will read the size of both system and userdata partition and give you an estimated sized need on your disk. You can name your backup. When you will click ok let's go, the phone will reboot into recovery and the backup will start :

At this and the phone will reboot into the OS. you will be able to find 2 tar file on your computer disk : one for the system-data, the other one for the user-data.

It is actually working fine on Meizu Pro 5.
BUT, in one of my previous thread, I had the issue that in recovery image, the user and system data partition was not mounted on /data.

In the installer code, I added for the Meizu Pro 5 the mounting of sda44 on /data/

So my questions to you are :

• Who else on different phone models have the partition /data/user-data, /data/system-data not mounted in recovery ? If that is the case, what is your partition device to mount ?
• does every one have the folder user-data and system-data in the /data folder while in recovery ?
• Are you ok with this feature or do you find it usless ?

I will now write the restore option.

@jamieweb pull it from github, here are my personal notes when I did it :

git clone https://github.com/ubports/ubports-installer.git
cd ubports-installer
npm run-script dist:linux
./setup-dev.sh
npm start

Thanks @dobey once again. I have nothing to modify in it, just trying to save time by copying a portion of existing code to create a new ListView for the VVM messages in the dialer-app, I copy the ListView from the call history and I was looking for the structure of the model.

I added a button (that will be showed only if the service is activated) on the dialer page :

That will display a new page :

I would like to display a play line when we touch the item (like the iphone style).

@ubuntoutou Ok, we progress... normaly SN should display the serial number of the phone (the one you get with adb devices. And the two line should display your WiFi mac addresses.

on my phone it give :

Mar  6 19:02:40 ubuntu-phablet kernel: [    1.246534]  [5:  kworker/u16:1:   59] [c5] @@@@ SN 860BCMSxxxxx
Mar  6 19:02:40 ubuntu-phablet kernel: [    1.246746]  [5:  kworker/u16:1:   59] [c5] @@@@ MAC 68:3E:34:xx:yy:58
Mar  6 19:02:40 ubuntu-phablet kernel: [    1.246957]  [5:  kworker/u16:1:   59] [c5] @@@@ MAC 68:3E:34:xx:yy:59

We have now to find what part of the kernel is giving thoses informations, if anybody had an idea ... you are welcome

@Flohack Hi back, thanks for your answer, I finally manage to do my backup and restore with success (thanks goolge).

I share here how I did:

Backup :

#!/bin/bash
echo "Backing up your data"
adb reboot recovery
sleep 15
adb shell mount /dev/block/sda44 /data
adb shell mkfifo /backup.pipe 
adb exec-out 'tar -cvp data/system-data 2>/backup.pipe' | dd of=system.tar & adb shell cat /backup.pipe &
adb shell rm /backup.pipe
adb shell mkfifo /backup.pipe 
adb exec-out 'tar -cvp data/user-data 2>/backup.pipe' | dd of=user.tar & adb shell cat /backup.pipe &
adb shell rm /backup.pipe
adb reboot

With this script, you will mount the data partition under the recovery mode, create a pipe to transfer the content of the folder (/data/user-data) through stdout to dd on the local computer in a file named user.tar, then it will do the same for the folder system-data.

Now to restore :

#!/bin/bash
echo "Restoring your data"
adb reboot recovery
sleep 15
adb shell mount /dev/block/sda44 /data
adb shell mkfifo /resto.pipe
adb push user.tar /resto.pipe & adb shell 'cd /; cat /resto.pipe | tar -xv'
adb shell rm /resto.pipe
adb shell mkfifo /resto.pipe
adb push system.tar /resto.pipe & adb shell 'cd /; cat /resto.pipe | tar -xv'
adb reboot

This script will boot the phone into recovery mode, mount the sda44 partition into /data folder, push your backup user.tar through the previously created pipe. On the phone the pipe is catched by cat then sent to tar for decompressing.

Your backup needs to be in the same folder as the script restore because I written it like this.

Credits goes there : https://www.forum-generationmobiles.net/t78912-tutoriel-backup-adb-sauvegarde-compressee-des-donnees-de-android-vers-votre-pc-gnu-linux

I tested it and it's perfectly working, I was able to clone one of my Pro 5 to the other one Pro5.

sda44 partition is mostly for Pro5, not sure that this mount works on other model.
I hope that this could help other people.

The best way is maybe to add this feature to ubports-installer, in order to be able to just backup/restore our phone (and of course re-installing it) only with one tool.

What are you thinking about that ?

@jamieweb Of course, no problem at all if that can help other people experiencing this with their Meizu If you need help for your script, please post in your original thread and I will try to help you. Good job.

@PINE64 You mean the SanDisk flash ?

@Stefano you can do this regarding the fingerprint reader, I did it on 16.04:

https://github.com/ubports/ubuntu-touch/issues/396

@stefano hi! Many thanks for your answer, I will try your solution, the phone was initially running Android, I convert it to Ubuntu 2 days after buying it. I should have the international version somewhere on my computer. I'll keep you informed.

@jamieweb you can spy dbus with dbus-monitor on a adb shell terminal , then try to lock and wake up the phone, you shoulder be able to see the commands that you need .

sudo dbus-monitor --system 

Hi @ubuntoutou, It makes a while that I didn't touch it but it was working well for PRO5, I'm using it for my own backup and restore.
If you use it please let me knwo about the result !;)

You will need as much free space on your hard drive as the phone occupancy.

For example if you have a 32Go memory and you are using about 16Go, you will need 16Go of free space on the computer where you are running the installer in backup mode.

Hope this will help you.

@Fla hi, It still in review. but you can try it a tell us your opinion on it ! I only could test it on Pro5.
thanks !

@elin_martell hi ! you will fond the solution in this post:

https://forums.ubports.com/post/6899

@matteo Yes true, even if I was hoping that it was an issue !

@Flohack Yes no problem... I'm too much utopian...
BUT I noticed a hudge difference between Pro 5 on flyme and Pro5 on Ubports regarding the flash LED back to the phone for the camera, on the Ubport, when you would like to use it as a torch, both LED are on (the white and amber) which give a kind of warm white not really nice for pictures at low light. On Flyme, only the white LED of the flash is on, which give a nice cold white.

How can we handle this on ubports ?

@Flohack @matteo Ok I have to correct what I say, you can forget the RGB on Meizu Pro 5, I unmounted one, and there is only a single white LED, no RGB LED on the PCB. I then powered up my Pro5 running Flyme and try to send it different notification (low batt, charging, sms messaging, missed call), all the time the notification was white, the only difference between sms and call is the led pattern. When a sms arrive, the LED is breathing like actually on ubport, when a call is missed, the led blink once quickly, then once quickly with a breath effect.
They are no LED indications on low battery or charging on Flyme.

There is no way of getting RGB colors on Meizu Pro 5.

We can only play with pattern.
That's why the driver was commented and the white LED was connected on the Red channel from the LD5562 chip.

@UniSuperBox I'm on the stable channel, sorry ...

@UniSuperBox Ok thanks ! I will try this. If I understand right from the previous Q&A (66), it's an issue due to an outdated key/certificate and the reneweal isn't working, they solved it for OTA-12.

@Flohack in my opionion, normally not, it must be a channel per color. a Year ago I modifyed the file already in order to use the 3 other channels but I don't remember where I put this file ...

@Flohack they are in fact 4 leds on the meizu pro 5 hardware, RGB and White. We can see the colors when the phone is running Flyme. I dont know the reason Why they only activate the white one but in hardware point of view, from the lp5562 datasheet we can see that it is able to drive 4 Leds, so I'm not sure that we can damage anythings on the phone by trying to activate other channels registers.

If you don't feel it, I can try it as I have 5 Pro5 and one of the isn't usable as phone because the IMEI are missing.

but you will have to wait as I don't have so many time to do that for now.