Database Users

[Q] LG G2 d802 completely ruined...help!

Hi all, hope you can help me. I've tried searching on the internet but no-one seems to be having any problems like mine. and my phone is now near enough bricked.
So i bought a LG G2 D802 from aliexpress, all working fine but no 4g lte option for some reason. Had a look around and seems updating to stock europe rom would have sorted this so i thought id do this.
So Updated the rom using flashtool2014, downloaded lg usb drivers, the europe rom D80220D_00 and lgmobile support tool. Went through the process and it all ran fine with no errors completed 100%and then said done pressed exit and disconnected phone.
Now, switched phone on . Straight away touch completely messed up click on the screen and different parts keep of the screen keep clicking. Eventually after 15mins managed to get out of the startup where it asks for wifi settings etc so i could try to factory reset. No luck even out of startup have not yet managed to get to the screen for usb debugging yet due to random screen clicking (keeps opening other apps, screens).
I cannot rerun the flashtool as i cannot enable usb debugging or even switch away from charge only to pc softwarw and it just says phone not connected on the flashtool and keeps ending.
Switched off by holding power button for long time. Holding down the down button and power does nothing just keeps restarting when i eventually let go.
Also sim is in phone but it says service disabled?
Any ideas how i can fix the phone! All was working fine before I did the europe rom update
Thanks
Jon

You can connect a mouse via otg and navigate to usb debug
Sent from my SM-N910H using XDA Free mobile app

Maybe try factory reset and just use mobile support tool update stock rom?
Sent from my LG-D803 using XDA Free mobile app

I would just use a wireless keyboard with an otg cable like sugested before
Sent from my LG-D805 using XDA Free mobile app

I eventually managed to select lg software as connection mode and flashed to another firmware but exact same issue again.
After trying for ages and opening the wrong thing again and again i managed to get to the screen in settings to click 5 times to enable developer options however now the screen just freezes and then you get a message saying settings has stopped working and phone locks up. This has happened 3 times since. Doesnt seem like anyway to get it sorted if i cant enable usb debugging.
Also it seems to be that the firmware change has erased the imei and that is what is causing all these problems. I found one site that details how to restore but once again you need usb debugging enabled.

Droidview has the page where you have to backup and restore imei, i dont have a backup so will need method 2. If i can get usb debugging enabled that is!

JON-JAY said:
I eventually managed to select lg software as connection mode and flashed to another firmware but exact same issue again.
After trying for ages and opening the wrong thing again and again i managed to get to the screen in settings to click 5 times to enable developer options however now the screen just freezes and then you get a message saying settings has stopped working and phone locks up. This has happened 3 times since. Doesnt seem like anyway to get it sorted if i cant enable usb debugging.
Also it seems to be that the firmware change has erased the imei and that is what is causing all these problems. I found one site that details how to restore but once again you need usb debugging enabled.
Click to expand...
Click to collapse
Try using onscreen phone maybe you could manage to set that up and then enable usb debugging?
.::.LG G2 D803.::.
.::.CLOUDYFLEX 2.7.::.

thanks for all the help, lg on screen just didn't work for some reason wouldn't connect to the phone. Was thinking about a otg cable but after an hour of clicking again and again I managed to get the developer options and usb debugging enabled.
I went through the procedure at droidview to restore imei using qpst but after finding the com port it says no phone detected so theres nothing more I can do, looks like I just have to accept this brand new brick lol.
Anybody know anywhere in London that does repairs like this, I have tried a couple of shops in London Victoria near work but they couldn't do anything. Apparently theres something called an octoplus/octopus box that can fix LG G2 imei or flash firmware.
Thanks again for everyones suggestions. .

Jon-jay, I have the same issue. I tried the "easy" kdz flash and tot flash and basically bricked my phone. The phone turns on but the screen is calibrated incorrectly like you describe so I can't click anything without trying over and over. I click one area of the screen and another is activated. I can pull down the notification pane but can't click anything in there. The phone is in a boot loop too if I don't touch it. I also want to turn on USB debugging so I could try to restore with adb or fastboot. I will let you know if I find anything.

