[Thread Moved to General] Unlocked Bootloader on H818!

[Halapeti]

Can i use this method for H818N also,
Please can any one write detailed instruction to unlock bootloader & which TWRP & how to install.

 

[kessaras]

find partitions , aboot partition

Can i use this method for H818N also,
Please can any one write detailed instruction to unlock bootloader & which TWRP & how to install.

wait for him to update his op.
me i dont know this way to view the partitions.. mounted partitions are written in /proc/mounts and all partitions are listed using the command

sgdisk --print /dev/block/mmcblk0

from pc terminal of course using adb shell its:

adb shell
su
sgdisk --print /dev/block/mmcblk0

mmcblk0 in our G4 is the disk name that LG used. So sgdisk lists the partitions of that disk that we chose in the command above.
And aboot is no.8 here on mine. so mmcblk0p8 is the aboot partition he is talking about.
i dont wanna brick your phone, so wait for the op to read again what he wrote.
That command in the op to find the aboot partition is totally wrong and useless.

you can test it on your phone to 'dd=...' that file in the op if you want, after you use this command to find the aboot partition.
But be ready , if the OP is wrong, you will have to use kdz to restore

And sorry for the edits i wanted to explain too, so that you all understand the command.

 

[Engelm]

Is ist possible to write this modded partition via flashfire?

 

[kessaras]

Is ist possible to write this modded partition via flashfire?

use my command above to find aboot and only use dd in the op to force copy paste the file.

flashfire too can do it. it has a choice for secondary bootloader (aboot).
First backup your aboot of course.

~EDIT: flashfire uses 'dd' too. If you go manually and not with flashfire, you can backup your aboot using dd again. you just do it reverse and choose to copy it to the /sdcard/ and from the sdcard you can take it to your pc.

AND i don't know if a mistake in the secondary bootloader will cause a bootloop. That's something out of my current knowledge. So if you won't be able to boot, you can't restore it to fix it. So the only method to fix it is KDZ.

 

[goran_oh]

Tnx for sharing

Sent from my LG-H815 using Tapatalk

 

[steadfasterX]

Patched the secure boot validation function. The patched aboot has the secure boot set to always valid condition no matter what image you flash.

Yeah but how do you patched it? Speak technically what do you have done to patch aboot please .. Do you have used a hex editor and if so where do you edit and how?

Explain it to me in a way so I can patch my aboot on my own. This would help a lot..

THX


Sent from my LG-H815 using XDA Labs

 

[pvineeth97]

Yeah but how do you patched it? Speak technically what do you have done to patch aboot please .. Do you have used a hex editor and if so where do you edit and how?

Explain it to me in a way so I can patch my aboot on my own. This would help a lot..

THX


Sent from my LG-H815 using XDA Labs

I am not gonna reveal it out since LG is gonna patch that too in future releases just like how Bump! and everything else was patched.

The methods aren't the same for every phone so there is no one method in patching it.

 

[pvineeth97]

As in case of g flex 2..
Everyone be warned..
The aboot on lg k10 is not signed
But in lg g4 there is a hash verification to aboot.
It may result in a hard brick.. so be warned

FYI, even K10's aboot is signed since it has verification keys embedded in it.

 

[kessaras]

I am not gonna reveal it out since LG is gonna patch that too in future releases just like how Bump! and everything else was patched.

The methods aren't the same for every phone so there is no one method in patching it.

so what ? you can update the modem only the same way we all do.
we extract the KDZ stock rom from LG and flash only the modem.
This way you are up to date, able to flash latest and any custom rom.
So sharing with our twrp dev is for the best.

Also, LG won't and can't patch an old KDZ -_- in the OP you said they all have to downgrade to lollipop

 

[uio88]

Is this method functions with h815?

 

[steadfasterX]

Can someone test TWRP after patching?

If you use my latest beta you should see that your device will be shown as DETECTFAILED in your file explorer when connected to a PC. I need the recovery log of as many g4 variants as possible to fix it in clean manner..

If there are users not willing to patch aboot yet do me a favour and do an:

adb shell getprop

and paste the result to http://paste.omnirom.org

Same here as many g4 variants (h818t h818n h815 sea and whatever else) as possible.



.




Sent from my LG-H815 using XDA Labs

 

[adds08]

I am not gonna reveal it out since LG is gonna patch that too in future releases just like how Bump! and everything else was patched.

The methods aren't the same for every phone so there is no one method in patching it.

U may not need to and it may not hinder with the twrp creation either..

FYI, even K10's aboot is signed since it has verification keys embedded in it.

Thats oddly strange as any modification would lead to loss of data integrity and will result in the rsa sha256 public key not being able to verify the aboot image signature ..
Oddly strange but i do hope this works

so what ? you can update the modem only the same way we all do.
we extract the KDZ stock rom from LG and flash only the modem.
This way you are up to date, able to flash latest and any custom rom.
So sharing with our twrp dev is for the best.

Also, LG won't and can't patch an old KDZ -_- in the OP you said they all have to downgrade to lollipop

The dev doesnot compulsorily share the method bcuz of what happened with bump.. he may use this method for further devices and by what he claims i guess its pretty simple idea he implememted.. changed the instruction such that the secure boot verification is always set to secure

 

[pvineeth97]

U may not need to and it may not hinder with the twrp creation either..



Thats oddly strange as any modification would lead to loss of data integrity and will result in the rsa sha256 public key not being able to verify the aboot image signature ..
Oddly strange but i do hope this works



The dev doesnot compulsorily share the method bcuz of what happened with bump.. he may use this method for further devices and by what he claims i guess its pretty simple idea he implememted.. changed the instruction such that the secure boot verification is always set to secure

Yeah... just the set the secure boot verification to always valid. I already shared the secret. Use IDA PRO Disassembler.

 

[onotor]

Looking forward to the news..

Sent from my LG-H815 using XDA Labs

 

[steadfasterX]

Looking forward to the news..

Thread moved to General - https://forum.xda-developers.com/g4/general/unlock-bootloader-h818-t3564238

Sent from my LG-H815 using XDA Labs