Clockwork mod blue - Fascinate General

Clockwork mod blue keeps coming up on my phone since I have flashed 2.6. I used Odin to put the new clockwork mod but its still comes up to the blue CWM. Any ideas on how to fix this?

That's the default android recovery. Do you have an update.zip on your sd card? If so, hitting apply update.zip will take you to red recovery.

If its blue that sound more like the stock recovery. what are the options displayed on it?
Sent from my SCH-I500 using XDA Premium App

I have the update zip and when I try to apply it the screen goes blank for a couple seconds and then goes back to blue recovery. There are only 4 options that I can remember

Same thing happened to me a couple days ago..you're going to need to reflash cwm through odin.

i reflashed through ODIN, and got it working, but it resets to blue after one use??

edit: reflash in odin looks to be best bet

Are you sure you got jt's latest cwm in this thread?
And how/which method did you use to get into recovery?

420fan said:
i reflashed through ODIN, and got it working, but it resets to blue after one use??
Click to expand...
Click to collapse
You seem to be using a stock kernel. Stock kernel has a check to see if recovery has been modified. If it finds that recovery was modified, it reflashes stock recovery on next boot.
So solution to that would be. Use a non stock kernel.

Related

Fascinate keeps booting into stock recovery after DL30 flash...

Okay, so I flash the Froyo ROM to my phone and I think I forgot to disable Voodoo... well it was hanging on the SAMSUNG splash and wouldn't ever load, so I tried to restore a previous backup using Clockwork... and now it only boots into stock recovery mode. I tried returning to stock, and now it only boots into stock recovery without even booting into CWM.
What do I do?
edit: Nevermind, I flashed CWM back in... I still can't get my phone out of stock recovery looping...
I've also tried wipe data/factory reset plus cache wipe... went into Odin and flashed the stock files using the PIT/PDA and now it still boots into manual mode... even after restoring CWM and flashing my restores.
At this point, forget about your backups. Especially if they were Voodoo backups. Flash the DJ05 or DL09 Odin stock, get the green CWM update.zip on there and then flash DL30 via CWM.
I'm not sure if I have the DL09 Odin stock... I'll have to get those and give it a try.
DeezNotes said:
At this point, forget about your backups. Especially if they were Voodoo backups. Flash the DJ05 or DL09 Odin stock, get the green CWM update.zip on there and then flash DL30 via CWM.
Click to expand...
Click to collapse
Yeah if you didn't back up with green cwm, probably going to have to get red back eventually, then you'll be able to restore any old back ups
Sent from my Eris using XDA App
Okay, I went to the Odin Restore files thread to get my restore files, so those are the ones I used. I'm not sure where to get the others, so I'll walk you through what I did.
1) Followed tutorial to return to Verizon stock.
2) Reboot phone, does not boot into anything but manual mode.
3) Flash CWM to access CWM.
4) ???
Okay, so new error. I found the stock DL09 Odin files and flashed them. Now my phone endlessly reboots with the "Wipe Data" over and over again. I need my phone working by tomorrow so that I can call my job as there's a blizzard here and I won't be able to get in.
I finally got it. I used Adryn's flash back to DI01 in order to restore my phone. Thanks anyway all.
Where did you find that stock restore for odin, I have the same issue.
im having same issue...any help would be great
I was getting this issue the other day. The only way I could fix it was as suggested... DJ05 flash with odin.

Rom Manager

This getting a little annoying.
I have the blue CMW, flash it to RED CMW, got red to work fine. Flash it to new CMW (green) got that to work fine. Found a few zip update on XDA said to use Rom Manager to flash, did that. Rom Manager revert CMW back to blue. So have to odin flash red again and then recovery mode update to new cmw again.
Will we be getting new Rom Manager? I even paid for the premium version too eheh...
Rom Manager revert CMW back to blue.
Click to expand...
Click to collapse
That's the stock recovery, not CWM I'm pretty sure. On that screen, you need to select the 'Apply updates.zip' option, which will take you to CWM. Also, if you're still running the stock kernel (pretty sure you should be running a voodoo if you're seeing red), it'll wipe out CWM.
Green & Red = CWM
Blue = Samsung Stock Recovery
KitsuneKnight said:
That's the stock recovery, not CWM I'm pretty sure. On that screen, you need to select the 'Apply updates.zip' option, which will take you to CWM. Also, if you're still running the stock kernel (pretty sure you should be running a voodoo if you're seeing red), it'll wipe out CWM.
Green & Red = CWM
Blue = Samsung Stock Recovery
Click to expand...
Click to collapse
Ur right, dumb me. I just realized that on the 20th reboot to recovery today...ahah

