yashsingh1/xdaforums huggingface dataset:
[G4 General] steadfasterX:
ok one thing: really 0 support if you do not read at least the OP. (just another hint: read the LIMITATIONS / KNOWN ISSUES) You really wanted to use LGUP? yea? read.

regarding the other stuff: extract the MM boot image of the ROM you have installed with SALT and flash that.

.
[G4 General] sdembiske:
As far as I know there is no carrier provided H812 with firmware version AT-00-V20j-302-500-AUG-22-2016-0.

AT&T uses the H810 model, so the firmware version you indicate you were on is reflecting I believe, in part at least, what you did by following the thread you indicated to me originally in this post: https://xdaforums.com/showpost.php?p=76194688&postcount=12

What firmware was your phone originally on before doing the above? You indicated you flashed the H812 Lollipop and Marshmallow KDZ's in LGUP-NEW before you unlocked your bootloader ... so how are you showing

LGH812AT-00-V20j-302-500-AUG-22-2016-0 ?

The blue screen on boot may be able to be overcome by following the suggestions in FAQ 20b) but given the frankenstein device you essentially created, I will defer to steadfasterX whether that should be your course of action now.
[G4 General] sushant_:
Who is the F500 user who unlocked his phone using Usu???
[G4 General] steadfasterX:
Well we need a valid starting point. So FAQ #20b) is perfect to create one.

He should ensure he uses proper MM firmware files (according to his model and carrier) reflecting the current ARB and not higher then ARB 2 ofc.

https://xdaforums.com/poll.php?do=showresults&pollid=26680
[G4 General] sushant_:
Hmm, Actually I was ready to test my F500L for Usu.

But then I came to know that its not compatible with Nougat.

I already have the official nougat, so I tried to downgrade to MM or LP.

But all of the method failed and I was stuck with my unrooted LG G4.

After that I got into rom development and since then my LG G4 is my primary device for making roms for moto E.

I check almost everyday this thread so that I can find any f500L user who was on nougat and successfully unlocked his phone using UsU.

Today I saw that one guys has done it.

So I just wanna know did he do it from Nougat and is he facing any issues?

Thanks :)
[G4 General] steadfasterX:
flashing UsU on Nougat firmware is (still) not supported.
[G4 General] sdembiske:
glenrocks: In that case, I recommend you download the H812 Marshmallow kdz for your original Canadian carrier and extract it in SALT to get clean copies of the required files - the backup I presume you did in SALT of the MM kdz you flashed may be corrupted by the AT&T files you installed before.
[G4 General] glenrocks:
This device has call drop issues ever since I got it online.... it came with MM (dont remember which carrier version).. so ever since, its been out of control cuz of locked bootloader. Before jumping on UsU and fully aware of risks and good possibilities of resolving it with unlocked bootloader and subsequent perils --- I tried all 3 LP flavors - all canadian carrier- Rogers, Telus and Videotron and repeated the process of <start with LP-version and upgrade to MM> using your suggestion..this version of upgrade seems to be VTR, which was smoothest and was not hanging when I jumped in UsU route.

I did try this sequence using SALT backup as indicated in 20a/b, fastboot flash factory factory.bin -> hyp hyp.bin -> modem modem.bin -> pmic pmic.bin -> rpm rpm.bin -> sbl1 sbl1.bin -> sdi sdi.bin -> sec sec.bin -> tz tz.bin; yes bluescreen gone and it now hangs on boot animation

Let me try MM KDZ I have for Rogers/Others and extract <factory, hyp, modem, pmic, rpm, sbl1, sdi, sec, tz>.... I assume once I flash that, current firmware system version will change in SALT, right?

---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------

I did suspect corruption as it created other problems due to multiple flashing of kdz over the time - first external-SD card stopped, then Sound due to ATT files, then camera.... due to all my adventures and persistence in resolving this donk G4 H812 work on US-ATT.

OKIE DOKIE.. Will try that.. at least now we are in control of bootloader.....THANKS :good: Cheers to both of you!!
[G4 General] sdembiske:
Where exactly did you download the VTR version? - post the site and link.

The good news, You're not hard-bricked and seem to be on the right track if you're just bootlooping on the boot animation screen ... it may not be necessary to re-do the sequence. Do you know the arb version of the VTR version (available in SALT) and what your GPT compatability showed in SALT?
[G4 General] glenrocks:
I have so many LP/MM KDZ in my folder; even I get confused..lol.. I believe it was on H812 Main Canadian post with stash of ROMs- the site which limits 2 downloads a day.. I remember that..lol.

