I got a G2 from Ebay a few months ago (4 to be exact) and from then and now I've not done much but than install a few custom ROMs (2) and restore to KDZ (3). All that time I've been getting Overheating issues. I am almost 96% sure that it is not a frankenphone but I feel something is up with this phone.
When I first got it. I used the phone for a few weeks on stock (it was on Jellybean shipped). Then KDZ upgraded to KitKat (no sim, full wipe). Still nothing, no overheating.
Then I finally decided to get a ROM going. I rooted with TowelRoot and installed recovery with AutoRec. Then upgraded TWRP to support lollipop ROMs (Blastagator's Thermal TWRP).
Now after all of that I successfully installed my first ROM of choice - Blisspop. It ran like a dream. But this is where the overheating started.
I constantly got 40C+ and above. I did nothing about it. Got sick of it, and installed another ROM (Cloudy 2.2). Of course it installed successfully. Nothing wrong. Still overheated like mad.
Used Cloudy for a few weeks and finally decided to back everything up and restore via KDZ (back to KK). After that. Overheating still occured although it was a little better than I expected... I wondered what was going on. By then it was a month and the Ebay seller said I was Out of Luck. Now I decided to install Resurrection Remix 5.1. It seemed to fix some overheating issues but they were still severe-ish.
Decided to restore via KDZ again (KK again) still nothing. After that I installed everything I needed and installed a Stock Lollipop Stripped Down ROM, I've heard bad things about LG's Stock Lollipop (including overheating) so I'm not surprised that this thing is overheating in this state. I am now stuck here. Wondering what the hell I need to do to get this thing back to it's former glory.
Look at my location. I live in Nevada. I know that High Temps here aren't good for this phone and that might be the problem. But this phone is hardly used anywhere without AC (Car, Home, Job, Banks, Buildings, ect) and both are really cool compared to outside's 100+F/37C heat. So that can't be a factor.
I'm wondering if I can return this thing back to LG/AT&T if they still allow them to be repaired. My seller gave some info like S/N and original purchase date. But I'd rather not do that. Also, if I'm Out of Luck on warranty. How much would it cost to pay LG for it to be fixed? Just wondering. But I would rather fix it on my own that to wait a few weeks without a phone.
TL;DR: Bought phone, upgraded from JB to KK. Rooted and installed recovery, flashed a ROM. Overheated. KDZ'd back, overheated. more rom installing ect, ect. still overheating. Wondering what I need to do to restore this thing.
Well if its is under warranty i would suggest going through lg however if you are not, there is a thermal mod on xda for the g3 which is also applicable for the g2 and it requires opening the phone up and applying thermal compound on the cpu chip. Google lg g3 thermal mod and there is an xda forum for it.
Sent from my LG-D800 using Tapatalk
xmayhemreturnsx said:
Well if its is under warranty i would suggest going through lg however if you are not, there is a thermal mod on xda for the g3 which is also applicable for the g2 and it requires opening the phone up and applying thermal compound on the cpu chip. Google lg g3 thermal mod and there is an xda forum for it.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
I've checked the threads and I've seen nothing about it working for the G2. Have you tried it?
It is compatible with almost all phones. Honestly, all it requires you to do put thermal compound on the cpu. It does work for the g2.
Sent from my LG-D800 using Tapatalk
Related
Is the ATT OTA any good or provide significant improvements? My phone is currently running pretty flawlessly with Grevious ROM and I'm kind scared to brick it following the Flash to stock thread instructions lol. I've read the instructions several times and I'm confident in following them, but I really don't want to somehow brick it or get into bootloops and be out a phone for any period of time.
thestrangebrew said:
Is the ATT OTA any good or provide significant improvements? My phone is currently running pretty flawlessly with Grevious ROM and I'm kind scared to brick it following the Flash to stock thread instructions lol. I've read the instructions several times and I'm confident in following them, but I really don't want to somehow brick it or get into bootloops and be out a phone for any period of time.
Click to expand...
Click to collapse
Personally, I wouldn't bother with it.
Update summary
On December 3, 2013, AT&T and Samsung released a software update for the LG G2 (D800). This software package updates the baseband version to M8974A-AAAANAZM-1.0.190034.
This software update includes
The size of the update file is 57 MB and is available for download via Wi-Fi.
ISIS Ready
EAS Fix (Enable Data Encryption Policy in the device via over the air)
Enhanced Google Map
Fix-to correct AT&T Messages name display issue within AT&T folder on the Home screen (wrapping of "s" to the second line)
Ready2Go enhancements
Click to expand...
Click to collapse
I also wouldn't bother with it. Besides the LG flash tool won't work since you are using a Rom with a different base. You would need to flash the stock rooted Rom or clean rom.
Sent from my LG-D800 using XDA Premium HD app
I unrooted and took the update. It's nothing life changing.
Sent from my LG-D800 using xda app-developers app
Cool thanks all. I'll just skip it for now!
Avoid it like the plague.
thestrangebrew said:
Cool thanks all. I'll just skip it for now!
Click to expand...
Click to collapse
You're not missing anything, if anything you're saving yourself aggravation. There's not a single improvement that I can see with the phone yet it's introduced a nice battery drain by the name of "Android System" once you update to the new firmware. Happened to my original G2, and last night on my 2nd G2 when it auto updated as I was sleeping. You'll notice "Android System" now taking up about 50% of your battery usage. I don't even know how it automatically updated last night as I was sleeping, must have been like that Windows auto update thing where it tells you it's gonna do it in 15 minutes unless you intervene or something. I'm really debating if I should try to flash it back to stock because it's that bad, this coming from a person running it stock this entire time without even rooting.
on the latest d802 4.4.2 custom roms and kernels i get a lot of freezes.
it will freeze in the middle of an animation and will take some seconds up to some minutes and then working normal again.
sometimes i have to hard-reboot to get out of freeze / lag.
on older 4.4.2 slimroms i never had this behavior, only since some weeks with new roms / kernels.
i`ve tried every rom / kernel combo but sooner or later i will get a freeze again.
could a revert to stock and re-rooting / flashing custom rom maybe a solution? i`m afraid to do this because of the long time to backup my 32gb data.
what are your experiences with the latest 4.4.2 roms and kernels? did you find a solution for this with any combo or fixes?
help would be appreciated.
push! no one else with same problems? maybe i got a hardware defect?
paratox said:
push! no one else with same problems? maybe i got a hardware defect?
Click to expand...
Click to collapse
The only thing I can say is I own the VS980 version of the device and i've tried every single 4.4 rom offered on this sight and have the same issue with all. Most of the time i'm using the device and it freezes, sometimes reboots, and sometimes comes out of it after a few minutes. Also not being able to wake the device only seeing a black screen and forced to hard reboot device. 4.3 seems to be a much better with these issues but not completely solved for me. I'm hoping the release of 4.4 source from lg will fix these issues but i'm unsure. So at least your not alone in these problems lol. I've tried multiple kernels and governors etc. Bumping up the min freq on the cpu seems to help and changing to interactive governor but doesn't eliminate the issue just help. I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
flyinj54 said:
I thought my next move would be to use lg flash tool and update to latest firmware reroot and install cwm.
Click to expand...
Click to collapse
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
paratox said:
i think i will do the same today after work. hopefully this helps.
the better option would be to stay some days on stock rom to ensure there is no hardware defect. but i can`t stand stock so this would be a hard route! ^_^
Click to expand...
Click to collapse
Yea unfortunately it seems very common among these devices so i'm pretty confident it's a software issue although i'm not 100% sure of that. I ran a flex rom for a few days on 4.2.2 and didn't have any of the same issues.
added a poll as a matter of interest.
omni-ROM, Mokee rom, vanir rom etc.freezing problem still continues.
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
lubirdy said:
Using CM11 (4.4.2) for 5 days with zero freezes so far.. note that this is on D800, not 802.
Click to expand...
Click to collapse
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Stock cm11 kernel?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yes, stock cm kernel.
I'm thinking back now and it did freeze once when first signing into the Google account immediately after flashing the ROM, but nothing after that. So.. nearly spotless
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
flyinj54 said:
Nice! Maybe they are getting the issues ironed out. Haven't been on cm11 for a week or so since it was the worst with freezes for me. I'll have to give it another shot.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Best of luck! To be specific, I'm using the snapshot release of cm11... still don't trust the nightly releases
i did a lg flash tool stock restore, factory reset and OTA updates. now the freezes did not come back until now *knock on wood*.
when i did a backup of the sd there was one corrupt media file which was not able to transfer.
maybe the media scanner did go crazy and was the reason for the freezes.
using cm11 m3 on my d802... very little freezes compared to previous nightlies, fingers crossed
What's going on world. I've recently found out that the T-Mobile G2 has kit kat ROM floating around and I was just wondering if anyone has flashed it and what their thoughts about it are? Also I've read that after flashing the ROM you lose custom recovery which in turn would leave one stuck with that particular ROM until one is created.. I guess I'm just asking if anyone believes a custom recovery would be up any time soon?
Sent from my LG-D801
DurbanPoison24 said:
What's going on world. I've recently found out that the T-Mobile G2 has kit kat ROM floating around and I was just wondering if anyone has flashed it and what their thoughts about it are? Also I've read that after flashing the ROM you lose custom recovery which in turn would leave one stuck with that particular ROM until one is created.. I guess I'm just asking if anyone believes a custom recovery would be up any time soon?
Sent from my LG-D801
Click to expand...
Click to collapse
Read the general G2 section.. There is a long thread about this.
Sent from my LG-D801 using Tapatalk
I just received my D801 back from LG repair after dead spots and phantom inputs on my device. LG replaced the touchscreen under warranty. Now the phone is smooth and very responsive, like it should be.
Since I had restored phone to the 10g firmware and unrooted before sending it in, I decided to flash the 20a KK update. Of course I lost root access and custom recovery, but I can live with that awhile I evaluate performance, which is, so far, better than 4.2 JB. T-Mo will eventually push the OTA update, which requires stock recovery. I figured I'd do it manually by flashing the .kdz file, which BTW does NOT wipe data. Despite large size (1.5 GB), file flashes quickly using LG Flash tool.
Maybe I'm just very happy to have my G2 back and working properly, but I like the KK update, although I hope a root exploit is found soon and we get a new custom recovery. That's why I donate to devs!
Don't know if that helps. Give KK a try, you'll like it!
LS980 = Major Pain. I've rooted and flashed over 20 phones/tabs and I think it may be worst.
Thanks for any help !
I have bone stock Sprint 4.4.2 Kitkat ZVC LS980, then rooted and w/ TWRP 2.7.0.
I get bootloop after flashing CM11 or Slimkat and wiping.
I can get back to stock KK if I spend 5+ minutes mashing the buttons in different combos w/ different timing and USB inserted or not, and getting to recovery. Then I restore the stock backup I made.
I previously flashed many different ROMs and kernels OK.
All this recent grief was preceded by flashing the wrong KK modem, then trying to load Mahdi ROM, having CM installed at that point. That gave me bootloop.
From recovery I used dd to flash ZVC partitions. Recovery stopped working and I got fastboot. I tried using fastboot to flash all partitions, then I got Security Error.
I fixed Security Error by spending 3 hours messing with a Windows 7 PC again, using flashtool to flash ZV8 that worked before. (This time I wrote down steps, for next time, LOL.)
So ZV8 worked, and I OTA'd to ZVA. That worked and I OTA'd to ZVC.
That's when I used ioroot25r1 to root succesful. And LS980_AutoRec to flash TWRP 2.7.0.
I've never used this phone as a phone or had any dealings with Sprint; not sure about it's previous history, I bought it on EBay.
BB seems to be M8974A-AAAANAZM-2.0.20046, I presume automatically updated w/ OTAs before root and recovery flash.
I swear I must have spent at least 8 hours on this "adventure". And I'm a dev who's been doing low level Android for 3.5 years and low level Linux stuff since 1996 and built various CPU and computer projects starting in the late 1970's...
So what the heck am I missing here ?
Thanks for any help !
I don´t know if it could be helpful, but I use to flash my LG G2 D802 with a stock rom JB not KK, and I use too CWM not TWRP and I´ve never had a problem flashing.
I have Slimkat in my device, although I had CM11 and stock roms modified without any problem with them.
Anyway, good luck
crombull said:
I don´t know if it could be helpful, but I use to flash my LG G2 D802 with a stock rom JB not KK, and I use too CWM not TWRP and I´ve never had a problem flashing.
I have Slimkat in my device, although I had CM11 and stock roms modified without any problem with them.
Anyway, good luck
Click to expand...
Click to collapse
Thanks...
Yeah, it should be easy enough to try CWM.
Some carrier variants, like my Sprint, often have issues the International models don't.
mikereidis said:
Thanks...
Yeah, it should be easy enough to try CWM.
Some carrier variants, like my Sprint, often have issues the International models don't.
Click to expand...
Click to collapse
I wish you better luck with CWM :good:
crombull said:
I wish you better luck with CWM :good:
Click to expand...
Click to collapse
Flashing CWM didn't help.
What worked was LG Flashtooling back to ZV8, and rooting and recovery installing from there, as I did many months ago.
I dunno why. But I'm happy for now, until next bootloop at least.
Finally, great news
crombull said:
Finally, great news
Click to expand...
Click to collapse
Only for a little while.
Flashed CM11. Good.
Flashed SlimROM. Good.
Flashed Mahdi and LS980 Patch. Good-ish for a while, then the kernel went crazy with audio devices disappearing.
Try to re-flash CM11. Bad.
Try to restore stock. Bad.
Grrr... Back to LG Flashtool ZV8. OTA to ZVA. Re-root.
Not sure about next step.
Time for me to learn about Loki I guess.
mikereidis said:
Thanks...
Yeah, it should be easy enough to try CWM.
Some carrier variants, like my Sprint, often have issues the International models don't.
Click to expand...
Click to collapse
These days, all phones for CDMA networks are going to have more issues than those for GSM networks. Really best to go with a GSM network if possible. But Verizon's network definitely beats AT&T's (and especially T-Mo). Not worth the price, IMO, but I'd say only use Verizon if you're in an area that only Verizon works well. Sprint is useless.
It´s a pity hear that, I wish you the less possible problems with it, and a soon solution
dandragonrage said:
These days, all phones for CDMA networks are going to have more issues than those for GSM networks. Really best to go with a GSM network if possible. But Verizon's network definitely beats AT&T's (and especially T-Mo). Not worth the price, IMO, but I'd say only use Verizon if you're in an area that only Verizon works well. Sprint is useless.
Click to expand...
Click to collapse
Thanks. But you may have missed the part where I said:
I've never used this phone as a phone or had any dealings with Sprint
Click to expand...
Click to collapse
This is a phone I bought only for testing of my FM apps. I think there's a place for a GSM SIM in it, but I still don't know and don't care too much right now.
EDIT: Hmmm, under System updates I've never been able to do "Update PRL", "Update profile" or "UICC Unlock" I think due to authentication issues. But I can "Update Firmware" and I think "Update LG Software".
I went with Sprint instead of D802 because they were cheap on EBay, as low as $200-250. Possibly a banned ESN (despite the EBay listing), but again that doesn't affect me.
But if I could do over, I might go for d802; as you say less troubles, and many more people have d802s than Sprint.
My Nexus 6P went in a bootloop recently.
It was shortly after I unlocked the bootloader and rooted the phone.
I tried everything I could (stock firmware 7.1, 7.0 and the oldest that was available) but nothing worked.
I still had warranty so I sent it back to webshop where I bought it.
Now I got my phone back and the note says 'Mainboard replaced'.
What I want to know:
- Can it be my fault the phone broke, I know the Nexus 6P has some issues concerning bootloops.
- Can I safely root again? Or would you not recommend it?
Thanks for your answers.
I have a backup phone, but I don't want to f*** my 6P up again.
Search for BLOD. You will answer your own question in no time. Lol No you are not to blame. It had or is happening to probably hundreds of phones by now. You will also see there are many different roms, 6&7, root or stock that have the problem.
Sent from my Nexus 6P using XDA-Developers Legacy app
Rooting doesn't cause the boot loop of death. Flashing something sometimes triggers it (including flashing a normal OTA on pure stock) but it is almost certainly a hardware issue.