yashsingh1/xdaforums huggingface dataset:
[G4 General] sushant_:
Wow!!!!

That's great news.

Does it means I can boot the cyoher OS oreo on my LG F500L?

CAn you provide me the deatils I want to try out.

Or can you give me the link of F500L, unlocking procedure?

Thanks anyways :)
[G4 General] steadfasterX:
yes that means you could boot even Oreo.

you got a PM. check it out and take the risk to wait or not - for a maybe needed recovery if (very unlikely) it fails :)

if it fails you have to wait until im back though.

Thx
[G4 General] sushant_:
Woow, Amazing I guess I Lineage OS 14.1 was for H815/H811.

SO, it's a pretty amazing thing to get it running on H812.
[G4 General] doomanix:
H812 LP and MM Unlock Test

Not sure if this would be helpful as the H812 has already been tested but I currently have two LG G4's; one on Lollipop with the Bootloop issue *but stable with cores disabled* and one running Marshmallow. Both are carrier unlocked and are are running on Freedom. I read earlier about the issue with the change in the GPT between LP and MM and thought if there was any way I could help by testing the unlock on both firmwares I'd be happy to test it. I'm also curious with the Bootlooping G4 if that means I'd need a modified boot to disable the cores at boot and if this would change the way in which the UsU aboot would need to be modified. If anything I've been waiting for this to be a reality since June of last year and I just wanted to thank [MENTION=5545101]steadfasterX[/MENTION] for all his hard work and dedication on what I feel is the last (and best) removable battery mobile phone out there.
[G4 General] steadfasterX:
Update for the current issues

H818

the touch driver gets not loaded on the test users device. this is very odd and I currently investigating why.

This happens in TWRP and in the ROM. Flashing another firmware (modem partition) does not solve the issue (we tested several).

At this stage it can be only an issue with the UsU aboot or a general hardware issue of the device (unlikely.. but who knows). So we will bring back the device to completely stock now to see when exactly the touch breaks.

This issue does not happen on any other G4 I unlocked before so its really weird... (and the reason why releasing UsU yet is too risky).

...and the good news

.. as I like good news .. ;)

The new SALT GPT compat check seems to work fine on several devices (validated and shows the correct result)

I can say the following: UsU will work on devices with ARB > 2 . Keep in mind that bricking such a device requires LG service so its always more risky then with ARB 0,1 or 2. .. but I flashed and booted an ARB device with ARB 3 fine.

Cheers
[G4 General] networkkid:
Update: I installed LineageOS Unofficial 14.1. It' s working flawlessly. :)
[G4 General] sushant_:
What was the model of your deivce? And which version did you flash?
[G4 General] networkkid:
I installed LineageOS Unofficial 14.1 on my H815 TWN.
[G4 General] Tomonok:
I dont know if it can help but I tried installing a while back the Nougat kdz for the Korean F500 on my H818P and I ran into the same issue, my touchscreen did not work until I flashed back H815 or H818 rom.
[G4 General] obvious:
I had a frankenphone with the same issue
[G4 General] steadfasterX:
Everytime when I think I am done something weird happens like now for the h818 device.

that device is very likely a Frankenstein device as well which may explain the strange behaviour of touch screen and maybe explains the strange recovery behaviour we had yesterday too:

Currently the 818 is in hard brick state as I ran out of time yesterday after some hours of analyzing and troubleshooting.

This is another good example why a backup with SALT is crucial important as of Frankenstein devices..

... and also a good example why releasing UsU at the current state

is not a good idea. Especially because I'm on vacation soon.

I hope for your understanding it's to your best.

Today we will restore the taken backup and see if we can fix the touch finally. I'll keep you updated.

UPDATE

ok so long story short: Its proven now:

Even when this is absolutely against everything I was able to identify during the whole journey and all I asked told me that this is not the case:

not only firehoses and sbl will blow fuses also aboot contains code to blow fuses (well or sbl reads aboot ARB and set it accordingly).

H818 touch screen stops working after flashing UsU

What does that mean? This means you cannot go back once flashed - at least on those devices having no ARB (H815,H818,...). Other devices

MAY

can go back (has to be proven again though) as they could flash a firmware with ARB v2 which others cant.

What does that mean for the

H818