[HOW-TO] New Clockwork Manager

[RED-CWM] (not orange)
Alright sick of scanning 3 different threads trying to help people with the new Clockwork manager I decided to write up this guide. This was tested from stock, I flashed back to stock to test both these methods, and they should work for everyone.
Stock versions tested: DI01 (stock), DJ05 (stock), odin method works flawlessly on these versions. cwm was not replaced by sammy kernel.
Stock DL09 will remove cwm on reboot, install a different kernel adryn's should work, pick your poison here: http://forum.xda-developers.com/showthread.php?t=915709 flashed cwm via odin. install kernel, then rebooted, if you get stock recovery flash via odin one more time.
Nonvoodoo EB01 currently some people report it will boot to blue recovery after installing new roms. nonoodoo users should leave, http://dl.dropbox.com/u/2056318/update.zip on the root of there sdcard that way after a new install of a rom you can get back to cwm. after applying udate.zip, install cwm-recovery-ALL.zip. (Thanks Landshark68)
To get to stock use adrynalyne's DI01 package get it here: http://forum.xda-developers.com/showthread.php?t=867648 flash via odin.
First I would like to thank jt1134 for fixing up the new cwm get your perferred version here: http://forum.xda-developers.com/showthread.php?t=942021
Odin method (preferred method stock users do this one!)
1. Alright let’s do this, head over to jt’s original post and download the cwm-recovery-ALL odin:
2. Plug phone into PC and turn off phone
3. Pull battery in phone and then press the down volume button
4. Open odin on PC and press PDA load cwm-recovery-ALL.tar, DON’T MESS WITH ANY OTHER SETTING! Then hit the start button.
5. Boot into recovery (cwm) do this by holding both volume keys plus the power button till you see Samsung screen, you can let go then.
6. Congrats your done now install your custom roms, kernels, radios, and other various things!
Clockwork manager method (only if you have cwm installed already)
1. Copy new cwm-recovery-ALL.zip to root of SD card. (do not need to rename!)
2. Boot into recovery
3. Choose install zip from sdcard
4. Choose cwm-recovery-ALL.zip
5. Reboot your phone and delete update.zip from root of SD card, and recovery-update.zip from clockworkmod folder.
The cwm should be red, and should say voodoo no matter if you have a voodoo kernel or not.
Rom manager will not boot your phone to recovery, install a new shutdown menu that includes boot to recovery or do a manual boot to recovery.
The new clockwork manager installs to the boot partition of the phone that's why you no longer need the update.zip file. Do not flash the cwm from Rom manager, it’s not needed folks, and will put your phone into an endless boot. The cwm jt gave us is customized for our phones.
Post your questions here I will be happy to answer them.
Below I attacked the clockwork manager files, plus odin3 v1.3 but visit jt's OP and give him a thanks, I'm just the translator, hes got plenty of other crap to do rather than test this out.
I am not responsible for any bricked, broken, or abducted phones.
Tried it, works fine. Took a bit on that first boot into recovery after the install was run (already had cwm installed), you know that held breathe of "did it work"!
vlucchetti said:
Tried it, works fine. Took a bit on that first boot into recovery after the install was run (already had cwm installed), you know that held breathe of "did it work"!
Click to expand...
Click to collapse
just be sure not to flash cwm from rom manager application, or you'll be holding your breath till you black out
Takafiji said:
just be sure not to flash cwm from rom manager application, or you'll be holding your breath till you black out
Click to expand...
Click to collapse
Seriously thinking of deleting ROM Manager altogether. I did dl Adryn's revised ROM Mgr but may switch to doing everything through cwm.
I think the slight delay after the double samsung flash is the program working through blue in the background so it jumps right to red afterward.
Adryn's kernel isn't working for me. But that's what searching is for.
I also owe you a huge thanks for all your help earlier.
Sent from my SCH-I500 using XDA App
lfrench0 said:
Adryn's kernel isn't working for me. But that's what searching is for.
I also owe you a huge thanks for all your help earlier.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
no prob thats what we're here for.
any custom kernel built for dj09 will work. only use a kernel for your raidio/rom version ie: dI01, dj05, dj09, dl30, ebo1 etc...
Hey Takafiji,
I posted a similar thread over at Android Central about the same time as yours here at xda. I discovered this ability to boot directly to red cwm, and I put together the how-to thread and everything was great until I booted to recovery one time and saw stock blue (2e) recovery. I played around with different options, but couldn't completely get rid of blue recovery. I decided to do some research in jt1134's thread and saw the link to yours and read everything here. I have tried every method in your thread and jt1134's thread and I keep running into the same problem. I can install the new cwm just fine and I can keep booting directly into red cwm just fine until.........I flash a new ROM. I can flash themes, patches, add-ons no problem, still able to boot to red cwm. As soon as I flash a new ROM, I boot to stock blue recovery. The only ROM I have been flashing is Adrynalyne's superclean 2.4. I read in jt1134's post that flashing a stock kernel will revert you back to stock blue recovery. The kernel in Adrynalyne's sc 2.4 is the farthest from stock we can currently get in nonvoodoo EB01. My guess is we will not be able to boot directly to the new red cwm on nonvoodoo until the devs get their hands on the source code and we get some custom nonvoodoo kernels. Any thoughts? Thanks
landshark68 said:
Hey Takafiji, Any thoughts? Thanks
Click to expand...
Click to collapse
ummm not sure here, you could try a voodoo kernel, they work wonderfully. how are you rebooting to recovery? rom manager doesn't work all too well in that area, try using the power menu and reboot to recovery that way. i will do some more testing but ive been jumping around on different eb01 roms just fine. Is it all roms or just superclean ones?
Takafiji said:
ummm not sure here, you could try a voodoo kernel, they work wonderfully. how are you rebooting to recovery? rom manager doesn't work all too well in that area, try using the power menu and reboot to recovery that way. i will do some more testing but ive been jumping around on different eb01 roms just fine. Is it all roms or just superclean ones?
Click to expand...
Click to collapse
I got rid of Rom Manager as soon as we got the long press power button menu with recovery in it. The only ways I boot to recovery are long press power and holding volume down, volume up, and power buttons.
ummm have you tried applying a older cwm after booting to blue recovery? maybe if you booted to that then installed jt's new cwm you'd be set. just a thought. http://dl.dropbox.com/u/2056318/update.zip should work, if it comes up unsigned we will have to explore different options. I'm trying to figure out why its going blue with a non-stock kernel, the new cwm installs to the boot partition.
Takafiji said:
ummm have you tried applying a older cwm after booting to blue recovery? maybe if you booted to that then installed jt's new cwm you'd be set. just a thought. http://dl.dropbox.com/u/2056318/update.zip should work, if it comes up unsigned we will have to explore different options. I'm trying to figure out why its going blue with a non-stock kernel, the new cwm installs to the boot partition.
Click to expand...
Click to collapse
Already tried that if the old cwm you are linking me to is the new red cwm for froyo we had before the current one. Loaded that cwm via ODIN, had new red on base of sd card, installed via old red cwm, no luck, went back to blue as soon as i flashed sc 2.4. The only thing I'm thinking is I don't think the kernel in sc 2.4 is truly a custom kernel. I believe I read the kernel in 2.4 is still the stock kernel, just slightly modified by Adrynalyne. Thanks.
landshark68 said:
Already tried that if the old cwm you are linking me to is the new red cwm for froyo we had before the current one. Loaded that cwm via ODIN, had new red on base of sd card, installed via old red cwm, no luck, went back to blue as soon as i flashed sc 2.4. The only thing I'm thinking is I don't think the kernel in sc 2.4 is truly a custom kernel. I believe I read the kernel in 2.4 is still the stock kernel, just slightly modified by Adrynalyne. Thanks.
Click to expand...
Click to collapse
have you tried flashing stock di01, then jumping to a stock eb01, maybe that would work. not sure but i know the dl09 recovery overwites cwm. maybe you just got parts of it still stuck there...
Sorry wish i was a c programmer i'd jump on board and start helping create a custom kernel.
Takafiji said:
have you tried flashing stock di01, then jumping to a stock eb01, maybe that would work. not sure but i know the dl09 recovery overwites cwm. maybe you just got parts of it still stuck there...
Sorry wish i was a c programmer i'd jump on board and start helping create a custom kernel.
Click to expand...
Click to collapse
No problem. I'm just going to keep going through blue recovery to get to red cwm until we get some custom nonvoodoo kernels. I updated my OP to advise everyone there on nonvoodoo to put update.zip back on the root of their sd card and do the same for now. Thanks again for the brainstorming and ideas.
EDIT- Also to let you know, yes I already tried flashing back to DI01 then to EB01. We are definitely thinking along the same lines.
Well now I'm totally gorked up. I followed Zacisblack's method with your addition of doing the ODIN install first. Now when I get blue recovery and hit apply sdcard:update.zip I go to green cwm. Trying to figure out a solution to that now.
EDIT - fixed that problem. Fortunately I still had a copy of the cwm_froyo.tar
I also have the same issue when flashing a new rom. It always goes to blue recovery.What I have to do every time is in blue cwm go to apply sdcard/update.zip which gets me in green cwm. Then I go to choose zip and scroll down to clockwork and choose cwm-recovery-all and flash it again then scroll down to update.zip and flash it then i go to applysdcard/update.zip and flash that then i reboot. Then next time i boot into recovery it always goes straight to red cwm. Sounds like a pain (and sometimes it is) but in reality it only takes like 5 minutes. I wish i didn't have to do that every time i flash a new rom but thats just part of my routine now as its what works for me.
I might not have to do all of those to get back to red but thats the way i originally got red cwm on my phone from a great write up on jt's thread (sorry but don't remember who did the write up). Maybe I'll experiment with just flashing one of those zip's next time i flash a rom to see if there's a faster way.
But I would really like it if there was a way to just always go to red cwm with a new rom instead of going thru all that.
Fantastic tutorial! Just what I was looking for! Thanks a million!!
Thanks Takafiji! I had just installed the Superclean v2.6 non voodoo and got the stock blue (2e) recovery as well. I tried to apply the update.zip and it took me to orange. I read your original post and it worked wonderfully!
Takafiji Quote from OP:
"Nonvoodoo EB01 currently some people report it will boot to blue recovery after installing new roms. nonoodoo users should leave, <drop box link to update.zip> on the root of there sdcard that way after a new install of a rom you can get back to cwm. after applying udate.zip, install cwm-recovery-ALL.zip. (Thanks Landshark68)"
...now, if I could just figure out why Google Voice can't seem to find my contacts, i.e. voice command "Call Mark Davis", nothing found and defaults to looking on the web.
My phone won't even update the app. When I try it d/l's, starts then aborts saying it isn't properly signed. Guess I'll stay with Adrynalyne's modified one for now.
I used ODIN to flash the new-CWM, but it always seems to boot into blue recovery. Using update.zip gets me into green, which seems to work fine for flashing roms. I've occasionally seen red recovery, but when using update.zip takes me right back to green.
Am I doing anything wrong here?
Thanks for the write-up I flashed recovery with ODIN
In read recovery and working great
again THANKS for the writeup

