Database Users

How do I get clockwork 2.5.1.2 back when I'm already in ext4? (solved)

So I have been on ext4 for a few days using quantum 2.5. Everything was working as expected there with clockworkmod 2.5.1.0 and 2.5.1.2 installed and available. This morning, I tried flashing the new midnight rom, but my file was corrupted so I went back to Mammon's Bonsai4All 1.0.4 with an ext4 kernel. Now, I can't get back into cwm 2.5.1.2. Bonsai4All should have a working recovery redirect, so I'm guessing I need to reinstall 2.5.1.2. The problem is, I can't flash the prepare.zip to ext4 with 2.5.1.0. So the question is, what do I need to push to the phone to get the modded recovery back? I have the prepare.zip and all other files from the onelickext4 1.3 and I'm not afraid of adb or using the terminal on my phone.

Boot into recovery. Goto advance. Select reboot recovery. That should bring you to v where you wanna be. If it don't then its time to odin
Sent from my SPH-D700 using Tapatalk

If you boot into CWM then go to advanced then reboot recovery that should put you in 2.5.1.2
Beat me to it.

mysteryemotionz said:
Boot into recovery. Goto advance. Select reboot recovery. That should bring you to v where you wanna be. If it don't then its time to odin
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
The problem is, that when I reboot recovery, it brings me back to 2.5.1.0. I have a working phone right now, so I don't feel like using Odin again, yet.
It seems like there should be a way to get the correct recovery back on the phone with the terminal or adb. I've only been using android since October, so it is taking some work to learn how everything is done in the android world. Luckily, I went to school for programming on linux, but I'm a little rusty.

found this tidbit in an the ext4 thread over at ppcgeeks
Please note that until other ROMs add support (namely the new recovery binary in /system/bin/recoveryfiles) I cannot guarantee recovery will function properly
Click to expand...
Click to collapse
So I'm going to try pushing the recovery file from the prepare.zip and see if that works.
edit: It works! I'm getting errors from missing bitmap files, but that should be pretty simple to copy over as well.

Bonsai4All 1.0.4 does not support ext4. I'm surprised your phone even boots, which leads me to believe that you may still be rfs.

DiGi760 said:
found this tidbit in an the ext4 thread over at ppcgeeks
So I'm going to try pushing the recovery file from the prepare.zip and see if that works.
Click to expand...
Click to collapse
Midnight has those files already
Sent from my SPH-D700 using Tapatalk

You could download the QuickBoot app from the Market. Selecting Recovery from within the app automatically boots the phone into Clockwork 2.5.1.2

siphuyoda said:
You could download the QuickBoot app from the Market. Selecting Recovery from within the app automatically boots the phone into Clockwork 2.5.1.2
Click to expand...
Click to collapse
He can't boot up so how would he get a app
Sent from my SPH-D700 using Tapatalk

