Hi!
A little back story, I lost my IMEI a few months ago, Samsung couldn't fix it so I continued to use it as a wifi only device for a couple months.
Fast forward to 3 days ago, I found someone who would repair it, and I can now make calls and so on. I assume they reflashed/formatted my phone, since I lost root, (but an icon with SuperSU was still there, but not with the usual icon).I factory reset my phone after the repair as well
Last evening, I had my phone in my bag for a couple of hours, and later found the device extremely hot, and it was stuck at the pulsing Samsung logo with the led on a solid blue.
This evening, I found the phone the same way, except that I hadn't used it for a half hour. And I don't think the blue led was on.
I'm on stock 4.4.2, not rooted (For fear of losing my IMEI again)
Would be grateful for any help, thanks!
Related
I have searched here and google all day to no avail. After charging my phone last night I tried to turn it on this morning and just get the amber led light then the green. It just won't boot. I have removed the battery several times, checked the battery contacts, all fine. I have tried the volume and power button trick but nothing. I rooted the phone about 4 months ago to gingervillian. All, has been well until now.I left the battery in there for a while and noticed that it got quite hot. I have now removed it and am going to leave it out overnight to see if it is anything to do with overheating. Anyone ever had similar or heard of this before, help appreciated.
Flashing amber usually means the battery is completely dead. Maybe try a new battery because it might be dead.
Oh, I like the sound of that planning to go to Tmobile shop (nearest one to me as on their network) to get it checked tommorrow. Thanks for that info.
Just an update for anyone who may have the same problem. I left the battery out all night, came down this morning and tried it and still the same amber to green and so on. Left the battery in and then about half an hour later just about to go out and noticed not flashing anymore. Tried it and it booted up fine! Battery only says 46% left will see what happens when I charge it tonight.
Tempted to go back to original rom in case this goes wrong again, didn't fancy telling the guys in the shop that I had rooted it and so voiding my warranty. Although I can't remeber what the warranty length was anyway?
Going to have a think about it as I really can't stand the original rom version.
About a few months ago, my lgg3 started restarting randomly (usually if I dropped it), but I never really paid attention to it. Then bout a week ago, my phone would freeze, then restart but not fully turn on (would turn off after logo appeared) and I would have to remove the battery to get it on and running normally again. Then a couple days ago, it started to not turn on at all and when I looked up what might be the problem, I figured it was probably a battery issue. So I bought a new battery and put it in, and it started to boot up but would still turn off after the logo screen. I have tried to hard reset it twice but when ever I press 'yes' to the reset, it would go to logo then turn off. I'm thinking I just need to get a new phone, as it is nearing 3 years old, but I figured I come here just to see if I can get any solutions.
Test your device with the charger plugged on, if the problem persists, it is not battery problem and maybe your motherboard has some issues.
Hello. I'm super new to this forum. I created this account and thread because I'm a bit desperate. I'm no expert in this so I'll try to explain the situation the best I can. I'd like for people to try and do the same, because, as I said, no expert.
The situation is this: my phone is known as the LG G3 Beat (D722). One year ago, I decided to root and also install a custom rom (CM12.1), which worked perfectly. A few months ago, I changed it to CM13. Worked great too.
3 days ago, I left my phone charging while I went away for a few minutes (maybe 10-15min). When I came back, the phone was completely dead. It won't turn on, it won't boot to TWRP, it won't light anything, no nothing. I know it was working because, before I went away I listened to my notification ringtone, and I ignored it because I was busy. I need some help because I think the phone somehow hard bricked.
Here's the info for tl;dr guys:
- D722p with CM13 installed
- Was charging
- Dead after checking the phone... Can't boot, go to TWRP, connecting the charger won't do anything nor connecting it via USB to the PC.
- Taking the battery / SIM out for a few minutes... connecting the charger without the battery... Those won't work.
So, possible things that happened in my opinion:
- Charger had some issues (it was faulty, but if left still, it would charge okay) could've possibly damaged the battery, making it useless (although, the battery looks fine).
- The phone's "motherboard" was fried because of the 1st thing mentioned, which I don't want to say it did.
I really think there's a way to recover this phone. And I'd love some help. Thanks in advance.
Hello, I'm new to the forum and I may need your help for a problem I've had today. I've been an happy owner of a Nexus 5X until this morning, when I was regularly using it while on charge and at one point it freezed for a few seconds with the screen still on. I pushed the standby button, the screen went off and from then on it was completely bricked. No signs of life, nor access to recovery mode via bootloader. Nothing. Already tried all the possible physical buttons combos, nothing.
It was on Android 8.1 (beta, very happy about that by the way), no root and with locked bootloader. I did some flashing experiments one year ago but in the end I reverted it back to totally stock and I haven't had issues ever since. Never had bootloops or similar problems, it just happened all of a sudden.
Hope to receive your help, by the way it should still be under warranty, so let's see...
Thanks for your help.
Same problem heare. I tried to install the factory image but now, the phone is completely death.
I beleve thet it was a android 8.1 issue because it was not a bootloop problem.
Same problem heare. 8.1 need a reboot but now, the phone is completely death
It might be an 8.1 issue then. By the way, being under warranty I sent it to customer assistance. I've had some signals of life before this morning though. The LED was flashing red indicating very low battery. I connected it to the charger and followed the instructions by Google themselves:
"If you see a red light, your battery is fully discharged. If the red light is flashing, there isn't enough power to turn on. Charge your phone for at least 30 minutes before restarting".
This seemed to resemble my case, so I waited for about 40 minutes (by that time the charging battery icon did show up with the phone still off) and tried to turn on. The only thing that I got has been the Google logo before the boot animation for a few seconds. Then the screen has gone off again and back to death.
From your comments it seems it might be an 8.1 related issue. Watching videos on Youtube about 5Xes with similar behaviours I was actually thinking about a motherboard failure, or a battery failure (the latter is more unlikely though). Disassembling and heating up the motherboard providing a temperature shock seemed to be a decent temporary solution to bring it back to life. I have warranty though so I sent it to assistance, we'll see... I'll probably unenroll my phone from the beta program just to stay safe.
Thanks for your answers.
My nexus 5x had same issue. A few weeks after 8.1, it totally bricked. I was able to get bootloader on once, but it was locked and fastboot didn't see it. Then after i let it discharge, I haven't been able to get it to recharge or get to boot screen at all. I bought another nexus 5x, but bit worried that 8.1 will kill it.
Been using Lineage OS for a few months and phone was running smooth and battery still strong.
Never had any unusual crashes etc, and gave me no need to upgrade.
Yesterday it would no longer turn on and trying to hard/soft reset only had the 1st RED LED blink occasionally.
Battery is at 3.75V and appears fine with no past problems.
Tried with power cord, left battery out over night but still no boot.
Took to a legit repair shop and they said if it doesn't boot they can't diagnose etc...
Is it time to finally replace the Note II? Doesn't have a scratch on it and always taken care of.
Only reason for Lineage OS was that a few apps no longer worked with the last Note II Android OS 4.1?
Any help is very much appreciated.