yashsingh1/xdaforums huggingface dataset:
[G4 General] Jorge Cervantes:
What is MM modem? Where can I download it?
[G4 General] martin234:
I have everything working to some extent except speaker audio in any of the roms I've tried(lineage, AOSCP mm, RR). Anyone have a fix for this?

H812
[G4 General] sdembiske:
You will have to download from somewhere a copy of the Marshmallow (MM) 6.0 rom for your specific model/carrier (Google it) and extract the rom using ONLY SALT. You will then have the appropriate MM modem image file in the files you extracted.

I suggest you start reading the OP's more carefully and making sure you understand everything before posting questions that can be answered by doing your homework first.

Note

: Learn to use the Thanks button (bottom right at the bottom of the post) when steadfasterX in particular and other members are trying to help you.

---------- Post added at 07:03 PM ---------- Previous post was at 06:58 PM ----------

Did you do a factory wipe

and

a Format Data when you flashed the rom? Did you flash your MM modem file after?

See post # 361 paying attention in particular to the paragraph starting with, "- IF, you've already installed the rom and are having problems ..."
[G4 General] Jorge Cervantes:
Oh, I understand, I must download MM ROM Stock and extract the ROM with FWUL / SALT to get the modem file. Is that correct? Do I download the ROM in KDZ format or in what format? Thanks in advance.
[G4 General] sdembiske:
Yes, that is correct. KDZ.
[G4 General] nilson1406:
Does any rom compatible with UsU have fm radio support?
[G4 General] nilson1406:
Is it safe to flash a rom H815-ONLY_ARB-0_29a_bootloader_UsU.zip?

Have fm radio?

**Sorry my english from google translate
[G4 General] fil3s:
Only if u have ARBv0
[G4 General] Jorge Cervantes:
Is the modem in zip format to flash with TWRP or how does it flash?
[G4 General] arana1:
h811 offical unlock BL?

I don't see h811 in the device supported list in LG Page,

The following devices will support unlocking the bootloader:

• LG V30: H930 and H930G for the European market

• LG G6: US997.USA for the U.S. open market

• LG G6: H870 for the European market

• LG V20: US996.USA for the U.S. open market

• LG V10: H960A for the European market and Android M (Except France)

• LG G5 SE: H840 for the European market

• LG G5: RS988.USA for the U.S. open market

• LG G5: H850 for the European market

• LG G4: H815 for the European market

Unlocking the Bootloader will only be supported on selected devices.​

Am i missing something? because I rather just use a fastboot command instead of the UsU unofficial method (I am a coward).
[G4 General] sdembiske:
If your device is not a frankenstein H811 but an official carrier supplied H811, you do not need to unofficially unlock your bootloader - you can do it, as you noted, with the fastboot command fastboot oem unlock.

---------- Post added at 11:33 PM ---------- Previous post was at 11:24 PM ----------

IF, you had actually extracted your relevant MM kdz by now, you would already know that the modem file is not in zip format. It will show as modem.image and can be flashed in fastboot mode with the command: fastboot flash modem modem.image.

You are still not reading through things thoroughly and/or searching in the relevant threads for answers. You must take some responsibility yourself in this undertaking.

No more soup for you !
[G4 General] grantdb:
Anyone have a factory (kind of) reset after phone shuts down because of low battery? Very strange.

Optimus? Have some logs from TWRP if wanted.
[G4 General] steadfasterX:
The corrupted system files and / or automatic factory reset is a very well-known issue for the G4. I have seen this very often in AOSCP Oreo thread

... And just to make it clear this is not an UsU issue ;)
[G4 General] grantdb:
Just randomly halfway resets? Lol wow LG
[G4 General] steadfasterX:
This can be either hardware-related like a faulty battery (occurs when you go under a specific battery level) or it is ROM issue I'm not sure cuz I never investigated this
[G4 General] steadfasterX:
1) this is totally OT pls open an own thread for questions not matching to an existing topic. Due to the following I answered here in the UsU thread instead.

2) i guess its the display then.. u may need to exchange the LCD too. its different on the h818

3) using QFIL is always a f*** bad idea (FAQ #23)

4) well.. if you dont mind loosing the mainboard completely (which you may already have as you are used QFIL - *SIGH* ) you could try UsU on that board with that panel.

The reason why UsU has not been released for the H818 is due to touch issues (while you always could see something on the screen). My guess is that your issue is about the panel too.

