S4 Not Charging - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Unplugged my phone this morning at 100%, went to charge it just now with factory charger and cable and nothing. Tried reboot and battery pull. Sitting at 60% right now. It's off in case I need to return to stock to exchange it. Any ideas?

Planktron said:
Unplugged my phone this morning at 100%, went to charge it just now with factory charger and cable and nothing. Tried reboot and battery pull. Sitting at 60% right now. It's off in case I need to return to stock to exchange it. Any ideas?
Click to expand...
Click to collapse
I had a bad cable, it is not the phone...damn cables were cheaply made.

Tried 2 cables. When the phone is off I get the battery icon with the circle in it, but it just loops this icon. It comes up, vibrates, turns off repeatedly. I tried to wipe cache and it said error. I'm rooted, defrosted everything I had frozen.

What I don't understand is why I'm getting an error when trying to wipe cache partition.I unrooted, so as far as I know im now totally stock. Is it safe to try to do a factory reset?

Planktron said:
Tried 2 cables. When the phone is off I get the battery icon with the circle in it, but it just loops this icon. It comes up, vibrates, turns off repeatedly. I tried to wipe cache and it said error. I'm rooted, defrosted everything I had frozen.
Click to expand...
Click to collapse
Sounds like kernel panic. Whatever rooting/custom mod/ blabla you have on that device is either buggy, badly flashed or something like that.
You need to have a good connection to Odin established, flash only stock rom (the untouched version/odexed), let it reboot normally from Odin, and wait. (it is important to have at least 50% battery left, you don't want it to quite on you in the middle of a flash)
Doesn't matter if it doesn't go all the way and setup the first time. Just pull the batter (after Odin rebooted), go into recovery, cleanup everything, and reboot.
Thank should get you back in the world of the living ...

http://forum.xda-developers.com/showthread.php?t=2261573&highlight=return+to+stock
So just do exactly what is written in this thread then? Do I have to go that far or can I try a factory reset from recovery?
Thanks BTW

Planktron said:
http://forum.xda-developers.com/showthread.php?t=2261573&highlight=return+to+stock
So just do exactly what is written in this thread then? Do I have to go that far or can I try a factory reset from recovery?
Thanks BTW
Click to expand...
Click to collapse
Easier things first, so if you haven't tried a factory reset yet then go ahead ( although that won't unroot you) try your factory reset first.
But then if your battery gets too low and still doesn't charged, you need to get it charged up first.
And yes that hotfile link is the original factory ROM dump, it is good.
That is the at&t stock file or you're on bell or rogers or ... get a samfirmware/sammobile account and download your ROM from there.

No dice on the factory reset, and I'm about 40%. I'm thinking I'm just going to exchange it. Device status says Official so I should be good, no?

Planktron said:
No dice on the factory reset, and I'm about 40%. I'm thinking I'm just going to exchange it. Device status says Official so I should be good, no?
Click to expand...
Click to collapse
you should be ok exchanging it although for most devices rooting voids the warranty
that was my main reason sending you the odin flashing route in case you wanted to exchange it but it is no big deal.

Well I'll be...
Did another factory reset from the settings menu this time, ON THE WAY to the AT&T store(while parked, of course), plugged it into the 'ol 12v and she fired right up. I agree about the kernel panic deal. I've had strange things happen before. The only thing that changed on my phone from last night until the no-charge state was the installation of SugarSync. It kept FC'ing so I uninstalled it. I think it may have changed some items deep deep in the areas of the OS that I know nothing about and it freaked out the bowels of Android.
Back when I had my Atrix 4G, I installed Dolphin Browser, and it sent my phone into a whirlwind of FC's.
Thank you for your assistance, Commodore.

