[G4 Android Development] steadfasterX:
I place it here because ppl using TWRP in FIsH are those maybe most interested in the progress and until I have something useful I don't wanna create a dedicated thread for this:

Current state efidroid:

- ported for unlocked devices

- stalled. Secondary ROMs still bootloop, still no testers and so I decided to go on with multirom

Current state multirom:

The following are the results of my last testing weeks:

- option A requires a kexec patched kernel --> means touching your boot image --> means soft brick

- option B requires not a kexec patched kernel (when you build with MR_NO_KEXEC) but that means when booting a secondary ROM it will replace the current boot partition with the one from your secondary ROM ---> means soft brick

I also had a talk with a multirom dev and I have tried to find a way around this especially when efidroid is able to handle it differently but there's no solution yet or will ever come. That means either pimp up/modify multirom to work like efidroid on my own or abandon the idea of multirom in FIsH..

Atm I feel more like the last one because the other option requires a LOT of work which means to rewrite many of the core code and there's a deal breaker: programming in C.

I can read and modify C but writing is out of my knowledge.

So I decided to abandon multirom in FIsH.

Current state of FIsH plate:

FIsH plate (the name was coming in my mind right now) is something BigCountry907 has created with my FIsH for his HTC device and the idea is to boot your device from the sdcard (plate) to bring several things up: full root access and so the ability to change whatever you like. E.g TWRP in FIsH. directly from the sdcard.

You remember? FIsH can be installed on a rooted device ONLY!

That's still true but with this you can boot TWRP even on a not rooted MM / N by using the FIsH plate..

The whole process makes use of a qualcomm feature which let you do this.

- the whole process is incredible complicated to get it working!!!

- the whole process is very sensitive and you have to find the right combination of needed partitons to make it work

- the whole process is a complete try & error

- if I mean IF I get this working I could patch the bootloader partition on that sdcard partition without touching the REAL bootloader to test without bricking...

- I work together with bigcountry907 to get it working but we live in complete diff timezones which makes it not easier :P

Complete OT:

Current state Bootloader investigation:

- I was able to extract the LG certificates (and something which I can't say what exactly it is.. But they are marked as rsa key files) out of the bootloader

- due to the amazing g4 technical unlock discussion thread where many ppl have already discussed some of the ideas I had in my mind I was able to understand the main verification process

- fact is you need either the private key from LG or you need to find an insecure implementation within the device bootloader or aboot

- fact is that the unlock file which you will get for those devices which can be unlocked is hashed/encrypted so can't be read and there are very high chances that it contains your imei and device id

- fact is that the aboot of h815 and h818 and I believe for all other models are using the same certificates to validate the unlock

- fact is if someone is able to find a hack based on a code finding or tricking the unlock verify it should work for any G4 model

- fact is without testing (with high chances of hard bricking) there will be no way to find a unlock solution

- afaiu each device will generate several device specific magic values (at least with your device id and imei) and compare them with the magic generated from the unlock file. If you could generate those magic values on your device you still have to sign it to have it accepted.. Which is not possible without the priv key.

- the other options require to modify device partitions which is near impossible because of the trusted boot chain. Means you can't just flash a patched bootloader and that's it. It will soft or hard brick your device because the verification will fail

- there's still a chance to find something over seen by others but that is a very tough job

- before you get too excited about what I do/have done here: I don't know if I will find something and I even don't know if I will proceed investigating!!! It's just i want to understand how things work - eg. the unlock process

.