I have run clockworkmod alongside CM11 for some time but i decided to install the touch version of CWM from Rom Manager. After the install I hit the restart into recovery button but every time the phone attempts to start it gets no further than the recovery booting screen, crashes and the phone restarts only to do it again. I cannot break this loop. All I want to do is get back to CM. Any suggestions?
sam.hinsley said:
I have run clockworkmod alongside CM11 for some time but i decided to install the touch version of CWM from Rom Manager. After the install I hit the restart into recovery button but every time the phone attempts to start it gets no further than the recovery booting screen, crashes and the phone restarts only to do it again. I cannot break this loop. All I want to do is get back to CM. Any suggestions?
Click to expand...
Click to collapse
Reflash your recovery. It'll fix whatever happened.
radicalisto said:
Reflash your recovery. It'll fix whatever happened.
Click to expand...
Click to collapse
Thanks. Managed to get into download mode and flashed a new recovery using odin
Related
I got my S3 today, and of course set out to root it immediately. Everything went fine until I went to install google apps. I inadvertantly chose the wrong zip and installed the ones for my Skyrocket. Now it boots fine, but is stuck in an error notification loop where it says gapps has closed and setup has failed. If I could get back to the recovery panel, I'd know exactly what to do, but I can't get there with this phone for some reason. When I reboot with down volume, it boots into "safe" mode, but still gets stuck in the loop. If I reboot with down volume and home, I go to the Downloading screen. Could someone please help me get back to the recovery panel???:silly:
workingmomjd said:
I got my S3 today, and of course set out to root it immediately. Everything went fine until I went to install google apps. I inadvertantly chose the wrong zip and installed the ones for my Skyrocket. Now it boots fine, but is stuck in an error notification loop where it says gapps has closed and setup has failed. If I could get back to the recovery panel, I'd know exactly what to do, but I can't get there with this phone for some reason. When I reboot with down volume, it boots into "safe" mode, but still gets stuck in the loop. If I reboot with down volume and home, I go to the Downloading screen. Could someone please help me get back to the recovery panel???:silly:
Click to expand...
Click to collapse
So close, Volume up home and power, and it should get to to recovery.
If you can't boot into recovery, but you can boot into download mode just flash a stock ROM through Odin then flash the correct version of gapps sand you should be good
m0cha5hake said:
If you can't boot into recovery, but you can boot into download mode just flash a stock ROM through Odin then flash the correct version of gapps sand you should be good
Click to expand...
Click to collapse
I can now get into recovery (thank you!) but it's a hobbled recovery, not the touch recovery I installed when I originally rooted. It only gives me four options, including install zip from external sd. When I try to install CM or gapps I get a failed to get permission message and the installation aborts. Unfortunately, fix permissions is not one of the four options I'm presented with
So now I'm trying to flash clockwork mod touch from odin, but it hangs at the Samsung Galaxy boot screen when it goes to reboot. Any ideas out there?
workingmomjd said:
I can now get into recovery (thank you!) but it's a hobbled recovery, not the touch recovery I installed when I originally rooted. It only gives me four options, including install zip from external sd. When I try to install CM or gapps I get a failed to get permission message and the installation aborts. Unfortunately, fix permissions is not one of the four options I'm presented with
So now I'm trying to flash clockwork mod touch from odin, but it hangs at the Samsung Galaxy boot screen when it goes to reboot. Any ideas out there?
Click to expand...
Click to collapse
I managed to flash a new cwm via odin and got into my familiar cwm. From there I was able to reinstall cm10 and gapps (the right one this time!) and it no longer hangs at the samsung galaxy boot screen, and is FIXED. Thank you so much for your help!!
My phone originally was using omega rom and philz recovery. I accidentally pressed the "remove recovery flash" while in philz recovery when I was trying to reboot the phone. My phone couldn't boot to os nor recovery, but download mode still works. So I tried to flash custom recovery again but it does not work. Tried flashing stock rom and kernel but recovery does not work. However, the phone is now able to boot to os but the screen color gone wrong. The whole screen is purple-ish when in os.
How can I get back recovery and also solve the purple problem?
Maybe try using a different recovery, at least to get back to stable? I've used TWRP and OUDHS via Odin, and both work well.
jejb said:
Maybe try using a different recovery, at least to get back to stable? I've used TWRP and OUDHS via Odin, and both work well.
Click to expand...
Click to collapse
Thanks alot! Finally able to enter recovery. Spent quite a long time trying to flash different roms etc.
Now trying to solve the purple problem....
Edit: Everything working fine now.
I had Mint Jelly2.1 installed and everything was working fine.
it started when I had used the APK Hide It Pro. I was in the process of hiding videos and I noticed that my phone got rebooted and got stock in the Samsung boot up image with the Custom Lock image.
I tried nandroid restore, 2 images, but both also failed to restore / bootup.
I tried re-installing ROM and it was successful but during reboot, it will still get stock on the boot image.
Last step.
I used ODIN to restore the stock ROM and ODIN was able to install and reset. And my phone rebooted but still got stock on the Samsung Logo with CUstom Lock Screen.
What else can I do to fix this?
Thank you.
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
I had tried to restore/flash from recovery before ODIN and it all Failed.
Anyway, the last step ODIN restore and it was still stock at the Samsung Logo with Lock image.
I left the phone to charge the whole night and this morning when I turned it on, it was able to start properly with ODIN stock ROM.
I tried to go to recovery, and can only be done manually, and it was not the TWRP recovery but the stock one, with very small characters.
I tried to install Mint Jell2.1 right away but just reboots.
I realized that I might need to root it again and downloaded the Tool and re-loki'ed/rooted and installed TWRP.
Now, I am able to install Mint Jelly 2.1 and restoring all my apps.
I appreciate the comment.
Thank you.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
CZ Eddie said:
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
Click to expand...
Click to collapse
I can confirm this works happened to me yesterday.
leoj85 said:
I can confirm this works happened to me yesterday.
Click to expand...
Click to collapse
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
I got stuck to 1st boot image of Samsung with Lock Custom Icon.
I did format data/factory reset/clear cache/dalvik.. all of the wipe ootions.
I flashed a new ROM, successful, rebooted pass the logo and booted fine. I did not change any settings yet and I rebooted to check if it will get stuck again and sure after reboot, it got stuck again on the 1st image that shows up : Samsung Logo with the Lock Custom Icon.
qwer43 said:
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
Click to expand...
Click to collapse
IMPORTANTwhen using*twrp*recoverydo not choose "format data"(that option will ask you to type "yes")what if i did?rom will not boot past "padlock" boot screen orrom will not boot on second reboot*help!! I did, I did*1. sigh2. d/l odin3. d/l odin stock restore MDL4. let it do its thang5. after its complete it will be stuck at padlock6. should have "rtfm" huh?*7. pull battery8. hold home button, vol-up, power at same time9. when phone vibrates, release power, while still holdingvol-up, and home button10. you will now be in "stock recovery"11. wipe factory reset then wipe cache12. reboot*13. swear you will never "ignore instructions"
I have TWRP installed and I booted into recovery, backed up my rom and everything was fine. A few minutes later I tried booting into TWRP again but it only rebooted the phone. It shows booting recovery above the Samsung logo then reboots the phone. I used apps like quick boot but yet still reboots the phone
Have you tried turning it off and then booting into recovery with the key combo?
GDReaper said:
Have you tried turning it off and then booting into recovery with the key combo?
Click to expand...
Click to collapse
Yup, reboots back
Try reflashing recovery. Or flash a different version.
NeosHaruki said:
I have TWRP installed and I booted into recovery, backed up my rom and everything was fine. A few minutes later I tried booting into TWRP again but it only rebooted the phone. It shows booting recovery above the Samsung logo then reboots the phone. I used apps like quick boot but yet still reboots the phone
Click to expand...
Click to collapse
Did you root it at first ? If not do so ,i also had that issue and was solved by rooting,normally root is not required for Flashing TWRP but still...
The same problem... I think the rom issue
Flash the latest stock ROM and try to enter recovery.
Hi,
I have Samsung Galaxy S4 I9500.
I installed Cyanogen latest nightly build. Cyanogen worked perfect. I reset to factory settings from Cyanogen's settings. But after that:
- I can not open the phone's recovery (volumeup + home +power)
- I can not start operating system.
On both theese actions "Samsung" logo appears for 3 seconds, but after nothing is happening. Black screen stucks.
I look from eclipse logcat's, there is no log from phone. because OS did not started.
I tried to re-install clockwork (exatly with same files), but did not changed anything. I am not getting errors or even warning.
I will be happy if you can help me.
Thank you
Are you able to get into download mode (volume down, home, power)? If so, flash a stock ROM using Odin. If the S4 works after flashing the stock ROM, install TWRP recovery and then install Cyanogenmod.
P. S. You want to install TWRP as Clockworkmod is no longer being updated.
Hi,
had the problem of not getting into recovery at all randomly. Shutting down the phone, removing the battery and leaving the phone untouched for about half an hour helped me to enter recovery.
Regards
Mr.Brick said:
Hi,
had the problem of not getting into recovery at all randomly. Shutting down the phone, removing the battery and leaving the phone untouched for about half an hour helped me to enter recovery.
Regards
Click to expand...
Click to collapse
Hi,
I try these: I wait for 1 night by putting out the battery, also I restart the phone million times. But nothing changed.
Strephon Alkhalikoi said:
Are you able to get into download mode (volume down, home, power)? If so, flash a stock ROM using Odin. If the S4 works after flashing the stock ROM, install TWRP recovery and then install Cyanogenmod.
P. S. You want to install TWRP as Clockworkmod is no longer being updated.
Click to expand...
Click to collapse
I did not try to install different recovery software. Because Clockworkmod is already worked for the first time.
I will try to install other recovery softwares and I will write the results here.
Thank you
marka_yirmi said:
I did not try to install different recovery software. Because Clockworkmod is already worked for the first time.
I will try to install other recovery softwares and I will write the results here.
Thank you
Click to expand...
Click to collapse
I solve my problem by installing TWRP recovery. I could not understand how Clockworkmod stoped to work itself by doing nothing.
Thank you for your interest.
Clockworkmod is no longer maintained and doesn't recognize some coding in recent updater scripts included with ROMs. That is why it fails while TWRP succeeds.