Closed Bug 1078710 Opened 10 years ago Closed 6 years ago

Back up user data before installing flash image and/or add public facing documentation about it

Categories

(Firefox OS Graveyard :: Vendcom, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: armenzg, Unassigned)

References

Details

Attachments

(1 file)

Attached image webcam-capture.jpeg
There are several issues I want to highlight
* We currently don't have any documentation on MDN about backing up the user data.
* We currently don't back up a user profile before installing the base image
* flash.sh comes with the incorrect permissions
* We include a file called #flash.sh#

I believe we should back up the user profile before paving with the base image.
I don't believe we should restore the user profile without asking the user first.

To fix the permissions of flash.sh I run this: "chmod +x flash.sh"

I currently backed up with user profile with backup_restore_profile.sh [2]

To back up my user data this is what I do:
* cd ~/repos/B2G-flash-tool
* ./backup_restore_profile.sh -r

These are the steps I followed:
* wget http://cds.w5v8t3u9.hwcdn.net/Flame_2.0_v180_1.zip
* unzip Flame_2.0_v180_1.zip && cd Flame_2.0_v180_1
* chmod +x flash.sh
* sudo ./flash.sh
* Go through FTU menu
** Connect to WiFi
** Click on date and time so the phone updates to current date/times
** I skip all other menus
** [Perhaps I don't have to do any FTU steps and run the restore]

To restore my profile I do this:
* cd ~/repos/B2G-flash-tool
* ./backup_restore_profile.sh -r

Unfortunately, restoring the profile failed completely. It would get the phone to the Flaming fox screen and stay there. If we added backing up and restoring as part of the acceptance test of a new base image it would be great.

To get my profile back, I decided to use flash_pvt.py -w and ask for a User image based on v2.0 of Gecko + Gaia.
After that I restored my profile as mentioned. However that got me into a weird state (see screenshot). My profile was back but we only were drawing half the screen.
A reboot got me into the right state.

I'm now on 1.80 [3] + I have my user profile back.

[1] https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame%27s_software
[2] https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/backup_restore_profile.sh
[3] armenzg-thinkpad B2G-flash-tool git:[master] $ adb shell getprop ro.bootloader
L1TC10011800
Is there a repo where I could contribute on what gets included as part of the zip file that contains the base image? Who could review such changes?
Flags: needinfo?(whuang)
Flags: needinfo?(frlee)
correction ni to Wesly (TAM)
Flags: needinfo?(whuang) → needinfo?(wehuang)
hi viral,

are you able to comment on this issue?
Flags: needinfo?(frlee) → needinfo?(vwang)
I think Al (CC'd) can help on the tool review and maintain :)
Flags: needinfo?(wehuang)
Flags: needinfo?(vwang)
Flags: needinfo?(atsai)
If I figure out what is the repo, I'm happy to contribute!
Flags: needinfo?(atsai) → needinfo?(fyen)
The big problem is that I also do not have any documentation about backup or restore the user data.

It seems like B2G doesn't provide the backup/restore profile feature, so we try to pull/push files by adb command. However, this way have some risk.
For example, when user backup profile from v1.4 then restore to v2.1, user might get stuck phone due to the changes of data structure and file structure.
Flags: needinfo?(fyen)
There is a user story for back up and restore (Bug 1026531)
Depends on: 1026531
This is my bug related to backup and restore old data from JJ image to a KK one: bug 1084491
Unless we automate the process of releasing a new base image and testing profile backup we're going to see non-staff members who own a flame hit these issues again and again.

It is already difficult without granting them full flashing (since they can't access private builds - pvtbuilds) to switch between versions since shallow flashing is prone to breaking and does not provide the gonk bits that each release requires.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: