yashsingh1/xdaforums huggingface dataset:
[G4 General] steadfasterX:
The current SALT version allows to flash already (with a "secret" start flag) but while it works for me it might not for others. It might not get released anyways as all newer Download mode versions are too restrictive without special adjustments.

reg 1: no not necessarily because a) some models can be cross-flashed and b) Frankensteins get a new PBL (primary bootloader) and nobody knows WHAT they actually flash (i.e which certs get trusted).

reg 2: both are possible but MM is a strict requirement.

as long as you find a ROM based on MM which gives all functionality it SHOULD work UsU'd as well. vs986 or h810. but.. as it turns out to be a vs986 you should note that we have users which are on Verizon network where it works for some and for some not https://github.com/Suicide-Squirrel/issues_pie/issues/41

reg 3: yes but as your Frankenstein - PBL allowing you to boot both you had luck.

reg 4: regardless if it is a vs986 or h810 (both are fusing devices) you should (!) be able to revert UsU as written in FAQ #1. Switching between stock Android is possible only when you ensure you stay at the same ARB.

reg 5: again, the most annoying and important thing about Frankenstein devices is: nobody knows. The main issue with these is the PBL which we cannot read (without special hardware and knowledge) and that one is responsible for ALL THE REST. It may behave like whats on the mainboard, it may behaves like what you bought it for, it may behaves neither one nor the other. It is like a blackbox or a wonderbag.

reg 6: as mentioned several times, Frankensteins are like wonderbags, I cannot say it will work or not, I just can say the risk is dramatically higher with them.

That leaves one question though: would vs986 firmware be possible to flash? From your story it seems there were no vs986 ROM installed so it MIGHT work or not.

ok anyways regardless of that, "reg 2)" above is the important one.

My recommendation is (if you wanna take the risk at all) now that you know how you can revert back the UsU state on your h810/vs986 device you might wanna go that way again now that you are on MM. But only if you are

not

on a verizon network.

.-
[G4 General] vert21B:
That's bit disappointing with their restrictive download mode, i won't even buy LG again because they won't give you your freedom. Next time i will just consider phone's which i will have peace of mind unlocking my bootloader and doing whatever i want as it's MINE.

My h810 is absolutely on AT&T in fact my brother said he unlocked it at a repair shop before he was able to use other network.

And NO, my h810 is not Verizon stock firmware everything is purely AT&T with their bloatwares :mad: all over the phone.

Yah i think am gonna UsU my h810 right now. Now that am on mm everything should work fine, hopefully. If not :cool: , my h810 has a history of tolerance, respect, obedience and forgiveness :laugh::laugh:

Am goona rest the h812 and give another try to UsU to h810 which i really wanna do.

See ya in a bit.
[G4 General] vert21B:
Hi steadfasterx, i officially confirm that my h810 is immune to UsU bricking :cool: as i can use UsU and go back to FULLY stock without any worries..just one click button and am on full stock and vice versa:laugh:

I UsU my h810 again after its on MM, then i flashed several roms and my findings and improvements were as bellow;

1. Rom is now smoother than previous

2. Network is very stable

3. No unnecessary lagging

But now the weirdest problem still exist :mad:

That's "i can't settup screen lock either pin, password or pattern" no matter the which rom i flash. the only option working is between swipe and none. Which is kinda mistry why it's doing that to me :fingers-crossed:

Again i flashed stock nougat in one of your faqs and so far that's the only rom i which screen lock is working.

I couldn't use that one because;

1. No network

2. Only front camera works (but previously when i missed requirement no. 3, no camera at all)

3. Can't play media (music and video)

4. Earpiece not working.

Of course i flashed the "kernel" but its purpose i guess is to brick the phone because whenever i flash without kernel it boots up.

Any modem i flash too brick the phone.

UsU baseband doesn't brick but couldn't help either.

Now i went back to fully stock and waiting for new suggestions and advice.

My thought is, maybe UsU is not fully UsUing my device correctly or am wrong?
[G4 General] steadfasterX:
UsU is working correctly on uours. Regarding stock nougat no idea without logs and that requires an insecure kernel to log properly on boot. The way it SHOULD work on stock nougat is your MM modem partition + UsU kernel or MM modem partition + baseband package with and without UsU kernel. Ensure you FORMAT data partition (special button in wipe menu in TWRP/SHRP).

It's clear that camera , audio are not working without UsU kernel or baseband package. That's why both exist.

Again if that does not work you have to create an insecure kernel by modding the boot.img (UsU kernel). Particulary that means setting it to permissive and disabling adb auth. Then you can run several debug cmds on boot like

