I've enjoyed this phone the entire time I've had it but in the last ~6 months it's gotten less and less reliable, to the point that it crashes and restarts itself randomly at least twice a day.
To be clear, this phone was unrooted, locked and on stock firmware when the first symptoms appeared. The first symptoms were that it would fail to connect to bluetooth in my car about once every 10 times. That became more and more frequent, then it would randomly FORGET all my bluetooth pairings and it would work for a while then progress in the same manner.
More recently it would start rebooting itself (when I wasn't even doing anything -- it would just be sitting on my desk and reboot) -- and now it has started to do this but get stuck in a boot loop.
So I figured I would take the plunge and try a new rom if everything else failed. I installed Lineage OS and so far everything has been good, but now twice it's crashed, rebooted, and been stuck in a bootloop and had to be factory reset *again*.
Is this phone just defective or is there something I can do to fix this?
Sounds like a defective eMMC chip... Not common, but hardly unheard of.
You can try going back to stock, performing a full factory reset, and add nothing but essential apps.
Otherwise, without a realtime logcat of the reboot to determine the cause, it's all speculation.
Related
My G1 has recently started playing up. The problems first started with cyanogen 4.1.9999 - it would loose signal, but a reboot sorted this out and it may only happen once every two or three days if that. It was an unstable ROM, no biggy.
But then one day, after rebooting, it got stuck at the android screen then just turned itself off. This repeated several times before it just wouldn't turn on. I left it for a while and tried again later, it turns on, boots but no signal. Rebooting did nothing.
I reflashed (without wiping) cyanogen 4.1.999. and everything seems okay. But then the phone started crashing and rebooting rather a lot, and rather unpredictably. So I wiped, flashed the ADP rom and then cyanogen 4.2.1 rom. This process was a massive brainache - plugging in the usb cable managed to crash the phone within 2-5 min guaranteed, it automatically rebooted.
So here I am. Cyanogen 4.2.1 - after a complete sdcard format, wipe, ext3 repair and flash. The problems still persist! But it's temperamental, a lot of the time I loose signal still, it often reboots itself and hates anything plugged in the usb when it's turned on - making charging the thing awkward.
I used the log collector app to get these logs
http://nopaste.info/17b5351296.html
http://nopaste.info/2e98b9d044.html
At some point during those logs, the signal is lost. The log collector doesn't seem to retrieve a very long backlist, these were taken minutes apart but don't overlap, so I haven't caught a crash. I'm not sure if there are better ways to view logs/debug?
But it's all very temperamental. Occasionally it boots up and life is fine. But more often than not it will loose signal and reboot itself somewhere along the line.
Has anyone come across anything like this before? When it looses reception if I manually try an connect to a network it will say
"This SIM does not allow a connection to that network"
Click to expand...
Click to collapse
I've read that could perhaps be a problem with the sim... but the sim wouldn't cause reboots would it?
Any advise would be great. I bought the G1 off ebay just under a year ago, so no warranty.
This is an ongoing, intermittent and devastating problem I have. My phone will be working perfectly fine, then all of a sudden it will randomly reboot. Then it will work for a few minutes or hours, then randomly reboot again. Then for a shorter time and reboot again until the phone basically can't even get through the bootup process without rebooting. It will be essentially bricked for anywhere from 1/2 a day to nearly a week (though it usually manages to get to working for 15 minutes at a time for most of the week. Then, all of a sudden and for no reason I can tell, it will just start working fine again for anywhere from several days to a month. This has been going on for at least 6 months.
It reboots during any manner of activities with the most common being phone calls, texting (I usually use Handcent Next SMS), anything with the keyboard (stock), browsing, swiping on the home screen, etc.. Really anything causes it, including it just sleeping with the screen off. The same problem occurs when in Safe mode, with or without the SD card (using as just extra storage, not phone memory), and with or without the SIM. It doesn't matter if it's plugged in or not. I have noticed what seems to be a greater tendency for rebooting to occur when the battery is low.
I am on T-Mobile (if that matters in any way for OTAs and such) and running the stock ROM without root. I'm about to try a factory reset but that has not been a permanent solution in the past.
so I just did the factory reset and it rebooted during the initial phone info setup (select your language, etc.)... I think it's toast... Does anyone know if this is the sort of thing that can be repaired for <$100 or should I just buy a new phone from ebay?
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 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
This may seem like a noob thread (which it probs is) but my issue is probably rare in htc 10 phones. You see.. my htc 10 just randomly decides to reboot from time to time. I've noticed some pattern to it but it still does not help. The reboots occur randomly. Some days, no reboot at all. Other days, it reboots so many times. Reboots more noticeably while watching videos (I got the phone knowing this problem). So, a logical person might say, "Hey, why don't you reset to factory settings/why don't you flash stock ruu/use htc repair tool or sync manager." To which, I reply, "I have done literally everything I can except getting it s-off and flashing custom rom on it. And the best part? when I select repair on htc sync manager, it says, "No software available for your device""
It may be a hardware issue. Most people say that it could be related to battery. If it were related to battery, the phone would just completely shut down and restart. However, in my case, the phone hangs or freezes for about 10 seconds and is unresponsive till it finally shuts down and reboots. I've put in safe mode as well but still no luck.
I've completely gone into zen mode now. I don't watch videos anymore xD
Help would be GREATLY appreciated. Thanks.