fancypants' experiments
216 subscribers
124 photos
4 videos
37 links
stuff
Download Telegram
at least breakfast/lunch works still xD
oof, system/sepol is checked against prebuilt policy now
Reset system/sepolicy to 0defd4f424055c8449ee07269bb14e7fc6873040 and it should pass build for now. (AOSP 10.0.0_r2 HEAD)
Forwarded from Jyotiraditya Panda
Forgot to share this here, everything other than camera works :D
Forwarded from Kshitij Gupta
Forwarded from Kshitij Gupta
AOSP source, in frameworks/base/core/java/android/os/Build.java
Forwarded from Adrian DC
@fancypants For those who don't know, that's a quote from "Q" in Star Trek The Next Generation with Picard :D
thinking of shitposting my begonia (mtk) experiments here too hmmmmmmmm
Forwarded from Kshitij Gupta
ok lmao
I'm actually an idiot.
So, fast forward, I'm bricked now for the second time. Luckily, from the first time, I have the BROM Flash log from SP Flash Tools. For those unaware on why a Mi authorized account is needed in the first place (speaking wrt to MTK platforms), MTK provides for a feature called SLA, which happens to be Serial Link Authentication/Authorization. Most OEMs don't implement this and MediaTek's own release of SP Flash doesn't have much in regards to SLA.
Xiaomi has SLA implemented and does things server side. The device generates 16 random bytes that it expects decrypted. If you give it the right answer, it'll continue with connect_brom and start flashing whereas wrong answer, it puts itself in an endless loop and won't listen to any more commands until BROM times out and goes for a reboot.
Now, if we are able to send DA to the device and connect to it without actually doing SLA, we wouldn't need to do SLA at all. A simple change to SP Flash should be enough to reflash the device.
Forwarded from Kshitij Gupta
update: I got bored again; managed to handshake with BROM xD