Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062020-05-07T06:01:49ZReplicant
Redmine Replicant - Issue #2027 (New): Investigate lthor / thor and samsung u-boot for Tizenhttps://redmine.replicant.us/issues/20272020-05-07T06:01:49ZKurtis HannaKurtis@riseup.net
<p>We already know of a method by which we can replace s-boot and replace it with u-boot, but it requires opening up the device and shorting a touch point on the logic board.</p>
<p>We have been looking for a method by which we can replace s-boot via software only techniques. One such technique might spring from the work being done here: <a class="external" href="https://github.com/oranav/i9300_emmc_toolbox">https://github.com/oranav/i9300_emmc_toolbox</a></p>
<p>Another option, if heimdall by itself doesn't prove in the end to be enough, might be lthor.</p>
<p>This upstream u-boot ODROID exynos4412 repo shows that lthor/thor is enabled: <a class="external" href="https://gitlab.denx.de/u-boot/u-boot/blob/master/configs/odroid_defconfig">https://gitlab.denx.de/u-boot/u-boot/blob/master/configs/odroid_defconfig</a></p>
<p>It was suggested to Wolfgang in the last email of this thread that he should use lthor to "convert" an i9300 to an RD-PQ/Trats2 board to get u-boot on the device: <a class="external" href="https://patchwork.kernel.org/patch/9345815/">https://patchwork.kernel.org/patch/9345815/</a></p>
<p>lthor is free software, but the i9300 doesn't have lthor support by default.</p>
<p>On post #77 here <a class="external" href="https://forum.xda-developers.com/showthread.php?t=2482563&page=8">https://forum.xda-developers.com/showthread.php?t=2482563&page=8</a> it is claimed that a modified kernel with access to the mmcblk0boot0 partition was used to flash a modified version of s-boot, which was dumped from a RD-PQ, that included u-boot with lthor enabled in it. Much of the same information is reiterated by the same author in this post: <a class="external" href="https://forum.xda-developers.com/showthread.php?p=64794497#post64794497">https://forum.xda-developers.com/showthread.php?p=64794497#post64794497</a></p>
<p>It is my understanding that once you can use lthor with your device, you can then very easily flash any image that you'd like onto the emmc using the free software program lthor. At least that is the suggestion after reading to the end of this section of a Tizen wiki: <a class="external" href="https://wiki.tizen.org/Exynos#Creating_the_image_manually">https://wiki.tizen.org/Exynos#Creating_the_image_manually</a></p>
<p><a class="external" href="https://wiki.tizen.org/images/b/bd/Lecture-1.pdf">https://wiki.tizen.org/images/b/bd/Lecture-1.pdf</a> has some information about creating updated versions of u-boot-mmc.bin, which might come in handy.</p> Replicant - Issue #2022 (In Progress): Update our git to include forkbomb's u-boot midas updates.https://redmine.replicant.us/issues/20222020-04-17T15:10:32ZKurtis HannaKurtis@riseup.net
<p>Forkbomb's midas u-boot repo has commits in it that aren't included in our git repo here: <a class="external" href="https://git.replicant.us/contrib/GNUtoo/u-boot-midas">https://git.replicant.us/contrib/GNUtoo/u-boot-midas</a></p>
<p>Here are his most recent commits: <a class="external" href="https://github.com/fourkbomb/u-boot/commits/midas-2020.01">https://github.com/fourkbomb/u-boot/commits/midas-2020.01</a></p> Replicant - Issue #1960 (Closed): Build release candidate image for 6.0 0004https://redmine.replicant.us/issues/19602019-10-09T19:48:49ZKurtis HannaKurtis@riseup.net
<p>We have identified a handful of remaining blockers for building a rc image for 0004. We hope to resolve these last few blockers in the coming days. This issue will only be open temporarily to allow us to visualize our progress towards removing the remaining blockers.</p> Replicant - Issue #1957 (New): Add MHL supporthttps://redmine.replicant.us/issues/19572019-09-12T05:00:38ZKurtis HannaKurtis@riseup.net
<p>The SiI9244 MHL Transmitter seems to be widely used in a lot of Replicant supported devices, but it doesn't seem to be supported in upstream LineageOS.</p>
<p>A discussion this on XDA's forums can be found here: <a class="external" href="https://forum.xda-developers.com/galaxy-note-2/devs-only/gt-i930x-hdmi-mhl-implementation-aosp-t2940110">https://forum.xda-developers.com/galaxy-note-2/devs-only/gt-i930x-hdmi-mhl-implementation-aosp-t2940110</a></p>
<p>This github wiki has a picture of the MHL chip in the Samsung Galaxy S, which is said to have the text, "SIMG 9244BO NCS371A 10L2230" on it: <a class="external" href="https://github.com/TeamApexQ/apexq/wiki/Board-info">https://github.com/TeamApexQ/apexq/wiki/Board-info</a> This wiki links to this Silicon Image document about the chip.</p>
<p>It was suggested here that the MHL (SiI9244BO) chip and schematics can be found in the GT-I9100 Service Manual: <a class="external" href="https://forum.xda-developers.com/galaxy-s3/development/building-hack-pack-t1624685">https://forum.xda-developers.com/galaxy-s3/development/building-hack-pack-t1624685</a></p>
<p>Some kernel drivers for the chip were posted to github here: <a class="external" href="https://github.com/TeamNDVRu/android_kernel_lge_x3/tree/fa8143a4b6082eb103796a19553bfaf646aa060a/drivers/video/tegra/mhl">https://github.com/TeamNDVRu/android_kernel_lge_x3/tree/fa8143a4b6082eb103796a19553bfaf646aa060a/drivers/video/tegra/mhl</a> and here: <a class="external" href="https://github.com/HONO/lge-kernel-iproj-mod/tree/17750854ebd6a4e11880f618846275a273fae120/lge/com_device/mhl_v1">https://github.com/HONO/lge-kernel-iproj-mod/tree/17750854ebd6a4e11880f618846275a273fae120/lge/com_device/mhl_v1</a></p>
<p>It seems as though the SiI9244 is supported in the upstream kernel based on this matrix: <a class="external" href="https://blog.forkwhiletrue.me/pages/midas-mainline/">https://blog.forkwhiletrue.me/pages/midas-mainline/</a></p> Replicant - Issue #1948 (New): Document how to install and run Replicant in a virtual machinehttps://redmine.replicant.us/issues/19482019-08-23T01:47:59ZKurtis HannaKurtis@riseup.net
<p>Some development work, <a href="https://redmine.replicant.us/projects/replicant/wiki/Exynos4Bootrom" class="external">like bootloader hacking</a>, is much easier to do when Replicant is running in a virtual machine rather than on a phone/tablet or a dev board.</p>
<p>There are likely also use cases for end users where knowing how to install and run Replicant in a virtual machine is useful as well.</p>
<p>There is a post here related to emulating Exynos 4210 BootROM (which is in the Replicant supported Galaxy S2) in QEMU: <a class="external" href="https://fredericb.info/2018/03/emulating-exynos-4210-bootrom-in-qemu.html">https://fredericb.info/2018/03/emulating-exynos-4210-bootrom-in-qemu.html</a></p>
<p>Here is the git repo for the Exynos 4210 BootROM in QUMU: <a class="external" href="https://github.com/frederic/qemu-exynos-bootrom">https://github.com/frederic/qemu-exynos-bootrom</a></p>
<p>Three years ago it was reported that Replicant could be run in VirtualBox using Replicant's SDK: <a class="external" href="https://redmine.replicant.us/boards/3/topics/10341?r=12267#message-12267">https://redmine.replicant.us/boards/3/topics/10341?r=12267#message-12267</a></p>
<p>Since we don't have a Replicant 6 SDK, those instructions can't be used directly by us for documentation.</p> Replicant - Issue #1947 (New): Ask upstream F-Droid to build up to date WebViewhttps://redmine.replicant.us/issues/19472019-08-22T19:28:06ZKurtis HannaKurtis@riseup.net
<p>An initial search of <a class="external" href="https://gitlab.com/fdroid/rfp/issues">https://gitlab.com/fdroid/rfp/issues</a> didn't yield any results related to them building their own version of WebView.</p> Replicant - Issue #1940 (Resolved): Have 'Replicant version' under 'About phone' say Replicant 6....https://redmine.replicant.us/issues/19402019-06-23T20:04:20ZKurtis HannaKurtis@riseup.net
<p>Currently, the only way to determine whether one is using Replicant 0003 instead of 0002 is by looking at the Build date. This isn't intuitive and makes it hard for users to determine if they have the most recent stable release. We should fix this for our 0004 release.</p> Replicant - Issue #1938 (New): Add the Offline Calendar app by defaulthttps://redmine.replicant.us/issues/19382019-06-18T04:29:30ZKurtis HannaKurtis@riseup.net
<p>By adding this app by default in the ROM we provide, users can create and use a calendar that isn't connected to an email account or "the cloud". <a class="external" href="https://f-droid.org/en/packages/org.sufficientlysecure.localcalendar/">https://f-droid.org/en/packages/org.sufficientlysecure.localcalendar/</a></p> Replicant - Issue #1937 (New): Liberate the bcm4334 wifi/bluetooth firmwarehttps://redmine.replicant.us/issues/19372019-06-13T03:52:43ZKurtis HannaKurtis@riseup.net
<p>The driver for this chip seems to already be free software and is in the mainline linux kernel: <a class="external" href="https://redmine.replicant.us/issues/1836">https://redmine.replicant.us/issues/1836</a></p>
<p>Cypress now owns the rights to the bcm4334 chips' firmware. To my knowledge, Cypress is more likely to say yes to a request that they release the source code to this firmware with a free software license than Broadcom would have been. I don't believe anyone has formally asked Cypress to do this. Since this chip is in a lot of Replicant's supported devices, it would make sense for our project to formally ask this of them.</p>
<p>The non-free firmware binary seems to be available here: <br /><a class="external" href="https://github.com/OpenELEC/wlan-firmware/blob/master/firmware/brcm/brcmfmac4334-sdio.bin">https://github.com/OpenELEC/wlan-firmware/blob/master/firmware/brcm/brcmfmac4334-sdio.bin</a></p>
<p>There were some efforts to hack this chip's firmware in the past, but it seems to not have gone anywhere...</p>
<p><a class="external" href="https://forum.xda-developers.com/showpost.php?p=52499037&postcount=5">https://forum.xda-developers.com/showpost.php?p=52499037&postcount=5</a><br /><a class="external" href="https://github.com/cociorbaandrei/bcmon">https://github.com/cociorbaandrei/bcmon</a><br /><a class="external" href="https://recon.cx/2013/video/Recon2013-Ruby%20feinstein%20Omri%20Ildis%20Yuval%20Ofir.mp4">https://recon.cx/2013/video/Recon2013-Ruby%20feinstein%20Omri%20Ildis%20Yuval%20Ofir.mp4</a><br /><a class="external" href="https://recon.cx/2013/slides/Recon2013-Omri%20Ildis%2c%20Yuval%20Ofir%20and%20Ruby%20Feinstein-Wardriving%20from%20your%20pocket.pptx">https://recon.cx/2013/slides/Recon2013-Omri%20Ildis%2c%20Yuval%20Ofir%20and%20Ruby%20Feinstein-Wardriving%20from%20your%20pocket.pptx</a><br /><a class="external" href="https://bcmon.blogspot.com/">https://bcmon.blogspot.com/</a><br />Some of this work seems to have been done by this developer, who we could maybe contact for help if we also want to hack the chip's firmware: <a class="external" href="https://github.com/shoote">https://github.com/shoote</a> <a class="email" href="mailto:shoote@gmail.com">shoote@gmail.com</a></p> Replicant - Issue #1906 (New): Replace S-Boot with U-Boot on exynos4412 (midas) deviceshttps://redmine.replicant.us/issues/19062019-01-11T02:28:53ZKurtis HannaKurtis@riseup.net
<p>This is needed in order to deal with TrustZone, RYF, mainline Linux, and making it so our current flagship devices can run GNU/Linux distros.</p>
<p><a class="external" href="https://github.com/fourkbomb/u-boot">https://github.com/fourkbomb/u-boot</a><br /><a class="external" href="https://blog.forkwhiletrue.me/posts/an-almost-fully-libre-galaxy-s3/">https://blog.forkwhiletrue.me/posts/an-almost-fully-libre-galaxy-s3/</a></p>
<p>It is my understanding that this currently works, but no u-boot console shows up on the display if you use the old linux kernel from Samsung that we are currently using.</p>
<p>"It's also worth mentioning that LineageOS/Replicant will boot under u-boot with a kernel compiled without CONFIG_ARM_TRUSTZONE set, but the display will not work (probably because u-boot does not initialise the display)."</p>