Yeah very tricky to fix this phone after flashing. Ive flashed loads of lg phones with the flash tool and never any problems until now. Ive currently sent to a shop in south wimbledon who quoted me £50-£80 for repair if he could fix it. I dropped it off on mon and still no response so im not holding my breath. It seems this phone will be going to the recyclers if he cant do anything.:crying:

JON-JAY said:
thanks for all the help, lg on screen just didn't work for some reason wouldn't connect to the phone. Was thinking about a otg cable but after an hour of clicking again and again I managed to get the developer options and usb debugging enabled.
I went through the procedure at droidview to restore imei using qpst but after finding the com port it says no phone detected so theres nothing more I can do, looks like I just have to accept this brand new brick lol.
Anybody know anywhere in London that does repairs like this, I have tried a couple of shops in London Victoria near work but they couldn't do anything. Apparently theres something called an octoplus/octopus box that can fix LG G2 imei or flash firmware.
Thanks again for everyones suggestions. .
Click to expand...
Click to collapse
Check out the thread lg g2 is unbrickable now, it involves shorting a couple capacitors to unbrick but its ingeneious. I bet itll help you out.
.::.LG G2 D803.::.
.::.CLOUDYFLEX 2.7.::.

the plot gets thicker...
okay so it has been a few months now and I revisited the phone sitting around. This is how I got on:
I gave the phone to shops in London, no-one could fix it got it back first week of Jan. So I thought I'd retry myself.
One guy told me that the imei may be for D802 but the screen and insides of the phone is a d800 model.
That makes sense as the touch works erratically. This was a refurbished phone I bought from aliexpress which claimed to be a EUR D802 but after I took the back cover off it says D800\d801\d803 inside on a lot of the flex connections and at the bottom of the plastic it says d800. I downloaded the AT&T stock rom and flashed with octoplus - touch worked perfectly! but phone kept restarting itself and looping really badly so I put in download mode and went back to D802 uk firmware - and touch not working again.
(Prior to this I bought the octopus box also in the hopes that restoring the imei I had previously lost will somehow be related to the screen.
This worked in restoring imei only and I have restored the d802 imei with octopus box)
Anyhow I then flashed stock uk firmware on the phone so everything in the phone works perfectly fine except the touch! so I am controlling touch with otg cable and mouse.
my next thought was install a d800 custom rom it will fix the touch! Now I then rooted, and installed d802 autorec.apk. I came on xda and downloaded a d800 stock custom rom (D80020k) from the AT&T subsection and thought I'd install this through twrp. All though the custom rom says successful when I reboot it comes to fastboot mode again. so I then go about restoring the stock d802 firmware. I installed d800 autorec.apk but that too send to fastboot mode.
So I am lost. Everything working perfect except the touch. Any ideas anyone? Im hoping some one says there is a stock lg custom rom that has all the screen settings for d800/01/02/03 which will sort my problem!
What it seems is the chinese company selling the refurb has somehow managed to get a d802 imei on a d800/01/03 not entirely sure how this is possible either!

JON-JAY said:
What it seems is the chinese company selling the refurb has somehow managed to get a d802 imei on a d800/01/03 not entirely sure how this is possible either!
Click to expand...
Click to collapse
What they're doing is flashing a d802 system.img with otherwise d800/01/03 firmware.

I saw a thread in the T-Mobile G2 area saying to get d802 on your d800/d801 you just flash a custom d802 rom and then a d800/801 kernel but this causes my phone to go back to fastboot...still lost! the custom rom works fine itself (Except for touch again!)

JON-JAY said:
I saw a thread in the T-Mobile G2 area saying to get d802 on your d800/d801 you just flash a custom d802 rom and then a d800/801 kernel but this causes my phone to go back to fastboot...still lost! the custom rom works fine itself (Except for touch again!)
Click to expand...
Click to collapse
There is a way to get them back to their original frankenphone state but it's quite a procedure. Flash d802 firmware. Use a otg usb mouse to navigate since it'll have touch issues. Root and install custom recovery using the actual hardware as your guide to which twrp version to install. D800 in your case. Do a nandroid backup. Move the nand backup to your pc for safe keeping. Now install d800 firmware using a hex edited tot to allow it to proceed and a generic dll to avoid cross dll issue. Root, install twrp again. Move twrp backup from pc to phone. Do a restore but only restore the system.img. Now you have firmware that cooperates with d800 hardware while appearing and acting like a d802 in every other way.
The other thought I had but have not tested yet would be to flash d800 firmware right off the bat, then root and install twrp. Then use dd to flash system.img to it's partition ( /dev/block/mmcblk0p34 ). I'm not sure how that would work due to the very large size of the system image. You'd have to extract it from the kdz. Because it's so large when it's extracted, it does it in parts so it must be merged back together to make one file. But if it did work, it'd save the step of having to root/recovery twice on two separate firmwares.