Well but when you have now a h811 panel and a h818 mainboard.. UsU may work without issues.. lol.. no idea if that would make things even more worse or not but if you have nothing to loose..

What happens when you turn on the phone and trying to boot into download mode and connecting with SALT? If its just the panel it should still load the dl mode (give it 2..3 minutes before starting SALT though).

Well not completely true as you have used QFIL ( *SIGH* -_- ) I have no idea how much you damaged your phone already. so even if the dl mode would have load first after using QFIL all can be different. Nevertheless give it a try to get into the dl mode

.
[G4 General] lonicron:
Hi [MENTION=5545101]steadfasterX[/MENTION] . First of all i want to thank you for all your efforts and make dreams come true and of course continuous support.

This was my first unlock/rom experience but learnt so much. However I did a crucial mistake i guess at the beginning; used forgetful FWUL with VMWare on my mac. Everything worked fine backup/unlock etc. Unfortunately after everything was done, got an error on VM and lost all my SALT backups from the beginning, taken before the unlock process.

Now everything seems fine on my phone. Tried several Roms so far.

Is there anything i can do for lost SALT backups? Will i need them or what can i do not to need them? I am a little scared about the unknown.

Model: H815TR

aoscp 7.1.2 USU

Flashed G4_29a_N_modem_UsU.zip
[G4 General] steadfasterX:
Yea the most important thing now is: do a SALT backup (basic is enough) NOW!

The backup before unlocking is just for the case something really bad happens. Doing it now will backup important partitions like imei etc. But it backups even more then a TWRP backup can do and a SALT backup is recommended in any case.

The bootloader can be recovered from a kdz so that's not an issue.

So do a backup now to have the other partitions just in case and copy them to a secure place. Then you're fine.

...and then just have fun ;)
[G4 General] grantdb:
I noticed that fsync is turned off by default in Titan kernel, maybe that along with the phone battery running out before the phone could shut down properly caused this to happen. I enabled fsync and don't notice any performance hit so I guess better safe than sorry.
[G4 General] fil3s:
Am I the only one that gets persistent fc's in various apps? I use substratum but so what I never had this problem with other devices with it. I uninstalled it and still Instagram, fb, fb messenger, and others keep going spastic on me. Very frustrating.
[G4 General] steadfasterX:
Nope that's not the reason. It wouldn't explain why system files get corrupt or factory reset happens. I strongly believe the reset happens as a result of no success to boot (oreo has implemented several tasks when a boot is not successful and one is an automatic reset).

Install the previous kernel and see if that makes a diff
[G4 General] fil3s:
Thx. The precise apps I'm having problems with: Instagram, Facebook ,messenger.

Its no big deal lol :D but i use fb to talk to my family etc.. Tried flashing a diff kernel same output. Reflashed usu build 50 nougat same output.. :eek:

No other issues.. :D
[G4 General] fil3s:
So after troubleshooting ,firstly format data, clean flash and reinstall from playstore N aoscp h815 usu & latest usu kernel, I was greeted with a 'randomly powering off device' upon opening messenger - twice :laugh:

After not getting any response here, or the UsU kernel thread I decided it actually was aoscp :)

I then flashed RR 5.8.5 and llama sweet kernel and, well, take a look at the screen, ;)

No problemo with messenger.. No problems at all, in fact. :)
[G4 General] sdembiske:
Any member seeing the above post: See my responses on the UsU lernel thread in posts # 75 and 77
[G4 General] fil3s:
Sorry.
[G4 General] fil3s:
Clean flash, format data install:

ROM (add more zips, latest twrp preview) latest nano openGapps - swipe to confirm

Boot - swipe to confirm, supersu 2.82

Reboot restore tibu backup, messenger shuts down the phone.
[G4 General] cablematicman:
Everything works perfectly except that every time i want to flash an h811 ROM to my h812 I have to manually edit the updater-script. Can I just flash a TWRP recovery for h811 instead?
[G4 General] Nitram126174:
hi, how install the rom aoscp for vs986 correctly, to avoid bugs
[G4 General] sdembiske:
Did you forget the MM modem file flash? Why re-install TWRP ... you installed an newer version? ... Restoring Apps + Data or just Data ... with Titanium Backup? Titanium restore can create problems sometimes and some Rom developers actually state not to restore with it ... but, more importantly, still not seeing other members here reporting the same issues ... so ... Hmm .../
[G4 General] fil3s:
:laugh: OK Bro calm down lol I meant i was using the latest twrp. Mm modem file?? But isn't the firmware I flashed appropriate for N.. Sorry don't wanna brick my device flashing mm modem file.

