CM 13 stuck at Reboot animation. Help please! - One (M8) Q&A, Help & Troubleshooting

It's been stuck at this loading screen for hours. Are there any ways out of this? I cant power off nor can I connect it to my PC. It always rebooted perfectly until I flashed the 5.0 version of ElementalX. Then this happened. Hope to hear some input asap as I'm trying my best not to panic. No other kernels are on here except for micro gapp and CM 13. I would remove the battery pack, but might as well get a new phone at that point. I would post a picture but I'm a new user so I'm restricted. Thanks!

legitbeans said:
It's been stuck at this loading screen for hours. Are there any ways out of this? I cant power off nor can I connect it to my PC.
would remove the battery pack, but might as well get a new phone at that point.
Click to expand...
Click to collapse
No need to do a battery pull on this phone, as you know is not really feasible. HTC has already thought that out, and built-in a hardwired button combo that does the same thing. Hold power button+ vol up until the phone reboots (may take a minute or so in the current condition). The moment the screen goes dark to reboot, slide your finger from vol up, to vol down (no need to keep holding power button at this point) and don't let go until the bootloader screen appears. From there, you can boot recovery, connect fastboot, etc.
If the button sequence above fails, its virtually always due to getting the timing wrong, either not pressing vol down soon enough, or letting go too early. Either of which, will result in trying to boot normally (not bootloader) which in your case puts you back stuck on the loading screen. Just repeat until you get it right.
Although, at this point, your battery may have just run out. In which case, you should be able to charge, and just hold power+vol down to boot directly into bootloader.
legitbeans said:
It always rebooted perfectly until I flashed the 5.0 version of ElementalX.
Click to expand...
Click to collapse
Here was your mistake. ElementalX is only for Sense and GPE ROMs, it doesn't work on AOSP ROMs like CM13.
Once you get booted into recovery, you should be able to dirty flash CM13 to re-install the CM kernel, then reboot. Or at the worst, wipe, flash CM13 and gapps again.

Related

Can't get past CM boot screen.

So tonight I rooted my phone and decided to download CyanogenMod to it. I created a backup of my phones current install, wiped/reformatted, and installed the latest stable release of CyanogenMod from their website (version 10.2.0). I followed the instructions on CyanogenMod's website for installing from recovery since Heimdall isn't supporting right now. Everything went great, said my radio was recent enough, installed with no issues. I go to reboot and I just got the spinning arrow for ages, won't load. Any ideas? Thanks in advance.
Grrr.. and now, when I try to restore my backup, my phone won't boot. It either crashes on the boot screen and turns off, or I get stuck in a "boot loop" where it just reboots over and over and over but never gets past the splash screen. Ideas?
IntoxicatingToxin said:
Grrr.. and now, when I try to restore my backup, my phone won't boot. It either crashes on the boot screen and turns off, or I get stuck in a "boot loop" where it just reboots over and over and over but never gets past the splash screen. Ideas?
Click to expand...
Click to collapse
I and a bunch people are going through the same. We're waiting for someone who comes up with a solution.
tpag02 said:
I and a bunch people are going through the same. We're waiting for someone who comes up with a solution.
Click to expand...
Click to collapse
Well, it's good to know I'm not alone I suppose, but this is frustrating - I don't have a backup phone. :/ Going through an alternate method to try and restore my phone to stock settings - stock is way better than no phone. Lol.
If it vibrates and restarts over and over until you remove the battery. It's a bad power button. I had it happen to me. I unsoldered the button off for now. It stays on now i have a touch recovery and use volume to wake and a tile to sleep.
xj0nx said:
If it vibrates and restarts over and over until you remove the battery. It's a bad power button. I had it happen to me. I unsoldered the button off for now. It stays on now i have a touch recovery and use volume to wake and a tile to sleep.
Click to expand...
Click to collapse
It's only a bad power button when I try to flash CyanogenMod, then. I found a way to revert back to stock and my phone is fine.
IntoxicatingToxin said:
It's only a bad power button when I try to flash CyanogenMod, then. I found a way to revert back to stock and my phone is fine.
Click to expand...
Click to collapse
That makes no sense. It definitely isn't a bad power button because it works just fine with stock.

[Q] S3 (I747) Powering off During Boot

Started two days ago. Phone would randomly power off and boot back up. Finally it shut off and would not power back on. I had Cm11 installed with CWM 4.0.4.6. The phone powers on after inserting the battery. The Samsung logo flashes and then it shows the "Galaxy S3" logo with the CM logo below it. The phone the powers off. I have done a factory reset, cleared both caches, formatted the system folder, flashed SlimKat from recovery and tried another known good battery. At this point I figured I would reflash CWM but if I put the phone into download mode, it powers off after just a few seconds as well.
If I boot the phone into CWM, the phone stays on as long as I want it to so it makes me think this might be fixable. Just need some help.
Except for recovery working, it sounds like the power button sticking. If you remove/replace the battery does it power on automatically? If so its definitely the power button.
Otherwise, let us know what firmware you are currently running on. Maybe reflashing in recovery could help.
DocHoliday77 said:
Except for recovery working, it sounds like the power button sticking. If you remove/replace the battery does it power on automatically? If so its definitely the power button.
Otherwise, let us know what firmware you are currently running on. Maybe reflashing in recovery could help.
Click to expand...
Click to collapse
It does power on automatically. Makes perfect sense that it is the power button. Is this repairable or replaceable? I start Googling around for power button issues.
Im currently running CWM 6.0.4.6 and SlimKat. SlimKat was only installed cause I thought CM 11 was the issue. At this point I would just like to get the phone to a point where I could sell it.
kylelever said:
It does power on automatically. Makes perfect sense that it is the power button. Is this repairable or replaceable? I start Googling around for power button issues.
Im currently running CWM 6.0.4.6 and SlimKat. SlimKat was only installed cause I thought CM 11 was the issue. At this point I would just like to get the phone to a point where I could sell it.
Click to expand...
Click to collapse
It can be replaced fairly easily, just look it up on youtube.
You can buy the part off Ebay (or any other site you might prefer) for fairly cheap.