? At the moment this means: Android stock boots, no touch. AOSCP-N boots, no touch, TWRP boots, no touch! This means its unusable atm and we cannot go back as it hard bricks then. I feel very sorry for [MENTION=1385167]jmfecon[/MENTION] who owns that device. I tried everything possible to identify the root cause and solutions and narrowed it down to the mentioned result. thats 100% sure and I cant change anything on the fact of blowing fuses. The only chance to get this working is identifying why the synaptic touch driver/module can be loaded but not used.

The good news: When TWRP loads I can access the device via ADB which is a comfortable situation. I can grab logs be root and I'm able to do a lot of tests about that issue (when im back from vacation).

btw: the touch issue itself makes no sense at all - especially the fact of the relationship to aboot. I'm pretty sure that there is no code in aboot related to that but there must be a relationship.

What does that mean for every other not yet tested device? Nobody knows. Maybe Touch will not work there as well... maybe there are other issues! If the device has no ARB 2 or higher firmwares available (like F500, 818, 815) this can result in a unusable device which only LG can recover (or by a mainboard replacement).

.
[G4 General] tnt719:
Freedom Mobile H812

Hello everyone, I've been a longtime lurker on this thread because I love my H812 and want to give it a new lease on life.

I'm with freedom right now on Marshmallow and haven't modified anything. LG did replace the motherboard though. I've been trying to understand how to unlock my bootloader so I can get Lineage OS.

Can anyone help me get started. Thanks!!
[G4 General] sushant_:
It's a very sad news for other devices.

I hope that he can bring back the device.

I think you should try flashing the F500 firmware on that device, maybe it could work.
[G4 General] steadfasterX:
Already tried. I tried many modem partitions like those from the f500 h815 and many others including different firmware versions.

As said.. Maybe the other variants will have absolutely no issues but I can't guarantee anything.
[G4 General] sushant_:
My device was H815 initially,when I received it. I tried updating it from LP to MM, but I got the blank screen. Then I flashed the F500L .dz files extracted from the .kdz file.

I flashed it in LGUP, and then It worked !!!
[G4 General] jmfecon:
First, I would like to thanks [MENTION=5545101]steadfasterX[/MENTION] for all the effort that he put into this. Working with him to troubleshoot this makes me wonder how hard was to him to get the solution up to this stage, which is really great for anyone who own a G4 and want to break free from LG chains. Also, to thank him for all the effort to make my device work, but unfortunately was not possible right now.