I'll wait for SFX see what he reckons, "Dear". Thx
[G4 General] steadfasterX:
nope. just ask the ROM maintainer to provide an UsU version of his ROM.

Well. You restored an app by titanium. This app has FCs. Its known that Titanium restores (especially between different ROMs or ROM versions) causes issues like that.

So its easy: Do NOT restore by titanium the app which has FCs. That's not an UsU issue anyways.
[G4 General] xdauser9675:
Hey,

Is there any work going on the h818 or is it closed?
[G4 General] steadfasterX:
nope.. nothing has been done. tbh if - I mean IF I will go on with that model I would need a test device located here in my hands.

I watch from time to time on ebay etc and if I ever see a very cheap one I may go on here.

.
[G4 General] Derpthunder:
Hello again, guys.

I wanted to ask what your experiences are with Quick Charge before/after unlocking and flashing the ROM of your choice.

I don't know much about the android h/w and s/w stack. Does any of the processes leading to flashing a new ROM (UsU>twrp flash>data wipe>ROM flash>baseband flash>gapps>supersu) affect the part of the phone which is responsible for handling the charging cycle?

Is that a part of the OS?

Or rather something in the baseband package?

Or does it reside on a separate chip, unreachable from our perspective?

The reason why I ask is that the stock L and then M mishandled a QC charger heavily - they did show "Fast charging" instead of regular "Charging" but they sort of faked the whole process - the battery reached 100% from 0% within around 30minutes but then it took about the same amount of time for it to discharge from 100% back to 0%.

Now, after going through the process described earlier, that same QC charger is no longer recognised as one - it just shows "Charging" but the charging/discharging looks the same.

The effect on my H815 is the same in AOSCP 5.3.1, Lineage OS 7.1 and when charging while only booted into TWRP.

The charger I use is Aukey PA-T9 - QC3.0. I also tested with Aukey PA-U28, which is basically older model of the same charger, only 2.0 compatible - the same results. Aukey seems to be a legit brand and both chargers were purchased from an official distribution channel so I wouldn't expect the problem to be on the charger's end.

I haven't tried with other QC chargers than these while the regular charger I compare the results with is the one that came with the phone.

Also, connecting regular charger sometimes doesn't start the charging process, only lights up the notification light as if it did but then the battery percentage doesn't progress and there's no notification that it's indeed charging. I then need to shut down the phone and connect the charger when it's off - then it boots into the system and starts charging normally.
[G4 General] EA801:
I'm on VS986 and I haven't been able to get any ROM up and running.

Am I not flashing in the right order? Here's what I've been doing:

Factory reset and format data

Flash the boot img

Flash the N modem zip, then the baseband zip

