I guess I don't understand where the problem lies. Is there a miscommunication?
Allow me to explain a little. Our phone is divided into a bunch of partitions. Two of these partitions in question, /dev/block/bml7, and /dev/block/bml8, contain our kernel, and our recovery, respectively.
Now, Odin files work as follows. They go by, not by package name, but internal image name. In this case, zImage is our kernel, and it will ALWAYS flash to bml7, as directed by Odin. There are ways around this, but this is how Odin does it.
Another image, named recovery.bin, contains another kernel, usually a copy, that also contains recovery. By default, its recovery (2e). All recovery images are run off of separate kernels from the main OS, regardless of phone.
The problem with the original cwmrecovery.tar is that it contained a recovery.bin (great), AND a zImage(not so great). I do not know why the kernel was put in there, as it pre-dates any kernel source and as such is a pretty stock kernel.
This kernel is NOT compatible with anything higher than DI01, due to initramfs (script files, etc, that make up the ramdisk).
By removing this zImage, only /dev/block/bml8 flashes, and we dont really care if we have haptic feedback in recovery, right?
As for red clockwork--this is a modification by jt1134 and supercurio, the voodoo maestro. It is meant to be used with voodoo, but supports it, and the stock filesystem. It is also fixed! Green clockwork was left in a poor state after Koush built it, and he has shown no interest in finishing it up. Now there are extra options in red clockwork that will not work unless you have voodoo, etc, but those are in the voodoo and advanced menus, and should not matter.
Now, how I went about making this is on the same principle as before--Odin flashes to a location according to image name. So, I renamed zImage from voodoo5, a version I compiled last month, and renamed it recovery.bin. Red clockwork is contained in the kernel. Then it flashes like always and works, but does not convert to voodoo because the main kernel partition, bml7, has not been flashed. So the voodoo portions remain dormant.
Thats all there is to this. No black magic, no major hacking.
Now, I am going to walk folks through how I did this, testing on my phone (in real time as I type this). Ive also had folks testing in irc with great success. Some do get the update.zip problem, some do not. I dont know the cause of that. Red clockwork does not use update.zip, and rom manager cannot boot to it. You need something like quick boot or do it manually with the 3 button method.
To test
----------
Flashed DL09 Odin back to stock, including recovery.
Booted up, skipped through the setup menu.
I enabled usb debugging, because I am a heavy adb user.
I rebooted to download mode so I could Odin again.
I restarted my odin app. You should NOT use the same instance over and over.
I loaded my cwm package. First, I tried green.
The phone rebooted.
I rebooted to recovery to verify it works (I have update.zip on my sd card)
I have blue recovery (2e). I hitapply sd card: update.zip.
I am in GREEN clockwork. I can stop here, but I like red clockwork better, as it, well, works better.
So I decided to switch to red. You do NOT have to flash green first.
I booted back up.
Then I rebooted to download mode.
I reloaded Odin.
I loaded up my red package, once again in the pda section.
I flashed it.
My phone rebooted, and I then rebooted via adb to test clockwork.
I have RED clockwork.
Now from here I could have rooted myself, but being that I have a nandroid, I loaded up my voodoo kernel, let it convert, then booted back to red cwm and nandroided back.
Ive tested this over and over. I wish I knew where things were going wrong. I've had folks test overand over in IRC too. I am not trying to make this hard on folks, I am trying to make it easier. Notice, I never ocne touched the currently installed kernel until after the fact.
Facebook
Twitter
Instagram