Almost every time when i reboot my phone, it's hangs at Google logo and the keeps rebooting.
Do i have to change / update the bootloader ?
The bootloader is primelc03
Thank you
Not 100% sure it's the same but I had a reboot issue when using TWRP recovery, flashing Clockworkmod recovery fixed it.
Same thing here, except it also tends to happen when shutting down. It's not a huge deal as long as I remember to check and shut down from the bootloader if this happens, but it would be nice if we could find a proper fix.
I'm running:
LiquidSmooth 7/3 Nightly
DirtyV kernel
CWM Recovery
Related
I am currently running Domination CM10 build 6 and was previously using the kernel that came with the rom.
Just updated to latest bricked which first just wouldnt boot (flashed kernel via fastboot and zip via recovery as normal) either normally or load recovery so used viper flasher to do kernel and modules (replaced ones it came with to latest ones from the kernel zip)
Now phone boots fine but after a few seconds it comes up "Failed to Load! " in a box at bottom (similar to boxes when something is given root access, checked and phone still rooted and that side working fine) but the box never seems to fade away so stays stuck over top of everything.
I only have 2 widgets... clock & calendar both of which load up fine, boots into recovery now if I boot normal and then use rom "reboot into recovery" but whenever I try to use it the phone just reboots, if I hold volume down when powering on it just boots as normal and dont load hboot
Any ideas? Know its not major issues and can probably be fixed with a wipe but tbh was lazy and didnt backup before flashing kernel thinking I wouldnt need it so hoping someones had similar and knows a simpler fix which wont involve wiping
ViaraiX said:
I am currently running Domination CM10 build 6 and was previously using the kernel that came with the rom.
Just updated to latest bricked which first just wouldnt boot (flashed kernel via fastboot and zip via recovery as normal) either normally or load recovery so used viper flasher to do kernel and modules (replaced ones it came with to latest ones from the kernel zip)
Now phone boots fine but after a few seconds it comes up "Failed to Load! " in a box at bottom (similar to boxes when something is given root access, checked and phone still rooted and that side working fine) but the box never seems to fade away so stays stuck over top of everything.
I only have 2 widgets... clock & calendar both of which load up fine, boots into recovery now if I boot normal and then use rom "reboot into recovery" but whenever I try to use it the phone just reboots, if I hold volume down when powering on it just boots as normal and dont load hboot
Any ideas? Know its not major issues and can probably be fixed with a wipe but tbh was lazy and didnt backup before flashing kernel thinking I wouldnt need it so hoping someones had similar and knows a simpler fix which wont involve wiping
Click to expand...
Click to collapse
try to reflash stock kernel, maybe it will be ok again, in worst case you'll have to wipe
Thought I would post here in effort to get faster responses.
Hi all, I was on AKOP's milestone ROM before trying to flash their newest one. I did not do anything to the kernel or anything by the way.
I'm using ClockworkMod Recovery v6.0.2.7 and I rebooted into recovery and flashed super dark side wipe and then JB-MR1 and then gapps.
I went through the entire start up process with inputting your information and then finally I got into the actual home screen. I clicked around to see how the UI looked and then decided to reboot through the menu.
It was in the rebooting animation icon for at least 30 min before I decided to pull the battery. I want to wipe and start again but my cwm recovery isn't installing anything.
The phone still works as I can boot into the phone and use it. I'm trying to reboot now: power button hold>reboot, but its taking ages. Pretty much phone is "functional" but any method of trying to reboot or reboot into recovery fails
Thanks all!
I was able to get my VS HTC One S-Off with Firewater, thankfully.
As I was trying to load Cyanogenmod, the Wipe Cache process seemed to take way too long >30minutes. I powered down and rebooted, and then loaded the cyanogenmod stable RC zip. The phone is now permanently stuck in the cyanogenmod boot loop, with the blue arrow going in a circle.
I can't even get it to power down successfully...but sometimes it will turn off and then go back into the same loop. I have gotten it to fastboot once, but I tried to wipe all the caches/partitions again, and reboot...and same loop.
Any help please?
=============
More info:
I was able to get into CWM v6.0.4.7 recovery. I'm was able to sideload the STABLE CM 10.2 for verizon htc one...and it seems to have installed. But I'm still going into a boot loop. The loop is different for the stable version than it was for the release candidate...just a different CM logo and circle. So that's how I know the CM 10.2 stable loaded effectively. It rebooted on it's own one time after 10 mintues of looping, but still stuck.
payrovi2 said:
I was able to get my VS HTC One S-Off with Firewater, thankfully.
As I was trying to load Cyanogenmod, the Wipe Cache process seemed to take way too long >30minutes. I powered down and rebooted, and then loaded the cyanogenmod stable RC zip. The phone is now permanently stuck in the cyanogenmod boot loop, with the blue arrow going in a circle.
I can't even get it to power down successfully...but sometimes it will turn off and then go back into the same loop. I have gotten it to fastboot once, but I tried to wipe all the caches/partitions again, and reboot...and same loop.
Any help please?
=============
More info:
I was able to get into CWM v6.0.4.7 recovery. I'm was able to sideload the STABLE CM 10.2 for verizon htc one...and it seems to have installed. But I'm still going into a boot loop. The loop is different for the stable version than it was for the release candidate...just a different CM logo and circle. So that's how I know the CM 10.2 stable loaded effectively. It rebooted on it's own one time after 10 mintues of looping, but still stuck.
Click to expand...
Click to collapse
It's the recovery, I'm 99% sure of it. I had the same issues that you described and resolved it by flashing CWM 6.0.4.4.
You should be able to find it somewhere on the forum but if not I have a copy on my FTP here: http://www.radracer.us/otp/droid/recovery-clockwork-6.0.4.4-m7vzw_2.zip
Once you flash the new recovery do a data/cache wipe as you usually would and then try loading CM once more. The data/cache wipe should be almost instant.(<60seconds)
vpxf said:
It's the recovery, I'm 99% sure of it. I had the same issues that you described and resolved it by flashing CWM 6.0.4.4.
You should be able to find it somewhere on the forum but if not I have a copy on my FTP here: http://www.radracer.us/otp/droid/recovery-clockwork-6.0.4.4-m7vzw_2.zip
Once you flash the new recovery do a data/cache wipe as you usually would and then try loading CM once more. The data/cache wipe should be almost instant.(<60seconds)
Click to expand...
Click to collapse
After trying a few other roms unsuccessfully, I read somewhere about a CM11 Nightly that was very stable. I wiped everything 3 times, sideloaded it, and voila...it's working fine right now.
Thanks for all the help...I'm finally on Cyanogenmod...which has been evading my phone of choice for so many years!
I've had a CM11 Official Nightly installed on my phone for a couple weeks, and just today my phone started turning off, and when I try to turn it back on it just shows the Samsung logo for a few seconds, then flashes the CM11 logo, then the screen goes black. It does fully boot up when I pull the battery for a few minutes then turn it on again, but it only lasts for a couple minutes before shutting off again. It does the same thing when I try to boot into recovery (TWRP), it shows the Samsung logo with the boot recovery text, then shows the TWRP screen for a second, then shuts off again. Rarely it will boot into recovery. Any idea what the problem is or how to fix it?
I would try installing the latest version of Philz Touch for the d2lte to see if you can get into recovery and stay in recovery. I used to have twrp on my phone but it gave me problems when flashing ROMs.
Thanks, installed Philz Touch recovery via Odin, and got it to boot into recovery and installed CM11 and it seems to be working so far.
Good news. For future reference, I would load the Samsung Phone Info app from the playstore to confirm the bootloader and modem on your phone as some ROMs may require the latest bootloader and modem to function properly.
CyanogenMod version: 11.0-InstallerXNPQ09Q
Hello, I just installed CM on my S3 via the one-click install. Now I have problems powering off or rebooting my phone. I select "Reboot" from the power menu, and click OK. Then it hangs displaying the "Reboot phone" window, displaying the busy animation and saying "Rebooting...". Power off does much the same thing. Is there any solution to my problem? I have to take the battery out to shut the phone down. Once turned off, it starts up just fine.
Sometimes, though, the phone restarts properly. I don't know what would make the difference.
I recommend flashing a custom recovery and flashing cm11 from recovery after doing a full wipe.
audit13 said:
I recommend flashing a custom recovery and flashing cm11 from recovery after doing a full wipe.
Click to expand...
Click to collapse
That's what I ended up doing. I've been running it now several days and everything is working fine. I should have done that in the first place, oh well. The installer sure didn't leave a good impression on me, but now that I have successfully installed CM and it is working, I love it!