Replicant

h1. Exynos4 Bootrom

{{toc}}

h2. Background information

The Replicant project wants to support devices with free software bootloaders, but most/all the smartphones and tablets supported by Replicant do check the signature of the first stage bootloader.

A presentation on the situation of some of the devices supported by Replicant was made at the Replicant contributors meeting in July 2019. The "presentation slides":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-bootloaders.pdf and "video":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-bootloaders.webm are available.

h3. Exynos 4 signature check

The Exynos4 bootrom has a strange way to check the signatures:

* The first stage bootloader is encrypted

* The signature check is not very clear[1]

* The header that holds the key has a "func_ptr_BaseAddr" field[1].

h2. Attempts

h3. xboot

"xboot":https://github.com/xboot/xboot is an OS that is supposed to run as the BL1 on a board that has the the Exynos 4412.

There is "an attempt to port it and run it on the Galaxy SIII":https://github.com/xboot/xboot/issues/21 but it didn't succeed yet.

h3. func_ptr_BaseAddr

If the xboot attempt doesn't work we could also try to understand with qemu[2] or a developement board that has JTAG, if func_ptr_BaseAddr is somehow used by the bootrom when verifying the BL1.

Testing with qemu[2] is probably way more easy than using the JTAG.

If it is we might be able to replace the bootrom check function.

fn1. https://fredericb.info/2018/03/emulating-exynos-4210-bootrom-in-qemu.html

fn2. https://github.com/frederic/qemu-exynos-bootrom

h3. JTAG, fuses and EMMC RPMB

According to "a post on the gsmhosting.com forum":https://forum.gsmhosting.com/vbb/f672/regarding-knox-s4-1775213/ :

<pre>

 Threr are 2 types of devices exist.

1. EXYNOS Devices with JTAG Disabled ( GT-I9300,GT-I9500,GT-N7100 etc.)

    KNOX Warranty bit are stored inside of RPMB area in eMMC

    Downgrade protection byte are stored in RPMB.

</pre>

So if that's true for most common devices and that we don't find a way to re-enable the JTAG we probably cannot use it to load bootloaders and/or to experiement with the hardware on these devices.

However it's probably still possible to use JTAG on some devboards.

The thing we can learn from this post is also that unlocking the device probably don't change the Exynos 4 fuses. I wonder why it is implemented this way when other devices use fuses. And for the devices that use fuses, what is the fuse bit used for? Is it to prevent the fuses to have all bits be modified to zero or 1 and which would make it easier to compute the private key? Does the Qualcomm SOCs have a more granular approach to fuses? How does the Management Engine which also burn fuses at runtime handle that?

h3. Other tests to attempt

* Try to understand better the scheme used to check the signature.

* Try to see if the fuses can still be written (zeroed) and see whether it's computationally feasible to compute the private key for a zeroed fuses hash.

* Try to understand why encryption is used.

h2. Other

h3. Rebooting to u-boot

On several SOCs families you can override the boot pins through register writes.

For instance on the OMAP 3630 you have a register for that at 0x48002910 which is publicly documented in its technical reference manual. 

Not all the system on a chip have something like that.

If registers to do that are found for the Exynos 4412, rebooting directly to u-boot from s-boot should be pretty easy to do.

The "i9300_emmc_toolbox":https://github.com/oranav/i9300_emmc_toolbox.git project can execute code in s-boot, and we can easily write C code to be executed in it.

Some examples are provided in the shellcode directory.

So it would be trivial to write to a register and use the already provided reboot function.

TODO:

* Look at older Exynos SOCs datasheet to find a register for that

* Look at various versions of the Exynos 4412 and other documentation on that SOC

* See if "sboot-binwalk":https://github.com/quarkslab/sboot-binwalk, which has signatures and plugins for binwalk that were written while analyzing Samsung S6's proprietary bootloader, can be of any use in conjunction with i9300_emmc_toolbox.

Note that this has not been seen in use yet, including in the "Galaxy SIII repair manual":https://www.ifixit.com/Device/Samsung_Galaxy_S_III#Section_Documents , which shorts a resistor to change the boot modes. Though the Samsung branch that does the smartphones and tablets is separate from the branch doing the System on a chip. So for instance the System on a chip branch was providing SOCs to Apple for its Iphones while consumer electronics branch was at (legal) war against Apple.

h2. HOWTO

h3. Loading a bootloader from SD

When booting Parabola with a Replicant 9 kernel on a Galaxy SIII (i9300), it is possible to erase the bootloader to make the device boot from the microSD instead.

This could be used to do some testing, for instance to see if the BL1 signature can somehow be bypassed, however as no free software bootloaders do exist yet (u-boot relies on nonfree and non-redistributable software), this is not very useful yet.

If you really want to erase the bootloader (your device will be broken and will never boot anymore), you could run the following:

<pre>

# echo 0 > /sys/class/block/mmcblk2boot0/force_ro

# ddrescue -f /dev/zero /dev/mmcblk2boot0

GNU ddrescue 1.24

Press Ctrl-C to interrupt

     ipos:    4194 kB, non-trimmed:        0 B,  current rate:   4194 kB/s

     opos:    4194 kB, non-scraped:        0 B,  average rate:   4194 kB/s

non-tried:    9223 PB,  bad-sector:        0 B,    error rate:       0 B/s

  rescued:    4194 kB,   bad areas:        0,        run time:          0s

pct rescued:    0.00%, read errors:        0,  remaining time:         n/a

                              time since last successful read:         n/a

Copying non-tried blocks... Pass 1 (forwards)

ddrescue: Write error: No space left on device

</pre>

And then verify that it's erased:

<pre>

# hexdump -C /dev/mmcblk2boot0

00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

*

00400000

</pre>

Also verify that the following partitions are also erased:

* mmcblk2boot1

* BOTA0

* BOTA1

I'm not sure what BOTA0 and BOTA1 are but they were already blank in my case.

h3. Recovering from a bad bootloader

Note that I didn't manage yet to go from u-boot to s-boot.

Requirements:

* A supported device, either:

** i9300

** i9305

** n7100

** n7105

* A programable PSU or another human that can help you

* A serial cable

* Very thin/precise multimeter probes that you connect together: attachment:probes.jpg

HOWTO:

* Prepare a microSD with u-boot

* Disassemble the device

* Connect the device to a programable PSU. The PSU has to be off

* Connect the serial cable

* Make sure that the device, serial cable, and connection to the PSU don't move. Example: attachment:n7100_bench.jpg You could also use cardboard and tape.

** VCC is available on the battery connector

** GND is available at many places

* Make sure that the PSU will go to the right voltage when set to on

* script the PSU power on, for instance wait 10 seconds before power on. For example:

<pre>

$ on(){ sigrok-cli -d korad-kaxxxxp:conn=/dev/ttyACM0 --set --config enabled=on ;}

$ off(){ sigrok-cli -d korad-kaxxxxp:conn=/dev/ttyACM0 --set --config enabled=off ;}

$ off

$ sleep 10 ; on

</pre>

* With the multimeter probes, short the resistor.

** For i9300 and i9305, see this picture for finding the resistor: attachment:i9300_resistor.jpg

** For n7105, see this picture for finding the resistor: attachment:n7105_resistor.jpg

You then should have u-boot running which can boot Parabola, so you can then easily recover.

Note that to run Parabola you need to make sure that you use an MBR and no gpt as u-boot is to be put at the second 512B block.