Rom Manager - Fascinate General

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

Related

[Q] red cwm and rom manager

Does anyone know if there is a way to force rom manager to bypass its check for cwm. I have red cwm installed, and don't wanna flash green cwm, I just want to use rom manager to pull down themes and such, and extract or manually flash what ( want, but it wont let me past the flash cwm or cancel pop-up....
Well, I still use green cwm, so Im not sure, but if Rom manager still lets you download stuff...
you can still manually install things you download in Rom manager.
They get stored in /sdcard/clockworkmod/download -
So you can download them, cancel the cwm install, then boot into recovery and install manually.
That's just it, it wont let me use it, unless I relent to let it install, green cwm. I'm on super clean dL09 with adrynalyne's 1230 voodoo kernel, which, if I understand is what red cwm was built for, voodoo I mean...
Sent from my SCH-I500 using XDA App
When you reboot into green CWM from Rom Manager, go to Advanced, and select Reboot to recovery, and it will reboot the phone into the red CWM. Either that, or you can power off the phone and old Power + Volume Up + Volume Down to get into red CWM, or use ADB or Terminal Emulator to enter the "reboot recovery" command, which will also have the same effect. Once in red CWM, just choose to install from zip file, and browse to the download folder that Bawb3 pointed you to to find the ROM zips to install.
If you haven't flashed CWM with Odin as well as ROM Manager then it won't actually install... Flashing with ROM Manager only puts the update.zip on your SD card, and flashing with Odin actually puts the recovery kernel on the phone.
Okay, gotcha.....thats what I needed to know.....
Thanks guys, much appreciated....
I odined the red cwm package that adrynalyne posted to go along with the voodoo 1230 kernel. I just wanted to make sure I didn't blast it out of the phone with rom manager. I can get to the red recovery just fine, as y'all mentioned with volume up/down and power, so.....three finger salute....
I'm coming from a Moto Cliq XT , which seemed a bit simpler to pop into recovery and flash stuff using an amon RA recovery than this one.... still learning the ropes..
Thanks again...
Sent from my SCH-I500 using XDA App

[Q] Stuck on my Touch Splash Screen

Hi, I have rooted my phone and have s off. I've purchased rom manager and installed clockworkmod 3 and have backed up my phone.
When I try to flash the latest cyanogenMod Nightly I run into problems.
The phone gets wiped and updates and then it gets stuck at the Tmobile my touch splash screen. I've left it there for 10 minutes and still no cyanogen.
Any help is greatly appreciated
Thanks
Also I'm able to go back into recovery mode and restore my backup. So my phone is currently back in stock rom.
AnroidGuy2011 said:
Hi, I have rooted my phone and have s off. I've purchased rom manager and installed clockworkmod 3 and have backed up my phone.
When I try to flash the latest cyanogenMod Nightly I run into problems.
The phone gets wiped and updates and then it gets stuck at the Tmobile my touch splash screen. I've left it there for 10 minutes and still no cyanogen.
Any help is greatly appreciated
Thanks
Click to expand...
Click to collapse
If you successfully backed up your phone you are not using Clockwork ROM Recovery 3.x. It's a well known fact that that Recovery image has problems backing up Nandroids, or restoring them for that matter.
What color was the text when you were in recovery? Orange or green?
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
AnroidGuy2011 said:
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
Click to expand...
Click to collapse
if you are wanting CM7 yes you need to flash Clockwork ROM 3.0 via the Fastboot ADB commands. If you are wanting your phone to work you can flash of any of the other ROMS as of right now.
Clockwork ROM 3.x will not do nandroid back ups in it's current state. As Gingerbread comes closer to being an official or RC i'm sure they make sure it can do nandroids. nor will 2.x do nandroids of CM7. but to answer your question you are correct.
AnroidGuy2011 said:
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
Click to expand...
Click to collapse
You are correct. See my thread here For the easiest way to install 3.0.0.5. And yes you can use Rom Manager for backups while on 2.5.1.2 but Rom Manager isnt compatable with flashing or backups for 3.0.0.5. You must use recovery.
TrueBlue_Drew said:
You are correct. See my thread here For the easiest way to install 3.0.0.5. And yes you can use Rom Manager for backups while on 2.5.1.2 but Rom Manager isnt compatable with flashing or backups for 3.0.0.5. You must use recovery.
Click to expand...
Click to collapse
This is good. Every time I try to answer a thread, you seem to beat me to it.
Thanks for the help
neidlinger said:
Clockwork ROM Recovery 3.x. It's a well known fact that that Recovery image has problems backing up Nandroids, or restoring them for that matter.
Click to expand...
Click to collapse
I rooted, made a back up with Clockwork ROM Recovery 3.x. , flashed CM7 and everything was fine. Then I flashed Kernel_2.6.32.27grankin01-CM-GB-OC-v0.09 and when I unlocked the screen everything started force closing on a black screen. I locked the screen again, powered off and on again then it got stuck on the splash screen. I restored my back up and it's stuck on splash screen still. Then I tried to flash Kernel 2.6.32.21grankin010OC0v0.05 thinking my back-up might need a stock kernel. I am a super noob at this, I have successfully flashed roms to my tab before, but I've only been learning about this for about a month. I've been searching and searching but can't seem to find a solution. Am I screwed?
igrillem said:
I rooted, made a back up with Clockwork ROM Recovery 3.x. , flashed CM7 and everything was fine. Then I flashed Kernel_2.6.32.27grankin01-CM-GB-OC-v0.09 and when I unlocked the screen everything started force closing on a black screen. I locked the screen again, powered off and on again then it got stuck on the splash screen. I restored my back up and it's stuck on splash screen still. Then I tried to flash Kernel 2.6.32.21grankin010OC0v0.05 thinking my back-up might need a stock kernel. I am a super noob at this, I have successfully flashed roms to my tab before, but I've only been learning about this for about a month. I've been searching and searching but can't seem to find a solution. Am I screwed?
Click to expand...
Click to collapse
IMHO opinion you are not screwed.
When flashing custom Kernels you need to have a program like SetCPU so you can govern the CPU speed. To fast of a speed or to slow of a speed and it will not boot correctly. You need to flash a different version of CM7 than you are using now, via the recovery screen. make sure to wipe the handset first. that should reset the Kernel to one that Zinx knows works with the phone.
As well i wouldn't recommend flashing kernels with Nightlies. They are unstable as it. and you need to make sure the kernel is compatible with Nightly you are using. And you can over clock them to 1.5Ghrzf from w/ in the ROM.
neidlinger said:
make sure to wipe the handset first. that should reset the Kernel to one that Zinx knows works with the phone.
Click to expand...
Click to collapse
HHHmmm I'm glad I never forget this step on the toilet! Thanks for the help!

[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

Clockwork mod blue

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.

[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