Related
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
I am new to modding my vibrant (phone is rooted but that's all) but looking to flash a new ROM. I dl'd rom manager and installed cwr. When I reboot into recovery mode via rommanager or manually doing it,I do not get the prompt to backup. Only options I get are to reboot system, reinstall packages, delete all user data, delete cache data, and format internal sd-card. Anyone know how to fix this? I just updated to 2.2 froyo UVKB5 kernel 2.6.32.9 if that helps.
looks like you have stock recovery.
try reinstall packages, might take a couple times..
or install CWM via replacing update.zip
What he said, yeah.
So just delete the current update.zip file on my phone and replace it with a new one? Any links to download the update.zip file?
Sometimes you have to Reinstall Packages twice for it to go from regular recovery to CWR. If you flash a custom ROM though, most have a custom recovery built in.
If you have to replace the update.zip (which I don't think that you do), this worked for me the first time I rooted.
http://forum.xda-developers.com/showthread.php?t=849028
How to Root.
I am rooted, but I want to back everything up so that way if I do not like the new custom rom I can go back. I tried reinstalling the update.zip file from the link but s till have the same issue. Any other solutions besides going back to stock and going from there? And if I did go back to stock, would I lose everything?
I backed up using Titanium Backup, is that the same as going into recovery mode and backing up?
Re-download recovery using ROM Manager, then repeat. Worked when I had a similar issue.
Tried that several times. I also reuploaded the update file and reinstalled the package several times. Still no luck so I think I might go back to stock using Odin.
Then DL Eugenes froyo don't brick ROM with the 2e recovery update in it, then re-install packages, maybe twice and you'll have the green recovery menu your seeking
Googled Eugene's DL and I do not feel to confident with it. Is it supposed to fix the issue with getting into recovery mode?
So I went back to stock last night using Odin, upgraded to 2.2, and rooted using Superoneclick. Phone's back up and running but faster than the first time I upgraded to 2.2. I still have the issue getting into the proper recover to install the zip file. I've read that deleting Slacker helped some people, assuming it freed up space on the System ROM. My system ROM was full until I started to delete some apps. I now have 20.7 MB free. Could not enough System ROM space be the issue?
I am now also getting a "Fail" attempt when I try and update su saying that it failed to find currently installed su binary. Any advice on fixing this?
TIA!!!
it would probably be easier to just odin back to stock jfd and then flash a deodexed kb5 build thats rooted with SU already in it from here in the forums.
http://forum.xda-developers.com/showthread.php?t=1036193&highlight=deodexed
If you flashed kb5 from kies or odin and don't want to reinstall the rom then you will need to flash a modified 3e recovery because you probably are not quite rooted and won't be able to use CWM until you flash the modified 3e recovery...
http://forum.xda-developers.com/showthread.php?t=833423
You might want to check out the AIO vibrant toolbox (pinned topic in the development thread) it will give you big easy buttons and instructions to flash back to jfd and root and flash a new rom if you need to... It comes with Odin so you can wander into the install folder and fire up Odin to flash the modified 3e recovery if you decide to go that route too.
If I flash a deodexed kb5 will i still be able to flash a custom rom?
I shall try to explain the situation best I can.
A long time back, I rooted my S2, then I thought I would sell it, so I wanted to put it back to stock and unroot, which I did.
Now months later, I decided to root the phone once again and put another rom on.
To cut a long story short, currently my phone wont accept any roms of any kind.
If I install CM7, MIUI, Sensation Rom, all of them seem to install a kernel as well, which causes the phone to panic upon boot. Which puzzles me, because if they are made for the S2, then why are they causing problems with my phone?
The only kernel that works for me so far is CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4. This allows me to access the internal SD via usb and put on roms. But I can't install them. As every time I do, I just either get a kernel panic or a black screen. I even used this guide, which should be foolproof and all I get is a black screen.
My phone has been in this useless state for 24 hours now and I've googled until I feel asleep at the keyboard.
Im hoping someone can seriously help me with this, as I don't pretend to know what I'm doing.
I was on ICS before this happened.
If you want your phone back then use the method in cnet to get it working again
and about the roms issue, did you factory reset and full wipe your phone before installing a rom?
I reset and wiped everytime. If I follow the cnet instructions to the letter, it just hangs on the Galaxy S2 logo when you turn on the phone and doesn't go any further. The only solution is to put on the kernel I mentioned above to get access to the SD card on my pc.
I now have managed to get CM7 RC working, but that's not the one I wanted. I wanted to use the Sensation rom, but that installs its own kernel which my phone, for some odd reason, doesn't like.
My phone details now are:
CM Mod 7.2 RC1
Kernel 2.6.35.14-g68ea119
[email protected] #1
1.Boot into recovery
2.Full wipe
3.Wipe cache
4.Advanced->Wipe dalvik cache
5.Install sensation rom zip only
6.Reboot
7.Wait for 5 mins
I followed your instructions precisely. I then installed SensatioN_ROM_3.0_ICS_i9100.zip from this thread
It installed, installed a kernel, flashed modem and said done. I then rebooted and waited.
It comes up with the S2 logo with the triangle, fine but now It just shows a battery symbol with a circle in the middle. After a while it goes to black and then comes back. Like its rebooting over and over.
I unplugged the usb cable and instead of the batter I just get the logo with the triangle. That stays there for a while, goes to black and comes back. Over and over.
I can't even get to recovery. Only thing I can do now is go into download mode and start over, put on the kernel I know that works, install CM7 RC1 and then at least I have a phone. But why sensation rom doesn't work is a mystery to me.
X82X said:
I followed your instructions precisely. I then installed SensatioN_ROM_3.0_ICS_i9100.zip from this thread
It installed, installed a kernel, flashed modem and said done. I then rebooted and waited.
It comes up with the S2 logo with the triangle, fine but now It just shows a battery symbol with a circle in the middle. After a while it goes to black and then comes back. Like its rebooting over and over.
I unplugged the usb cable and instead of the batter I just get the logo with the triangle. That stays there for a while, goes to black and comes back. Over and over.
I can't even get to recovery. Only thing I can do now is go into download mode and start over, put on the kernel I know that works, install CM7 RC1 and then at least I have a phone. But why sensation rom doesn't work is a mystery to me.
Click to expand...
Click to collapse
Don't install anything else
Repeat the steps without any modem or anything
Any try to redownload the zip
How do I stop the install of the modem? The thread only shows one zip file and if I install that in recovery, it installs everything. I can't chose what parts to install. Do I have the wrong zip?
X82X said:
How do I stop the install of the modem? The thread only shows one zip file and if I install that in recovery, it installs everything. I can't chose what parts to install. Do I have the wrong zip?
Click to expand...
Click to collapse
Just install this zip by the method above
https://docs.google.com/open?id=0Bzv8B0L32Z8lZ2hSanUtVHpSb0tFUlhkRVQ1RFhEUQ
Nothing else
While it downloads from google, I just want to clarify.
Wipe data, wipe cache, wipe dalvik. Then I go to install zip from sd. Find SensatioN_ROM_3.0_ICS_i9100.zip, then it installs. But the last time I did this, it scrolls up saying it was installing file system, then flashing kernel, then flashing modem.
Am I doing something wrong here?
And that google link is slow as hell, quoting me 7 hours to download it. Got it from hotfile instead, going to try that one.
X82X said:
While it downloads from google, I just want to clarify.
Wipe data, wipe cache, wipe dalvik. Then I go to install zip from sd. Find SensatioN_ROM_3.0_ICS_i9100.zip, then it installs. But the last time I did this, it scrolls up saying it was installing file system, then flashing kernel, then flashing modem.
Am I doing something wrong here?
And that google link is slow as hell, quoting me 7 hours to download it. Got it from hotfile instead, going to try that one.
Click to expand...
Click to collapse
Yes it should work like that if you have a i9100
Done exactly as you said. I downloaded it from the hotfile link instead and installed it.
Came up with the same thing.
Cleaning Old System files
Installing System
Data Files
Symlinks
Flashing Kernel
Flashing Modem
Ready
Then I reboot and the same looping over and over. Can't access recovery. Only solution is using odin to flash the kernel I used before and be forces to use CM7 since nothing else works.
It's so confusing as Im using the same hardware as everyone else on the sensation rom thread, but it wont work for me. at all.
you sure you have i9100?
GT-I9100
I'm totally puzzled. MIUI doesnt work, Sensation doesnt work and stops me from using recovery. The only thing that works is kernel CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.tar then install CM7 RC1 which upgrades the recovery to version 5 and the phone works. But only on CM7. If I try to install any other rom, it dies a death.
X82X said:
GT-I9100
I'm totally puzzled. MIUI doesnt work, Sensation doesnt work and stops me from using recovery. The only thing that works is kernel CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.tar then install CM7 RC1 which upgrades the recovery to version 5 and the phone works. But only on CM7. If I try to install any other rom, it dies a death.
Click to expand...
Click to collapse
And don't tell me that you flash cf-root after flashing every rom from recovery
No, I only flash that when the rom seems to corrupt it. Like when installing sensation. The only way I can access the SD card to put on another rom is to install that kernel.
X82X said:
No, I only flash that when the rom seems to corrupt it. Like when installing sensation. The only way I can access the SD card to put on another rom is to install that kernel.
Click to expand...
Click to collapse
This is really weird
Maybe someone else can help you
Sent from my x10i using Tapatalk
ok lets try again........
1: forget everything [ideas you have.]
2: go into clockwork recovery
3: format every partition including system / boot [remove your sdcard before starting]
4: use odin and flash stock 2.3.6 LA2 [u can flash whatever you like] and let it boot.
5: now use cf-root and root your device [http://forum.xda-developers.com/showthread.php?t=1103399 ]
6: i assume you know your way from here.
note: its very important to format system / boot partions
if yo dont have cwm or you want to try from scratch heres the latest cwm
http://www.mediafire.com/?wkki6xahfhb3bim
Thanks for info. Just to clarify, the cf-root link contains loads of different ones. How do I properly know which one to use or doesn't it matter? And as for the stock 2.3.6 LA2, again, where do I find that? Reason I ask dumb questions is I don't want to assume and try the wrong one and come back here and complain when it was my fault, I just want to be 100% sure, so again sorry for the obvious questions.
I flashed I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME then CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.
It seems to be working fine now with the default rom. However, when I go into recovery to say perform a backup or mount the sd card, It won't have any of it.
When I try to mount the sd card it just says "error mounting sd card" and when I mount usb storage it says "unable to open lunfile (no such file or directory)". So I don't want to try another rom yet.
X82X said:
I flashed I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME then CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.
It seems to be working fine now with the default rom. However, when I go into recovery to say perform a backup or mount the sd card, It won't have any of it.
When I try to mount the sd card it just says "error mounting sd card" and when I mount usb storage it says "unable to open lunfile (no such file or directory)". So I don't want to try another rom yet.
Click to expand...
Click to collapse
lol when i said or what you want i meant from GB you flashed a ICS ROM. well do this and this time just do what i say......
use odin again and flash XILA2 . after boot dial *2767*3855# [a must]
after reboot you should be running a problem free ROM.
now from CF-root find LA2 and flash that now play with it a while and than you do whatever as now you know where and how to get back to working ROM.
plus after LA2 you will find everything on your phone works so any problem you get on other roms is not hardware
recovery issues should be fixed now. otherwise use odin and again flash that cwm file i posted earlier. you wont loose root
Download ROM from Here
I am currently trying to flash my vibrant back to stock 2.2. My latest attempt was done using the AIO tools. Every method I have tried has lead to the Vibrant boot screen appearing for a few seconds, and then rebooting. Any suggestions?
Have you tried Odin?
Sent from my SGH-T959 using XDA
whatever5 said:
Have you tried Odin?
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Yes, I have tried Odin with and without AIO tools. In all of the threads I have looked at, the answer seems to be flash back to 2.2 stock, but that is what I am trying to do. Thanks.
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Woodrube said:
Try to boot into recovery and factory reset and see if that breaks the bootloop. If not, see below.
*********
Do you have a nandroid backup of the 2.2 you were on an using? If so, I suggest Odin-ing to stock (2.1), then pull the CWR from my signature put it on your internal card and label it Update.zip. Boot into recovery and hit Reinstall Packages. It will cycle through and you'll have to hit it again. It will cycle through again and your stock (blue) recovery will go to CWR (green). From there you can restore your nandroid backup of the 2.2 you last made (or should have).
You can go to 2.1 using the toolbox, as it has the correct pit/tar files to do so.
Click to expand...
Click to collapse
I currently can not get into recovery mode. I am holding the power, vol+, and vol- buttons, inserting the battery and then releasing them when the vibrant screen appears. But it just continues to boot cycle.
I flashed the pit and tar that came with AIO tools. No go. Still just boot cycles. Sorry for being a pain.
I do have a backup, but I am not sure what I can do with right now.
Try turning the phone off, plug in USB hold just volume up and power on the phone..... that should put it into download where you can run Odin and flash back to stock
Sent from my touchpad using XDA
related problem (sort of)
Solved: problem solved. I reflashed CM7 over the bootlooping mess, and it took. Then I was unable to get AIO Vibrant Toolbox to recognize that debugging mode was on, even though it was. So I just copied the files over and went through a massive round of forcing the zip files on again and again. I now have Slim 3.5 on my phone, so I can start playing with it.
*****************************************
I'm an extreme noobie, trying to upgrade my T959 to ICS. I've picked Slim 3.5 (latest release version as of this week) as my first attempt (but really any simple but well-functioning ROM will do for me).
I've rolled back to Eclair (from the official Tmo Froyo upgrade way back when), rooted, and numerous times followed various directions to install the zip for Slim -- sometimes trying CM7 as an intermediate step. The CM7 install failed in the same way as the ICS, as described below.
I've done it with and without AIO Vibrant Toolbox. I've used ClockworkMod Recovery 2.5.1.2 to wipe the data, clear both cache partition and Dalvik cache, and format system. I've popped the zip file in various folders and at toplevel, both external and internal SD.
In all cases, it gets off to a good start, and then I'm left with endless bootlooping: Vibrant logo, Mod logo, a textblock of about 15 lines, repeat. I've always been successful after that in using Odin3 v1.81 to get back to Eclair.
I got sucked into a tech vortex until 4:30 am last night trying again and again, and I'm way way too old for that!
Any thoughts?
This is my first time posting.
I am a noob, but I am trying to get beyond that. I have flashed kernels and ROMS to my GT-I9100, with success. The other day, I was going to flash a new ROM, and I tried to make a Clockworkmod backup of my current ROM...while the phone was charging. Is this a major blunder?
The reason that I ask is that CWM crashed in the middle of the backup, and now I can't enter CWM recovery and the phone doesn't boot properly. I just get stuck in a bootloop. I can get into download mode. I used Pistachio's post about how to fix a soft-bricked GS2 to flash back to stock thru Odin. Then I used CF-ROOT to re-root the phone. After that, everything works fine, and I can get to Android recovery mode. Then when I try to flash a ROM, Titanium Backup must be restoring the previous version of ROM Manager, and I get stuck in the same bootloop when trying to get into CWM recovery.
Is Clockworkmod corrupted? Did the recovery partition get corrupted? Should I flash back to stock, delete ROM Manager, then re-install it? Should I bite the bullet and delete my Titanium Backup folder, then re-install everything from scratch? Should I flash back to stock with Pistachio's .PIT file and tick RE-PARTITION?
I looked for an answer specific to this problem, and cannot find the exact same scenario in any other threads. There are similar problems, but I think that I have a CWM app or recovery partition problem, or I may have a NAND rw corruption. I don't think that it is a NAND rw corruption though, because I can flash different kernels and ROMs.
I have been using Resurrection Remix versions 2.2, 2.4.1, and 2.5.3.
I have been using Siyah 3.3.2 kernel.
Please help, and excuse my noobness if I am beating a dead horse with this question.
Sounds like Rom Manager borked CWM/CWRecovery, which it seems to do on SGS2 quite a lot.
Most of the scenario you outlined in para.3 of your post (back to stock, delete ROM Manager) sounds like a good WTG, but do not reinstall it.
If you're going to use a kernel which has CWM/CWRecovery (like Siyah), do not use Rom Manager at all. Uninstall it & keep it that way. CWM/Recovery can do pretty much everything Rom Manager can, and you're playing with fire having both on the phone. Eventually Rom Manager will bork CWM again if you use it.
In the first instance, go back to stock, re-root your phone & reinstall the rom/kernel you're wanting to use. If Rom Manager is installed by default, uninstall it before you do anything else. With a bit of luck, you shouldn't have to do anything else (like messing around with PIT's which you also mentioned in para.3). If you batch restore your apps with TI, make sure you don't restore Rom Manager.
Thanks for the speedy reply.
I will try what you have suggested, but how do I flash the .zip file from my phone without ROM Manager? Do I have to do it through Odin?
Yep, that's right. Get an Odin flashable rom from Intratech's thread (search for it on here). If links in that thread don't work, search here or Samfirmware.
Edit - And once you've got your phone back up & running the way you want, use CWRecovery to do all your flashing.
My apologies, I should have been more specific. I want to flash the RR 2.5.3.zip. Should I still download it to the PC, then flash through Odin, or can I use Android recovery to do it through the phone?
OK. Let's rewind a bit.
What state is your phone in right now ?
I am flashed back to stock, and about to use CF-ROOT.
OK. Root the phone, CWM/Recovery will be installed by default. Once the phone is rooted, reboot into CWRecovery, flash your RR zip & you should be GTG. Just remove Rom Manager if it's installed as part of that process before you do anything else (including backing up). If you're going to restore a backup, again, uninstall Rom Manager immediately after you restore.
OK, after I flash CF-ROOT, I will re-install Titanium Backup, and delete ROM Manager to be safe before proceeding. Then I will flash the ROM.zip and test CW recovery and reboot again. I will reply after doing so.
Thanks
ARRRGH!
After flashing CF-ROOT I cannot get to the splash screen upon reboot. I made sure that I ticked USB debugging before flashing the kernel. I can still get into download mode and CWRecovery, so I flashed back to stock, and tried again to no avail. I tried flashing the RR 2.5.3.zip, in CWRecovery, and it flashed. I get to the splash screen but no further. I feel like a terrible noob now, because yesterday I had the phone flashed to stock and rooted no problem. Is there something that I am missing? I made sure that I used the proper CF-ROOT kernel.
So you're getting bootloop when you flash RR ? Have you tried booting into recovery & doing a wipe/factory reset ?
I believe that I am fixed.
I restored a Nandroid backup of my stock ICS from right after my original rooting, and the phone booted fine. I did a wipe/factory reset and wiped cache. Then I flashed RR 2.5.3. The phone rebooted fine again. I IMMEDIATELY uninstalled ROM Manager and made sure it was out of Titanium Backup as well. I have rebooted several times, normal, download, and CWRecovery, and everything works as it should. I think that I am getting over my noobness.
I WILL NEVER INSTALL ROM MANAGER AGAIN...DOWN WITH ROM MANAGER!!!!!!!!!!!!!! Except for the Little Alex icon, that's still pretty cool.
A thousand thanks for your help. At least I was on the right track when I first asked for help. I was pretty sure it was a problem with ROM Manager, because when it crashed, it started this whole mess. I'll be sure to press the THANKS button for your help, and I'm going to thank Pistachio for his thread as well.
Not n00bness, stuff happens sometimes ;-) You weren't the first person to get tripped up by Rom Manager (I did not long after I got my phone), and you won't be the last.
Yep you had a fair idea of what might have caused it, and your detailed OP certainly made it a lot easier to work out WTF was causing the problems.
No probs. Glad you got it sorted ;-)