adb logcat -b all

and in parallel

adb shell dmesg -c (best in a loop or repeatedly all the time )

So if I understood correctly custom ROMs are working for you (camera, network, call, audio) just not the screen lock but all the rest works now?

Do you have used FORMAT data before trying the screen lock on a custom ROM ?

Flash LOS pie and follow the FAQ on how to provide a "specific issue" log and post the link in the LOS thread.

If you want to spent time on stock or custom ROM troubleshooting is up to you ofc.
[G4 General] vert21B:
Of course UsU is working everyone just that this device is kinda weird and a Frankenstein.

As matter of fact, i usually format everything (davik, system, data, internal etc) before any rom flash as i have my important stuffs on the h812.

The thing about my h810 on this nougat is that the UsU kernel doesn't have effect on it at all, which should restore sound and camera while the kernel do the bricking stuff.

Building an insecure kernel? That's a new thing to me but i would love to know how though.

Yah you understood right, everything is working correctly on custom roms ( your LOS, havoc, aosip, pixel experience) for this weirdo phone but ONLY SCREEN LOCK doesn't. (note: screen lock works only on stock roms even on your nougat)

As i said earlier i have nothing important to lose on my h810 so i format everything in recovery mode including internal storage. So clean format is it.

Unfortunately my little adventure has to be PAUSED for a while. :(. My sis dropped her phone and her screen is not working so i have no choice but to surrender one of my phones because she can't go to repair shop (coronavirus lockdown :) )

I could have chosen the h810 to continue my exploration but

1. I need a working phone for different purpose

2. I hate AT&T bloatwares..i mean they are too many on the phone (that's even if i should return to stock with h810)

So for that reasons i will gladly surrender my h810 for now.

Thank you veeeeeery much steadfasterx for your time and patience.

Hope to continue later though:laugh:
[G4 General] mkrts:
https://xdaforums.com/showpost.php?p=73492882&postcount=3

if i flash this , will error message go ?
[G4 General] steadfasterX:
Which error message? Ensure you read the OP (important: use a browser as the xda app is buggy like hell) and FAQ19 if you meant the secureboot one.

and read the whole FAQ as you're asking to flash a bootloader stack on an UsU device which is not made for UsU.. Thats the same as flashing a kdz/tot which has been mentioned over and over in the OP as well.
[G4 General] mkrts:
Yes sir I had read all the FAQ and all the thread

You had said there is no way to remove bootloader message

İ just confused when i see that post

Could you know what the op want to say in that post ?

Is there a message about bootloader in officially unlock method

Does the op talking about official method?
[G4 General] steadfasterX:
your mentioned post was written long time before UsU has been released.
[G4 General] mkrts:
dear sir

i have not officially unlocked any g4

now i have learned that there is also a warning message in official method

Also i had made a presentation for Turkish Noobs (I am also a Noob :) )

Now i have recorded a video in FWUL

Maybe Someone want to look at that video --> https://www.youtube.com/watch?v=avht0FnaupA

Also lookig at ARB Value --> https://youtu.be/aFfUTQYzEGU
[G4 General] murick_show:
something happend. At boot logo it takes like 2 minutes to boot to android, wifi stopped working. Everything else works fine. That is not cpu problem, I reballed it after wifi issue
[G4 General] steadfasterX:
There can a lot happen when reballing. Things like that are just one example .

Besides a hardware defect there is a rare issue for some users (not UsU related) where you have simply no MAC addr. Checkout the LOS 16 thread for that.

The first boot of android can take a long time.

Well in any case this is the wrong thread to discuss that ;)
[G4 General] mkrts:
Sir, is arb value changeable by flashing different kdz files ?

Can we downgrade or upgrade it ?
[G4 General] steadfasterX:
All details (also follow the tech links there!) are here: http://bit.do/antirollg4

The short answer is yes you can INCREASE (no one wants that though) the arb but never decrease it. Its a physical blown fuse not software.
[G4 General] naish@123:
I am getting this error pls help me

[IMG="Image 1"]https://web.500px.com/photo/1016906174/429837C2CBE246DF8529C7344EF729EF-by-Naish-Meghani[/IMG]

[IMG="Image 2"]https://web.500px.com/photo/1016906173/0EA3436DDC4341CBBBAF45A3E92E3E27-by-Naish-Meghani[/IMG]
[G4 General] sbagger:
no sim card AND camera video not working?

Hi there