Yes, I never flashed KDZ other than H812 flavors- hence no brick.

ARB was 0; GPT is/was H811

---------- Post added at 12:40 PM ---------- Previous post was at 12:28 PM ----------

Quick Qs-

When I extract KDZ, it gives me factory.image... so flash command remains the same as .bin files??

Since GPT is H811, and I do not care about H812 carriers, is it possible to use H811 MM/N stack+N ROM? I understand currently there was no need for UsU-compatible-H811-Nougat-Rom-Build... steadfasterX, can you suggest one already out there which is H811 build ready to use on UsU?
[G4 General] sdembiske:
I have been unable to find that specific firmware version for the H812 so I am concerned as to what you actually flashed ... it doesn't mean that it doesn't exist, just that I cannot locate it exactly. Closest I have found is: H81220v_00_0621.kdz or H81220j_00_0822.kdz.

If, steadfasterX thinks you should proceed, the commands would be as follows:

fastboot flash factory factory.image

fastboot flash hyp hyp.image

fastboot flash modem modem.image

fastboot flash pmic pmic.image

fastboot flash rpm rpm.image

fastboot flash sbl1 sbl1.image

fastboot flash sdi sdi.image

fastboot flash sec sec.image

fastboot flash tz tz.image

However, I would prefer if you let steadfasterX suggest your next steps before proceeding with flashing the files listed above from the clean extract.

I went to extract the H81120X stock rom and discovered it was arb version = 3. For any recent (addendum: stock) H811 MM version, the arb version could create BIG problems ... Be wary, wary careful ...
[G4 General] glenrocks:
I will look up and share the link so that for future, users can be warned. - ok I believe this was the source - [Updating Link] https://lg-firmwares.com/lg-h812-firmwares/#firmwaresList

Can you please share link of latest H81220v or latest with ARB 0?

Thanks... I can wait too... it seems that SALT does warn if ARB is not read correctly from KDZ.. I need to clean all kdz from my local disk.

I believe I bravely tried flashing H811 - aoscp_h811-4.2-20180425-unofficial.zip (non-UsU) and it gave me some compatible problem msg.. never thought of arb issue with them... glad you warned.
[G4 General] sdembiske:
Sharing the link would be great but the link you mention I did check first. Perhaps it is the 'v' version I noted and shows your detail when it is installed . One exact version I found was for an H815, so you can understand my concern ...

The AOSCP UsU H811 version posted by steadfasterX in the Downloads in the OP in this thread is fine - I installed an earlier version of it but I removed the 1st Assert line in the Rom before I flashed it, something you should have done. I was referring to stock H811 roms or versions thereof that are not built with UsU devices in mind ... Don't stray from his versions ... to be on the safe side.

The H812 UsU version is made for the H812 with H811 GPT compatability.
[G4 General] glenrocks:
Quest to make H812 work on US-ATT using UsU

- I got lucky with no brick..:angel:

- I did see that mentioned as I was grazin thru but didnt read more on How and where Assert was/is in zip file- aoscp_h811-4.2-20180425-unofficial.zip
[G4 General] sdembiske:
How to remove the Assert line

:

- Double click on the zipped folder of the rom to open it

- then, open the following sub-folders sequentially >

- META INF folder >

- COM folder >

- Google folder >

- Android folder >

- copy the Updater Script file to your desktop or another location > open with Notepad++ (free download) > remove the top (1st) Assert line >

save

& close Notepad ++ - then, right click on the file, copy it and paste it back in the same place in the zipped rom sub-folder (may take a little time when you indicate to replace the file and it may appear to be not working, but eventually it will copy it over). Open the updater script file again when it's completed with Notepad ++ and confirm the top Asset line is removed. When confirmed, exit all the sub-folders to the zipped folder.

- Copy over the zipped rom folder to your SD card and proceed when ready to install it.

Alternate method

