Related
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
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 ?
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.
I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.
Working but not enough
Hey, first thank you so much for sharing your experience. It gave a guide to follow step by step which I really appreciate. I have tried the heating tecnique and has partially worked 3 times, google logo turns into the other google logo but at a really low speed, then it switches off my phone. I tried to start on Safety Mode as you said but it just says "Not command" nex to an android icon. Any aditional advice?. Thank you
Speed1908 said:
I would like to share my experience on how I saved my Nexus 6P which was bootlooping with bootloader locked and inaccessible recovery mode.
The problem started when I had updated my phone with latest OTA update 8.1.0 (Oreo). While I was browsing fb after the update, suddenly the phone froze and restarted. And ever since that moment it begun to bootloop. I tried to access recovery from Fastboot so that I can clear the cache which would most of the time resolve the bootloop issue however this time around I was unable to go to the recovery mode too. I wouldn't been able to flash from fastboot since bootloader was locked. There is no way to get around this unless I would be able to load the OS and go into Developer option to turn on "Enable OEM unlock" in the settings.
Since I would not be able to flash the stock ROM or get into recovery mode, I contacted Google support for help. They directed me to Huawei Support. Huawei told that since my phone is out of 1 year warranty they would not be able to service this phone and would cost me nearly $400 for getting me a replacement. Spending $400 for 20 months old phone was absurd.
I started to explore online what are the options available given the tight situation that I was into. I came across few forums discussing about using a heat gun above the finger print sensor to throttle the CPU which may stop the phone from bootlooping. I used a hair dryer to heat the phone while the phone is continuously bootlooping. I would heat for about 7 - 10 mins to an extent where I would not be able to hold the phone anymore. After nearly 7 to 8 failed attempts spread over 2 weeks, the magic worked.
The last attempt was slightly different. Here is what I did -
1. Battery was fully drained
2. I started to charge the phone while I kept it outside my window for about 20 mins. Temp outside was around 15 degrees Fahrenheit. (Did this step since I read somewhere that keeping the phone in refrigerator and restarting would resolve bootloop issue) However it continued to bootloop.
3. While the phone continued to bootloop, I allowed the phone to charge overnight.
4. Next day I saw that the phone did not restart like how it used to. It was stuck at GOOGLE and would not restart.
5. I disconnected from the charger. Went to fastboot and switched off the phone.
6. I started to heat the phone using hair dryer with the phone switched off for about 10 mins. I held it was a cloth since it gets hot pretty fast.
7. Paused for a sec, turned on the phone (it was bootlooping) and continued to heat the phone for another 5 mins. (by then I gave up)
8. Stopped heating. I left the phone and went out to work on something else. After half an hour, when i returned I saw that the phone was completely switched off and was not bootlooping. I got excited since I know that the phone was fully charged overnight and there is no way that the phone would have died due to battery drain.
9. I immediately turned on by holding on to the VOL down button. I selected recovery from fastboot. To my surprise for the first time in 2 weeks I was able to go into recovery mode. I cleared cache and restarted the phone in Normal mode.
10. Phone booted properly and loaded the OS.
11. First thing I did was to go into developer options and turn on "ENABLE OEM UNLOCK" option. (By now I knew how important it was to have this enabled. THIS COULD SAVE YOUR $549 PHONE!!)
12. Took a backup of all the files and unlocked the bootloader.
I downgraded the OS to 7.1.2 (Aug release) which I felt was a stable one for Nexus 6P. I also did a h/w check and all the tests passed CPU / Memory is fine. I am still not sure what could have caused the bootloop but the fact that it happened after the Oreo OTA would make me to stay away from upgrading the Android version beyond 7.1.2.
Click to expand...
Click to collapse
---------- Post added at 05:18 PM ---------- Previous post was at 05:09 PM ----------
I just waited like 5 or 10 minutes and my phone started in system. Just enough to activate stuff in developers options!
arkanthos said:
Hey, first thank you so much for sharing your experience. It gave a guide to follow step by step which I really appreciate. I have tried the heating tecnique and has partially worked 3 times, google logo turns into the other google logo but at a really low speed, then it switches off my phone. I tried to start on Safety Mode as you said but it just says "Not command" nex to an android icon. Any aditional advice?. Thank you
Click to expand...
Click to collapse
I just had this happen to me. Friday evening, I noticed an update and I usually read reviews prior to downloading, but I clicked anyways. All seemed fine until Saturday night, was in fb, watching a cooking video and clicked on a link for the recipe when my phone went blank and to the Google screen. tried for 2 days to reboot, get into boot-loader, recovery, anything!
Luckily, I have 9 more days on my Square Trade warranty. They required me to take to a fix-it store (all they could try was a battery pull, which was unsuccessful). Square Trade sourced me a replacement, so it came in last night and I am downloading all my apps and trying to get back "to normal".
I did do an Android update, at the urging of my son, since he has the same phone. Now I see one more, that is a small update. Worried if I should download or not?
I just found this forum and haven't yet gone searching for help on it.
This info is good to know.
Thanks and take care!
Thank you save my life again i have no hair dryer and place it on my rick cooking about 10 mins after that it boot slow gooe animated and i format factory and clear cach first try and succeeded
Hi,
My Nexus 4 has been acting up for some time. I had the infamous "optimizing apps" issue almost one year ago. Since then I used an app ("optimizer app fix" or something) to get around it. It's rooted, but I can't remember the details/versions.
More recently, the phone started to lose the network connection. I tried to change the setting from automatic to my home network, it did seem to help a bit, but didn't really fix the issue.
Yesterday I was using the flashlight, and just before I turned it off, the phone rebooted itself. From then on it became very unstable. If I leave it alone in flight mode, it will stay on. If I start doing anything, at some point it will shut down. If I keep it plugged to the charger, it stays on, though. So it looked like the battery is gone. I'm just not 100% sure because if I boot it into recovery mode it stays there apparently with no issues, for a long time. It could be that the current draw is not so big in that mode, though.
I have just finished backing up whatever I could, and wiped the data/dalvik/cache partitions from the TWRP recovery menu. Still not good. Did a Format Data from there too. No luck.
Given the cost and hassle and wait and the number of fake batteries in the market, I don't want to buy a new battery to revive this phone (knowing that it's likely to fail again sooner than I can expect). Is there anything else you'd suggest that I try before I go shop for a new phone? :crying:
Thanks,
VMat
vmat005 said:
Hi,
My Nexus 4 has been acting up for some time. I had the infamous "optimizing apps" issue almost one year ago. Since then I used an app ("optimizer app fix" or something) to get around it. It's rooted, but I can't remember the details/versions.
More recently, the phone started to lose the network connection. I tried to change the setting from automatic to my home network, it did seem to help a bit, but didn't really fix the issue.
Yesterday I was using the flashlight, and just before I turned it off, the phone rebooted itself. From then on it became very unstable. If I leave it alone in flight mode, it will stay on. If I start doing anything, at some point it will shut down. If I keep it plugged to the charger, it stays on, though. So it looked like the battery is gone. I'm just not 100% sure because if I boot it into recovery mode it stays there apparently with no issues, for a long time. It could be that the current draw is not so big in that mode, though.
I have just finished backing up whatever I could, and wiped the data/dalvik/cache partitions from the TWRP recovery menu. Still not good. Did a Format Data from there too. No luck.
Given the cost and hassle and wait and the number of fake batteries in the market, I don't want to buy a new battery to revive this phone (knowing that it's likely to fail again sooner than I can expect). Is there anything else you'd suggest that I try before I go shop for a new phone? :crying:
Thanks,
VMat
Click to expand...
Click to collapse
No. You need to replace the battery.
Sent from my Nexus 6 using Tapatalk
trent999 said:
No. You need to replace the battery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's what I thought. What a bummer.
Thanks for the reply. Happy new year, everyone!
VMat