(Here's where I get confused) Flash the ROM, flash the baseband zip again, and just reboot?

I'm holding off on Magisk and gapps until I have a working ROM. I've The only sign of life I've gotten is from the stock N ROM, which will at least show me the "android is starting" message, but then it reboots and hangs on the shiny LG logo. I'd rather be on the latest AOSCP, though.
[G4 General] sdembiske:
Let's see: You post in the Resurrection Remix thread (post # 277), "I'm running aoscp N on my usu unlocked h815 and I just wanna be sure that I'm getting same info about updates. Dirty flash ROM and GApps (supersu ?) and that's it? Sorry if its already been answered (have only just subbed this thread"

So ... why you posted this on the RR thread in the first place is a mystery, frankly. So here's what I think: You may have

clean

flashed AOSCP in the first place followed by mini-Gapps etc., BUT when you upgraded you dirty flashed the AOSCP newer version and restored your apps with Titanium Backup ...

Flashing MM modem will not brick your phone on AOSCP N, contrary to your misguided statement - it has been suggested by steadfasterX and many of us actually read and followed his suggestions ...

If you think calling people "Dear" is a put down (something you seem to have a habit of doing in some of your more petulant posts ), frankly it sounds like you're flaming your rainbow colours ... ;)
[G4 General] steadfasterX:
Flash latest vs986 Modem (again)

No baseband zip

Flash aoscp nougat(!) vs986(!) version

Boot and test.

Start with aoscp UsU nougat first before going on as here I have UsU kernels included and so need of flashing a baseband zip is required.
[G4 General] Jorge Cervantes:
I want to thank steadfasterX and its collaborators for having developed this project, it served me. One question, are the AOSCP UsU updates that come out installed without having to delete anything?
[G4 General] aliarslan007:
Stuck with ARB v3 on H810

First of all, I simply love your work. You are a genius and I hope you get what you truly deserve according to your amazing potential.

I have a couple of questions: (I reached installing the SALT part of the tutorial but my ARB was 3)

1. I have been working with mobile firmwares for a while now. There is an option in SALT that I am tempted to use; wipe partitions. Now, like in MTK, can I wipe all my partitions and start flashing from scratch like aboot etc. Then TWRP, then usu ROM, then usu Baseband?

In short, would Wiping all partitions and then clicking Unlock in advanced settings of SALT revive the phone?

2. In SALT, it said the carrier of my G4 H810 is AT&T which is correct. But the GPT Compatibility was displaying H811. I am pretty sure mine is H810. Which one to trust?
[G4 General] steadfasterX:
You mean dirty flashing?

I do it always the same: full backup, flash dirty, test and if you have issues: do a clean flash instead

Reg 1)

Wiping will erase partitions. Don't do that unless you really know what you do and more important if you wanna flash you better wait for SALT v4 which will also allow flashing.

In short words the answer is no.

Besides that's better read more about ARB in https://bit.do/antirollg4

ARB can't be tricked. So never UsU for you.

Reg 2)

GPT compatibility is not about your model. GPT compatibility means your device GPT(!!!!) is compatible(!!!!!) with ...

this has nothing to do with your model! It's about your gpt only.
[G4 General] sdembiske:
Direct quote from the ASOCP OP thread: https://xdaforums.com/g4/development/g4-cypheros-t3680102

-- On dirty flash you need to also dirty flash gapps. The AOSCP survival script deletes them --

The line is immediately before the heading Screenshots ... in the OP. Not sure whether that still is the case, given steadfasterX's response above - worth confirming, anyway.

You will likely lose SuperSU as well, necessitating a re-flash of it.
[G4 General] aliarslan007:
Thank you for the quick reply. I have 2 more questions:

1. Would wiping all partitions erase the record of ARB? Does the ARB record sit in a specific partition, if so, which one?

2. For now, I will follow your advice and give up on UsU. But could you please at least help me with this annoying MM 21y update? The security settings don't work. Uninstalling an app restarts the phone.

P.S. this is official AT&T update! They should either hire developers from XDA or stop locking down the bootloaders.
[G4 General] steadfasterX:
Follow the link I gave you above it's all written down and explained in detail what ARB is and how it works. For the rest this is not a support thread for installing stock ROMs create your own but better use the search before
[G4 General] sarthak191:
Any news about H818N?
[G4 General] EA801:
OK, I tried that, and unfortunately it still doesn't work for me that way.

The only way I was able to make it boot was to follow all the commands in #759:

Honestly, I don't fully understand these partitions, so I can't tell which one actually allows the ROM to boot, but I've ruled out modem, because I tried flashing just that one, and it would still hang on boot.

