I purchased a LS998 and followed ChazzMatt's guide to convert it to a US998. This worked fine:
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
I was able to unlock my bootloader and flash TWRP all OK.
I eventually flashed the latest LGUP firmware "US99820h_00_0318.kdz".
From this I was able to install the latest Magisk 20.4, "AK3_RCTD_Remover", and "Disable_Dm-Verity_ForceEncrypt".
LG's native rom boots fine and everything seems to work; wifi, camera, etc.
Satisfied with this setup, I flashed "lineage-16.0-20200807-UNOFFICIAL-h930.zip" and set everything up as I wanted. Everything worked-- EXCEPT for the camera. Every time the stock AOSP camera (or any other camera app) launched, it would immediately crash.
I flashed "US99820h_00_0318.kdz" back with REFURBISH and confirmed that the camera was fine. Since this removed TWRP as the stock recovery, I had to repeat the same steps from above.
But now every time I boot into LOS 16, it will hang after a short period of time at the setup screen (where it says START). I can click on start while it is still responsive but the "Just a sec..." message and the progress circle will spin and not proceed. The phone will then eventually locks up from there.
I have been unable to figure out how to fix this. I can always revert back to "US99820h_00_0318.kdz" without issue but I can no longer get back onto LOS 16 for some reason.
I did make a TWRP backup of Boot/Data/System but restoring this on top of LOS 16 results in the phone booting up to a progress message "Phone is starting..." which will eventually lead to it too failing to progress and locking up.
I have been flashing roms for years and I have NEVER had this much trouble before. Once a recovery is loaded, flashing a rom, wiping data and doing a factory reset ALWAYS gave me a working system. But it fails here. Why?
Kahenraz said:
I purchased a LS998 and followed ChazzMatt's guide to convert it to a US998. This worked fine:
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
I was able to unlock my bootloader and flash TWRP all OK.
I eventually flashed the latest LGUP firmware "US99820h_00_0318.kdz".
From this I was able to install the latest Magisk 20.4, "AK3_RCTD_Remover", and "Disable_Dm-Verity_ForceEncrypt".
LG's native rom boots fine and everything seems to work; wifi, camera, etc.
Satisfied with this setup, I flashed "lineage-16.0-20200807-UNOFFICIAL-h930.zip" and set everything up as I wanted. Everything worked-- EXCEPT for the camera. Every time the stock AOSP camera (or any other camera app) launched, it would immediately crash.
I flashed "US99820h_00_0318.kdz" back with REFURBISH and confirmed that the camera was fine. Since this removed TWRP as the stock recovery, I had to repeat the same steps from above.
But now every time I boot into LOS 16, it will hang after a short period of time at the setup screen (where it says START). I can click on start while it is still responsive but the "Just a sec..." message and the progress circle will spin and not proceed. The phone will then eventually locks up from there.
I have been unable to figure out how to fix this. I can always revert back to "US99820h_00_0318.kdz" without issue but I can no longer get back onto LOS 16 for some reason.
I did make a TWRP backup of Boot/Data/System but restoring this on top of LOS 16 results in the phone booting up to a progress message "Phone is starting..." which will eventually lead to it too failing to progress and locking up.
I have been flashing roms for years and I have NEVER had this much trouble before. Once a recovery is loaded, flashing a rom, wiping data and doing a factory reset ALWAYS gave me a working system. But it fails here. Why?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v30/how-to/detailed-guide-aosp-roms-issues-solution-t4002535
That helps to explain the camera (it doesn't work with anything but GCam) but not how to get LOS 16 working again.
Kahenraz said:
I purchased a LS998 and followed ChazzMatt's guide to convert it to a US998.
This worked fine:
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
I was able to unlock my bootloader and flash TWRP all OK.
I eventually flashed the latest LGUP firmware "US99820h_00_0318.kdz".
From this I was able to install the latest Magisk 20.4, "AK3_RCTD_Remover", and "Disable_Dm-Verity_ForceEncrypt".
LG's native rom boots fine and everything seems to work; wifi, camera, etc.
Click to expand...
Click to collapse
You're welcome!
Kahenraz said:
Satisfied with this setup, I flashed "lineage-16.0-20200807-UNOFFICIAL-h930.zip" and set everything up as I wanted. Everything worked-- EXCEPT for the camera. Every time the stock AOSP camera (or any other camera app) launched, it would immediately crash.
Click to expand...
Click to collapse
Some people have had issues with camera on LOS and need different permissive kernel. @tech_infinity is one of the experts and I see he's tried to help.
You were correct in flashing LOS-16 from last stock Oreo. If you had updated to stock Pie, then tried to flash LOS-16, I would have said that was part of your problem.
I do not know why you cannot load LOS-16, but one possible way of fixing it is a little tedious, but you can try if you are willing.
Flash Nougat US998 KDZ via Refurbish mode. This is only temporary stage. You will lose TWRP and root but still have unlocked bootloader. Going back to Nougat cleans out a lot of stuff. Then flash US998 20h KDZ. You will still have unlocked bootloader.
At that point, then, follow WTF Section 6 to reinstall TWRP, encryption disabler, root check disabler, root.
Then, try to install LOS-16 again. But this time perhaps try a different permissive custom kernel, which @tech_infinity can suggest to you. That may solve your camera problems, and hopefully the Nougat-back-to-Oreo will solve the LOS-16 loading issue.
Kahenraz said:
That helps to explain the camera (it doesn't work with anything but GCam) but not how to get LOS 16 working again.
Click to expand...
Click to collapse
You tried going permissive already?
The issue with the boot hang ended up being an issue with the SD card I had inserted. It worked fine in TWRP and LG's Android rom but it would hang for LOS 16.
Before I had done a wipe of my first install of LOS 16, I backed up the rom and copied it over to disk on Windows. But I must have made a mistake on removal that left the FAT32 filesystem in an inconsistent state.
I finally stuck it into my PC where Windows asked that I repair it. LOS 16 worked fine after that; with and without the same SD card.
The camera was fixed by enabling SELinux to Permissive. I'm not a fan of this as I do like the security that SELinux provides. But I also need my camera... and I see no alternative.
Kahenraz said:
The issue with the boot hang ended up being an issue with the SD card I had inserted. It worked fine in TWRP and LG's Android rom but it would hang for LOS 16.
Before I had done a wipe of my first install of LOS 16, I backed up the rom and copied it over to disk on Windows. But I must have made a mistake on removal that left the FAT32 filesystem in an inconsistent state.
I finally stuck it into my PC where Windows asked that I repair it. LOS 16 worked fine after that; with and without the same SD card.
Click to expand...
Click to collapse
Glad you got it figured out.
Kahenraz said:
The camera was fixed by enabling SELinux to Permissive. I'm not a fan of this as I do like the security that SELinux provides. But I also need my camera... and I see no alternative.
Click to expand...
Click to collapse
All V30 LOS-based ROMs need Permissive. Sometimes when reverting from LOS-17 ROMs back to stock Android 9, you then still need to run permissive kernel. Or else camera won't work and other sensors. It's like remnants of LOS-17 still affecting the phone even though you are back on stock. The way people can fix that (most of the time) is to refurbish to Nougat, then go back to newer firmware. That was why I suggested that, but it turned out to be your microSD card.
Are you saying that I could have SELinux Enforcing if I had not flashed stock Pie and then LOS 17?
Kahenraz said:
Are you saying that I could have SELinux Enforcing if I had not flashed stock Pie and then LOS 17?
Click to expand...
Click to collapse
No. I'm saying all V30 LOS ROMs require permissive.
Furthermore, after running LOS ROM 17 if you wish to return to stock you may STILL need permissive mode for camera and other sensors. (LOS-16 doesn't have this after-effect returning to stock.) The fix for the LOS-17 remnants gunk is to refurbish back to Nougat, then update again to newer stock. That often works.
But all V30 LOS ROMs require permissive.
Related
I am wondering why I can not put a custom rom onto my V30 converted to a US998. Everything I find online is for the H931 and I would like to try out some of these roms. I read that they should work on the phone but when I tried it I did not receive any signal from Verizon. Also when going threw to new phone setup the screen would go black. After I would reboot and go threw the process again it still happened.
danieledwrds2014 said:
I am wondering why I can not put a custom rom onto my V30 converted to a US998. Everything I find online is for the H931 and I would like to try out some of these roms. I read that they should work on the phone but when I tried it I did not receive any signal from Verizon. Also when going threw to new phone setup the screen would go black. After I would reboot and go threw the process again it still happened.
Click to expand...
Click to collapse
You have a exfat sdcard? Kernel driver probably doesnt like it, and eventually crashes the phone (and when youre "too slow", that happens during setup)
The H930 roms work fine on H930(D/DS/G), US998, LS998 and VS996, you would be the first for who it wouldnt work . Its just known that you kinda need to place a call every now and then on Verizon (and only there...) otherwise you wont receive sms/calls but data works fine...
Just (converted) H931 and H933 bootloop (except 1 guy who managed to make it work on his H933... and nobody, not even himself, knows how). No idea of the 3 korean variants now though...
SGCMarkus said:
You have a exfat sdcard? Kernel driver probably doesnt like it, and eventually crashes the phone (and when youre "too slow", that happens during setup)
The H930 roms work fine on H930(D/DS/G), US998, LS998 and VS996, you would be the first for who it wouldnt work . Its just known that you kinda need to place a call every now and then on Verizon (and only there...) otherwise you wont receive sms/calls but data works fine...
Just (converted) H931 and H933 bootloop (except 1 guy who managed to make it work on his H933... and nobody, not even himself, knows how). No idea of the 3 korean variants now though...
Click to expand...
Click to collapse
I do not have any sdcard installed on my phone at all. I don't know how I am being to slow with the setup. When it pops up with the setup I just press on next or fill everything in. Just for some reason the screen goes black. I used the v30 version of resurrection remix. And I used the stock version of Open GApps, I read I should probably try to nano or pico version. Just to verify I should be using the ARM64 version correct?
Please explain the have to make a call to verizon (every once in a while) or I can recieve sms or calls.
danieledwrds2014 said:
I do not have any sdcard installed on my phone at all. I don't know how I am being to slow with the setup. When it pops up with the setup I just press on next or fill everything in. Just for some reason the screen goes black. I used the v30 version of resurrection remix. And I used the stock version of Open GApps, I read I should probably try to nano or pico version. Just to verify I should be using the ARM64 version correct?
Please explain the have to make a call to verizon (every once in a while) or I can recieve sms or calls.
Click to expand...
Click to collapse
Thats a weird behaviour for a VS996
havent heard of that before. Usually it only crashes during setup if the kernel shouldnt like the installed exfat sdcard. Never heard of it happening otherwise
And what i mean with that was that for some reason only verizon users need to place a call after booting (or after some amount of time), otherwise they wont receive any calls or sms, even though data works all the time.
SGCMarkus said:
Thats a weird behaviour for a VS996
havent heard of that before. Usually it only crashes during setup if the kernel shouldnt like the installed exfat sdcard. Never heard of it happening otherwise
And what i mean with that was that for some reason only verizon users need to place a call after booting (or after some amount of time), otherwise they wont receive any calls or sms, even though data works all the time.
Click to expand...
Click to collapse
I don't know if it matters but its a converted VS996 to a US998. I know its weird, is there a version of resurrection remix os that I should try. I tried the unofficial one here. ( https://forum.xda-developers.com/lg-v30/development/rom-resurrectionremix-v6-0-0-t3798443 ) due to not being to find a supported version on Resurrection Remix's website at all. I really want to get this to work just don't want to brick my phone in the process. I understand that is always a risk that everyone takes but when I followed the directions it still didn't work. Maybe I am looking at the wrong place, or doing something wrong.
I am running the 20d of the US998 firmware
Used TWRP format everything execpt the actual system itself.
Used TWRP to install ( RR .zip file and then the GApps file) <-----should i use the micro or pico?
Booted into the phone everything went good during the setup process I chose mobile data and turned off wifi. Then the setup screen went black. I could still see the status bar in the top where it shows battery etc...
(During the setup process I had no connection with verizon) <------Any idea why?
I have the Verizon vs996 as my phone. I have used the Frankenstein method to change it to the us998 version, then unlocked the bootloader and then eventually rooted the phone. I have successfully installed and used at least most, if not all of SGCMarkus' roms, including RR (the version you linked).
I have also used AEX, DotOS, AOSIP, Dirty Unicorns 9.0, twrp flashable vs996 and us998 roms (currently on the twrp vs 996_20f), and maybe others that I am forgetting (it seems like I am forgetting a rom or two)? I have successfully flashed and used all of those I have mentioned. I have successfully flashed and installed Boom box rom, but cannot get the data to work on it. I have not tried to flash or install lineage.
So, I know that it can be done on a Verizon VS996 phone.
So, if you are successfully boot loader unlocked and rooted with twrp installed, it should work.
So, I would download the rom of choice and the suggested gapps (I normally use Nano, and I think v30, does use the arm 64 version. Make sure you have the correct 8.0 or 8.1 download of gapps) and Magisk.
I have used both the data only and also wifi in the setup process successfully. Don't ever recall getting a black screen. I do have an old 32gb SD card that has not given me any trouble (yet).
Hopefully, you can get it worked out and working OK.
I found the reason for all my issues was because I used the Open GApps Stock instead of the nano I switched it out and its working perfectly.
gimpy1 said:
I have the Verizon vs996 as my phone. I have used the Frankenstein method to change it to the us998 version, then unlocked the bootloader and then eventually rooted the phone. I have successfully installed and used at least most, if not all of SGCMarkus' roms, including RR (the version you linked).
I have also used AEX, DotOS, AOSIP, Dirty Unicorns 9.0, twrp flashable vs996 and us998 roms (currently on the twrp vs 996_20f), and maybe others that I am forgetting (it seems like I am forgetting a rom or two)? I have successfully flashed and used all of those I have mentioned. I have successfully flashed and installed Boom box rom, but cannot get the data to work on it. I have not tried to flash or install lineage.
So, I know that it can be done on a Verizon VS996 phone.
So, if you are successfully boot loader unlocked and rooted with twrp installed, it should work.
So, I would download the rom of choice and the suggested gapps (I normally use Nano, and I think v30, does use the arm 64 version. Make sure you have the correct 8.0 or 8.1 download of gapps) and Magisk.
I have used both the data only and also wifi in the setup process successfully. Don't ever recall getting a black screen. I do have an old 32gb SD card that has not given me any trouble (yet).
Hopefully, you can get it worked out and working OK.
Click to expand...
Click to collapse
After flashing and upgrading to pie, my camera stopped working as a whole. The app freezes every time you open it, and the camera is no longer recognized by apps (e.g. Instagram) and the facial recognition setup. The flashlight also doesn't work anymore.
Along with this issue, some Google apps have strange behavior (e.g play music doesn't download music, youtube never loads, etc.), which persisted even when I uninstalled and reinstalled the apps.
Did I do something wrong? I'm running pie US99830B on a H931 frankensteined to US998. The way I flashed it follows these instructions https://forum.xda-developers.com/lg-v30/how-to/guide-booting-aosp-stock-pie-us998-t3954155 but replacing the last step with flashing of the US99830B zip (the other methods of flashing resulted in the phone being stuck at the LG Life's Good logo). What should I do?
carl807 said:
After flashing and upgrading to pie, my camera stopped working as a whole. The app freezes every time you open it, and the camera is no longer recognized by apps (e.g. Instagram) and the facial recognition setup. The flashlight also doesn't work anymore.
Along with this issue, some Google apps have strange behavior (e.g play music doesn't download music, youtube never loads, etc.), which persisted even when I uninstalled and reinstalled the apps.
Did I do something wrong? I'm running pie US99830B on a H931 frankensteined to US998. The way I flashed it follows these instructions https://forum.xda-developers.com/lg-v30/how-to/guide-booting-aosp-stock-pie-us998-t3954155 but replacing the last step with flashing of the US99830B zip (the other methods of flashing resulted in the phone being stuck at the LG Life's Good logo). What should I do?
Click to expand...
Click to collapse
Try Dev Patched LGUP Refurbish to PIE KDZ. Or Partition DL to Pie KDZ.
You probably have some H933 Partitions confusing things.
So from my installation, do I just get into download mode and refurbish to the pie kdz? Do I need to do any additional prep work, or is that it?
carl807 said:
So from my installation, do I just get into download mode and refurbish to the pie kdz? Do I need to do any additional prep work, or is that it?
Click to expand...
Click to collapse
I would try Partition DL with all partitions.
I managed to solve the problem.
What I did is that I reflashed the US99830B zip in TWRP, reflashed magisk, and cleared the cache/dalvik. Then everything worked, from the camera to youtube to the google apps.
Thanks for your help though. I'll keep that in mind the next time I screw up.
carl807 said:
I managed to solve the problem.
What I did is that I reflashed the US99830B zip in TWRP, reflashed magisk, and cleared the cache/dalvik. Then everything worked, from the camera to youtube to the google apps.
Thanks for your help though. I'll keep that in mind the next time I screw up.
Click to expand...
Click to collapse
U dirty flashed or wiped then flashed?
I dirty flashed over my current installation.
Ok having same issue as you so gonna try it now
---------- Post added at 05:29 AM ---------- Previous post was at 05:22 AM ----------
That fixed it... Thanks a lot
@ChazzMatt might be worth mentioning over at the us998 pie thread?
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
First, you need to be on the latest stock firmware. Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
AOSiP was built from LineageOs.
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
50UND2 3NG1N33R said:
Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
Click to expand...
Click to collapse
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
50UND2 3NG1N33R said:
AOSiP was built from LineageOs.
Click to expand...
Click to collapse
Cool. I cant install neither.
50UND2 3NG1N33R said:
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
Click to expand...
Click to collapse
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
50UND2 3NG1N33R said:
All others might work, please do not ask in here how to up- or downgrade!
Click to expand...
Click to collapse
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
thegamerchunk1 said:
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
Cool. I cant install neither.
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
Click to expand...
Click to collapse
okay, sorry for not understanding you. You ain't a noob. So I should expect you did a clean install. Wiping Dalvik/ART Cache, Cache, Data, Internal Storage and System. this will give you a clean slate. And be on the latest TWRP which you already are in. If that fails, I can't help beyond that. VOLTE is Voice Over LTE. You are correct.
So I really messed up I think.
My friend - who is on vacation had borrowed my phone earlier this year, and for some reason didn't reset it properly.
Now I need it again, but I couldn't start it up, due to the phone being locked to his Gmail account.
So I went into TWRP and reset the phone, did a wipe on Dalvik/Art Cache, System, Data and Cache. Then I realized I just deleted the ROM that was previously on it, so I downloaded another ROM for the phone. But it wouldn't finish booting after starting to load the system, so I downloaded another one. This one still won't boot up after coming to the system bootup after the LG V30 Thinq logo has shown. I have tried Havoc and Liquid ROM with and without gapps.
My phone is the Korean version.
Do I need to flash some kind of Magisk or SuperSU with the ROM, or can anyone help me so I can get my phone working again?
BobberK said:
So I went into TWRP and reset the phone, did a wipe on Dalvik/Art Cache, System, Data and Cache. Then I realized I just deleted the ROM that was previously on it, so I downloaded another ROM for the phone. But it wouldn't finish booting after starting to load the system, so I downloaded another one. This one still won't boot up after coming to the system bootup after the LG V30 Thinq logo has shown. I have tried Havoc and Liquid ROM with and without gapps.
My phone is the Korean version.
Do I need to flash some kind of Magisk or SuperSU with the ROM, or can anyone help me so I can get my phone working again?
Click to expand...
Click to collapse
What was the previous ROM? If it was LOS-16 based, you can't replace with LOS-17 based ROM without first flashing stock Pie firmware. LOS-17 ROMS need stock Pie blobs (drivers), while the older LOS-16 ROMs need stock Oreo blobs (drivers).
That's the most common reason for what you describe and fits the timeline of you not having the phone in your hands for several months.
Yes, you do need to flash Magisk with the custom ROM and usually GAPPs as well. (Although a few ROMs come with their own GAPPS.)
Here's current LOS-16 ROM if you want to try that:
XDA THREAD:
https://forum.xda-developers.com/lg-v30/development/rom-lineageos-16-0-lineageos-17-0-wip-t4042333
DOWNLOAD:
https://github.com/ShapeShifter499/...ses/tag/lineage-16.0-20200716-h930_oreo-blobs
That dev makes new builds almost every day -- both for universal "H930" (all variants except T-mobile H932) and also builds specifically for T-mobile H932. That download link is for 07/16 daily build for "H930".
But there is still the matter of the account: FRP doesn't go away just by wiping in TWRP or flashing a different ROM, as far as I know.
The best solution would have been too simply log in with the previous account, then delete the account in the OS. That would release the FRP.
If you manage to boot any ROM, I would do that first thing. If your friend is far away, then give him a call. He could temporarily change his Google password to something simple, give it to you, then change it back once you have removed his account from the phone.
Edit: maybe flashing with LGUP Refurbish mode clears FRP. Do you know that, @ChazzMatt.
ChazzMatt said:
What was the previous ROM? If it was LOS-16 based, you can't replace with LOS-17 based ROM without first flashing stock Pie firmware. LOS-17 ROMS need stock Pie blobs (drivers), while the older LOS-16 ROMs need stock Oreo blobs (drivers).
That's the most common reason for what you describe and fits the timeline of you not having the phone in your hands for several months.
Yes, you do need to flash Magisk with the custom ROM and usually GAPPs as well. (Although a few ROMs come with their own GAPPS.)
Here's current LOS-16 ROM if you want to try that:
XDA THREAD:
https://forum.xda-developers.com/lg-v30/development/rom-lineageos-16-0-lineageos-17-0-wip-t4042333
DOWNLOAD:
https://github.com/ShapeShifter499/...ses/tag/lineage-16.0-20200716-h930_oreo-blobs
That dev makes new builds almost every day -- both for universal "H930" (all variants except T-mobile H932) and also builds specifically for T-mobile H932. That download link is for 07/16 daily build for "H930".
Click to expand...
Click to collapse
Is there an easy way to use that manifest? Normally it's just a ZIP file you need to flash. What it says in that guide looks like rubbish to me
Sorry for being a complete noob
BobberK said:
Is there an easy way to use that manifest? Normally it's just a ZIP file you need to flash. What it says in that guide looks like rubbish to me
Sorry for being a complete noob
Click to expand...
Click to collapse
Normally just go here and click on the heading of the build you want. At least on PC it starts a download. If it's not triggering a download make sure your pop up blockers are disabled. Unless something has changed there recently. @ShapeShifter499?
https://github.com/ShapeShifter499/LG_v30-LineageOS_Manifest/releases
Do NOT choose any T-Mobile H932 builds, since you don't have that model.
About This Rom
This is a debloated stock rom based on stock F800K_30H. Most likely the last update the V20 will get.
Installation Procedure for F800 L/K/S
Download the F800***.7z to a PC and extract with 7-zip app on Windows PC or the equivalent on OSX / Linux . This will expand to a single 6GB system.img file. Copy over to internal storage on your device.
Update TRWP recovery to 3.4.x.x using TWRP.
Download also the F800 boot imgage and F800K-ezv2020.zip kernel.
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Boot into twrp and flash the system image.
Install>Install_Image(bottom right)>navigate to system.img file and select system image partition.
Repeat the same procedure for the boot.img, flash on boot partition.
Flash ezV2020 Kernel and then Magisk. Done.
If you are coming from Oreo download also the Pie partitions and flash that first, then as above. Also wipe data so have your apps backed up.
In the case your were already on PIE no need to wipe data but do wipe Dalvik / ART cache and Cache in TWRP before reboot. Device will be slow for a while and will speed up as Dalvik cache is rebuilt in the background. Sometimes that can take a while especially if you don't let the device rest.
==========================================================
Update Nov 2022: You now need to flash in twrp this Chrome update to pass initial setup screen after phone reset or fresh flash.
F800 - Google Drive
drive.google.com
Release v2
This is based on K rather than L for no good reason (new: flash the K partitions in my repo and ezv2020 K kernel), but makes no difference as all carrier apps have been deleted. This is a 'start again' version rather than an update to ver 1 and is recommended to update due to reports of better performance.
Added
QLens
V30 and G6 themes ( I like the black one with dark grey accents)
Sim unlock app (I think it's for phones locked to sim, not sure if it is or if it works)
Wap Push Service (for carrier settings sent via text msg)
Collage Wallpapers from G6 - only works on Lock Screen, dunno why, i'll try fix.
LG Smart World. You must hide it in Magisk first, then software update. Don't know how to change Korean language, sorry.
If you don't care for any of these additions delete them from /system/product/app , using a root browser
RCT (root check tool) remover has already been applied.
Known issues (minor)
Touch screen is not responsive after coming out of Laf Download Mode at times. To recover this simply reboot into recovery and reboot. It's not that serious and doesn't occur after a normal reboot. You just need to be aware of the fix in case you experience it.
If you have any apn issues do the 'reset apn settings to default' in the apn settings menu. Cuz my carrier apn didn't show up initially.
==========================================================
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
TarAntonio said:
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
Click to expand...
Click to collapse
Install Mixploer from here http://mixplorer.com/
Download the attachment provided and extract the folder to Internal Storage
Using Mixplorer copy and paste the Folder named LGCalendarProvider to...
root>system>product>priv-app
(you may be asked to grant root permission here)
Make sure you can see the LGCalendarProvider Folder is in priv-app folder, now reboot.
Google calendar is working for me now.
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
TheRoyalDuke said:
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
Click to expand...
Click to collapse
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
ezzony said:
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
Click to expand...
Click to collapse
Bluetooth works fantanstic. Connected my portable speaker and it played smoothly, never disconnected.
TheRoyalDuke said:
Edit: F800L30H_Partitions is needed to get fingerprint working.
Click to expand...
Click to collapse
Thanks for that. It might be just the modem that is needed. Can you get into download mode after flashing the partitions? Be careful. That is why I said in the OP don't flash Pie Partitions on non-F800 although you may not have seen that as I added it later.
I have a zip somewhere to flash back oreo partitions. I'll upload it later.
edit: just checked my us996, fingerprint is working fine without flashing pie partitions. Please delete your edit as I don't want anyone flashing pie partitions on non-f800 devices because of the laf download problem.
I will have to figure out what exactly is going on but until then I don't support of advise anyone to flash Pie partitions on any non-F800 device.
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
TheRoyalDuke said:
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
Click to expand...
Click to collapse
Ah good. Because there was an issue with the new Pie LG LAF (download mode) not being detected in LGUP. Experienced that myself. The danger is then if you accidentally deleted TWRP or somehow got corrupted there would be no way to ever flash the phone again and you'd be stuck with what you have. That is why I'm being extra cautions.
Note:
I still don't advise anyone to flash pie partitions on non-f800. There are so many variants it's not certain or knowable if all will be okay for all of them.
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloated right?
xxseva44 said:
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloat right?
Click to expand...
Click to collapse
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
ezzony said:
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
Click to expand...
Click to collapse
Ahh okay, thx for letting me know
Edit: So i flashed it and at first it was very stable but then it crashed to that green apps watchdog bark, i then rebooted and it crashed and showed the purple secure watchdog bite screen a couple of seconds after unlocking the phone. not sure if this is relevant but when it crashed it was downloading about 40 apps, and i was trying to log into instagram. Maybe it was just a fluke, i'll see if it happens again
Edit2: So i rebooted and everything seems fine again
Edit3: okay so it crahsed again, same thing happened, it crashed to the green watchdog bark screen although this time it went from that screen to the purple watchdog bite screen without rebooting or anything. When it crashed, i went to unlock it and it froze while i was unlocking the phone
Could this have anything to do with the fact that my phone was originally a vs995? Cuz i converted it to a us996, I noticed that there was a vs995 pie kernel, should i flash that and see if the crashes stop? I'm not too sure if it would do anything especially since i was running alpha omega oreo with your us996 oreo kernel just fine but it's worth a shot but just to be sure, for now i'll reflash the us996 kernel again and see if the crashes return
update: It worked fine for the past hour but crashed to the watchdog bite screen again, i'll try flashing the vs995 pie kernel and see if the crashes stop. Okay so i successfully flashed it, now i just have to wait and see
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
xxseva44 said:
Ahh okay, thx for letting me know
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Click to expand...
Click to collapse
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
ezzony said:
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
Click to expand...
Click to collapse
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
TheRoyalDuke said:
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
Click to expand...
Click to collapse
You could try flashing the modem only. The pie modem, in twrp. I'd be curious to know what would happen. I have just uploaded it. Worth a try. The fingerprint for some reason uses files in the modem partition. Why there are there I don't know.
Be advised everyone all this mixing and matching pie with oreo may result in unforeseeable negatives. We can only know what works by trial and error. And, your welcome!
xxseva44 said:
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
Click to expand...
Click to collapse
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
ezzony said:
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
Click to expand...
Click to collapse
Yea i double checked, i flashed the us996 pie kernel twice actually, but had the same results
Okay so before i added anything, i tried to open the alexa app again, this time it worked fine and didn't cause my phone to crash, so this time i'm going to open a lot of apps and see if that will trigger the crash
Edit: nope, that did not cause it to crash either, i have no idea what's causing the crashes, maybe it has something to do with the cache because i remember when i tried rebooting after the second crash, it was stuck at the boot animation, it only rebooted after i cleared delvik and cache. Maybe the cache is getting corrupted after a while?
Update: Phone has been running fine for 1 day
Update2: Phone crashed this morning while scrolling to instagram, these crashes seem to be happening at random. Only thing the crashes have in common is that it would happen roughly every 20 hours to a day. Sometimes if i'm unlucky it just repeatedly crashes after a couple of reboots
Update3: Okay yea theres something funny going on with the cache because, i went to the gallery to look at some videos that i know would play but when i tried to play them it kept saying something went wrong, tried a reboot but still the same result. and when i'd watch videos on instagram they looked corrupted, tried force stopping and clearing the cache but still the same result. reboot didn't help either, only thing that fixed those issues was clearing the cache and delvik in twrp
Update: So i have found a temporary solution which is to clear the cache and delvik every once in a while
Idk if this is relevant but what did you come from before flashing this cuz i came from oreo so idk if that could have anything to do with the issue