Hey, I'm having some trouble with my ROM'd HTC Hero, running RegawMOD. She was running beautifully for a few weeks before today, where, after her battery dying, she refused to boot, entering an infinite loop cycle. I don't have a recent Nandroid so I'd like to avoid backing her up, but so far I can't get her to run properly.
Does anybody have suggestions? Could this be due to an application I was running? Her battery was dying unusually quickly, if that helps. And I recently installed AntPlayer.
Update: I've since attempted to restore my phone to her first available NANDroid backup, still got stuck at the boot screen, even after the boot screen I was using (the Nexus One boot) was replaced with the Hero's original boot. I feel this could be a hardware issue?
HZ.
Have you tried wiping/re-flashing?
If that doesn't work, it could be full memory, bad recovery(based on the nand fail), or bad hardware.
Related
Hi everyone,
while using my Note earlier today, it suddenly shut off (with about 75% battery) so I assumed it was just a crash. However after rebooting I could only reach the homescreen and after a few seconds it shut off again. This happened 2 more times.
After that I couldn't boot intro Android at all anymore. After displaying the Samsung splash for about 1 second, the phone shuts off. I tried things like removing the battery for some time etc..
I can boot into CWM where I tried to make a backup. After confirming the start of the backup, the screen image distorts for half a second and the phone shuts off. Then after connecting the charger, creating a backup was successful. Trying to boot into Android still didn't work though.
I did a full wipe and tried another ROM without success. The phone shuts off either after the Samsung splash screen or 1 second after displaying the boot animation of the ROM.
Is it a battery issue or could it be something else?
augenleet said:
Is it a battery issue or could it be something else?
Click to expand...
Click to collapse
Why don't you verify the first part of your question yourself? After that the second one would make sense.
So: new battery first.
ThaiDai said:
Why don't you verify the first part of your question yourself? After that the second one would make sense.
So: new battery first.
Click to expand...
Click to collapse
I've ordered it, it'll take a few days to arrive.
Just in case anyone else runs into this issue. I found that my Galaxy Note was doing exactly the same thing and it was a dodgy or dying battery.
I could run CWM or Android Recovery or Philz Recovery and I could also flash the stock roms with ODIN but after the flashing, the phone would boot to various stages (N7000 splash screen, SAMSUNG splash screen, "Updating Android" screen and then turn off. After flashing a dozen times I worked out it was the battery. Replaced it and all sorted.
I ran into a same kind of problem once. Factory resetting the phone fixed the problem for me.
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
GreenMunky said:
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
Click to expand...
Click to collapse
If a factory reset does not fix the issue, all I can suggest is find the thread "Return to Stock" and follow the instructions to flash the entire stock SBF for your carrier. This should fix any corrupted files, if present. Either option WILL erase everything, so backup anything you need first.
Good Luck
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
KJ said:
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
Click to expand...
Click to collapse
Nope, phone had been off the charger only a few hours, still had 85% or so. I actually tried plugging the phone in while it was booting up to see if an extra jolt of juice would somehow help it to fully boot up... made no difference. After 6-8 failed boot attempts, it finally booted up and has been running fine since... although I have yet to try to manually reboot it.
Well, if it acts up anymore...I'd consider a full wipe and return to stock. Same android version you're on now of course.
Otherwise...probably a fluke. ?
First, I will say that i'm not a developer. I am familiar with backups, rooting and custom roms. I'm just at a total loss with a total loss phone :/
So here's the rundown of my issue/s with my Moto Turbo (XT1254)
The phone is completely "unmolested." My phone is stuck in boot loop, currently. I did bust my screen a few weeks back but it had been working just fine. I picked up my phone to check texts, and I saw the "updating 24 of .... apps." Once finished, it's been stuck in a boot loop since. (Odd thing, my screen now shows split Moto image when trying to boot. Ex: a slot machine with only 2 roller wheels that wont match up)
I have tried to clear the cache several times with no luck of it booting up correctly. I do have files that I was trying to recover since they are not linked to a cloud account, and was trying to avoid a full on reset. I did, however, get frustrated and even tried to reset it back to full factory settings. That did not work either. So, all this being said, I'm back to trying to recover my files (my daughter's first year of life, family stuff, etc), since I cannot get it to even preform a factory reset. Does anyone have some guidance or same issue on this matter? Again, I am trying to salvage my files now while stuck in soft brick / boot loop status.
Thanks any and all who can help me with this!
******* Solved********
I have better diagnosed and fixed my own issue. I'm sorry I don't have pictures or video to better document what I did, but in short, it was as simple as replacing my damaged screen/digitizer, with a new one.
My theory was that during the update, the phone checked over it's systems and found that the digitizer was non-responsive in a few very small areas (this I already knew from using it a couple weeks with the screen damaged) and it somehow caused it to go into a boot-loop. My experience with fixing Playstations 3's, helped shed some light on this for me. I had a PS3 i thought was in good working order, updated firmware to it, and it bricked the system. Come to find out, the blu-ray laser head was no good. Upon the firmware doing system checks, it found that was bad and ended up bricked.
I did replicate the problem by switching the broken screen and new screen back and forth 2 more times after the initial fix. Upon disassembly, (youtube for teardown vidoes) you disconnect the battery from the logic board anyways, so when you boot the phone up, it does a app check and system check again. Every time the damaged screen was connected to the logic board and then powered on, it would end up in boot loop. The new, undamaged screen, would do the required checks, then boot up like normal.
I will do my best to borrow/rent a camera soon, so I can make a short video to show this works.
I'm not going to promise this will work for everyone but with replicated results, hopefully it's a fix for someone!
I hope
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Note 5 crash
Yep, have the same problem, but I have not attempted to Flash the Phone yet...
Did multiple factory resets, clear caches... but to no avail. There is no structure or pattern in crash rate. Although it is getting more often day by day...
Found no working sollution, but it feels like there is a bad memory segment or something. Everytime it randomly uses that segment... crash!
Really don't know. Will try to get warrenty fix.
Let me know if you found a sollution on your side?
Cheers,
Wim
kbiscu1t said:
Hi,
I've owned my VERIZON Samsung Galaxy Note 5 since early December and have not rooted the device. Today while taking notes in lecture, the device began displaying notices for crashed background apps (Gmail has crashed, Nova launcher has crashed, etc.) The problem persisted for another hour, even after booting into safe mode. I wiped the cache and factory reset the device, however during setup, Samsung keyboard would crash along with other apps running in the background during setup (One time I got "Samsung Galaxy has stopped working"). The phone started increasingly randomly rebooting since the phone first began to malfunction.
Since the factory reset didn't seem to actually reflash the firmware, I downloaded OJ3 stock ROM and flashed successfully using Odin, however the phone began acting even more erratically and failed to boot 4 out of every 5 boot loops. I tried flashing OGJ, which failed to boot worse than OJ3. I just flashed OJ2, which seems to be more stable than the other flashes I tried, however I'm still getting sluggish performance, random reboots and crashes of background apps immediately after booting.
At this point I believe it is defective hardware and I should call in the warranty for a new phone.
Has anyone experienced similar issues? Any speculation on the source of the issue? What should I know going into attempting to exchange for a new phone?
Click to expand...
Click to collapse
OP here. Made a warranty claim, they seem to have replaced the motherboard as the solution. Complete repair experience from warranty claim to package back at my doorstep was less than two weeks, which is impressive for what I've heard about Samsung's support. Good luck!
Hello all, new to the forum, though have been using it for issues I've had along the way with my Sony Xperia Z3 Compact.
Presently it is in a boot loop. It will boot up, and the phone is usable for approximately 2 minutes before it shuts down and immediately restarts. Only to do the same thing over and over. It also takes 2-8% out of the displayed battery remaining each time. Generally the battery is getting really hot though all of this.
Each time it registers as a "System Incident" in the diagnostics. Though no details are given. Does not register the crashes as "restarts" in the diagnostics.
Here's the kicker: It will NOT boot loop and operate normally (without overheating) if the phone is connected to a computer via USB or if it is playing music or a movie. But, once either of these conditions are no longer, it goes right back into restarting itself.
Here's the phone info:
D5803 (Originally a Canadian market phone)
Android version 5.1.1 (has been since I've owned it)
Build Number: 23.4.A.1.200
Unlocked
NOT rooted
No SD card mounted or present
Here's what I've done:
Hard reset (multiple times)
Boot in safe mode (will still boot loop in safe mode) restart in regular mode.
PCC repair, twice
Gone into service mode and wiped customizations
Complete factory data reset
*Done all of the above WITHOUT restoring my backup files in case there was a corrupt file within those backed up. Also have tried reset attempts with and without re-downloading my normal array of apps from the Play Store. Though none should be crashing the OS.
Even took the Flashtool to it, and reflashed 23.4.A.1.200 Customized US firmware with APPS_LOG and USERDATA wipe, no exclusions. Though, I was suspect of this, as the firmware is US, and on initial setup, it still defaulted to "English (Canada)" for the language on the first screen. Which is where it usually defaults. So I don't think memory was totally wiped or the firmware was reflashed in its entirety.
I would suspect hardware if the phone was not functioning properly while playing music or a movie. I have all functions and all systems working properly otherwise, even during the boot loop, just before it crashes.
Had a similar boot loop issue when 5.1.1 came out, much like many others. That problem righted itself with a few restarts and a full night of being totally shut off. This is not fixing the issue this time.
Thanks in advance for your help. All is appreciated.
Yeah, so this seems to be a hardware, i have had this happen to me, although just randomly.
You should send it off to be repaired, as restoring software should have fixed the issue.