I converted my Legendary 2.2 backup to MTD, and it's been running pretty smoothely. But today... I tried to backup my ROM from rom manager and I got an error, when it was backing up the boot img. It backs up just fine if I back it up directly from recovery, but I noticed that inside the backup folder, all the files I had to rename from ext4 extensions to yaffs2 are just image files now. Sooo, I'm a bit unsure the backup will work if I try to restore them and I'm a bit sketched to try it out.
Can anyone help me out with what's going on here?
xLoveHateLegend said:
I converted my Legendary 2.2 backup to MTD, and it's been running pretty smoothely. But today... I tried to backup my ROM from rom manager and I got an error, when it was backing up the boot img. It backs up just fine if I back it up directly from recovery, but I noticed that inside the backup folder, all the files I had to rename from ext4 extensions to yaffs2 are just image files now. Sooo, I'm a bit unsure the backup will work if I try to restore them and I'm a bit sketched to try it out.
Can anyone help me out with what's going on here?
Click to expand...
Click to collapse
Did you change ROM Manager for MTD use? There was lots of posts about this. You need to hit menu in ROM Manager, pick Manual Flash Overide, Epic-MTD and clockwork 3.x.x.x. The CWM installed when you converted to MTD is special and needs to be the only one used. Do not flash another recovery while on MTD. If you do you will have to convert again to get it.
I have not changed ROM Manager for MTD use. Someone told me to convert it, but when I click Manual Flash Override, it asks me if I'm having trouble flashing the recovery with rom manager, but whether I click ok or cancel, it doesn't really do anything. I don't see anything about MTD in rom manager.
xLoveHateLegend said:
I have not changed ROM Manager for MTD use. Someone told me to convert it, but when I click Manual Flash Override, it asks me if I'm having trouble flashing the recovery with rom manager, but whether I click ok or cancel, it doesn't really do anything. I don't see anything about MTD in rom manager.
Click to expand...
Click to collapse
You are supposed to click OK and a screen will pop right up with 3 Epic choices. Pick Epic-MTD and the clockwork 3.x.x.x then it will use the correct MTD clockwork installed. If this don't work your ROM Manager is bad. Uninstall and reinstall. If you still can't get it working you will have to not use it and 3 finger to CWM.
Sent from my SPH-D700 using XDA App
You Save my Rom Manager =)
kennyglass123 said:
You are supposed to click OK and a screen will pop right up with 3 Epic choices. Pick Epic-MTD and the clockwork 3.x.x.x then it will use the correct MTD clockwork installed. If this don't work your ROM Manager is bad. Uninstall and reinstall. If you still can't get it working you will have to not use it and 3 finger to CWM.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thank You very much Sir KennyGlass123.
I had this same dreaded error backing up the boot img when I upgrade to CM9 Beta 3 and used Rom Mananger 5.0.0.7 BackUp Rom option in app then it would reboot to CMW 5.0.2.7 and fail to do a backup.
The only way I was avoiding this error was to do a reboot to recovery in power options or do the 3 finger CMW then back Up would work ok. But I was annoyed about this error and how before in early FC09 & EL30 roms I had not experienced this.
I recently was with CleanGB 1.1.2 BML Rom but decided to go for MTD format. I flashed the CleanGB 1.1.2 MTD rom then tried out a bunch of other great epic 4g MTD roms while backing each before installing another and finally landed to CM9. After updating kernel and updating to CM9 pre4 I started to backup my CM9 b3 and found out I was herbed.
Not until I read your posts and followed your recommendations that it totally fixed this error in Rom Mananger. Now I have both ways to back up my current rom either using Rom Manager Back Up Rom option that kicks me to CMW or 3 finger salute, lol...
XDA is the gift that keeps on giving...
Thank You for xmas everyday with new roms and themes and great info.
Lanboy =)
Related
I'm looking for CW 2.5.0.1(?) so I can flash radio and other files. It seems like 3.x "aborts" install with some files.
I have not been able to find the 2.5.x CW img for the Evo. Also, now that my phone is crippled (flashed a new ROM), how do I install the 2.5.x over the 3.x? ROM Manager does not give me the option to flash back to 2.5.x
Thanks for any quick help!
BTW, I'm not using RA because it doesn't seem to allow me to navigate the SD directory to chose files to flash. If there is something I'm missing, let me know.
Edit:
See post #7 below, it contains the file to get you back to 2.5.0.1!!
snovvman said:
I'm looking for CW 2.5.0.1(?) so I can flash radio and other files. It seems like 3.x "aborts" install with some files.
I have not been able to find the 2.5.x CW img for the Evo. Also, now that my phone is crippled (flashed a new ROM), how do I install the 2.5.x over the 3.x? ROM Manager does not give me the option to flash back to 2.5.x
I believe that the new clockwork is causing problems for a lot of people, myself included. I cant revert to an old clockwork like 2.5 either. I just had to flash RA 1.8 on my phone and my wife's Evo.
Click to expand...
Click to collapse
Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.
Justin.G11 said:
Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.
Click to expand...
Click to collapse
For some reason that method isn't working for a lot of people, myself included. The thing that is working is to flash RA 1.8
I tried several times to revert to an old clockwork and kept getting an error.
go here... http://www.clockworkmod.com/download/recoveries/
click the supersonic recovery you want... make sure its the .zip file.
put on ur SD card and flash. hope this helps
Justin.G11 said:
Rom manager has an option at the very bottom called "all clockwork recoveries"... Use that and select whatever build you want.
Sent from my pants. You figure out how I typed it.
Click to expand...
Click to collapse
cbond007 said:
For some reason that method isn't working for a lot of people, myself included. The thing that is working is to flash RA 1.8
I tried several times to revert to an old clockwork and kept getting an error.
Click to expand...
Click to collapse
Correct, the older versions in ROM Manager do not work for the Evo.
I ended up finding a pc36img.zip and flashed it. I am now back to 2.5.0.1. I don't use RA because I can't select files. It's a pain when I have a lot of files to flash.
Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Edit: Some additional info to save you some searching:
Make sure you flash using bootloader and NOT your current recovery. Power off, hold Vol Down, and Power On. Let it update the image, then reboot into recovery again. At that point, you should see 2.5.0.1.
ROM Manager does not properly downgrade. 2.5.1.4/3, I have been told, is not for Evo. You will need to flash manully as I described.
snovvman said:
It seems like 3.x "aborts" install with some files.
Click to expand...
Click to collapse
There's a more sinister problem with 3.0.0.1 (which appears to have now been retracted, as ROM Manager, after updating me to 3.0.0.1, is now showing "Latest Recovery: 3.0.0.0" at the time I write this).
It's only sheer chance that I had another unrelated problem, or I would have been screwed -- the Nandroid backup is broken in 3.0.0.1 (it completed the backup operation within about 2-3 seconds, clearly not having backed up everything!)
Edit: I checked in the backup directory, and the only files backed up by 3.0.0.1 were boot.img and recovery.img
Now that I reverted to 3.0.0.0, at least the backup takes a good long time and seems to be listing all the usual stuff, but I don't feel that I can trust 3.0 now.
I'm going back to what was working for me a couple of days ago (2.5.1.2) when I tried CyanogenMod (6.1.1) for the first time. ROM Manager and ClockworkMod Recovery handled it all so perfectly that I kicked it off with checkboxes enabled for the "back it up" and "wipe" options, got called away for about 1/2 hour, and when I returned, there was CM6 in all its beauty, even including the Google apps.
Is there an "official" place to report bugs for ClockworkMod Recovery? I noticed that the clockworkmod.com web site has gone poof (Google cache shows it intact on Dec 11th).
--tgi
HTC Supersonic / Sprint EVO 4G / Hardware 002
myn's Rooted Froyo 2.2 3.29.651.5 Radio 2.15.00.09.01 Kernel 2.6.32-ge2fb08e [email protected] #11
I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.
tgi007 said:
There's a more sinister problem with 3.0.0.1 (which appears to have now been retracted, as ROM Manager, after updating me to 3.0.0.1, is now showing "Latest Recovery: 3.0.0.0" at the time I write this).
[/COLOR]
Click to expand...
Click to collapse
When ROM Manager prompted me to update tonight, I got 3.0.0.2. I was able to complete a backup, including the WiMax partition. Going back to the advanced restore menu, I was given the option to backup WiMax and other partitions seperately.
Does flashing work properly now?
At this point I'm afraid to try.
Product F(RED) said:
Does flashing work properly now?
Click to expand...
Click to collapse
Flashing works just fine with 2.5.0.1.
snovvman said:
Flashing works just fine with 2.5.0.1.
Click to expand...
Click to collapse
+1
.......
snovvman said:
Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Click to expand...
Click to collapse
I have a Root folder I made in sd card and put the image file in folder in bootloader now its not reading it. what to do?
Edit: I figured it out and works perfect!! Thanks Button..
Product F(RED) said:
I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.
Click to expand...
Click to collapse
+1 on this I will have to admit other than folder search I see nothing better about CW over AR and AR has great wiping features and usb mode. But to each its own...
Product F(RED) said:
I'm sorry, but as an AR Recovery user, I see no reason to switch to Clockwork other than being able to browse folders other than the root of your memory card for ZIPs. AR seems much more stable and has had all of the features (except that one) that CW recently had added.
Click to expand...
Click to collapse
playya said:
+1 on this I will have to admit other than folder search I see nothing better about CW over AR and AR has great wiping features and usb mode. But to each its own...
Click to expand...
Click to collapse
Question for yoru guys: When you flash with RA (/AR), do you just rename the file and put it into the root of SD each time? Is there an easier way to flash with RA that I am not aware of?
snovvman said:
Here is the Clockwork 2.5.0.1, packaged flashable.
Put it in the root of your SD, boot into bootloader, let it update, and life is good again...
Click to expand...
Click to collapse
I tried this it says it runs the recovery but after I reboot and run rom manager it says clockworkmod 3.0.0.2. Am I missing a step?
snovvman said:
Question for yoru guys: When you flash with RA (/AR), do you just rename the file and put it into the root of SD each time? Is there an easier way to flash with RA that I am not aware of?
Click to expand...
Click to collapse
Not defending CW, but it does have USB Mode. It's just tucked away in the menu.
If I'm on my PC, I download and then just drag to the phone or I use Dropbox, then Astro to move it to the root. If I'm not, then I use Astro. I don't have to rename anything.
ARG! I flashed 2.5.0.1 and still non of my old backups work they all hang at the white htc boot screen. I am just booting into recovery and running restore should I be doing something first?
[Q] Help flashing [ROM]Bonsai4All EXT4/Clockworks 3.0.0.5 support V2.0.1 >02/03/2011
Ok guys, im gonna attempt a flash([ROM]Bonsai4All EXT4/Clockworks 3.0.0.5 support V2.0.1 >02/03/2011) today on my friends samsung epic 4g which is fully stock at the moment, i already have read the instructions but i need a little guidance in the right direction. I have flashed clockworkmodrecovery using
http://http://forum.xda-developers.com/showthread.php?t=782300
& http://http://forum.xda-developers.com/showthread.php?p=7933592#post7933592
so now i can boot into clockworkmod recovery, but b4 i flash anything im going to do a backup through the clockworkmod recovery, i read in the Bonsai4All thread that i need to "Odin the dk28 modem first", can someone tell me how i can do that, like give me a link to the required files and how i would go about installing them. Also is there anything else that i am not doing that is required to flash to the Bonsai4All ROM from a stock samsung epic 4g , all feedback is greatly appreciated, thanks in advance guys.
This is the Epic wiki. Scroll down to Odin Stock Flashing and follow those instructions. Under Official Roms (just above Odin Stock Flashing) is the dk28 file. It's titled 'SPH-D700-DK28-8Gb-REL.tar.md5 Stock DK28 (Leaked).' That's what you put in Odin to flash to stock dk28. Scroll down further to Community Roms and you will see the Bonsai4All rom. Once you are on stock dk28, have cwm3 installed, and download the Bonsai rom to the SDcard, you can flash Bonsai through cwm.
running_the_dream said:
This is the Epic wiki. Scroll down to Odin Stock Flashing and follow those instructions. Under Official Roms (just above Odin Stock Flashing) is the dk28 file. It's titled 'SPH-D700-DK28-8Gb-REL.tar.md5 Stock DK28 (Leaked).' That's what you put in Odin to flash to stock dk28. Scroll down further to Community Roms and you will see the Bonsai4All rom. Once you are on stock dk28, have cwm3 installed, and download the Bonsai rom to the SDcard, you can flash Bonsai through cwm.
Click to expand...
Click to collapse
The wiki says I have to "Select the victory_8G_100528.pit on the right in the pit section" on step number 4, do I have to do that to flash to Bonsai, or do I just do what you told me.
Sent From my
HTC GLACIER USING XDA APP
HTC GLACIER PERMA-ROOTED S-OFF
CM7 NIGHTLIE
OC TO 1.5GHz
kdunn1994 said:
The wiki says I have to "Select the victory_8G_100528.pit on the right in the pit section" on step number 4, do I have to do that to flash to Bonsai, or do I just do what you told me.
Click to expand...
Click to collapse
When I flashed to stock dk28 , I used the Victory pit along with the SPH-D700-DK28.tar. So, I would do both.
I have used it without victory BUT I was already on dk28. I had a 2.2 rom and I was flashing back to stock dk28.
So, final answer, for the first time going to dk28, I would use both the pit and tar.
On a side note, make sure only the reset time and auto-reboot check boxed are checked. There shoud be three total check boxes. For the first time, only check those. If you install a rom and want to go back to stock dk28 in the future, then only check auto-reboot.
So basically what you're saying. Is all that I really need to do is substitute the dk28 tar u told me instead of the one used on step 5?
Sent From my
HTC GLACIER USING XDA APP
HTC GLACIER PERMA-ROOTED S-OFF
CM7 NIGHTLIE
OC TO 1.5GHz
kdunn1994 said:
So basically what you're saying. Is all that I really need to do is substitute the dk28 tar u told me instead of the one used on step 5?
Click to expand...
Click to collapse
You got it.
Nice ill give it a try when I get out of school.
Sent From my
HTC GLACIER USING XDA APP
HTC GLACIER PERMA-ROOTED S-OFF
CM7 NIGHTLIE
OC TO 1.5GHz
ok, one more question before i begin is, do i backup with clockworkmodrecovery before i flash dk28, or if im correct the flash will delete everything including root, and upgrade the phone to 2.2, so the backup would be irrelevant until b4 i flash the bonasi?
kdunn1994 said:
ok, one more question before i begin is, do i backup with clockworkmodrecovery before i flash dk28, or if im correct the flash will delete everything including root, and upgrade the phone to 2.2, so the backup would be irrelevant until b4 i flash the bonasi?
Click to expand...
Click to collapse
Yes, using flash with ODIN will erase everything including root. So, backup everything before you start. It should backup to your SDcard. When you do the stock flash, root, install cwm3 and flash your 2.2 based rom, you should be able to boot into cwm, go to backup/restore- advanced restore and restore data.
I would install My Backup or something similar before attempting though. Just in case cwm doesn't keep your backup after the flash. It's worked for me in the past. After backup, you can also move the backup file to your computer's hard drive for safekeeping. It's in the root of the sd folder under Clockwork recovery.
thumbs up picking bonsai rom. ive tried midnight, viper, nebula already and none of them even compare to the speeds of bonsai. if your going for speed and no force closes choose bonsai.
to kind of answer your question, always backup, it wont hurt anything.
running_the_dream said:
Yes, using flash with ODIN will erase everything including root. So, backup everything before you start. It should backup to your SDcard. When you do the stock flash, root, install cwm3 and flash your 2.2 based rom, you should be able to boot into cwm, go to backup/restore- advanced restore and restore data.
I would install My Backup or something similar before attempting though. Just in case cwm doesn't keep your backup after the flash. It's worked for me in the past. After backup, you can also move the backup file to your computer's hard drive for safekeeping. It's in the root of the sd folder under Clockwork recovery.
Click to expand...
Click to collapse
ok, thanks, i think i got the steps down, after i have this installed, i root it using(insert link and awesome advice here)?
I'm on my phone now so I can't see the links and so forth. I think the bonsai rom will install root, cwm, convert to ext 4 file system and install bonsai. Double check the rom thread though. If not, theres a one-click root w/ cwm3 in the dev section
running_the_dream said:
I'm on my phone now so I can't see the links and so forth. I think the bonsai rom will install root, cwm, convert to ext 4 file system and install bonsai. Double check the rom thread though. If not, theres a one-click root w/ cwm3 in the dev section
Click to expand...
Click to collapse
So everything worked out great, and it was much easier than i thought, all i needed was some guidance in the right direction and you gave me that "running_the_dream" and for that i can not emphasize enough how much Thanks i have for you, i really appreciate the help, thanks for all the support
kdunn1994 said:
So everything worked out great, and it was much easier than i thought, all i needed was some guidance in the right direction and you gave me that "running_the_dream" and for that i can not emphasize enough how much Thanks i have for you, i really appreciate the help, thanks for all the support
Click to expand...
Click to collapse
Great! Enjoy!
I have EC05 right now. Yesterday I flashed to ACS MIUI and it seems to work fine. Today I try to upgrade to EI22 with CWM 5.0.2.7 using modem.EC05toEI22.zip, but I get an error every time:
Updating modem to EI22...
script aborted (no error message)E:Error in /sdcard/firmware/modem.EC05toEI22.zip
(Status 7)
Installation aborted.
I tried re-downloading the file multiple times from different sources and I keep getting this error. What am I doing wrong?
Just had someone had a similiar issue with a modem.... can you odin back to stock ec05 and it completely flash everything?
It could be a hardware problem if your unable to flash back to stock ec05 and it gets stuck at modem.bin
Otherwise I'm sure someone else knows why its not flashing right... oh and have you tried flashing an alternative recovery possibly acs recovery5 its better. One more thing are you flashing from rom managers boot to recovery or your 3 finger salute?
Sent from my OG Epic
I odined back to stock EC05 then ota'd to EI22. Except now after I rooted and installed clockwork mod I can't boot into clockwork mod, I can only get into android system recovery, which I can't install a custom rom from. I have tried installing ACS CWM and the latest official CWM via odin and I still can't boot into anything but regular android system recovery using the three finger boot.
What is wrong now?
jagothejago said:
I odined back to stock EC05 then ota'd to EI22. Except now after I rooted and installed clockwork mod I can't boot into clockwork mod, I can only get into android system recovery, which I can't install a custom rom from. I have tried installing ACS CWM and the latest official CWM via odin and I still can't boot into anything but regular android system recovery using the three finger boot.
What is wrong now?
Click to expand...
Click to collapse
Samsung put a code into the kernel that reboots the original recovery mode every reboot. Download a custom kernel (which will overwrite this setting.) I recommend nebernal for this as it will work on rfs and I don't know if the others will... there is a qbking vid to properly root on ei22 if this is confusing you... Odin the cwm .tar and DON'T have auto reboot checked. After flashing cwm pull battery and reboot into recovery via the 3 finger method... now flash that kernel I told you to download and boom you now have a cwm tha sticks after reboot!!! Now you can flash whatever rom you would like... btw for future reference I'm pretty sure you have to mount/system in cwm when flashing anything from the new miui and cm roms because of the new mtd partition...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Samsung put a code into the kernel that reboots the original recovery mode every reboot. Download a custom kernel (which will overwrite this setting.) I recommend nebernal for this as it will work on rfs and I don't know if the others will... there is a qbking vid to properly root on ei22 if this is confusing you... Odin the cwm .tar and DON'T have auto reboot checked. After flashing cwm pull battery and reboot into recovery via the 3 finger method... now flash that kernel I told you to download and boom you now have a cwm tha sticks after reboot!!! Now you can flash whatever rom you would like... btw for future reference I'm pretty sure you have to mount/system in cwm when flashing anything from the new miui and cm roms because of the new mtd partition...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks! I will give it a shot tonight. Can you please explain for a noob what you meant by "btw for future reference I'm pretty sure you have to mount/system in cwm when flashing anything from the new miui and cm roms because of the new mtd partition..." ?
jagothejago said:
Thanks! I will give it a shot tonight. Can you please explain for a noob what you meant by "btw for future reference I'm pretty sure you have to mount/system in cwm when flashing anything from the new miui and cm roms because of the new mtd partition..." ?
Click to expand...
Click to collapse
Not sure if this entirely right but with the new partition or reserved memory space the system needs to mounted in order for anything affecting or changing the system to work properly. However to do so its in mounts and storage you'd need to go to mount /system in cwm and then try flashing the ec05toei22.zip then it should work.
Sent from my OG Epic
Anyone having problems with their CWR sticking? I have to reflash every time before i reboot or i get the sad android w/ his red triangle I have LTE ver. on stock android 4.02
Did you try renaming system/recovery-from-boot.p?
Sent from my Galaxy Nexus using Tapatalk
Edit: didn't work for me either. If i press keys from the sad Android i reboot into safe mode and then reboot from rom into odin mode.
I'm not all that familiar with cwm, my last device used amon-ra recovery.
I believe if you have a stock ROM, CWM won't stick because the stock ROM will "fix" the recovery partition.
TaFFeR said:
I believe if you have a stock ROM, CWM won't stick because the stock ROM will "fix" the recovery partition.
Click to expand...
Click to collapse
Not if you delete the "recovery-from-boot.p" file. Should skip right past that.
I had this same thing happen after I first unlocked/rooted, but then I deleted the file, re-install CWM through Rom Manager, and it works perfectly now.
hotleadsingerguy said:
Not if you delete the "recovery-from-boot.p" file. Should skip right past that.
I had this same thing happen after I first unlocked/rooted, but then I deleted the file, re-install CWM through Rom Manager, and it works perfectly now.
Click to expand...
Click to collapse
Yup, same here. I used the toolkit, though. Basically, flashed CWM, deleted the recovery-from-boot.p file, then flashed CWM again.
I had this very issue when I first rooted. What I did was I made sure I had a ROM (I used Revolution at the time) and once I flashed Clockwork Mod thru Fastboot, I flashed the ROM and it made it stick for me
hotleadsingerguy said:
Not if you delete the "recovery-from-boot.p" file. Should skip right past that.
I had this same thing happen after I first unlocked/rooted, but then I deleted the file, re-install CWM through Rom Manager, and it works perfectly now.
Click to expand...
Click to collapse
Oh, good to know then. Thanks!
I tried deleting using both astro and super manager, cant get it off either way. Any pointers?
Thanks everyone for the posts, appreciate the help!
Try it with Root Explorer
I installed this yesterday jb-takju.zip. I was originally on cm9 rc1. In the process I managed to wipe my entire directory, nandroid backups included. I tried to get cwm back via fastboot and was able to then flashed CWM-SuperSU-v0.89.zip to get root right after. Now besides losing all my data, I cant keep the cwm touch recovery on, it keeps going back to the default recovery screen when I try to boot into recovery from rom manager. So at this point I'm baffled, not used to not have an sd card.
How can I have avoided this? How does titanium backup work with dropbox I couldnt get that set up. Also should I be flashing a different version of JB?
I didn't loose all any data on sdcard but was losing car. I ended up using the xbigie version. That was decided,rooted....
Sent from my Galaxy Nexus using xda premium
You must mean the virtual sdcard which I dont even see in my directories.
Can anyone tell me why I keep losing cwm touch recovery at least? lol
Should I just flash a different jellybean rom .zip?
SysAdmNj said:
Can anyone tell me why I keep losing cwm touch recovery at least? lol
Should I just flash a different jellybean rom .zip?
Click to expand...
Click to collapse
You can stay with CyanogenMod 9 RC1 and wait for the official release of JB!! What about that ???
:cyclops:
carloscarvalho said:
You can stay with CyanogenMod 9 RC1 and wait for the official release of JB!! What about that ???
:cyclops:
Click to expand...
Click to collapse
Not acceptable, I already lost all my nandroid backups so I might as well use available JBs and start fresh
You're losing your cust recovery because there is a script you need to delete that auto installs default recovery on every reboot. It should be named the same as it was in ICS when the phone first came out. I'm look for the exact name now unless someone beats me to it.
Edit: /system/recovery-from-boot.p is the file. Rename or delete. Then it should stop reloading stock recovery. Just make sure you have CWM installed already and you're good to go.