Hey,
i just woke up yesterday (2017-08-17) without my phone ringing my alarm. It did not respond at all (power button,...) When i did reboot it there didn't seem to be a problem.
I was running official LOS (build 2017-08-03) with the latest bueffla kernel back then.
The phone was connected to a charger to charge it over night.
I installed the latest LOS build (2017-08-17) in the evening without reinstalling bueffla kernel (to check if this problem was kernel related).
When i woke up this morning (2017-08-18) the phone did not respond again.
I tried to call the phone but it was not connected to the network.
Did anybody have the same problem related?
I've attached the console-ramoops-0 file but there much garbage in there. I did reboot the phone at ~6:10 - 6:20 (i'm not sure about the exact time)
Related
purchased a new Galaxy S4, from sprint.
rooted using auto-root and installed teamwin recovery. all good. kept using the phone flawlessly for three days.
was going to flash CM10.2 through the recovery when i noticed the big button in the CyanogenMod home advertising the installer.
since this phone is compatible, then decided to try that.
CM11 installed right away and worked great, charged the phone, took a couple pictures, great.
then an update was requested to the ROM, so i installed it.
that update resets all my settings, so i started downloading all my apps and applying the settings again.
when the phone was around 18% of charge, i plugged the phone and nothing happened.
tried another phone with stock android in the same charger and everything went well fine so, i turned off the
SGS4 and plugged it again.
it vibrated once, (like it was about to start charging) but nothing happened. a few seconds later, it vibrated again, and that went on and on...
turned back on the phone in recovery, i noticed that TeamWin was replaced by ClockWorkMod recovery.
wiped Dalvik, cache and did a factory reset. turned phone back off and plugged the charger.
now it vibrates once, the screen lights up, a drained battery shows up and nothing happens, (just like it froze there).
the phone is not taking charge and its dead jim. doesn't have enough charge to power on.
havent tried anything else.
any clues or workarounds?
please and thanks.
EDIT: downgraded to CM10.2.1 and installed chronic kernel for CM10.2, problem solved.
I have a Nexus 4, Running Oct-M and AK kernel.
Today the phone started to just turn itself off for no reason.
I turn it on, it is on for 2 or 3 minutes and turns off, even when plugged to a charger.
I can boot it up again but it just turns off again and sometimes stuck in bootloop and I have to go to bootloader and start it.
I am also facing similar issue since yest night..
Rom: Purity Lollipop version
i tried reflashing Rom but issue persists..
though my phone works when its plugged to charger.. but when I remove it switches off
m_harsh said:
I am also facing similar issue since yest night..
Rom: Purity Lollipop version
i tried reflashing Rom but issue persists..
though my phone works when its plugged to charger.. but when I remove it switches off
Click to expand...
Click to collapse
+1 problem.
Hi folks, my S5900i went weird on me in a hurry. Any tasks that used a lot of power shut the phone down. Rebooting was hit and miss. It started when I flashed a rom update (stock rooted) and a boot loop happened. Plugged in to power enabled a back up flash to get an OS. I first thought I had buggered up the update, but the fix was a new battery.
I hope this helps if users that get similar symptoms.
Hi! I got my Essential Phone from someone that had it boot loader unlocked etc. I have experience with flashing and all so it was not a problem for me. Yesterday when I got the phone I went here and flashed AOSIP Rom again since it was the one it had but a wanted to make sure to have a fresh install etc. All working fine by then until about an hour ago the phone turned it self off and now it doesn't do anything. Every time it finally boots it shuts down again. If I try and enter recovery or Bootloader for fastboot, same thing. Sometimes it holds up for about 20 seconds and goes back to Off and be unresponsive for a period of time.
Has anyone had this problem before? If so, is this a Hardware problem?
I can't fix it by computer so I don't know what I am into right now. Its the only phone I have so I'm kind of stressed right now
Even before I had issues it would stay relatively warm when just charging it at 5W (it still does that when it's turned off) so I started suspecting liquid damage (prior experience) or the battery starting to show its age even though it's only been charged about 300 times. This all started after I flashed LOS on it where hwc was disabled. The phone had pretty much stayed unused until late 2021 and was meant as a dev/backup phone.
After a second hard crash it stopped trying to boot and will now only enter Download mode and nothing else. Prior to this I only had to reflash it, but this time it's not looking so good.
I'm too facing the same, tryin to revive my cousin's s8, which is not even rooted once. Tried flashing stock fw using odin. It just doesn't show samsung logo but still goes to download mode. Any help devs?