yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] droidzach:
Did anyone else have their phone boot into safe mode after installing this? Mine did and I had no access to any apps other than the stock ones. Ive never seen it before booted back into recovery and wiped dalvik and all was well tho just wondering if any one else had this?? Thanks for this by the way!

Swyped from my Mesmerize using XDA app
[Fascinate Android Development] Azaurath:
No. Didn't know Android had a safe mode either.
[Fascinate Android Development] obliviator33:
nvm, I figured it out. Had to use the rename
[Fascinate Android Development] ivorycruncher:
Forgive me if this has already been answered somewhere, but I've been looking and haven't seen the question posed. I am currently running the red Voodoo-capable CWM with DL09 Super Clean and a Voodoo kernel. I am considering taking the plunge to EB01 Super Clean, and while I understand that I will need to disable the Voodoo lag fix first, I'm unsure of whether I need to do anything with CWM or not.

I know green CWM is broken, but my question is does the Voodoo red CWM work okay with the new Froyo ROMs, or do I still need to flash jt's new non-Voodoo red CWM first?
[Fascinate Android Development] jt1134:
flash one of the packages in the OP, and you'll be good
[Fascinate Android Development] jt1134:
Updated OP with new versions of the recovery which WILL work with voodoo installations.
[Fascinate Android Development] BeeDubs:
Ok, I can't seem to install this.

I'm on DJ05 modem, a UV voodoo kernel, and was on SC 0.9.

I just flashed the EB01 modem in Odin (PDA mode).

I rebooted into red cwm to flash this updated CWM, but when I do that, I get the error:

E:can't chown/mod /tmp/kernel_update/redbend_ua
(no such file or directory)
E:failure at line 3:
set_perm 0 0 755 TMP:/kernel_update/redbend_ua
Installation aborted.

Any ideas what's wrong?
[Fascinate Android Development] Southp@w:
^^ Me too EB01 Supa Clean
[Fascinate Android Development] BeeDubs:
So you have no working red cwm (voodoo), right? Because you couldn't update the CWM recovery?
[Fascinate Android Development] Southp@w:
Correct and Im non voodoo
[Fascinate Android Development] jt1134:
my bad

fixed
[Fascinate Android Development] BeeDubs:
So just redownload file in OP and flash again in Red CWM?
[Fascinate Android Development] euklid:
So what version is this cwm suppose to say..i flashed using odin and using zip file and im not sure if it updated because i cant seem to update zips still..it says cwm red voodo lag fix v2.5.1.x
[Fascinate Android Development] jonagpa:
Cant mount SDCARD!!

Ok i used odin to flash this.

it automatically boot into red CMW

i can go through the menus

when I try to installed from sd (choose zip from sdcard) it says something about not able to mouth SDCARD

E:cant mouth /dev/block/mmblk1p1 or /dev/block/mmcblk0

(invalid argument)

E:cant mouth /sdcard

I tried several times, taking out and putting back in the sd card, I flashed odin package several times with same result

some please shine a little light.

edit: forgot to add that I am on EB01, I tried this after successfully flashing super clean 2.1 using the old CmW. I try to boot into CMW(old) but did not get past blue screen. I read that the old CMW does not work with froyo so I flashed this red CMW.
[Fascinate Android Development] Hypnosis4U2NV:
Just installed the zip through Green CWM and I was able to boot into Red CWM via Rom Manager so it appears to be working correctly.. Haven't tried installing zips yet or using any of its functions..

Sent from my Fascinate running SuperClean v.4 DL09 ROM/Adrynalyne Test SV 1/21 Kernel on TapaTalk
[Fascinate Android Development] BeeDubs:
I got it to work (I think). Well, I mean that it installed (the new file in updated OP).

Thanks, jt.
[Fascinate Android Development] onemotodroid:
check to see if you have errors when backing up your roms. just look and check all messages
[Fascinate Android Development] dadsterflip:
I'm having trouble flashing the red recovery over. I'm in the dl30 leak. I've tried Odin and still boots to green. Then I tried flashing over and it gets flying letters and revolts back to the green recovery. What am I doing wrong? Dl30 and on the dl09.
[Fascinate Android Development] theGross1:
Amazing! This just saved my butt. Phone was booting into recovery and wouldn't get into CWM. Nothing seemed to work. Repushed CWM via Odin with not change. Found this thread flashed new CWM red and booted just fine. Thanks! EB01
[Fascinate Android Development] tmlhodge:
JT,