This has worked twice for me. I did it the first time, and I had to do it again because my I somehow killed my ROM trying to get cell service working.
[G4 General] steadfasterX:
use the search (keyword h818 as it doesn't matters if you have a h818p,n,or whatever)

ofc you need to flash the MM bootloader stack (once!) but you now have that.

so you are trying aoscp Nougat - UsU vs986 version now?? Which exact version?

.
[G4 General] fates13:
AOSCP only works on VS986 on GSM carriers. CDMA carriers like Verizon pull the wrong APN.
[G4 General] steadfasterX:
His problem is that he cannot boot and not about mobile data connection
[G4 General] timn_13:
success!! now the april 21 2018 AOSCP UsU rom is flashed and working lovely on my steadfasterX *fixed* canadian h812! FWUL was an hour long usb write, but worth it as SALT did its magic and yoinked pristine files off my phone before defiling it right proper :D my carrier can kiss my tush, now, all hail UsU and the unlocked LG G4!!

as for the rom (i know this is the unlock thread, but i hope it's okay to mention) there's a little bit of lag on some inputs like the power button, regardless of what kernel aduitor settings i've used - but it's tolerable, especially considering that with root i'm able to run greenify and amplify (via xposed) and somehow still get 4+ hours SOT on my beat up oem battery (plus judicious use of manual screen brightness/no gps/most ambient sensor stuff off)! i've been looking at purchasing a powerbear battery replacement and keeping using this phone, now that it's not a ticking security expoloit timebomb (nary a single update ever came to my device since marshmallow dropped); but with the great tools now available thanks to the wonderful steadfasterX things aren't so dire!

huge thanks to everyone who contributed their time, devices, advice, feedback and community to this project - we are really lucky someone kicked LG's stupid bootloader lock to the kerb, that's for sure! now i don't have to upgrade my device itself just to be current/secure, what a concept!! cheers
[G4 General] EA801:
I'm on 4.2 20180421 (latest nougat).

The only thing not working for me right now is cell service, and I can't edit my APNs (The ril.sales_code=LOL and ro.csc.sales_code=LOL trick didn't fix it).

LTE data works fine but, no MMS or calls.
[G4 General] sdembiske:
I came across a couple of articles by one author which might provide some clues to resolve (it's the only one that seems to have taken a little more in-depth look at the issues you and other other members are confronting).

Carrier programming on CDMA Android phones - starting from Carrier configuration in the Android OS

Link: https://seasonofcode.com/posts/carrier-programming-on-cdma-android-phones.html

Flashing a Sprint Nexus S 4G to Verizon - starting from Step 5: Programming Android

Link: https://seasonofcode.com/posts/flashing-a-sprint-nexus-s-4g-to-verizon.html

With careful reading it seems to me they could provide some things to try with a good file manager with root ... keeping in mind both AOSCP and Lineage spawned from Cyanogen Mod.
[G4 General] steadfasterX:
1) Try latest 4.1 as well pls (format data as written the FAQ #zzz). Any difference?

2) Besides what sdembiske wrote you may have a Frankenstein device (see FAQ) which would explain the behavior as well.

3) As long as you have exactly (!) flashed the vs986 MM bootloader stack as written in the FAQ(!!!!) including the modem of the vs986 as written in the FAQ too it should just work. Following the FAQ to the latter is crucial important including how you extract the files .

4) if you don't wanna follow the FAQ of detecting a Frankenstein device and 1....3 doesn't work for you be flashing pure stock MM :

Format data in TWRP as written the FAQ #zzz

Flash the system and boot image of a vs986 MM based ROM

Flash the baseband TWRP zip

5) next try would be flashing pure stock LP :

Format data in TWRP as written the FAQ #zzz

Flash the system and boot image of a vs986 LP based ROM

Flash the LP modem

6) Last but not least I know there are others unlocked the vs986 before and its maybe an option to ask them what they made different
[G4 General] EA801:
1. I'll try that as a last resort, but currently I'm just dealing with not having cell service.

2. I highly doubt it's a Frankenstein device - even if it's technically refurbished (this is my third G4, don't bring back memories of the motherboard failures 0_o lol) I did get it through Verizon.

3. I have flashed a MM bootloader stack (from either my SALT backup or the 28a KDZ, they both worked), and that's what finally got me running Android. Are you saying that now I can just flash that N modem zip through TWRP? That's in FAQ 7, which said I need to flash baseband. However, you said I don't need to do that anymore since I already have the USU kernel (the bootimg).

6. I'll keep searching. Maybe it's time to start our own threads in our specific device's forums, so we don't clutter this thread with ROM guides and other stuff.
[G4 General] steadfasterX:
3. no I just saying: follow the FAQ (#20) . I always point to the FAQ as here you find important things like ARB info etc. thats better then following random guides in the thread as they dont care about e.g. the ARB. jm5c.

Well you can try the N modem! And yes there is no need to flash the baseband as long as you are using UsU ROMs or Kernels. Would be nice to know if it boots up fine with the N modem!

6. VS986 aoscp thread opened :P Further tests and reports should go there: https://xdaforums.com/verizon-g4/orig-development/rom-cypheros-4-2-t3782147#post76334277
[G4 General] steadfasterX:
I have added a new section in the OP:

Model specific ROM threads

In that new topic I added links to new threads (others will follow):

- H810

- H812

- H815

- VS986

.
[G4 General] fates13:
I mentioned it because there was a good chance he was using VS986 on Verizon and I knew it was pointless to try AOSCP since I've tested it multiple times. Just as I predicted, he can't get APN working correctly.