[Q] Bricked Samsung Galaxy Nexus I9250

i seem to have hard bricked the device and i have been attempting to find a way i can fix it for hours.. i seem to be stuck. Its stuck on the boot animation cyanogenMod logo. I am unable to get into the recovery mode, as well as fast boot mode. i let it sit on that boot logo for hours without anything at all happening. No progress what so ever. Now the biggest thing i am trying to figure out is how i even managed to get this to happen. there was a software update notification that i received, so i figured it may have been the Android L update or something, so without taking into considering what exactly i was agreeing to i accepted, and continued. Let it reboot, and thats how i got to come across this issue. Any suggestions.
So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.
efrant said:
So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.
Click to expand...
Click to collapse
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.
Jewelzxo said:
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.
Click to expand...
Click to collapse
What I find strange is that it boots to the boot animation -- that means the bootloader has loaded up the kernel and Android is attempting to start. The bootloader loads up before anything, so it is obviously working. Don't know why you can't access its menu though with the 3-key press. Maybe one of your volumes keys is not working properly? By holding those three keys down, it should not boot to the boot animation...
Can you get into download mode? Hold only volume down and press and hold power. If so, then you can use Odin and flash a stock ROM as per this thread.
In any case, if you can't get into the bootloader or download mode, then your only option is using OMAPFlash (as per this thread). That will re-flash your bootloader. If you still can't get into the bootloader menu after that, then there is a hardware issue.

No ROM, can't access bootloader, stuck in bootloop

Hey guys,
Ok, this is a tough one for you. I'm actually not 100% convinced that my phone isn't hard bricked. But every where I look for, it says, it's only hard bricked if your phone wont turn on at all and that's just not true in my case. So here's the story:
My volume-up button is kind of screwed, I don't know, what happened to it, but one day, it just started being triggered randomly until it just didn't work at all anymore. It wasn't that big of a problem, since I was still able to change the volume by hitting the volume-down button once and changing the volume by the on screen slider. I was running SkyDragon GPE V5.5 for quite a while now.
But now I wanted to upgrade to Android 6.0, so I downloaded the firmware from here. Next I rebooted to bootloader switched to fastboot and used "sudo fastboot oem rebootRUU" and "sudo fastboot flash zip firmware.zip" twice. So far so good, everything went fine and I actually even am able to see the new Google splashscreen.
So now I want to flash this ROM. But, for some reason, the touchscreen doesn't work anymore, even though it's activated in the CWM Philz Touch GUI settings enabled. Alright, so I "wipe to install a new ROM" and navigate to the zip file to install it and it starts the aroma installer, which I can't control since the touchscreen doesn't work. So, I'm kind of frustrated by now, I flash TWRP, because, maybe here, the touchscreen works. I flash it and try to reboot into it. But it doesn't work, it just stays at the Google splashscreen, I can restart by holding down the power button but it will just go back to the Google splashscreen. After a couple of tries I actually get it to turn off, so I hold down power and volume down to get into the bootloader but it just goes back to the splashscreen.
I can't get to the bootloader, I don't have a ROM installed and I can't get into the recovery. Is there anything I can still do or is everything lost?
Which TWRP version ? You need to use 2.8.7.0
You can't get to bootloader because of the timing when pressing power & volume down button.
If you can turn it off, press and hold volume down button then press power button until it vibrates then release the power button.

Probably hard bricked - not sure

Hi,
after running a rooted Kitkat for a year or so I thought I wanted to install CM12.1. So I wiped and flashed via CWM Recovery and also flashed some GApps (probably the wrong one). After flashing (with confirmation that everything was successful), I wanted to reboot but after clicking on reboot, the screen just went black. Waiting for 5 mins, nothing changed.
Pushing the Power-On button lets the phone vibrate once, that's it. Pushing Vol+ or Vol- together with Power-On does not change anything. Connecting a charger to the phone, let the red LED flash once.
What can I do to revive my phone....?
Suggestions or hints are greatly appreciated
aalemann said:
Hi,
after running a rooted Kitkat for a year or so I thought I wanted to install CM12.1. So I wiped and flashed via CWM Recovery and also flashed some GApps (probably the wrong one). After flashing (with confirmation that everything was successful), I wanted to reboot but after clicking on reboot, the screen just went black. Waiting for 5 mins, nothing changed.
Pushing the Power-On button lets the phone vibrate once, that's it. Pushing Vol+ or Vol- together with Power-On does not change anything. Connecting a charger to the phone, let the red LED flash once.
What can I do to revive my phone....?
Suggestions or hints are greatly appreciated
Click to expand...
Click to collapse
Try holding power and volume up together for 8-10 seconds, just to make Sir it's totally powered off, then connect the charger and see if it starts charging. Older batteries don't do well in this phone. It wseems to me you might have had the sudden-battety-drain phenomenon when you flashed.
levone1 said:
Try holding power and volume up together for 8-10 seconds, just to make Sir it's totally powered off, then connect the charger and see if it starts charging. Older batteries don't do well in this phone. It wseems to me you might have had the sudden-battety-drain phenomenon when you flashed.
Click to expand...
Click to collapse
Thanks, that seemed to have work. I am now a happy user of CM12.1 on my Xperia Z1 Compact

Categories

Resources