Planktron said:
Well I'll be...
Did another factory reset from the settings menu this time, ON THE WAY to the AT&T store(while parked, of course), plugged it into the 'ol 12v and she fired right up. I agree about the kernel panic deal. I've had strange things happen before. The only thing that changed on my phone from last night until the no-charge state was the installation of SugarSync. It kept FC'ing so I uninstalled it. I think it may have changed some items deep deep in the areas of the OS that I know nothing about and it freaked out the bowels of Android.
Back when I had my Atrix 4G, I installed Dolphin Browser, and it sent my phone into a whirlwind of FC's.
Thank you for your assistance, Commodore.
Click to expand...
Click to collapse
That is always good to hear. thanks for reporting back.
Plus if you did reset it while you were driving, not that some people haven't ... , at&t will start making new screen stickers saying :
"don't factory reset your phones and drive ... it can wait".

Oh well. Since im a junkie and couldn't wait to re root, as soon as it charged back up I re rooted. All was well until I started freezing bloat, then it stopped charging. Got a replacement on the last day of the return period. Wish I knew what was causing this. Looks like im staying stock until we get recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

It's been a few days so I'm bringing this thread back from the grave, but I want to know if anyone else has experienced similar issues. It's really strange, what happened, and I'd like to know more about why it happened. I should have made a logcat but too late now. I'm not the type of person to experience something like that and take the easy way out with an exchange (I've experienced worse), but with my battery percent remaining an ODIN flash would have been risky at best. Like I said, everything was fine for days until I installed sugarsync.
I only froze bloat. Everything starting with AT&T, and some Samsung apps like S-Voice, ChatOn and push service.
Until I can figure this out or get custom recovery, I'm stuck stock because I'm not going to cheat again for another exchange.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

I had exactly the same thing happen to my rooted s4. Took it back to the shop i bought it ( Unrooted ) and they replaced it.

Same here.
I get it to charge sometimes for about 10 minutes and then it'll disconnect.
USB via the PC doesn't work as well.
I think replacement is probably a safest bet.
We aren't the only ones either...
http://forums.androidcentral.com/samsung-galaxy-s4/275276-galaxy-s4-wont-charge.html

This has just happened to me. I plugged it in last night with about 19% remaining, woke up this morning and it was at 7%-- hadn't charged. I tried a couple different chargers and cables, and nothing has worked so far. The charge has since dwindled to 4%. I'm running slimrom, and I guess I can't risk flashing back to stock since the battery is likely to die completely during the process.
When I did a shutdown and then plugged it in, I got the "charging" icon, of the battery with the green bar repeatedly moving up through it. But after leaving it for half and hour, I tried to boot it, and that was the point where it had gone from 7% to 4%, so apparently it wasn't really charging. Might have to buy another battery and see if that's the problem or the charging circuit in the phone.
---------- Post added at 03:01 PM ---------- Previous post was at 02:48 PM ----------
Ok, so this is weird. I have been using some older chargers/cables that I had left over from my Captivate, and they've been working fine for a month, until now. But I went and got out the charger that came with the GS4 and tried that, and although the ROM still says "not charging/connect your charger", the battery % is increasing. Very strange.

I think u need to get back to stock rom to solve this issue..and u won't get warranty as your device is rooted even if u revert back to stock your bincounter will ramain same that's of you had flashed your device twice with custom rom your bin counter will be 2...so samsung can easily understand it by going into download mode...u can also see the number of bin counts by entering into download mode screen ....so u need to reset bin counter before taking it to customer care otherwise they will woid ur warranty:thumbup:
Sent from my GT-I9500 using xda premium

Related

Phone locks up at 5am each morning.

