Related
I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?
TimidRat said:
I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?
Click to expand...
Click to collapse
So completely unrooted/returned to stock it STILL random reboots?
If so, sounds like a hardware related issue.
Yeah went all the way back to unrooted s-on, I was starting to think it was hardware related, thanks mattykins
I can confirm that this is a hardware issue. My first EVO had the exact same problem you had, and continued to get worse and worse to the point where it would cycle 10 times before actually staying on for a little bit.
I called Sprint and told them that I thought my phone was defective, and when I explained the problem they said it was a known issue and that it would be replaced free of charge.
A friend of mine is actually dealing with this very thing right now and he said that Sprint is now shuffling people off to HTC for defective phone replacements. If you are within 1 year of buying the phone it should be free, as per the manufacturer's warranty.
I also had this happen and got it replaced. Now I'm without root but at least my phone works. It's definitely hardware related.
Sent from my PC36100 using XDA App
I had the same problem, no matter the rom or kernel, it would reboot and get stuck in bootloop. I finally gave in and went to sprint, turned out it was something with the hardware that would heat up my battery and then when it got to a certain temperature it would cause it to reboot. Definitely take it into sprint.
Sent from my PC36100 using XDA App
Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.
TimidRat said:
Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.
Click to expand...
Click to collapse
Try anyway.
Technically you would win legally because the crack has nothing to do with the issue you're having thus the warranty is valid.
(Although I guess they could claim you must have dropped it and that could have damaged something internal)
But the worst case scenario is they say you have to pay the $100 to get a new one and if you don't you still have your phone.
The best case, they fix or replace it.
Either way, its worth a shot.
There seems to be a dead spot on the touchscreen near the top. It's there on the stock ROM and on custom roms (both AOSP and ROMs based on LG's UI). Do you guys have the same issue?
http://i.imgur.com/4fKjQmG.jpg
Tried that on quick memo. I dont have it luckily.
Sent from my LG-D802 using xda premium
Tried it also. No problem for me too.
Sent from my LG-D802 using Tapatalk
My first one developed that after some time, same place too. Went to verizon, showed them that, and they replaced it with a "certified like-new" which thankfully seems to be new as far as i could tell.
UberMario said:
There seems to be a dead spot on the touchscreen near the top. It's there on the stock ROM and on custom roms (both AOSP and ROMs based on LG's UI). Do you guys have the same issue?
http://i.imgur.com/4fKjQmG.jpg
Click to expand...
Click to collapse
Saw it already reported here before. But I do not have it.
It's been reported several times here, in 99% of the time an update fixed that.
Which version do you have?
robogo1982 said:
It's been reported several times here, in 99% of the time an update fixed that.
Which version do you have?
Click to expand...
Click to collapse
I have the LG-D801 aka T-Mobile US version. The software version on it is D80110C_00. I used the LG flashing tool and flashed a .kdz file named "T-Mobile USA D80110C_00.kdz" since I bought it from craigslist and wanted it back to 100% stock (guy sold it for $80 since he rooted it and then did the OTA which caused him to go into that recovery boot loop issue and only way to fix it was to flash that .kdz file)
I'm not rooted and I am not using a custom recovery. I guess I'll do the OTA update the phone was bugging me to do.
EDIT; Installed the latest OTA. The issue is still there but it did decrease the dead zone. The biggest problem is that I can't press "install" for apps in the play store since the button is right in the dead zone.
Getting the same problem here on my device, suddenly. I updated to the new Kit Kat update (I'm on Sprint) but didn't seem to make a difference. How annoying this suddenly happened and my phone was not dropped or damaged or anything. My other friend with a G2 had the issue and it went away on its own over time somehow. i'm noticing the bar where I have trouble is aligned exactly with the power button on the back, so I wonder if that has something to do with it, in the hardware.
Hi I have the same problem too, affects where the install open button area on Play Store near the top right. I am running CloudyPro 2.1.
Did you manage to fix this problem?
randomvector said:
Hi I have the same problem too, affects where the install open button area on Play Store near the top right. I am running CloudyPro 2.1.
Did you manage to fix this problem?
Click to expand...
Click to collapse
This is very weird, same thing happened to me today around noon, phone was fine all morning, then dead zone in same area, wth is this, is At&t or LG doing something ota that we do not know about.
edit: just wanted to add, I am on the D800
I'm don't think so as I'm on a custom rom. I've heard from some on xda the update fixes it but I've used the stock KitKat Rom and no luck there. I'm now using cloudy flex 2.2 still the dead zone is there.
Sent from my Nexus 4 using Tapatalk
Same issue here too. Stock Verizon G2 on Kitkat. Can't click on install button when in play store. Turned on the 'show touch' in developer mode and it doesn't recognize the install button when on an individual app in the play store, it shows as touch above or below it. It also skips the button when i run my finger across the screen.
coreygator said:
Same issue here too. Stock Verizon G2 on Kitkat. Can't click on install button when in play store. Turned on the 'show touch' in developer mode and it doesn't recognize the install button when on an individual app in the play store, it shows as touch above or below it. It also skips the button when i run my finger across the screen.
Click to expand...
Click to collapse
Funny how this happened to me right after the ota as well...
Dead zone in the same spot ..
And well in order to fix it( the install button atleast) is to change the DPI to 330
I called lg and they gave me an authorization to send it in for repair.
Call and see what they tell u guys
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Yep. VS980 Stock Kit kat rooted with TWRP 2.7.0.0
Same exact issue. Same exact spot. Can't hit install on the play store. Haven't tried taking it to Verizon yet. I bought my phone through Target though I hope Verizon will replace it if it is in fact a hardware issue. I'm not gonna try and take it in until after I try a couple different ROMS to make sure it is a hardware issue.
I am on D800 was on CloudyFlex when it happened so it has nothing to do with OTA exactly, I returned to fully stock At&t 4.2.2 and it was still there. I am getting a replacement under warranty. Something weird is definitely happening if so many have seen this issue. It is almost like a timer going off in phone coding and bam that part of screen is deactivated. Whatever it is, this will be my last LG phone. Never had an issue with my iphone or galaxy s2 skyrocket.
Same problem here, VS980. It started happening right after I tried the newest build of CloudyStock with knock on support. I've been browsing through multiple CloudyROM threads and I'm seeing identical problems, (including the exact area of the dead spot, around where the install button is on the Play Store). I can't post in any of them because a. I don't have enough posts, b. Cloudy in his FAQ states that the VS980 is only for testing. I've tried flashing different AOSP and Stock roms including the latest PA and XDABBEB builds and the problem crosses over after full wipes. Has anyone figured out a way to fix this yet other than returning the phone for another?
To be clear: This phone has no damage to it whatsoever. No scratches anywhere including the screen, etc. I'm worried about how Verizon will take a warranty seeing as there's an "UNROOTED" flag in the bootloader.
Has anyone tried to update touch firmware?
Sent from my LG-D803 using XDA Premium 4 mobile app
jester12345 said:
Has anyone tried to update touch firmware?
Click to expand...
Click to collapse
I've read some people do it to no avail, but I'd like some confirmation on that. The service menu still hasn't been discovered on the VS980 from what I've read. It's not the same code with a different model number at the end like the D802. For example, Every other model of the G2 is 3845#*XXX#, but the Sprint model is 5689#*980#. 3845#*980# for the VS980 doesn't work.
Dang. Now im worried to update.
Sent from my LG-D803 using XDA Premium 4 mobile app
Suddenly from one day my phone started heating. It is also heating when not in use. As it is going to 46°c turbocharging is not working. Due to that (As turbocharge won't work above 44°c)I am not able to turbocharge my phone. Someone give me a solution for heating issue or atleast how can I force my phone to turbocharge above 44°c.
If you TurboCharge your phone above the safe limit, your phone might overheat. That safe limit is there for a reason.
Check what is causing your phone to heat up. We really can't guess a cause or a solution. You've got to figure it out on your own.
I'd suggest starting by looking into what is eating your battery and running in the background. Try booting into safe mode. If it's an app causing excessive phone usage, it'll not show then.
Whatever the manner, you've to help yourself before we can help you.
zeomal said:
If you TurboCharge your phone above the safe limit, your phone might overheat. That safe limit is there for a reason.
Check what is causing your phone to heat up. We really can't guess a cause or a solution. You've got to figure it out on your own.
I'd suggest starting by looking into what is eating your battery and running in the background. Try booting into safe mode. If it's an app causing excessive phone usage, it'll not show then.
Whatever the manner, you've to help yourself before we can help you.
Click to expand...
Click to collapse
Yeah I checked about it. Even in safe mode it is heating up.
From one month I am having this problem and yesterday only I figured that the charging problem is due to overheating.
Overheating is tackled by march security patch, check if your phone has latest software update or not
Sent from my a3300-hv using XDA-Developers Legacy app
ca_guri01 said:
Overheating is tackled by march security patch, check if your phone has latest software update or not
Sent from my a3300-hv using XDA-Developers Legacy app
Click to expand...
Click to collapse
After that update also it's heating
Try factory reset then
Sent from my a3300-hv using XDA-Developers Legacy app
ca_guri01 said:
Try factory reset then
Sent from my a3300-hv using XDA-Developers Legacy app
Click to expand...
Click to collapse
Tried many times.
Today I thought of reinstalling OS and unlocked bootloader.
As mine is having March update now I'm unable to lock bootloader
sainaren said:
Tried many times.
Today I thought of reinstalling OS and unlocked bootloader.
As mine is having March update now I'm unable to lock bootloader
Click to expand...
Click to collapse
Looks like the March 2017 fastboot ROM is up, so you may be able to re-lock your bootloader:https://forum.xda-developers.com/mo...-npjs25-93-14-4-march-1-t3608138/post72329008
Be aware relocking won't restore your warranty (which you'll have voided when/if you unlocked your bootloader in the first place). If you've not unlocked your bootloader and wish to keep your warranty, you may consider visiting a service centre to see if they can re-flash the OS for you.
echo92 said:
Looks like the March 2017 fastboot ROM is up, so you may be able to re-lock your bootloader:https://forum.xda-developers.com/mo...-npjs25-93-14-4-march-1-t3608138/post72329008
Be aware relocking won't restore your warranty (which you'll have voided when/if you unlocked your bootloader in the first place). If you've not unlocked your bootloader and wish to keep your warranty, you may consider visiting a service centre to see if they can re-flash the OS for you.
Click to expand...
Click to collapse
We are better than the service center guys.
After relocking bootloader I claimed warranty for 1 time and then after five months they realized and my warranty is voided.
Thanks for the link
I just purchased a LS997 with ZV8 software version.
I am assuming that the 'recowvery' technique that I have seen won't work, and that dirty Santa only works to ZV7.
I read a number of comments on the LAFSPLOIT thread that made me believe that a technique may be available, but that it won't be released till the next version of Android (Oreo) is released for LG V20, or 2020.
I'm actually probably going to be OK with waiting, but, I would like to have somebody state, unequivocally that it WILL be released.
Alternatively, I'm not opposed to returning the phone to the seller, and purchasing one that I know will work with TWRP and Root. What model presents the easiest root? I like the 910 and the 918, as they have FM radio, which would be a cool feature to have.
At any rate, what are your opinions regarding both keeping the ZV8, or returning it and buying a different one, as well as, if I buy one, which should I buy for easiest and stablelest root.
And what are your recommendations for ROMS too? I previously had a LG G3, with FULMICS 8 on it, and really liked that.
Thank you, in advance for bot your time reading this, and possibly for the time you spent answering my query as well!
CHEERS
Kevin
wyldnewbie said:
I would like to have somebody state, unequivocally that it WILL be released.
Click to expand...
Click to collapse
I would say it's likely something will be released, but unequivocally? Unless you hear it from @runningnak3d, don't believe it.
If I were you, I would trade your LS997 for a H918 and root using lafsploit.
Good luck!
wyldnewbie said:
I just purchased a LS997 with ZV8 software version.
I am assuming that the 'recowvery' technique that I have seen won't work, and that dirty Santa only works to ZV7.
I read a number of comments on the LAFSPLOIT thread that made me believe that a technique may be available, but that it won't be released till the next version of Android (Oreo) is released for LG V20, or 2020.
I'm actually probably going to be OK with waiting, but, I would like to have somebody state, unequivocally that it WILL be released.
Alternatively, I'm not opposed to returning the phone to the seller, and purchasing one that I know will work with TWRP and Root. What model presents the easiest root? I like the 910 and the 918, as they have FM radio, which would be a cool feature to have.
At any rate, what are your opinions regarding both keeping the ZV8, or returning it and buying a different one, as well as, if I buy one, which should I buy for easiest and stablelest root.
And what are your recommendations for ROMS too? I previously had a LG G3, with FULMICS 8 on it, and really liked that.
Thank you, in advance for bot your time reading this, and possibly for the time you spent answering my query as well!
CHEERS
Kevin
Click to expand...
Click to collapse
Or buy a Samsung, updates and support from LG sucks
Sent from my LG-H910 using XDA Labs
Well. I think you've got the right idea,,,
SMTB1963 said:
Are there any versions or builds to avoid? That would make root access harder, I meAn.
Thank you very much for your input and time.
Kevin
Click to expand...
Click to collapse
I had to go off the grid for a while due to a family emergency. Because of that emergency, I realized just how MUCH I used the ability to swap batteries. I refuse to buy a phone that is sealed.
The V20 is a little dated, but it is plenty speedy for what I do (if I want to game, I will buy a freaking 3DS or a Switch).
Now I am getting to the point. I have an H918, and as long as I have an H918, it will be rootable. Take that however you want
-- Brian
You are (without a doubt) THE MAN!
runningnak3d said:
I had to go off the grid for a while due to a family emergency. Because of that emergency, I realized just how MUCH I used the ability to swap batteries. I refuse to buy a phone that is sealed.
The V20 is a little dated, but it is plenty speedy for what I do (if I want to game, I will buy a freaking 3DS or a Switch).
Now I am getting to the point. I have an H918, and as long as I have an H918, it will be rootable. Take that however you want
-- Brian
Click to expand...
Click to collapse
Brian,
I ended up returning the LS997 I had, because even though it was GSM unlockeď, I couldn't get MMS via SMS to work. It seemed like the MMS settings weren't being modified when I set up my APN for Virgin Mobile Canada. I am now hunting ebay for a H918.
I have been following your various threads here on XDA, and have to say that I appreciate the way you think through these things.
Also, I hope that your family emergency has resolved well.
Are the any specific 918s that I should avoid (ie: android or lg software updates, ARBs, etc...)
Thank you again.
Kevin
Well, I can't deny good advice when it's given !
SMTB1963 said:
I would say it's likely something will be released, but unequivocally? Unless you hear it from @runningnak3d, don't believe it.
If I were you, I would trade your LS997 for a H918 and root using lafsploit.
Good luck!
Click to expand...
Click to collapse
As it happened, the LS997 wasn't sending MMS via SMS, and seemed to not let me update the MMS section of the APN settings. So I've sent it back. Am looking for a nice H918 right now.
So... thank you for your good advice!
Kevin
Yea, it makes no difference what software is on the H918.
The LS997 should be avoided like the plague. It will be rootable, but it will probably never be worth a damn. Sprint had LG flip additional switches in that models CPU (qfuses), so hardware wise it is different enough that it just isn't fixable even when rooted. For example, cellular bands being disabled at the hardware level.
When the 700Mhz auction took place, Google was able to get some provisions into the agreement for that spectrum where carriers had to allow other devices on their network, and had to allow for unlocking. However, if the phone doesn't have the hardware needed to work on other carriers, well, then it is moot.
Sprint is taking advantage of that, and making sure their models only work on their network. They need to keep as many customers as they can.
-- Brian
Hi Brian,
I have an unlocked LSS97, I'm not sure how they unlocked it as I bought it from a mobile seller.
But unfortunately, I updated the software from ZV6 or ZV7 to ZVA (ARB=1) , and now I'm stuck with it. I'm still waiting for magical happens on my device, so that I can root it and flash a customer kernel and rom, since the stock rom is messy for me. It's very laggy even when I play game on low graphic setting (PUBG is an example), while other phone with lower GPU can play it smoothly.
But you said that "hardware wise it is different enough that it just isn't fixable even when rooted", does it mean that even I root the phone and install another kernel, issue related to GPU/ CPU is still there? And how about the network?
As of now, I can't find any other phone has the reasonable price than LG V20 (for Camera quality, dual screen and speaker).
Thank you!
dvckbiz said:
Hi Brain,
I have an unlocked LSS97, I'm not sure how they unlocked it as I bought it from a mobile seller.
But unfortunately, I updated the software from ZV6 or ZV7 to ZVA (ARB=1) , and now I'm stuck with it. I'm still waiting for magical happens on my device, so that I can root it and flash a customer kernel and rom, since the stock rom is messy for me. It's very laggy even when I play game on low graphic setting (PUBG is an example), while other phone with lower GPU can play it smoothly.
But you said that "hardware wise it is different enough that it just isn't fixable even when rooted", does it mean that even I root the phone and install another kernel, issue related to GPU/ CPU is still there? And how about the network?
As of now, I can't find any other phone has the reasonable price than LG V20 (for Camera quality, dual screen and speaker).
Thank you!
Click to expand...
Click to collapse
If you follow his other threads you'd know he's been working on a root solution for the 997 so be patient otherwise if you want be risky he has a thread here seeking volunteers to test just know you due risk a possible brick. Your issues won't be solved just by rooting, those issues are typically kernel, hardware, and rom related.
Sent from my LG-H910 using XDA Labs
I am talking about using it as a phone on any carrier besides Sprint. Yes, once rooted, you can turn it into a fine tablet -- it is phone calls that I was referring to.
If it works fine for you now making phone calls, then it will continue to do so. The lag can be fixed.
-- Brian
cnjax said:
If you follow his other threads you'd know he's been working on a root solution for the 997 so be patient otherwise if you want be risky he has a thread here seeking volunteers to test just know you due risk a possible brick. Your issues won't be solved just by rooting, those issues are typically kernel, hardware, and rom related.
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
I have been following the LAF exploit thread for a long time, and very happy to see that he have come back and opened another LS997 rooting thread. But you know, my concern is about performance of the phone; will be improved with another kernel / rom or not.
---------- Post added at 05:33 PM ---------- Previous post was at 05:30 PM ----------
runningnak3d said:
I am talking about using it as a phone on any carrier besides Sprint. Yes, once rooted, you can turn it into a fine tablet -- it is phone calls that I was referring to.
If it works fine for you now making phone calls, then it will continue to do so. The lag can be fixed.
-- Brian
Click to expand...
Click to collapse
Thank you Brian for this good news ^_^
I did, and I did,and your advice was very correct. I like my H918 more than the LS997.....
I'm a happier guy for having followed your advice.....
Sorry... I was responding to the person who told me to get a 918
So I've had this for a few days now and I've noticed it's dropped connection quite a few times, and when, IF it reconnects without rebooting, it usually gets stuck on H+.
I'm currently on OOS 10.3.0. Tried a custom ROM, same issue. Tried regarding to 9.0.11, same issue. Bought a new SIM card, same issue. I'm thinking I have to get back to the T-Mobile 9.0.16 and send this back. I'm getting sick of this. Anyone have any ideas what the issue could be?
Sorry you are having so much trouble. This won't help, but my 6T global model (not T-mo) is the best reception phone I've ever had, at least on the ATT network.
It's hard to tell whether your problem is hardware based, something to do with the T-mo to global OS transition, or something else.
I have had it a full year and have no plans to swap it any time soon. I'm stock, unrooted (first time ever), and still on Pie for now, having deferred the update until it settles in a bit.
Good luck whatever you decide to do!
Sent from my ONEPLUS A6013 using Tapatalk
Signal is still dropping!
I'm having second thoughts about this phone. Two SIM cards and several calls to my cell provider and still no fix in sight.
I'm gonna see if the Swappa seller will send me a replacement.
Sounds like a problem with the hardware and pursuing a replacement is the right move. I had similar issue with a Samsung phone years ago.
Sent from my ONEPLUS A6013 using Tapatalk
Frankenscript said:
Sounds like a problem with the hardware and pursuing a replacement is the right move. I had similar issue with a Samsung phone years ago.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I thought that as well when I read the first post. However, I would try one more thing.
I would break out the MSM Tool, and completely flash back to 100% stock. Then I would test it again. The issue he is describing could actually be due to a mismatch in firmware partitions. Possibly that is, I dont know that for a fact. I would give it a try. That tool has fixed countless errors that I "may or may not have" induced by poking around.
Scott said:
I thought that as well when I read the first post. However, I would try one more thing.
I would break out the MSM Tool, and completely flash back to 100% stock. Then I would test it again. The issue he is describing could actually be due to a mismatch in firmware partitions. Possibly that is, I dont know that for a fact. I would give it a try. That tool has fixed countless errors that I "may or may not have" induced by poking around.
Click to expand...
Click to collapse
I did exactly that, back to T-Mobile firmware, and the issue still existed. So I returned the device.