But not all is lost, it boots the rom, the camera is working, the rotation sensor. It seems that only the touch is not working, as he said, very strange. Will try to investigate myself, specially because I have no other phone around :( (well, I have a Nokia 5233, but I do not know if that counts as a "phone" nowadays...).

That's why he did not released it yet. Be patient, testing this is not for the faint of heart, and even the brave ones can have bad results.

Now let me check if my Nokia downloaded Whatsapp, it takes really long when this is done at 1,37 Kbps...
[G4 General] AlexBodewig:
Does unlocking the device through UsU mean that we can no longer use the stock firmwares on h815 devices, or is it possible to flash stuff like the v29a files through twrp? Aside from that, We'd be free to flash over any ROM built for the h815 in general, correct?
[G4 General] steadfasterX:
Tbh I have to thank ppl like you taken the time and willing to test as I do not have any model to test with.. It was and still IS really a pleasure to have such testers! Thank you all!

You can use stock.

You can use custom ROMs.

You can use even v29 bootloader (I have made a UsU package for this) and it works fine as I wrote in a previous post.

Which ROM can be flashed depends on your gpt and SALT will tell you which is compatible with yours.

I think we will see maybe model specific ROMs in the future. Depends on how good they work for every model..
[G4 General] AlexBodewig:
Thank you for the clarification.
[G4 General] sushant_:
Does anyone know what does this OEM Unlock do?

This is available in the nougat developer menu.
[G4 General] AlexBodewig:
This enables access to the bootloader(adb reboot bootloader), I.e. it's the option you turn on to be able to use fastboot commands. If you run that reboot command without turning on that option, it'll tell you to enable it and then boot normally.
[G4 General] adam_s_459_:
So as you were saying earlier about the partition tables and such on the h810 [MENTION=5545101]steadfasterX[/MENTION] , is there any way to know if my h812 on stock marshmallow should flash either device model once this gets released? My carrier is Rogers by the way. Thanks for all of this I can't wait to flash ROMs.
[G4 General] terence.tan:
Are you using a custom kernel, or the same kernel that was originally on the device?

I think the touchscreen was interesting as the Synaptics driver was compiled directly into the kernel, not loaded from a partition. (Including a firmware blob also compiled directly into the kernel.) Perhaps H818 needs a special kernel?

This is speculation based on what I've seen on some other devices, maybe it doesn't apply to the G4.
[G4 General] steadfasterX:
When you start SALT it will tell you your devices ROM compability.

This way is the only way to identify what ROM you can install later.

We can't say the model XXX can install XXX. It depends on what gpt is active on the device.

E.g. If on LP you can have another gpt then on MM. So just check SALT and that's it.

No this is not just guessing it's the first thing which came into my mind when I saw the dmesg ;) I used several kernels in my tests but only titan in twrp.

When back I want to use the regular 818 kernel in TWRP to see if and how it behaves then. The thing is... it makes still no sense. Even when booting 818 stock ROM the same issue appears which is really weird. But I want to use the 818 kernel in TWRP as I have full access then and maybe get a clue what happens.

Sorry was not able to upload the dmesg but it shows the synaptic module itself get loaded but writing into a buffer failing with timeouts. After that many errors happened and the module lge_touch don't get loaded at all. Still no idea what this should had to do with aboot...

I will also look with IDA again into the UsU aboot to maybe get more ideas as well.

Besides that I will look into the 818 kernel sources as well to get an idea how this is implemented.

This is all not the end yet. I have many ideas and things I can try but the best bet will be to identify the root cause in aboot as it definitively is related..
[G4 General] jmfecon:
Well, I got a dmesg log when was trying something: https: //hastebin.com /afinipikuy.md (because i am not allowed to post links) . Any ideas or analysis on it will be useful and appreciated.

I sent my phone today to LG service, let's see how they will fix it, if it is just necessary to download the stock rom or something worse.

Cheers
[G4 General] terence.tan:
OK, it looks like you have considered a lot of things.

One more thought. The device hardware of H818 is different: it has an extra SIM slot. So all the hardware device addresses might have shifted around, i.e. it's got a different device tree.

When you boot from your modified aboot, you identify to the kernel as an LS991, right? Does that mean it picks up the LS991 device tree? Maybe you can compile a custom kernel where the LS991 device tree contains the H818 hardware map.

Anyhow thanks for all your interesting work :)
[G4 General] steadfasterX:
Yes I know that the 818 has a second SIM slot. The thing is you can flash the 815 boot stack to a 818 and have both SIM working afaik. So no I don't think this is like that. The rest of the hardware is identical between all models with only one exception the modem.

What we tested was a h818 boot stack (here the hardware like radio gets initialized) and 818 boot image, ROM etc. Only aboot is different. That's the reason why SIM has no issues anymore as in previous versions of UsU where we can't get signal etc.

Hm maybe it's all just much more easier.. Atm UsU has one little limitation which is on my to-do list: you can use only LP basebands. The reason for this is: aboot changes ofc the boot cmdline and the basebands in MM and newer expect a specific string before they get loaded. If you use a MM baseband it will crash. The fix for this would be simple: a little kernel change which overrides the cmdline with the expected one. This way we can use even newer basebands with UsU.

The workaround atm is that I have prepared an flashable TWRP UsU package for every model which just replaces the baseband files of the modem partition. This way LP basebands loading and everything else is left untouched (so you can even use N modem partition).

I just haven't had the time to look into this yet as it was important for me to get everything running..

The same may apply to other parts of the firmware like the touch sensor in the 818.maybe there it expects a value which is missing to work properly! This can be found out easily. I just need to compare the origin aboot cmdline with the UsU one...
[G4 General] steadfasterX:
No brave F500, US991, H819 testers out there?

Still have no users willing to test these devices..

If you own such a device pls send me a PM including the SALT debug log. Take a SALT backup and let me know when ready.

I have the instructions with me so that's not an issue ;)

Cheers

