I've had this problem since I first flashed the 10.1 nightlies months ago, and I was curious if anyone else has noted this problem.
When I turn off or reboot my phone, more often than not the Samsung Galaxy S4 logo screen just hangs there, without booting into the OS. I often have to reboot my phone 4 or 5 times to get CM to boot. This has been happening more and more frequently too.
Does anyone else have this issue?
Which recovery/version are you using to wipe/flash?
According to Cyanogenmod this is already a known issue. Check their Original Cyanogenmod thread and post #2.
Just found out myself.
xBeerdroiDx said:
Which recovery/version are you using to wipe/flash?
Click to expand...
Click to collapse
I'm going to take a wild stab in the dark and say TWRP. I've never had an issue with any other recovery after formatting data.
Sent from my GT-I9505G using xda app-developers app
Most likely it's a problem with TWRP.
Just wondering, how would someone with TWRP flash to CWM? Would they have to use odin to flash to stock, root and then download clockworkmod to flash? Or can I just flash CWM over TWRP?
Im running slim bean with twrp 2.5.0.2 and experience this problem.
When stuck on Samsung screen boot into recovery. When in twrp recovery use the option in the lower right to boot into recovery again. Then use that same option to boot system.
Sent from my SGH-I337 using xda app-developers app
Use CWM instead of TWRP. I was using TWRP and had this issue 1 out of 3 reboots. I haven't had the Samsung logo hang since I flashed CWM.
Related
Just recovered from an issue using cwm recovery on a HTC Rezound. While it was fun to resolve, fear of turning it into a paperweight was not the best feeling.
Will there be similar issues with cwm recovery on the N7? Should one stay away from a ROM that requires cwm recovery?
I've had no problems with cwm on the Nexus 7. What kind of problems did you have?
*Sent from Nexus S*
I have flashed, probably, ten times on my N7.....All using CWM with absolutely no problems.
The official cwm 6.0.1.0 is still rock solid touch recovery. No problem since I had it. I'm constantly using it for the cm10 nightlies and custom kernels.
Tapatalked from my Ace 2
I did have one instance where CWM recovery couldnt see the storage and i could not flash anything after formatting. I had a backup on the PC though and was able to bring it back manually.. its always a good idea to be careful!
Sent from my Google Nexus 7 using xda app-developers app
I tried to format the system folder while installing cyanogenmod nightlie and it froze. took battery out and rebooted and got back into download mode and cwm - resintalled it - all ok, but just stuck of the cyanogenmod boot screen.
Tried ot flash a stock rom, all goes through ok, but is stuck of the samsung boot screen
Help?
I can get into the cwm and download and odin connects ok
That isn't even a soft brick, just a bad flash. Go into recovery and try to flash CM again. If it doesn't work restore your stock backup (I assume you made a backup).
Sent from my GT-I9505 using xda app-developers app
u need to wipe data
Sorted - thanks for both replies - wiping the data has done it - I thought i had already tried that and was still stuck.
It will never be bricked until you cannot access to recovery
Never worry about bricking. It's not a rare occasion. You'll be able to go through the recovery & reboot in your sleep lol.
Sent from my SPH-L720 using Tapatalk 2
Hey all,
Just rooted my Galaxy S4 yesterday on AT&T. Rooted it using tLoki + TWRP + Motochopper CASUAL method. I have TWRP recovery installed and can get to that no problem. I have the following build of Cyanogen flashed:
cm_jflteatt-userdebug 4.3 JLS36G f65925b07a test-keys
CyanogenMod version:
10.2-2013007-NIGHTLY-jflteatt
Baseband: I337UCUAMDL
Phone works flawlessly after the flash, but as soon as I power off or reboot, it just hangs at the Samsung Galaxy S4 screen and doesn't do anything. Only way out is to boot into recovery wipe and re-flash the Cyanogen ROM.
Any thoughts? I don't even know where to start...
a.stalker22 said:
Hey all,
Just rooted my Galaxy S4 yesterday on AT&T. Rooted it using tLoki + TWRP + Motochopper CASUAL method. I have TWRP recovery installed and can get to that no problem. I have the following build of Cyanogen flashed:
cm_jflteatt-userdebug 4.3 JLS36G f65925b07a test-keys
CyanogenMod version:
10.2-2013007-NIGHTLY-jflteatt
Baseband: I337UCUAMDL
Phone works flawlessly after the flash, but as soon as I power off or reboot, it just hangs at the Samsung Galaxy S4 screen and doesn't do anything. Only way out is to boot into recovery wipe and re-flash the Cyanogen ROM.
Any thoughts? I don't even know where to start...
Click to expand...
Click to collapse
Use twrp 2.5.0.2. I'm guessing you're using 2.6
jd1639 said:
Use twrp 2.5.0.2. I'm guessing you're using 2.6
Click to expand...
Click to collapse
No, I am using 2.5.0.2 just verified.
a.stalker22 said:
No, I am using 2.5.0.2 just verified.
Click to expand...
Click to collapse
This has been an issue on other devices. Flashing with cwm seems to have consistently worked. Once you get it up and running you can flash back to twrp for your nandroids. I've had to do this on my i727.
jd1639 said:
This has been an issue on other devices. Flashing with cwm seems to have consistently worked. Once you get it up and running you can flash back to twrp for your nandroids. I've had to do this on my i727.
Click to expand...
Click to collapse
Thought maybe it was a ROM problem, but any I've tried have this same problem.
How do I go about replacing twrp with cwm? I have no idea how to replace the recovery. Any direction would be much appreciated :good:
a.stalker22 said:
Thought maybe it was a ROM problem, but any I've tried have this same problem.
How do I go about replacing twrp with cwm? I have no idea how to replace the recovery. Any direction would be much appreciated :good:
Click to expand...
Click to collapse
This is already a known issue for Cyanogenmod 10.1 and 10.2. Using CWM will help it a little bit, but will still occur. There is no fix.
emckai said:
This is already a known issue for Cyanogenmod 10.1 and 10.2. Using CWM will help it a little bit, but will still occur. There is no fix.
Click to expand...
Click to collapse
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?
a.stalker22 said:
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?
Click to expand...
Click to collapse
Get a cwm zip file and flash it like you would a rom but don't do any wipes. It'll flash on top of twrp and replace it. Do the same thing to go back to twrp.
a.stalker22 said:
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?
Click to expand...
Click to collapse
Just download ROM Manager and flash CWM.
Which ROMs have you tried so far? Are they based off of CM?
Try to clear the delvik cache and the cache. I believe it will boot normal then
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
emckai said:
Just download ROM Manager and flash CWM.
Which ROMs have you tried so far? Are they based off of CM?
Click to expand...
Click to collapse
No, they're not all based off of CWM.
The last few I tried were BeanStalk and Task650 AOKP. The Task650AOKP booted up fine the first time, I did a reboot and then it was permanently stuck at the Samsung Galaxy S4 screen, even after I cleared cache's and factory reset with a re-flash. I tried that several times and still couldn'y get back in, so luckily I had a backup of my original rooted config and that booted up.
I did install rom manger just now and flashed cwm recovery...just afraid to reboot..haha. I wish I knew what the problem could be here...
I have TWRP recovery, and stock rom.
Thing is, I sold to phone to a guy, he tried to install the update and now the phone reboots to recovery. I told him to restore the backup, he did so, but he says it still reboots to recovery everytime he tries. He doesn't boot to bootloader or recovery, but presses power off and then manually turn the phone on - still to recovery. I can't really help him because I can't see what's the problem.
What should we do?
If you have custom recovery you shouldn't take ota search for g2 ota twrp and you will find some helpful threads
Sent from my LG-D800 running kitkat using XDA Premium 4 mobile app
XxZombiePikachu said:
If you have custom recovery you shouldn't take ota search for g2 ota twrp and you will find some helpful threads
Sent from my LG-D800 running kitkat using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok but my question is why when I restore it still boots to recovery? If I restored it then it should reboot regularly.
I was running (and am after the restore) Android 4.3.1 slimBean jflteatt build.2official.
So my friend convinced me to try CM12 lolipop nightly.
I made a backup wiped everything and installed CM12 and the gapps.
upon boot after the instalation all the play services were crashing so we reinstalled CM 12 but without GAPPS and all was fine.
BUT now i CAN"T reboot my phone. Regardless of ROM (except stock) the att galaxy s4 gets stuck on the boot splash screen (the screen before the boot screen) The screen it gets stuck on looks like this: http://img18.imageshack.us/img18/8910/20120813002112.jpg
The screen used to look like this: http://2.bp.blogspot.com/-aCD7kATq-to/UaIBfYW5oKI/AAAAAAAAO88/ShlHR6459kk/s1600/boots4.gif
I have tried restoring and installing a clean ROM but that did not solve my problem. Only way for me to restore is to wipe everything, then format the data and the restore. I restored to stock TW MDL via a TWRP backup i have.
I am running TWRP 2.5.0.1 (I think). I am currently using the SlimRoms 3.4.0 kernal. I am rooted according to root checker.
Can someone please help me solve the reboot problem? (Could it have anything to do with Xposed?)
I would update twrp and try again. You have an old version.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I would update twrp and try again. You have an old version.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
i have 2.5.0.2, what do you suggest i update to ? (and how?)
I've been afraid to update anything because if it aint broke don't fix it.
Do you suggest TWRP 2.8.0.1 touch recovery [2014-09-12]
as this suggests?: http://forum.xda-developers.com/showthread.php?t=2413746
thank you for your reply.
sharpknight said:
i have 2.5.0.2, what do you suggest i update to ? (and how?)
I've been afraid to update anything because if it aint broke don't fix it.
Do you suggest TWRP 2.8.0.1 touch recovery [2014-09-12]
as this suggests?: http://forum.xda-developers.com/showthread.php?t=2413746
thank you for your reply.
Click to expand...
Click to collapse
Flashing roms in an old version of twrp won't work. If your rooted, which I assume you are, get flashify forum the play store. Then download the latest twrp.img and flash it in flashify. http://dl.twrp.me/jflteatt/ The link is for the at&t s4, if you have a different variant you'll need a different image.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Flashing roms in an old version of twrp won't work. If your rooted, which I assume you are, get flashify forum the play store. Then download the latest twrp.img and flash it in flashify. http://dl.twrp.me/jflteatt/ The link is for the at&t s4, if you have a different variant you'll need a different image.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
ok i have succesfully updated to TWRP 2.8.4.0 (newest on the link you provided) via flashify as you suggested.
What do i do now? BTW really appreciate the help.
sharpknight said:
ok i have succesfully updated to TWRP 2.8.4.0 (newest on the link you provided) via flashify as you suggested.
What do i do now? BTW really appreciate the help.
Click to expand...
Click to collapse
If you want cm12 download the zip and gapps and flash those in twrp. Do the default wipe in twrp first. Note, it will wipe your apps but if you have had Google backup your device it will restore them.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If you want cm12 download the zip and gapps and flash those in twrp. Do the default wipe in twrp first. Note, it will wipe your apps but if you have had Google backup your device it will restore them.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I don't wan't CM12 at this moment. I just need to have old SlimRom working without the reboot issue. too much business related data there at the moment. So should i reinstall slimRom and the restore that data maybe?
Could it be the slimKernal? Ive had the problem where it gets stuck at that screen for a long time now but id just do a batery pull and turn it on and it would work after 2-3 tries.