I got my LG V20 from sprint and I am trying to flash stock ZV7 off me2151's AndroidFileHost page. I've been using exclusively LS997 roms since I've had this phone but upon trying to install this rom it says "This package is for "elsa,ls997" devces; this is a "us996"
This doesn't make any sense. The only difference is I just got my phone back from repairs. The camera physically broke so I went to sprint and they said they had to send it in and that "the phone would be completely wiped." The phone came back in the same exact condition, rooted, custom ROM. Everything was still on my device. So I don't know what the deal is or if they actually changed something and I just don't know it.
Related
The perfect storm...
I broke my phone about a month ago, bought a hold over on craigslist until I fixed my phone. Left the phone stock and yesterday sold it to a truck driver via craigslsit. I did a factory reset handed over all good to go. He is now out of town
This morning he calls me and says the phone is locked in TWRP and is politely upset. Confirmed the phone worked when I gave it to him. I did not install or root this phone so the crap ass before me must have and did it and not mention it. The guy has no clue what happened, went to bed fine, woke up and stuck looping in recovery.
I tried to walk him through it. Reboot, says it lands right back at TWRP. He seems up to the idea of using a tool or utility to flash it.
I found this thread [Guide] Unroot/Unbrick - flash official factory firmware with LG Mobile Support Tool but it does not seem to cover the Verizon variant.
Can anyone point me to some instructions I can send this guy on getting this thing back to stock?
Hi guys, I got my LG G2 a few months ago and it was my first android phone. Since I always jailbroke my apple devices I decided to root my lg g2. Everything worked fine until last week when I was prompted to install a software update. I thought this might mess up the phone since it was rooted so I postponed it until later in the day to give me time to research, but I forgot to postpone the update again and it went through at the scheduled time. Now when I turn my phone on, the lg logo is displayed, and then I get a boot certification verify error. I don't really know what that means but I can't do anything, no recovery, no download mode. I started to follow this tutorial but am stuck at what files to download. I do not know if I have the 10b, 11a, or 12b variant, and I can't find a way to check it without turning the phone on, which I can't do. I'm really lost at what to do at this point, I can't follow the only guide that might fix my phone. Is there another way to solve this issue or find which variant I have? Would verizon accept it back to fix or replace it since it's been rooted? I've read some people saying they unrooted their phone and then returned it to the carrier, is it possible to do that in my situation? I really need some help guys.
TBH: I would call Verizon, and tell them the phone was bricked by the update- hope they don't notice it was rooted when they warranty it. Problem is, if they do you get charged full amount for phone. I'd consider if you have insurance to just claim it on insurance.
try download lg support tool from lg website http://www.lg.com/uk/support/software-manuals
plug the device and wait for the software to recognize ur version.
I downloaded and installed it, but it won't recognize by phone. I have installed the drivers for it
ok.
try to follow this guide http://forum.xda-developers.com/showthread.php?t=2681089
and the files download from here:http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware/10B_Partitions
lets try this virsion and see what happend..
download the 10B zip file and the dll file too http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware
now it doesn't boot at all, not even to the lg logo. Additionally the partitions don't show up in ubuntu any more. I guess i'm completely screwed now?
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!
hello, so it all began with the lollipop update, i wanted it on my new phone (less than a week old), so i've read everything i can about flashing the G2, and i guess i did nothing wrong (i used normal flash instead of CSE the first time), but i didn't back up my original ROM and that's the problem, so the KDZ installed normally, but when tried to configure the phone, the touchscreen went crazy , exactely like this https://www.youtube.com/watch?v=hYwumfkokOA. so i downloaded a 4.4.2 kitkat rom, but it didn't correct the problem, i used an OTG and a mouse to use the phone, and i found out that my IMEI is "null", and there is no signal at all, plus the phone heats up and the battery drains really fast, and some apps like the browser freeze when i open them, i tried at least 5 roms, and they all have the very same problems.
then i tought maybe my phone isn't a d802, so i checked my IMEI on every IMEI check website, and they all told me it's a D802, but when i removed the back cover, i found "D800 0815" written under some sticker, and i'm afraid that i'll brick my phone if i try the stock d800 firmware, and it's android 4.2 while my original firmware was 4.4.2, i even took my phone to a repair shop but no luck, i'm really confused and can't replace or buy another phone, all my savings went into this one, and this forum is the only place that can help me, so please, if anyone has a solution help me
TL;DR: my touchscreen went crazy and my IMEI says "null" after i tried a lollipop update on my LG G2 D802
Where did you got your phone from?
There are a lot of shops selling refubished D800 or D801 as D802. They replace the Model number in build.prop which is a simple trick. Then you get flashing errors and other crazy errors.
During the process of unrooting my samsung galaxy S7 the recovery got deleated and I think the boot.img did as well. So in order for me to get it back and working I thought a Rom might work so I used this https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-t3636434 which eventually turned out to work but the only problem I had is that now when I boot it up it says Verizon and I'm not sure is that because I didn't do the last 2 steps which were using flashfire. Because It booted up when and in order to use flash fire you would need to root the phone. Is there anyway to get it back to saying T-Mobile cause when inserting the sim it says "This isn't an Verizon Sim". Please help if you can.
Just noticed I posted this in wrong fourm and couldn't find how to deleate it my bad.
Cattman33 said:
During the process of unrooting my samsung galaxy S7 the recovery got deleated and I think the boot.img did as well. So in order for me to get it back and working I thought a Rom might work so I used this https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-t3636434 which eventually turned out to work but the only problem I had is that now when I boot it up it says Verizon and I'm not sure is that because I didn't do the last 2 steps which were using flashfire. Because It booted up when and in order to use flash fire you would need to root the phone. Is there anyway to get it back to saying T-Mobile cause when inserting the sim it says "This isn't an Verizon Sim". Please help if you can.
Just noticed I posted this in wrong fourm and couldn't find how to deleate it my bad.
Click to expand...
Click to collapse
Surprisingly, the non-beta AT&T Oreo firmware is not SIM-locked (the same was true of the beta firmware). It works out rather nicely, since the UnCarrier still has not released their Oreo firmware for Snapdragon phones. I ran the beta firmware on this same phone - which turned out to be absolutely irrelevant, as the Darth Cookie firmware even took my last Nougat backup with nary a quibble. So if you rock the UnCarrier and want a cookie, you can have one - a Darth Cookie, that is.