[G4 General] steadfasterX:
ok folks..

I NEVER believed that this will happen this way (without limitations) but its the time for miracles right?!

today i was able to fully unlock my H815 without any known limitations!

Camera

Sound

Cell service (yeeeeha!) so calling, SMS

LTE (yee.. u know)

WiFI

TWRP

LOS

ARB=0

everything fine....

and yes it is still a H815! still ARB=0 and no fuse blown. so I can go back fully..

This should work the same way for any device but every device needs to be prepared different with different files.

Pls forgive me but i need to prepare things first. Just wanted to let you know that something good is coming..

Note:

This should do for EVERY device which

never

used the EVIL firehose and still have an ARB lower then 3 (so one of 0, 1, 2 will work).

tbh even any other device could work if we will be able to flash the files we need in download mode. This

MAY

come with SALT one day.

Cheers

yours steadfast steadfasterX

UPDATE:

I flashed the N bootloader which in general works fine so far but I get Kernel crashes now. The main reason for this is:

[ 7.600264 / 01-01 00:04:24.049][0] Fatal error on the modem.
[ 7.600299 / 01-01 00:04:24.049][0] modem subsystem failure reason:[B][COLOR="Red"] lge_init_fw.c:175:lg_model_name = .[/COLOR][/B]
[ 7.600311 / 01-01 00:04:24.049][0] [LGE] MSM Chip info : MSM Chip version 10000 ID fb FML 39.
[ 7.600324 / 01-01 00:04:24.049][0] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = SYSTEM.
[ 7.600399 / 01-01 00:04:24.049][0] M-Notify: General: 8
[ 7.600416 / 01-01 00:04:24.049][0] lge_disable_watchdog
[ 7.600425 / 01-01 00:04:24.049][0] panic in suspend: 0
[ 7.600435 / 01-01 00:04:24.049][0] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.

I will give it another try with the MM bootloader stack now..

UPDATE2:

Ok I flashed the MM bootloader stack and the same as for N. It seems LG prevents the use of the not matching modem partition (so when modem != LP ) and then the kernel panics.

the instructions in the kernel are here

and here the panic

Don't get me wrong the kernel is not the reason it acts as it should. The modem cannot be initialized and so it panics.

I will investigate that further but first:

LP bootloader stack plus latest AOSCP-N (2017-12-18) boots fine, camera, sound etc all is working it seems :)

UPDATE3:

so.. after modifying the kernel to not panic (thx [MENTION=5461026]kessaras[/MENTION] ) I'm able to boot AOSCP-N even when on N bootloader stack. With some limitations: no baseband :P, no adb but hey camera and sound is working ;) Ok I will investigate this further but now.. its christmas time.. ;)

UPDATE4:

While trying to find the root cause of that model checking and so modem crash I find 2 files which may take the responsibility for this. b13 and b22 containing traces for this and I will first try to replace just those to see if it would work. If not I will replace all baseband files to see if that works which would mean to have a LP baseband with a N camera etc.

In parallel I will try to get through the disassembled code of the baseband files (which are heavy) to maybe just disable that check on the MM and N basebands. This one would be the most elegant way to solve the issue but the hardest task obviously.

Just writing down everything as Christmas is near and I may forgot something otherwise ;)

UPDATE5:

ok replaced just b13 with no success.

replaced b22 as well with no success.

replaced all modem* files: success.

Just booted Oreo and everything except camera (which is a general issue we are currently working on) is working..

i may look into a better approach of using the N baseband files later (hexediting maybe).

Conclusion: This method can boot any ROM now (including a proper firmware partition) with a small modification

.