Project

General

Profile

Actions

FindDevicesWithUnsignedBootloaedrs

Given the huge number of devices out there, buying each device and checking it doesn't scale. Especially as there are multiple variants and even multiple versions of the variants.

For instance for the Galaxy SII we have the GT-I9100 that has an Exynos4 and GT-I9100G that has an OMAP4. And for the GT-I9100G, there are multiple versions.

Making it easy for people to check the devices they have

The first step would be to document what tools already exist to do that and the ones that are lacking.

Some tools enable to check that.

We could make it easy to use such tools to do that by making sure that they are packaged and writing tutorials on how to do the check and report the result as well.

See BootloadersFreedom#Tools for more details.

Notes:
  • Even with fuseegelee we might want to know if the device has restricted boot or not. See the BootloadersFreedom for more details about the limitations of fuseegelee and how to potentailly bypass them.
  • sunxi-tools: does "if sunxi => unsigned?" still stand now that there are fuses drivers? If so still mention the tool as it could detect the SOC which would then tell us that it's most probably unsigned.
  • No tools (beside devmem2 and a good datasheet) to analyze boot settings and dump registers at runtime?

Checking images at large scale

The idea would be to find a way to get a very large number of stock images for Android devices make tests on the images and automatically check if the bootloaders are signed.

If the bootloaders are under a free software license and are unsigned, once we get and identify the corresponding source code we could publish them.

For the signed bootloaders under a free software license we'd better check with the FSF what is best to do as we need not to redistribute any software that is practically nonfree.

Constraints:
  • Check with FSF lawyers how to do it legally

Updated by Denis 'GNUtoo' Carikli over 2 years ago · 19 revisions

Also available in: PDF HTML TXT