I've had a SII for a couple of weeks now (new user to android) and I have flashed it to Lightning Rom 1.5. But even before doing this and also afterwards the phone seems to crash/lockup at 5am on about 5-6 occasions.
Is there any program/app I can install to monitor what is kicking in at this time so that I can disable/uninstall it?
Thanks
What do you mean by crash exactly ? Reboot ? Freeze ?
What you could do is plug your phone to your computer before it crashes, and start adb logcat, wait for the crash, and then look at the log to see what caused the crash.
It is completely frozen. I get up at 6:15am and the phone has a blank screen, but I can press a button to activate the screen and the clock is stopped at 5:01am and you cannot do anything else except turn the phone off and back on.
Maybe its the rom? Have you checked its thread? Try flashing bacm to stock. See if problem occurs.
Sent from my GT-I9100 using XDA Premium App
I checked the thread but doesn't appear to be anyone else with same issue. I might try the stock ROM to see if the problem persists. Although I sure it happened once on the firmware that came on the phone (KE2 I think it was).
scheduled backup?
I couldn't find any backups scheduled. So I wiped the phone last night and applied the Lightning 1.5 ROM again and it seems to have been fine this morning..no lockups.
Thanks for the advice.
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
OccasionalDroid said:
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
Click to expand...
Click to collapse
I'll keep that in mind if it happens again..cheers. Been OK this morning so shall see how it goes.
Its done it a few more times since I did a factory reset, always at 5:01am. After rebooting the phone and checking the battery stats it appears that 'Cell Standby' has used 52% of all battery consumption and the battery drained from 100% to 9% over 8 hours. The problem also occurs even if the phone is on charge over night.
So maybe it is a buggy radio? Gonna take it back to the store tomorrow to be looked at.

[Q] Nexus 4 shuts down right after boot every time!

Hi,
I don´t know what to do. I got my phone 2 days ago. All fine. Rooted right away and used only adfree and titanium backup to restore apps.
Today out of the blue my phone shuts down. When I reboot it shuts down again right after Android booted up. Every time!
Can´t use it at all!
Tried reflashin factory und relocking but still it shuts of right after start of Android. I can get to bootloader and wipe in recovery all day. That works but as soon as android boots up it shuts down again once you reach the lockscreen.
Guess my phone has a failure but I wanted to ask here first before returning it.
And honestly I did not do something kernel or rom or OC.
Can't tell you on the N4, but my vivid, anytime it started to do what you're describing, I had to re-flash the boot.img and reinstall the ROM to stop the boot loops.
Sent from my Nexus 4 using xda premium
I already did a factory reste via image flash. Still no good. Once you reach the lockscreen it shuts down "powering off"
temperature issue?, there must be some hardware fault that's forcing it to shutdown after all services are loaded or a issue with battery stats.I would restore it and rma, or somehow drain the battery then recharge it
republicano said:
temperature issue?, there must be some hardware fault that's forcing it to shutdown after all services are loaded or a issue with battery stats.I would restore it and rma, or somehow drain the battery then recharge it
Click to expand...
Click to collapse
Mine is doing the exact same thing. I have returned it to bone stock but no change. Will try to drain the battery but it might take days with just the recovery /bootloader screen on!
OP: were you able to fix yours?
instigator008 said:
Mine is doing the exact same thing. I have returned it to bone stock but no change. Will try to drain the battery but it might take days with just the recovery /bootloader screen on!
OP: were you able to fix yours?
Click to expand...
Click to collapse
Hi,
I did the same.....drained battery but afterwards it would not charge again all i got was a red LED and no hint to fix it helped me. Phone is completely dead.
I already ordered a replacement unit and am still waiting for it
Same deal with mine. It worked fine for 6 weeks, it was completely stock the entire time. I have sent it away for RMA.
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
Also, when I told the CSR what it was doing they had absolutely no hesitation to process the RMA, they didn't even suggest a factory reset, I'm assuming this must be a known issue.
Same issue/ diff reason
I have the same issue with starting up the phone and automatic shut down.
I dropped mine in the water, however. Nothing seems to be wrong with it other than this auto shut down.. I was thinking that the battery was possibly fried. I ordered a new one to see if that would fix it.
Mine is also rooted too, however. This was the issue of the above original post. If there is a solution for either of my issues, I would greatly appreciate it.
thanks!
Pmarsh91 said:
I have the same issue with starting up the phone and automatic shut down.
I dropped mine in the water, however. Nothing seems to be wrong with it other than this auto shut down.. I was thinking that the battery was possibly fried. I ordered a new one to see if that would fix it.
Mine is also rooted too, however. This was the issue of the above original post. If there is a solution for either of my issues, I would greatly appreciate it.
thanks!
Click to expand...
Click to collapse
Hey dude this the new battery work? exactly the same issue here.
Nexus 4 shutdown after boot
Hey guys
I tried replacing the battery and the issue still persists and also tried a few different roms including stock but it does the same thing.
My N4 is not under warranty any more. Has anyone got this issue fixed...??

