yashsingh1/xdaforums huggingface dataset:
[G4 General] berkantkz:
Hello dear steadfasterX.

You may have seen that re-locking method through flashing tot files. As far as I know, he talked to you before publishing that guide ans you had confirmed that this way re-locked the bootloader which means removed the UsU.

His device was one of carriee labeled devices those are sold in USA. So, my question is would this method work on our H815 devices? I'd really like to have installed a custom rom on my G4 but due to that bootloop problem, and the fact that my warranty still goes on, I am a bit scared of unlocking it in this way. It may bootloop when I am on a custom rom and warranty may not repair it for free due to that custom rom.
[G4 General] steadfasterX:
I guess you are referring to this thread: UsU Removal and Relock TOT Method

Have you seen this in his OP?

That's 100% true as that's exactly what I wrote him. No re-lock possible for these.

JFI: I send my device in several states of hard bricks and UsU unlocked to LG several times without an issue but ... well there is no guarantee that this is the same for every country/LG Support center

-
[G4 General] berkantkz:
Yes, that's what I was talking about.

I now remember that I had seen it but didn't notice that it's for ARB2 versions only.

What's the reason behind that it's not possible for our devices?

Thanks for extra information. I also had sent my previous LG device, which is replaced with my current new G4, with bricked state. Even though it was bricked due to my fault, they replaced with G4 :silly:

Thanks again, man!

Edit:

Right after posting this reply, I tried to unlock my G4 (H815TR) with UsU.

I've run FWUL on a USB stick and updated the salt as well. When I clicked on unlock my G4 (don't remember the exact title ?), it has given me an error like "your laf is not supported. Downgrade to either lp or mm". Is this something special to me or a common warning for those who use stock Nougat? And also I would like to ask the reason behind no support on Nougat laf.

Thanks twice!
[G4 General] EA801:
Alright, I'm gonna try going back to MM.

I'm assuming we should also exclude the bak partitions - abootbak and raw_resourcesbak

Edit: Do I really need all 46 of these?

fastboot flash apdp apdp.image
fastboot flash boot boot.image
fastboot flash cache cache.image
fastboot flash carrier carrier.image
fastboot flash DDR DDR.image
fastboot flash devinfo devinfo.image
fastboot flash dpo dpo.image
fastboot flash drm drm.image
fastboot flash eksst eksst.image
fastboot flash encrypt encrypt.image
fastboot flash eri eri.image
fastboot flash factory factory.image
fastboot flash felica felica.image
fastboot flash fota fota.image
fastboot flash fsc fsc.image
fastboot flash fsg fsg.image
fastboot flash grow grow.image
fastboot flash hyp hyp.image
fastboot flash hypbak hypbak.image
fastboot flash keystore keystore.image
fastboot flash limits limits.image
fastboot flash modem modem.image
fastboot flash msadp msadp.image
fastboot flash operatorlogging operatorlogging.image
fastboot flash persist persist.image
fastboot flash persistent persistent.image
fastboot flash pmic pmic.image
fastboot flash pmicbak pmicbak.image
fastboot flash rct rct.image
fastboot flash rpm rpm.image
fastboot flash rpmbak rpmbak.image
fastboot flash sbl1 sbl1.image
fastboot flash sbl1bak sbl1bak.image
fastboot flash sdi sdi.image
fastboot flash sdibak sdibak.image
fastboot flash sec sec.image
fastboot flash sns sns.image
fastboot flash spare1 spare1.image
fastboot flash spare2 spare2.image
fastboot flash spare3 spare3.image
fastboot flash spare4 spare4.image
fastboot flash ssd ssd.image
fastboot flash system system.image
fastboot flash tz tz.image
fastboot flash tzbak tzbak.image
fastboot flash userdata userdata.image
[G4 General] steadfasterX:
Read the OP. Nougat is not supported. The hack I use to write stuff in download mode does not work on nougat (yet). If you haven't read that you maybe go through the whole OP again until you understand everything and made all precautions.

Also going through the FAQ is a good idea to get a good understanding of all UsU parts, goods and bads.

Backup with SALT before doing anything else is the most important one but there are others ofc.

I see no reason why you wanna do this. It's fully enough to restore the bootloader stack usually.. But yes all these 46 partitions (well actually you can leave out all Bak partitions as well) BUT :

BEWARE OF THE ARB (THE FILES YOU FLASH SHOULD NOT BE LOWER THEN YOUR CURRENT ARB AND NEVER HIGHER THEN 2)

DO A SALT BACKUP BEFORE!!!!
[G4 General] EA801:
I've only used exactly ARB2 KDZs.

Anyway, I did all that and when I got to the systemimg (from 28A), it would just get stuck on one of the first sections.

sending sparse 'system' 1/8

for about 20 minutes, then

sending sparse 'system' 2/8...

Full-wipe & restore went smoothly, though.
[G4 General] berkantkz:
Okay, I see. Thanks for noticing. I've downgraded to MM and will unlock with UsU soon. I've some more questions as well.

The first one is that I backed-up (full backup) my device while I was on Nougat, right before attempting to unlock it. Would this backup help me in case something happens wrong or should I backup again on Marshmallow?

The second one is that if I want to go back to stock Marshmallow after UsU'ing my device, how can I flash stock Marshmallow? I searched but couldn't find a zip like Nougat V29a.

Thanks again and I wish you good luck.
[G4 General] fil3s:
I just wanna make a public apology to member [MENTION=6302635]sdembiske[/MENTION] .

I finally re read the op and flashed h815 mm modem and no issues to report.

Thx

Update : still experiencing issues. But its no fault of the op ;) same thing on every rom I've tried with usu . but as the op stated, this does not concern usu.. Wonder if the official h815 unlocked variants are having massive headaches with every rom they flash.. Hmm. Interesting ;);)
[G4 General] sdembiske:
The MM SALT backup should be done as well. You never know when it will come in handy but also keep your N backup.

You can get back to MM, currently, by doing a TWRP backup once you've unlocked the stock MM and followed the OP exactly, installing TWRP etc. - it is stated in the OP - before flashing a custom rom.
[G4 General] fil3s:
that's the lamest copout I've ever heard!

This has turned me off this website in general. A special member here would not accept several attempts to accept an apology but instead starts a flamewar until I reacted. I was willing to let it go but not now ;)
[G4 General] fil3s:
Back to RR again. After on aoscp loosing audio followed by a bootloop because some dipper tells me to flash a random file not mentioned in the op, loss of twrp too.

I am growing very dubious about usu in all honesty, or could be its just becoming boring :P

My sister is selling me her S6 in couple months hopefully its a legit unlock process.
[G4 General] spartan268:
I thought I was the only one who uses the word Dipper LOL.
[G4 General] fil3s:
Sorry

Let me try to explain without telling my life story.

About just over three months ago i changed a major antipsychotic to a bad one that i had to take every three months. Long story short im registered back to the original medication that is given to me by injection from a nurse. I'm due for it Monday. I have major drug induced psychosis spawned from 25+ years of narcotic abuse.

[MENTION=5545101]steadfasterX[/MENTION] i really do respect you as a developer even if I've posted inexcusable and inappropriate posts in your threads. I'm relatively new to XDA although I've been labeled a 'senior member'. For the first few years of signing up i never partipated in any threads

Anyway. Thanks again.
[G4 General] EA801:
Well, I'm sad to say this, but I can't have my G4 as a daily driver anymore, without any calls or text.

Just got a P2XL, so I'm back to locked stock for a while, until an unlock comes out for that phone.
[G4 General] glenrocks:
Hi [MENTION=5545101]steadfasterX[/MENTION] ,

Can you suggest what to do with unlocked H812 to be run on ATT-US? UsU or wait to resolve current issues first??

In short- Currently, device is all messed up due to multiple flashing of kdz (my adventures) with "no sound+no camera+no call function+no external-SD card mount". But somehow device connects to ATT carrier with bars +(data works+SMS can be sent/received) .
[G4 General] floast:
hi ı unlocked my h815 with usu then flash twrp and baseband and try lots of roms and modems and have done steps at FAQ #20b. but my device only boot into twrp lg up seen my rom h815 v20d but salt says h815 at v20l tot can anybody help me
[G4 General] steadfasterX:
Well. member sdembiske has done a great job in writing a guide for the h812 but its up to you. Here some thoughts though:

I'm the only one who build ROMs for UsU devices and I guess that will never change. I have still hope but well...

ROMs would be the way to solve issues in its best way.

I cant do that though.

I cant support 8 models in terms of unlocking, building kernels, building ROMs, plus SALT, plus FWUL and other stuff.

When you followed 20b you should now have MM bootloader is that correct?

If so:

flash the N modem

do not flash the baseband package

flash the h815 UsU AOSCP NOUGAT (4.x)
[G4 General] king200:
H110

ARB=3

Software version H1022f

I can find a rooted System image H1010e

Is it safe do the H1010e image without brick? Is a H1022f rooted system image available? I just learned that I have to be on the same version of firmware as the rooted, system image. Project will be to make a rooted system image!