I have installed lineageos 15.1-20200517-unofficial-h812-usu on a lg 812 running android 8.1.0 lineage os api llama 9.

I have a sim card which works in another phone running Tmobile vanilla ( calls wifi et al) but the same sim card will not work in this phone, I get a "no sim card" message and I am sure it's inserted properly.

Should I expect the sim card to work in this phone and os?

ALSO

the standard camera app video doesn't work, I get "camera error can't connect to the camera"

thank you.
[G4 General] steadfasterX:
1. this thread is about unlocking by UsU

not a LOS thread

. post in the according ROM thread pls.

2. yes the above should work if you flashed correctly (i.e. current bootloader stack, UsU based ROM without baseband package)

3. ensure you read and understand the known issue: https://github.com/Suicide-Squirrel/issues_pie/issues/15 which exists since Oreo in all ROMs.

.-
[G4 General] sbagger:
1 sorry, I am not used to this forum and keep missing that SIMPLE fact. I will make sure I don't do it again

2 thank you for taking the time to answer given 1

3 didn't know about that issue thank you again
[G4 General] dragano:
LGH815AT-00-V20i-SEA unlocked

Hello,

successfully unlocked a foreign phone which was denied by LG to unlock. Was a slightly bumpy ride, as the FWUL update did not work fully, it got stuck during boot of the graphical part.

I installed SALT on my MINT distro instead and followed the instructions which was successful. The desktop icon did not work but manually starting the program did.

The only thing that was not really obvious to me was that after flashing the ROM the usu-twrp had to be reflashed. Did it and BANG - it worked!!

Thank you very much for your efforts, you gave 2 old G4s a new live.:good:

dragano
[G4 General] guillefs:
HELP.

unlock my G4 H815P. OK

flash trwp in fastboot OK

reboot in trwp "OK" but the touch screen does not work in the recovery and I cannot access any trwp menu.

If I start my phone it works as usual. But my touch only works if I turn the screen off and on again. Any way to operate trwp without touch?

EDIT: The last TWRP touch screen does not work . OLD versions works OK !!!
[G4 General] steadfasterX:
Can happen with frankenstein devices or when mainboard / display has been exchanged
[G4 General] guillefs:
Yes.

In my phone I changed the dead H815TW motherboard for an H815P motherboard and from that moment they had phantom touch problems and the final recovery didn't even touch.

Could you give me a little more information about these franskeinstein equipment problems?

Thank you
[G4 General] steadfasterX:
Unfortunately not. The only thing i can say is it is hardware related then. Maybe you touched a sensor or just a bit too much pressure at the wrong place.. Even though it is a replace friendly phone doing that is like balancing raw eggs while driving the highway on a motor bike.
[G4 General] guillefs:
Yes, it could be that when changing the motherboard several times I have tightened the connector of the screen too much and some pin of the touch is unsoldered.

The strangest thing is that at times when the battery is complete it works almost perfect.
[G4 General] marcelrobitaille:
TWRP not showing REAL device model when connected to the PC

I followed the instructions diligently, but TWRP is still not showing the correct model name in my computer. If I try to flash a rom, I get: "E3004: This package is for device: g4,p1,h812; this device is �ro.product.name."

recovery.log: https://bpa.st/X7NQ (sorry, I'm not allowed to post outside links)

dmesg.txt: https://paste.omnirom.org/view/46bc2931

ROM I'm trying to flash: Your build of Lineage OS

ROM version: MM

Not encrypted

H812
[G4 General] steadfasterX:
This can happen in rare cases just follow faq 25 and it will be fixed
[G4 General] marcelrobitaille:
Worked a charm! Thank you sir!
[G4 General] baran1706:
i have read this thread, maybe i have miss, is there a way to unlock device with ARB 3?

i have LG G4 H810 with ARB 3
[G4 General] ThePiGuy:
Unfortunately not. ARB 2 or lower is required (see Requirement 2 in the main post for more info)
[G4 General] Sazobaer:
Im getting ERROR 7&6 While flashing Custom rom in TWRP How to Solve?

I unlocked my device with this technique...so thanks for that....But now I cant Able to flash any Custom Roms They Getting erro7 ...but i Figured it out and solve that....but after solve error7 its getting error 6 in twrp when i tryed to flash..(Im in lp H815 10c and i finished Your Usu Unlock method while having Lp)so my software is lp till now......I tryed many Ways But any one of them didn't worked (execept just error7 . by removing assert line from the update.script of that rom..but after finishing that..im having error6) plz plz plz plz plz plz plz plz plz plzZzzzZZZZZZzzzzZZZ