[Q] Nexus 4 -- Only working while plugged in...?!

Yeah... I'm not great at titling... Anywho...
I've come across a problem, of which I'll attempt to go through everything I did that leads to the point, which is; my Nexus 4 doesn't turn on without being plugged into, either the wall or any PC.
So my phone crashes, solemnly (probably because I have Cyanogen on my phone), but lately (lately is in this past week), it's been crashing 3-4 times a day. Then, a few days ago, I was on it and it crashed again, this time, it wouldn't turn on -- my brother was (and probably still is) under the impression that I bricked it -- I would still be thinking the same but seeing as the phone turns on whilst being plugged in I'm wondering if the battery is shot, the hardware is shot, they're both shot or something more undesirable is happening.
I'm not blaming the app for this, however, the frequent crashing did start to happen more violently after I installed and used "Google Camera" for no less than 5 minutes -- at which time, I uninstalled the app and went to the Default Camera App, only for it to also crash the phone, thereafter, the phone just started to crash no matter what I did.
The phone also chooses when to shut itself off; sometimes if I unplug it, it'll turn off immediately, other times I've noticed it'll actually stay on for awhile (the longest its gone so far is 5-10 minutes). I was playing around with wallpaper when I decided to see if I might be able to use the camera, to my dissatisfaction, the phone crashed -- I noticed this when I looked back at the screen.
So now, for the last 18 (give or take 4 hrs) hours, I've been using the phone 'normally' whilst plugged in.
JJBerryere said:
Yeah... I'm not great at titling... Anywho...
I've come across a problem, of which I'll attempt to go through everything I did that leads to the point, which is; my Nexus 4 doesn't turn on without being plugged into, either the wall or any PC.
So my phone crashes, solemnly (probably because I have Cyanogen on my phone), but lately (lately is in this past week), it's been crashing 3-4 times a day. Then, a few days ago, I was on it and it crashed again, this time, it wouldn't turn on -- my brother was (and probably still is) under the impression that I bricked it -- I would still be thinking the same but seeing as the phone turns on whilst being plugged in I'm wondering if the battery is shot, the hardware is shot, they're both shot or something more undesirable is happening.
I'm not blaming the app for this, however, the frequent crashing did start to happen more violently after I installed and used "Google Camera" for no less than 5 minutes -- at which time, I uninstalled the app and went to the Default Camera App, only for it to also crash the phone, thereafter, the phone just started to crash no matter what I did.
The phone also chooses when to shut itself off; sometimes if I unplug it, it'll turn off immediately, other times I've noticed it'll actually stay on for awhile (the longest its gone so far is 5-10 minutes). I was playing around with wallpaper when I decided to see if I might be able to use the camera, to my dissatisfaction, the phone crashed -- I noticed this when I looked back at the screen.
So now, for the last 18 (give or take 4 hrs) hours, I've been using the phone 'normally' whilst plugged in.
Click to expand...
Click to collapse
Have you tried to make a clean install and not restoring anything to check if that helps? If that doesn't help I would try flashing a factory image.
theminikiller said:
Have you tried to make a clean install and not restoring anything to check if that helps? If that doesn't help I would try flashing a factory image.
Click to expand...
Click to collapse
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
JJBerryere said:
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
Click to expand...
Click to collapse
You download the full stock ROM from Google, and use fastboot to flash it. Here is a guide on how to do it. http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
JJBerryere said:
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
Click to expand...
Click to collapse
If you want a 100% clean flash, just download the factory image and flash it by executing the flash-all.bat (you are using windows I guess) script. It might be necessary to reboot into the bootloader first.
cheers
greg17477 said:
If you want a 100% clean flash, just download the factory image and flash it by executing the flash-all.bat (you are using windows I guess) script. It might be necessary to reboot into the bootloader first.
cheers
Click to expand...
Click to collapse
Tried this, didn't work.
My phone has basically been flashing red for awhile now and it doesn't turn on at all.
Your battery is dead, same happened with me 3 months ago.....
I took it to service centre, they just changed the battery (ask them specifically otherwise they will wipe data too, internal included)
Overall it cost me INR 1200 i.e approx $20
anupampb said:
Your battery is dead, same happened with me 3 months ago.....
I took it to service centre, they just changed the battery (ask them specifically otherwise they will wipe data too, internal included)
Overall it cost me INR 1200 i.e approx $20
Click to expand...
Click to collapse
Yeah, so I figured.
My father and I just replaced the battery with a Tablet's battery. Although probably not seen as proper. If it works, why fight about it? Haha.
Thanks.
JJBerryere said:
Yeah, so I figured.
My father and I just replaced the battery with a Tablet's battery. Although probably not seen as proper. If it works, why fight about it? Haha.
Thanks.
Click to expand...
Click to collapse
Your farther does not really worry enough for your health
https://en.wikipedia.org/wiki/Lithium-ion_battery#Safety

