Sailfish X startup: "Your device has been unlocked and cant be trusted"

Thanks for the answer!

So it might be replaceable if it is just an image. Sailfish logo would be very nice instead of that warning.

Suggestion for new splash screen:

"Your device is running Sailfish OS so it can be trusted"

;-)

excuse me, but how to access to \ramdisk\res\images\warning?

Some more info on the ramdisk.img here https://android.stackexchange.com/questions/66825/what-is-the-purpose-of-a-ramdisk-in-android

i think it would be necessary to reflash the firmware to alter this. I'm sure it could be done by Jolla in their SailfishX image but they may not be allowed to.

I took a look at some of the mmc partitions to see if it was there, but had no luck.

mmcblk0p22 is an android boot image containing the kernel + initrd AKA ramdisk, but the warning image was not in that ramdisk. There are several other kernel images in other partitions that I didn't look closely at (check the partitions that file identifies as ELF binaries) - it is possible that one of them may contain an embedded initrd (relatively unusual setup, but certainly possible and you can use readelf to pull it out IIRC), so probably worth another look.

mmcblk0p14 is an image (file identifies as TIM format, which was used by the PlayStation, which makes sense given this is Sony, but imagemagik cannot convert it (probably updated file format since the PS) and after examining it in a hex editor I very much doubt that it is what we are after).

I ran photorec over every partition looking for other image files with no luck (but it might be in a compressed image or a format that photorec does not understand), and checked the contents of a handful of other partitions to see what they were. This doesn't mean that it isn't there - with 52(!!) partitions I could have easily missed something and I didn't check them all, but it doesn't seem likely.

This is a comment, not an answer.

@bocephus: You'r right, didn't interpret the meaning of 'Your Answer' the right way, my bad. My intention was to promote this question to the top...

You can convert answers to comments and vice versa. FYI ;)

Also, the statement “officially supported by Sony” is not entirely true. It’s supported by allowing to be flashed by fastboot (OEM unlock) and by Sony releasing their kernel sources for AOSP. The flashable image itself is not, and thus not signed by Sony.

i like this message to scare my friends (and how often you restart ur sailfish device?? for me - only when new update comes)

yes, it's annoying and the boot is delayed by 5 seconds, but it is faster than android! LOL

I hope Jolla can figure something out with Sony

Yup, I second that, it would be great if Sony accepted to sign the Sailfish X kernel with their official key.

Or do it the way that it got solved for UEFI's SecureBoot on Windows PC : Microsoft signed a shim with their official keys that passes the secureboot, and that shim in turn loads the linux boot loader (e.g.: Grub) or linux kernel.

agreed, Sony said it officialy support Jolla. It shall provide ways to remove this msg. can something be done to push them in that way ?

I like the idea of having an integrity checked base image - preferrably including the Android support subsystem, so that it counts as safe/locked again. Might help with some security sensitive apps, though admittedly it would make the OS less tinker friendly.

Somewhere it was indicated that Jolla has received help from Sony regarding this project. I find it real hard to believe that Sony would have helped Jolla if this warning screen wasn't dealt with...

Honestly there is no reason why Jolla would develop an image for the librem, as long purism isnt paying for that.

I dont see any perspective, from what your answer is an answer for the question.

@mettska Is Sony paying for the image for the Xperia XA and X? I see the Librem 5 as a perfect fit for Sailfish. Jolla makes a great OS, which is not part of the big, bad Apple/Google spy apparatus, but is out of the hardware business. Purism is focused on privacy, to the point of having hardware kill switches to ensure off truly means off. Some may prefer PureOS, but from what I've seen, Sailfish is much more elegant. The original topic was about being warned every boot up that the bootloader has been tampered with. With PureBoot, this wouldn't be an issue.