Help me out SteadyFasterX....Appreciate for Usu guide ...but Now I need help!!!!!!:crying::crying:
[G4 General] steadfasterX:
You're aware that unlocking on LP is not recommended?

These error numbers are useless.. A log is needed.

But the first thing you should do is upgrading your bootloader stack to 20p otherwise you will have issues with any ROM later. That's just ONE of the reasons why it's clearly mentioned in the guide to be on MM before unlocking. If you dont have a SALT backup ensure you do one NOW! Only when you have a backup flash this in TWRP: h815_UsU_20p_bootloader_20p_modem_TWRP-flashable.zip

From here: http://leech.binbash.rocks:8008/stock/LG/h815/20p/

Then reboot to TWRP

Then reproduce your issue and share the recovery log (see the guide in my signature).
[G4 General] steadfasterX:
you havent followed my guide, otherwise you would have used a paste service.

you havent followed my request otherwise you would have tried to re-produce the issue (trying to flash something) and THEN grab the log.

.-
[G4 General] Sazobaer:
I'm Doomed!!

After successfuly doing usu unlock every think seems fine but I had no root access to o tryed to root by flashing SuperSU zip in recovery but it doesn't work..after that i tryed many times to install the lineage os 16 but it's not flashing too...so iv tried to wiped my system data and cache and the iv tried but same it's getting failed with errors when iv try to install that rom...iv tried to access with my computer via adb but adb can't able to find any device... neither other software like lg up...I can't access my system neither recovery nor fastboot or download mode cuz it's not opening iv charged.my phone enough to I has charge but it's still not responsing what should I do now..if there's away to fix plz plz help me !

I love my phone so much:crying::crying::crying:
[G4 General] steadfasterX:
ok

1. supersu is from the last century and is end-of-life. use magisk.

2. what happens when you boot in the recovery mode? Follow the exact procedure in the OP (see changes in behavior)

3. if the screen just keeps black whatever you try (booting to fastboot, booting to recovery, booting to download mode) you might get hit by the ILAPO, see FAQ #14

.-
[G4 General] coder.toolbox:
device firmware must be MM

Hello [MENTION=5545101]steadfasterX[/MENTION],

I'm working through this LG G4 tutorial to unlock my newly acquired phone.

Caveat: I bought it via AliExpress as a H815, but SALT reports it as a "device model: LG-H810, GPT comp: H811".

I took a screenshot and uploaded it on imgbb: ibb.co/9hRsXCj.

Within the device it states that the Android version is 5.1.

So now I'm stuck at "device firmware must be MM".

- firmware laf: H81010o

- firmware system: LGH815AT-00-V10h-GLOBAL-US-AUG-17-2015-ARB02+0

How would I go to upgrade this device to MM? [I tried already LG Bridge, but likely because it's a so-called "Frankenstein" device it wasn't able to update itself.]

Thanks!
[G4 General] steadfasterX:
...and another Frankenstein ...

The most important first:

Unlocking is always a risk. Well known. Unlocking a Frankenstein is like a lottery though. No one knows what they did at bootloader level.

At least 1 thing is sure: you have an ARB of 2. That's the most important part as it means if you would flash a h815 bootloader or kdz it would immediately brick.

So your model MIGHT be a h810. The only way to be sure is viewing at the mainboard as written in the faq. Even then this does bot necessarily mean that it behaves like a h810 as they modified the bootloader to be able to boot a h815 ROM. So who knows what would happen if you treat it like a h810?!

Other then that SALT detected a h810 bootloader which is usually pretty accurate but again .. Frankensteins are not usual.

Anyways if you just wanna take the risk then flash UsU and afterwards flash the bootloader stack of the h810 as described in the faq. You can do that easily by TWRP once installed.

The TWRP flashable download for that is here then:

http://leech.binbash.rocks:8008/stock/LG/h810/20n/

Ensure you download h810_20n_UsU_bootloader_ARB2.zip (so the UsU one).

Just to be clear you were TRICKED by ali express! I would try to get my money back as this is 100% no h815..

Ali express is full of frankensteins btw.
[G4 General] coder.toolbox:
Sadly enough yes :). But who doesn't love a challenge? :p

Anyway. I love the G4 phone a lot, so to me it's worth the efforts.

After disassembly (I took pictures so I can make a Franken-root tutorial later on ;)), the backside of the main board shows:

- EAX66488601_VS986_MAIN_1.0 (2)

- RISU80 (or something like that??) 94V-0X 1612K