Galaxy S5 Reboot loop

Hi all,
My galaxy s5 is stuck in a reboot loop. It started doing this today around 12:18pm and I can't get it to stay on long enough to back up my data. I took it to AT&T and they basically did nothing but tried a different battery and booted into safe mode. Neither of those options worked. I took it to best buy and the tech installed the latest updated and flashed the ROM (I believe). Still didnt work. She believed the issue was with the battery but didnt have any new ones there to test so I went to batteries plus and tested a brand new battery, still is rebooting. I am home now and just wiped the cache in recovery mode, still not working. Is there anyway at all I can get this phone to turn on long enough to backup my data? Any other commands I can try to clear whatever is causing this? I was not using my phone when this happened. It died at 15% which I didnt make too big a deal of because I know the battery has been weakening, but when I charged it up for a bit then turned it on, this problem started. When I turned it on, I had a text message coming through and then it restarted. As I was able to get it on for a bit that same text kept coming in over and over again so I thought maybe something with the messaging app and I disabled that all together but the problem remains. I hope someone can help me out here. Thank you.
SOLVED: Samsung Galaxy S5 Reboot Loop
I figured out a workaround and I take full credit because this creative solution was no where to be found on the internet nor did AT&T, Samsung or Best Buy offer any other alternatives aside from wiping the device. This is what I did:
I booted back into Recovery mode and looked through the logs for any indication of what was happening. My assumption was that it was a driver error and so scrolling through the logs I saw an error that said something like fail psy battery. I immediately think maybe its the drivers for power so I thought I'd see how it would respond if I put it in Ultra Power save mode. Thankfully the phone stayed on just long enough for me to put it ultra power save which did work. The phone stopped the reboot cycle it was stuck in but I still was not able to back anything up since the Ultra power save disabled the USB drivers and port. I let it charge up overnight in ultra power save and said I would try regular power save mode in the morning to see if that would also work but this time allow me mass storage access. Well, that worked! I put it in power save and I am backing everything up now as I type. I've got all my pics and now just letting samsung switch do its thing to perform full backup. YAY! I WIN! Hopefully this helps someone else that may have this problem and have tried everything else that is recommended for solving this issue.
-Natasha
Chicago, South side born and raised
Don't really get it, what cause the boot loop in the first place? And you are flashing back to which rom?
I don't know what caused. I wasn't using the phone when it started. I hadn't downloaded any new apps and I wasn't messing around with the OS or system files. The phone battery died at 15%. I plugged in the charger and disconnected when it was at about 28%. I powered the phone on and there were a number of text messages coming through from my friend I was going to lunch with. I opened that message and noticed the text was duplicating itself then it rebooted. Each time I powered it up and got in for a bit that same text was coming through or trying to over and over again. So, I don't know what caused it but I have all of my data backed up and I am going to wipe it now.
Also, the Best Buy tech flashed the ROM so I am not sure which version or anything like that.
Aimara said:
Don't really get it, what cause the boot loop in the first place? And you are flashing back to which rom?
Click to expand...
Click to collapse
samsungGs5 said:
I don't know what caused. I wasn't using the phone when it started. I hadn't downloaded any new apps and I wasn't messing around with the OS or system files. The phone battery died at 15%. I plugged in the charger and disconnected when it was at about 28%. I powered the phone on and there were a number of text messages coming through from my friend I was going to lunch with. I opened that message and noticed the text was duplicating itself then it rebooted. Each time I powered it up and got in for a bit that same text was coming through or trying to over and over again. So, I don't know what caused it but I have all of my data backed up and I am going to wipe it now.
Also, the Best Buy tech flashed the ROM so I am not sure which version or anything like that.
Click to expand...
Click to collapse
which os phone on ? lop or MM ?

