tl;dr: My chronology of the infamous LG V10 boot loop death which got repaired under LG's unannounced extended 15 months warranty. Important lesson learned is make sure to back up all the phone's valuable data (even though I technically didn't lose anything critical).
01/03/2017: I finally experienced the infamous boot loop of death with my AT&T LG V10 yesterday (01/02/2017). The boot loop I encounter isn't due to flashing gone bad or wrong, but due to regular use. My phone wasn't excessively overheating at the time, but I do know that the metallic ring around the power/finger print sensor was warm due to surfing the internet at the time on Chrome. I do have a tempered glass on the phone and a slim translucent plastic cover to protect my phone. What happened was that my phone suddenly just powered off the display screen. I thought the phone just experienced a force close and forced reboot, not that I ever experienced one with the V10, but other Android phones before (i.e., very old ass Android phones). But I waited for the phone to boot up, but it never did. I tried to reboot the phone and then that's when it got to the home screen and locked up. Ever since then, reboots failed to get pass the AT&T logo, but could pass the LG logo.
I've already tried the refrigerator/freezer trick to cool down the phone, but it appears that I'm passed that stage where the phone would not boot pass the LG logo or AT&T logo. The more I tried to get the phone to boot up, the more it will just stall or reset at the LG logo, or refuse to boot up (i.e., speed up its death). Even the charging screen once showed, no longer reaches the charging stage where it shows the percentage of the battery's power remaining through the wall charger or being plugged into a computer laptop. Pulling the battery and letting the phone sit idle (to cool down the internal circuits?) for a while will allow it to come back to life with the boot loop problem or the ability to charge the battery via a computer's USB port. I tried charging with the wall adapter, but that forces the phone to boot up, and render the phone useless thereafter, so I elected to charge the phone via computer.
My AT&T LG V10 (H900 variant) is on Android 6.0 (H90021w00). It's not rooted anymore due to upgrading to Android 6.0 (I updated back in November 2016 here) without issue and wasn't abused (e.g., phone dropped, water damage) for it to cause the boot loop of death. The hardware version (H/W) is 1.0 with the SKU 6084A. Battery manufacturing date appears to be 2015.11.07 (D). The OEM package boxing has DHHS Code MC1, manufactured date of 12/2015 and made in Korea.
I wanted to try and save some data off of my phone, but the phone couldn't stay on life support long enough. Of course, fastboot won't allow me to save data (it's design is to write data only). I did manage to put the phone into download mode (i.e., phone powered off, hold down volume button and plug in USB cable from computer) one time and try to flash an upgrade of Android 6.0 firmware H90021w00 with LG Up, but it failed somewhere after 10%.
Good thing I have Google Photos backing up all my photos and videos, and nothing critical resides on my phone other than auto logins. I'll just have to change all my passwords soon enough if my phone has to be taken away for warranty. I wanted to at least save data and do a data wipe to make sure that nothing falls into the wrong hands. But I now can't do any of the two. I called the nearest AT&T corporate store, but was directed to one that has a warranty center. I will be on my way to an AT&T corporate store later tonight that has a warranty center. Just doing so to avoid traffic. I know my phone has the usual 1 year warranty, and speaking to the AT&T corporate store with the warranty center, I was told that I have at least 80 something days left of warranty. So good thing I'm not screwed and can at least get a replacement phone.
Currently the phone is sitting on my desk charging at a slow ass rate and up from fluctuating anywhere between 12% and 21% to a now whopping 30% power capacity. I want to at least demonstrate the boot looping to AT&T personnel and it's not due to physical damage or water damage. I'll report back what's happening with my situation so that way, anybody else who experienced this situation will have something to go by.
Update 01/04/2017: I read through the freezer trick thoroughly this time and the entire thread. I decided to try it again, but this time, I left the phone in the freezer for a short time (half an hour or so) without the battery. After time elapsed in the freezer to cool down the phone, I plugged in the USB to the phone while having my laptop near the refrigerator with LG Bridge loaded and ready to back up, and then put in the battery. Lo and behold, the phone did manage to boot up all the way to the lock screen, due to various sound cues from the phone (AT&T logo) and USB connectivity (from Windows 7). However, when I tried to unlock the phone, that's when it froze and rebooted. After that, it hit the boot loop and won't get as far as the initial try. So I'll keep trying to revive my phone long enough to get some data off of it and wipe it clean. I still have time with warranty, so I'm in no hurry. Besides, I attempted warranty processing last night and missed the opening as the warranty department closed early.
Update 01/11/2017: I managed to get my LG V10 phone to boot up further than the freezer trick by utilizing the hair dryer trick here. Basically, what the video shows is that one must take a hair dryer, blow dry on the highest heat setting to the bottom of the backside phone up to the point where the phone gets hot, without the battery for over a minute. After that, put in the battery, boot up the phone and blow dry the bottom of the phone and heat it up even further while it's booting. I had to repeat the hair dryer heating process many times in order to stabilize my phone because it would reboot within minutes after I try to initially back up with LG Bridge's LG Backup tool. I did manage to overheat the bottom part of the phone so much that Android denied charging the battery via USB connected to the computer. Further exacerbating the problem was that the battery was so hot, LG Bridge denied backup because it thought the battery charge status was under 30% when in fact, my LG V10 showed at 49%. I did get the most important file that I was after on my phone after many tries (kept rebooting on me), but I'll persist to back up the entire phone in case I needed something else before turning this phone over to AT&T warranty service.
Update 1/19/2017: As much as I tried to back up my LG V10 and wipe afterwards, my attempts were futile. The phone couldn't stabilize enough after reaching the home screen, and would reboot shortly thereafter. At least I got what I've wanted. When I kept trying to revive it with the hair dryer trick, it just wouldn't go pass the boot screen most of the time (i.e., LG logo or AT&T logo). It even got to the point where it would turn on slowly (i.e., there's a delay booting up when power was pressed on). So at this point, it appears that the boot loop of death is sinking in further into my LG V10. I also tried the freezer trick again and then going back to the hair dryer trick when the freezer trick stopped working, although not back to back, otherwise that would provide temperature shock to the components. The freezer trick did manage to get further, but it only happened twice where it got to the home screen and then rebooted. Note to those wondering if condensation would trip or activate the moisture sensors on the phone and the battery, it does not when you take careful steps of taking the phone out of the freezer and putting it into the refrigerator and then take it out, letting maybe 10 minutes pass by for each step of temperature transition so that the phone's temperature can get to room temperature without condensation buildup.
Anyways, I decided that I've spent way too much of my time trying to revive my phone to back up data that most likely I wouldn't need. I went the route of sending my phone to LG for repair instead of going to AT&T store and receiving a refurbished LG V10. I'd rather have my phone repaired by LG and receive my phone back with the repaired hardware than to receive someone else's LG V10. I based my decision on this thread here over at Android Central where someone sent in their phone for repair, got theirs back with a clean start (i.e., don't expect LG to either back up your data or reuse your memory storage as no personal data was saved). It is good to note that LG has extended LG V10 warranty of 1 year (12 months) to 15 months. I'm pretty sure LG granted a 3 month warranty extension on LG V10s due to the boot loop issue. I didn't realize I got the extension until thinking back, when I called AT&T warranty center, they told me I had about 86 days of warranty left, which is about 3 months extended from my 1 year of warranty when it ended. The phone was bubble wrapped (removed back cover, battery, SIM, microSD) and shipped off in a small box that I re-used from another item that was shipped to me. Shipping carrier is by FedEx Ground that was paid for by LG, being shipped to LG's repair center in Texas.
Update 01/24/2017: The phone has arrived at the Texas facility yesterday (Monday) according to FedEx, but the status of my repair hasn't been updated anymore than giving me estimated delivery date of 9 days. What's odd is that LG didn't update the received date at repair facility field and have deleted my FedEx tracking number.
Update 01/25/2017: LG updated the repair status last night which pretty much acknowledged item received, diagnosed, repaired, and prepared for shipment back to customer. The repair was "Swap Board (Main/RF) : Others". I should have the phone back on 01/28/2017 and will update then accordingly. It appears that LG probably replaced the entire mother board which would include the 64 GB of memory holding user data, among others. Considering that others have reported of receiving a freshly formatted phone, I would expect the same once the phone reaches back to me. I would highly doubt LG went the extra length to migrate data off of the failing motherboard onto the new one. It would be nice if they did.
Update 01/28/2017: I have received my phone today via FedEx Ground shipping, and they delivered on a Saturday. The status of my phone was factory reset. I can tell it was factory reset because I still have the unlimited tethering (hotspot) enabled from the previous rooting (Lollipop) and then went to Marshmallow and losing the root, but still have unlimited tethering. Also, Android OS is updated to H90021x (from the previous H90021w00), build number MRA58K, with Android security patch level 2016-11-01. You will need to set up the phone just like you did the first time. They also removed my tempered glass and left a narrow sticky film that doesn't cover the entire front screen glass that can be peeled off. Good thing I have an extra tempered glass for the V10. The phone came back with the same serial # and ESN/IMEI that I've sent to LG. If you're like me trying to migrate data from one LG phone to another, it's best to use the LG Backup in Backup & Reset under Settings that's found native in the phone. LG PC Suite and LG Bridge won't work with Verizon's LG G4 (VS986) on Windows 7 for me, no matter what I did (installed many LG G4 drivers, including Verizon's). Some backup apps, such as LG Backup (Sender) and Super Backup & Restore do not back up everything, neither does the native backup LG Backup in the Android Settings menu.
Update 02/03/2017: What appears to be a puzzling action on my repaired LG V10 is that I'm going to take no chance and back up my phone in case I end up losing data again. What happened earlier was that I was surfing the Internet with Chrome, reading up on a news article, when I was prompted to Miracast and enter a PIN. WTF? I ignored it a few times and then it got to the point where my phone was unresponsive with the Miracast prompts, but I was able to force my phone to reboot. Upon reboot, I noticed that the phone loading up was sluggish and not typically responsive. I decided to shutdown my phone to prevent further irreversible problem in the future (hint: boot loop). I waited for my phone to cool down for perhaps a few minutes before I powered on the phone again. This time, when the phone booted up, it was responsive as it normally has. Before all this happened, I didn't use my phone excessively nor extensive in a short period of time. I really have doubts that LG really applied a fix to their faulty connection problem and just used a replacement just to pass by.
Update 02/04/2017: I received an e-mail from LG requesting my feedback with respect to the repair. I gladly answered the survey, gave them good credit with respect to the repair itself, but when it comes to the quality of the LG product, they took a hit and I expressed my concern with respect to the boot loop.
These bootloops have been happening quite a lot lately. Makes me worried.
Affangta said:
These bootloops have been happening quite a lot lately. Makes me worried.
Click to expand...
Click to collapse
I would suggest that anybody with a functioning LG V10 to do their due diligence and back up their data on the phone in case there's a catastrophic event such as the boot loop I've experienced. At least I have most of my data backed up. Just some that I disabled but now realize it's worth having.
It happened to me too on Nov 2016. I have been told to return the phone to AT&T and get a replacement phone under warranty. I did receive a replacement V10. Now AT&T pissed me off on changing the phone contact expiry date to next year. I am on AT&T Next 12 plan. I am supposed to get a new phone on January 2017, but now I have to wait till 2018. Next time, I am buying phone myself.
anand_pv said:
It happened to me too on Nov 2016. I have been told to return the phone to AT&T and get a replacement phone under warranty. I did receive a replacement V10. Now AT&T pissed me off on changing the phone contact expiry date to next year. I am on AT&T Next 12 plan. I am supposed to get a new phone on January 2017, but now I have to wait till 2018. Next time, I am buying phone myself.
Click to expand...
Click to collapse
A replacement phone under warranty should not extend your contract. Did you contest the contract extension? Under the warranty exchange, there's no mention of contract extension required: https://www.att.com/esupport/article.html#!/wireless/KM1044996
Its kind of best to buy the phone out right.
On AT&T Next. What ever payment plan you choose, you dont get to keep the phone until it is completely "paid off". Which pushing through the confuseing payments costs as well as additional costs, in reality your technically paying more then the phone sells for. So if you intend on keeping your next phone. Just go out and buy an unlocked version. Or get an unlocked international version.
Try baking it?
My wife's v10 started bootlooping about a week ago and is out of warranty. This happened right after doing a FOTA security update. I figured it was due to that so I tried resetting the phone but could not boot in to anything to get it to reset. After extensive searching and reading, I have "fixed" the phone so far. It has been booted up and running for almost 2 full days now. We are not using it at the moment, we had a spare phone so its not like we were going to be out of anything. Instead of the freezer trick (was not worried about data backup), I did the baking trick and as surprised as I was...it worked! Here is what I did if it might help anyone else.
Please note that your warranty will really be void after doing this, especially if anything gets damaged. The information here is reference only and results may vary due to altitude and baking temps (thought I would NEVER put that in a disclaimer for gadgets and software, lol). You may or may not have data loss either, so do not blame me!
You will need to take the phone apart so you will need a small precision set of screwdrivers. Check out the video from the link below to see how to disassemble the phone, you only need to get to the part where the circuit board is removed.
https://www.youtube.com/watch?v=7N_mGT-P1ZA
And now...seriously,
1. Pre-heat your oven to 385 F (~195 C).
2. CAREFULLY take the circuit board out of the phone, use the video above as reference.
3. Place the circuit board in the oven and bake for 7 minutes. I set my board on a baking rack so it was not directly on a cookie sheet.
4. Take circuit board out, shut off oven and let sit for at least 20 minutes to fully cool down. Add salt for flavor? (j/k)
5. After cool down, CAREFULLY place circuit board back in and put phone back together.
6. Put battery in and let charge if needed before booting the phone up.
7. Cross fingers and turn the phone on!
We were at a point to where we did not want to file a claim if we were going to end up with the same phone possibly again and have issues so I figured I would try it out. My kids thought I was insane watching me bake a circuit board.
However, the electronics knowledge in me knows this is just enough to actually do solder reflow on the board. From the numerous posts that I have read, it appears that some of the soldering is faulty and sometimes a reflow will fix the issue. Since circuit boards are so small and intricate, it takes extremely serious skill to actually use a solder iron to fix those...so for those of us who are not extremely seriously skilled in soldering, the oven seems to work. Don't get me wrong, I can solder like no tomorrow...but not on circuit boards
So if you have nothing to lose...give this a shot!
I had the same problem, I'm unsecured so I take a repair where a technician and told the hay processor to re-weld it because it got off the board.
Ten days ago, during an ordinary work morning, and without warning, my V10 entered the boot loop spiral of death. The unprompted reboots became more frequent, moving backwards from home screen, to AT&T screen, to LG screen, from where the phone eventually refused to proceed. I bought the phone during the first week of U.S availability in October 2015, so it's past warranty, of course.
I submitted a ticket at the LG website, and shipped my comatose V10 via FedEx an exact 27 miles across the DFW metroplex to the LG Service Center near Alliance Airport north of Fort Worth. The package arrived there the next day thanks to close proximity to local ground service, rather than making a fun trip to Memphis and back.
My V10 returned yesterday. I paid $72 + tax for out-of-warranty replacement of the main logic board, which we surely suspect to have failed because of the well-known factory defect that appears to have affected the V10, G4, and even the G3. $72 is still a fair price for this type of repair on a large premium smartphone. My software and settings were easy to restore after my having number moved back from my wife's old G2 to a new SIM.
Will it last? I hope so.
Your are genius, so does your kid will grow up the same way...
Hi John!
I register this forum just for the purpose saying " Thank You! You are genius"
I followed your step by step guide and brought up my LG V10 to life, which casued by the so called " boot loop" problem few days ago.
I was almost ready to send my V10 back to the LG, and requesting for the replacemnt of the internal board of my LG V10. Luckily, I read your thread, and presume that your assumption is right with logical analysis. Now my phone is working without boot problem, and I successfully bring back my data from the internal memory, too.
Thank you so much, John!
eddie.
johnkirchner said:
My wife's v10 started bootlooping about a week ago and is out of warranty. This happened right after doing a FOTA security update. I figured it was due to that so I tried resetting the phone but could not boot in to anything to get it to reset. After extensive searching and reading, I have "fixed" the phone so far. It has been booted up and running for almost 2 full days now. We are not using it at the moment, we had a spare phone so its not like we were going to be out of anything. Instead of the freezer trick (was not worried about data backup), I did the baking trick and as surprised as I was...it worked! Here is what I did if it might help anyone else.
Please note that your warranty will really be void after doing this, especially if anything gets damaged. The information here is reference only and results may vary due to altitude and baking temps (thought I would NEVER put that in a disclaimer for gadgets and software, lol). You may or may not have data loss either, so do not blame me!
And now...seriously,
1. Pre-heat your oven to 385 F (~195 C).
2. CAREFULLY take the circuit board out of the phone, use the video above as reference.
3. Place the circuit board in the oven and bake for 7 minutes. I set my board on a baking rack so it was not directly on a cookie sheet.
4. Take circuit board out, shut off oven and let sit for at least 20 minutes to fully cool down. Add salt for flavor? (j/k)
5. After cool down, CAREFULLY place circuit board back in and put phone back together.
6. Put battery in and let charge if needed before booting the phone up.
7. Cross fingers and turn the phone on!
We were at a point to where we did not want to file a claim if we were going to end up with the same phone possibly again and have issues so I figured I would try it out. My kids thought I was insane watching me bake a circuit board.
However, the electronics knowledge in me knows this is just enough to actually do solder reflow on the board. From the numerous posts that I have read, it appears that some of the soldering is faulty and sometimes a reflow will fix the issue. Since circuit boards are so small and intricate, it takes extremely serious skill to actually use a solder iron to fix those...so for those of us who are not extremely seriously skilled in soldering, the oven seems to work. Don't get me wrong, I can solder like no tomorrow...but not on circuit boards
So if you have nothing to lose...give this a shot!
Click to expand...
Click to collapse
hoang51 said:
tl;dr: My chronology of the infamous LG V10 boot loop death which got repaired under LG's unannounced extended 15 months warranty. Important lesson learned is make sure to back up all the phone's valuable data (even though I technically didn't lose anything critical).
01/03/2017: I finally experienced the infamous boot loop of death with my AT&T LG V10 yesterday (01/02/2017). The boot loop I encounter isn't due to flashing gone bad or wrong, but due to regular use. My phone wasn't excessively overheating at the time, but I do know that the metallic ring around the power/finger print sensor was warm due to surfing the internet at the time on Chrome. I do have a tempered glass on the phone and a slim translucent plastic cover to protect my phone. What happened was that my phone suddenly just powered off the display screen. I thought the phone just experienced a force close and forced reboot, not that I ever experienced one with the V10, but other Android phones before (i.e., very old ass Android phones). But I waited for the phone to boot up, but it never did. I tried to reboot the phone and then that's when it got to the home screen and locked up. Ever since then, reboots failed to get pass the AT&T logo, but could pass the LG logo.
I've already tried the refrigerator/freezer trick to cool down the phone, but it appears that I'm passed that stage where the phone would not boot pass the LG logo or AT&T logo. The more I tried to get the phone to boot up, the more it will just stall or reset at the LG logo, or refuse to boot up (i.e., speed up its death). Even the charging screen once showed, no longer reaches the charging stage where it shows the percentage of the battery's power remaining through the wall charger or being plugged into a computer laptop. Pulling the battery and letting the phone sit idle (to cool down the internal circuits?) for a while will allow it to come back to life with the boot loop problem or the ability to charge the battery via a computer's USB port. I tried charging with the wall adapter, but that forces the phone to boot up, and render the phone useless thereafter, so I elected to charge the phone via computer.
My AT&T LG V10 (H900 variant) is on Android 6.0 (H90021w00). It's not rooted anymore due to upgrading to Android 6.0 (I updated back in November 2016 here) without issue and wasn't abused (e.g., phone dropped, water damage) for it to cause the boot loop of death. The hardware version (H/W) is 1.0 with the SKU 6084A. Battery manufacturing date appears to be 2015.11.07 (D). The OEM package boxing has DHHS Code MC1, manufactured date of 12/2015 and made in Korea.
I wanted to try and save some data off of my phone, but the phone couldn't stay on life support long enough. Of course, fastboot won't allow me to save data (it's design is to write data only). I did manage to put the phone into download mode (i.e., phone powered off, hold down volume button and plug in USB cable from computer) one time and try to flash an upgrade of Android 6.0 firmware H90021w00 with LG Up, but it failed somewhere after 10%.
Good thing I have Google Photos backing up all my photos and videos, and nothing critical resides on my phone other than auto logins. I'll just have to change all my passwords soon enough if my phone has to be taken away for warranty. I wanted to at least save data and do a data wipe to make sure that nothing falls into the wrong hands. But I now can't do any of the two. I called the nearest AT&T corporate store, but was directed to one that has a warranty center. I will be on my way to an AT&T corporate store later tonight that has a warranty center. Just doing so to avoid traffic. I know my phone has the usual 1 year warranty, and speaking to the AT&T corporate store with the warranty center, I was told that I have at least 80 something days left of warranty. So good thing I'm not screwed and can at least get a replacement phone.
Currently the phone is sitting on my desk charging at a slow ass rate and up from fluctuating anywhere between 12% and 21% to a now whopping 30% power capacity. I want to at least demonstrate the boot looping to AT&T personnel and it's not due to physical damage or water damage. I'll report back what's happening with my situation so that way, anybody else who experienced this situation will have something to go by.
Update 01/04/2017: I read through the freezer trick thoroughly this time and the entire thread. I decided to try it again, but this time, I left the phone in the freezer for a short time (half an hour or so) without the battery. After time elapsed in the freezer to cool down the phone, I plugged in the USB to the phone while having my laptop near the refrigerator with LG Bridge loaded and ready to back up, and then put in the battery. Lo and behold, the phone did manage to boot up all the way to the lock screen, due to various sound cues from the phone (AT&T logo) and USB connectivity (from Windows 7). However, when I tried to unlock the phone, that's when it froze and rebooted. After that, it hit the boot loop and won't get as far as the initial try. So I'll keep trying to revive my phone long enough to get some data off of it and wipe it clean. I still have time with warranty, so I'm in no hurry. Besides, I attempted warranty processing last night and missed the opening as the warranty department closed early.
Update 01/11/2017: I managed to get my LG V10 phone to boot up further than the freezer trick by utilizing the hair dryer trick here. Basically, what the video shows is that one must take a hair dryer, blow dry on the highest heat setting to the bottom of the backside phone up to the point where the phone gets hot, without the battery for over a minute. After that, put in the battery, boot up the phone and blow dry the bottom of the phone and heat it up even further while it's booting. I had to repeat the hair dryer heating process many times in order to stabilize my phone because it would reboot within minutes after I try to initially back up with LG Bridge's LG Backup tool. I did manage to overheat the bottom part of the phone so much that Android denied charging the battery via USB connected to the computer. Further exacerbating the problem was that the battery was so hot, LG Bridge denied backup because it thought the battery charge status was under 30% when in fact, my LG V10 showed at 49%. I did get the most important file that I was after on my phone after many tries (kept rebooting on me), but I'll persist to back up the entire phone in case I needed something else before turning this phone over to AT&T warranty service.
Update 1/19/2017: As much as I tried to back up my LG V10 and wipe afterwards, my attempts were futile. The phone couldn't stabilize enough after reaching the home screen, and would reboot shortly thereafter. At least I got what I've wanted. When I kept trying to revive it with the hair dryer trick, it just wouldn't go pass the boot screen most of the time (i.e., LG logo or AT&T logo). It even got to the point where it would turn on slowly (i.e., there's a delay booting up when power was pressed on). So at this point, it appears that the boot loop of death is sinking in further into my LG V10. I also tried the freezer trick again and then going back to the hair dryer trick when the freezer trick stopped working, although not back to back, otherwise that would provide temperature shock to the components. The freezer trick did manage to get further, but it only happened twice where it got to the home screen and then rebooted. Note to those wondering if condensation would trip or activate the moisture sensors on the phone and the battery, it does not when you take careful steps of taking the phone out of the freezer and putting it into the refrigerator and then take it out, letting maybe 10 minutes pass by for each step of temperature transition so that the phone's temperature can get to room temperature without condensation buildup.
Anyways, I decided that I've spent way too much of my time trying to revive my phone to back up data that most likely I wouldn't need. I went the route of sending my phone to LG for repair instead of going to AT&T store and receiving a refurbished LG V10. I'd rather have my phone repaired by LG and receive my phone back with the repaired hardware than to receive someone else's LG V10. I based my decision on this thread here over at Android Central where someone sent in their phone for repair, got theirs back with a clean start (i.e., don't expect LG to either back up your data or reuse your memory storage as no personal data was saved). It is good to note that LG has extended LG V10 warranty of 1 year (12 months) to 15 months. I'm pretty sure LG granted a 3 month warranty extension on LG V10s due to the boot loop issue. I didn't realize I got the extension until thinking back, when I called AT&T warranty center, they told me I had about 86 days of warranty left, which is about 3 months extended from my 1 year of warranty when it ended. The phone was bubble wrapped (removed back cover, battery, SIM, microSD) and shipped off in a small box that I re-used from another item that was shipped to me. Shipping carrier is by FedEx Ground that was paid for by LG, being shipped to LG's repair center in Texas.
Update 01/24/2017: The phone has arrived at the Texas facility yesterday (Monday) according to FedEx, but the status of my repair hasn't been updated anymore than giving me estimated delivery date of 9 days. What's odd is that LG didn't update the received date at repair facility field and have deleted my FedEx tracking number.
Update 01/25/2017: LG updated the repair status last night which pretty much acknowledged item received, diagnosed, repaired, and prepared for shipment back to customer. The repair was "Swap Board (Main/RF) : Others". I should have the phone back on 01/28/2017 and will update then accordingly. It appears that LG probably replaced the entire mother board which would include the 64 GB of memory holding user data, among others. Considering that others have reported of receiving a freshly formatted phone, I would expect the same once the phone reaches back to me. I would highly doubt LG went the extra length to migrate data off of the failing motherboard onto the new one. It would be nice if they did.
Update 01/28/2017: I have received my phone today via FedEx Ground shipping, and they delivered on a Saturday. The status of my phone was factory reset. I can tell it was factory reset because I still have the unlimited tethering (hotspot) enabled from the previous rooting (Lollipop) and then went to Marshmallow and losing the root, but still have unlimited tethering. Also, Android OS is updated to H90021x (from the previous H90021w00), build number MRA58K, with Android security patch level 2016-11-01. You will need to set up the phone just like you did the first time. They also removed my tempered glass and left a narrow sticky film that doesn't cover the entire front screen glass that can be peeled off. Good thing I have an extra tempered glass for the V10. The phone came back with the same serial # and ESN/IMEI that I've sent to LG. If you're like me trying to migrate data from one LG phone to another, it's best to use the LG Backup in Backup & Reset under Settings that's found native in the phone. LG PC Suite and LG Bridge won't work with Verizon's LG G4 (VS986) on Windows 7 for me, no matter what I did (installed many LG G4 drivers, including Verizon's). Some backup apps, such as LG Backup (Sender) and Super Backup & Restore do not back up everything, neither does the native backup LG Backup in the Android Settings menu.
Update 02/03/2017: What appears to be a puzzling action on my repaired LG V10 is that I'm going to take no chance and back up my phone in case I end up losing data again. What happened earlier was that I was surfing the Internet with Chrome, reading up on a news article, when I was prompted to Miracast and enter a PIN. WTF? I ignored it a few times and then it got to the point where my phone was unresponsive with the Miracast prompts, but I was able to force my phone to reboot. Upon reboot, I noticed that the phone loading up was sluggish and not typically responsive. I decided to shutdown my phone to prevent further irreversible problem in the future (hint: boot loop). I waited for my phone to cool down for perhaps a few minutes before I powered on the phone again. This time, when the phone booted up, it was responsive as it normally has. Before all this happened, I didn't use my phone excessively nor extensive in a short period of time. I really have doubts that LG really applied a fix to their faulty connection problem and just used a replacement just to pass by.
Update 02/04/2017: I received an e-mail from LG requesting my feedback with respect to the repair. I gladly answered the survey, gave them good credit with respect to the repair itself, but when it comes to the quality of the LG product, they took a hit and I expressed my concern with respect to the boot loop.
Click to expand...
Click to collapse
You may not have to change your passwords. Depending on what hardware is damaged they will likely trash the whole board. If any part of the chipset is fried or damaged in some way, your safe since everything is on a single chip. So if it is a hardware failure on the chip, then all your stuff thats on there is going in trash to never see light of day again.
mobile_edc said:
Hi John!
I register this forum just for the purpose saying " Thank You! You are genius"
I followed your step by step guide and brought up my LG V10 to life, which casued by the so called " boot loop" problem few days ago.
I was almost ready to send my V10 back to the LG, and requesting for the replacemnt of the internal board of my LG V10. Luckily, I read your thread, and presume that your assumption is right with logical analysis. Now my phone is working without boot problem, and I successfully bring back my data from the internal memory, too.
Thank you so much, John!
eddie.
Click to expand...
Click to collapse
Glad to hear it worked, you are most welcome!
@johnkirchner you are a genius. Thanks for the advice, freshly baked V10 back to life.
johnkirchner said:
My wife's v10 started bootlooping about a week ago and is out of warranty. This happened right after doing a FOTA security update. I figured it was due to that so I tried resetting the phone but could not boot in to anything to get it to reset. After extensive searching and reading, I have "fixed" the phone so far. It has been booted up and running for almost 2 full days now. We are not using it at the moment, we had a spare phone so its not like we were going to be out of anything. Instead of the freezer trick (was not worried about data backup), I did the baking trick and as surprised as I was...it worked! Here is what I did if it might help anyone else.
Please note that your warranty will really be void after doing this, especially if anything gets damaged. The information here is reference only and results may vary due to altitude and baking temps (thought I would NEVER put that in a disclaimer for gadgets and software, lol). You may or may not have data loss either, so do not blame me!
You will need to take the phone apart so you will need a small precision set of screwdrivers. Check out the video from the link below to see how to disassemble the phone, you only need to get to the part where the circuit board is removed.
https://www.youtube.com/watch?v=7N_mGT-P1ZA
And now...seriously,
1. Pre-heat your oven to 385 F (~195 C).
2. CAREFULLY take the circuit board out of the phone, use the video above as reference.
3. Place the circuit board in the oven and bake for 7 minutes. I set my board on a baking rack so it was not directly on a cookie sheet.
4. Take circuit board out, shut off oven and let sit for at least 20 minutes to fully cool down. Add salt for flavor? (j/k)
5. After cool down, CAREFULLY place circuit board back in and put phone back together.
6. Put battery in and let charge if needed before booting the phone up.
7. Cross fingers and turn the phone on!
We were at a point to where we did not want to file a claim if we were going to end up with the same phone possibly again and have issues so I figured I would try it out. My kids thought I was insane watching me bake a circuit board.
However, the electronics knowledge in me knows this is just enough to actually do solder reflow on the board. From the numerous posts that I have read, it appears that some of the soldering is faulty and sometimes a reflow will fix the issue. Since circuit boards are so small and intricate, it takes extremely serious skill to actually use a solder iron to fix those...so for those of us who are not extremely seriously skilled in soldering, the oven seems to work. Don't get me wrong, I can solder like no tomorrow...but not on circuit boards
So if you have nothing to lose...give this a shot!
Click to expand...
Click to collapse
Big thanks to you, LG V10 baked back to life, LG BackUP running 57% !
Its too bad I didn't know about this before hand. My phone just bootlooped last Saturday without warning. I contacted my carrier but I was literally 4 days over the warranty period with them. Contacted LG, and they told me they couldn't either repair or replace my phone because its an international model and they did not have the hardware for international models(no clue why they couldn't replace it, unless they stopped manufacturing this specific model). Either way, I didn't worry too much about my files as I had contacts and texts on the SD card as well as Google, and my pictures and media where stored on my SD card. However, for the latter, I didn't realize that you could only 'unlock' files with the same phone you locked them with, so they were sitting on my SD, completely useless. I also lost all my progress on Yu-Gi-Oh! Duel Links because apparently Konami are idiots that don't realize they can link progress to a Google account rather than going through their own service.
I just got done disassembling the device and heating it up with a heat gun. I had nothing to lose, so why the hell not? Surprisingly, its managed to remain working just fine for 2 hours now. Managed to recover my locked files, my Duel Links progress, and my Authy backup. Still, I know it will eventually happen again, and I'm still under contract for another year so I'll be forced to buy another phone and still pay for this "almost" paper weight. Here's hoping that Class-Action Lawsuit actually leads somewhere and LG deals with this fairly.
@johnkirchner
You saved me couple of hundred of bucks.
I almost made a deal to buy a new phone and for the sake of wasting time, i tried your method.
I am shocked to see my phone in working again.
You are amazing.
Pretty sure my phone isn't in warranty anymore anyway since it's been over a year since obtaining it (sadly it's not eligible for an upgrade until January of next year, since pay-off rates are now every 2 years minimum), but I'm hesitant to try the bake method -- especially since I don't have my own oven currently, being that I'm staying with someone else's family currently due to economic situations.
With that said, I can get to the factory reset option by holding the Vol-Down + Power buttons, I just don't want to lose my data. I know for a fact USB Debugging is enabled, because I always enable that pretty much first thing when I get my Android phones, but I can't get ADB to recognize it. Windows always shows it as a "USB Charge Only Interface". I know there's a way to use ADB to backup data ("adb backup -all" should work IIRC) so I was going to try that first, then try the factory reset and see if it helps at all. Any suggestions?
If I can even get the phone to start up at all, just long enough to take it to AT&T, I can just trade it in for a new phone. Otherwise I'm stuck paying over $200 more for a phone that doesn't even work anymore anyway, just to get a new one.
johnkirchner said:
My wife's v10 started bootlooping about a week ago and is out of warranty. This happened right after doing a FOTA security update. I figured it was due to that so I tried resetting the phone but could not boot in to anything to get it to reset. After extensive searching and reading, I have "fixed" the phone so far. It has been booted up and running for almost 2 full days now. We are not using it at the moment, we had a spare phone so its not like we were going to be out of anything. Instead of the freezer trick (was not worried about data backup), I did the baking trick and as surprised as I was...it worked! Here is what I did if it might help anyone else.
Please note that your warranty will really be void after doing this, especially if anything gets damaged. The information here is reference only and results may vary due to altitude and baking temps (thought I would NEVER put that in a disclaimer for gadgets and software, lol). You may or may not have data loss either, so do not blame me!
You will need to take the phone apart so you will need a small precision set of screwdrivers. Check out the video from the link below to see how to disassemble the phone, you only need to get to the part where the circuit board is removed.
https://www.youtube.com/watch?v=7N_mGT-P1ZA
And now...seriously,
1. Pre-heat your oven to 385 F (~195 C).
2. CAREFULLY take the circuit board out of the phone, use the video above as reference.
3. Place the circuit board in the oven and bake for 7 minutes. I set my board on a baking rack so it was not directly on a cookie sheet.
4. Take circuit board out, shut off oven and let sit for at least 20 minutes to fully cool down. Add salt for flavor? (j/k)
5. After cool down, CAREFULLY place circuit board back in and put phone back together.
6. Put battery in and let charge if needed before booting the phone up.
7. Cross fingers and turn the phone on!
We were at a point to where we did not want to file a claim if we were going to end up with the same phone possibly again and have issues so I figured I would try it out. My kids thought I was insane watching me bake a circuit board.
However, the electronics knowledge in me knows this is just enough to actually do solder reflow on the board. From the numerous posts that I have read, it appears that some of the soldering is faulty and sometimes a reflow will fix the issue. Since circuit boards are so small and intricate, it takes extremely serious skill to actually use a solder iron to fix those...so for those of us who are not extremely seriously skilled in soldering, the oven seems to work. Don't get me wrong, I can solder like no tomorrow...but not on circuit boards
So if you have nothing to lose...give this a shot!
Click to expand...
Click to collapse
i am absolutely blown away...i can't believe this worked. not that i didn't believe you, but i had to be skeptical until i tried it. and it worked. plain and simple. thanks so much for this post. i'm beside myself with excitement
Edit: well that lasted a whole 20 hours, this morning back to bootloop . sigh....was good while it lasted i guess
johnkirchner said:
My wife's v10 started bootlooping about a week ago and is out of warranty. This happened right after doing a FOTA security update. I figured it was due to that so I tried resetting the phone but could not boot in to anything to get it to reset. After extensive searching and reading, I have "fixed" the phone so far. It has been booted up and running for almost 2 full days now. We are not using it at the moment, we had a spare phone so its not like we were going to be out of anything. Instead of the freezer trick (was not worried about data backup), I did the baking trick and as surprised as I was...it worked! Here is what I did if it might help anyone else.
Please note that your warranty will really be void after doing this, especially if anything gets damaged. The information here is reference only and results may vary due to altitude and baking temps (thought I would NEVER put that in a disclaimer for gadgets and software, lol). You may or may not have data loss either, so do not blame me!
You will need to take the phone apart so you will need a small precision set of screwdrivers. Check out the video from the link below to see how to disassemble the phone, you only need to get to the part where the circuit board is removed.
https://www.youtube.com/watch?v=7N_mGT-P1ZA
And now...seriously,
1. Pre-heat your oven to 385 F (~195 C).
2. CAREFULLY take the circuit board out of the phone, use the video above as reference.
3. Place the circuit board in the oven and bake for 7 minutes. I set my board on a baking rack so it was not directly on a cookie sheet.
4. Take circuit board out, shut off oven and let sit for at least 20 minutes to fully cool down. Add salt for flavor? (j/k)
5. After cool down, CAREFULLY place circuit board back in and put phone back together.
6. Put battery in and let charge if needed before booting the phone up.
7. Cross fingers and turn the phone on!
We were at a point to where we did not want to file a claim if we were going to end up with the same phone possibly again and have issues so I figured I would try it out. My kids thought I was insane watching me bake a circuit board.
However, the electronics knowledge in me knows this is just enough to actually do solder reflow on the board. From the numerous posts that I have read, it appears that some of the soldering is faulty and sometimes a reflow will fix the issue. Since circuit boards are so small and intricate, it takes extremely serious skill to actually use a solder iron to fix those...so for those of us who are not extremely seriously skilled in soldering, the oven seems to work. Don't get me wrong, I can solder like no tomorrow...but not on circuit boards
So if you have nothing to lose...give this a shot!
Click to expand...
Click to collapse
I gotta give it to sir john. I was hesitant to bake my board, but i figured i really wanna toast it anyway so what the heck. 15min after i turned off the oven i reassemble my v10, and it now boots onto home screen like magic.
Salt to taste
mobile_edc said:
Hi John!
I register this forum just for the purpose saying " Thank You! You are genius"
I followed your step by step guide and brought up my LG V10 to life, which casued by the so called " boot loop" problem few days ago.
I was almost ready to send my V10 back to the LG, and requesting for the replacemnt of the internal board of my LG V10. Luckily, I read your thread, and presume that your assumption is right with logical analysis. Now my phone is working without boot problem, and I successfully bring back my data from the internal memory, too.
Thank you so much, John!
eddie.
Click to expand...
Click to collapse
Thanks john
After limited temporary success with the hair dryer method your post led me to the baking method. It took 3 attempts at increasing time and temps . Started at 385 for 7 min. And it tried to boot but not. Then tried 385 for 10 min and it made it to just past the red round hello. Then I went all in. 400 for 13 min. With a dash of salt and a sprinkle of mesquite flavor. I'm in Kansas city... we love our bbq...what can I say? Anyhow, it sure as hell worked.... can't believe it but yes indeed... and it makes for a great no **** kinda story... thanks to all who shared here... oh btw, toothpaste does in fact make for a great heat sink..... paddle faster I'm hearing banjos
Related
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
The de-casing was fun, and yet there isn't an obviously damaged component. It was pronounced dead at 6:20 yesterday evening.
R.I.p.
Sent from my SGH-T699 using XDA Premium 4 mobile app
tylik said:
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
Click to expand...
Click to collapse
Get a new battery for it....had this issue before and placing new battery in it fixed my bootlooping and not being able to flash or get past samsung screen...the samsung batteries have an overcharge feature which has been known for causing errors such as this...
Just as the title says. A couple of days ago, I flashed the MOAR rom, everything was great with it up until last night, when I went to look at my phone and it was doing this. I cannot restart the phone using the "simulated battery removal" method of holding vol down + power button. Any ideas? Do I actually need to take this sucker apart?
Let the battery die completely is the first step. Plug it in to charge holding the buttons to start Download Mode/Recovery. If that works try (if you boot to recovery) and wiping the cache/davlik to see if that does anything. If not then a factory reset and then if not a full odin.
I'm under the impression that it's using very, very minimal battery. Thus, letting it drain may take days. But you may be right, maybe I'll just have to live without it for now.
To speed the process up, you could take the device apart and manually unplug the battery from the board. Its not the most difficult device to take apart, but that is coming from someone that takes apart phones for a living. If you're willing, and have the tools available, that would be the quickest way to get the phone to at least boot into recovery (if it will) and try an reflashing MOAR/stock.
edit: and you could also check and see if the board connection to the display is not loose as well if you go this route. If you do not feel comfortable, and you have Total Equipment Protection, you could take it in to a Sprint Service & Repair location and they can take it apart as well (or at least should be able to). I cannot speak for their level of competence when it comes to taking apart devices, but all of my technicians are well aware of how to take the Note 5 apart without causing any damage.
Get an usb otg cable and charge something from the phone lol that'll kill that battery
PS: This is just me being nosey, but it looks like your phone has "seen some things" aka it looks a little rough lol. Has it been dropped in the past? I used to be a phone repair technician for sprint and I saw this same thing, it ended up being that the cable from the digitizer had barely become wiggled loose on one side. There was another occasion where the GPU had toasted itself (this was an htc one) and we had to send it in to be repaired.
So im interested to know if a reboot solves your issue.
I took the phone apart at work, and from what I can tell, the main board has gone bad. I believe that simply because I've disconnected every non-essential component from the main board and it's still doing the same thing. I'm going to part out any good parts on ebay and scrap some cash from it.
The display should fetch a pretty penny. Enough to get yourself Nexus 5X without having to pay too much out of pocket, seeing as a Note 5 outright is pretty pricey.
If you have TEP, you can always go through the store and get a new one ordered for you. If you do not, a $75 fee occurs, but at least its a cost effective route for a bad board, if you do not want to part it out.
This was an apparent issue on s7 based on Google search.
I am getting this error message on a s8+ that has never seen water. It's been like this for about a week.
Kinda strange for a phone touted as waterproof.
Correct me if wrong but samsung warranty is voided on water damage?
Anyway to reset this?
Anyone with thoughts?
Sent from my SM-G955U using Tapatalk
I don't think it implies you have water damage. The warning is to prevent you from trying to charge if the port is wet after being exposed to water. You may just have a faulty port.
My first s7 did this and eventually would not charge anymore , and had to get a replacement
Sent from my SM-G955U using Tapatalk
It will wireless charge still.
Normally shows up fire a bit after the phone gets wet. Once it does it will go away.
I've gotten my phone wet all works great.
If you truly haven't gotten the phone wet or take it back because it might have an issue.
If the phone has nevee been wet then there is a problem.
Now if you live In the area where the humidity is high.
The that can trigger it also.
OMG the same thing is happening to my phone I've only had it for about 30 to 40 days-and like yours never seen water and it's giving me that moisture warning it has to be something wrong with these phones they need to give us our money back or replace them
Same thing just popped up on mine. I've had this phone for a week. Granted it's a really humid and rainy day here but this phone hasn't seen a drop of moisture.
Sent from my SM-G955U1 using XDA Free mobile app
Try giving the connector/port a wipe with some isopropyl/rubbing alcohol. This should clear the error.
so I have had this issue for about 2 weeks. the first time....it wouldn't charge. so I waited 3 hours and it still wouldn't charge. I turned my phone off and turned it back on and it worked fine. couple of days later it did the same thing....and then again. then yesterday....it restarted my phone at least 10 times and it was still saying moisture detected. MY PHONE HAS NEVER GOTTEN WET!! I googled and ever since the last mandatory update....alot of ppl are having this issue. so today....again...I can't charge my phone. i called tmobile and they are replacing my phone. i checked the little card inside the SIM card slot and it does NOT show water damage so it is a SYSTEM ISSUE!!! come on samsung!!! first the NOTE 7 issue....now this?! so tomorrow I'm getting a brand new phone being sent to the store and lets see what happens with this cause now I can only use my wireless charger which takes HOURS to fully charge my phone!!!!
Samsung has a hard rule, no repairs for water damage ever. I had to jump through hoops to get a brand new note fixed even after they agreed to fix it, the repair facility tried to not do it, more time in the phone with customer service. Samsung will go out of their way to deny warranty work and make you tell every higher person in the customer service chain your entire story over and over again. Terrible customer service unless you have a lot of patience and a lot of time to sit on hold.
mandyed66 said:
so I have had this issue for about 2 weeks. the first time....it wouldn't charge. so I waited 3 hours and it still wouldn't charge. I turned my phone off and turned it back on and it worked fine. couple of days later it did the same thing....and then again. then yesterday....it restarted my phone at least 10 times and it was still saying moisture detected. MY PHONE HAS NEVER GOTTEN WET!! I googled and ever since the last mandatory update....alot of ppl are having this issue. so today....again...I can't charge my phone. i called tmobile and they are replacing my phone. i checked the little card inside the SIM card slot and it does NOT show water damage so it is a SYSTEM ISSUE!!! come on samsung!!! first the NOTE 7 issue....now this?! so tomorrow I'm getting a brand new phone being sent to the store and lets see what happens with this cause now I can only use my wireless charger which takes HOURS to fully charge my phone!!!!
Click to expand...
Click to collapse
I've had issue with this as well but it's disappeared for the last few weeks not sure why......
Is there any chance that sand could cause the moisture alert? I had the same issue for an entire day, the phone did not get wet, but I live in a very sandy area and figured a grain of sand had triggered the alert. Just curious..
All you need ti do to fix this is plug in the cable then quickly restart phone without taking the charger out and when it comes back on seeconds later its fine
I've also had this problem for the past couple of days. Have had the alert before (phone has never been wet, but I used to live in a humid environment and mostly happened when my finger had been sitting over the connector). Then yesterday it stopped charging - very convenient not having a working phone while moving house and starting a new job /s.
I don't think hacks like rebooting while plugged in are an OK solution; I've never been unable to charge any phone during regular use before!
Reading around the net, Samsung has obviously pushed an update that has either increased the sensitivity of the cut-off, or just has a bug. Perhaps in response to issues with wet phones shorting and causing damage, and want to push warranty claims as user error or damage.
I've had an S3, S4, S6 and now S8; between this and Bixby hijacking my phone and constantly pushing updates to itself my next handset might be a Pixel.
Stifler87 said:
All you need ti do to fix this is plug in the cable then quickly restart phone without taking the charger out and when it comes back on seeconds later its fine
Click to expand...
Click to collapse
This worked for me. Thanks! Going to call T-Mo tomorrow though to get it replaced.
I'm having this issue with my Note 8 that is less than 2 months in use, Samsung is collecting it for repair on Friday and it will 7 to 10 days, phone have Not been exposed to moisture and won't work in the DeX station either, there is clearly a problem with charging ports on several different Samsung devices, fingers crossed it will come back fixed up OK with no more hassle
j_hansen said:
I'm having this issue with my Note 8 that is less than 2 months in use, Samsung is collecting it for repair on Friday and it will 7 to 10 days, phone have Not been exposed to moisture and won't work in the DeX station either, there is clearly a problem with charging ports on several different Samsung devices, fingers crossed it will come back fixed up OK with no more hassle
Click to expand...
Click to collapse
Could be an app causing it or multiple other things as mine just suddenly stopped doing it after an update a long while back.
Another thing was I have it a good rinse and then let it dry my phone on a stand so any water would move down and out.
I've been down all avenues including deleting apps and booting into safe mode that disables 3rd party apps, couple of factory resets and few hard resets from recovery and also have a problem with phone not detecting my brand new DeX, this digs deeper than I want to deal with now so Samsung can fix it since I did nothing wrong, I look after my phones really well, this is my first note to have a problem so I'll give Samsung the chance to put it right without me having a husdyr fit
Device: SM-G920F
ROM: stock 7.0
Build number: nrd90m.g920fxxu5eqf1
kernel version and its settings: 3.10.61-10958180 [email protected] #1
Not rooted
So my phone has been acting up for good 6 months now. I was getting random reboots and freezes that would last anywhere between happpening just once or going on to continue for a day. Sometimes it gets so bad, that the phone would not work longer than a minute or so and would immediately reboot again. During the freezes the battery gets drained really fast (about 20-30% in 15 mins). If the phone freezes and I reset it (volume down+power) it just reboots and then it could freeze again in a minute.
I went to samsung and they told me it's a software problem, so they reset all the software. In less than a week it happened again, and yesterday it froze while at recovery menu, so it's probably not software. Today I went to Samsung again and they told me that if that's still going on, they have to change the motherboard (which would cost me like $320 and I'm better off getting a new phone anyway). So what would be your advice? Can it still be software related? Or can it be related to a hardware component that can be replaced separately from the board and I should try private repair shops?
Hi, my son has become the same problem on the same phone model.
I put him in a private repair shop, and twice he was dismantled and repaired. If nothing happened on the phone, it worked, but as the problems began to work, they reappeared.
It's some cold connections on the base plate ...
We have ordered a new phone ...
GREY_LIGHT said:
Device: SM-G920F
ROM: stock 7.0
Build number: nrd90m.g920fxxu5eqf1
kernel version and its settings: 3.10.61-10958180 [email protected] #1
Not rooted
So my phone has been acting up for good 6 months now. I was getting random reboots and freezes that would last anywhere between happpening just once or going on to continue for a day. Sometimes it gets so bad, that the phone would not work longer than a minute or so and would immediately reboot again. During the freezes the battery gets drained really fast (about 20-30% in 15 mins). If the phone freezes and I reset it (volume down+power) it just reboots and then it could freeze again in a minute.
I went to samsung and they told me it's a software problem, so they reset all the software. In less than a week it happened again, and yesterday it froze while at recovery menu, so it's probably not software. Today I went to Samsung again and they told me that if that's still going on, they have to change the motherboard (which would cost me like $320 and I'm better off getting a new phone anyway). So what would be your advice? Can it still be software related? Or can it be related to a hardware component that can be replaced separately from the board and I should try private repair shops?
Click to expand...
Click to collapse
Did you spill water on your phone in the past? may be left it in a foggy or misty area? try to remember. your phone shows symptoms of shorting in logic board. in that case approach a private repair shop that does ultrasonic cleaning. this will mostly fix your phone.
donco22 said:
Did you spill water on your phone in the past? may be left it in a foggy or misty area? try to remember. your phone shows symptoms of shorting in logic board. in that case approach a private repair shop that does ultrasonic cleaning. this will mostly fix your phone.
Click to expand...
Click to collapse
Thanks for your reply!
I did not spill anything on my phone, or have been in a foggy area for a while. There might have been some exposure to rain though. Is there any way to confirm water exposure as a culprit (as opposed to a broken motherboard) without disassembling the phone?
GREY_LIGHT said:
Thanks for your reply!
I did not spill anything on my phone, or have been in a foggy area for a while. There might have been some exposure to rain though. Is there any way to confirm water exposure as a culprit (as opposed to a broken motherboard) without disassembling the phone?
Click to expand...
Click to collapse
I am afraid thats not possible. you have to eventually open up phone to inspect logic board. i strongly recommend approaching to samsung service centre or a private shop(that does ultrasonic cleansing) rather than opening up yourself.
To give some context, my S10e (Verizon SM-G970U) decided to boot loop out of nowhere. Since this happened, I have factory reset the phone, no success. I brought it to a local repair shop who said they couldn't fix it. Now I have flashed the phone with Odin and despite the phone being flashed it STILL is boot looping. At this point, I'm assuming something went wrong with the hardware but I don't even know where to start with that. If anyone has any suggestions I would greatly appreciate them.
Firmware used :
Download Samsung Galaxy S10e SM-G970U VZW USA (Verizon) G970USQU5GUBH firmware
Fast download latest Samsung Galaxy S10e firmware SM-G970U from USA (Verizon) with G970USQU5GUBH and Android version 11
www.sammobile.com
Vivala8955 said:
... it STILL is boot looping...
Click to expand...
Click to collapse
If it is a hardware issue (which sounds likely), there's an old electronics trick you might try: Power it off, put it in the refridgerator awhile, take it back out and power it on. This has work'd for me with stereo components, for example, as well as a phone. It once revived a hard disk drive long enough for me to capture important data. Oh, but the phone this has brought back for me, an S10e BTW, works only while still cold and has issues with charging while its temperature is low. Still may be worth a try.
MrGoodtunes said:
If it is a hardware issue (which sounds likely), there's an old electronics trick you might try: Power it off, put it in the refridgerator awhile, take it back out and power it on. This has work'd for me with stereo components, for example, as well as a phone. It once revived a hard disk drive long enough for me to capture important data. Oh, but the phone this has brought back for me, an S10e BTW, works only while still cold and has issues with charging while its temperature is low. Still may be worth a try.
Click to expand...
Click to collapse
Wow, I just did this and to my surprise it worked! Prior to this, I wasn't able to get past the Google sign in page on start up (on good attempts) but now I was able to get it all the way to the homescreen and even install some apps before my battery died. Any idea of what this could mean for the actual hardware? I.e. this means the battery needs to be replaced etc
Vivala8955 said:
Wow, I just did this and to my surprise it worked! Prior to this, I wasn't able to get past the Google sign in page on start up (on good attempts) but now I was able to get it all the way to the homescreen and even install some apps before my battery died. Any idea of what this could mean for the actual hardware? I.e. this means the battery needs to be replaced etc
Click to expand...
Click to collapse
Great; glad it work'd. Did you attempt to charge it while it was working? Mine actually took charging after warming up only a short time, once. Got it back all the way to 100% charged. But then it quit with dead black screen, and now revives only for a minute or two.
In the old days of individual transistors, we used to turn on a non-working electronic device and blast a shot of freeze spray on various components until the device started working; even with IC (integrated circuit) chips that have lots of transistors. This way, we knew which part needed replacement. But with today's phones, you replace the entire circuit board because the soldering is done by machines; it's too finely detail'd to replace one chip.
MrGoodtunes said:
Great; glad it work'd. Did you attempt to charge it while it was working? Mine actually took charging after warming up only a short time, once. Got it back all the way to 100% charged. But then it quit with dead black screen, and now revives only for a minute or two.
In the old days of individual transistors, we used to turn on a non-working electronic device and blast a shot of freeze spray on various components until the device started working; even with IC (integrated circuit) chips that have lots of transistors. This way, we knew which part needed replacement. But with today's phones, you replace the entire circuit board because the soldering is done by machines; it's too finely detail'd to replace one chip.
Click to expand...
Click to collapse
I haven't tried charging the phone when it's on. Only when it's off and has returned to room temperature. Seems to me that about an hour in the fridge equals about 5 minutes of screen on time until the phone heats up again.
As for the internal component's you bring up a good point. Even if I were to determine what is causing the issue, I don't have the will/technical know how to buy the parts and do it myself. Outside of just replacing everything, in which I'd just buy a new phone haha.
Vivala8955 said:
... I'd just buy a new phone ...
Click to expand...
Click to collapse
That's what I did. Look'd at lots of possibilities, ended up buying another S10e.