Project

General

Profile

Actions

GTI9100GBootloaderFreedom » History » Revision 31

« Previous | Revision 31/56 (diff) | Next »
Denis 'GNUtoo' Carikli, 03/27/2020 01:09 AM
moved to bootloader interfaces


I9100GBootloader

Findings, TODO and status

  • The I9100G of hpagseddy is unsigned but the omap-usb-tool says the soc is in HS mode.
  • If I recall well, the string was verified by hpagseddy, so MLO was flashed and ran
  • MLO was flashed through heimdall frmo Android 4.x bootloader's odin mode
We need to solve this OMAP HS mystery:
  • I've looked at u-boot, barebox, linux, crucible and I didn't find any driver or code for fuses for any OMAP SOC.
  • GNUtoo is in Paris where we're confined in our homes due to COVID-19 and I can't afford to brick my GT-I9100G
  • It might be due to the fuses having been programmed with the hash of a key / certificate but not being in enforcing mode.
  • The website for breaking motorolla restricted boot is only about OMAP3 devices but it contains infos on the structure of signed MLO
  • I've extracted the MLO but I'm unsure of its size and when I sent it through USB to the bootrom it failed. It might be because of the sram size limit but anyway as I don't know how to parse signatures yet (I need to look at the wiki for breaking motorolla restricted boot) I'm unsure of the exact binary size to send. Once I can parse that stuff, I will know the exact size of the signed area and so of the binary.
  • I've not managed to get any difference by booting from mmc1
  • I've not dumped yet the usual register for booting configuration like SYS_BOOT
TODO while reading the TRM:
  • check the device's OMAP4 the sram size limit
  • check the load address / memory mapping of MLO in case of USB boot or boot from eMMC.
  • Check mmc1 booting constraint (card size, look if < 4GiB works)
  • Read about SYS_BOOT and booting, though fuse infos is most probably missing
TODO while reading code:
  • check if chipsec has infos on OMAP fuses
TODO other readings:
  • Read more on the wiki against motorolla
  • Try to find a way to access the OMAP wiki and look if there is any stuff on fuses and restricted boot
Upstreaming:
  • If infos about fuses are ever found, ideally write drivers and upstream them in Linux, u-boot, Barebox and crucible
  • Look if crucible is good for adding infos about OM pins, SYS_BOOT etc. Not sure if Linux exports such registers and where
Last news 27/03/2919:
hpagseddy and GNUtoo tried several tests on their respective devices, and the device always ended up going to the battery charging screen:
  • Building xloader and loaing it with omap-usb-boot through USB
  • Same with the addition of a for(;;) loop in the code to see if it hangs (it's supposed to if the code runs)
  • Same but with the watchdog being configured to reboot after 1 second (it's supposed to reboot if the code is correct and runs)

hpagseddy and GNUtoo also found that when using odin to flash the MLO partition, odin interface makes the user think that the MLO partition was flashed correctly, while odin didn't flash anything. That may be due to the partition being set Read-Only and/or to the "File Offset" and "File Size" being 0.

-- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: X-loader
Flash Filename: MLO
FOTA Filename: 

We know that nothing was successfuly flashed as we dumped MLO, and verified that the binary was signed by looking if it contained the strings that indicate that (PRIMAPP, KEYS, CertPK_)

How to check if you have a signed bootloader

How to check from the bootloader interface to install the recovery.

To do that you need to get into the ODIN MODE that is typically used to install the Replicant recovery:

  1. Start the device by holding the following key combination: Volume down, Select, Power,
  2. Hold the key combination until the device shows a Warning message.
  3. Confirm that you want to download a custom OS using volume up
  4. Make sure the device is in Downloading mode

When this is done, it should show some text:

ODIN MODE
PRODUCT NAME: GT-I9100G_CHN_CHN

Here CHN_CHN probably refers to the Chinese version. And it looks like that version has a signed bootloader: According to a thread on the XDA developers forum "Means that you own a chinese bootloader locked I9100G. You can't flash any other bootloader than the chinese one."

How to check with command line utilities

To get the bootrom to try to boot on USB, you need to do the following:
  • Connect the USB cable to the device but make sure it's not connected on the computer.
  • Power off the device
  • Connect the USB cable

If we do that, we get the following in the kernel log of your laptop:

usb 1-1: new high-speed USB device number 24 using ehci-pci
usb 1-1: unable to get BOS descriptor or descriptor too short
usb 1-1: New USB device found, idVendor=0451, idProduct=d00f, bcdDevice= 0.00
usb 1-1: New USB device strings: Mfr=33, Product=37, SerialNumber=0
usb 1-1: Product: OMAP4430
usb 1-1: Manufacturer: Texas Instruments

Note that your kernel might need to be compiled with CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
to print that. In Parabola CONFIG_USB_ANNOUNCE_NEW_DEVICES=y is enabled.

We can also try to get a bit more infos with omap-usb-boot:

$ sudo omap-usb-boot -v -w boot invalidbootmedia
Finding and opening USB device
Found and opened omap4 USB device: OMAP4430
ASIC device id: 4430, HS device
Booting from device invalidbootmedia...
Booting device invalidbootmedia not found
Booting from device failed

Here we know the device is signed because it's a "HS device".
If it was not signed it would print "GP device" instead.

Using the Android version or other devices properties?

hpagseddy/i9100g_xloader is based on ths-backup/i9100g_xloader which has an ics (Icecream Sandwitch, an Android version) branch only. According to hpagseddy, that branch is also used for Android Jelly brean.

It's still unclear if there is some correlation between Android version and signed bootloaders.

The device that was given to GNUtoo that has a signed bootloader also has the following characteristics:

Software state: Running the stock OS, unmodified
Android version: Android 2.3.6
Baseband version: IG9100GZCLC2
Build number: GINGERBREAD.ZCLC2
Kernel version: 2.6.35.7 se.infra@SEI-30#2

According to a thread on XDA there is a corelation between the Baseband version and the geographic zone that is targeted. And as we can see above, the Build number seem to be related to the Baseband version as well. While the list of baseband versions is incomplete, we can still use it to avoid the Chinese version (CHN_CHN) which has a signed bootloader.

At this point it's also still unclear if any of the other characteristics above correlate to signed or unsigned bootloaders.

As the binaries are under the GPLv2 or later, It would also be a good idea to collect all of them, match them with the device characteristics like the Build number and Baseband version, and verify if they are signed or not with some free software tool.

We could even publish the unsigned versions. As for the signed versions, if they cannot run on devices that don't enforce bootloader signatures, it would probably not be a good idea to publish them as the binaries wouldn't respect the 4 freedoms, but we can still check with the FSF if they have good ideas on that point.

Source code

TODO

  • Document the various firmware version mentioned here: https://www.sammobile.com/samsung/galaxy-s2/firmware/#GT-I9100G
  • Understand how to get unsigned versions (Android version, serial number, etc)
  • Get a device with an unsigned bootloader and u-boot and ask samsung for source code
  • Check the boot order on unsigned devices (is it possible to boot from USB easily?)
  • Try to boot the xloader nevertheless, as the device could be in some "verify but not enforce mode" for signatures

Updated by Denis 'GNUtoo' Carikli about 4 years ago · 31 revisions

Also available in: PDF HTML TXT