Develop Bugs

[Q] Please help a Noob

OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.

Drivers
landran said:
OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.
Click to expand...
Click to collapse
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.

TheMighyLoki said:
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.
Click to expand...
Click to collapse
Yes I have. I think I did figure it out though. I put the device into "download mode" and my computer could see, and communicate, the phone.
To put my phone into "download mode" I did the following:
I connected the phone to the computer physically with USB cable
I turned phone off.
I pressed BOTH volume buttons and held the power button while phone was attached to computer.
With BOTH volume buttons still pressed, I released the power button.
The phone screen was black with a little dialog box in the middle saying "download mode"
I could then use LGFlash Tools to flash Stock AT&T TOT file back into phone. Took 519 seconds to complete the stock flash.
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.

landran said:
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.
Click to expand...
Click to collapse
It sound like you need to manually set the APN. Do a Search for your provider.. ie AT&T T-Mobile the setting is under Network/Tethering & Networks/ Mobile networks/ Access point name/ Hit Menu Button and New APN

You are the MAN / WOMAN!! Thanks for the help. That fixed it.
For posterity and to help another "noob" stuck in my case later (maybe months down the line)
This is what I've done up until now in plain text:
Used LGFlashtool to flash AT&T stock "10k" build
Went into Settings Icon>General>Developer Options>check off "USB Debugging"
Used "E980 Universal Root" from forums to gain Root access (verified with "Root Checker" from Playstore)
Used FreeGee to get TWRP recovery installed (rebooted into recovery with "QuickReboot" from Playstore).
Used TWRP recovery to install "E980 Baseband.zip" from forums
Factory Reset
Setup new phone and input APN settings (located in Settings Icon>Networks>Tethering & Networks>Mobile networks>Access point names>Menu button "New APN"/input carrier values/Menu button "Save")
Now that I know how to get back here, I'm going to scrap the stock ROM and try to do this whole process with a custom ROM. . . and another flash-a-holic is born. The learning journey continues.

Welcome:beer:
*KCCO*2SHAYNEZ*E980*

That is what this forum is for.
I have been helped out a lot from the group and I just thought it was time to pay it back. It is good to hear that you got it up and running. But one last word of advise BACK UP, BACK UP, BACK UP, and when that is done, back up the back up to the computer.

[Q] Unsure if my LG G3 is fixable, please say it is

Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.

xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.

epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.

I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.

Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.

Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone

Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!

Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.

xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?

epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.

[Solved] Galaxy S III led won't stop flashing

I installed the latest Lineage 14.1 last night on my S3 and the LED slowly flashes blue as it boots up but doesn't stop once the boot is finished. If I plug into the micro usb for a moment it stops but every time I reboot I have to do it again. Am I missing something?
Great work BTW my old S3 has never run so well.:good:

I assume you have the official build installed?
https://forum.xda-developers.com/showthread.php?t=3544531
Sent from my XT1650-03 using Tapatalk

