Develop Bugs

rooted....now lost! Please help

I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom

Bump.....ANYONE?!

So the following questions would need to be answered:
1) What version of stock were you running before you rooted? (i.e. 1.47, 1.32)
2) What root method did you use?
3) What recovery do you have?
4) If you have wireless tether working than you would need to have installed a custom kernel, which one did you install?
I'm sorry that no one else has tried to assist you in this, however, next time please post this in Q&A as this is for development purposes.
~Jasecloud4

nova0387 said:
I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom
Click to expand...
Click to collapse
my personal experience sometimes if your using the rom mangager to flash roms it doesnt always wipe it fully so i use amon recovery all the time now

Im honestly not sure which version i was running b4 I just my Evo about 4 days ago...I used the SimpleRoot 1.47 to root my phone...all went fine for rooting...I didnt install any custom kernal...I pretty new at this so bare with me a bit if you could
and thnx for your time for even replying man!

nova0387 said:
Im honestly not sure which version i was running b4 I just my Evo about 4 days ago...I used the SimpleRoot 1.47 to root my phone...all went fine for rooting...I didnt install any custom kernal...I pretty new at this so bare with me a bit if you could
and thnx for your time for even replying man!
Click to expand...
Click to collapse
i honestly dont know anything about that simple root i have heard that it does work though i rooted in the beginning with toast's method. anyway what happens when you try and get to recovery mode IE powering the the phone off, then holding the volume down button while powering the phone on?

danon.brown said:
i honestly dont know anything about that simple root i have heard that it does work though i rooted in the beginning with toast's method. anyway what happens when you try and get to recovery mode IE powering the the phone off, then holding the volume down button while powering the phone on?
Click to expand...
Click to collapse
Well when i try to go into recover mode it first gives me a black screen that shows a cell phone and a triangle with a exclamation point then i hold the volume up keyand press power and it says "e can't open cache recovery command" n then takes me to a screen where it says
Android system recovery <2e>
use d-pad to highlight; center to select.
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition

nova0387 said:
I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom
Click to expand...
Click to collapse
Okay during the process of rooting my device, ebo 4g, v1.3x
I ran into the same problem, you have to or I'm sure on this forum just do some research,.....
In RA, dalvik wipe, cache wipe and phone wipe. Then I flashed the rom via sd card, using clockwork custom recovery. If you used Simple root 3 click process you should have clock work.Via step 2.
Rename the Rom to update.zip and place in root sdcard.
Adb reboot recovery
Update.zip from SD card
Finnish do full system wipe and dalvik cache.
Make sure you are nand protected before flashing.
Via step 3
I don't know if this mighhelp just some recent stuff I ran into. Rooted my g1 a WHILE back. Hope these noobietips help lol
Sent from my PC36100 using XDA App

Do this! It's the fastest and easiest way.
Once you get 1.47 and singed sigs then do DC ROM again.
http://forum.xda-developers.com/showthread.php?t=715915

elitekernel said:
Okay during the process of rooting my device, ebo 4g, v1.3x
I ran into the same problem, you have to or I'm sure on this forum just do some research,.....
In RA, dalvik wipe, cache wipe and phone wipe. Then I flashed the rom via sd card, using clockwork custom recovery. If you used Simple root 3 click process you should have clock work.Via step 2.
Rename the Rom to update.zip and place in root sdcard.
Adb reboot recovery
Update.zip from SD card
Finnish do full system wipe and dalvik cache.
Make sure you are nand protected before flashing.
Via step 3
I don't know if this mighhelp just some recent stuff I ran into. Rooted my g1 a WHILE back. Hope these noobietips help lol
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?

stewie-droid said:
Do this! It's the fastest and easiest way.
Once you get 1.47 and singed sigs then do DC ROM again.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
I ttried that and it works fine until i get to the part about the su file...it doesnt let me go into recovery mode it shows me the black screen with a cell phone and a triangle with an exclamtion point

nova0387 said:
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?
Click to expand...
Click to collapse
adb reboot recovery just reboots your phone into recovery mode. once your in that do all the wipes i think its 3 dlvk, data and something else. power off the phone once more then boot to recovery again. now one of the options is flash from zip go there and you should find whatever rom your trying to flash. also you should be putting your zipped rom files in the root directory of your sdcard. on a side not if your on a mac dont download them with safari use firefox or something else

nova0387 said:
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?
Click to expand...
Click to collapse
also clockwork and ra are 2 different types of recovery you wont notice anything until u actually reboot the phone into recovery mode

Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?

nova0387 said:
Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?
Click to expand...
Click to collapse
you forgot to wipe something common problem.. reboot to recovery again.. go to the wipes part and do all of them.. reboot one last time to recovery then flash DC it should work then

wipe the first 3 if your on RA 1.7.0.1 data/factory, cache, and dalvik.. then reboot into recovery again and flash

nova0387 said:
Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?
Click to expand...
Click to collapse
nova,
I had the same boot loop issue. My thread for it here:
http://forum.xda-developers.com/showthread.php?t=728955
The issue was that I wasn't totally 100% rooted. By carefully following these directions, I was able to resolve my issue:
http://forum.xda-developers.com/showthread.php?t=721055
I hope this helps also, I did it using the "PC" method. If you have questions regarding those instructions I'd be happy to share my personal experience.

Ok Ok Ok!!! I think I jsut got it my dood! How do i know tho? It booted up and everything just fine and i have wayy more apps including like Dconfig ad superuser permission...is that kinda how i kno?

nova0387 said:
Ok Ok Ok!!! I think I jsut got it my dood! How do i know tho? It booted up and everything just fine and i have wayy more apps including like Dconfig ad superuser permission...is that kinda how i kno?
Click to expand...
Click to collapse
Errr... maybe? Superuser permission, etc. certainly doesn't come with stock. It depends on the ROM you installed. Here's one way to find out...
Go to Settings -> About Phone -> Software Information and check the "Build Number". AFAIK it's impossible to install DamageControl without full root (I tried to myself before fixing my root and going to Fresh 1.0.1) so if that's what you have I'd say you're good.
There may be a better way but that's all I know.

aikeru said:
Errr... maybe? Superuser permission, etc. certainly doesn't come with stock. It depends on the ROM you installed. Here's one way to find out...
Go to Settings -> About Phone -> Software Information and check the "Build Number". AFAIK it's impossible to install DamageControl without full root (I tried to myself before fixing my root and going to Fresh 1.0.1) so if that's what you have I'd say you're good.
There may be a better way but that's all I know.
Click to expand...
Click to collapse
Yep my Build Number says DamageControl v3.2.3! Thnx again everyone who tried to help me and def a special thnx to Danon.Brown! Hollllllla

[Q] Clockworkmod Recovery Help!

Hey All,
I am a long time "rooter" (June of 2010) on my Dinc. However, I am trying to Flash the new version of Clockworkmod Recovery. I open Rom Manager, click option 1 to "Flash ClockworkMod Recovery" to version 3.0.0.5. It asks me to verify my phone (Dink) and then says it flashed correctly. So, I reboot into Recovery and it is still the green text and says version 2.5.x.x. I reboot the phone and look in Rom Manager again it is says my Current version is 3.0.0.5. So, Rom Manager thinks I have the latest version of Recovery but I don't. I have tried other methods of Flashing the new version but that isn't working either. Specifically, I tried the ADB Shell. I get into ADB Shell just fine, but when I try to mount the SDCARD I get an error. I can boot the phone up and navigate just fine to the SDCARD. So I am not sure what the issue is. Any help would be greatly appreciated.
**UPDATE** I also had update.zip on the root of my sdcard, I deleted that and it still doesn't work.

i think you have reformat the partition

carepack said:
i think you have reformat the partition
Click to expand...
Click to collapse
Will that do damage? What partition, the SDcard? Please elaborate. Do that in the Clockworkmod Recovery?

FWIW, the new clockwork has compatibility issues with 95% of the flashable roms and extras out there right now. I wish I had not updated, and I am unable to go back (a nand restore would not do it.) Unless you feel a pressing need, you may be better off with the old version.
I got so frustrated, I switched my recovery to Amon_RA, which seems to work better for me at this point.

CJeep said:
FWIW, the new clockwork has compatibility issues with 95% of the flashable roms and extras out there right now. I wish I had not updated, and I am unable to go back (a nand restore would not do it.) Unless you feel a pressing need, you may be better off with the old version.
I got so frustrated, I switched my recovery to Amon_RA, which seems to work better for me at this point.
Click to expand...
Click to collapse
Ok, well I am using CM7 ROM and I think you have to have the new version. I reallly like CM7 so it would be worth it for me if I can get it to work. Can I use Amon RA with CM7 Rom?

foldog22 said:
Ok, well I am using CM7 ROM and I think you have to have the new version. I reallly like CM7 so it would be worth it for me if I can get it to work. Can I use Amon RA with CM7 Rom?
Click to expand...
Click to collapse
You do not need the new recovery for CM7 to work. You should also go to 3.0.0.8, there are problems with 3.0.0.5
See http://forum.xda-developers.com/showthread.php?t=970032 for details.