I apologize for asking here. I searched elsewhere and could not find information. I just bought the phone and I've never kept an phone without root.:(
[G4 General] floast:
flashed G4_29a_N_modem_UsU and then aoscp_h815_usu-4.1.2-20180316-unofficial but again booted into twrp :((( ı am going crazy for 2 days ...
[G4 General] steadfasterX:
share the recovery log once it rebooted into TWRP

-
[G4 General] floast:
here sir

here
[G4 General] sdembiske:
The H812 guide steadfasterX is referring to is post # 361 with respect to installing ASOCP Nougat.

Before you do anything, see if you can get your phone carrier/sim unlocked. As of Dec 1, 2017, Canadian carriers are not allowed by law to charge for this service. It should be done as a matter of course, IMO, when installing any custom roms.

There is no excuse for not doing it

... then, proceed to unlock your H812 bootloader and follow my guide.
[G4 General] seanwarez:
After UsUed my VS986, both AOSCP and 29a_any UsU roms make VS986 camera video stop working. So I ended up not using either one, but flash magisk root to stock MM rom in TWRP and it is working great.
[G4 General] floast:
Thanks for helping

here you are sir
[G4 General] steadfasterX:
first thing you should do is upgrade TWRP to the

N

one.

Then try again

If the error persists:

let it bootloop once again and when we have luck that command should work:

adb shell "ls -la /sys/fs/pstore/"

adb pull /sys/fs/pstore/console-ramoops-0 dmesg.txt

share that dmesg.txt which you hopefully were able to pull

if this dont lead to success and as you have the h815 (if not dont proceed) you can flash the full v29 STOCK rom:

https://xdaforums.com/showpost.php?p=75829995&postcount=98 --> H815-ONLY_ARB-0_v29a_FULL-STOCK-ROM_UsU.zip

It includes the N bootloader as well so if you missed a step this should cover it.

If that worked you can flash aoscp or whatever you like again

.
[G4 General] floast:
Thanks for helping

adb commands gave me error- closed and not found ....:(( will try flash rom like you said and report back ...
[G4 General] steadfasterX:
do you have upgraded TWRP?
[G4 General] floast:
Thanks for helping

yes upgraded to this twrp-3.2.1-PREVIEW-109_g4_N

---------- Post added at 11:12 PM ---------- Previous post was at 10:26 PM ----------

flashed H815-ONLY_ARB-0_v29a_FULL-STOCK-ROM_UsU bootloop into twrp again :(((
[G4 General] mtamtas:
Great Work !!!

I unlock my h815 Optus/Australian without any problem. FWUL is very useful.
[G4 General] floast:
Thanks for helping

maybe ıts about the kernel ?
[G4 General] steadfasterX:
Read FAQ #4

hm interesting and odd ofc..

no it isnt the kernel. When you flashed the full stock ROM above it must work..

so you can boot into download mode? If so do it and grab the log in the advanced menu (upload button, share the link)

also consider to come to IRC .
[G4 General] floast:
Thanks for helping

yes ı can boot ınto dowload mode ...

sir ı flashed the stock recovery and device now blue light blinking with lg logo ı think starting to normal boot ıs ıt ok?
[G4 General] amahmoudeg:
Any News for H818p unlocking

Smart work wish you luck

I'm dying to root my H818p.

Any News for H818p unlocking?

do you find why the touch not working?
[G4 General] steadfasterX:
ah sure yes that should do it. give it 10-15 minutes though.

nope. i have no time for this atm and maybe never as said multiple times (use the search)
[G4 General] floast:
THanks for helping

I flashed H-ROM g4 and UsU modem and then fastboot flashed stock 29a recovery.......

At last my device opened :)) everything working perfect and smoothly Thank for everybody and especially [MENTION=5545101]steadfasterX[/MENTION]
[G4 General] mwahahaa:
Hi steadfaster, below is the SALT output from lusb. You will recall that my H812 hardbricked after flashing the MM files in entirety.

[android@fwul ~]$ lsusb

Bus 004 Device 004: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick

Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 005: ID 05ca:18c4 Ricoh Co., Ltd

Bus 001 Device 006: ID 0489:e036 Foxconn / Hon Hai

Bus 001 Device 003: ID 04f3:002d Elan Microelectronics Corp.

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[android@fwul ~]$

Is my device truly dead? I plan to send back to LG if it so.
[G4 General] steadfasterX:
is your FWUL running in a VM? If so: do you have ensured that any possible USB device is attached to the VM?

If FWUL is running from USB stick: ensure you plug the cable directly and not on an USB hub

Its nothing related there.. which means either a defective USB port (phone or - very unlikely - PC) or cable. I bet the USB port of the phone then.

-
[G4 General] xdauser9675:
[MENTION=5545101]steadfasterX[/MENTION] I wish to try on H818n can you guide me what to do? If I can get back to stock using LGUP then I am ready to try.

I may help you build by giving back logs maybe?
[G4 General] mwahahaa:
That is quite a coincidence that the port would have died the moment I flashed those files. The phone went dead upon reboot after flashing all the MM files, with no usb issues at all before that.
[G4 General] steadfasterX:
i see no reason why not. You have used the port and it died (if that IS the case). If the USB port died (which is also a known issue for the G4) it would just happen without a warning ;)

I will not say that there are no other possibilities but i have no idea what else could cause that.

Using UsU on a H818 means:

- no touch anymore - seriously TOUCH WILL STOP WORKING!

- no way back

- no help from me (I'm out of free time)

if you are fine with that lemme know. I have no time to debug that though.

What you CAN do seriously is to provide a dmesg output

directly

after a fresh boot:

adb shell dmesg

and copy the WHOLE output (which is a lot) to bpaste.net -> select "never" in the drop down box and share the resulting link

this way I can compare yours with others and maybe identify things better. but again - dont expect anything in the next months - or maybe ever.

.
[G4 General] mwahahaa:
Even if the port died, why would the phone go dead if it had a near-full battery?

So, even if it is not a dead usb port, it seems there is no hope for resuscitation. Let my case serve as a warning to tread carefully when trying UsU.
[G4 General] steadfasterX:
sorry but I really believe that this is not UsU related. hardware defects are well known for that device.
[G4 General] xdauser9675:
Sorry to ask once more but I cannot go back to any stock rom right?
[G4 General] steadfasterX:
correct you will be stuck there
[G4 General] glenrocks:
Make LG G4 H812 work on US ATT

I believe you have done more than anyone expected.. I have jumped on the bandwagon on UsU... was able to unlock G4 after backup of G4 using SALT.

First step-confirmed with SALT that UsU found with Carrier/Country/firmware(laf) all marked UsU. :good: flashed TWRP latest release and recovery runs using fastboot recovery option within FWUL.

Second Step: Upgrade to Nougat:

Based on the steps laid out, in Recovery mode, I have TWRP 3.2.1.PREVIEW-109.g4_N.

I wiped /format data -> then install in this sequence from adb push(ed) files to /data/media/0/

G4_29a_N_modem_UsU.zip

H812_UsU_baseband_flash-in-twrp.zip

aoscp_h812_usu-4.2-20180421-unofficial.zip

open_gapps-arm64-7.1-mini-20180423.zip

SuperSU-v2.82-201705271822.zip

Go to Fastboot mode and using Simple-ADB interface within FWUL, flash boot h812_aoscp_boot_build-50-nougat.img

Result:

-Android boot animation shows- > Google Go screen showed up-> then booms into Blue screen-> Subsystem Crash!: modem (subsys-restart:Resetting the Soc)

-Second boot is hangs on <android> boot animation

Not sure how to get dump files.. I do see a command somewhere for dmesg log

It seems that I have missed something in between or its not a clean nougat install... yours and S help is always appreciated... hopefully I can get this resolved with help from both of you.

I believe that I am free to install any H811 compatible rom since I dont care about Canadian carrier and only want it to work on US ATT first. So please help guide.

THANKS AGAIN FOR ALL THE INCREDIBLE UNSELFISH HELP you and S have provided. Cheers!!

---------- Post added at 06:52 PM ---------- Previous post was at 06:44 PM ----------

Thanks.. I did jump in.. so lets see if I can make it work on US ATT.. and I liked your answer to Dumbbag..:D

Let see if I can resolve this modem crash and also get it to work. THANKS AGAIN for always being HELPFUL
[G4 General] sdembiske:
Refer to steadfasterX's post: [ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [H812]

Refer to the 1st line under Installation:

1. If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:

- TWRP flashable MM modems (N will not work)
[G4 General] glenrocks:
I am confused there - I checked Wipe section and saw no Modem folder- so which one to use (ie flash) for US-ATT - I assume that G4_29a_N_Modem_UsU.zip or stick with h812_20z_modem.zip will ??

So the sequence is (based on my understanding):

Format Data

Install below in order

G4_29a_N_modem_UsU.zip

h812_20z_modem.zip

H812_UsU_baseband_flash-in-twrp.zip

aoscp_h812_usu-4.2-20180421-unofficial.zip

open_gapps-arm64-7.1-mini-20180423.zip

SuperSU-v2.82-201705271822.zip

Go to Fastboot mode and using Simple-ADB interface within FWUL, flash boot h812_aoscp_boot_build-50-nougat.img

Excuse me for grazing through the OP and missing that.
[G4 General] glenrocks:
1-Update for 20z modem: >>> Shows Google then >>> Subsection Crash: Modem with 20z modem too

2-Update for modem.bin: tried simple <fastboot flash modem modem.bin> from SALT backup >>>> hangs on boot animation!
[G4 General] bdasmith:
Usu is a software based process....please stop blaming it for hardware related issues. It successfully works for the majority of those who have used it.
[G4 General] mwahahaa:
Don't stick your nose where it doesn't belong. I didn't directly blame UsU. I unlocked with UsU and it buggered up my device because of my particular variant and software version. I then had to go through many attempts to try and get it working right again. The last suggestion led to my phone bricking. (no way it is a hardward failure). I don't blame steadfaster or UsU for that. The work he has done on this is incredible.That said, UsU is basically in alpha phase. It is my responsibility in full to take the risk. That said, there are risks out there for some, and that should be known.
[G4 General] sdembiske:
Sequence: No more, no less - do it exactly as listed here.

-

do a clean flash

in TWRP, i.e., wipe Data, Cache and Dalvik,

followed by

Format Data >

- flash the rom >

- flash Gapps >

- flash SuperSU >

- re-flash the Marshmallow (MM) modem.bin file from your Salt backup or the modem image file extracted from the appropriate MM kdz >

- reboot

If issues still persist after trying that: refer to FAQ 20b) in the OP in the [UNLOCK][UNOFFICIAL][G4] Unlock **ANY** LG G4 device with UsU thread - check with steadfasterX first to see if he concurs.
[G4 General] Cisuwek:
I have unlocked but when booting in top left corner have some message: secure boot error. Any way to remove it?
[G4 General] steadfasterX:
one question: what was your firmware version before unlocking with UsU?

Really? Consider to read the FAQ #19 (or even the OP - Changes in behavior) before asking. Thanks.
[G4 General] Cisuwek:
steadfasterX, I see now, long to read, only necessary things, thanks
[G4 General] steadfasterX:
the problem with UsU is: EVERYTHING is important to read.. ;) - especially before asking questions which may have been already answered.
[G4 General] Cisuwek:
Works fine, next time will read EVERYTHING. Thanks, great job
[G4 General] AdventL:
Hi guys

I'm kinda stuck and I'm not sure what's up

I've used salt to Unlock my phone, when i launch SALT, it says UsU under Firmware, Carrier, and Country.

From following the instructions, I understand that I have to next boot into fastboot (I used adb reboot fastboot as my down button is broken)

I downloaded TWRP from the provided link, used "fastboot flash recovery <filename.img>", reboot into recovery but it is still the default recovery and not TWRP.

I've tried flashing

TWRP 3.2.1 109,108,107,106 and variables from marshmellow to nougat (my current rom is the original lg MM rom), but no matter which I flash, I still boot into the original recovery.

Any help would be greatly appreciated!

Thanks!
[G4 General] steadfasterX:
its not an issue with TWRP so just use the latest one.

If your volume button is broken: HOW do you try to boot to recovery then?

-
[G4 General] AdventL:
Do I just use the nougat TWRP although my current rom is on MM?

I boot my phone normally and use adb reboot recovery /:
[G4 General] steadfasterX:
read this regarding the TWRP flavors (also mentioned in the OP there):

https://xdaforums.com/g4/developmen...h-recovery-t3442424/post76048006#post76048006

when you boot your phone after flashing TWRP it gets overwritten by android on next boot. TWRP must load once and directly flashing.

so in your special situation do this instead:

Ensure you have a SALT backup (basic is enough) before proceeding!!

fastboot flash recovery twrpfilename
fastboot flash boot twrpfilename

(yes to BOOT too!)

then just turn on the phone and it starts to TWRP.

Now in TWRP choose: reboot -> recovery

TWRP will popup again but this time from the recovery partition.

As you now have overwritten the boot partition you need to flash the boot image of your SALT backup again in fastboot:

fastboot flash boot boot.image

Now just boot and try again to go to TWRP from within Android. It should work now. The above is just needed once so TWRP is now sitting fix there until you decide to flash other STOCK roms (maybe).

.
[G4 General] glenrocks:
firmware (system) LGH812AT-00-V20j-302-500-AUG-22-2016-0

---------- Post added at 05:05 AM ---------- Previous post was at 05:04 AM ----------

Moves past Boot Animation to Blank Blue Screen with no error msg
[G4 General] AdventL:
Oh man I got too excited and flashed twrp as boot without backing up :rolleyes:

I've tried using LG UP to reflash my old lg MM rom back but it doesn't seem to work, any ideas?