Related
Why my LG Optimus 2X freezes and/or reboot?
Most of us have the same problem, we are trying to find a solution. In the meanwhile we can solve only removing battery.
Is it related to baseband version?
It does not seem related to baseband version. The problem is present in last baseband versione too:
1035.21_210110405
FRG83G
V10b
Is it related to ROM Version?
Apparently it happens on both stock and custom ROMS
I read that it is due to wall charger problem
Some of us have the same problem recharging both from USB PC and Wall Charger
I read this is due to overheat problem
Some of us still have the problem in standby mode with battery under 25° C.
LG told me to ask for a replacement
Some of us did it and had the same issue on the replaced phone.
I read it is due to hidden menu/car navigation/ecc. ecc.
There are no prooves about it.
Could it be a ROOT problem?
No. Same thing happens on both rooted and original phones.
I got it. It's a SD problem
Some of us has this problem both with or without SD card
So it's a HW problem
We are not sure about it. Most of us (me too) think this is a SW related issue. Some other thinks about a HW one.
Anyway it looks like a Nvidia/Tegra related problem.
It happens on Motorola Atrix too:
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
So: what can I do?
Follow this thread and partecipate
Try to install latest version v10b and do a full reset.
Try to uninstall the "Any cut" application.
Try removing your SD.
NOTE: These are temporary solutions while we wait to understand something more.
Nothing else?
Sure, you can add informations here to keep updated the FAQs.
What about contacting LG?
It looks like something is moving and a new update will be released soon:
http://translate.google.com/transla...alligevel-problemer-med-optimus-2x,lid.15324/
Hey, new V10C is available. Does this solve?
Not sure yet. Some of us still have problems, but some others solved with this upgrade.
How can I help?
You can sign this petition on line
http://www.petitiononline.com/LGO2XPrb/petition.html
Last updated: Tue 7th July 2011
Mine has now shut down 3 times while i was in a call, battery pull on each occasion to rectify the problem
Added in the first question that pulling off the battery temporary solves.
1 week ago I do faced 2 time reboot each after receive sms during standby mood.
Dont know what happen.
Later I remember the reboot problem started after I had installed "Any cut" sw and started to activate the hidden menu.
Then I uninstall it and now haven facing any reboot no more.
Already 1 week pass and no reboot at all. I also never restart my O2X yet and seem everything is OK, no lag or etc on the system.
Hope this help.
Was using the original lg rom only for a good day and had one shutdown. Switched to custom rom and didnt have a reboot or shutdown yet in over a week. Appears to be software related.
Sent from my LG-P990 using XDA App
Useful topic, thanks!
My experience in 15 days of use.
with stock rom V10a and external sd:
- 1 time screen locked black in a warm day during standby
with stock rom V10a without external sd:
- many times screen locked black just after a notification (almost always after sms incoming notification)
with official rom V10b without hard reset and without external sd:
- 1 time reboot after pressing power button to exit from standby
- 2 times screen locked black the day after I've changed the useragent setting from the hiddenmenu and installed "AutomateIt" app
with official rom V10b after a hard reset 2 days ago and without external sd:
- no problem till now (2 days of use)
All the time I used both original charger (at home) and a generic usb adapter with an output current of 1mA (at office).
This is the sort of stuff that should be sent to LG to deal with. Not the idiots at call centres but the people who made the phone and get them to work on it.
Problem with these phone guys, they make a phone and then just stick out to the salesman and then when things like this happen to everyone we get no support or real contact.
It's always send it for repair. The phones are like a month old and that is really a valid response?
Time LG were held accountable (as well as other company's)
Ok, added some "Possible solutions"
Good thread, will hopefully cut down on some of the idle speculation that has been going on!
I believe that it is a software bug, namely in Nvidia's cpufreq-dvfsd driver. I saw this process misbehaving when doing a 'top' command via an ADB shell after it froze, and I'm not the only person to have witnessed that. I've posted that info over at MoDaCo.
As kholk is the only person other than Paul I know around here who might be familiar with a Linux kernel, I've asked him to take a look. Not sure what will come of that, if anything.
And just to add fuel to my argument that this is a Tegra/Nvidia issue, and *not* necessarily an LG one, check this out (from Moto Atrix forums):
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
Read from the postings that, for charger-specific reboot/lockup problem, it might be better charging from a computer USB port or a charger with lower current output (I think someone is using as low as 350mA).
Fyi, I've never had AnyCut installed and I've had these problems.
Yup, we do not have still found THE cause, but some events.
We are trying to understand if they are related to the issue.
I am reporting infos from the other thread and from this one to help people ti find a partial solution.
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
follo said:
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
Click to expand...
Click to collapse
Not necessarily. In embedded/real-time systems, timing is crucial and in some components varies according to manufacture tolerances, heat, etc. Also everybody's phone has different apps and they do things at different times so you can't say that everybody's phone is just "the same" as everyone else's.
And this bug could well be one that only happens for some very specific condition that the original developer didn't forsee when he wrote that code or tested it. But the law of chance means that so many of us are seeing it - some more than others, and some days worse than other days.
So this would explain why people think that doing something like switching launcher or taking out an SD card might be solving or making the problem worse, because every action can and does change the likelihood of this specific condition occurring by changing how the phone behaves overall, workload, sleep time, etc etc. And why all these "solutions" that people are posting are so random and unrelated but each person is convinced that theirs is the one that works!
Basically, we need more evidence from logs to see what is really going on...
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
mikeyd85 said:
Fyi, I've never had AnyCut installed and I've had these problems.
Click to expand...
Click to collapse
Im not an expert, but its work for me. I will keep you all updated if reboot happen again.
Edit: just having my FB hang in 15 second and force to close. This definately due to sw problem.
Sent from my LG-P990 using XDA App
i will believe only when i will see one
spawndk said:
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
Click to expand...
Click to collapse
they said that gingerbread update will be on 18 april to and didnt
They said jun/jul. Check out dk site.
lmerega said:
They said jun/jul. Check out dk site.
Click to expand...
Click to collapse
Well thats the most realistic schedule
Hi,
My daughter is using the i8190.
The device is self rebooting itself, on an unknown basis.
The device was never rooted, and is using the original stock ROM (Android 4.1.2).
Nothing was installed recently.
The main suspect was the availability of free storage, but there is 1.07 Gigs of available storage, which is reasonable.
Another suspect is Whatsapp, in which she gets thousands of messages per day.
Any ideas what can cause those reboots?
Thanks!
amir77a said:
Hi,
My daughter is using the i8190.
The device is self rebooting itself, on an unknown basis.
The device was never rooted, and is using the original stock ROM (Android 4.1.2).
Nothing was installed recently.
The main suspect was the availability of free storage, but there is 1.07 Gigs of available storage, which is reasonable.
Another suspect is Whatsapp, in which she gets thousands of messages per day.
Any ideas what can cause those reboots?
Thanks!
Click to expand...
Click to collapse
It can be a cause of a used battery. Take it out and se if if it wobbles on a flat surface. If it does, replace battery asap.
There can be more reasons for this to happen, but battery is most likely to be your problem since it's not rooted or anything.
Don't know about Whatsapp, but maybe try to remove it a day or two to see if there is any difference.
The battery seems to be just fine.
I'll try to remove whatsapp (and disconnect my daughter from her friends world.. Hahaha..).
Hi
I had the very same problem with my stock ROM (4.1.2 also). Since I rooted and changed ROM I've seen these way less than when running stock.
A fiend's girlfriend had a major issue with her battery, it began to inflate to the point it can't be held on the phone. He bought her a new one and problem solved.
So my conclusion here is that S3 Mini's batteries are defective. They are cheap to replace, though. But now I confirm my suspicions.
The battery seems to be just fine, no visible inflates..
Currently, I've asked my daughter to remove some photos and I'll also remove whatsapp.. and see who the device will work
I would check my battery as I have a similar issue
Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Rooted?
You mention in the title that the phone is rooted. To be able to discount hardware errors, have you tried flashing a factory image to set it back to stock? If the same problems continue, then I suggest that you return it to Google. I did this myself when the back of my N6 started to peel and the process was painless, since they send you the new phone before you return the old one, so you lose no airtime.
saraddictive said:
Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Click to expand...
Click to collapse
Yes, as mentioned, flash a factory image to rule out any software issues. However, it is most likely hardware failure. Especially the camera fault. I've noticed this is becoming a rather common issue lately. So, you should probably RMA again.
Thanks guys. I was just concerned as I unlocked the bootloader and rooted the phone almost immediately after I got it. If I try to RMA it, they won't cry foul over a re-locked boot loader,will they?
Also,I have a feeling this might be an OTA that is acting up. It appears that loads of people have had issues after installing an ota (I did this before unlocking and rooting) so I'm going to try to flash a factory image. Thanks guys
Hello everyone,
as an update, I did exactly as dahawthorne and evolution_tech said, and re-flashed a factory image. However, i found it extremely strange that both my nexus 6s were experiencing the same issue so i did a little research.
Turns out, many users from 5.1 have been experiencing issues with changing their dpi in android 5.1 and above. Because I'm not all that familiar with build.prop and using adb shell (tried using it once, it wouldnt work properly so i just gave up), im not going to bother changing my dpi and it works all fine and good now.
To anyone else experiencing the same issue, check this page out: http://forum.xda-developers.com/nexus-6/general/dpi-conflicts-lmy47e-t3061261.
Cheers
Yep, well known issue.
So recently my Note 4 decided it's time to make my life hell and it's slow, buggy, and all around a terrible performer. I don't know what has caused this.
I've flashed the stock rom in odin, no improvement. No matter the ROM, kernel, root/noroot, it's still buggy and slow. Abnormally slow. Screen locks randomly, apps freeze up very often, etc. Honestly I'd like to just give up and get a new phone - but I don't have the money. Is there anything I'm not considering? To me it feels like I've done everything and I'm tired of dealing with this.
It's either being very slow, randomly locking, or straight up getting in a bootloop for 15 minutes and coming out like "yumad".
Just an update - I started getting random crashes where it complained about the EMMC. So I googled the exact code and it's very apparent my phone has a bad motherboard (bad flash storage, to be exact). So I've replaced it. Consider this thread done.
tannerzion said:
Just an update - I started getting random crashes where it complained about the EMMC. So I googled the exact code and it's very apparent my phone has a bad motherboard (bad flash storage, to be exact). So I've replaced it. Consider this thread done.
Click to expand...
Click to collapse
My phone is having similar problems as well...it randomly reboots then takes forever to reboot. Where did you get the motherboard? Did you replace it yourself or take it to a repair place?
Thanks
tsdsbrk said:
My phone is having similar problems as well...it randomly reboots then takes forever to reboot. Where did you get the motherboard? Did you replace it yourself or take it to a repair place?
Thanks
Click to expand...
Click to collapse
I replaced the phone. Not the motherboard. I plan on getting rid of the Note 4.
Yeah, I'm not so sure it's the motherboard and lots of people have been having this issue.
I literally have the exact same problem as you and posted a few days ago.
http://forum.xda-developers.com/note-4-tmobile/help/whats-wrong-note-4-slowdowns-galore-t3317254
is there something else at work?
cuteman said:
Yeah, I'm not so sure it's the motherboard and lots of people have been having this issue.
Click to expand...
Click to collapse
Mine is an original Note 4 and I have never had any problems, but before I install a new ROM, I always do a complete wipe of the Internal storage, including an fstrim of the system, data and cache. This may seem excessive to some, but I never have had any problems.
So I rooted my G4 a week ago. Everything was fine, was running a stock rom, no issues whatsoever. So today, I was watching a YouTube video when my phone froze. Couldn't do anything, had to pull the battery. Then it wouldn't come on after putting in the battery. I pulled it again and left it out for about 10 mins, put it in, put it on a charger and it started charging. Turned it on, the date/time was wrong, kept saying it was July 21st and 2:38 pm. Went into settings and updated the date/time; was working after that.
I left it on the charger and went on with my day. Came back and the phone was completely off, no charging LED. So it's been like this all day, it won't charge (at least the LED indicator doesn't come on), won't turn on, nothing. I figured the battery was shot. I went over to my buddy's (he has the same phone) and tried his battery in mine, nothing. I tried my battery in his and it worked, so I've established it isn't a bad battery. I've tried everything so far, keeping the battery out and holding down power so it resets it's charge, EVERYTHING, etc.
When it did come on and it was displaying the wrong date/time, that was the day I rooted it and about the time it was rooted too (2:38 pm). So, has this happened to anyone else? Am I bricked/screwed? I just don't understand why it would just die all of a sudden. It's well taken care of, no damage or anything. I really don't know what to do, I'm in a rough spot right now and not having a phone is really going to make things even worse.
Was just curious if somebody could help me with this or has any other info.
Thanks in advance!
I'm going to try the Unbrick Guide on here, hopefully that works.
So I was able to get it into download mode but then it died on me. The battery only had a 40 percent charge and now it won't do anything (again). Does the battery need to be charged at least to 50% or more in order to get in into download mode?
Though the classic bootlooping issue is just that--the phone locks up and freezes, and then on restart continuously reboots to the LG logo--the underlying problem causes a whole spectrum of conditions. For example, some affected phones will just shutdown during boot, and not continuously reboot. The stage at which the shutdown occurs is also variable--it can happen before the LG logo appears, after it appears, after the carrier logo appears, etc. The point is that the bootloop issue is not always expressed as the classic continuous rebooting to the LG logo issue. What you describe with your phone definitely falls within the spectrum of what is possible so I am going to guess that you have been hit with the bootloop issue like many others.
This just happened with my wife's VS986 after 1.75 years of flawless service. She was using it last week, then bam, it froze up, and after that it was dead. On trying to restart it immediately, it was completely dead. But by letting it sit around for a while to cool down, it could boot to the LG logo and sometimes would do this 2-3 times before shutting down again. By placing it in the freezer to really cool it down, I could boot up past the Verizon logo, but then during the Android optimizing apps screen, it would fail again. So out of the blue--after 1.75 years of perfect service--bam, it was struck with the bootloop issue.
Though I had seen mention of the bootloop issue previously, I never really investigated it till my wife's VS986 was strickened. If you do a search on it, you will see it is extraordinarily common...
Fortunately, LG is now taking responsibility for this though they were basically denying there was a problem initially. The good part is that they are repairing phones with this particular issue for free of charge even if they are out of warranty. In my case, my wife's VS986 was clearly out of warranty, but when I called up LG and explained the problem, they said they would repair it free of charge. So they steered me to the lgmobilerepair.com website to set up repair service.
They supposedly fixed my VS986, and it is now being shipped back. Curiously, they identified the problem as "Unit is not charging with cable" with the repair being "Swap Board (Main/RF) : Others". By the way, this was definitely NOT just an issue of not charging--I have an H811, and on putting my H811 battery into the VS986, the VS986 had the same problem. And on putting the VS986 battery in my H811, it worked perfectly. Whatever the case swapping the mainboard is the solution, and they did that, so they can call it whatever they want.
Anyway, do a little bit of searching on the G4 bootloop issue, try the freezer test, etc., and I am guessing you will also become convinced your G4 has been hit by the bootloop issue. If so, call up LG, explain the problem, and I bet they will offer to repair it for free. Hope this helps, and do let us know the results!
Awesome response! I'm aware of the class action against LG, but with my phone being rooted I don't think it's the best option to contact them and it's out of warranty. I do not have a bootloop issue, my issue is I cannot get the phone to go into download mode. I really hope it isn't a main board issue like you had, that means I have no way of fixing it.
I was able to get the phone into download mode, this was right after I connected it to the PC via USB and held the volume down button while connecting it, it just came on. I was able to get to the T-Mobile splash screen then it started making a weird noise (almost like PC when it locks up, a high buzzing sound). I was able to then get it into DL mode (holding volume up while connecting) but it died on me during that phase or froze. After pulling the battery then, it will now not do anything. I'm optimistic that if I can get it back into DL mode I can flash the stock KDZ and get it working again. I will let you know what happens. After spending almost all day messing around and hassling my buddy for his battery (same phone, he charged his battery to 100% and let me use his, he's using mine) I'm going to have some beers and play Titanfall 2. I'll pick it back up tomorrow. Worst case is I have to get a new phone and I just don't have the means of doing that ATM.
Regarding your phone being rooted, my wife's VS986 was rooted as well. This did not even come up in conversation with the LG. Even though her VS986 was clearly out of warranty, as soon as I started to explain the symptoms I was seeing, the LG rep (without mentioning the word "bootloop") said he recognized the problem, and that they would repair it for free. In sum, at least in my experience, having the phone rooted did not make one iota of difference. I guess the takehome message is that this issue has obviously reached levels far greater than the average 5% electronics failure rate--LG recognizes it is a hardware problem, and is prepared to deal with it (even on rooted and out of warranty devices).
You said your phone does not have the bootloop issue, but I invite you to investigate it further because the bootloop issue is not strictly confined to continuously bootlooping as I tried to explain originally. What you have described completely fits within the spectrum of observed issues related to the bootloop issue. Question for you--when you turn on your phone, is it normal that it shuts off at some (whatever!) stage of booting? You said that at point you actually got into download mode, but then it failed there--is that the normal/expected reality? No, it's not, and this behavior is definitely one type of expression of the bootloop issue... And as you reported yourself, you boot seem to fail at a range of different spots, not always consistently at the same moment. If it were a software problem, wouldn't it always happen at the same stage? That it happens at different stages of the boot process suggests an external control, i.e. a hardware issue.
You asked about the freezer trick--let me roll things back a bit, and I'll get to this in a minute. The bootloop issue is supposedly related to a failed electrical connection for a component on the phone mobo, and so how far along the boot process actually gets before failing gets is related to thermal expansion of components, at least this is my guess. As I mentioned, when my wife's phone originally locked up, on trying to restart it immediately, it was completely dead, no LG logo no anything. But after letting it sit untouched for a couple hours to cool passively, the boot process would at least advance up to the LG logo, but then fail. After this, if I tried to reboot again while the phone was still warm, again, complete failure (not even reaching the LG logo) until I let it sit and cool for a while. This is all related to the freezer trick...
I read that on freezing their phones, some people were able to boot as far as the homescreen, and have a few minutes to rescue their contacts and photos before subsequent failure. So I tried that with the VS986, and was even able to get past the Verizon logo as mentioned above. But failure occurred during the optimizing apps stage, and I could never reach the homescreen. Whatever the case, this freezer trick simply works because of thermal contraction--by cooling the phone down enough, the components contract rebridging the failed electrical connection, and if it can can stay cool enough for long enough, you might actually have a few minutes to rescue things before failure.
There are some other data rescue techniques, too, and though you do not seem to be concerned about rescuing data, I mention them because they also point to this thermal issue. In particular, besides freezing, some folks have tried exactly the opposite--intense heating--and they have been able to get a few minutes of data rescue time out of their phones. This involves heating the back of the phone with a hair dryer until it is close to burning hot, and then trying to boot. This certainly works because of thermal expansion--heating the phone up so much causes everything to expand which literally forces the components back together bridging the failed electrical connection temporarily until the component heats up internally, and overcomes this extra pressure.
Another data rescue technique involves adding a spacer above the CPU to cause more force pressing down on the component to bridge the connection failure. And some people have literally ironed their CPUs in attempts to resolder things, and have had various levels of success. But in the long run, all of these attempted repairs to phones with the bootloop issue have the common characteristic of rebridging the failed component connection temporarily, and that is key here--they are only TEMPORARY. They work for anywhere from 1.) not at all to 2.) a few minutes to 3.) a few hours to 4.) a few days, but in the long run, they are temporary, and mobo replacement is needed.
Anyway, I encourage you to investigate the G4 bootloop issue a bit more before you conclude that your phone is not affected. And furthermore, in the long run, if you do conclude that it is afflicted by the bootloop issue, contact LG about it, and they will probably repair it for free. Don't fear about being out of warranty or having rooted the device--at least in my case these things did not matter!!!
---------- Post added at 11:53 AM ---------- Previous post was at 11:47 AM ----------
I have reread your description above, and now even more think you may have the bootloop issue! You wrote that you were able to get into download mode, but then it failed, and then it would not do anything. This is exactly my experience with the VS986--immediately after a failure when it was still hot, if I tried to restart it, bam, nothing, not even the LG logo. But if I let it sit around a while to cool, it then was willing to show some semblance of life. Let your phone sit around after the next failure to cool down a bit, and I bet that after that, again, you will start to see a few indications of life instead of it being completely dead. If so, this should convince you even more that this is a hardware-level issue, and not simply a matter of being able to get into download mode to reload the OS.
Well I let it sit without the battery for about 14 hours, tried it again today and nothing. It won't turn on, won't charge, no LED indicator, no download mode, no safe mode, nothing lol. I'm convinced it's completely dead at this point.
MTN927 said:
Well I let it sit without the battery for about 14 hours, tried it again today and nothing. It won't turn on, won't charge, no LED indicator, no download mode, no safe mode, nothing lol. I'm convinced it's completely dead at this point.
Click to expand...
Click to collapse
A suggestion--remove the back cover and battery, put the bare phone in the freezer for an hour in Ziploc bag, then pull it out, immediately put in the battery, and see if you can get some sign of life out of it. Obviously, this is not a long-term workable solution, just an experiment to see if you can get any signs of life out of it at this point. When you finally decide to let it warm up, do so while it is in the sealed Ziploc bag so it avoids direct condensation.
Whatever you conclude about your phone, the G4 is still a nice piece of equipment with a great camera even though it was released over two years ago. So repairing it is worth the effort if LG will do it for free. If you live in the US, their contact number is 800-243-0000. I'd suggest calling them up, explaining that out of the blue, the phone locked up, and since then, even though you have been able to do partial reboots a few times, it would always shut off during one of these boot attempts. Now it doesn't boot at all. There is no reason to mention that you rooted your phone a week ago (unless you want to...) because again, this is a well-known hardware problem that they know about, and that they are repairing even for phones that are out of warranty.
Admittedly, sending the phone in for repair is a bit of a hassle. In my case, I had to foot the shipping bill out to the repair facility in Ft. Worth, TX, but the turn around time was super fast. Indeed, it arrived to the facility this past Monday according to tracking, but was not actually checked in to their RMA system until Wednesday night. Notwithstanding, by Thursday evening, they had diagnosed it, replaced the mobo, and put it into Fedex shipping back to me all at no cost! I expect you would have a similar experience if you contact them to explain the problem like I have suggested.
Good luck, and let us know how the saga ends!
Your freezer trick worked! For now at least, I have the phone in DL mode but the KDZ I tried to flash gets stuck at 9% when using LGUP, I think I need to find the right KDZ to flash, looking for that currently...
UPDATE: Dead again, lasted in DL mode for maybe 10 or so mins. If that KDZ I had was right it might've worked, gonna refreeze and try again with a different KDZ...
So MTN927, I think the evidence is pointing to a hardware problem... It seems that you are thinking that this is a software-level problem, and that by reloading the correct KDZ, the phone will return to normal. Why would freezing the phone have any effect on a software-level problem? Of course, freezing the phone could clearly have an effect on a hardware-level issue.
I am not really a betting man, but at this point, I suspect that even if you find and load the correct KDZ, it will not solve your phone's problem because it appears to be a hardware-level issue. Whatever the case, give it a shot, and here's to hoping my logic above is incorrect!
Here is a possible technique that might give you a few more minutes to load a KDZ--after you freeze the phone, don't take it out, just let it sit there. And then, run a USB cable into the freezer to plug into the phone. I'm not sure it will buy you much more time, but maybe it will be just enough to get a KDZ loaded?
That's what I'm thinking, hardware and not software now, obviously.
I suggest you investigate the possibility of LG fixing it for free. Though it's a hassle to be without your phone for 1-2 weeks, at this point it's not working anyway so what do you have to lose? The G4 is still a great piece of equipment so repairing it is worth the effort.
verbage said:
I suggest you investigate the possibility of LG fixing it for free. Though it's a hassle to be without your phone for 1-2 weeks, at this point it's not working anyway so what do you have to lose? The G4 is still a great piece of equipment so repairing it is worth the effort.
Click to expand...
Click to collapse
Yea, that's gonna be the last resort. I'm checking to see if I can get a new phone right now with my carrier. Thanks for all your help though, you've been great. Honestly, if I can get it fixed for free then sure, but I'm not too confident in the phones future considering what's already happened.
MTN927 said:
...but I'm not too confident in the phones future considering what's already happened.
Click to expand...
Click to collapse
I will not be any less confident with my wife's repaired VS986, in fact, given that they replaced a known defective component, I think I will be more confident! Good luck with your replacement--here's to hoping your carrier is willing to help out given the G4's known history.