Hey guys,
I was using my phone today and decided to turn it off. I am currently on 5.1 and I am rooted on stock. When I turned it back on, I was kind of stuck on a boot loop but I can usually bypass this by holding down the power button until I feel a quick vibrate and then my phone starts doing the "Optimizing Apps...". However, it didn't do that this time so I decided to reboot my phone into recovery, wipe the cache and dalvik and restart. Again, stuck on the boot animation screen. So I just let it run its course and then all of a sudden I see my phone go to the home screen but my launcher is reset and I am running out of cache space. I decide to connect my phone to my computer and backup some files. As I backup the last of my DCIM folder, my phone reboots and all of a sudden I have the new Motorola boot animation with the stitching I guess. But then I'm stuck at the bootloop again.
Anyone else experience this or know how I can fix this? I reaaallly don't want to factory reset.
I recently did a reset via settings on a gen 1. No change in boot animation. I then did a reset via stock recovery and got the new animation. I then did another reset via settings and during the first boot it had the old animation but subsequent boots have the new animation.
Related
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.
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 ?
I got my moto x today, updated it right away to lollipop, then went to work unlocking the bootloader, rooting, and installing TWRP.
All worked great, and then i went into TWRP to do a factory reset so that I could have the setup wizard when i turned my phone back on to set it up.
well after I did a factory wipe in TWRP (now i am thinking maybe i also checked to wipe system as well, but im not positive).
after the factory reset my device boots to the boot screen, and stops on the blue m logo at the end.
So i flashed the stock kitkat images using mfastboot, and it boots to the boot screen and then shuts off, doesnt even hang at the end anymore.
What are my options/ what the hell did i do?
Was running stock 6.0.1 in unlocked mode, and applied the 7.0 OTA Tuesday AM. Phone booted fine, with the exception that the 6.0.1 boot animation displaying. Phone booted into 7.0, so whatever. worked great for 2 days, when i woke up yesterday screen wouldn't turn on, so hold the the power button and re-start. Phone got to boot animation and stayed there for an hour until i shut it off, never got to the pattern unlock screen. I've tried wiping it, factory resetting it, installing TWRP to wipe and install, nothing, still stuck at the boot animation, no matter how long i let it sit. I've tried flashing other roms, with the same results. I can get into bootloader and recovery without issue, and can flash without errors (that i'm aware of) but always have the same result. Any thoughts? Or am i going phone shopping today?
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?