CJeep said:
FWIW, the new clockwork has compatibility issues with 95% of the flashable roms and extras out there right now. I wish I had not updated, and I am unable to go back (a nand restore would not do it.) Unless you feel a pressing need, you may be better off with the old version.
I got so frustrated, I switched my recovery to Amon_RA, which seems to work better for me at this point.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showthread.php?t=970032 on how to downgrade clockworkmod.
If your theme/extras developers have not upgraded their install scripts (like they have been warned to do for quite a few months) then this is the reason they do not work with the new CWM.

I followed the instructions but it still isn't working. I think the issue is ADB Shell can't mount the SDCARD. While in recovery, I can navigate to the SDCARD, but for some reason ADB Shell can't mount it. I tried all three methods as prescribed in the link. None work.

foldog22 said:
I followed the instructions but it still isn't working. I think the issue is ADB Shell can't mount the SDCARD. While in recovery, I can navigate to the SDCARD, but for some reason ADB Shell can't mount it. I tried all three methods as prescribed in the link. None work.
Click to expand...
Click to collapse
While you are booted in recovery I do not believe you can flash a new one. Boot to your ROM and try from there.

I figured it out. I ran the Unrevoked for Life patch and at that point it would let me update the Recovery image. Not sure if that was a prereq. or not. However, I am still experiencing issues. I am running CM7 with 3.0.0.8 Recovery. I am trying to update the nightly builds and it fails. Using Rom Manager to update my rom, it downloads the update. Reboots into Recovery and then says something about E:\ failure.

Well, I finally got the new recovery image but I can't update CM7 ROM's. It downloads the "Nightly Updates" but then says it can't mount E:\ when it reboots into recovery.

[Q] E: Can't open CACHE:recovery/log

I'm pretty new to rooting and flashing, but did flash several ROMs over the period of a few months. Recently, I wanted to clean my phone up so I thought I'd start from scratch. I unrooted which which went well and then rooted again last night via Unrevoked (3.70). I used bootloader for AmonRa's 2.3 recovery which went well, made a nand, and flashed Miks 4.5 ROM. Since then, when booting into recovery, I see 'E: Can't open CACHE:recovery/log' and it worries me as I have no clue what it means. Also, and I'm unsure if it's even related, but my Market worn't download anything anymore.
Any thoughts/solutions?
Thanks in advance!

cdadams1223 said:
I'm pretty new to rooting and flashing, but did flash several ROMs over the period of a few months. Recently, I wanted to clean my phone up so I thought I'd start from scratch. I unrooted which which went well and then rooted again last night via Unrevoked (3.70). I used bootloader for AmonRa's 2.3 recovery which went well, made a nand, and flashed Miks 4.5 ROM. Since then, when booting into recovery, I see 'E: Can't open CACHE:recovery/log' and it worries me as I have no clue what it means. Also, and I'm unsure if it's even related, but my Market worn't download anything anymore.
Any thoughts/solutions?
Thanks in advance!
Click to expand...
Click to collapse
try booting into recovery and wiping your cache

I thought I tried that already per a suggestion I read somewhere, but it didn't work. Lemme try it again and I'll post back in a few.
Thanks!

if it doesnt work try downloading terminal emulator from the market (free) and run this command:
su
cd /cache
rm -rf *

