So, I was running Anerik's Unofficial CM12 but decided I wanted to try out the GPE 5.0.1 .
I followed "The Ultimate Guide to flash 5.0.1" by pfufle and it seemed to work fine.
I used Titanium Backup to restore a few apps and then restarted my phone because that's what you are supposed to do after restoring apps.
Only problem is that after the reboot, it would get past the Boot Logo (The Google logo with the unlocked padlock) but then stay on the Boot Animation (The 4 colours moving around) eternally (I left it there for around 20-25 mins.
I then got fed up of waiting and decided to retry flashing 5.0.1 by following the guide from the start and flashing gpe 4.4.4 then 5.0.1 etc.
Same problem. I tried maybe 4 times all of them ended with the same result.
I gave up and then went back to 4.4.2 from which I flashed Anerik's CM12 again.
I restored my apps via TB, restarted my phone but what do you know. Got past the Boot Logo but got stuck on the Boot Animation (The one with the CM Logo and the arrow spinning around) eternally.
I haven't checked if this problem happens in 4.4.2 and GPE 4.4.4.
How do I fix this?
Related
I had installed Mokee OS 4.3 as my main OS (System_1 in Boot Menu Manager). When I flashed Gapps for Android 4.3, it got stuck at black screen during startup, so, I flashed "p3_edison-edison-user-4.1.2-6.7.2_GC-404-434-release-keys" using RSDlite (which I did many times today and it worked) and it is now stuck at the boot animation, whereas in RSDlite it shows as PASS, what should I do? Please help! :crying:
UPDATE : Solved! I was flashing JB leak 3 which is an update, but there was no ICS present, so I had to flash the ICS sbf first!
Sorry, I don't know how to delete the thread.
Hello everyone!
I have a mexican (Telcel) Moto G XT1032. I installed the GPE ROM on it, then did an update to Android 4.4.4.
Today I wanted to try AeroKernel. I booted onto TWRP and performed a boot backup.
After that I installed the new AeroKernel release from today. It worked fine, so I downloaded its tweaking app and started playing a bit with the undervolting. It worked fine for a while, so I marked the checkbox to keep the changes after a reboot.
Then I performed a reboot and, after the initial logo, got a black screen instead of the boot animation. So I went to TWRP and restored my boot backup. But still, black screen.
Anything I can do to restore the original volt values?
In advance, many thanks.
What I ended up doing:
- Went into TWRP, backup my data and move the backup to my PC.
- Restored GPE and updated to 4.4.4.
- Get the data backup from PC to my phone.
- Restored it with TWRP.
Took me some minutes but I'm OK again. :silly:
I accidentally (don't ask) wiped my system while trying to install cyanogenmod. After doing that CM seemed to finally successfully install but it was stuck at a bootloop. I went back into recovery to restore my backup but it resulted in an error the first time. I tried it again and it said it was successful. I tried booting that up but the boot logo looked different than before and it wouldn't boot. It wasn't a bootloop but it was stuck on the boot logo. After trying a few more different things nothing worked and I decided to flash the stock firmware back. When I tried RSDlite failed the flashing process. Maybe I don't have the right firmware for my phone or something. I can't figure it out. I'd really appreciate anyone input on this. I need to get my phone up and going again as soon as possible. It's a Droid Maxx. It's not the Dev Edition but it does have an unlocked bootloader.
Thanks
EDIT:
I tried flashing that firmware again and for some reason it worked the second time. This thread can be deleted.
If you find it wont boot past the CM bootanimation, go back to recovery and Factory Reset - that normally will get it to complete the boot process. Make a backup first so you can easily restore back if you choose. Beats RSD back to stock and starting over...
I also run an unlocked Droid Maxx, non dev, currently on AICP ROM or CM, whatever flavor I feel like and who is updating their ROM the most often.
Last week I manually flashed 5.1 on my Nexus 5, because it was rooted an OTA update didn't work. It was working just fine, till yesterday. It's not rooted and it doesn't have custom recovery installed. My battery died and phone turned off. I charged it over night and turned it on in the morning. The phone was booting longer than usual so I left it and came back 2 hours later. It was still displaying boot animation. It's not restarting or anything, it just shows boot animation. I restarted it to bootloader, flashed 5.1 with Nexus Root Toolkit, the phone again stopped at boot animation. Then I went to cmd, used fastboot and erased partitions, flashed it again, it still didn't work. Then I flashed 5.0.1, it still stopped at boot animation. Then I flashed 4.4.4, it booted, play store didn't work, but I managed to install 5.0.1, this time over OTA. After it rebooted, guess what happened. It still stopped at boot animation. After that I installed TWRP, went to recovery, wiped ALL partitions and used TWRP partition repair function, rebooted to bootloader, manually flashed 5.1 AGAIN and my Nexus is still stuck at boot animation. I even tried erasing partitions, still didn't work. All flashings were done without any error reported. Any ideas what might be wrong? Bootloader and Recovery are fine, It boots without problems on KitKat. But I was using Lolipop without any problems for a few months now. Suggestions?
This is a strange issue. I did not found any solutions for that. What I have in mind is that backing up modemst1, modemst2, persist and misc partition then erase the whole emmc with boarddiag tool. This is a bit risky because if this error caused by a faulty emmc we may cannot reflash the bootloader after the emmc is erased because it will fail on some I/O error.
I rooted my phone by unlocking my bootloader, putting philz touch recovery, and flashing superSU.zip. After using my phone with root for a while, i noticed that some things were really unstable and buggy, such as it wouldn't charge, so i decided that i might as well flash cyanogenmod 12 since i have a recovery. This was my first mistake, as flashing cyanogenmod put my phone into an infinite boot animation screen. I then used adb to sideload the official Motorola 5.1 update. But this also gave me an infinite bootloop. I tried flashing cyanogenmod 12.1, that also didnt work. I tried flashing stock android 5.1, also bootlooping. I did some searching and i found that my bootloader was not recent enough to flash lollipop roms. So i tried again after updating my bootloader, and now its even worse. It doesn't even attempt to start up, it just goes straight into recovery mode as soon as i boot it up. It also has this strange screen flickering/glitching going on, like this. I don't even know where to go from here so any help would be greatly appreciated.
Some extra info:
I did clear all cache before flashing.
Model number is XT1032
Bootloader version is 4118, before it was 4113.
I recommend flashing a stock 4.4.4 ROM to your phone using fastboot commands. Do no flash anything older than 4.4.4.
Flash cm11 first. I had the stuck at bootanimation. On cm 12.1 flashed 11 then wiped and flashed 12.1 and all is Good