Related
my nexus 5 d820 16 gigs would randomly shutdown for no reason, it wouldn't turn on without plugging it in. i was rooted and running cm11, then i tried carbon ROM, then c-ROM. c-ROM started to give me problems so i factory reset and switched to carbon but the problems remained. then i unrooted, thinking that root was the problem but no signs of improvement, so i re-locked the bootloader but still the problem remained. it would sometimes also shut down if i unplug it and would always forget my WiFi connection for some reason. help me please. thanks in advance.
Well sounds like a hardware problem since you already unroofed and relocked boot loader I would say call lg and get a warranty replacement
Sent from my Nexus 5 using Tapatalk
Sorry to bring this post back after a long time.
I had a similar but not exactly the same problem.
2 nights ago I left the phone on the table, and a few minutes later, when I picked it up, it was off (It had about 60% battery left when I put it down).
Then it would not wake up; I kept the power button pressed for like 20 seconds to force a shutdown, and then tried to power up with no luck, so I'm thinking I'm screwed.
I tried again and it powered up to a graphical noise screen as seen in the attached image, but then it showed the boot animation and came back to life.
This morning it shut off by itself while listening to music (Google play), but powered back on right away...
Rooted 4.4.4, stock ROM, Xposed with Greenify, Amplify and wakelock detector (all latest versions). But no changes for a couple weeks before this started happening.
No specific app running (at least in the foreground).
Any one knows where I can find any kind of log or trace about this, if any at all?
Has anyone experienced this as well?
Thanks
So I just picked up this s3, it will turn on but shuts off halfway through galaxy splash screen. Boots into recovery and Odin mode just fine, prior to purchasing we plugged it in, got it to boot and did a factory reset, to clear privious owners data, and it went fine, did it reboot and took me to setup. Satisfied with its performance I went ahead and made the purchase, upon unplugging it shut off, as I expected if battery was indeed shot. What gets me is I let it charge, unplugged, booted, shut off at splash screen, plug back in and says its still fully charged. Boot into recovery and indeed, 100% battery. I haven't gotten around to flashing twrp or rooting, was wondering if anyone has experienced this?
Sent from my HTC Desire HD using XDA Free mobile app
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Phone was already on 4.4 when I got it, I downloaded and flashed stock firmware (ne1) via odin, I got the whole way to the end of setup and as soon as it started loading the homescreen it cut off and went to the green battery charge icon when phones off. Everytime I try and boot it, she'll go through all the splash screens and ill catch a very short glimpse of the homescreen and it shuts off. Also it HAS to be plugged in still, or else it just shuts off halfway through initial "galaxy s3" splash.. I don't understand...
Have you tried a new battery? Even if it's plugged in it won't run if the battery is completely shot.
Also if you indeed have a Verizon S3 on NE1 firmware you will not be able to install TWRP as the bootloader is locked. You will be able to root, however.
Muhff said:
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Click to expand...
Click to collapse
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
XdrummerXboy said:
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Muhff said:
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Click to expand...
Click to collapse
I'm glad you fixed the problem!
Sent from my SCH-I535 using XDA Free mobile app
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
Switched phone on after work, phone powers up, boots up and then freezes after around 20 secs then switches off and re-boots, the process then starts again over and over again.
I've tried deleting cache, master reset, safe mode, simulated battery reset which does not work. I let the battery run flat by putting the phone into download mode and then recharged the battery but still nothing. The phone seems stable only in download mode.
I managed to re-install stock 7.0 firmware via Odin. Firmware installs fine, phone boots up and then freezes on welcome screen and then boots up again. I then tried 6.0.1, again installs fine, I get the welcome set up screen but after a 20 odd secs freezes up again.
The phone is less than two years old. Samsung service centre warranty job? Thanks.
Yes. Mine had also freezing and reboot issues, Sammy changed the Mainboard
The phone is less than two years old. Samsung service centre warranty job?
Click to expand...
Click to collapse
Same problem after 5 months.
Yes get it back to service centre
guys this sounds like the same issues the lgg4 was having with the ilapo bootloop also a snapdragon
had bad solder points on the big cores and they would come loose over time and basicly the phone was stuck in a infinite loop
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Cappelletti said:
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Click to expand...
Click to collapse
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Mr.Ak said:
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Click to expand...
Click to collapse
I'm fairly sure that there is no local shop that could check it.
Right now, before checking this thread, I let the battery completely drain and now it's on the wall recharging. I'll enter recovery when it's 100% charged and do a factory reset. Then install everything back and use it for a few hours.
Let's see it that helps.
Thanx for the reply.
- phone battery completely drained
- phone battery completely charged
- booted to recovery and factory reseted
- initial COS configuration done without any freeze and/or reboot
- updating Google Apps
So far, so good.
And it rebooted twice, during apps update.
Although it updated main Google apps, it was not supposed to reboot.
:/
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
iPusak Gaoq™ said:
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
Click to expand...
Click to collapse
It does not get stuck. At times, it reboots during boot. Some times (rarely) it does that for two or three times and then turns off. But most of the time it freezes, reboots and I can use it normally for hours and hours.
seanwlk said:
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
Click to expand...
Click to collapse
I'm "almost" fine with the way it works for me. As most of the time it's fully operational.
I found a OPO with damage screen for sale here. He guy didn't want too much $ for it. I bought it and will receive next week. Will try to swap logic boards.
Let's see what happens.
Was able to have logcat running when the device froze (during game) and rebooted.
Is anyone able to see any error on the log that could make the device freeze and reboot?
Got the broken screen OPO two days ago. Yesterday my phone was impossible to be used. Rebooting like hell.
I swapped logic boards and all is fine. No freezes and reboots (of course, it's pratically another phone). I kept only my screen, housing and battery.
My logic board had a 2.5 sticker on it. The one I got now has a 2.1 sticker. Does anyone know what's that about?