do you have rom manager, believe rom manager lets you flash amon ra recovery, its an option at the bottom of the menu, if it lets you flash and you are able to go into recovery i would wipe cache, dalvik and data and the reflash the rom(you should probably download it again and put it in the root of your sd card, i say re-download just to make sure you didn't get a corrupted download the first time)

cdadams1223 said:
... Recently, I wanted to clean my phone up so I thought I'd start from scratch....
Click to expand...
Click to collapse
Next time just wipe EVERYTHING twice and flash THIS, then you will be stock and clean BUT still rooted

@blakeboys - Well, your suggestion worked. Apparently I tried wiping my Dalvik-cache and not just cache. This time I did both and voila...it worked. I'm now able to download apps from the market again. I haven't returned to recovery to see if I get that same error so I'm not sure about that.
@emcp422 - I do have ROM Manager, but I do not use it. It is not set-up yet to flash the latest AmonRA which is 2.3. I never had a problem of accessing my recovery. If it happens again, I will do as you suggested and re-download it and install it again.
Thanks for yall's help!

no problem, glad we could help ya

blakeboys said:
Next time just wipe EVERYTHING twice and flash THIS, then you will be stock and clean BUT still rooted
Click to expand...
Click to collapse
Will do...thanks man!

cdadams1223 said:
@blakeboys - Well, your suggestion worked. Apparently I tried wiping my Dalvik-cache and not just cache. This time I did both and voila...it worked. I'm now able to download apps from the market again. I haven't returned to recovery to see if I get that same error so I'm not sure about that.
@emcp422 - I do have ROM Manager, but I do not use it. It is not set-up yet to flash the latest AmonRA which is 2.3. I never had a problem of accessing my recovery. If it happens again, I will do as you suggested and re-download it and install it again.
Thanks for yall's help!
Click to expand...
Click to collapse
Actually ROM manager does flash Amon Ra 2.3 for some reason the app shows 2.2.2 or whatever but if you boot into recovery its actually 2.3

RileyGrant said:
Actually ROM manager does flash Amon Ra 2.3 for some reason the app shows 2.2.2 or whatever but if you boot into recovery its actually 2.3
Click to expand...
Click to collapse
That's good to know! Thanks!

[Resolved] Recovery installed but no root access

I used AlphaRevx to achieve S-OFF and when it asked if I wanted the CWM recovery, I said yes. It installed the recovery properly. I have SU. However, if I try to run Titanium, it says that there is no root access. I have rebooted several times. I tried to flash CM7 and it was stuck in a bootloop. Downloaded from the mirror and it booted up fine. I tried playing around with ROM Manager while I was booted into CM7 and it told me there was no recovery image on the root of the SD card.
Hopefully it's just something simple that I'm overlooking. Any suggestions?
Another thing I though was weird is that I couldn't sync to Gmail while booted into CM7.

To gain root access on the stock rom, you first have to flash thisthrought recovery.

I actually did flash that as well. Still had the same results.
Should I have removed the SU file that was already installed on the sd card and then flashed the patch?

Hmm weird, maybe try flashing one of these 2 roms
this
or
this
Both are based off the stock froyo rom, debloated and rooted.

I'll probably give that a try in a little bit. I suspect that it will not work as I didn't even have root access with CM7 installed.

Maybe before you flash clear all the data at least 2 times, do a factory reset, and clear the dalvik cache. If nothing works try the manual way to flash CWM and reflash it.

I only wiped data/cache once before I flashed each time. I'll try wiping more than once next time.
Do you think I could have flashed a corrupt file for SU?

brocksdad said:
I only wiped data/cache once before I flashed each time. I'll try wiping more than once next time.
Do you think I could have flashed a corrupt file for SU?
Click to expand...
Click to collapse
Make sure you wipe /data, /cache, /system before you flash any rom. If you do this it removes the chances for errors to occur. if you flashed CM7 over the original /system, you might have corrupted the su file.

I don't think that I did, but it is possible. I'll first start by removing the SU file that is on there now and then flashing the patch that you posted up. I'll update after I do that.
I have to wait though, my battery is dead.
Thanks for your help!

No problem. If you didn't format the /system before you flashed CM7, you flashed over the original /system, sometimes it makes no difference, sometimes it messes stuff up. Kinda hit or miss.

Yah normally doing a Factory wipe then a wipe data/cache/dalvik should get her done try rerunning alpharev utility and see what you get

Update: I removed the su-2.3.6.1-ef-signed.zip from the SD card and then flashed the patch. Still having the same issues. I tried to run AlphaRevX again and it came back saying something like "You already have S-OFF with AlphaRev. What do you think you're doing?"
Any other suggestions?

First of all i s-offed and cwmed with alpharev.
Then in cwm i wiped phone + cache + dalvik .
Then flashed this http://forum.xda-developers.com/showthread.php?t=1138274
Then after phone boots and so on i restart in cwm again and flashed this
http://forum.xda-developers.com/showthread.php?t=1160745
After all i got SU in programs and got root for all my apps.
Try this )

The whole point of this is to have Titanium backup installed so I backup all my apps before I flash a ROM.

brocksdad said:
The whole point of this is to have Titanium backup installed so I backup all my apps before I flash a ROM.
Click to expand...
Click to collapse
Hey brocksdad,
Why not give this a shot as this is what I had to do:
-Alpharevx s-off which you've done
-flashed CWM via fastboot adb which seems like you've done: http://forum.xda-developers.com/showthread.php?t=1134520
-flash this patch which will install superuser, busybox, and rooter kernal in the correct places /system/xbin: http://forum.xda-developers.com/showthread.php?t=1134520
-reboot and you should be good to go.
I think you were having the same issues I was in that the SU app would not update the binaries for me, so I had to install the manual patch I found in the development forum.
Let me know if this works for you....