Thanks for the reply... this is literally my very first ever try at rooting a phone or installing a ROM so I fully admit I'm not really sure what I'm doing.
I downloaded the latest rom from here....
lineage-14.1-20170306-nightly-d2att-signed.zip
used this version of TWRP (3.1.0.0)
dl.twrp.me/d2can/
used SuperSU 2.74
download.chainfire.eu/964/SuperSU/
used this method to install
lineageosrom.org/install-lineageos-twrp/
It took me 3 tries to get gapps to install because I was using the largest packages and they were too big for the partition so ended up installing 'pico'
I have a Canadian i747m Galaxy S3 so I went into build.prop with an editor and changed 2 entries from d2can to d2att and then installed the rom. Seems like everything was fine initially but I tried to plug it into my PC and access the phones file folder through Windows (which didn't work). After that I started to notice the LED wasn't stopping after bootup. Now if I plug into the PC for 1 second the light goes from flashing blue to solid green with a bit of orange. Remove the micro USB and the light goes off until I reboot again. I've also noticed that there is no red charge light when I'm charging with the phone off and email notifications flash red instead of blue.
Again totally new to all this so not really sure what's up. Everything seems to work well other than that. I also have some random date/time issues but nothing that stops me from using the phone.
PS. I can't post links yet so I edited them down

You don't need SuperSU. They provide a open source package themself here.
https://forum.xda-developers.com/showthread.php?t=3545275
And BTW, try asking in the S3 thread that I posted.
Tried a quick search for your version but could not find a own tread for it. They probably have more info and experience from that specific phone.
If it has some similarities to mine (Moto Z) go to settings and search for "light" (mine activated a kind of led despite stock firmware never used it). Most settings related to the led should be found. Try to disable some and see if something solves it or at least disable the led as a temp solution.
Sent from my XT1650-03 using Tapatalk

I tried multiple way/times to install the SUaddon without success but thanks for the info.... I ended up using SuperSU since I had previous success with it.
Solved the LED issue by doing a clean install with the newest nightly release.
Thanks for the info on LED settings... I found them in my phone and OMG there are a bunch.

Samsung note 10+ 5g not booting after firmware update

Hi,
I have applied firware update for years without problems but today I am stumped.
I tried to update todate from 6ETLL firmware to the newer 6FUBD both Android 11.
Set up Odin using 3.14.4 and started ok.
Then I had the install stopping and disconnecing to the phone.
Eventually I disconnected the phone lead and it now wont boot passed the error message -
An error has occurred while updating the device software.
Use the Emmergency recovery function in the Smart Switch PC software.
So I installed this on my pc it it fails to recognise the phone even in Emmergency recovery mode.
I have tried all methods of trying to reboot the phone but it always comes back to the above arror message and wont go into recover mode or download mode.
I did not but this from O2 but directly from Samsund and its just out of warrantee.
I dont know wheer the service center is in the Uk and thats a lst resort anyway.
Any suggestions please.

Repaste from my other reply on the UI3 update :
"
Odin hates thunderbolt - If you plan on using a USB-C port make sure it's not thunderbolt. It will fail half way in and freeze. Get a well rated cable and do it via USB concentrator directly
If you get stuck and you cannot access recovery via key combo or smartswitch emergency recovery use Odin
Open options and select get device info - It will reboot directly to the recovery if it was previously written (check the log). After that disable the get device info option and reconnect the cable (select files for flashing again - should go smoothly.
If after the reboot and setup you get a moisture warning on the USB port - this does not make nay sense but it works - Turn off the Note, plug in a usb cable on the PC and reboot the phone connected to the cable - It will reset the sensor warning and should work flawlessly.
Hope to have helped - Had a bit of a jarring adventure setting this one up this time.
The lag in the animation is there, however, I think it's the animation timer that is set higher (slower) it's not slow "per se" but it shows. "

Bomm,
I must say.... I dont know how to thank you. Your post saved my Note 10.
I emailed Samsung repair and after 2 days they said phone xxxxx if you need it repaired under warrantee.
I waited a week for the phone to lose its battery and when booted back on charge cane up with the same error.
So I went back on xda and you had kindly posted the exact fix I needed. I didn't expect that. I know now if I have the same issue again. It was my pc I think using usb-c to usb-c like you said. Thank you so much.

I didn't get any warnings at all. booted up fine.

Johny1fin said:
I didn't get any warnings at all. booted up fine.
Click to expand...
Click to collapse
had the same issue. I was stumped at first too

I've tried all the posts but when I say start in odin, the phone restarts and gives an error

As you say you are super, my friend, I applied it step by step, the phone entered the download mode.

Not sure why you want Q or above on the 10+.
I'm still running on Pie/One UI. Fast, very stable and zero issues. Last reload was back in June.
If the OS is running well and fulfilling its mission let sleeping dogs lie.

One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.

Johny1fin said:
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Click to expand...
Click to collapse
No problem here. All my PCs, their XPx64/W7 OSs as well as my Androids Kitkat/Pie OSs are now unsupported.
No issues and all continue to fulfill their missions.
Forced learning curves waste my time and offer little in return. My last learning curves were from Kitkat to Pie and XPx64 to W7.
I stopped updating with the best versions of both MS and Android. I don't rat's arse if it stays like that for the next 10 years... or if my Windows machines mutate into Pie or Linux machines
Whatever works best for me.

It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.

Johny1fin said:
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Click to expand...
Click to collapse
I've never had a malware or virus issue that required a factory reset in over 7 years of using Android. More than half of the time was using out of date OS's. My current Pie OS is over a year out of date.
99% of rootkits, viruses etc are uploaded by the user. There's no protecting the stupid.
I have redundant complete backups so a factory reset will cost me normally 2 hours and at worst case 6-8 hours if I need to restore the SD card.
You waste far more time then this fighting with the bugs, the learning curve and the forced factory reset that a major firmware update requires.
I get to use the OS of my choice... you get whatever they throw at you and the ride that comes with it.

LG G4 Bricked? Attempt to install alternate Mobile OS

Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock

Lilrock said:
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Click to expand...
Click to collapse
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.

steadfasterX said:
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
Click to expand...
Click to collapse
Thanks for the positive feedback, I will attempt to fix my phone with your solution. This phone is technically almost garbage and when I fully update the phone, it runs like trash. So, if I can install a custom ROM, it may run a little better or have the tools I would personally like in a phone.
I'll let you know the details of my attempt,
Lilrock

You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.

SkewedZeppelin said:
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
Click to expand...
Click to collapse
Which is included in mAid (https://maid.binbash.rocks).. ... Even with a UI...

Thank you very much with your support. I was able to unlock, bootloader and install the image installer.
I'm on the verge of compiling and installing Ubuntu Touch on my LG G4 H812.
Hope you guys proceed with everything you're doing right!