[Q] I messed up. Followed instructions but still cannot fix my phone.

Hey guys. I know for sure there is another thread about a similar problem but the biggest problem I'm having is figuring out what to do next, or better yet, what did I even mess up?
I made a thread a couple days ago here asking about the LTE option on my phone and how there was none. It's an Intl' phone and therefore I guess doesn't work on Canadian LTE networks.
Before we start, I'm using TWRP 2.7.0.0 . My phone is the UAE version of the D802, which is the D80220C. My current custom rom is Liquidsmooth MS3.2 .
So I found a list of modems and flashed the one for Bell. It was for the D803, but the thread I was looking at said it was cross-compatible so I assumed that meant it's okay for me to flash it on my phone.
Even so, I backed up my EFS partitions just to be 100% sure. I even used the .zip file that automatically backs up the current modem files. So I thought there was definitely a way out if it didn't work.
I will give you the full story of what was done and maybe I can get some guidance on maybe something I did wrong.
1) I flashed the D803 Bell modem.
2) Reboot to system, LS3.2 hangs on start up. Tried a hard restart to see if it wasn't a fluke. Nothing. Still hanging.
3) Figured the EFS files were toast, so I ran the restore .zip for my EFS. Reboot, and still hanging.
4) Said WTF? and restored my first stable rooted stock rom. It booted into the rom fine, but when it got to the lock screen I saw the "Service Disabled" and the phone quickly crashed.
5) Didn't even attempt to restart on that rom. So I tried a couple terminal commands to copy the modems1.img and modemst2.img files to corresponding partitions. Copied both just fine, but no change. Still screwing up.
So, this is where I am so far. I am in the process of downloading the D80220C UAE .kdz file so I can try to flash that one first. If that doesn't work, I'm really at a loss.
When I read into this some more, all I see is people who have totally wiped their EFS files and having to spend a whole bunch of time using a bunch of different programs to get in an recover the IMEI number.
What do you guys think?

Some good news right off the bat. I found a KK baseband for D802 and flashed it. So now I was able to restore my LS3.2 rom and boot into it fine. I see my IMEI and MAC address and can get WiFi at last!
Mods, you can delete this thread if you wish.

LG V20 H910 Rom issues

For some reason I can't post when I use the model number listed in the title and the Canada variant model name. Says the post is "flagged". So that's why I'm not using the model numbers.
Hi. So last week I got a new V20....and I bricked it...within 3 hours. I'm hoping someone can help me out. So, here's what happened. I'm sure this subject has been posted 1000 times, but nothing I've read is exactly like my situation.
I bought a AT&T Model. I didn't realize how complex it was to root it. Was very easy on my D855. First I made a backup of all partitions with LGUP. Which is useless, since it's, not a kdz. I tried to unlock the bootloader with Dirtysanta. I got the static. I reflashed it with the stock Canada variant kdz. It booted just fine, but had no service. Dirtysanta also resulted in static with Canada variant rom. Reflashed Canada variant again. This time using one of the LG tools I tried merging the AT&T Model modem into a kdz file, hoping it would get a cell signal again. This failed spectacularly, because LGUP said it wasn't a valid kdz. (I'm guessing kdzs are signed and LGUP verifies them? Don't know. This stuff is clearly new to me.) Anyway, at this point I tried the dirtysanta method one more time. Got stuck with a bootloop about "corrupt device" and the red triangle. Finally managed to get download mode to work again. Flashed it with stock US996 v10f. Now it's impossible to go back to Canada variant kdz, and there is still no AT&T Model kdz. So it looks like my once AT&T Model is now stuck as a US996. Which, I guess is ok with me. Mainly I just wanted to get rid of the AT&T crapware. But, of course the FM Radio doesn't work now. Also, dirtysanta also gives static with US996 rom. Most people said if you turn the screen off and back on, the static goes away. But for me, the buttons don't. Phone doesn't show up in ADB, Windows explorer or device manager. But it's fully booting, because through the static I can see the "Welcome" screen. Now, if I'm understanding this right, the FM Radio doesn't work in the US996 version because of the kernel. And boot partiton = kernel? So using LGUP with PARTITON DL, I flashed just the boot partiton from the Canada variant kdz. Got to the second "LG" screen and doesn't boot past that. So, I flashed the correct boot partition back and it once again booted. So, fianlly to what I'm asking. Is there anyway to get:
1. TWRP recovery
2. Rooted US996 rom
3. The static to go away...and go away permanently
4. FM Radio working (there was talk about custom kernel?, but haven't gotten that far since I can't get the static to stop)
5. Red triangle error to go away
Last issue isn't that big of a deal, but just wondering if anyone has a fix for this yet. Help would greatly be appreciated. Thanks.

