Related
The phone started restarting on it's own a few days ago. Only one day has passed and then it stopped going over the booting process and got stuck there. It gets really hot and freezes.
Tried getting it into recovery mode and it freezes there aswell. Had some pictures i wished to save but seems theyre gone now.
Everything is stock , GSM 4.0.1 android.
Anyone else had this kind of problem ?
I have the same problem. My phone has 1 week, I was playing for one hour, and then, it restarted and never passed again from the "Google" logo, and it freezes here and in the recovery (with strange colours). It seems a graphic card failure, I don't know.
I called to Vodafone, and waiting for a new Galaxy nexus.
Mine froze at the "google logo". Tried recovery and all sorts of things. But it was as if the flash had gone missing.
I returned it and the service shop replaced the whole motherboard as it was defect. It sucked but I'm hoping that I won't have the same issue anymore.
I have randomly started experiencing a problem where my device would turn off randomly which has gradually gotten worse to the point where it's stuck in a boot loop sort thing and will shut off randomly during boot then restart.
The problem started by every now and then (sometimes not happening for a day at a time) the phone would turn off then turn back on again gradually getting worse. The problem started when I installed the latest update during the update the screen froze (no it was not interrupted in anyway and done officially through the phone) so after leaving it overnight and it not progressing I took the chance and removed the battery. it then turned on and finished the update without an issue. The phone has since as I explained got into a 'boot loop' sort scenario where it will work if the charger is plugged in but couldn't be a battery issue as doesn't turn off if I put it into download mode. Things I've tried: Doing a complete reset- Still no fix. and now today I entered download mode and re-installed the firmware which was successful but still no prevail?! What the hell could this be?! Thanks
samisthebest said:
I have randomly started experiencing a problem where my device would turn off randomly which has gradually gotten worse to the point where it's stuck in a boot loop sort thing and will shut off randomly during boot then restart.
The problem started by every now and then (sometimes not happening for a day at a time) the phone would turn off then turn back on again gradually getting worse. The problem started when I installed the latest update during the update the screen froze (no it was not interrupted in anyway and done officially through the phone) so after leaving it overnight and it not progressing I took the chance and removed the battery. it then turned on and finished the update without an issue. The phone has since as I explained got into a 'boot loop' sort scenario where it will work if the charger is plugged in but couldn't be a battery issue as doesn't turn off if I put it into download mode. Things I've tried: Doing a complete reset- Still no fix. and now today I entered download mode and re-installed the firmware which was successful but still no prevail?! What the hell could this be?! Thanks
Click to expand...
Click to collapse
Maybe it's a hardware issue
hi, where did you get the firmware? it could be corrupted. if I were you I would download again the firmware and reflash it.
after that I'll do a hard reset.
samisthebest said:
I have randomly started experiencing a problem where my device would turn off randomly which has gradually gotten worse to the point where it's stuck in a boot loop sort thing and will shut off randomly during boot then restart.
The problem started by every now and then (sometimes not happening for a day at a time) the phone would turn off then turn back on again gradually getting worse. The problem started when I installed the latest update during the update the screen froze (no it was not interrupted in anyway and done officially through the phone) so after leaving it overnight and it not progressing I took the chance and removed the battery. it then turned on and finished the update without an issue. The phone has since as I explained got into a 'boot loop' sort scenario where it will work if the charger is plugged in but couldn't be a battery issue as doesn't turn off if I put it into download mode. Things I've tried: Doing a complete reset- Still no fix. and now today I entered download mode and re-installed the firmware which was successful but still no prevail?! What the hell could this be?! Thanks
Click to expand...
Click to collapse
Well i guess im not alone as i have the same exact problem as you do! WHich version do you have? I have the White T-Mobile version and i bought it the same week it was on sale i felt that i got a phone that was part of a bad batch because of some problems ive had with it but i didnt buy insurance for it. i was on LG's OS and it started to get worse and worse so i restored it and went to a lollipop rom. its still happening but it only reboots once. however, as soon as i start using apps it reboots on me. i want to unroot it but at the same time i dont want to go through the trouble of rooting it again. Any ideas of what it could be?
My problem just randomly started happening and i noticed this started happening strangely after my phone completely died on me and didnt want to turn on so i connected it to the charger and it started charging but had a yellow warning triangle somewhere on the screen.
EduardoZ714 said:
Well i guess im not alone as i have the same exact problem as you do! WHich version do you have? I have the White T-Mobile version and i bought it the same week it was on sale i felt that i got a phone that was part of a bad batch because of some problems ive had with it but i didnt buy insurance for it. i was on LG's OS and it started to get worse and worse so i restored it and went to a lollipop rom. its still happening but it only reboots once. however, as soon as i start using apps it reboots on me. i want to unroot it but at the same time i dont want to go through the trouble of rooting it again. Any ideas of what it could be?
My problem just randomly started happening and i noticed this started happening strangely after my phone completely died on me and didnt want to turn on so i connected it to the charger and it started charging but had a yellow warning triangle somewhere on the screen.
Click to expand...
Click to collapse
Hey, nice to hear someone has the same issue, I however hvent had the yellow warning triangle come up yet, as an update all of a sudden it keeps turning off as soon as it boots even on charge!!!??? It just keeps getting gradually worse?! However I have noticed the battery % it shows when turned off is 100% and very randomly it displays 70% then when the phone boots it will show 2% for the 2 seconds it stays on before it dies?!
samisthebest said:
Hey, nice to hear someone has the same issue, I however hvent had the yellow warning triangle come up yet, as an update all of a sudden it keeps turning off as soon as it boots even on charge!!!??? It just keeps getting gradually worse?! However I have noticed the battery % it shows when turned off is 100% and very randomly it displays 70% then when the phone boots it will show 2% for the 2 seconds it stays on before it dies?!
Click to expand...
Click to collapse
Wait now it reboots on you even if its charging? I too started noticing that with my battery . if I turn it off and charge it it and lets say it says its at 75% well I turn it on and its like at 40%? I really don't want to buy another battery but I actually hope the battery is the culprit. There's a guy with a G3 in my school I'm going to see if he let's me try his battery out on my phone I'll keep you posted
EduardoZ714 said:
Wait now it reboots on you even if its charging? I too started noticing that with my battery . if I turn it off and charge it it and lets say it says its at 75% well I turn it on and its like at 40%? I really don't want to buy another battery but I actually hope the battery is the culprit. There's a guy with a G3 in my school I'm going to see if he let's me try his battery out on my phone I'll keep you posted
Click to expand...
Click to collapse
Hey how did you go? Managed to get mine to let me use it when connected by doing ANOTHER factory reset
samisthebest said:
Hey how did you go? Managed to get mine to let me use it when connected by doing ANOTHER factory reset
Click to expand...
Click to collapse
Hey sorry for taking so damn long on replying i've been busy studying for some exams.
I've got good news for you though, i took my phone in to T-Mobile and showed them my problem. Without me putting much effort into persuading them, they shipped me a new phone, and no i didn't pay for insurance on T-Mobile, this was covered by LG's 1 year Manufacturers warranty!
Anyways, I received the device but did not receive a battery. So i tried my battery on the new one and what do you know? SAME PROBLEM!
So yea you should either try to unroot the phone and take it to the store but don't mention that you think its the battery, they'll send you a new phone! Then just buy a battery online or call them after a few days and say your problem is still occurring with the new phone and see if they send you a replacement battery, im a little skeptical on this second option as id rather keep this new phone haha
EduardoZ714 said:
Hey sorry for taking so damn long on replying i've been busy studying for some exams.
I've got good news for you though, i took my phone in to T-Mobile and showed them my problem. Without me putting much effort into persuading them, they shipped me a new phone, and no i didn't pay for insurance on T-Mobile, this was covered by LG's 1 year Manufacturers warranty!
Anyways, I received the device but did not receive a battery. So i tried my battery on the new one and what do you know? SAME PROBLEM!
So yea you should either try to unroot the phone and take it to the store but don't mention that you think its the battery, they'll send you a new phone! Then just buy a battery online or call them after a few days and say your problem is still occurring with the new phone and see if they send you a replacement battery, im a little skeptical on this second option as id rather keep this new phone haha
Click to expand...
Click to collapse
Hi, even i am having this problem, my phone is a D855 and in my country (Mozambique) i am not using a contract so its different than US, we have a LG store here but in the LG website our country is not stated. So only way is to go to a trusted Store that repairs phone here. My question is that, when its not connected in the charger it just keeps reboting (the notification LED doesnt even blink) infinite times. At first i thought it was a software but after going from Stock to Cloudy to CandyRom the problem was still there. Then after i plugged in a charger the phone would succesfully boot up and i could use it normally but had to stay connected on a charger. So what have you done to fix this? Did you replace the battery with a new one and then it stopped rebooting?? Please help me as i want to buy a new battery but first want to confirm if its the battery at fault....
skullzboy said:
Hi, even i am having this problem, my phone is a D855 and in my country (Mozambique) i am not using a contract so its different than US, we have a LG store here but in the LG website our country is not stated. So only way is to go to a trusted Store that repairs phone here. My question is that, when its not connected in the charger it just keeps reboting (the notification LED doesnt even blink) infinite times. At first i thought it was a software but after going from Stock to Cloudy to CandyRom the problem was still there. Then after i plugged in a charger the phone would succesfully boot up and i could use it normally but had to stay connected on a charger. So what have you done to fix this? Did you replace the battery with a new one and then it stopped rebooting?? Please help me as i want to buy a new battery but first want to confirm if its the battery at fault....
Click to expand...
Click to collapse
Hello buddy, sorry for taking so long to reply. Im usually not on XDA too much. Yes i solved my issue with a new battery. I tried my bad battery on 2 lg g3s and it rebooted both. I also unrooted my phone and flashed a completely stock update and was still having that issue.
I hope my response isnt too late for you!
No problem bro! Got a new battery and do far my phone doesnt reboot, but the only problem i am having is that my phone shutsdown at 30% battery and when trying to turn on it says it has 0%
EduardoZ714 said:
Hello buddy, sorry for taking so long to reply. Im usually not on XDA too much. Yes i solved my issue with a new battery. I tried my bad battery on 2 lg g3s and it rebooted both. I also unrooted my phone and flashed a completely stock update and was still having that issue.
I hope my response isnt too late for you!
Click to expand...
Click to collapse
Im having the same problem gotba new battery and no different so annoying
Best thing just happened. I had the G3 for a while and my first one had an issue and had to get a warranty replacement. Long story short... I got two more G3s from T-Mobile that were defective and most carries have a policy where if you get 3 warranty replacements you can chose a different phone. To wrap it up, you can ask for a phone of equal or lesser value when purchased from the carrier (I bought mine off eBay and they didn't even notice, I spoke to several reps and no one caught on.) So they can either send you a whole new phone, a new battery, or in my case: I received a new LG G4 since I had gone through three which pretty much anyone can do with a bad battery.
Guys. Im having this same exact problem on my LGG3!!!
Expired Battery or Faulty Power Button could be the culprit
This issue just started happening to my LG G3 over the last 2 weeks. I've had my LG G3 for exactly 15 months and all of a sudden it started cycling endlessly and if it did get to my locked screen and i tried to unlock it it would just restart again.
I found that when I plugged in the device to a wall charger or high power power brick, it would halt the reboots but otherwise it would get stuck in an endless cycle of partial reboots (when it did stop after plugging in, I would find all my apps still open and waiting for me, so they weren't real power cycles).
One of my coworkers has a newer LG G3, so we swapped batteries and immediately he had the cycling issue on his phone and with his battery in my phone the issue vanished.
On closer inspection, my battery was a few months past its expiration (FYI to anyone with a LG G3 - your battery will expire more or less exactly as its warranty protection does!), so went and bought a new battery and everything is fine now.
For those of you who have tried replacing the battery and find it still occurs, another coworker said his wife had a similar issue on a different device and it was resolved by having the power button replaced, so it is possible that this could be a factor also and you should have your phone sent in for inspection/repair.
Hope this is helpful for some of you.
Sarah.Minchom said:
This issue just started happening to my LG G3 over the last 2 weeks. I've had my LG G3 for exactly 15 months and all of a sudden it started cycling endlessly and if it did get to my locked screen and i tried to unlock it it would just restart again.
I found that when I plugged in the device to a wall charger or high power power brick, it would halt the reboots but otherwise it would get stuck in an endless cycle of partial reboots (when it did stop after plugging in, I would find all my apps still open and waiting for me, so they weren't real power cycles).
One of my coworkers has a newer LG G3, so we swapped batteries and immediately he had the cycling issue on his phone and with his battery in my phone the issue vanished.
On closer inspection, my battery was a few months past its expiration (FYI to anyone with a LG G3 - your battery will expire more or less exactly as its warranty protection does!), so went and bought a new battery and everything is fine now.
For those of you who have tried replacing the battery and find it still occurs, another coworker said his wife had a similar issue on a different device and it was resolved by having the power button replaced, so it is possible that this could be a factor also and you should have your phone sent in for inspection/repair.
Hope this is helpful for some of you.
Click to expand...
Click to collapse
I've had the same issue since February, when my phone was about 17 months old. It kept turning off saying SIM card not detected. I tried replacing the SIM card and washing that area with alcohol with no luck. Then I replaced the battery with a second one that came with the phone which I'd never used, but I noticed no difference. It also has no phone service for several hours without my knowledge. LG just told me to reset the phone, but it looks like that doesn't work from what I've read. T-Mobile said they'd give me a new phone but there are no G3s in stock and offered me a Samsung 3, which is three years old, so I am worried that it won't be able to handle the software updates. It's ridiculous that a phone that costs this much won't even last long enough for me to pay it off. My last phone was an Iphone, which I had for more than four years.
I had the exact same problem a few weeks ago, posted a detailed explanation of the problem and got 0 replies and a few hundred views (thanks guys!)
Easy answer:
Replace your battery
Thats what I did, and the problem is now gone. When you do get a new battery make sure you drain it completely first, then charge it for 4 hours without exceptions.
I tried factory resetting, installing a new firmware, going to stock and going to custom but nothing worked.
The girl in the shop where i bought the battery surprised me, i just asked her if they had one available and her immediate reply way "why, is your g3 stuck in a boot loop?", apparently EVERY SINGLE PERSON that bought a g3 battery from them had the exact same issue.
Now the problem is gone, and my phone actually lasts longer than before.
skullzboy said:
No problem bro! Got a new battery and do far my phone doesnt reboot, but the only problem i am having is that my phone shutsdown at 30% battery and when trying to turn on it says it has 0%
Click to expand...
Click to collapse
Hey, I am having the EXACT same issue. LG G3 was stuck in an endless loop, replaced the battery, now it works down to about 30% and shuts off. When I try to restart it says 0%. I even tried a third different battery, and still getting that 30% shutdown. Did you ever figure out what it was? I am wondering is it something to do with how the phone reads the battery charge i.e. does it think the battery is dead when it gets to 30%? It has e stumped!! Any advice would be most welcome. Thanks.
wtf,actually same with my LG G3,after when I bought a new battery. Shutsdown at 30% and it says has 0%.
same problem
bmoremotivated said:
Guys. Im having this same exact problem on my LGG3!!!
Click to expand...
Click to collapse
I HAVE THE SAME PROBLEM help PLEAAAAASE
Up until this point I hadn't messed with this phone, it was stock all the way. About a week ago it started acting funny, slow, would freeze occasionally. Figured it was time to root and throw a custom rom on. But the probably seems to just be getting worse. The phone is practically unusable.
Recovery still works fine, still pulls up into ODIN no issues and flashes.
I've tried 100% stock flashes, I've done the OTA, I've tried the awesome Note 5 port going around, even the older ones. Have tried OK1, OB7. And now I'm flashing the MM Odin File. Like I said the flashing is going through perfectly every time. But after setup yet it just keeps freezing, and then immediately goes to reboot. Sometimes it even gets stuck in bootloop, have to pull the battery. A couple times it has went directly to Download and said "Cannot do normal boot" or something like that.
Is this phone done for? Like I said, sometimes it's unusable. For instance, I just went 4-5 hours with it performing flawless, and at this exact moment; I couldn't make a phone call if my life depended on it.
Any ideas/help is greatly appreciated. Would be happy to provide any more info.
Thanks!
By any chance are you using the fingerprint scanner for your lockscreen? I had a similar problem until I turned it off in favor of a pattern lock screen. No problems at all ever since.
No, just the typical slide screen. My first thought was an app, but it is so sporadic, plus it has even locked up during the setup menu after one of the flashes. Very strange.
Mine started doing the same thing a few weeks ago. Freezing then rebooting. SystemUI.apk crashing.
Fresh ODIN to latest. Rebooted during setup. Eventually my phone wouldn't power on last Saturday.
I'd recommend backing up your phone and prepare for it suddenly dying. I found a few posts on Reddit saying others had similar issues.
I took it back to Sprint and they offered me a refurbished Note 4, so far so good!
AVAH0LIC said:
Up until this point I hadn't messed with this phone, it was stock all the way. About a week ago it started acting funny, slow, would freeze occasionally. Figured it was time to root and throw a custom rom on. But the probably seems to just be getting worse. The phone is practically unusable.
Recovery still works fine, still pulls up into ODIN no issues and flashes.
I've tried 100% stock flashes, I've done the OTA, I've tried the awesome Note 5 port going around, even the older ones. Have tried OK1, OB7. And now I'm flashing the MM Odin File. Like I said the flashing is going through perfectly every time. But after setup yet it just keeps freezing, and then immediately goes to reboot. Sometimes it even gets stuck in bootloop, have to pull the battery. A couple times it has went directly to Download and said "Cannot do normal boot" or something like that.
Is this phone done for? Like I said, sometimes it's unusable. For instance, I just went 4-5 hours with it performing flawless, and at this exact moment; I couldn't make a phone call if my life depended on it.
Any ideas/help is greatly appreciated. Would be happy to provide any more info.
Thanks!
Click to expand...
Click to collapse
I had the same issue. the phone kept rebooting in to download mode. sometimes I would have to pull the battery for a few hours to get the phone to even start. I Replaced the logic board to fix my phone.
Logic board? How hard is that to do? Where can i buy that part?
Ive had to replace the usb port, that wasnt too bad, im assuming its a similar task?
Lol the thing that makes me feel like such an idiot - I came here immediately when it started happening, and since I hadn't rooted this phone before I didn't do it 100% and cause Knox to trip.
The kicker? My 1 year warranty expired 4 days AFTER it started happening. So had I not screwed up and trippes knox, Samsung wouldve replaced.
My freind sold me his note 4 for $50. There are alot of videos on how to do it. It wasn't that hard. Some of the videos have links where to buy the different component's. https://youtu.be/OUDgGaFcCNY edit. The logic board is the motherboard
Sent from my SM-N910P using JellyBombed Tapatalk 2
This is insane.
After dealing with this issue for a while, I finally ponied up the cash and bought a Note 5 from eBay.
The phone was still acting ridiculous all day - I must have done soft resets at least 10 times between 6am-1:30. Excited to get home because the Note 5 was in the mailbox.
I get home, call Sprint, have them switch activation to the 5. They told me to turn them both off, they did their thing, and now service is on the 5. Just like normal.
The ONLY thing that has changed was the information in the phone regarding service/activation; and now the Note 4 is running FLAWLESSLY. I don't understand how that could cause the problems that I was having, but now I'm frustrated as I just dropped a good amount of money to buy a phone without a contract/upgrade, and now it's working perfectly. Does anybody have any ideas on how this could have changed anything???
Same here also...
My phone just started doing this out the blue about a week and a half ago. It will freeze, hang, get extremely sluggish, reboot randomly, power off randomly, there will be about a 5-7 second delay with touch responses, typing will be delayed, etc. I did all the things, rebooted, pulled the battery, unrooted, went stock, re-rooted and tried other ROMs, tried custom kernels; I got the same results. I have a Note 3 I'm going to reactivate over the weekend and see if my Note 4 suddenly performs flawlessly since it won't be activated.
Installed CyanogenMOD and it still resets, locks up and has other performance related issues.
I did an OTA update to Marshmallow originally. This corrupted my SD card and then caused about 10 resets a day, ranging from when I was using it lightly to heavily or even when it was sleeping/screen off. If I woke it up it would reset or I could feel it reset when it was in my pocket.
First thing I did was a factory reset. I tried other tricks such as swapping out the battery, SD card (or none at all), clearing cache, etc.... Nothing worked. So I tried installing CyanogenMOD, and I failed. But I got the phone back to BPA1. I updated back to marshmallow via my computer and the Verizon software updater.
About a day later the resets and lockups came back. I kept it light of apps but did slowly begin to reinstall some of my usuals (from the play store).
I had some more time so I tried installing Cyan again and was successful. It took a long time to load and optimize but it worked. I used gapps mini and the only step I did not follow in the guide was I did not install xposed.
It's been running for about 12 hours and has hanged, locked up and rebooted on me multiple times. Chrome even locks up (it will stop resounding, I'll get the message asking if I want to wait or close at the same time it starts responding again.)
When it reboots, it still takes forever and even optimizes apps (that I assume have already been optimized). I've seen two boot screens for it, one the little alien guy and the other with gears turning. It did the gears the second time I booted and then I haven't seen them again.
I'm not sure what my next step should be. Maybe I'll try reflashing Cyanogen. I have a feeling it's a hardware issue at this point, but I'm open to ideas. Are there any good diagnostic tools that could help my situation?
The phone is out of warranty and I'm sure that now that I've installed Cyanogen, the warranty was voided anyway. It's a shame because this phone was perfect up until the marshmallow update. I probably had 5 lockup/boots in the year or two I've had it.
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
HORIZONx720 said:
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
Click to expand...
Click to collapse
Admittedly, I did not even know about lineage until my phone was wiped with no OS. I did a quick Google search for it but could not find a Verizon note 4 mod. Now that I am not pressured to find a fix, I'll research it a bit more. Thank you.
I tried EmotionOS and NSeven, but both share the same error.
Emotion FCs random processes sporadically and then when my cell/data switches to Searching, it crashes multiple processes until the UI (trebuchet is default for Emotion?) and/or settings FCs and I have to restart. I am also stuck on 3G on that platform. I'm guessing network connectivity / switching is the root of the problems.
Nseven installed and right at the Welcome Screen where I pick my language, Google Play Services started crashing. I only had the option to click OK and then every 5 seconds after that, it kept crashing. I set up the phone, restarted and Google Play Services started crashing again. I am in the process of restoring back to Emotion, as it is the most stable platform so far.
I tried a new SIM card, hoping this was the problem but to no avail.
Does anyone have any other suggestions? I'm guessing its hardware at this point, but since it happened on an OTA Update and I can reproduce the same errors every time, I'm hoping there's still an option left for a fix.
Holy crap. As I was typing this and restoring Emotion, it fully installed and booted. I have 4G! I don't know if that will fix the FC issues, but I have regained a little hope!
I'm still getting FCs and restarts. The more I use it the more it happens, but at least with EmotionOS, It's more limited. Only about 3 or 4 a day compared to 10-20.
I'll try one more flash and I guess tough it out until my contract is up in April.
I can't help you with EmotionOS (haven't tried it yet), but if you want to stop the Google Play Services crashing in NSeven you can make your way to Settings - Applications, then select Google Play Services - Permissions and give it all permissions. It's a bit of a chore to get there when the warning pops up every five seconds, but it will stop once you do that.
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
trickyvinny said:
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
Click to expand...
Click to collapse
I know a lot of people are blaming software, but I'm fairly certain that the problems in many cases are caused by failing hardware. I went through many of the same trials and tribulations with my Note 4 (except I never rooted the phone). I finally contacted Samsung Customer Support and sent the phone in for repair. They replaced a lot of the hardware including the motherboard and returned the phone in "like new" condition. I've been using it for a few weeks now and the performance is flawless.
I was planning to get either the V20 or the G6 if I wasn't able to get the phone fixed. How do you like the V20?
I'd agree that it's most likely hardware and having to put everything in the freezer for it to when confirms it for me although I have no real expertise to say so. But I'd argue that the update created the hardware issue, it was night and day with the update. It was working 100% and then directly after the update to marshmallow, it started having catastrophic issues. Oh well, it's nice not having to pull the battery every hour or so.
V20 is pretty nice. Having used EmotionOS for a few months the switch to the Nougat was pretty smooth. The xda forums for it are a little more limited but I didn't start messing with my phone until it broke and I'm hesitant to try with a new phone given my limited knowhow.
To be honest it's not a big difference in day to day usage from the note 4. Which I like!
+ I never used the finger print scanner but really like it on the v20. I didn't bother with a screen lock before but now I'm protected and have a just as quick access.
-the grip is too slick, I feel like I will drop it. The note had that rougher back which I liked better. A case or a replacement cover should fix that though.
+ I like this top menu screen, I have quick access to a few select apps or can turn the flashlight on or whatever. I'd like it more customizable, I find I switch screens too much when trying to just pull my top menu down. If I could put everything on one tab and combine their special buttons (ie the flashlight button) with apps, it would be perfect.
-the back button and menu button are switched. I can probably customize that but I don't yet know how and by the time I figure it out, I will have relearned that habit. It actually is probably a better placement for how I hold the phone but I'm a big fan of choices.
+ upgraded camera, sound, storage. I don't notice the screen size difference, but it is a lighter phone.
-bloatware
All in all its a good shift from the note 4. I'm happy to be off of Samsung and still have the same basic user experience.
trickyvinny said:
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Click to expand...
Click to collapse
I have had the exact same problem with my note 4. It wouldn't last 30 seconds at a lock screen from a cold battery before it would start boot looping, and the longer you left it in, the worse it got. Google told me I needed a new battery from several other forums and places I read. So I ordered one and replaced with a genuine Samsung one direct from them, and it didn't change anything.
I figured out it was heat related and I had it sit on an ice pack and it would run and work fine as long as the ice pack held out, about 2 hours. I've down graded, flashed, rooted the boot loader, installed a recovery console, flashed to different versions, all have the same problem. So I've kind of reserved myself to the fact it must be a hardware problem. Perhaps it was caused by the update, but nothing software change wise seems to be able to fix it. Did wake-loc fix as well. I've spent the last week with mine trying everything in the world and every evening having it on the ice pack hooked up trying whatever I could think of or read up on doing, and basically as soon as it warms up, it starts doing it again.
Heres a pic; http://imgur.com/a/5L64V
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
trickyvinny said:
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
Click to expand...
Click to collapse
Just out of curiosity, what phone did you wind up going to?
The LG v20 and so far so good!
My Pixel XL just took a crap this morning. It was working as expected early on. A bit later I could not access the internet despite showing a pretty strong lte connection. I didn't think much of that because it's not unheard of for service to not reflect the indicator. I was listening to a podcast and it just died. Went into an endless boot loop. It has had a steady decline in how far it will boot. I once got into TWRP but it crashed shortly after and once got to the login screen, again, crashing before I could login. Now it doesn't get past the google screen.
I have tried flashing the stock image from the bootloader as well as trying to fastboot twrp and neither go well. The flashing "works" but doesn't boot. Fastboot doesn't give an error but the phone just bootloops.
As it sits the bootloader is unlocked (not sure it matters at all).
At this point I have already bought a new phone but am considering trying to fix it to have a backup if I can get an idea of where to start or what it would cost to send in.
Any advice or help would be appreciated.
This sounds really similar to what I had happen after a while with my first Pixel XL. I tried to document everything HERE.
Wiping dalvik cache through TWRP seemed to be a short term fix (daily), but even that eventually stopped working. I ended up being able to jump into an "open enrollment" period for adding insurance for the phone with Verizon and then was able to use their extended warranty system to get a replacement phone (which was confusing since they said it was not an insurance claim since it appeared to be a phone defect out of my control, so I'm not 100% sure I even needed the insurance? Your mileage may vary.) The replacement was a refurb but has worked perfectly ever since I got it. They still had them in stock at the time or else I'd have tried to push for a 2 (or maybe now push for a 3 or 3a?). Good luck!
just went through the same thing. research shows it was most likely a known motherboard issue. its out of warranty so i bought a used one on swappa for 80 bucks and then sold my non functioning one at an ecoATM for 30 bucks. so im only net -50.
tgumina said:
My Pixel XL just took a crap this morning. It was working as expected early on. A bit later I could not access the internet despite showing a pretty strong lte connection. I didn't think much of that because it's not unheard of for service to not reflect the indicator. I was listening to a podcast and it just died. Went into an endless boot loop. It has had a steady decline in how far it will boot. I once got into TWRP but it crashed shortly after and once got to the login screen, again, crashing before I could login. Now it doesn't get past the google screen.
I have tried flashing the stock image from the bootloader as well as trying to fastboot twrp and neither go well. The flashing "works" but doesn't boot. Fastboot doesn't give an error but the phone just bootloops.
As it sits the bootloader is unlocked (not sure it matters at all).
At this point I have already bought a new phone but am considering trying to fix it to have a backup if I can get an idea of where to start or what it would cost to send in.
Any advice or help would be appreciated.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/gsi/Pixel/Pixel-AB-11-20200909-ErfanGSI.img-0125.7z
↑extract and fastboot flash this