Database Users

No OTA updates after restore to Stock Firmware

Hey all,
Having a small issue with my Verizon LG G2.
When I first got it on launch, I rooted it, installed loki (to bypass the locked boot loader) and have been running custom ROMs.
This is the way I ahve been running it since, on 12B, with loki and CM11.
Before I installed custom roms I did a image backup using Clockwork.
Yesterday I bought a Droid Turbo, so it was time to restore the G2 in preparation for sale.
I attempted to restore my original backup of the stock image, but it failed (stating something about an inability to restore/system, resulting in a soft bricked phone.
I fixed this by downloading the LG Flash tool, and the stock 24A .kdz image, putting the phone in download mode and flashing it.
The LG flash tool seemed a bit buggy, complaining about not finding servers, but eventually flashed the phone with the .kdz.
Everything seems to have worked well. Root is gone, clockwork is gone, (and I assume loki is gone as well, but I can't tell) but now I can not do the latest OTA updates, and am stuck on 24A.
It's not that it downloads the OTA, and then fails to install it, but rather it complains that it is unable to download the updates at all.
I was thinking this might have something to do with the fact that the CDMA radio is now unactivated (since I got a new phone) and it somehow needs to verify with the Verizon network prior to downloading, so I grabbed a working SIM and popped it it in. Even with 4G via the SIM, the OTA downloads don't succeed.
Does the CDMA radio need to be activated in order for a phone to receive OTA updates? If not, I ahve something else wrong going on, and would appreciate any suggestions regarding fixing it.
The plan was to sell the LG G2 to pay for my Droid Turbo upgrade, but I don't want to sell the phone to someone if I think it may be having issues.
I would appreciate any thoughts and suggestions from you guys!

H910 Second Attempt at rooting and flashing help appreciated

Hey folks,
So I'm on my second H910 now, I went into the first one all confident and what not having done this sort of thing before on old Samsung Galaxy phones, only to learn that LG is a whole different sort of beast.
I followed this guide https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 and managed to kill the modem. I didn't do a backup (this time I will) and I just have a few questions before I start the process this time around. This Ebay seller has no returns so this is do or die (or lose a couple hundred bucks rather).
I believe the problem was, besides not having done a backup in LGUP, my first H910 had the H91010L software version, I upgraded my new H910 to the H91010t version, but I'm not sure if I should keep going or not. Am I safe to follow this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 with H91010t?
I then plan on flashing the version of TWRP in this thread https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 and flashing the Alpha Omega rom 1.1.8 https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510.
Should I be fine doing this after following the guide in my first question above or should I expect to lose my modem or any other issues?
Lastly, if I run into issues with celluar service again and try going back to stock with my LGUP backup, will that restore my modem/service or is the actual hardware fried? I've tried restoring the modem with fastboot and files downloaded on this website and reddit and didn't manage to fix the first phone.
Thank you for any help and feedback!
Edit: I stayed at 10t, went ahead with everything as planned and everything went smoothly, enjoying my new V20.

So how badly i bricked LG V20 LS997?

I got LS997 that was not completely unlocked (Sprint support confirms unlock status but phone did not receive unlock command, and i got no sim card and no previous owners name to re-initiate ota-unlocking process)
First thing i did - i used pathed LGUP and dirtysanta rooted my phone.
Suggested 995 kdz rom was vibrating like crazy (as described in dirtysanta guide) but i got root and started experimenting further.
Than i flashed rootable 996 kdz, rooted, had no vibration problem but got static boot issue, ok, installed mk2000 kernel, no static - all good but still not enough.
LOS16 = gsm/lte unlocked but battery was drained in 5 hours with screen turned off and no camera, got back to 996, rooted, super rom, all good but LTE not operating for some reason. Really enjoyed stock functionality (camera, seconds screen) and decided to get back to stock system.
HOWTO: Root LS997 up to ZV7, did it all, started flashing available 'stockish' roms one by one [this, and this], so there goes bad stuff.
At this moment i was still being able to boot into twrp, so i didn't really notice that phone was bricked, those stockish systems was just hanging in LG logo for hours without any progress. ok, found another one stock ls997 rom in dirtysanta root post, flashed it - and nothing, phone still stuck at lg logo.
LGUP flashing routine that was always helping me recover, now if fully completes partition_dl process but results are the same - lg logo for hours without anything happening, except vibrator motor starting to work on power up on Verizon firmware version and no vibro on 996 variant (as it sould):
996 kdz - stuck on logo
996 kdz- stuck on logo
flashing everything i got from lg-firmwares.com:
US99610g_00_1216 - stuck on logo
US99610f_00_1205 - stuck on logo
US99620f_00_1120 android 8.0 - stuck on logo
VS99512A_06_1114_ARB00 - stuck on logo
download couple more variants and still nothing, phone stucking in lg logo
so how badly i bricked it? is there any method of recovering that i am not aware of?

There is an older thread on returning the LS997 back to stock that may help.

C D said:
There is an older thread on returning the LS997 back to stock that may help.
Click to expand...
Click to collapse
Yeah, thanks, been there.
Unfortunately i'm not meeting 2 of 3 prerequisites:
- Your device needs to be able to boot into TWRP and fastboot mode
- You need access to a computer to run ADB commands to the phone
There are no more twrp presents on device because of kdz uploads from LGUP, i was thinking that it was recovery and aboot partitions that was messing up my system.
And there is no bootable system on device to turn on usb debbuging to run ADB commands as only thing i get is boot logo, fastboot are also locked to 995 or 996 (whatever version i've uploaded last from LGUP, and they are not unlockable because LG recognizes original LS997 hardware identification and refuses to give me unlock.img.
As i get it - the only thing that can tinker with my device is something that can get same hardware access as LGUP (laf is still operational or idk, maybe not, but it should be getting everything up and running but that is not the case anymore for some reason)

So you are saying that LGUP can still see the phone but ADB can't. Did you by any chance do a full system dump of the phone on LGUP before the whole DirtySanta procedure in the beginning? I wonder if those files can help getting things back on track. Not sure if they are device-specific, but I did make a dump of my own LS997, so if you think there's something useful there, let me know, and I can upload the files somewhere.

C D said:
So you are saying that LGUP can still see the phone but ADB can't. Did you by any chance do a full system dump of the phone on LGUP before the whole DirtySanta procedure in the beginning? I wonder if those files can help getting things back on track. Not sure if they are device-specific, but I did make a dump of my own LS997, so if you think there's something useful there, let me know, and I can upload the files somewhere.
Click to expand...
Click to collapse
Yes i did full LGUP backup at first system state, but nature of this backups makes them pretty useless in this system state - because they are just images of partitions.
Only software that can write directly to those partition may be able to utilize those backups, there are a lot of post on this forum describing TWRP routine for making update packages based on LGUP backups.
So unfortunately there is only LGUP, but it only can make backups but can not restore them as it uses some special file format (KDZ) that containing some dll's and data files (like glued partition images with special info of where to put what) and i didn't find a way to make my own KDZ files from backup images.
I'm now getting another idea - that this can be a blowed fuse in CPU ARB protection mechanism, if anyone has experienced ARB 1 please confirm that system should be in this state in case of ARB error

Did I just brick my device trying to root?

Hello, I really messed this up... I haven't rooted a phone in over 5 years, but just ordered a moto g7 from google fi because I wanted to play around with rooting and rooted apps again.
Setup:
-got moto drivers, adb, set developer mode, unlocked bootloader
I had tried to just root using the "simple?" method of using Magisk with the lolinet firmware files. I used the PPO files in the Official/FI dir. I thought that I had seen an error when flashing the magisk modified boot.img that there was an issue or that it wasn't valid, I (stupidly) assumed that this was like the notification you get after unlocking bootloader about invalid key or whatever. When trying to boot up it would just keep boot looping, and I went into hard panic mode... I saw other people had mentioned using retail or retus firmware on the google fi variant, so I proceeded to try to just flash those stock boot.img files after the fi one hadn't worked. I then finally got it to boot up fully, I don't even remember which firmware it was (retail maybe) and felt a little bit better about it, but had also seen that some people had said it wouldn't have the full functionality of network switching if I wasn't using the fi firmware. So... back to the fi firmware...
I was able to get it booting up on stock fi firmware, and to be honest I should have stopped there and given up on root, because I'm guessing I would have been perfectly fine up to that point... I again tried magisk modified fi firmware to no avail, and was having trouble getting back on stock fi for some reason... I followed a post to reset to stock and relock bootloader ***I'm guessing this was my major fault***, I must not have been paying enough attention to the command prompts doing this, but I think this is where I messed something up royally. It was able to boot, but then it said it had updated software to the 'PPOS' variant which I thought was strange... After attempting to reflash stock fi and then magisk fi boot.img it is failing and won't even get to boot loop.... when trying the slew of commands to flash full stock firmware I keep getting issues with the "_a" partition being not found.
At this point I can't get to recovery, or boot after attempting to flash a number of times. Any help would be appreciated, even if it is just a confirmation that I f'd this device and to stop wasting my time and give up on ever having a rooted device again lol.
Thanks for your time, and let me know if there is additional info to provide that may help.
Edit: Current status:
"Start Up Failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the software Repair Assistant."
in Bootloader logs, but I don't know what software repair assistant it is referring to, i have tried connecting to pc.
Edit 2: Or I'm just a complete idiot and needed to re-unlock bootloader with the code like previous... which I totally should have known, but again, I'm an idiot...
So, now that I've got it booting up, do I attempt reflashing a magisk img or just admit I'm too stupid to do this? Or should I go with twrp which seemed like more steps and potentially more issues to run into?
Sorry for the scare and immense stupidity!

Trouble flashing stock kdz

I have an H872 on Havoc 4.4. I have upgraded to a Pixel and will be giving the H872 to my father-in-law. He will only be using it for phone calls - very unlikely he will text, and definitely won't use data. It will also be his first smart phone. Since the H872 is rooted, when it boots up it gives the warning display that the phone may be "Corrupted". I don't want to have to explain all that "root" stuff to him, etc... I want the phone as basic and simple as can be, hence , I want to reflash the stock firmware.
I am having troubles though. Booting the phone into download mode and starting LGUP fails to recognize the phone. I've tried with Uppercut as well and it says I'm missing a file in Apps/Roaming, etc...
Not sure the problem because I have reflashed stock many times with LGUP. Could it be that Havoc has changed the "identity" of the phone, or that it's on Android 11?
Any help to get this back to stock is much appreciated!

Got it figured out. Flashed back to an older TWRP (was on Orange Fox), flashed an old stock Oreo ROM, and then was able to flash kdz with LGUP.