popit12 said:
For some reason I can't post when I use the model number listed in the title and the Canada variant model name. Says the post is "flagged". So that's why I'm not using the model numbers.
Hi. So last week I got a new V20....and I bricked it...within 3 hours. I'm hoping someone can help me out. So, here's what happened. I'm sure this subject has been posted 1000 times, but nothing I've read is exactly like my situation.
I bought a AT&T Model. I didn't realize how complex it was to root it. Was very easy on my D855. First I made a backup of all partitions with LGUP. Which is useless, since it's, not a kdz. I tried to unlock the bootloader with Dirtysanta. I got the static. I reflashed it with the stock Canada variant kdz. It booted just fine, but had no service. Dirtysanta also resulted in static with Canada variant rom. Reflashed Canada variant again. This time using one of the LG tools I tried merging the AT&T Model modem into a kdz file, hoping it would get a cell signal again. This failed spectacularly, because LGUP said it wasn't a valid kdz. (I'm guessing kdzs are signed and LGUP verifies them? Don't know. This stuff is clearly new to me.) Anyway, at this point I tried the dirtysanta method one more time. Got stuck with a bootloop about "corrupt device" and the red triangle. Finally managed to get download mode to work again. Flashed it with stock US996 v10f. Now it's impossible to go back to Canada variant kdz, and there is still no AT&T Model kdz. So it looks like my once AT&T Model is now stuck as a US996. Which, I guess is ok with me. Mainly I just wanted to get rid of the AT&T crapware. But, of course the FM Radio doesn't work now. Also, dirtysanta also gives static with US996 rom. Most people said if you turn the screen off and back on, the static goes away. But for me, the buttons don't. Phone doesn't show up in ADB, Windows explorer or device manager. But it's fully booting, because through the static I can see the "Welcome" screen. Now, if I'm understanding this right, the FM Radio doesn't work in the US996 version because of the kernel. And boot partiton = kernel? So using LGUP with PARTITON DL, I flashed just the boot partiton from the Canada variant kdz. Got to the second "LG" screen and doesn't boot past that. So, I flashed the correct boot partition back and it once again booted. So, fianlly to what I'm asking. Is there anyway to get:
1. TWRP recovery
2. Rooted US996 rom
3. The static to go away...and go away permanently
4. FM Radio working (there was talk about custom kernel?, but haven't gotten that far since I can't get the static to stop)
5. Red triangle error to go away
Last issue isn't that big of a deal, but just wondering if anyone has a fix for this yet. Help would greatly be appreciated. Thanks.
Click to expand...
Click to collapse
Static after engineering boot is fine. It boots up after a minute of wait on static screen. Also that triangle mark screen is fine too, wait for a minute which u didn't.
You should have followed brian's guide to root an H910.....
[ROOT] HOWTO: AT&T H910 up to v10v (FULLY TESTED)
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Even I was able to root using this method on my Puerto Rican v20 H910PR

Thank you. I finally realized what I was doing wrong. I was skipping the step on installing H915 kdz FIRST. Guess it helps to actually follow all the instructions! Anyway, I got it working. I was even able to completely get rid of static boot with MegaRom & the mk2000 kernel. FM Radio works, too!

U System firmware on BLv5/6 Phone

1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!

Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks

Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.

Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.

lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself

elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.

lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.

elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?

lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.

It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.

lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then

sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.

Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.

LG V20 H910 No Mobile Data, Calling & Kernel crash [4G, notifications solved] + Headphones not working

Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.

I was going to follow the instructions in this post and install the F800K10e.kdz but the lg-firmwares.com website is limiting me to 2 files per 24h so I decided to give the H91510e_00_VTR_CA_OP_1205.kdz another go. It wouldn't boot again until I formatted the data, it seems to be working so far.
I'm sure this is some noobie knowledge but most posts/guides didn't say to do that and I am indeed a beginner. I will update this thread with information on what I do next if relevant and if I can get my mobile data working somehow.
Edit : SMS work, 4G works but the sim card crashes when I call or get called.
Unfortunately I didn't even try my sim card when I got the phone so maybe it was the same onthe H91010l. Looks like I'll have to redo the unlocking procedure and continue fixing this mess.
Edit 2 : Notifications don't work properly either like on the custom roms... For example skype messages.

Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.

Darnrain1 said:
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Click to expand...
Click to collapse
I didn't flash any kdz to root initially. I just started flashing stuff once I lost my bootloader and TWRP. I managed to have the H91510e working that's where I'm at currently as per the second post. I will try and root it again following this procedure soon. I have to look into why I can't call or get called first. We'll see what happens, but according to this thread I will lose mobile network when I root the H915 version. I'll see when I get there.

Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.

Darnrain1 said:
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Click to expand...
Click to collapse
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Edit : I just installed the h91010r with having wiped + formatted before and formatted after, it still goes into secure boot...

Xanvast said:
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Click to expand...
Click to collapse
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.

Darnrain1 said:
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Click to expand...
Click to collapse
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !

Xanvast said:
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Click to expand...
Click to collapse
Yes your data partition is encrypted still. You need to format it in twrp.

Darnrain1 said:
Yes your data partition is encrypted still. You need to format it in twrp.
Click to expand...
Click to collapse
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.

Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.

Darnrain1 said:
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Click to expand...
Click to collapse
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.

Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.

Darnrain1 said:
It's complicated,
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.

Xanvast said:
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Click to expand...
Click to collapse
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot

Darnrain1 said:
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Click to expand...
Click to collapse
Unfortunately as stated in my first post, I have no backup of the state of the phone when I got it as a H91010l. I didn't do one either while on the H91510e because I didn't see the point, it was already modified and calling didn't work.
Thank you for the explanation.
Something I'd like to mention for other readers is that there is one main visible difference between the first root (from H91010l with the old guide) and second one (H91510e with newer guide). The first time the warning message with the red triangle during boot was very distorted and duplicated. It was unreadable. Now it is clear. I don't know enough to say what was causing it or point at what made 4G work in the second case but this was something worth noting.

Alright, going into this de-Googling trip I did not know that many apps relied on Google Play Services to work and the Google cloud services, Firebase cloud etc... to send their notifications. I had no idea that Google was managing the notifications for most of the world and so much more. That only reinforces my desire to get away from it.
So these apps like Discord, Skype and others that don't send notifications it's directly because of the lack of Google Play Services. I noticed today that MicroG has a Cloud Messaging option but I will not enable it.
Signal works fine without any of it. I also found Skype Lite to send notifications so that's what I'll use from now on. Discord is going into the trash. I've read that Telegram is supposed to work too. So another problem solved. I have no issues making concessions on my convenience to be freer.
A website I came across which references how apps behave without Google : https://plexus.techlore.tech/

Darnrain1 said:
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.

Xanvast said:
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Click to expand...
Click to collapse
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20

Darnrain1 said:
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Click to expand...
Click to collapse
Yes the post is in that thread. I didn't have this problem the first time I used LOS 3 weeks ago so I assume it has to do with the green screen crash caused by the kernel I didn't flash after the h910-10r.rar. So it's still unaddressed in my opinion. Should I go ahead and flash that missing kernel or the H915 modem ? I don't know what's the difference and both seem plausible.
It's fine if you aren't sure and I will end up asking there.