The other main board had "EAX66473001_1.0_F500L_MAIN" on it. So that's an F500 bootloader I need right?

So, based on, for the first I assume I need the VS986 partition instead of the H810 right? And for the second I don't see a bootloader on your leech site?

(fun: is it H815, H810, H811, VS986, F500, ... ? wtf do they do there in China?)

Based on the numbers on the mainboard I would need to take the "vs986_2BA_UsU_bootloader_arb2.7z" instead, no?

I don't know if these are compatible though. It's both arb2, so I wouldn't hard-brick the device, I think?

I could send it back, but that would cost about as much as buying a new phone. They offered me a $5 refund though. So not bothering with the refund and going to try to root it anyhow.

Found a European variant on a 2nd hand site over here for €15 (broken glass, but otherwise workable -- H815 + arb0 + Android 6.0). So that one would go much smoother anyway. Will see how that goes after I get it.
[G4 General] steadfasterX:
woa.. yea a Frankenstein puzzle as it can't be better.

ok so if you wanna go that route I would first search for 2 things: vs986 QFIL files and H810 QFIL files. Both must be on ARB 2 - not lower - not higher.

you can verify the ARB with linux (u need mAid anyways) so find the sbl1.img in the QFIL package and do this in a terminal (right click within the folder in mAid -> open in terminal):

strings sbl1.img | grep SW_ID

the long chain of numbers has in its 6th or 7th digit the ARB level , or share the output here.

It is hard to completely hard hard brick a LG G4 thats the good point. When you have QFIL or a box like infinity etc you can recover from almost every brick (other then ARB mistakes)

once you got that I would go on with the h810 tbh. I mean it might hard brick - thats why you should have QFIL prepared - but if the current bootloader stack is h810 its better then the vs986 one.

vs986 might have issues when in Verizon network but if that does not affect you it is maybe not a big deal.

anyways I would flash the h810 bootloader stack and if it bricks use QFIL to bring up the vs986 one first.

either they modded the bootloader stack or they modded the PBL (read-only flash) to be able to load a h810 bootloader. Even then .. I mean why modding it to load a h810 bootloader instead of the vs986 one? The only thing I can think of is that the vs986 may act a bit different for the radio/baseband so they wanted to avoid that and as you cannot remove fuses (i.e. ARB) they took the h810 one.. well just guessing here. but if (and thats still a question) this is a h810 bootloader stack I would go on with that one.

.-
[G4 General] coder.toolbox:
:good: Check on the ARB, I'm extra careful around that one ;).

So from your comments I understand:

- Hardware: VS986

- Bootloader: H810

- Software (faked?): H815

Problem: I found a bunch now (H810 Fix By QFIL -- SW_ID included 00..2..00 so arb2).

I also found rooted tot files... At least that's what the name suggests: for example: "LGH810AT-00-V10o-ATT-FixFull-Rooted.tot"

And I found some 512MB dump files... I vaguely remember seeing another post discussing here that you could extract partitions from it, but I fail to find that post again. But I also remember reading somewhere that you needed leaked qfil files to be able to use this method (correct?)?

Anyway, H810 qfil found, no vs986 except for some dumps (all arb2 -- 13b kdz, 24c kdz & dump, 25a kdz & dump, 27c kdz & dump).

I added a few of the files into a mega drive: mega.nz/folder/0wUwASIC#sQHqSNKoRAzmevy3HLhUgQ. (for anyone looking for these --> Could you confirm these are the correct ones?)

Next step would be to flash the "h810_20n_UsU_bootloader_ARB2.zip" as mentioned in FAQ #20?

But wouldn't this cause an issue internally? As this bootloader is 20n (from experience 20 seems to mean MM), and my OS version is 10o (LP)?

I don't really care about the calling network.

It'd be nice to have it, but not really caring very much. I would use it as a wifi device only anyway.

Also, I took a backup as suggested. So when I flash them and something goes wrong, I can just re-flash the original partitions and be on my merry way? [confirm/deny]?

Thanks for your support! If I can do anything to help :)
[G4 General] coder.toolbox:
Hello [MENTION=5545101]steadfasterX[/MENTION],

Next step would be to flash the "h810_20n_UsU_bootloader_ARB2.zip" as mentioned in FAQ #20?

But wouldn't this cause an issue internally? As this bootloader is 20n (from experience 20 seems to mean MM), and my OS version is 10o (LP)?

Also, I took a backup as suggested. So when I flash them and something goes wrong, I can just re-flash the original partitions and be on my merry way? [confirm/deny]?