Thanks man like I said just wanted to be sure. Baby is sleeping so I could theoretically get away with it now
Sent from my LG-H872 using Tapatalk
Sent from my LG-H872 using Tapatalk
Its up and running. Everything seemed to go well. I got the Android starting guy and the system was wanting to update the os. But I'm booting to recovery fine.
Oh ya I keep reading stuff about vendor and system partition mounting. Should those two be ticked when I boot into recovery? because they aren't, I can get system to tick but not vendor. It's another of those just checking things thing
Sent from my LG-H872 using Tapatalk
Oh ya I keep reading stuff about vendor and system partition mounting. Should those two be ticked when I boot into recovery? because they aren't, I can get system to tick but not vendor. It's another of those just checking things thing
Sent from my LG-H872 using Tapatalk
Yeah definitely dont accept any OTA updates. There is probably a way to disable those notifications, but im not sure how off the top of my head. You will probably end up right back where you started if you accept one.
I have never tried to mount vendor in TWRP. The only reason to really use that partition would be for backups. Zips that are flashed with TWRP should be able to mount vendor just fine. Magisk actually mounts vendor when it's flashed, so if it wasnt able to you would have seen an error flashing it. Vendor is actually a part of System anyway, so I wouldnt worry about it too much.
@weakNPCdotCom
And neither stays ticked after a reboot. Think you were the one mentioning that you had to mount system manually before being able to flash something?
So far nothing strange. Tb pro doesn't seem to want to uninstall anything (magisk debloat script seems to work) but I do have it saving to the sd card instead of internally which I believe was always the point of that app. And I couldn't do that before, app wouldn't write to it from there but I could move stuff to the card manually through es file explorer.
I found magisk interesting since I'm not seeing the preserve encryption deal ticked. That I thought you'd find interesting. I believe that's what you were after with some of this.
I caught your last post.
Lol ya I'm glad too. (I've never had anything be this big a pain in the sack) Maybe this post will change that. Just wanted to let you know what I'm seeing as I go through it since all this stuff in here is your thing, let me know if you want me too look around while I'm in here.
I'm going to make an assumption that from this point I should be able to flash whatever and be ok. Going to back all this up in a few. Would it be worth to do the laf replacement? I'm thinking yes so I'll always be able to run that way if necessary.
Its definitely appreciated. so far I think beyond root you've been doing the stuff that's needed for this device.
Not to mention you put up with me for how long asking you stuff?
Sent from my LG-H872 using Tapatalk
And neither stays ticked after a reboot. Think you were the one mentioning that you had to mount system manually before being able to flash something?
So far nothing strange. Tb pro doesn't seem to want to uninstall anything (magisk debloat script seems to work) but I do have it saving to the sd card instead of internally which I believe was always the point of that app. And I couldn't do that before, app wouldn't write to it from there but I could move stuff to the card manually through es file explorer.
I found magisk interesting since I'm not seeing the preserve encryption deal ticked. That I thought you'd find interesting. I believe that's what you were after with some of this.
I caught your last post.
Lol ya I'm glad too. (I've never had anything be this big a pain in the sack) Maybe this post will change that. Just wanted to let you know what I'm seeing as I go through it since all this stuff in here is your thing, let me know if you want me too look around while I'm in here.
I'm going to make an assumption that from this point I should be able to flash whatever and be ok. Going to back all this up in a few. Would it be worth to do the laf replacement? I'm thinking yes so I'll always be able to run that way if necessary.
Its definitely appreciated. so far I think beyond root you've been doing the stuff that's needed for this device.
Not to mention you put up with me for how long asking you stuff?
Sent from my LG-H872 using Tapatalk
It's all good man. Honestly through this whole process it pays off since I can use it too lol.
I wouldnt worry about system being mounted by default in TWRP. That is how mine has worked too.
I patched the boot image of the rooted rom to remove dm-verity and force encryption, and with it doing that and magisk all at the same time... that might have actually been the magic combination to keep it from encrypting your data. All of these things are good signs to me.
Personally I am keeping TWRP on my laf. If for any reason I lose it on recovery, I can just boot to laf and flash recovery again. Having the StockLAF zip on your phone for convenient access if you ever want to restore DL mode is probably not a bad idea though. Just boot to recovery and flash it when the time comes that you need it. That's just my thinking. I dont want to lose BOTH laf and recovery one day because i had a doh! moment and then have to go through this whole process.
TWRP on LAF, on recovery, and having root are all backup plans in case you lose 2 of 3. If you lose all 3... well let's hope that never happens lol
@weakNPCdotCom
Just wanted to let you know that everything seems to be good. Still haven't restored a backup and there's the mounting system thing prior to flashing anything through twrp. But no weird hiccups.
I saw you got 20a up there now. Has anybody tested that yet? If it runs as well as this does I may go to it. Really like the camera on that build.
I'm all for custom stuff but that ran well without all the garbage in it. Just need to get substratum to work, even on this.
Sent from my LG-H872 using Tapatalk
Just wanted to let you know that everything seems to be good. Still haven't restored a backup and there's the mounting system thing prior to flashing anything through twrp. But no weird hiccups.
I saw you got 20a up there now. Has anybody tested that yet? If it runs as well as this does I may go to it. Really like the camera on that build.
I'm all for custom stuff but that ran well without all the garbage in it. Just need to get substratum to work, even on this.
Sent from my LG-H872 using Tapatalk
glad to hear that man. twrp does the same thing for me but normally things flash fine without me manually mounting system.
Im not sure about the 20a zips being tested, but they should work just fine. FYI though the root one is not deodexed so there is nothing special about it other than being pre-rooted. I ran into some issues with sepolicy on oreo and still haven't got back to it. I plan on trying to deodex it again soon.
If you do try that one you should flash Eliminator74s full 20a stock zip first to get the bootloader and modem otherwise it won't run.
These zips work great but with one caveat. I don't know if it is me somehow and I was hesitant to write anything because I don't want npc to have to feel like he has to do more work. I think this is fine for 99% of people. That being said, bluetooth volume is still really low with these zips. It is about half the normal volume at max and the bass is missing. I am not sure why... I flashed FullStock and then SysBoot on top of that. I followed all the correct procedures. Format data, reboot to recovery, wipe system/data/cache/dalvik cache, flash FullStock, wipe system/data/cache/dalvik cache again, flash SysBoot w/ Magisk, wipe cache/dalvik cache and boot into system. After initial setup, installed Magisk manager and root worked perfectly. So the zips work great, just not bluetooth in my testing...
In the end I am really grateful for the stock 11g laf. This is the next thing I can use to flash the original 11g kdz and start rooting from the ground up. Bascally, I want to run 11g rooted because it is so stable (everything works) and it eats less battery than anything else (including aex in my testing). I haven't tried 20a, but I hear that it eats battery life quickly. Though, those 20a zips npc made may be another thing to try before going the kdz route. Although I don't quite know if I need to upgrade to 20a via kdz first before flashing those zips. Maybe I just need to flash the 20a bootloader zip and then the rest of the 20a zips will work? Either way, thanks npc. :highfive:
Oh and one little fun thing I learned.... This probably doesn't belong in this thread, but it may help someone. If you are restoring apps using Titanium Backup and when selecting your backup folder on external storage it asks you something like, "It looks like you have 78 backups in this folder. Do you want to move them somewhere right now?" DO NOT SAY YES. Lol. I did this and everything disapppeared into thin air. The backups were not moved to internal storage or whatever, they were just deleted. My heart dropped into my stomache and I was in hell :good::cyclops:. I didn't have another backup so I had to restore a nandroid backup and then backup all the apps to get everything back again, then reflash everything. The way I got Titanium Backup to work right was by selecting "Document Storage" as the storage provider and then select the external sd card root directory, then you can pick the correct folder. Phew.
In the end I am really grateful for the stock 11g laf. This is the next thing I can use to flash the original 11g kdz and start rooting from the ground up. Bascally, I want to run 11g rooted because it is so stable (everything works) and it eats less battery than anything else (including aex in my testing). I haven't tried 20a, but I hear that it eats battery life quickly. Though, those 20a zips npc made may be another thing to try before going the kdz route. Although I don't quite know if I need to upgrade to 20a via kdz first before flashing those zips. Maybe I just need to flash the 20a bootloader zip and then the rest of the 20a zips will work? Either way, thanks npc. :highfive:
Oh and one little fun thing I learned.... This probably doesn't belong in this thread, but it may help someone. If you are restoring apps using Titanium Backup and when selecting your backup folder on external storage it asks you something like, "It looks like you have 78 backups in this folder. Do you want to move them somewhere right now?" DO NOT SAY YES. Lol. I did this and everything disapppeared into thin air. The backups were not moved to internal storage or whatever, they were just deleted. My heart dropped into my stomache and I was in hell :good::cyclops:. I didn't have another backup so I had to restore a nandroid backup and then backup all the apps to get everything back again, then reflash everything. The way I got Titanium Backup to work right was by selecting "Document Storage" as the storage provider and then select the external sd card root directory, then you can pick the correct folder. Phew.
Don't have that Bluetooth issue myself but then I run viper on everything. Also with tb you can move them from internal to external storage. After this it's correct and on external but I had to do it that way once before. Maybe it needs a tb folder already in internal?
Sent from my LG-H872 using Tapatalk
How do you get viper to work? I was totally trying to use it to fix the bt volume issue except I can never get the driver to install, it always fails. The last time I tried it, system ui crashed at boot and made the screen go black.
the one I'm using is the magisk module version 1.7.4 and pick old each time it asks during flash through magisk itself not recovery
Sent from my LG-H872 using Tapatalk
That's interesting. I am honestly not sure why the bluetooth audio would have issues. Unless you used the deodexed rom the entire system image is untouched and a straight copy from the KDZ. But, I can tell you that I also have had bluetooth volume issues with certain apps ever since I got this phone. Most of the time it would be youtube, or I would be listening to music while using GPS and when the GPS app reduced volume to speak, then all of the sudden my audio volume was super low and couldnt be fixed without rebooting.
Regarding 20a, flashing the 20a bootloader first will allow the 20a sysboot rom to work. However, you might want to go ahead and update the modem too. So either flash bootloader and modem and then sysboot, or flash Eliminator74's complete 20a zip, wipe system and flash sysboot.
Thank you for your feedback on these. And if there is ever a problem, don't hesitate to mention it. I dont want to supply crappy software for everybody
Only time I have an issue is when I'm watching something and a call comes through I'll get a beeping nose that won't go away till I disconnect and reconnect bt
Sent from my LG-H872 using TapatalkThat's interesting. I am honestly not sure why the bluetooth audio would have issues. Unless you used the deodexed rom the entire system image is untouched and a straight copy from the KDZ. But, I can tell you that I also have had bluetooth volume issues with certain apps ever since I got this phone. Most of the time it would be youtube, or I would be listening to music while using GPS and when the GPS app reduced volume to speak, then all of the sudden my audio volume was super low and couldnt be fixed without rebooting.
Regarding 20a, flashing the 20a bootloader first will allow the 20a sysboot rom to work. However, you might want to go ahead and update the modem too. So either flash bootloader and modem and then sysboot, or flash Eliminator74's complete 20a zip, wipe system and flash sysboot.
Thank you for your feedback on these. And if there is ever a problem, don't hesitate to mention it. I dont want to supply crappy software for everybody
Patched LGUP not detecting phone on TWRP LAF
@weakNPCdotCom, @Ken C, Hey mate, I am on 11g rooted with TWRP on LAF and Recovery. I want to go to Oreo 20a/20d, as I have to use patched LGUP (for partition dl option), I power off then press vol up + USB cable and fire up LGUP.
It does not detect phone "the phone is not connected", no com port detected, though device manager detects adb composite driver.
Do I have to flash stocklaf from recovery before LGUP detects it?
Any suggestions?
@weakNPCdotCom, @Ken C, Hey mate, I am on 11g rooted with TWRP on LAF and Recovery. I want to go to Oreo 20a/20d, as I have to use patched LGUP (for partition dl option), I power off then press vol up + USB cable and fire up LGUP.
It does not detect phone "the phone is not connected", no com port detected, though device manager detects adb composite driver.
Do I have to flash stocklaf from recovery before LGUP detects it?
Any suggestions?
Yeah I don't have a clue either. Even when my phone was flashed with the kdz, I had weird volume changes with maps and secondary sound sources, but not a limited volume issue. It would occur in a similar scenario to yours. If I started playing music BEFORE launching google maps, then the maps voice sound would be at a really low volume. You could increase the volume while the voice directions were being given, but every consecutive time the volume would go back to near zero. The only way to get those apps to work together is to launch maps first and get the voice directions going through bluetooth and only then launch a second source of sound (youtube/newpipe background/music player/etc). Then when it lowered the music audio, the voice directions were at a high enough volume as well. That is a weird bug in 11g I think.That's interesting. I am honestly not sure why the bluetooth audio would have issues. Unless you used the deodexed rom the entire system image is untouched and a straight copy from the KDZ. But, I can tell you that I also have had bluetooth volume issues with certain apps ever since I got this phone. Most of the time it would be youtube, or I would be listening to music while using GPS and when the GPS app reduced volume to speak, then all of the sudden my audio volume was super low and couldnt be fixed without rebooting.
Regarding 20a, flashing the 20a bootloader first will allow the 20a sysboot rom to work. However, you might want to go ahead and update the modem too. So either flash bootloader and modem and then sysboot, or flash Eliminator74's complete 20a zip, wipe system and flash sysboot.
Thank you for your feedback on these. And if there is ever a problem, don't hesitate to mention it. I dont want to supply crappy software for everybody
I am going to keep trying different things including 11h, 20a, and using viper as well. I will let you know what solution I discover. Thanks for the heads up on the 20a procedure when using eliminators zip. I am going to try his C2 zip which is complete without laf.
Your software is legit, far from crappy my friend! I really like how you explain things in detail. That is something lacking on xda in my experience. Thanks for all your hard work.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
Hmm I'll try this... Does viper work on 11g, 11h, and 20a? What are you running now? Thanks buddy.
---------- Post added at 10:50 PM ---------- Previous post was at 10:37 PM ----------
weakNPCdotCom will probably have a better answer for you, but I might be able to help. If you followed the root procedure by runningnak3d, then you have TWRP on your LAF partition and you also have TWRP on your Recovery partition. This is actually a good thing because if one gets wiped or flashed over, you have a failover. Now because TWRP is on LAF, that is why LGUP will not see your phone and you are not able to install via kdz currently.
Essentially, you have three options to go to 20a.
1. Boot into recovery, format data, then reboot into recovery again. Wipe system/data/cache/dalvik cache. Flash the 20a bootloader without LAF (very important to retain recovery on LAF) and modem zips available from Eliminator74: LG-H872_Oreo-20a_Bootloader_B2.zip (WO/LAF), LG-H872_Oreo-20a_Modem_Only.zip (Safe Either Way). Then Then flash the 20a SysBoot zip w/Magisk from the 20a thread by weaknpc. Now wipe cache/dalvik cache again and boot into system. Then you are on 20a and have root.
2. Boot into recovery, format data, then reboot into recovery again. Wipe system/data/cache/dalvik cache. Flash the complete 20a zip available from Eliminator74 without LAF (very important to retain recovery on LAF). That is this one: LG-H872_Oreo-20a_Complete_C2.zip (WO/LAF). Then wipe system/data/cache/dalvik cache. Then flash the 20a SysBoot zip w/Magisk from the 20a thread by weaknpc over the one from Eliminater74. Now wipe cache/dalvik cache again and boot into system. Then you are on 20a and have root.
3. Flash the 11g StockLAF zip in this thread and then use LGUP to flash the 20a kdz. Then follow the whole root process from runningnak3d again.
I think that option 1 and 2 are easier and less risky since you retain recovery no matter what. The zips from Eliminator74 and weakNPCdotCom DO NOT have the stock recovery in them, so they won't flash over the recovery partition where you have TWRP. As long as you pick the right zips, they will also leave your LAF partition alone as well, which means TWRP stays on LAF as well.
Last edited:
couldn't have answered any better :good:Yeah I don't have a clue either. Even when my phone was flashed with the kdz, I had weird volume changes with maps and secondary sound sources, but not a limited volume issue. It would occur in a similar scenario to yours. If I started playing music BEFORE launching google maps, then the maps voice sound would be at a really low volume. You could increase the volume while the voice directions were being given, but every consecutive time the volume would go back to near zero. The only way to get those apps to work together is to launch maps first and get the voice directions going through bluetooth and only then launch a second source of sound (youtube/newpipe background/music player/etc). Then when it lowered the music audio, the voice directions were at a high enough volume as well. That is a weird bug in 11g I think.
I am going to keep trying different things including 11h, 20a, and using viper as well. I will let you know what solution I discover. Thanks for the heads up on the 20a procedure when using eliminators zip. I am going to try his C2 zip which is complete without laf.
Your software is legit, far from crappy my friend! I really like how you explain things in detail. That is something lacking on xda in my experience. Thanks for all your hard work.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
Hmm I'll try this... Does viper work on 11g, 11h, and 20a? What are you running now? Thanks buddy.
---------- Post added at 10:50 PM ---------- Previous post was at 10:37 PM ----------
weakNPCdotCom will probably have a better answer for you, but I might be able to help. If you followed the root procedure by runningnak3d, then you have TWRP on your LAF partition and you also have TWRP on your Recovery partition. This is actually a good thing because if one gets wiped or flashed over, you have a failover. Now because TWRP is on LAF, that is why LGUP will not see your phone and you are not able to install via kdz currently.
Essentially, you have three options to go to 20a.
1. Boot into recovery, format data, then reboot into recovery again. Wipe system/data/cache/dalvik cache. Flash the 20a bootloader without LAF (very important to retain recovery on LAF) and modem zips available from Eliminator74: LG-H872_Oreo-20a_Bootloader_B2.zip (WO/LAF), LG-H872_Oreo-20a_Modem_Only.zip (Safe Either Way). Then Then flash the 20a SysBoot zip w/Magisk from the 20a thread by weaknpc. Now wipe cache/dalvik cache again and boot into system. Then you are on 20a and have root.
2. Boot into recovery, format data, then reboot into recovery again. Wipe system/data/cache/dalvik cache. Flash the complete 20a zip available from Eliminator74 without LAF (very important to retain recovery on LAF). That is this one: LG-H872_Oreo-20a_Complete_C2.zip (WO/LAF). Then wipe system/data/cache/dalvik cache. Then flash the 20a SysBoot zip w/Magisk from the 20a thread by weaknpc over the one from Eliminater74. Now wipe cache/dalvik cache again and boot into system. Then you are on 20a and have root.
3. Flash the 11g StockLAF zip in this thread and then use LGUP to flash the 20a kdz. Then follow the whole root process from runningnak3d again.
I think that option 1 and 2 are easier and less risky since you retain recovery no matter what. The zips from Eliminator74 and weakNPCdotCom DO NOT have the stock recovery in them, so they won't flash over the recovery partition where you have TWRP. As long as you pick the right zips, they will also leave your LAF partition alone as well, which means TWRP stays on LAF as well.
By the way, before you take my advice on upgrading to 20a, hold on a moment. I just tried flashing the Eliminator74 Complete C2 zip from option 1 and it fails verification and cannot flash. In option 2, the Bootloader B2 works, but the Modem Only zip also fails verification. So, I would not reccomend steps 1 or 2 that I originally gave you at the moment. I will update you. Maybe it was my mistake.
Did you post in his thread? I let him know a few days back that his checksum portion of one of his zips had a simple error in it. I think he's taking a break from dev stuff atm though.By the way, before you take my advice on upgrading to 20a, hold on a moment. I just tried flashing the Eliminator74 Complete C2 zip from option 1 and it fails verification and cannot flash. In option 2, the Bootloader B2 works, but the Modem Only zip also fails verification. So, I would not reccomend steps 1 or 2 that I originally gave you at the moment. I will update you. Maybe it was my mistake.
I can try to make a FullStock for 20a but I won't be able to until later tonight
Yes I did post in his thread... I think you are right. That man needs a break. If you could do that, wow, amazing. Though you should take your time and enjoy the weekend! Thanks buddy.
I am going to redownload his zips and try once more...
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone