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

[Request]: How-To create Jolla SOS image as security backup for flashing

asked 2014-06-26 22:44:49 +0200

Nekron gravatar image

Recently our well-known device hacker @Nieldk bricked his phone after an update / recovery process went wrong locking his bootloader unable to recover his phone.

In many users opinion a broken device software should not be an issue for sending the phone back to Jolla care. On the other hand Jolla stated that because of legal or license reasons they are not being able to provide a SOS image for the phone. So we have an annoying stalemate here.

Now what I wanted to request is that Jolla (official or by community help) shows a way how each owner of a Jolla device can backup the complete SOS on their own, creating a legal security backup image of the software he/she purchased which can be reflashed to the device in case like @Nieldk something went wrong.

Maybe this can be implemented by Jolla as a "flash image creation app" for security backups? In this case Jolla would not need to provide (illegal) official SOS image files but on the other hand you as a Jolla owner can create a working image which can be reflashed to the phone with all of your installed apps giving you a working phone in case a software glitch bricks your phone.

edit retag flag offensive close delete

Comments

4

Not a bad idea, that. We definitely nees something like that.

Another possibility would be to provide a flashable base rescue image that contains no vendor-private parts by Qualcomm, just basic bones to get the device to a state that it could connect to Jolla Store via USB networking for example, to download the official image.

juiceme ( 2014-06-26 22:55:38 +0200 )edit

2 Answers

Sort by » oldest newest most voted
11

answered 2014-06-26 23:07:08 +0200

rainisto gravatar image

updated 2014-06-26 23:15:46 +0200

If you use latest bootloader, use rescue menu to unlock bootloader, you can use dd to make backups your partitions that you can always recover. In that case you only have to remember not to ever use factory reset (or downgrade to old bootloader). If you follow those rules you can always recover.

PS. And if you ever need to do factory reset, then use the UI to upgrade to latest release and not use ssu trickery.

PPS. for really advanced stuff would be to make btrfs snapshot of your working env, and then delete factory snapshots and rename your working snapshot to be factory snapshot. That way if you ever need to do factory reset it would go back to your working env and not to 1.0.0.5.

edit flag offensive delete publish link more

Comments

I guess you didnt read my case. The device rebooted during update. Changing my unlocked bootloader to a locked state!, and recovery boot is also screwed, so I cant enter recovery to unlock again. This makes it impossible to recover from even my dd images (which I have, and have used multiple times). I have now. No recovery Fastboot is not allowed due to the re-locked bootloader Phone in boot-loop when trying to power on. I have a suspicion this is due to a now completely flat battery, but ... I cant get a new battery, and it seems that the phone will not recharge the battery. https://together.jolla.com/question/48622/goodbye-jolla/#post-id-48632

Nieldk ( 2014-06-26 23:23:05 +0200 )edit
3

@Nieldk, yes I read your case, I can see ssu re 1.0.2.5 ... version --dup, which flashes 1.0.2.5 bootloader which doenst have unlocked bit reading included. Thus your screwed. If you would have stayed with 1.0.7.x bootloader and not have done dup on re 1.0.2.5 this would have not happened (as you would have been able to fastboot boot with 1.0.7.x bootloader and use dd backups). You might still able to recover with external battery chargers, if its only because of battery that recovery menu does not appear.

rainisto ( 2014-06-26 23:30:31 +0200 )edit
3

@rainisto Yes, It seems like it might just be battery drain - I have ordered an external charger, so we will see. But I have to emphazie, this happened due to a device sudden reboot during an update, this is a serious issue, not only to a 'hacker-wanna-be' but towards normal users aswell. I have a chance of recovering at least. But many wont have that option. Also, Jolla care have asked that I send the device for repair, fair enough. Probably will leave me in a much better situation, as any future 'factory resets' wont restore to 1.0.0.5 but probably 1.0.2.5 or later versions, which will prevent this bootloader issue I am sure. Still, I will give it the weekend and see if I can manage to get a bit of power on the battery.

Last: Despite the negativity of my posts, this is mostly done to bring an issue like this to Jollas and users attention, thus hopefully saving many others from similar experience.

Also, a provate thank you to you, and stskeeps who have both been involved on a very personal level. stskeeps even the day before his sons first birthday (I really dont want to be an intruder of that), but it shows the lattitude of involmenet by key persons at Jolla, which despite issues, should be appreciated!

Nieldk ( 2014-06-27 10:42:37 +0200 )edit
4

answered 2014-12-19 17:42:28 +0200

mariner gravatar image

The most important part of any backup mechanism is that it should be simple - if not it is pointless because no-one uses it. As well as the SOS it should be easily possible for any user to make a complete backup of the whole software/data of the phone.

edit flag offensive delete publish link more

Comments

I totally agree!!! We need an easy to use possibility for a complete backup of the whole software/data and the same for restore it.

peter-berlin ( 2014-12-19 21:09:26 +0200 )edit
Login/Signup to Answer

Question tools

Follow
9 followers

Stats

Asked: 2014-06-26 22:44:49 +0200

Seen: 1,204 times

Last updated: Dec 19 '14