You all misunderstand.
I can boot just fine. I was on Quantum 2.5 and switched to Bonsai4All 1.0.4, which was pre-ext4. I installed the ext4 kernel at the time of flashing, so the phone works.
No matter how I got into recovery after installing Bonsai4All, it went to 2.5.1.0. That includes using quickboot or reboot recovery from within recovery. And I can't flash anything with 2.5.1.0 since it won't flash to ext 4.
How I fixed it:
1. Remount as rw
2. Copy /system/bin/recoveryfiles/recovery and /system/bin/recoveryres/* from the prepare.zip to my phone.
3. Remount as ro
And voila! Now I can get into 2.5.1.0 and 2.5.1.2.

Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer

I too have epic experience 2.0.07 working with ext4. I actually have the same problem he's having so I'm gonna try his method. It boots up fine and and works but can't get into CW 2.5.1.2. Funny thing is I can still flash zip files through regular CW. Probably because they're not roms. I've checked through adb and and it says I'm using ext4. I can also tell the differance to. My quadrant score is like 1536. I know quadrant it ain't real world but the dev of midnight rom has a video in his blog showing the differance. I'm pretty close to what he got.
Sent from my SPH-D700 using XDA App

musclehead84 said:
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
Click to expand...
Click to collapse
The new Dual Kernel maybe? It bridges the gap between the two file systems.

musclehead84 said:
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
Click to expand...
Click to collapse
You can make other DK28 roms work with ext4 by flashing an ext4 compatible kernel after flashing the rom. If I had just tried to flash bonsai without an ext4 compatible kernel, it would freeze at the samsung screen and I would have to Odin out of it. I made that mistake once already when I stopped paying attention to what I was doing.

It says (solved) but I don't see the solution. guess that means I'm still an android n00b.
Stuck at SAMSUNG screen (Help!)
I had CWM3 and EXT4
I flashed Quantum Rom 2.7
tried to flash Nebula Rom 1.6 but it didn't take cuz of EXT4
I flashed ReRFS.Format.ROM.DK28-signed.zip to bring me back to RFS
reboot - hangs at SAMSUNG splash
reboot back into recovery, now 2.5.1.0
tried flashing Nebula Rom 1.6 - but reboot still hangs at SAMSUNG
tried flashing Quantum Rom 2.7 - but reboot still hangs at SAMSUNG
tried Odin, but I don't know what to do with Odin except flash the DK28 modem, so I did that, but it didn't help
so I'm basically trying a bunch of crap without knowing what I am doing, and as fun as this is - I'm kinda stuck - just going in circles

plus I keep seeing "E:can't open /cache/recovery/log" while in ClockworkMod Recovery 2.5.1.0 - and when I do the Reboot Recovery as people have said to make it go to 2.5.1.2, it still just hangs at the SAMSUNG splash...

I found SPH-D700-DK28-8G-REL.tar.md5 and flashed that and now I'm back in business - **phew**

Cobaltikus said:
It says (solved) but I don't see the solution. guess that means I'm still an android n00b.
Stuck at SAMSUNG screen (Help!)
I had CWM3 and EXT4
I flashed Quantum Rom 2.7
tried to flash Nebula Rom 1.6 but it didn't take cuz of EXT4
I flashed ReRFS.Format.ROM.DK28-signed.zip to bring me back to RFS
reboot - hangs at SAMSUNG splash
reboot back into recovery, now 2.5.1.0
tried flashing Nebula Rom 1.6 - but reboot still hangs at SAMSUNG
tried flashing Quantum Rom 2.7 - but reboot still hangs at SAMSUNG
tried Odin, but I don't know what to do with Odin except flash the DK28 modem, so I did that, but it didn't help
so I'm basically trying a bunch of crap without knowing what I am doing, and as fun as this is - I'm kinda stuck - just going in circles
Click to expand...
Click to collapse
Clarification on how I solved my problem is below. I had a usable phone the entire time, I just didn't have the cwm I needed.
It almost sounds like a your problem is a kernel issue, except you have it with so many roms. There may have been an error in the file system conversion somewhere that is causing you trouble. You don't usually get the "E: can't do whatever" error if your cwm is compatible with your file system.
My suggestion to you would be to Odin back to a good image. You do it basically the same as doing the modem. Uncheck everything on the left. Put your .pit in the pit section. Put your .tar file (or .tar.md5) into the box that says pda (the first box). Then, plug your phone in and flash.
After that, you can run the one-click root and recovery to get root and cwm 2.5.1.0 back. Then you can start playing again. Remember, if you use ext4 then you must have an ext4 compatible kernel. If you use rfs, you must use an rfs compatible kernel. You can use any rom on ext4 if you flash an ext4 kernel immediately after you flash the rom and before you reboot the phone. If you forget to do the kernel, you will hang at the samsung screen. Some roms are ext4 or rfs only, and some have a dual file system kernel. Currently, you can mix and match any dk28 kernel with any dk28 rom. Don't try to mix kernels and roms from different builds, though.
Now for further clarification on how I got 2.5.1.2 back when using a rom that didn't have it baked in:
DiGi760 said:
How I fixed it:
1. Remount as rw
2. Copy /system/bin/recoveryfiles/recovery and /system/bin/recoveryres/* from the prepare.zip to my phone.
3. Remount as ro
And voila! Now I can get into 2.5.1.0 and 2.5.1.2.
Click to expand...
Click to collapse
I guess my solution was about as clear as mud. In order to do this, it helps to be somewhat comfortable using a command line.
I used the prepare.zip that was a part of the original ext4 conversion to get the recovery files. When you open the prepare.zip it has the standard flashable zip structure and is organized according to where the files are supposed to end up on your phone. Open the zip, open the system folder, open the bin folder and copy the folder named "recoveryres" to your sd card. Then open the "recoveryfiles" folder and copy a file named "recovery" to your card as well. Put these files somewhere easy to find, like a folder named "cwm" at the root of your card.
Next, use a terminal emulator to remount your phone to rw so you can write to the protected areas. Most of our roms included a small remount script, so all you have to do is type "remount rw" without the quotes. Later you will use "remount ro" to make things read only again.
Now, you're going to copy those files that you got from the prepare.zip to their proper places on your phone. You did leave them somewhere easy to find, right?
Copy "recovery" to /system/bin/recoveryfiles/ and copy the "recoveryres" folder to /system/bin/. You may have to watch and make sure it doesn't skip any files when copying the recoveryres folder.
After that, remount ro and you are done.

Lost Clockwork Mod Recovery :(

Hey all,
I have got root permissions on my Samsung Galaxy S and also have ROM Manager installed but when I click boot into Clockwork Mod Recovery it just boots up the standard Android Recovery and shows the E: signature verfication failed etc which means I cannot flash to another ROM or anything?
It used to work but for some reason since installing a new custom ROM it does not anymore? Please help
Phone Details:
Model number - GT-I9000
Firmware version - 2.2
Baseband version - I9000XXJPY
Kernel version - 2.6.32.9 hardcore 'at' speedmod-k11a-256hz #50
Build number - FROYO.XXJPO

Tried downloading and installing a new copy of CWM .
jje

I have the same problem. If I try booting into recovery via the ROM Manager app, I get the original 3e recovery. However, if I try entering recovery directly (power off, hold vol up, home and power at the same time), I get into Clockwork Recovery every time.
I have the latest ROM Manager installed so I don't know why this is happening but it doesn't really affect me so I've not investigated further.
[edit] I'm only saying that I have the same problem because we're both running a speedmod kernel (albeit different versions) which installs a modified recovery to "fix" the 3e recovery issue.

Hello Both,
Yep I have tried installing it again JJEgan but no luck
I can't even boot into CWM recovery with the 3 button method because my phone doesn't support the 3 button thing - another gripe I have

Swatto86 said:
Hello Both,
Yep I have tried installing it again JJEgan but no luck
I can't even boot into CWM recovery with the 3 button method because my phone doesn't support the 3 button thing - another gripe I have
Click to expand...
Click to collapse
Ummm. Before doing ANYTHING, why not proceed to fixing the 3-button issue? There's a thread pinned to every i9000 forum for a reason.
I'm guessing (don't know for sure) that you might have to reflash the kernel afterward to resolve the 3e recovery if it's placed back on your phone.

flash clockwordmod recovery from rom manager. it will create a "update.zip" file on your internal card. then reboot into normal recovery and apply update.zip twice, there you are
Swatto86 said:
Hey all,
I have got root permissions on my Samsung Galaxy S and also have ROM Manager installed but when I click boot into Clockwork Mod Recovery it just boots up the standard Android Recovery and shows the E: signature verfication failed etc which means I cannot flash to another ROM or anything?
It used to work but for some reason since installing a new custom ROM it does not anymore? Please help
Phone Details:
Model number - GT-I9000
Firmware version - 2.2
Baseband version - I9000XXJPY
Kernel version - 2.6.32.9 hardcore 'at' speedmod-k11a-256hz #50
Build number - FROYO.XXJPO
Click to expand...
Click to collapse

behemot24 said:
flash clockwordmod recovery from rom manager. it will create a "update.zip" file on your internal card. then reboot into normal recovery and apply update.zip twice, there you are
Click to expand...
Click to collapse
no you are wrong.. the signature failed is because you are not using 2e recovery but 3e (2e is lost when flashing to froyo).. you will need to restore 2e recovery with a custom kernel or custom rom.. search and read up on it and dont comment if you dont know what you are talking about.
recommend chainfire cf kernel to restore 2e recovery.

yub, what lgkahn said.
you need to flash a different kernel.
lots of ppl recommend hardcore's speedmod too, but try a few different ones and see which you like

I have the same problem. Can't get into clockwork recovery, instead it boot into Samsung 2e..

gtg2 said:
I have the same problem. If I try booting into recovery via the ROM Manager app, I get the original 3e recovery. However, if I try entering recovery directly (power off, hold vol up, home and power at the same time), I get into Clockwork Recovery every time.
I have the latest ROM Manager installed so I don't know why this is happening but it doesn't really affect me so I've not investigated further.
[edit] I'm only saying that I have the same problem because we're both running a speedmod kernel (albeit different versions) which installs a modified recovery to "fix" the 3e recovery issue.
Click to expand...
Click to collapse
not me. the same "Android system recovery <3e>" and
E:failed to verify whole-file signature
E:signature verification failed
...hen trying to apply update.zip
Saw the post about losing 2e when flashing to froyo. Thanks for that, I won't bother trying to fix it any more. Do You think there's going to be an update supporting 3e ?

iv got same problem but u need 2erwcovery which im trying to get

Try this, works perfectly on my Galaxy S

[RECOVERY] 3e Recovery Modded w/ No Verification

NOTE
This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://forum.xda-developers.com/showthread.php?t=833423)
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**

Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.

designgears said:
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
Click to expand...
Click to collapse
I done the exact method above and works fine for me...
Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others

sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.
Thanks
Sent from my SGH-I897 using XDA App

If you look at Darkyy's rom he has a script that does this.

Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.

Tested and works with Rogers 2.2 Rom. Thanks

skorchir said:
Tested and works with Rogers 2.2 Rom. Thanks
Click to expand...
Click to collapse
I also have.
Thanks

Works great on Rogers 2.2. Thanks

I tested it on Galaxy S i9000m bell and it work A+
i do not have to flash cf-boot to make unsigned zip to be installed
thanks a lot for your hard work.
only thing is botton function become different then original 3e
but its working A+

I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.
Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.

I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.

Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.

davidis57 said:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
Click to expand...
Click to collapse
Use a terminal emulator or adb shell and type...
Code:
chmod 777 /system/bin/recovery
That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.

Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?

Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'
I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.
Thanks for this!

Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?

davidis57 said:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
Click to expand...
Click to collapse
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
Sent from my SGH-I897 using XDA App

It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App

davidis57 said:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works

Help - Clockworkmod Recovery

I'm trying to flash a custom rom made from romkitchen however have hit a wall. Any help pointing out a solution or where i may have gone wrong would be most appreciated. I'll outline all the steps i took, not sure if they are related to the issue or not.
I started of with froyo dtjp5 with no 3 button and 3e recovery. I started by using odin to flash the canadian bootloader fix which worked perfectly and gave me 3 button download mode. I then flashed chainfire cf-root 1.3 kernell which also worked perfectly and i know have working 2e recovery mode. I then donwloaded clockwork rom manager form the app market, and flashed the clockworkmod recover 2.5.1.2. It appeared to be successful. However when i attempt to enter recovery mode, either through the application, or through 3 button mode it, simply boots into normal 2e recovery mode rather than clockwork mod. I have tried applying the flash again but it still did not work.Untill i can boot into clockworkmod recovery i cant apply my romkitchen zip file so im kind of stuck. I must be missing something but cant figure it out, so once again any held would be much appreciated. Thanks

flash for example voodoo or speedmod kernel with odin/heimdall or kernel flasher(haven't used it often so i am not sure about kernel flasher)
Sent from my GT-I9000 using Tapatalk

Make sure CWM is set as update.zip on your sdcard - ROM Manager should actually do this for you - then in 2e recovery select flash update.zip ... the very first time it should just reboot your device (so go into recovery again), the second time it should start CWM.
Not sure why CWM is built that way.

Thanks very much

Ok so I am having a problem with cwm that i hope someone can help me with. I just flashed the latest speedmod kernel using the sgs kernel flasher app. Now when i try to reboot into recovery from cwm so that i can access the tweaks menu, the cwm options dont appear. It says i am in android sytem recovery(3e). where my only real option besides wiping the phone is to apply sdcard:update.zip, which does not work even though cwm is set as update.zip on my sd card. Any help to this noob would be appreciated.

Cap18k said:
Ok so I am having a problem with cwm that i hope someone can help me with. I just flashed the latest speedmod kernel using the sgs kernel flasher app. Now when i try to reboot into recovery from cwm so that i can access the tweaks menu, the cwm options dont appear. It says i am in android sytem recovery(3e). where my only real option besides wiping the phone is to apply sdcard:update.zip, which does not work even though cwm is set as update.zip on my sd card. Any help to this noob would be appreciated.
Click to expand...
Click to collapse
to apply CWM from 3e recovery you need it on your sd card. it has to be named 'update.zip'
the other way to do this, is download odin version, boot into download mode, and flash.
overall process takes less than 5 mins.

Check if you really have it -> settings -> about phone.
And try to flash it using odin, that worked flawlesly for me.
Sent from my GT-I9000 using Tapatalk

The kernel definately flashed correctly. I am not sure why the update.zip isnt workingfro cwm (the signature verification keeps failing), but i am going to try odin and see what happens. I've never used it before, but i am downloading it now.

[Solved] For the life in me I cannot seem to get the ROM Manager to work right

Hi all,
I would love to be able to do a ROM backup of my SGS2, but I kept getting the "Verification Failed Error".
This is what I have done so far:
1. CF-Root KF1 v4.0
2. Stock Kernel KF1 (to rid of yellow triangle)
3. Installed bmarko82 & muveszur's ROM, which works beautifully
4. Installed ROM Manager, flashed CWM Recovery and rebooted
5. Ran ROM Manager, attempted to "Backup Current ROM" and rebooted into "Recovery mode"
6. That is where it stopped and showed the error messages
Am I missing a step?

If i remember reading correctly ROM Manager has issues with the CF Kernal, i think they have incompatibles which CF has said would need to be fixed app end not kernal end.

do you have an app called CWM? it works like rom manager but works with cf-root.

kubia said:
do you have an app called CWM? it works like rom manager but works with cf-root.
Click to expand...
Click to collapse
This is what I have:
CWM Manager v1.80
Current Kernel: CF-Root 4.0
ROM Manager v4.3.2.3
I have done everything by the book.

Try the developer .
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
jje

I am no expert but, i i remember reading the cfroot topic that it is not compatible with rom manager , that is why it includes the app CWM...

So from what I understand, here is your issue. With Samsung phones, the recovery and kernel are packaged together as one. That's why in the codeworkx thread, there's a kernel in there that's needed for compatible interaction with ROM Manager. You can also flash the recovery portion through ROM Manager itself, but I believe you need the kernel in order for it to fully work.
If you're using CF Root, it comes w/ CWM as others have mentioned. To paraphrase CF, his custom-built CWM essentially fixes a few things that CF finds annoying with the stock CWM: Home button works as an enter key, it supports the external SD card, etc. Koush said those things would never make it into the stock CWM as it would fragment the code. (Stock CWM treats the internal space as the SD card, which would leave no place for the actual external SD card to mount).
Here's what I recommend: If you want to use CF Root, stick with the CWM app that CF built. CF Root works just fine w/ the Tegrak OC module loading. If you want to use ROM Manager, load the kernel that codeworkx has packaged with his thread and plan to use SetCPU if you want to do any overclocking. Both are valid options and both will give you what you want: CWM backup, OC capabilities and CWM flashing.
Hopefully this helps!

slyydrr said:
Here's what I recommend: If you want to use CF Root, stick with the CWM app that CF built. ......................
Click to expand...
Click to collapse
+1
You can easily backup from CWM or Nandroid in Recovery.

Thanks everyone for their help and the suggestion from slyydrr helps.
Thanks again.