[Q] Flashing Adrynalyne's DL17 deodex for Continuum

I've rooted my phone, and followed these instructions here http://www.addictivetips.com/mobile/install-clockworkmod-recovery-on-samsung-continuum/ to put CWM on and these instructions here http://www.addictivetips.com/mobile/install-dl17-clean-rooted-android-2-1-rom-on-samsung-continuum/ to flash the ROM on. I also added tried adding these test kernels http://forum.xda-developers.com/showthread.php?t=926555 as well.
None of this seems to have stuck. When I reboot the phone after clearing all data and caches in CWM and installing the ROM, it boots up to the standard Samsung Continuum interface. When I go into recovery mode again, it goes back to the standard Android recovery mode instead of CWM. I have also tried CWM manager, but it does not work because the Continuum is not on its list of phones to install the recovery, and because the recovery I manually install does not stick, i can't use the interface to install the rom.
Please, can someone point me in the right direction with what I did wrong/why the ROM does not seem to be working?
Thanks!
May i ask what you mean by, "standard Samsung Continuum interface"? Once you flash a rom, it is definitely going to "stick"... You know that this is just a cleaned up rom, right? no theming or anything? so it is going to look the same (excluding the launcher)...
One thing i can think of is to ake sure that in Mount in CWM that System is mounted, just to make sure..
Also, by following those posts, you SHOULD go to the original recovery screen... Then you need to press "apply:update.zip" or whatever to get into CWM.. if that doesn't work, then do this:
use ODIN to flash the recovery and kernel, and as soon as it is done, hold in the recovery button combination (power, vol up/down)... Sometimes thats the only way to get into it for some people...
Yeah, I just meant cleaned up. When I reboot, my phone still has touchwiz interface, Bing and bloatware. I do use the update.zip to get the CWM recovery screen, which works fine, but when I try to get into the recovery screen again, i have to reload the update file, and when I try to use Rom Manager is says that CWM is not installed.
In CWM, after loading the update file, it says that the three zip files are installed, but when I exit the recovery screen via reboot, the files that were supposedly installed do not take effect.
is "Mount" an option somewhere in the CWM commands?
Yea clockwork recovery won't stick. It's not supposed to. whenever you go into recovery mode you will have to load the update.zip every time. But I have the clean ROM flashed and the peanutbutta jelly time kernel and it's working just like it's supposed to. I think imnuts is working on getting the recovery to stay
Sent from my SCH-I400 using XDA App
i just tried flashing the peanutbutta jelly time kernal and clean DL17 and the two updates, but the phone freaked out after the samsung logo on reboot, scrambling the screen and looking frozen. I pulled the battery and reinstalled adrynalyne's test kernals and but now it is just booting to the regular factory OS.
oh and the system is mounted
After you flash the kernel the boot screen should mess up. It's fine after it boots though
Sent from my SCH-I400
Ok so waited for the phone to boot, but still booting to stock Samsung OS/interface. My flashing in CWM was as follows:
Delete data
Clear cache
Clear davlik
flash peanutbutta
flash DL17
flash email update
flash social app update
reboot
samsung logo, screen messed up but still hearing booting sounds, then finally loads into the stock samsung interface.
What am I doing wrong?
The stock samsung interface WILL remain, aka touch wiz. There will be a couple verizon apps that will remain with this rom. Also what version of cwmr are you using?
oh ok, that would be where the confusion lays. It was my understanding that it was detouchwizzed as well. Does debinging remove bing as the default and only search engine in the browser? is there a mod/ROM that de touchwizzes the continuum?
Also, I feel like this is a stupid question, but if i have this ROM on here, that means I won't be able to get OTA updates, correct?
Correct....
Sent from my SCH-I400 using XDA Premium App