If I wanted to manually put the CWM recovery in there do I just flash OVER what I already have or do I need to remove the recovery that is already installed? If I have to remove it, how do I go about doing that?

brocksdad said:
If I wanted to manually put the CWM recovery in there do I just flash OVER what I already have or do I need to remove the recovery that is already installed? If I have to remove it, how do I go about doing that?
Click to expand...
Click to collapse
You would just reflash over the recovery. I'm hoping you used the recovery that was posted for us and not the one with Rom Manager as that is an older recovery that hasn't been updated for Inc2 support yet.
In any case, it wouldn't hurt to go and do the process over again. You should have fastboot.exe in the same folder as your adb and might as well have the CWM flash .img in that same folder as well to make things easier. once you do that you can flash the SU patch in recovery and you should be good to go.
Update: By the way if you need adb, you can just download the files from the "Temp Root" post in development and download fastboot.exe by searching in google.

I used the recovery that the AlphaRev tool gave me.
I'll give that a try and see how it goes.
Thanks!

brocksdad said:
I used the recovery that the AlphaRev tool gave me.
I'll give that a try and see how it goes.
Thanks!
Click to expand...
Click to collapse
Okay then you should be fine. Go ahead and flash that SU zip in recovery mode. Once you reboot, open up superuser and go to settings. Check the SU binary and make sure it says v2.3.2-efgh (eclair, froyo, gb, honeycomb).
If it does then you should be good to go. Also make sure when there are md5 sums provided by the uploads that you check those to make sure they match so that you don't try flashing corrupted downloads. There's a free app in the market for checking the md5 sums right on your phone, it's called AFV (Android File Verifier)

I just looked at the SU information. It says v2.3.6.3. Underneath it says SU binary voutdated. I tried to update and it comes back with an error saying that su-2.3.1-bin-signed.zip has been placed on the sd card. Please reboot into recovery mode and flash it to update the SU binary.

Rom Manager doesn't see CWM is installed?

Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
edit: CWM v5.5.0.4

do you try "wipe cache" and "advanced->wipe dalvik cache?"

Thanks, I just tried, it took quite a while to clear the cache. When I booted up it went through a whole Optimizing Apps process, I'm not sure if that was due to wiping the dalvik cache? But it still didn't fix the Rom Manager issue.

Its probably not yet compatible if you have the touch version of cwm installed, so it wants to flash the standard one. Or you could always just let rom manager just reflash cwm overtop and then you may be good to go.

EvanVanVan said:
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk

I don't have the touch version installed (doesn't seem to be the touch version anyway). I should have said this in the first post but it CWM v5.5.0.4.

Herman76 said:
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Flashing CWM over CWM shouldn't wipe my phone right? It's only the stock bootloader that requires a full wipe?

I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...

Clancy_s said:
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Click to expand...
Click to collapse
ah, that would probably do it...guess i'll just wait it out a little longer, thanks

I have the exact same issue as this Rom Manager refuses to see I have CWM installed so just keeps telling me I need to install it it also can't download and flash its own version and just freezes after download
So any updates on this or more users experiencing it ?

I think I've found the solution. In ROM Manager tap the menu button at the top and then tap Manual Flash Override. Next it'll ask you if you've flashed CWM manually so tap OK because that's what we've done. Next pick which GN you have and then choose CWM 3.x+. There you have it, it should work now.

Don't use ROM Manager - problem solved!!
Seriously, though, it's a TERRIBLE piece of software

I'm fairly new to using it but it seems decent, why is it so terrible? I had an eris before this and did everything manually through recovery, this seems like it's a lot better than that.

It's just more trouble than it's worth. Why not just manually flash CWM using fastboot and get your head around that as opposed to an app which can - frankly - break things?

Flashing it via fastboot is what causes the above issue. Since you flash it manually rom manager can't see it, that's why I posted the above steps to kind of "force" rom manager to see the manually installed version.

But if you're not using ROM Manager then what's the issue? Copy ROM to SD card, reboot to recovery, flash ROM...where is ROM Manager needed in that equation?

If you're not using it then there is no issue, but this thread isn't about using it or not, it's about getting it to work with the galaxy nexus when you manually flash CWM.

I like it for the backup and restore feature and being able to change the names used to backup