It has been quite a while since I messed with a hero. My nephew had to have his replaced thru asurion. I got the phone and rooted it using regawmod tools and it rooted just fine. I then replaced the cw recovery with amon. I flashed the fresh 2.4 and after a while it booted up. It works fine and I can install apps and use the data connection. If I reboot the phone or power it off and then back on, it won't boot. It goes past the splash screen and then plays the boot animation over and over. It will play for a bit, vibrate and then start playing the boot animation over again. It sat like this for over half an hour. I have tried doing a factory reset and formatting the system, boot, and data but it keeps happening. I tried a different rom and the same thing happened. Any ideas how to fix this?
[SOLVED]
I fixed it by booting to recovery and telling it to fix uid.
Related
It's been randomly crashing and and shutting off a lot lately. Today, whilst on a call, it shut off and wouldn't boot back up.
ClockworkMod still works and I have wiped boot, system, data and cache and then re-installed CM7 (the rom it was on when it died) but it hangs at the boot ani. Tried a rooted 2.3.4 and it hangs/reboots on the X.
It's had the mobo replaced a while back - could this one be dead now too? Or is there something else I can try?
TIA
managed to get it to boot again with updated hboot (spl) from here:
http://forum.xda-developers.com/showthread.php?t=744605
Hi - need some advice on my Galaxy Ace S5830T.
For some history, I rooted it a year ago and installed clockwork mod recovery. Apart from loading a few apps that need root privelage I haven't done much to it, ie has standard rom etc.
The other day a couple of applications came up with the 'Force Close' Screen (internet, facebook). Normally I just click on OK and everything is fine, but whenever I ran either app I got a force close error straight away. Used my app killer to shut down everything running, still had same problem.
Switched phone off and went to reboot, now it displays initial "samsung" screen with web address, flashes the Telstra logo in a few colours, displays "samsung" in the glowing letters, then hangs for a while. Goes back to Telstra logo and repeats.
I can boot into recovery mode. I tried restoring the boot partition from a backup I made before rooting, but it made no difference.
I've tried wip;e data/factory reset, wiping cache, and restoring the image, but it's still stuck in the boot loop.
The fact that I can boot into recovery means, I assume, that the hardware is still all functional, so can anyone advise what to try from here?
Thanks.
Woke up to my phone at a fully white screen. I shut it off, but every time i turend it on it would simply freeze at boot animation.
Figured it was time for a new rom anyway so flashed paranoid android and it worked. Rebooted and it froze during boot animation.
Tried Android Revolution, Cyanogen Mod... all jsut start booting then freeze during the animation (all different animations). Sometimes they'll freeze for a while, then the animation runs for a second, then freezes again. Never ending. Wiped the whole device, clean install. Not sure what could possibly be going on.
I still have access to recovery (twrp 2.7.1.1/adb/fastboot).
It's awesome timing as i just got a moto360 yesterday... anod now can't use it as my phone is dead!
madorb said:
Woke up to my phone at a fully white screen. I shut it off, but every time i turend it on it would simply freeze at boot animation.
Figured it was time for a new rom anyway so flashed paranoid android and it worked. Rebooted and it froze during boot animation.
Tried Android Revolution, Cyanogen Mod... all jsut start booting then freeze during the animation (all different animations). Sometimes they'll freeze for a while, then the animation runs for a second, then freezes again. Never ending. Wiped the whole device, clean install. Not sure what could possibly be going on.
I still have access to recovery (twrp 2.7.1.1/adb/fastboot).
It's awesome timing as i just got a moto360 yesterday... anod now can't use it as my phone is dead!
Click to expand...
Click to collapse
you say you wiped did you ever format data ?
have you tried re-flashing the firmware
have you tried flashing stock recovery / factory reset from stock recovery ?
Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.
Today I had to reboot my device and now my touchpad is stuck on the boot screen (the spinning logo). I used Clockworkmod to clear the cache and dalvik cache, but it doesn't seem to have done anything?
Sometimes I'll see the Android is Updating/Optimizing apps screen, but it'll stop and go back to the spinning logo boot screen.
If I leave it running for a long time, will it boot into the system? Is there anything I can do to recover the system? I'd like to avoid deleting everything if I can.
Edit: after 10 minutes or so it booted into the system but then it immediately restarted and went back to the spinning logo again...
Thanks.
A bit of an update. I restored an old backup I happened to have and it worked... up until the tablet started to update itself. At some point, it rebooted and was stuck on the boot screen again, so I am assuming that some update is causing the problem.
Is this fixable or should I just move to a different ROM at this point?