I haven't seen anything about the updated ClockworkMod Recovery here on XDA, and I'm not sure if many others know about it. =P
Update: ClockworkMod Recovery for the Droid X has been updated to 5.0.2.0. A new blue recovery!
WARNING: This can be used on both 2nd init and blur roms; however, on blur roms you must first use Droid 2 Bootstrapper to bootstrap.
EDIT: Make sure that you're ROM Manager is up-to-date. A new version was just released that fixes bugs with flashing the new recovery.
Open ROM Manager and select 'Flash ClockworkMod Recovery'.
When it asks you to confirm your device select 'Droid X (2nd init)' or 'Droid X', respective to your current rom.
It should then download and install ClockworkMod Recovery 5.0.2.0.
Reboot hy holding the power button and selecting Reboot > recovery, or rebooting to recovery from ROM Manager. Enjoy your new blue recovery ^_^
EDIT: In MIUI on the Defy base you must use `CWM Recovery' from the reboot menu to access ClockworkMod Recovery.
Sent from my DROIDX using XDA App
Strange...I did those steps and I'm still getting v2.5.0.8
Try seeing if an update is available for ROM Manager. If it is, install the update and try again.
Sent from my DROIDX using XDA App
infazzdar said:
Try seeing if an update is available for ROM Manager. If it is, install the update and try again.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Found the update.zip files however how do I flash it with ROM Manager? I've used it maybe a handful of times and that was only when I first started playing with ROMs late last year. I haven't used it since then...always done everything with CWM.
JagoX said:
I'm assuming you mean an update.zip file? I see one with today's date in the root directory of my SD card.
Click to expand...
Click to collapse
No, I mean check the Marketplace to see if an update for ROM Manager is available. It was updated this morning to further support CM7 on the Droid X.
Sent from my DROIDX using XDA App
infazzdar said:
No, I mean check the Marketplace to see if an update for ROM Manager is available. It was updated this morning to further support CM7 on the Droid X.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Oh weird...it didn't show up in my Market list as needing an upgrade but was available. No luck though Gonna try removing ROM Manager entirely with TB, rebooting & reinstalling ROM Manager to see if that fixes it.
JagoX said:
Oh weird...it didn't show up in my Market list as needing an upgrade but was available. No luck though Gonna try removing ROM Manager entirely with TB, rebooting & reinstalling ROM Manager to see if that fixes it.
Click to expand...
Click to collapse
Good luck. Be sure to make a nandroid backup just in case =P
I'll keep searching and see if I can find a remedy for your issue.
Sent from my DROIDX using XDA App
infazzdar said:
Good luck. Be sure to make a nandroid backup just in case =P
I'll keep searching and see if I can find a remedy for your issue.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Thank you Captain Obvious j/k
I get kind of tired of hearing my wife say "what are you doing to your phone now?" if I reinstall a ROM too much in one week LOL
Yea still no luck
Did the following (based on a suggestion in the Rootzwiki forum):
- Fully removed RM & the Premium license files
- rebooted
- reinstalled RM & Premium license
- Cleared Download cache in RM
- re-installed CWM 2.5.0.8 (chose Droid X)
- Cleared Download Cache
- updated CWM to 4.0.0.5 (choosing DX 2nd-init)
- reboot
- no luck
Gonna try removing RM again & going straight to CWM 4.0.0.5 to see if that works.
What good does having the newer recovery do? Just curious.
ghub1 said:
What good does having the newer recovery do? Just curious.
Click to expand...
Click to collapse
Through my experiences I've discovered that it's faster... and orange!
Sent from my DROIDX using XDA App
infazzdar said:
Through my experiences I've discovered that it's faster... and orange!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I tried flashing it as well and it says in ROM manager that I'm on 4.0.0.5 but in recovery it says 2.5.0.8 so weird. Have you figured out what causes this?
ghub1 said:
I tried flashing it as well and it says in ROM manager that I'm on 4.0.0.5 but in recovery it says 2.5.0.8 so weird. Have you figured out what causes this?
Click to expand...
Click to collapse
Make sure that your ROM Manager is up-to-date and try again. The latest version has a bug fix that wasn't in the version updated this morning. (I believe)
Sent from my DROIDX using XDA App
infazzdar said:
Make sure that your ROM Manager is up-to-date and try again. The latest version has a bug fix that wasn't in the version updated this morning. (I believe)
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Ya I updated and still not working. then uninstall and reinstall still not working. its really weird.
*edit
Now its working randomly. Not complaining haha
ghub1 said:
Ya I updated and still not working. then uninstall and reinstall still not working. its really weird.
*edit
Now its working randomly. Not complaining haha
Click to expand...
Click to collapse
I got mine working now An update came out (v4.3.2.3) which mentioned a fix for this exact problem & it updated properly for me too. I did notice that cache partition wiping is not as fast as v2.5.0.8 but who cares...IT'S ORANGE!
I know right, that is some sexy orange. One thing though is I've heard that you can only use backups made with 4.0.0.5, haven't actually run into myself since I cull my backups every once and a while to free up SD card space, and that some update zips won't work anymore because the new clockwork requires another file inside of it, my memory is failing me on what that file exactly is.
How is the 2nd inti different from Koushs recovery? I heard it had something specifically to do with CM7. But why cant they use the normal CWM. Wasn't obsidian able to use the regular CWM it was almost pure AOSP besides the kernel. So why the change? Just curious why it is needed.
joebob296 said:
How is the 2nd inti different from Koushs recovery? I heard it had something specifically to do with CM7. But why cant they use the normal CWM. Wasn't obsidian able to use the regular CWM it was almost pure AOSP besides the kernel. So why the change? Just curious why it is needed.
Click to expand...
Click to collapse
cvpcs did a really nice write-up on the subject that should answer all your questions =)
http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
meshdub said:
cvpcs did a really nice write-up on the subject that should answer all your questions =)
http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
Click to expand...
Click to collapse
Thank you very much I am now indulged in an interesting read.
EDIT: Ok so I read the post and followed it somewhat not knowing all the technicalities but got the jist of it. We still cant unlock the boot loader or kernel. Knowing this, what features are not going to be implemented in CM4DX?
joebob296 said:
Thank you very much I am now indulged in an interesting read.
EDIT: Ok so I read the post and followed it somewhat not knowing all the technicalities but got the jist of it. We still cant unlock the boot loader or kernel. Knowing this, what features are not going to be implemented in CM4DX?
Click to expand...
Click to collapse
As far as I know, right now all of CM7 features are implemented, except for the known bugs like camera/camcorder not working.
Related
i have Motorola droid 2 on 2.2 rooted with bootstrap recovery, everything was workin fine till i decided to install custom rom, which was unleashed epic 2.5 (by mat) and now everytime i turn on my phone it goes into a loop reboots and never turns on all the way.
i have tried using sbf RSDlite to restore it, tried using linux ubuntu(newk8600 method ty btw) method as well to restore it, none seems to work i keep getting errors whenever i try to do it.
however before i installed the custom rom i did full backup using bootstrap recovery but the only way (that i know) to get in recovery is using bootstrap app, so is there a way i can manually get into bootstrap recovery so i can restore from backup?
please let me know, or if you have different method i'll appreciate your help. thanks in advance.
Which version of the software did you have before you installed epic unleashed, and which SBF did you use?
From what I have heard, Epic Unleashed will "brick" your phone if you try to install it on the 2.3.20 build. Since your phone did get bricked, it's likely that you are running 2.3.20 and not 2.2. You might want to make sure you are using the 2.3.20 SBF to flash your phone, and not the 2.2 SBF (which won't work because the kernel changed between the two)...
What type of errors do you get?
i always have luck getting into clockwork recovery by having my phone plugged in and within the first few seconds taking out my battery forcing it to take along time booting after the M logo and hence putting it into clockwork. I hope this helps
after you get passed the M pull the battery then boot back up it should come up in to recovery
thank you all for your help, however i tried all of these steps already, but i found another way to get it workin, here is the solution to whom got the same problem as mine.
its not letting me post the link for some reason, anyway just search for (Droid 2 Global SBF File (2.4.29) Full and RSDLite ).
just got relased today , big thanks to team Black Hat and MyDroidWorld
hope that helps.
Glad you got it fixed. Let me ask you something though. Before you installed the custom rom, did you wipe data and cache? Not doing so could result in a bootloop.
Sent from my DROID2 using XDA App
orkillakilla said:
Glad you got it fixed. Let me ask you something though. Before you installed the custom rom, did you wipe data and cache? Not doing so could result in a bootloop.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Sounds like the OP was trying to install a ROM for the original Droid 2 on the Droid 2 Global. It wouldn't have worked, no matter what install steps were used.
Phoible said:
Sounds like the OP was trying to install a ROM for the original Droid 2 on the Droid 2 Global. It wouldn't have worked, no matter what install steps were used.
Click to expand...
Click to collapse
Ah op didn't mention it was a global. Should have realized when he said he used the global sbf though... brain fart
Sent from my DROID2 using XDA App
orkillakilla said:
Ah op didn't mention it was a global. Should have realized when he said he used the global sbf though... brain fart
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It's all good people need to read where they are posting this is in the D2 General section not the D2 Global general section. That's half his problem, he's been looking at ROMs for the original D2 not the device that he currently uses.
Check your ROM Manager to flash 3.0.0.5 and have it show correctly.
Sent from my HTC Vision using XDA App
DAMNIT...you beat me to it lol...I was so stoked when I saw that.
No I just have to get this damn ext4
troby86 said:
Check your ROM Manager to flash 3.0.0.5 and have it show correctly.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Is this for people who have flashed ClockworkMod 3 already?
Will I see this? I have ROM Manager v3.0.0.7 w/ ClockworkMod 2.5.1.3 currently.
Sorry if this is a dumb question, I'm just a little confused.
hogg2500 said:
Is this for people who have flashed ClockworkMod 3 already?
Will I see this? I have ROM Manager v3.0.0.7 w/ ClockworkMod 2.5.1.3 currently.
Sorry if this is a dumb question, I'm just a little confused.
Click to expand...
Click to collapse
I had the same setup as you (RM v3.0.0.7/CM 2.5.1.3) and saw the update, now I have the latest ClockworkMod Recovery 3
WOOOOHOOOOOO
Now all the threads about people not being able to get it will stop!
borisimo said:
I had the same setup as you (RM v3.0.0.7/CM 2.5.1.3) and saw the update, now I have the latest ClockworkMod Recovery 3
Click to expand...
Click to collapse
Ah alright so now when I get it that should allow me to install Cyanogenmod 7 then right since clockwork 3 supports ext4? I didn't do the ENG-Hboot though. I'm assuming that could prevent me from doing any Gingerbread ROM?
hogg2500 said:
Ah alright so now when I get it that should allow me to install Cyanogenmod 7 then right since clockwork 3 supports ext4? I didn't do the ENG-Hboot though. I'm assuming that could prevent me from doing any Gingerbread ROM?
Click to expand...
Click to collapse
NOPE. That is not necessary to flash CM7. With CWM3, you are good to go.
TJBunch1228 said:
NOPE. That is not necessary to flash CM7. With CWM3, you are good to go.
Click to expand...
Click to collapse
Wonderful =D. I thought I seen that somewhere... One more queston lol. I was thinking of also GingerVillian ROM. I should be good with doing that then too?
Thank you everyone
hogg2500 said:
Wonderful =D. I thought I seen that somewhere... One more queston lol. I was thinking of also GingerVillian ROM. I should be good with doing that then too?
Thank you everyone
Click to expand...
Click to collapse
Yeah for sure. GV has most of the gingerbread source kanged from CM7 anyway, with some visual tweaks as far as I have been able to see. With CWM3, you will be good to flash any G2 ROM that is available to us.
TJBunch1228 said:
Yeah for sure. GV has most of the gingerbread source kanged from CM7 anyway, with some visual tweaks as far as I have been able to see. With CWM3, you will be good to flash any G2 ROM that is available to us.
Click to expand...
Click to collapse
Sweetness. I seen that Eng-hboot in the Cyanogenmod 7. Not really sure why?
But I did Get Root using Rage & Gfree. I have never flashed back to an older recovery though.
Is this universal now or will I still need to downgrade to get back to
cm6.1.1
loustrk said:
Is this universal now or will I still need to downgrade to get back to
cm6.1.1
Click to expand...
Click to collapse
Ganii ran a test with it said he could flash between 2.2 and 2.3 with no problems plus he was able to do nandriods of both and restore them, so sounds like it is universal for all roms 2.2 and 2.3.
Sent from my HTC Vision
Yes,seems to be no problems there.
Come from CM7 Nightly,then I did a wipe data/factory reset.
Installed now CM 6.1.1 Froyo 2.2 ROM,works.
Did a nandroid backup,works.
Then tried to restore,works too
CWM 3.0.0.5 seems to work now with 2.2 ROMs too
i was on the 2.xxx recovery in rom manager and it prompted me to flash new recovery of 3.0.0.5. so I dont think its for people who already have 3.0.0.5
I had 3.0.0.5 already and yes it did promt me to update to 3.0.0.5 because proir to this everyones recovery in rom manager said 2.5.1.3 even if they were on 3.0.0.5, so this is for everyone.
Sent from my HTC Vision
joemm said:
Ganii ran a test with it said he could flash between 2.2 and 2.3 with no problems plus he was able to do nandriods of both and restore them, so sounds like it is universal for all roms 2.2 and 2.3.
Sent from my HTC Vision
Click to expand...
Click to collapse
Thanks Joemm & Ganii, Will try after work!
Spastic909 said:
i was on the 2.xxx recovery in rom manager and it prompted me to flash new recovery of 3.0.0.5. so I dont think its for people who already have 3.0.0.5
Click to expand...
Click to collapse
Installed few days ago from here,but it`s the old one:
http://phones.crackflashers.com/vision/index.php?folder=cmVjb3Zlcmllcw==
Can`t restore 2.2 ROMs with this,so the recovery 3.0.0.5 which
you can download now via ROM Manager is newer.
Updated fine, just want to know do I have to partition my sd card
with ext 4 before I try cm7? I backed up my sd to my computer and
have cm7 and gapps downloaded and ready to go.
No,not needed.
Ganii said:
No,not needed.
Click to expand...
Click to collapse
Sweet, giving it a go now.
Hello, i just bought myTouch 4g and i'm a noob, could someone explain me how to install the Android 2.3 from zero?? I want the Nexus s version. Please!!!
ringox said:
Hello, i just bought myTouch 4g and i'm a noob, could someone explain me how to install the Android 2.3 from zero?? I want the Nexus s version. Please!!!
Click to expand...
Click to collapse
1) root the device and turn s=off. Threads in the development section
2) visit the Cyanogen mod CM7 thread
[sent via Cyanogen powered Android]
Root your phone via one of the many available methods although the gfree has seemed to have some issues. I'd recommend visionary method. Once you have root and have S-off install Rom manager via the market and flash clockwork (and correct me if I'm wrong as I get confused a lot with recoveries build #'s lol) mod recovery version 2.5.1.2, 3.0.0.5 or 3.0.0.6. 3.0.0.6 is the best available currently. After flashing clockwork in Rom manager (its the first thing that pops up) scroll to download Rom and download cyanogen mod 7 rc4 from that menu. (You will have finished downloading the rom and have booted into recovery by now) MAKE A NANDROID BACKUP BEFORE PRECEDING. Then Wipe data and cache via recovery and then go to install zip via SD card then choose it again find the .zip file for cm7 and hit install. It WILL take awhile to install. After it finishes reboot. Again this will take awhile. Once it comes up, wait 3 minutes or so then reboot. Then set up and your good to go. Once you've done that its basically rinse repeat for other roms. But remember to read the roms flashing instructions before hand as it may have some wacky process for flashing. Good luck!
Sent from my HTC Glaciee using XDA Premium App
Not to nitpick, but 3.0.2.4 is the latest version. It just came out the other day, so that's probably why you're not aware.
EDIT: To the OP, like neidlinger said, your first step is to root. This is the guide I followed and it works great: http://forum.xda-developers.com/showthread.php?t=858021.
TeeJay3800 said:
Not to nitpick, but 3.0.2.4 is the latest version. It just came out the other day, so that's probably why you're not aware.
Click to expand...
Click to collapse
I was aware just wasn't aware of the stability thanks for the heads up though!
Sent from my HTC Glaciee using XDA Premium App
Nicgraner said:
I was aware just wasn't aware of the stability thanks for the heads up though!
Click to expand...
Click to collapse
I usually worry about the same thing with brand new releases. In this case, it seems to be good to go.
Thanks man if it looks good to you I'll probably flash it
Sent from my HTC Glaciee using XDA Premium App
Thank you to all of you guys!! I'll try to do it this afternoon.
So I just need to follow this instructions: http://forum.xda-developers.com/showthread.php?t=858021 and find a good custom rom to install, right?? which kind of room do you recomind me, as I said I want the Nexus S apariance.
ringox said:
So I just need to follow this instructions: http://forum.xda-developers.com/showthread.php?t=858021 and find a good custom rom to install, right?? which kind of room do you recomind me, as I said I want the Nexus S apariance.
Click to expand...
Click to collapse
Once you're finished with that tutorial, you'll be rooted and have a custom recovery installed. At that point, create a Nandroid backup, and then wipe all three items in the recovery menu and install the custom ROM. There is no direct Nexus S port to the MT4G, but CM7 and RoyalGinger are essentially the same thing, and in fact better, so check those out in the dev section.
Hey guys, I have a question about upgrade to other Roms from a rooted gingerbread ver. 4.5.573
I already have Droid 2 bootstrapped and have this version rooted. So would I be able to just upgrade via bootstrapped straight to a new rom?
Sent from my DROIDX using XDA App
Do u have clockwork recovery installed? If not, download "rom manager" from market place, and install clockwork. And from there u should be set, however u may need to update to a newer version of gb, the newer roms are running on to of .595 & .596.
Sent from my DROIDX using XDA Premium App
at this point you may really want to consider getting up to a .596 base before flashing a newer rom. liberty for example is only going forward on the .596 build, they even pulled earlier gb versions (v.01-5) from their toolbox as those were all built on the earlier gb leaks
once you make a reliable .596 backup you should find it much easier to switch between roms, tbh app now has a one step zip to take you to .596 rooted from any other framework.
none selected the
Could you link me to that zip? Cause I have black hat release but the version says its: 4.5.573_MB810 is there a newer one?
Sent from my DROIDX using XDA App
shukero said:
Could you link me to that zip? Cause I have black hat release but the version says its: 4.5.573_MB810 is there a newer one?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
http://www.mydroidworld.com/forums/...-5-596-release-thread-something-everyone.html
OK, now HERE's my question. Cause I have NO CLUE what I'm running anymore -.-
First thing: I'm running system version: 4.5.573.MB810.Verizon.en.US
So does this mean I have a order cracked version?
Second thing: I have a droid strapper backup of rooted froyo, so if I do need to go back to froyo, can I just load up this backup?? or do I need to sbf back?
shukero said:
OK, now HERE's my question. Cause I have NO CLUE what I'm running anymore -.-
First thing: I'm running system version: 4.5.573.MB810.Verizon.en.US
So does this mean I have a order cracked version?
Second thing: I have a droid strapper backup of rooted froyo, so if I do need to go back to froyo, can I just load up this backup?? or do I need to sbf back?
Click to expand...
Click to collapse
1. yes
2. sbf to go back.
OK, I just tried to sbf, and now its stuck on 100% on RSDLite at the boot logo... What do I do?
shukero said:
OK, I just tried to sbf, and now its stuck on 100% on RSDLite at the boot logo... What do I do?
Click to expand...
Click to collapse
pull battery, enter stock recovery, wipe data, reboot
Thanks, Yeah figured out that my sbf was corrupt re-did it with new file and now working on .596
AND JUST AN FYI to those people who are wondering about the recovery for the 2 part gingerbread update: you choose "install from .zip file" not install update.zip
Do that 2 times, part1 then part2. If it doesnt boot up the first time after you exit, pull battery and reboot again. worked for me the second time
After all the moaning and groaning about loosing root after the OTA I bothered to lauch into boot loader today and check my "S" status, and it is OFF. does this mean that i can flash a custom recovery? If so, where can I find a flashable version of Clockwork or amon?
any help would be greatly appreciated!
CaptEvo said:
After all the moaning and groaning about loosing root after the OTA I bothered to lauch into boot loader today and check my "S" status, and it is OFF. does this mean that i can flash a custom recovery? If so, where can I find a flashable version of Clockwork or amon?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Put this file on the root of your sdcard and boot into the bootloader.
thanks I'll try that out when I get home.
CaptEvo said:
After all the moaning and groaning about loosing root after the OTA I bothered to lauch into boot loader today and check my "S" status, and it is OFF. does this mean that i can flash a custom recovery? If so, where can I find a flashable version of Clockwork or amon?
any help would be greatly appreciated!
Click to expand...
Click to collapse
If you used unrevoked forever to achieve root, you will not lose s-off from an ota. After receiving an ota you can simply flash a PC36IMG of a custom recovery and then flash the latest superuser.zip from your recovery.
Sent from my PC36100 using XDA Premium App
I'm digging around here and can't find what I'm looking for which is a pcm36img.zip of amon ra. can you please post a link for me if you know off hand where it is?
thanks
CaptEvo said:
I'm digging around here and can't find what I'm looking for which is a pcm36img.zip of amon ra. can you please post a link for me if you know off hand where it is?
thanks
Click to expand...
Click to collapse
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
CaptEvo said:
I'm digging around here and can't find what I'm looking for which is a pcm36img.zip of amon ra. can you please post a link for me if you know off hand where it is?
thanks
Click to expand...
Click to collapse
It can also be found in the first post of the amon_RA 2.3 thread in the EVO 4g development forum.
Sent from my PC36100 using XDA Premium App
Originally Posted by CaptEvo
I'm digging around here and can't find what I'm looking for which is a pcm36img.zip of amon ra. can you please post a link for me if you know off hand where it is?
thanks
Click to expand...
Click to collapse
It can also be found in the first post of the amon_RA 2.3 thread in the EVO 4g development forum.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
That's where I got it.
Thanks guys, i got it done but had troubles with superuser not flashing. Had to go to androidsu.com and get the ginger compatible version. Didnt even know there was such a thing. Only issue now is that it kicks an error in rom manager when trying to fix permissions. Any ideas?
CaptEvo said:
Thanks guys, i got it done but had troubles with superuser not flashing. Had to go to androidsu.com and get the ginger compatible version. Didnt even know there was such a thing. Only issue now is that it kicks an error in rom manager when trying to fix permissions. Any ideas?
Click to expand...
Click to collapse
I think you need to flash a rom now. I don't think you can add superuser to the recent OTA. Once you flash a rom, you will be rooted, just not on stock (unless you flash the stock GB).
CaptEvo said:
Thanks guys, i got it done but had troubles with superuser not flashing. Had to go to androidsu.com and get the ginger compatible version. Didnt even know there was such a thing. Only issue now is that it kicks an error in rom manager when trying to fix permissions. Any ideas?
Click to expand...
Click to collapse
Remove rom manager and reinstall it. when you try to fix permissions this time you'll see the SU prompt to accept.
You need to flash a rooted rom now... Soff does not provide you with SU permissions inside stock rom.
Sent from my PC36100 using XDA Premium App
Thats what Im doing next, uninstalling it and reinstalling. It does currently get su permission, but something just may not be right.
You can have su on the OTA, you just have to go to androidsu.com and select the version for gingerbread. Worked for me....
Try downloading titanium backup from the market. when it first loads click on problems at the bottom. this will install the newest version of busybox which may help the rom manager issue.
Sorry, edit...
Sent from my PC36100 using XDA Premium App
CaptEvo said:
Thats what Im doing next, uninstalling it and reinstalling. It does currently get su permission, but something just may not be right.
You can have su on the OTA, you just have to go to androidsu.com and select the version for gingerbread. Worked for me....
Click to expand...
Click to collapse
Could it be from trying to run fix permissions in Rom Manager but having Amon Ra loaded? Or maybe still the wrong version of SU? I believe there's an app in the market by the same guy to fix Superuser version.