steadfasterX
[G4 General] obvious:
Get back to your holiday! ;)
[G4 General] augusto1024:
I have a US991 with ARB v4 (zvf). Is there any chance to hard brick it? If not, then I can test it (with dumb proof instructions provided :p)
[G4 General] steadfasterX:
Ls991 and us991 are very similar and ls991 is unlocked without issues.

a chance of a hard brick is general just around 1%.

What CAN happen?

- touch not working (was NOT an issue on h810,h812,ls991,h815. Only h818 had this. So the chance is 4:1 ;) )

- you could unleash it .. What I mean is.. it could just work ;)

- as you own a device with ARB > 2 you MAY even could go back to your current bootloader stack

If you want to test start with creating a SALT backup ( https://bit.do/SALTatXDA ) and send me a PM when done with your model in the subject.
[G4 General] augusto1024:
I'm sorry, i actually have an ls991 from sprint, my bad. If you need to test on my device no problem! :)
[G4 General] adam_s_459_:
So did you flash a custom ROM on your device? If so, did you're rotation work with it?
[G4 General] Ilaancue:
As UsU works with H815, does that mean that every H815 model is supported? For example. Will I be able to unlock my H815ar bootloader?
[G4 General] sushant_:
Has anyone tried this on a nougat build already installed before using this method.

(Only the device whose bootloader is locked tell me)
[G4 General] steadfasterX:
Auto rotation is likely an issue with an outdated modem partition.

When I say EVERY g4 model I mean it like that. ;)
[G4 General] adam_s_459_:
So that means that it wouldn't work on any ROM? Sorry I'm new to all of this
[G4 General] steadfasterX:
It's like with even official unlock. If you do not use a compatible modem partition you will encounter issues e.g. Camera is not working or sensor jssues. The fix is flash the right modem partition regardless if you use UsU or an official unlock.

The only difference with UsU is that you need to flash a UsU package after flashing a modem which I provide together with the UsU file. And Im pretty sure that even this may be not needed any longer when I have fixed some stuff.
[G4 General] sushant_:
I am not able to flash the aboot_UsU.

I put it in the download folder in the internal storage and it's showing that it's not in /data/media/0/Download

And then it exits.
[G4 General] steadfasterX:
See.. Without a log I cant say anything..
[G4 General] whitewolf1608:
A polite request for support with blocking the Bootloader in LG G4 h815

Hello Dear steadfastX

I am asking you with a very kind request to give me a free time

time to answer the question.

If I have placed the bootlader in LG G4 h815 according to this method

> http://developer.lge.com/resource/mobile/RetrieveBootloader.dev

Is it possible to be blocked again by another method?

After unlocking the Bootloader, I did not upload TWRP recovery in LG on the same day G4.

After changing the name of the image file. Img from twrp-3.1.1-1-g4 to lgG4-twrp.img, using Tool All In One, I downloaded TWRP recovery.

from this link> https://dl.twrp.me/g4/twrp-3.1.1-1-g4.img.html

Is it possible to be able to check it with a command or other tool

did TWRP recovery sound into a smartphone?

When I try to block the bootloader through Tool All In One, I have one

situations as on the attached screens:

https://drive.google.com/file/d/1bWTREiAnHc923csneFXF2hodjaT4dj3q/view?usp=sharing

https://drive.google.com/file/d/1RduTsw_ykkRr196gopPPOdm4Np9au7Xw/view?usp=sharing

https://drive.google.com/file/d/16j6IqDj7MzSgwOovEksakUj1rcQ4NseZ/view?usp=sharing

After clicking any key according to the third screen, it closes

CMD console in Windows. I turn to you with a very kind attitude

asking for help in the topic.

Regaeds Luke
[G4 General] steadfasterX:
This is complete off topic. Create an own thread and do not post here and write me a PM with the exact same stuff. This is not polite in any way.
[G4 General] mateus.sc:
deleted oops
[G4 General] djamolsky:
Hi,

I read all the topic, wow, very impressive work [MENTION=5545101]steadfasterX[/MENTION] ! :)

I own a LG G4 H815 SEA, I gave a try to your unlocking solution which asks for an aboot_UsU.img image... I couldn't find this file anywhere. Maybe it has not been released yet or need to be generated.