[Q] What exactly happens when CwM doesn't stick?

I'm wondering because I just rooted and flashed SuperClean3 w/ KGB mod. When I first opened up Odin, I actually used the blue CwM. It booted right up so I thought everything was fine. I booted into stock, tried to go back into recovery to flash SuperClean3 but the recovery never showed up again. It just went to stock recovery without a update.zip option. So I opened Odin up again and used red, but this time flashed SuperClean3 and KGB right from the start. I'm still wondering though, what exactly happens when CwM doesn't stick? Does the kernel kick it off, uninstalls it, or what? Is the blue CwM I used first still on my phone somehow?
adoboyo said:
I'm wondering because I just rooted and flashed SuperClean3 w/ KGB mod. When I first opened up Odin, I actually used the blue CwM. It booted right up so I thought everything was fine. I booted into stock, tried to go back into recovery to flash SuperClean3 but the recovery never showed up again. It just went to stock recovery without a update.zip option. So I opened Odin up again and used red, but this time flashed SuperClean3 and KGB right from the start. I'm still wondering though, what exactly happens when CwM doesn't stick? Does the kernel kick it off, uninstalls it, or what? Is the blue CwM I used first still on my phone somehow?
Click to expand...
Click to collapse
The blue recovery is mainly for mtd roms. You need to longpress the power Key and boot into recovery that way or it will always revert to stock recovery iirc.
Sent from my SCH-I500 using XDA App
adoboyo said:
I'm wondering because I just rooted and flashed SuperClean3 w/ KGB mod. When I first opened up Odin, I actually used the blue CwM. It booted right up so I thought everything was fine. I booted into stock, tried to go back into recovery to flash SuperClean3 but the recovery never showed up again. It just went to stock recovery without a update.zip option. So I opened Odin up again and used red, but this time flashed SuperClean3 and KGB right from the start. I'm still wondering though, what exactly happens when CwM doesn't stick? Does the kernel kick it off, uninstalls it, or what? Is the blue CwM I used first still on my phone somehow?
Click to expand...
Click to collapse
Anytime you odin cwm recovery over a stock rom/kernel you have to three finger into recovery right away. If you let the phone boot once the stock kernel will not let cwm stick. So then you have to odin cwm all over again. Use red recovery for anything touch wiz btw.
---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------
mkuehl06 said:
You need to longpress the power Key and boot into recovery that way or it will always revert to stock recovery iirc.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thats incorrect...
Stock ROMs have a script called install-recovery.sh. If it boots, custom recoveries are overwritten. Thats why you have to flash a custom ROM right away, or remove that script.

Categories

Resources