Help! Bootlooping out of the blue for NO reason

So... For no explainable reason my phone has gone into a bootloop, simply from me attempting to restart the phone.
Details of anything I can think of that might be related are below. I need a genius to help me A) figure out WHY this happend, B) help me figure out if there is a way to (non-destructively) get out of this bootloop (i.e. NOT having to do a factory reset), and / or C) tell me if there is a way that I can perform a full system backup using ADB, Fastboot or Odin with a phone that can't get past recovery or bootloader without going into an endless bootloop. I'm not a lazy guy and normally take the time to research problems and figure them out on my own, however at present this is my only activated phone, it's almost 11pm, I have to be up and out the door at 6am tomorrow, I will be judging competitions all day and will not have any opportunity to do anything about this until late tomorrow... In the meantime, I need a functioning PH1!!
My PH1 is the Sprint variant and I have not rooted it nor have I unlocked the bootloader. The only thing I have "done" to the phone is to sideload the latest OTA, NMJ32F (the day it came out, over a week ago, and it's functioned perfectly since that update). My phone has been in use throughout the day today with no difficulties. I went into a building with very spotty service for several hours this evening. On the way home, I noticed that I was stuck in 3G service, despite being in an area I know has good 4G/LTE coverage. I also noticed an unidentified icon on the status bar, a rectangle, which was located (I believe) to the right of the battery icon. It looked like a rectangle, perhaps representing a screen, or a phone? IDK. The other item of note is that I did sign into the guest account on my phone so that my daughter could use the stopwatch for timing competetion events without tampering with anything. She didn't drop it or get it wet or anything along those lines... she used it to time events, returned it to me in perfect shape. I logged out of the guest account, back into my account, rebooted to try to get the phone back into 4G service, and boom, I'm stuck in a frigging bootloop for no apparent reason.... And I'm about to lose my mind over this.
I CAN get into download mode and into recovery mode by holding the appropriate button combinations when it loops, but from there whether I power off and power on again or whether I select reboot from recovery menu, it continues to loop...
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
So I am running O beta rooted and last night this happened to me. I ended up going into fastboot and starting OS through there and I had no issue with the reboot bootloop. However, last night I went to bed with a phone @ 75-80% and woke up 6 hours later with a dead phone. Charged and rebooted this morn and everything seemed normal today. It was super wierd
Had to return mine for this very reason. Less than a week in service and went into boot loop. The reboot happened after it lost all battery power (corrupt filesystem?). Several factory resets did nothing to fix it. Removed the SIM. The phone was also fully charged. Did not try ADB as it was brand new and a return was the safest easiest option.
ccopelan said:
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
Click to expand...
Click to collapse
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
chray1 said:
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
Click to expand...
Click to collapse
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
fhlutiis said:
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
Click to expand...
Click to collapse
interesting.
If it's your second phone, have you looked at what applications you install?
The probability of getting two bad phones is pretty slim unless there is a major manufacturing flaw.
Not saying it can't happen, but it would be unusual.
Could it be due to Encrypted Data partition?
It once happened to me on a Huawei Mate 2 which I encrypted data and battery dead, then bootloop.
If that's due to corrupt encrypted partition, there seems only other recovery mode can help you get some files back.

Categories

Resources