Sailfish OS flashing files
 

Flashable images for:

RIP: 3.4.0.24 forever

Jolla 1 - EXT4
Jolla 1 - LVM
Jolla 1 - BTRFS

---

Jolla C
Aqua Fish

Jolla Tablet

Inoi R7
Inoi T8 Tablet

https://mega.nz/folder/z6pEgKgA#qSgijfgV0auYbAOnIpawUA

Re: Sailfish OS flashing files
 

Uploaded Jolla C flashable image for fastboot

Re: Sailfish OS flashing files
 

How sweet. But.
How did you get/make these
And
Its probably not a very good idea to share these, they are property of Jolla, and not least, Qualcom.

Re: Sailfish OS flashing files
 

this image was built with ks file using genunie jolla repositories.

Re: Sailfish OS flashing files
 

How to use this image? The upgrade process on my Jolla C made a big failure and not only it doesn't boot anymore but "Reset device to factory state" does not work either.

Re: Sailfish OS flashing files
 

well, best advice from me, dont use it.

What happened to you is s big warning sign to others, to not use some "random image". Even more when zero information is given.
Recovery, as you found out the hard way, may be impossible.

Re: Sailfish OS flashing files
 

I appreciate your advice but you didn't understand well the picture. I haven't touched this image at all yet, the device just got frozen with a regular OTA update (yeah, call it "my fault" because updates on the terminal are less likely to fail in my experience ). And what is even worse is that the recovery mode is not working either dumping some checksum error.

So, any way to restore it will be more than welcomed.

Re: Sailfish OS flashing files
 

I see, well, sorry my bad.
Are you able to connect to the device using ssh ?

Re: Sailfish OS flashing files
 

Uploaded ks file and build + flash commands
You can build your own firmware image

Also reuploaded firmware as zip file for windows users

Re: Sailfish OS flashing files
 

I can only access the phone in recovery mode. The boot log shows that the systemd init procedure gets stalled at the beginning but I don't have enough free time to look further in.

The checksum error seems to be from the filesystem normally mounted at /fimage