(if first doesn't work):

- Extract the zipped Rom folder & in the unzipped folder open the following sub-folders sequentially >

- META INF folder >

- COM folder >

- Google folder >

- Android folder >

- Updater Script > open with Notepad++ (free download) > remove the top Assert line >

save

& close > exit all the sub-folders and when back to the main extracted folder right click on it > Send to > Compressed (zipped) folder >

- copy to your SD card and Install the Rom in TWRP etc.
[G4 General] AdventL:
I've tried backing up using the backup button in salt which gave me alot of bin files including one called boot.bin, aboot.bin and abootbak.bin, as well as extracting the original kdz which gave me a .dz file but I can't seem to find a boot.img

Am i doing something wrong?
[G4 General] steadfasterX:
Your question is about SALT so I answered you in the proper thread here:

https://xdaforums.com/g4/general/tool-salt-lg-revolution-t3717864/post76408014
[G4 General] :
Post removed by request of the thread's OP.
[G4 General] glenrocks:
Make LG G4 H812 work on US-ATT.. Quest continues

I did that but somehow it gave me error.. maybe repackaging zip or original zip of H811 was corrupt.. Will try this process with Oreo package of H811

Update on device:

I remembered reading H812 in one of hyperlinks, so tried G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip and strangely worked... ( I did have to download GAPPs 7.0 version) bringing device to life.

Now the ISSUES:

- STRANGELY, Flashing this rom brought back old memories of core problems I had before UsU...:eek:

Cons: No Sound+No Calls+No Camera+No External SD Pros: Boots/Wifi/SMS/Data/Google Account works

I will wait before I tear apart Oreo H811 to see if core H811 flash do the trick of rectifyin.
[G4 General] sdembiske:
Try the ASOCP N rom for H812 and remember to to do a clean flash following the steps I laid out in post # 921 and in particular, re-flashing the Marshmallow (MM) the modem image file extracted from the appropriate MM kdz. The other thing is, with respect to the G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip: did you re-flash the complete bootloader stack from your extracted stock Marshmallow kdz as per FAQ 20b) and the commands I showed in post # 943 ? If not, maybe give that a try followed by the clean flash steps but with the N modem.

The Oreo is not ready for use as a Daily driver yet - you will have even more problems in addition to what you have now ... steadfasterX doesn't suggest using it as such.
[G4 General] glenrocks:
Yes I did - Only struggle is I have to connect to FWUL to push zip files back since external-SD is not working- such a pain if one does it multiple times- I also found using alternate TWRP command useful (in place of putting a device in fastboot mode).. but still a pain to go through for all combinations of ROM+Modem

Yes I did that.. even using extracted Rogers MM 20e version, salt-backup-VTR-version, 20z_modem.zip. Device just sat on boot animations' fat bottoms :laugh: somehow

OK thanks.. that means, steadfasterX will have to guide me how to overwrite these sound/mount/camera drivers- looks like UsU process tries to avoid touching them for good reason- dont break it if its not. But my case is unique-with my adventures contributing a lot too...:crying:

Out of context, does UsU work on G3 Tmo locked devices too...and also G4 H810 which is locked to ATT with ARB > 2 ?? Just thinking ahead as I have those 2 devices too.
[G4 General] sdembiske:
Note: I did do some corrections to my post after you perhaps read it the first time ... just in case.

Simple answers: G3 and G4 H810 with arb

greater than

2 = No x 2.

I sincerely hope you can get the issues resolved ... steadfasterX is your go-to now. Best of luck.
[G4 General] glenrocks:
Okay-- I think its mentioned so many times on the forum but its tempting to ask again.. I will have to connect those devices to FWUL to confirm ARB of G3 (dont think I ever got there

I really do appreciate your help and guidance ... THANKS.

I will definitely re-read for sure and try the process again to make sure.... right now, device is alive--I did LG restore and worked...after doing LG Backup to Cloud drive on this stock 7.0 ROM., I will do AOSCP test cycles again.

Now I understand what steadfasterX meant before I jumped on UsU, seems these sound,modem,camera functions are controllable thru kernal builds he has out there. Wonder the difference in modems of H81220e Rogers version, H81220 VTR version, H81220z.zip and H812-BaseBand-version??!!
[G4 General] steadfasterX:
TL;DR

when you use the STOCK N: use MM modem + TWRP baseband flashed

when you use AOSCP Nougat UsU: use (untouched) MM modem - so reflash if you previously flashed the TWRP baseband package

note: sound and camera issues are 100% related to the modem partition.

consider to use IRC (see OP).

-
[G4 General] AdventL:
Sorry I keep getting confused on what should belong in each thread.

What I did before getting the error was

1. Flash Nougat Modem from Here

2. Re-flash baseband package from Here

3. Remove Assert line (Line 1) from META-INF > com > google > android > updater-script

Rom was from Here > /lineage/nougat/h815/

4. Flash ROM using TWRP

but I still get Error 7 /:
[G4 General] glenrocks:
Thanks!!

-

Okay.. Great..Appreciate!!

UPDATE for steadfasterX: fastboot flash modem : Sound works, Camera Works, Video Does Not, Mobile Networks Lost connectivity, No External SD Card

THANKS
[G4 General] ReeS86:
You may want to check if your SD card is formatted as exFAT. A couple of us have found that if there is a mismatch with some boot vs system files that the exFAT modules will fail to load - this is on LP versions of Android but you can try a microSD card that is formatted FAT32 to see if it works in your current situation. The only downside is you can't store single files larger than ~4GB which is typically not a problem on a phone.
[G4 General] steadfasterX:
try to flash the TWRP baseband package now
[G4 General] glenrocks:
Update: I did and still no Mobile Data Connection
[G4 General] berkantkz:
Hi [MENTION=5545101]steadfasterX[/MENTION]

As you know, I've recently unlocked my device with UsU. And as I told before, I had taken my Nougat's backup using SALT. Today, I did following commands

fastboot erase boot
fastboot flash boot boot.bin
fastboot erase system
fastboot flash system system.bin
fastboot erase userdata
fastboot flash userdata userdata.bin

Everything was good. It booted as I expected though. On the lockscreen, when I entered my knock-code, it told me it was wrong as usual. Then I booted to TWRP and deleted the files those hold lockscreen pin code. When I booted again, I set my knock-code again but there were no option for Smart Unlock. It was missing on LOS 15.1 too.

Besides, before unlocking my device with my UsU, the carrier label was "Vodafone TR". But now w/ UsU, it shows "vodafone TR" (first letter is not capital). So, I think that carrier label and missing smart unlock is due to either modem or baseband. As far as I know, now I'm on Lollipop baseband.

Do you think that would these changes come back if I flash Nougat baseband?

Edit: Baseband version is shown as "uknown" under "software information"

Edit: Oh well, yesterday, I installed V30 port rom just to test and I was able to use smart unlock options. So the problem I wrote above is not related with baseband. At the first times of LOS 15.1, I was able to use it as well. Then on both stock nougat and LOS 15.1, I deleted that screen pin files. So I am not able to use smart unlock features anymore.

Edit2: I've found out a way to make it visible again. I'm not sure if this is a fix or a work around.

I've just navigated to /data/system/users/0/ and removed the files below:

settings_global.xml
settings_secure.xml
settings_system.xml

After booting to Android, I've seen that most of the settings were reset such as quick settings toggles, navigation bar layout, whether a function was on or off and much more. Almost all of the settings I had set in Settings were reset. Anyways, better than that, I didn't lose any data.

So, the only thing I have is unknown baseband version. Would flashing it from Nougat work?

One more edit too: VoLTE doesn't seem to be work.
[G4 General] steadfasterX:
Well for me most of the times "baseband unknown" is just a cosmetic thing (as long as u get cell service etc).

The usual fix for this is: backup modemst1 and modemst2 and misc partitions in SALT or make a TWRP backup and choose EFS.

Then you would erase these 2 partitions - BUT (for anyone thinking about this):

THIS WILL ERASE ANY NETWORK/CARRIER UNLOCK

AND CAN POTENTIALLY DELETE THE IMEI - if things go worse.

Loosing the imei is not that critical. Restore the backup and thats it. You could even just restore the IMEI manually without that backup (there's a guide here in the g4 forums) - but not the carrier / network unlock. So backup before doing anything!

fastboot erase modemst1
fastboot erase modemst2

EDIT

reg. VoLTE:

thats a setting which is deep in the system and I know it was and is an issue with several ROMs (UsU'd devices or not). I followed the tries of enabling VoLTE for a while and saw its a PITA.

does it work when flashing the UsU stock kernel and the untouched MM/N modem partition?

EDIT2: typo, hided the fastboot cmds to make sure ppl read (sigh)
[G4 General] berkantkz:
Well, okay. As soon as I get home, I will restore these both. I don't have any sim lock/unlock so it doesn't bother me.

And I guess that VoLTE related to baseband. Because before UsU'in my device, it used to work. As you know I only flashed laf, baseband and aboot. Could aboot affect the VoLTE?
[G4 General] steadfasterX:
double post - sometimes XDA hates me :p
[G4 General] berkantkz:
I will try these both as well.

By the way, I wonder what is the relationship with modemst* after UsU'ing? As far as I know it doesn't touch this partition
[G4 General] steadfasterX:
they are not UsU related. its just partitions containing modem stuff (dunno exactly what and how) but they can get sometimes corrupted or containing old/invalid data. thats why it CAN help to erase them
[G4 General] steadfasterX:
Statement / New findings / Revert UsU

yes it seems to be possible to completely

revert

UsU - but only for those having firmware files with an ARB of 2 (or higher).

its all about fuses..

the discovery to completely revert UsU is quite new and I can not test it personally (as I have no firmware files with an ARB 2 or higher) but at least member [MENTION=7161385]jacoblong09[/MENTION] was able to verify it.

Technical details:

Fact is: You can

not

boot an aboot of ARB

0

anymore after you flashed the aboot of UsU which is ARB

2

.

The ARB after you flashed UsU on an ARB 0 device will be:

aboot (UsU):

2

, sbl1:

0

, tz:

0

, rpm:

0

All that is expected and well known (to me) but..

I thought its a fuse which has been blown when booting with the UsU aboot once. .. well and thats true so far.

I own a h815 only - so I have no firmware files with a higher ARB then 0 so I can't test everything i wanted to.

My assumption was that blowing ARB fuses is just happening in general and that's it. .. and that the UsU fuse is a special fuse which gets blown.. but it turns out and thats the only logical explanation at all:

ARB fuses are blown for each of: aboot, sbl1, rpm, tz

SEPARATELY

! woot yea.. that makes totally sense. I still believe that the code which is blowing the fuses is not in aboot but in sbl1 but it may check each of these and then blows.. oh my yea thats how it works. Didn't realize that earlier but that makes sense..

TL;DR

fact is:

u can

not

revert an aboot with an ARB of lower then 2. Backup or not. fuses are fuses.

So if your model does

NOT

have firmware files available with an

ARB of 2 (or higher)

you can

NOT

revert

(Means these models: H812, H815, H818, H819, F500 will never be able to revert)

the new assumption is:

you can replace the aboot with another / pure stock one as long as it has an ARB of 2 (or higher but that will make it impossible to UsU again)

So if your model

HAS

firmware files available with an

ARB of 2 (or higher)

you

MAY BE

able to revert

(Means these models: LS991, H810, H811, US991, VS986 may be able to revert)

special thx to [MENTION=5809770]berkantkz[/MENTION] and [MENTION=5398780]glenrocks[/MENTION] btw.

These both made nothing special but the questions they had and things they shared made me think about all that again which then lead me to the above conclusions.

:)

-
[G4 General] jacoblong09:
Yes, if it were not for [MENTION=7473109]berkant[/MENTION]z and [MENTION=5398780]glenrocks[/MENTION], my guide would not exist :)
[G4 General] berkantkz:
Hahah ?

What I did was searching for LG G4 UsU on YouTube and contacting you.

If there weren't your videos, I wouldn't be able to be ?
[G4 General] berkantkz:
This will be doubled post but I need to inform you [MENTION=5545101]steadfasterX[/MENTION]

I haven't tried the suggestions you gave me above. And I have just realised that my phone always stuck on 4g. It doesn't switch to 4.5g. I was able to use 4.5g before UsU'ing. I hope that I will get VoLTE and LTE+ with your suggestions. Just wanted to inform you. UsU might lead to lack of VoLTE and LTE+.
[G4 General] mwahahaa:
Hey steadfaster, LG has repaired my device under warranty and it is on its way back home as we speak...

If I use UsU again to unlock with the intention ONLY of rooting on MM (without trying to update to Nougat from rooted LP as I did before) is there any risk of problems with calls/camera/video etc.?
[G4 General] steadfasterX:
I can't think of a reason for this tbh. Well the bootloader args change. So maybe just comparing and adjusting the kernel cmdline is enough to bring it back. That would be the easy fix.

If its not that ROM adjustments could bring it back too. The hardware is still the same even when UsU'd so there must be a way.. I can't help on that much though. I'm too busy with other stuff.. Feel free to ask things on IRC or here but I can't dig into code etc.

yes
[G4 General] berkantkz:
Well, how can I get that bootloader arguments? I'll try adding them to boot image.
[G4 General] steadfasterX:
you would first need a device which is not unlocked by UsU and where VoLTE is working :p

then on this device you would need to do:

adb shell cat /proc/cmdline

or

adb shell "dmesg |grep -i cmdline"

(must happen in Android directly after booting as the buffer gets overwritten after a while)

then we need to compare them with the one of an UsU'd device.

.