Any help or confirmation would be awesome! Thanks.
[G4 General] steadfasterX:
If you followed this thread you would have noticed that UsU is not released yet. H815 is proven to work so no further testers needed. Just be a bit more patient. ;)
[G4 General] SamilGokts:
I'm about to sell the phone. Please post a moment ago :(
[G4 General] whitewolf1608:
Hello Dear steadfasterX

Does the Smartphone LG G4 h815 have a built-in function of listening - uploading completely compiled Roma already with Root?

Dear steadfasterX I am asking you with a very kind request to give

me how to lock the bootlader in my smartphone?

I want to try the locked bootlader to upload TWRP recovery.
[G4 General] doop:
You will have to be patient like the rest of us :) steadfasterX stated the same 2 posts above yours.
[G4 General] datscoolmetoo:
Guess there's no hope for H818, right [MENTION=5545101]steadfasterX[/MENTION] ? Boring life...

And also i gotta be sorry for not making donation for yo amazing job. I'm from Iran and I can't access paypal rn. Hitting the tnx button is the only way i can appreciate it i think.

Cheers man
[G4 General] steadfasterX:
Ofc there is hope. I'm just on vacation atm. Clicking thx is fully enough. My payment is to kick in LG's ass ;)
[G4 General] grantdb:
You are kicking ass big time LG should put you on a payroll!
[G4 General] scholbert:
Touchscreen issue on H818...

Hi steadfasterX,

i know you're on holiday but i found something interesting...

I'm pretty sure i found the reason for this issue, but i'm really limited in time right now.

So my guess is, it is hardware related. Let me in short explain what i found out:

Here's some essential part of a hardware difference concerning touch controller on H818 vs H815 (european model).

By looking into the schematics i found something, which could be related to the touchscreen malfunction on H818 devices, when using other boot stacks.

While the basic interface to the touch controller itself is the same on both platforms, there's a small difference on the power domains.

On the H815 hardware the power domain +1V8_VREG_L10A (derived from PM8994) is powering up the touch controller.

You may check pin 49 on CN1 (display connector).

This is different on H818.

On H818 the power domain +1V8_VREG_L10A is used for the second SIM.

To power up the touch controller a separate LDO (U7501) is used.

This chip is activated by a dedicated GPIO of MSM8992 which then powers up a separate voltage called +1V8_TOUCH_IO.

GPIO_63 -> TOUCH_IO_EN -> activates U7501 -> generates +1V8_TOUCH_IO from VPWR.

You may check pin 49 on CN1 (display connector) here as well.

... or make some measurements on C7507.

As controlling the power domains is essential, even in bootloader mode, this setup maybe independend of kernel code.

In other words this is already done in aboot or related setup code.

This behaviour could possibly be fixed by using a work around in kernel code, e.g. by setting the MSM8992 GPIO_63 high at boot time.

Could need some other tweaks as this pin could be part of the power management on H818 as well.

Maybe someone needs to refer to the kernel sources!

EDIT:

As there are no custom kernels for H818 yet, someone should refer to the LGE open source package provided by their web portal.

Look for the related parts for management of GPIO_63.

So this is it in short.

Have a nice day!

Regards,

scholbert
[G4 General] steadfasterX:
Great stuff! You see it from the hardware point of view. Me I do it from the software one. The bootloader stack will stay device specific when using UsU with only one exception: aboot. I still believe that aboot is NOT responsible to initiate the touch hardware (like modem which gets loaded in sbl). As aboot is the only diff after flashing UsU it must be related though. I still believe that its just a special cmdline in aboot needed as aboot changes and / or extend that. As I cannot change it there directly it's a kernel overwrite needed but that's not a problem....

That's a fundamental change compared to early tries of an unofficial unlock where I replaced the whole bootloader stack. Now all hardware stuff gets initialized like it should and for the specific device model. aboot provides fastboot stuff is responsible to communicate on low level e.g. to generate unlock stuff on h811 or validate an unlock file for the h815. I never read anything about initialize hardware stuff like touch there. That's why I think it must be something else. I already know that aboot cmdline is wrong for newer baseband files for any device which I will fix as well by a new kernel.

I currently try to find and shot a damaged h818 on eBay which would makes things much more easier..

At all the h818 users out there (needs root):

adb shell

su

cat /proc/cmdline

I will grab this from the h818 aboot later as well but the above is a nice comparison.