Can I fix permissions and wipe battery stats with the new recovery. I know it didnt work with koush's

Thanks
[Fascinate Android Development] dadsterflip:
You don't happening to have that new update.zip do you????
[Fascinate Android Development] lfrench0:
ok, If I have just rooted and need to install this cwm for the first time. I got the all odin package, but I don't see the .tar file which would normally go in odin or the update.zip to put on the sd card. What exactly do I do with the .zip? Sorry for the newb questions, but I'm new to this and would prefer to get it right the first time(if all goes as planned, but that's just wishful thinking)

Thanks
[Fascinate Android Development] ivorycruncher:
You must be very confused. This CWM installs to your phone's boot partition, so you do not need update.zip on your sdcard for it to work. For some reason, nobody seems to understand this.

As for the tar file for flashing from Odin, the download link is clearly accessible in the op post. Not sure what else to tell you there. The zip file from the op post is simply an alternate install file that installs the new red CWM from another version of CWM (older red, or green) if you prefer not to flash it from Odin.

Posted from my EB01 SuperClean Fascinate with Voodoo
[Fascinate Android Development] lfrench0:
I am confused, I downloaded the all odin file. I don't see the .tar file. Just 2 subfolders.

EDIT: For some reason my pc kept downloading the all .zip file when I clicked on the odin file, but alas I finally got the .tar file.

Thanks
[Fascinate Android Development] peterkim89:
hi, i just tried to go into eb01 from di01 completely stock phone.

when i tried to flash the new cwm, it says:

"--Install from package...

Finding update package...

Opening update package...

Verifying update package...

E:failed to seek in /cache/update.zip (Invalid argument)

E:signature verification failed

Installation aborted."

can someone help me?!
[Fascinate Android Development] ivorycruncher:
You're still using the stock recovery, which will only install zip files signed by Verizon/Samsung. Since you have never rooted, you will need to first install the CWM from the OP post using Odin, and then you will be able to use that to install other roms. Search the forum for instructions on how to flash via Odin. Plenty of posts out there that tell how.

Posted from my EB01 SuperClean Fascinate with Voodoo
[Fascinate Android Development] jonagpa:
Has anyone found a solution to my original problem? I still cant mount my sd card, I am able to boot in to the RED CMW and go thorough the menus.

I understand that this flashes CMW on to the phone itself and there fore I dont need any update.zip or recovery_update.zip right?

if it does require an update zip can someone please share it here.
[Fascinate Android Development] lfrench0:
I just flashed the odin .tar file to my phone(newb so I've never had cwm before). But I can't get into red recovery. I only get the factory blue recovery? Other threads state that you must place an update.zip file on the sd. Is it required? There wasn't one in the download. I'm not exactly sure what's happening. I thought it flashed successfully. But when I go to Rom Manager to backup current rom, it says I must install CWM. All help is appreciated.
[Fascinate Android Development] Takafiji:
no worries this is a forum we're here to help one another out.

yeah put an update.zip on the root of the sd card, http://db.tt/kWmVm4F should do it. rename it to update.zip

here are my fool proof steps:

used this method multiple times, if your on stock skip the first step.

Put http://db.tt/kWmVm4F at the root of sdcard, call it update.zip

1. Go to download mode, revert to dl01 (stock) package.

2. After reverting i went straight to download mode and proceeded to odin this file http://db.tt/6dZUc7d (thanks jt!).

3. Then after reboot i went directly to recovery mode, it took me right to red cwm. I then flashed a custom rom (super clean 2.4) and a custom voodoo eb01 kernel. I think this step is key to the process. Also applied update.zip

4. After this i went back to download mode and odined the eb01 modem, then booted to android.

5. After all this i put my device into usb mode and copied http://db.tt/kWmVm4F (thanks again jt!) putting it on the root of my sd card, naming it update.zip. (skip if you did this already before going to stock)

6. Lastly i copied it again to my clockworkmod folder on my sd card and renamed it "recovery-update.zip"

Booted to recovery installed things (zips) no problem.

Hope this helped!
[Fascinate Android Development] lfrench0:
OK, one more question I think rom manager put cwm on my phone by ittself. What's worse is I deleted the clockwork folder and its update.zip. I wasn't thinking but I didn't want that cwm. I know it was stupid, but I just hope I didn't cause too much harm. If it helps Rom Manager now wants to install cwm again. So I think that may be a good sign.

If I use the odin method with the included update.zip can this override the one rom manager installed which I then proceeded to delete.
[Fascinate Android Development] Takafiji:
odin method will allow you to boot to cwm on next boot i believe, because of the sammy kernel/recovery. (could be wrong, no probably am wrong, anyways)

i would download http://db.tt/kWmVm4F rename it to update.zip, and copy that to the root of my sd card overwriting older cwm first.
[Fascinate Android Development] lfrench0:
I get an error that says:

Failed to verify whole-file signature

Signature verification failed

Im pretty sure that's what it read, didn't catch it all. Again many thanks
[Fascinate Android Development] Takafiji:
need to get a verified version of cwm here you go use this update.zip file first http://dl.dropbox.com/u/17566514/update.zip

This is a pretty good guide after you get that on your sd card.

http://xdaforums.com/showthread.php?t=957132
[Fascinate Android Development] ivorycruncher:
I will repeat this as many times as necessary. The version of CWM in this thread does NOT require or use an update.zip file on your sdcard. I know this because I have no such file on my sdcard, and can still boot into CWM just fine. This CWM installs onto your phone's boot partition, instead of being loaded from the update.zip file on the sdcard, which is the Rom Manager method.

EDIT: Just to clarify, if you want to use Rom Manager to reboot into recovery, you should be theoretically be able to do so with a newer update.zip. Don't use the old 2.1.0.4 green version though (just tried it on mine, and got booted into the screen with Andy and the big exclamation warning; thought I bricked myself for a second there). I would personally recommend avoiding Rom Manager altogether, and reboot into recovery using the three finger salute, or via the modded shutdown menu.

Posted from my EB01 SuperClean Fascinate with Voodoo
[Fascinate Android Development] Takafiji:
Thanks for sharing that, i hadn't read the whole thread just jumped in for this part.
[Fascinate Android Development] lfrench0:
Im so lost. How exactly should I go about this? Thanks
[Fascinate Android Development] ivorycruncher:
Sorry, I know it's confusing. There's so much conflicting information, and so many versions of CWM running around, I'm having a hard time wrapping my head around it too. Here's what I know to be true:

The red CWM installs onto the phone, replacing the stock recovery. When successfully installed, no zip files of any kind need to be maintained on the sdcard. I would strongly recommend not attempting to use Rom Manager after this.

If you're still running a stock kernel, it has a tendency to reload the original stock (blue) recovery when it boots, overwriting the red CWM recovery. If you install a modified kernel, such as the Voodoo one, this should no longer be an issue.

Here's what I would try. First of all, download the .zip from the OP post, put it on your sdcard, and rename it to update.zip. Next, re-flash the .tar file with Odin. Once that's done power off the phone, and then boot directly into recovery by holding the power and volume buttons until the Samsung boot logo disappears and reappears again. This should get you into red CWM. From there, select the "apply sdcard:update.zip" option. You'll see some funky blue text on the screen, and then it should bring you back to the red CWM screen with a message stating it's been installed successfully.

At that point, based on all the pieces of data I'm putting together from Takafiji, Zacisblack, and others, red CWM should be permanently installed. You can try rebooting into recovery a few times to try it out. If it stays put, you can delete the update.zip file from your sdcard, as it's no longer being used, although it doesn't hurt to leave it there for emergencies. If blue comes back, you should be able to get back into red by applying the update.zip file. I would also recommend installing the Voodoo lag fix, as it gives a good performance boost, and will pretty much 100% guarantee that red CWM will stay put.

I'm guessing this is why I've never had issues with the stock recovery reappearing, because I've been on Voodoo ever since I first installed CWM. I've only seen the blue recovery reappear once, which was after I disabled the lag fix and installed EB01 Super Clean without Voodoo. I had to reinstall red CWM once then, and after installing the EB01 Voodoo kernel, red CWM is once again a permanent fixture on my phone.
[Fascinate Android Development] Grimis:
Did it exactly as you said and it worked flawlessly. I to would get blue stock recovery pop up from time to time. It does appear that when on a non voodoo kernel it happens more frequently. I'll report back after running this awhile. Thanks
[Fascinate Android Development] lfrench0:
First off I'm not running voodoo. I placed cwm-recovery-ALL.zip on my sd card renamed as update.zip. I flashed using odin. It booted to red. I selected update.zip. Blue text came up. I tried booting into recovery again. Got blue, selected update.zip. and got triangle with exclamation mark.

I desperately need help. Any help is greatly appreciated.

I need help figuring out how to get cwm working. It wouldn't bother me if I could boot into red from blue, but it fails. So no backup for me, which also means I can't proceed with eb01 with blackhole.

Again thanks.
[Fascinate Android Development] Takafiji:
you cant use that file to boot to cwm for first boot, try flashing http://db.tt/6dZUc7d via odin, it will save you the headace of all the other crap, thats the only thing you will need to flash in theory. no more blue recovery, or update.zip ect.

I will try this new method right now, tell you what happens.
[Fascinate Android Development] ivorycruncher:
As long as you're running the stock kernel, that's going to keep happening. Flash via Odin and boot into red one more time, like you just did. As soon as you're in red, do a nandroid backup if you want, and then immediately wipe the data, cache, and dalvik cache, and install the rom and kernel of your choice. Do not exit red CWM until you've done so. Once you've installed a different kernel, either by itself or one included with a rom, the blue recovery shouldn't come back anymore.
[Fascinate Android Development] Nobody Important:
I'm trying to follow these instructions, but can't seem to get to red CWM ever. I flash the above tar via Odin, it reports success and the phone boots normally. But when I shut down and reboot into recovery I get blue CWM. What am I doing wrong? Sorry for the newbie question.
[Fascinate Android Development] Takafiji:
ive addressed that in this thread read the top carefully.

http://xdaforums.com/showthread.php?t=960118
[Fascinate Android Development] Nobody Important:
Ah, now I see. Odin was set to automatically reboot the phone. When it rebooted, it would appear that it booted normally, loading the regular kernel and rom, including the blue CWM. At least that's my guess. What worked for me was to uncheck this box. Then after Odin was done flashing, I unplugged the phone and booted into recovery, and got the (correct) red CWM. Many thanks.
[Fascinate Android Development] drumtrucker:
i am getting access denied when trying to d/l from OP. Have not seen this before. Have dl lots of stuff from xda.
[Fascinate Android Development] Takafiji:
i attached the files in this thread along with odin. there the exact ones posted here.

http://xdaforums.com/showthread.php?t=960118
[Fascinate Android Development] drumtrucker:
Thanks, I already got via IRC, but hope someone fixes this access denial issue.
[Fascinate Android Development] id0l:
legit

amazing sweet
[Fascinate Android Development] ignitros:
Forgive me for being a noob but How do I install this new CWM? Do I follow the same instructions from the CWM install thread and flash via ODIN? Any help would be greatly appreciated as I really would like to have my CWM working again with Blackhole
[Fascinate Android Development] Takafiji:
here i go over most things here http://xdaforums.com/showthread.php?t=960118

any problems or questions post em here ot there.
[Fascinate Android Development] vlucchetti:
just installed sc2.6 and when I went into recovery, it was blue. Does not seem this stuck as I had installed it several sc's ago.
[Fascinate Android Development] rivaaaa253:
This is just voodoo lagfix recovery right??
[Fascinate Android Development] Grimis:
So is RM now fixed for the fascinate after your hard work JT? Should we now download the update and flash Clockwork Mod.
[Fascinate Android Development] preymond:
I was wondering the same thing, RM just prompted that i should update to 3.0.0.8... Is this version working?
[Fascinate Android Development] BrwnSuperman:
Is there a cwm version 3 that supports voodoo?
[Fascinate Android Development] jearl75:
This new cwm basically replaces the old green cwm, and can be launched from RM.

If you had red cwm before, you still have it. You can access it the same way. Manual reboot takes you to red, rm takes you to the new orange.

You can also go under advanced in orange and reboot recovery to get to red.

This is how it works for me anyway! Hope it helps
[Fascinate Android Development] Daswolven:
If you're running voodoo it's best to not flash the update unless you do this stuff in your sleep.
[Fascinate Android Development] uslacson1:
Does not seem to be, tried to flash a theme via RM, FAIL!!

Worked on JT's recovery.
[Fascinate Android Development] mkarps:
Love how I see the update in Rom mgr than I sign in and here's a discussion about exactly what I am wondering. You guys rock!
[Fascinate Android Development] BrwnSuperman:
Ah thanks man, I wasn't thinking quite clearly last night.
[Fascinate Android Development] OldManJames:
Thats likely because clockworkmod 3.0 and above no longer supports amend update scripts. (update scripts tell recovery what to do with the zip)

Right now essentially everyone if not everyone in the fascinate community is using amend and not the new edify scripts. So at the moment the new cwm is really only good for backing up and restoring nandroids. It will be functional when everyone that releasing roms, themes, kernels, etc changes to edify which honestly is the better way to go.

I will be switching my 2 themes to edify as soon as I have time to sit down and figure out how it all works.
[Fascinate Android Development] sgtbenny:
I am a newby and was trying to download EB01. I rooted and did everything correct step by step, and I received the same error.

E:cant mouth /dev/block/mmblk1p1 or /dev/block/mmcblk0

(invalid argument)

E:cant mouth /sdcard

The problem is that ROM MANAGER does not work on the Fascinate any longer. You have to Boot in recovery mode manually (hold volume up/down button and power button) not through ROM MANAGER.

When I did this everything worked great. And I have Froyo on my Fascinate.

I did read somewhere today that ROM MANAGER was working again for the Fascinate, but if you are still having the problems then try my suggestion.
[Fascinate Android Development] Maninthemirror:
So I cant get the update to go through, nor can I get superclean 2.6 to flash I get an error on both when it starts to read the zip, Amend scripting is no longer supported. Amend scripting was deprecated by Google in Android 1.5.

Any ideas?
[Fascinate Android Development] HybridByNature:
You have to go into recovery manually and flash it from the SD card. Also, I have a Voodoo kernal but Voodoo was disabled for some reason. So it may be unrelated because I flashing from Ron Manager still doesn't work.

In short: Flash manually from CwM.
[Fascinate Android Development] cabjmb:
Can't you still change the name of the latest red CWR to update.zip and place it on the root of the sd card? Then you would make a copy and change the name to update-recovery.zip and place that in the /sdcard/clockworkmod/ directory? Please someone correct me if the file name to go into the /clockworkmod/ directory is wrong. I don't use RM anymore so I may be remembering wrong... Anyway, this should still be a valid way to use RM to boot into the red CWR, right?
[Fascinate Android Development] jbjarko:
I ended up reflashing RED CWR through Odin and doing away with orange.
[Fascinate Android Development] H3Dude:
CW load via update.zip?

Can I load CWM by changing the name of the file to update.zip
[Fascinate Android Development] :
Alright, so I've been trying to fix this for a couple hours now. I updated to orange a couple days ago, but then used odin to flash this red version yesterday. I also updated to superclean 2.6, but now I can't flash the visual voicemail zip, either through RomManager or manually. When I try, I get the error:

E:Failure at line 2:

copy_dir PACKAGE:system SYSTEM:

Installation aborted.

I've tried re-downloading the file from multiple sources, and I've re-flashed clockworkmod with no luck. Any suggestions? Thanks in advance.
[Fascinate Android Development] RacerXFD:
You sound like what I had on my phone. Try the adrynalyne 2.7.1 fix with the odin file. That eb01 tar should realign your /dbdata partition. Then flash the eom that you want. Make sure you flash as PDA.

Basically, you dbdata position is corrupted. I had to do exactly that to fix.

Also, I don't recommend the orange cwm as it doesn't do everything we need to flash roms.
[Fascinate Android Development] :
Worked like a charm, restored my nandroid backup and everything's working again. Thanks!
[Fascinate Android Development] lane32x:
Clockwork is no longer working for me. Red was working fine until earlier when I made a slight mistake.

Here's the long and short of what happened. I wanted to be able to start installing apps to my SD card, so I told ROM Manager to format my sd. It attempted to reboot into recovery to format my SD and messed everything up. I'm still not sure what it did, but my phone was d-e-d, dead. Stuck me into a boot loop.

I ended up using Odin to re-flash to SuperClean 2.1 using the EBO1SC_DXC.tar.md5 file available...in another thread.

So now my phone is working agian. No problems once I'm booted. The problem is that I no longer have a working CWM.

Now when I boot into the Samsung recovery mode and tell it to apply Update.zip, instead of taking me to ClockworkMod, it takes me to a screen with a Yellow caution sign.

*edit*

I had to delete my Clockworkmod directory on my SD card, and re-flash using the old CWM that I used a month ago. That worked fine.

So I tried updating to the newest version found in the first post and all I get now is a yellow caution sign.

Ideas on how to remedy this?