Hey everyone, I've run into quite an issue.
My phone was in the charger working very well, I went away for only a few minutes and when I was back it was totally unresponsive.
I've tried to do a forced reboot, double click the screen, try to boot into recovery and fastboot. But so far no luck. Even upon inserting it to my PC and look at device manager, it doesn't show anything, not even when unplugging it and plugging it in again. Also have tried different adapters and so on.
I'm quite unsure what could cause this happening out of nowhere.
Could it perhaps be the bettery giving up? If any of you are able to come with suggestions before going out and getting a new phone, I'd be very greatfuld.
I'm running pixen-os 10.0. So far never experienced any issues, and been running it a long time.
Related
I guess **** happened...
At morning taking phone from the dock, I noticed some apps FC. And it continued sporadically along day, so at one point I simply decided to reboot. Phone turned of fine... However I was unable to turn it on immediately after. It was showing black battery. Whatever I did no dice. I even tried my wifes phone battery.
That happened on the road, so at one point I decided to plug it in. Oh miracle - phone booted with power!!! But then my troubles worsened, because I've noticed that it always shows USB connected, starts desk home in night mode, shows battary constantly charging. Stuff like this. I've tried factory reset, reflash to stock DJ05. Nothing helped. Now it getting worse, because screen started to blink when on power...
Does it sounds familiar to somebody? Need to replace?
After trying everything I can imagine, it is kind of obvious that I have HW failure. My problem is that in order to return it back to Verizon I need to have DI01. I did backup from recovery before flashing DJ05.
All this is fine, however I'm not sure if this backup will restore radio. I guess not. If not, how I can flash one? I'm having problems to get in download mode and I think ODIN is unable to detect port. Do we have radio zip i can flash with recovery?
My first fascinate had the same problem, had to return it.
Sent from my SCH-I500 using XDA App
It seems like USB is still alive, at least partially. After countless attempts I managed to connect it computer in download mode and flashed DI01. At first it looked like it fixed the problem... However now USB indicator changes on and off constantly. If you turn it off it reappears in a few seconds. Only upside is that comp sees it and I now have unrooted DI01.
Sad. My phone was in mint condition after over 3 months of usage. Who knows what kind of refarb I'll get.
So I've attempted to debug this best I could but I've come up with absolutely nothing thus far.
About a month ago, I'd say, I started having very infrequent complete lock-ups. I'd pick up the phone and try to turn on the screen and nada. It would still be running as the notification LED would sometimes pulse according to my Lightflow settings. Plugging it into my computer, it appeared as an unrecognized device and adb wouldn't be able to get anything from it. I've never had this happen while I was actively using the phone, mind.
Holding down the power button until it force shuts down and rebooting it works just fine, but it's a bit annoying and worrying to have it go blank every few days. Once, it was even completely working but the touchscreen would not respond regardless of what I tried.
I since did a factory reset, thinking it might've been a kernel issue (I was running on faux's kernel) and it went fine for a week but it just did it again... And this is on stock 4.4.2, rooted, without any new app in a long time (ie. I can't think of an app that I'd have installed when the crashing started).
Any ideas, short of writing it off as the occasional problem and planning on a much earlier replacement than initially expected?
Alright, so like many people, I tried to play Pokemon GO. I was playing for about 20 minutes on my break at work, and I noticed that as I was switching between it and other apps, my phone was getting pretty laggy and bogged down, to a point where the phone just froze for a minute, then when the screen turned off. I couldn't turn it on for a further minute or so. Eventually after a few minutes of this, the phone just crashed, Upon trying to restart it, it went to the odin screen, saying "mmc_read error", or something like that. I pulled out the battery and let it sit for a few minutes and tried again. It started to boot, but it was stuck on the phone's model splash screen for several minutes, which its never done before. After the phone finally got booted up, it would freeze often, and I would not be able to turn the screen back on for several minutes at a time. This has persisted all night, crashing and freezing for the remainder of my shift. After I got home I tried restarting it again, and the phone wouldn't turn on at all, so I again pulled the battery and let it sit for a while. I've done this a few times now.
Sorry it's a bit lengthy, but I tried to recreate the events of what's happened as best I could. If you need any other info just ask
I have uninstalled the game from my phone now, the phone is completely stock, no roms, not rooted. I do not recall it feeling too hot as if it had overheated
I really am not experienced with issues like this, and I really would not like to have to buy a new phone
Hmm, that error is supposedly of the EMMC failing, now you will be lucky if it was a one time incident. Now to be quite honest I don't think anyone could tell you that whether the problem will come back or not, and you can't do much anyway. I will say if the phone is running okay now, let it. Or if you are really unlucky then the problem will come back, the EMMC might fail permanently. But if you see one or two more reboot incidents like that, I think its fair to conclude that your phone is done mate.
Currently I can turn on the phone, but after I turn the screen off, it won't come back on again
Oh darn mate. You could try to wipe the phone completely from recovery (TWRP) and then flash the stock ROM. Now please don't blame me if the phone gets dead or something after that, cause my Note 3 died just few months back, and it took me a good couple of months to get over that fact. However one thing is for sure, if your emmc is supposed to fail, or motherboard, then it will no matter what.
Hello! Okay so this is a weird issue with my phone. It started in November and i had to switch to an older galaxy s5 which is pretty slow for today's standards. Anyways one day while it was charging it started to reboot and didn't stop. I didn't think much of it. I took the phone apart to make sure it wasn't shorting out or anything. I reset everything on the phone. I replace about half the phone. I really need the phone to work because I need the speed. So the full problem the phone would turn on and boot but right when it going to the lock screen it would restart. Sometimes it boots all the way but it crashes and reboots about 1 minute of use. I cannot find a solution. I tried flashing a the original rom and it still didn't work. I put the boot loader back to stock. I tried to reflash the kernel, that also didn't work. If watched a ton of tutorials but no one seems to have the same problem.
I bought a droid turbo 2 about a year ago, and after a few months of use it was dropped into a sink causing minor water damage. Other than minor screen bleed everything seemed to have been in working order after a few days of drying.
About a week and a half after it finished drying and was in use, the phone shut down and went into a boot loop. It will boot to the motorola M but after 30 seconds it shuts down and restarts.
I have tried doing a verizon update from my computer but after the program says "updated" my phone is unable to restart dissallowing the update. I do have the ability to boot the phone in "fast boot" or "recovery mode", But if i go into recovery mode and do a factory reset the problem persists through it.
I figured the best way to try and fix my phone would be to flash a factory android version onto the phone, but that is where i am running into issues. Maybe it is my lack of understanding of ADB and flashing, but i dont understand how i am supposed to allow debugging on my phone if it is already stuck in a boot loop? I also am running into the issue of my phone not being recognized by the ADB daemon. even though the verizon updater recognizes it and allows for an update. Please any help from somebody with experience with these sorts of things would be extremely appreciated.
Bootloop after disconnecting charger, tried everything
I am having same problem after disconnecting charger from phone, went into bootloop. Did you ever fix yours?
Same problem, different reason.
Goes to Motorola logo and restarts until battery dead. I have flashed up-to-date stock ROM both with "Verizon Software upgrade" program with windows 10(once) and 7(several times), and have flashed with old "RSD lite" in win 7. Both flashing methods worked flawlessly and says "successful". but still looping. Have tried draining battery to totally dead and full recharge, no joy. Can boot into recovery fine. Did full factory resets, etc. Thought battery may be problem, but battery lasted full day or more before needing recharge before problem, and drains normally now with constant restarts, but gets hot. (plugging in to check % charge after restarts says still in 90+% range after many restarts).
I know this is an old thread, but any suggestions are appreciated. Cant understand if flashes good, why cant restart.
Old thread, old problem -- my problem, as well. (In my case it's a hand-me-down phone for experimentation; all my own androids are rooted starting with my first.)
This 'Droid Turb'o 2' worked fine until left alone a while, after which time its battery then seemed to lose its "elasticity" as it were, resulting in poor charging/capacity characteristics, and then shortly thereafter, this annoying and horrid bootloop. (It's also a Verizon phone, they like to "tighten-up" the phones they sell to one, or so I have read.)
All I have to offer really, are my observations, and possibly some insight. My suspicions of something to do with the current flow/battery-drain are also pure conjecture, and perhaps an educated guess at best. I, too, continue to solve this mystery because it's somewhat atypical of my own android experiences, and this is the sort of knowledge that broadens the spectra of engineering as a whole (and the suspense sometimes can give one a hell of a headache).
For now, my conclusion is that this appears to be a problem specific to a particular model that is no longer made, and perhaps for good reason. I still hope to find this mystery solved some day.
73 DE N6BHU