Any idea how to flash my idiotic LG? - LG Spirit Questions & Answers

Hello,
I really do not remember how I used to flash LG, I've tried everything on google, the LG Flash tool 2014 and LG UP method.
LG flash tool gives me contact system admin thus the LG UP when goes to Com port and saying my phone model it says not compatible or something.
I need to reflash it cause the Twrp is stuck at factory reset on mem cache.
Its H440 aka Spirit 4G LTE (on back it says soo C70 E).

Occasionally it becomes difficult, but you will achieve it, just read and go learning again to do it! with patience

Related

[Q] [t-mobile d801 soft bricked can't use LG tool

I can get into download mode, but have a secure boot error and cant use ADB or fastboot. I've been reading every thread I can find.
I tried the LG tool, it never downloads the firmware, just hangs at 12%. Tried different drivers etc. Let it run overnight just in case it was a slow download - nada.
Tried the LG tool by entering the imei number first, but the tool reports a low battery and won't load the firmware. Phone is fully charged, i assume that battery level reporting is not working correctly.
Tried to load the kdz with the R&D tool, it errors out at 49%.
Tried to do the offline process with shttp from the unbrick any phone thread. It uses an older version of the LG tool and won't recognize that the phone is plugged in. If i install the newer tool that sees the phone, the process crashes the tool.
it all started when i tried to flash twrp and used the one for a different model g2. Dumb, I know. this is my first time soft-bricking a device.
Can anyone please point me in another direction?
UPDATE: phone was reporting that it was an 802. Downloaded and flashed an 802 kdz file and the phone booted! First time it was able to get past 49%. Nothing really works on the phone, but now i'm able to use the LG Mobile support tool to flash the correct firmware. The program is downloading the sofware now.
When you say LG tool I'm assuming you're talking about the official program you can download from their site?
I have the Verizon G2 and promptly erased everything on it the first night I got it.. Don't flash / wipe files at 4 AM when you've been up all day and night.
Anyway this thread http://forum.xda-developers.com/showthread.php?t=2432476 really saved my rear. Maybe the T-Mobile version will work to get yours back to stock.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
Vepaot said:
When you say LG tool I'm assuming you're talking about the official program you can download from their site?
I have the Verizon G2 and promptly erased everything on it the first night I got it.. Don't flash / wipe files at 4 AM when you've been up all day and night.
Anyway this thread http://forum.xda-developers.com/showthread.php?t=2432476 really saved my rear. Maybe the T-Mobile version will work to get yours back to stock.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
Click to expand...
Click to collapse
works at the start and hangs at 49%. There is one bit that needs to be switched and this would work.
okay, looks like the phone is reporting that it is a d802 from my first f'd up flash. I think this may be causing the problems with flashing the 801 kdz.
Can i flash an 802 kdz onto an 801? then possibly later go back to 801?

[Q] Bricked my LG G2

Hi Friends,
I am new to this Forum and Android as well. I recently bought unlocked LG G2 32 GB in India. It was:
Model - D802
Android version - 4.4.2
Software version D80220b
As it's wifi reception and network reception was not good, I thought of installing the ROM again. The biggest mistake that I did not install any recovery and didn't even rooted my device. I checked with root checker and it showed that your device is not rooted. Then I follow the method given on below link:
http://forum.xda-developers.com/showthread.php?t=2432476
I took the firmware file named "India 32GB D80210C_00.kdz" and select type as "3GQCT" and performed the Normal Flash. It went well but after it booted up, my touch screen calibration was totally lost. I connected mouse using USB OTG cable and calibrated the device but it didn't work out. Calibration still seemed gone.
After all try, I couldn't do much and read of TOT method to go back on Jelly Bean. I did that as well using "BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0.exe" from which I extracted the TOT file and performed the flashing again by coming in "Download mode".
After that my phone is in boot loop and same issue of lost screen calibration. If I try to go into recovery it gives me option only to factory reset the phone which does not help out at all. I guess it's because i didn't root my phone and didn't even installed any recovery.
I know I have done a lot of mess with no knowledge but please help me out as its my new phone and I have hardly used it for 1 month and it's not even under warranty.
Thanks.
grvshri said:
Hi Friends,
I am new to this Forum and Android as well. I recently bought unlocked LG G2 32 GB in India. It was:
Model - D802
Android version - 4.4.2
Software version D80220b
As it's wifi reception and network reception was not good, I thought of installing the ROM again. The biggest mistake that I did not install any recovery and didn't even rooted my device. I checked with root checker and it showed that your device is not rooted. Then I follow the method given on below link:
http://forum.xda-developers.com/showthread.php?t=2432476
I took the firmware file named "India 32GB D80210C_00.kdz" and select type as "3GQCT" and performed the Normal Flash. It went well but after it booted up, my touch screen calibration was totally lost. I connected mouse using USB OTG cable and calibrated the device but it didn't work out. Calibration still seemed gone.
After all try, I couldn't do much and read of TOT method to go back on Jelly Bean. I did that as well using "BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0.exe" from which I extracted the TOT file and performed the flashing again by coming in "Download mode".
After that my phone is in boot loop and same issue of lost screen calibration. If I try to go into recovery it gives me option only to factory reset the phone which does not help out at all. I guess it's because i didn't root my phone and didn't even installed any recovery.
I know I have done a lot of mess with no knowledge but please help me out as its my new phone and I have hardly used it for 1 month and it's not even under warranty.
Thanks.
Click to expand...
Click to collapse
There might have been a problem with the firmware that you used and the flash method. Use this to find your firmware and pick cse flash this might solve it.
I searched the firmware in your given link by my IMEI number, but I have a problem. After I click on "Upgrade start" in "Normal web test upgrade", it does not give me country select option. Instead it open LG Mobile support tool which just keeps on showing "Waiting for Connection".
If I click start upgrade without selecting "normal web upgrade test", it gives me country selection window.
What should I do? Can I directly click on "Start upgrade" ?
try this one
http://forum.xda-developers.com/showpost.php?p=51265001
OP I have the same problem, see my recent posts. Let me know if you found a fix.

[Q] VS980 stuck as a F350K, generic DLL no good

This is a good one. Let a friend borrow my VS980 (Verizon LG G2), ofcourse it was modified with TWRP, etc. He like me knows how to handle roms, etc. However, he seems to have flashed a Korean G Pro 2 firmware of some sort and while the phone was booting properly with actual Verizon roms, wifi, signals, etc did not work. So upon attempting to revert to stock I noticed Download Mode did not work. So I used AutoRec for the vs980 and it caused the phone to get into fastboot mode. Using the following guide, I fixed the fastboot issue:
http://forum.xda-developers.com/showthread.php?t=2681089
Now I am still detected as a F350K, this is usually due to that information being stored in the build.prop, which I couldnt wipe since the fastboot loop would ban booting into DL mode or TWRP.
I have also read about the generic .dll file, but it is a no go, assumingly because were talking about two different phones.
Any suggestions? Will a .kdz restore be more better than a .tot restore?
:crying: I got desperate and permabricked it. Tried flashing the Korean G Pro 2 firmware and now it will not power on. No download mode, not detected, etc. Eventually it will show the notification LED flashing colors like it wants to boot, and nothing more. I guess this is the end for my VS980.
I Have same Problems facing bos! Now what can i do! Help Me Plzzzz...........
Youtube:

LG G2 display problem after going back to stock

a few feeks ago bought a second hand lg g2 d802 running kitkat 4.4.2 wich was only detecting 2g when i try to connect to the internet, i tried to solve this problem by entering the hidden menu and selecting the network types it could detect but no luck, so i decided to upgrade to lollipop, i downloaded the lg support tool and went for it, when the update was done i found myself with an almost completly functioning device except it had the "imei=null" problem, meaning no network at all --"
i tried the QPST but it was unable to detect my phone, so i decided to root my phone and go for a custom rom, the cyanogenmod13 nightly (i don't really know what i was thinking at that point :s ) and when done i was stuck in a bootloop, so i tried flashing a stock rom kdz method but the lg flash tool would stop automatically. since then i've been trying to flash stock TOT roms, the process would stop at 94% and the phone reboots. the screen shows random pixels and lines, the start up lg tune is there and i feel vibration when i press the home buttons location, i've tried to reset it to factory settings and i've used theLGUP_8974.dll, selecting the BOARD DL option in the lg flash tool but that didn't solve the problem. i have read somwhere that it could be a kernal problem, i don't know if i should go that way ( am at that point where i don't want to mess up my device anymore xD ) what do you guys think?
thank you for your help
restlessone said:
a few feeks ago bought a second hand lg g2 d802 running kitkat 4.4.2 wich was only detecting 2g when i try to connect to the internet, i tried to solve this problem by entering the hidden menu and selecting the network types it could detect but no luck, so i decided to upgrade to lollipop, i downloaded the lg support tool and went for it, when the update was done i found myself with an almost completly functioning device except it had the "imei=null" problem, meaning no network at all --"
i tried the QPST but it was unable to detect my phone, so i decided to root my phone and go for a custom rom, the cyanogenmod13 nightly (i don't really know what i was thinking at that point :s ) and when done i was stuck in a bootloop, so i tried flashing a stock rom kdz method but the lg flash tool would stop automatically. since then i've been trying to flash stock TOT roms, the process would stop at 94% and the phone reboots. the screen shows random pixels and lines, the start up lg tune is there and i feel vibration when i press the home buttons location, i've tried to reset it to factory settings and i've used theLGUP_8974.dll, selecting the BOARD DL option in the lg flash tool but that didn't solve the problem. i have read somwhere that it could be a kernal problem, i don't know if i should go that way ( am at that point where i don't want to mess up my device anymore xD ) what do you guys think?
thank you for your help
Click to expand...
Click to collapse
Sounds like to me you may not have a D802. You'll need to take the back cover off, and look and see what model #s you see. As if your having screen issues that sounds like your flashing a D802 firmware on a D800 or D801.
Also remember flashing will almost always stop before 99%.. Anything after 85% its done this is normal and will almost always happen.
These D802's have a LONG history (mostly bought referbs) of not being what they are being sold as.
hyelton said:
Sounds like to me you may not have a D802. You'll need to take the back cover off, and look and see what model #s you see. As if your having screen issues that sounds like your flashing a D802 firmware on a D800 or D801.
Also remember flashing will almost always stop before 99%.. Anything after 85% its done this is normal and will almost always happen.
These D802's have a LONG history (mostly bought referbs) of not being what they are being sold as.
Click to expand...
Click to collapse
the problem has been solved, it tuned out to be an ls980, now my G2 is fully back to life :laugh: thanx alot hyelton for your help :good:

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

Categories

Resources