chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-amlogic
naoki has quit [Quit: naoki]
naoki1 has joined #linux-amlogic
naoki1 is now known as naoki
hexdump0815 has quit [Ping timeout: 252 seconds]
hexdump0815 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
zsoltiv_ has quit [Ping timeout: 244 seconds]
djrscally has joined #linux-amlogic
ungeskriptet_ has joined #linux-amlogic
ungeskriptet has quit [Ping timeout: 252 seconds]
ungeskriptet_ is now known as ungeskriptet
vagrantc has quit [Ping timeout: 260 seconds]
ldevulder has joined #linux-amlogic
vagrantc has joined #linux-amlogic
vagrantc has quit [Ping timeout: 268 seconds]
naoki has quit [Quit: naoki]
naoki1 has joined #linux-amlogic
naoki1 is now known as naoki
naoki has quit [Client Quit]
naoki has joined #linux-amlogic
jacobk has quit [Ping timeout: 248 seconds]
f11f12 has joined #linux-amlogic
jacobk has joined #linux-amlogic
anessen973383701 has joined #linux-amlogic
naoki has quit [Ping timeout: 276 seconds]
naoki has joined #linux-amlogic
mripard has joined #linux-amlogic
f11f13 has joined #linux-amlogic
f11f12 has quit [Read error: Connection reset by peer]
naoki has quit [Quit: naoki]
mripard has quit [Quit: WeeChat 4.5.1]
buzzmarshall has joined #linux-amlogic
jacobk has quit [Ping timeout: 260 seconds]
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 276 seconds]
jacobk has joined #linux-amlogic
vagrantc has joined #linux-amlogic
<f_>
lvrp16: Well, either all GXL SoCs still have the vuln, or I ended up with a vulnerable Xiaomi TV Stick, but I just managed to get unsigned code running
<f_>
I think this part of the BL1's uart logs: "GXL:BL1:9ac50e:bb16dc;" might be the git hash or something, or part of it
<f_>
it's identical on the boards where I saw the bootROM was identical
<f_>
and nonetheless it's different on the non-GXL boards.
<f_>
Though one might say "heh, obviously!"
<f_>
In the meantime I stumbled upon a git repo with lots of bootROM dumps, and among them there are 2 dumps for one SoC, apparently different revisions.
<f_>
ah nevermind I misread.
<f_>
Now, (obviously) if I try loading BL2 it's going to try enforcing secureboot settings.
<f_>
Frédéric's guide on how to run ubuntu using that exploit implies manually patching out the relevant bits and pieces .. but I think I might have another idea
<f_>
Possibly I could try running u-boot-spl? But that'll require some work on the USB mode handling
<f_>
But that's for the far future. For now I want to decrypt and dump the "BL2 AArch32" strange build that's there.
<f_>
and maybe BL2Z since I've no idea what it's doing and I want to find out :)
<f_>
(though it might be bundled into BL2, just like BL21?)