Ok I've been reading and reading these threads and have found a lot of great info. Right now my phone is useless so I guess I'm asking for a little more specific info for my current situtation. I used mskip's toolkit to root my phone then followed wwjoshdew's video on how to use goomanager to flash CyanogenMod 10.1.2. Everything seemed to be going fine when I got the spinning blue circle screen then came the "Unfortunately, setup wizard has stopped" and "Unfortunately, the process com.google.process.gapps has stopped". Over and over and over. I can get to download mode and recovery mode but not sure what my next coarse of action should be. This is on an AT&T galaxy s3 originally running 4.1.1. Thanks in advance to any and all help....
I wouldn't use goo manager to flash anything!! U should have flashed straight from recovery, be it cwm or twrp. Did u perform a nandroid backup before u flashed cyan? If so, I would wipe, factory data reset, and install your backup.
Have you tried reflashing Google Apps?
Reboot to recovery, clear cache/dalvik, reflash GApps, clear cache/dalvik again to be sure all is tidy.
Also be sure you have the correct version of GApps; that has messed me up at least once.
Other than that you can always retry the whole process i.e. CM and Apps
Thanks for the replies. I'll try and figure that stuff out. Only reason I've gotten this far was because I was following the toolkit prompts and did the steps in the video as he did them. This is the first time I've tried anything except updating to JB so...
Well, I can't say I've made any progress. I googled correct gapps for cm 10.1.2 and downloaded it but it's like a big collection of stuff that odin won't put in the PDA file spot. I'm not even sure if its the right one. I'm so lost right now. I see all these cwm and twrp recovery files in the toolkit files but not sure if they would help me or not. I know this is fixable since I can still get into recovery and download mode. At this point I would even just go back to stock at least that way I could get rooted again through the toolkit. I'm guess I'm such a noob that I need step by step. I feel like my right arm is missing not having a phone...
Ok I have 2 different versions of gapps that claim to be the right one. I would love to try flashing them to try them out but odin doesn't see them. What am I doing wrong?
Which recovery do u have installed on your phone?
For one dont use odin to flash any custom roms, first download the latest cyanogen mod and gapps, if you need the latest gapps you can get them here. Next you are going to want to boot to recovery and do a factory reset/full wipe then wipe cache/dalvik cache, next go to the top and select load zip from sd card, install cyanogen mod and gapps and reboot the phone.
Ok something different happened this time when I went into recovery. TWRP v2.3.3.1 showed up. I wiped the cache/Dalvik and did the factory reset from there. I have cm-10.1.2-d2att and gapps-jb-20130301-signed ready to copy somewhere. I opened the internal card and saw 8 or so icons that said local disk. so I created a new folder and put the cm and gapps files in there. Does that sound right?
Well that seems to have worked. Rebooted and went through all the google stuff. I'll test everything and see how it works
Glad u got it working!! I usually download Roms straight from my phone, over WiFi of course, and place on the root of the SD card, not in a folder, and flash from there...
Related
Ok so, I was flashing CM7-GX4...everything was going fine until I flashed GAPPS, now I'm stuck at two screens alternating between the CM7 boot animation and the screen that says "Welcome to PC36100", upon this screen loading it quickly restarts the CM7 boot animation, so on and so forth. I am able to get into CWM recovery. Please help.
Thank you in advance.
thats a boot loop, looks like you want to wipe everything and try again
elegantai said:
thats a boot loop, looks like you want to wipe everything and try again
Click to expand...
Click to collapse
What if the PC36IMG file is renamed? I changed the name previously per the instructions of some thread I saw somewhere. Could this be the problem?
well you lost me at the hboot image. The only time i have ever had to use a file like that is when i was rooting my phone.
I also do not use cwm, so i am kinda limited in the help i can provide. Did you wipe your system/data/cache before you flashed cm7?
I wiped everything. I've put the SD card in another phone and renamed it back to PC36IMG...lets see what happens LOL
Renamed file back to PC36IMG...still stuck in boot loop
What exactly are you using the pc36img for?
elegantai said:
What exactly are you using the pc36img for?
Click to expand...
Click to collapse
I'm not using it for anything. It's just there from back when I rooted the phone. I had renamed it a while ago. Everything was going fine, install CM7 GX4 ROM, rebooted, attempted to install GAPPS and thats when I got stuck going back and forth between the two screens. I have put the SD card in another phone and renamed it to the original PC36IMG (figuring since I was stuck at a screen saying Welcome to PC36100 it couldnt find the file or something), and I'm still having the same problems. I've wiped and wiped and wiped using CWM and reinstalled CM7-GX4 several times and am still getting the same bootloop.
I'm running a restore from CWM...hopefully that will take me back to a point where I can do something.
yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from:http://mirror.teamdouche.net and grab the gapps from: http://goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.
elegantai said:
yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from: mirror.teamdouche.net and grab the gapps from: goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.
Click to expand...
Click to collapse
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!
nooomoto said:
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!
Click to expand...
Click to collapse
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!
elegantai said:
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!
Click to expand...
Click to collapse
I used the gapps from your source and everything went fine. Thanks again for the help!
no problemo, glad you got it working!
Noob here. No longer a virgin after this post. Ok, I have been reading for weeks and have most of the basic understanding down on phone setup and flashing using ROM Manager/CWM but still having issues I can't find answers to so here goes.
Samsung Captivate running 2.2 flashed from ODIN one click. Backed up apps and data using TI backup. I have installed ROM Manager, picked the Dragon ROM to flash and here are my problems.
1. ROM Manager 4.2.0.2 - Pick Flash CWM Recovery- 2.5.1.2, pick captivate, "successfully downloaded CWM Recovery" (did not say "installed" CW Recovery). Where did it download to and how do I install? Its not in My Files. Some of the recovery options are missing when in Sys recovery <3e>and don't look like the options listed in posts.
A. Tried to backup current ROM with RManager - It gave me a stamped file name, said "backed up" within a few seconds but when I click "manage and restore backups" I just get a black screen. Can't find the backed up ROM nor the files listed on one of the posts??? I read it takes several minutes and the copied files scroll. This did not happen.
B. Install ROM from SD card - Everyone has said make sure the ROM is installed in the "root", but exactly which file are we talking about??. No one ever says which file exactly. I use Droid Explorer and there is a file named SD Card, then SD. Which file is the ROM to be installed in? No file called "root". I used SD file and renamed it update.zip. I click "install ROM from SD" then pick SD and the update.zip file, click all three options (B/U ROM, wipe data N cache, dalvik cache then ok. Phone reboots, click reinstall packages, ERROR: E:failed to verify whole file signature - E: signature verification failed, installation aborted.
2. I have read to reinstall 2.1 via ODIN before flashing new ROM's. Trying to flash "Dragon ROM RC7" "Full Flash" which is 2.2.1. Can I not just flash this over 2.2?
I know there is more. I was up till 2 last night and tried to get all issues posted here. Like I said, pretty new to the ROM thing but not a dummy and can follow instructions. Have read a ton but there is sooo much out there. If anyone can help me through this I would be very greatful. Hitting the frustration point real quick now.
Found this: ROM Mgr 4.2.0.2 "Samsung users: You must flash a Clockwork compatible kernel first." This could be one issue. Which kernal? Have not tried to flash any kernals yet. Still reading.
Same issue
I'm having the exact same issue. Tried install and uninstall, no go.
Which part did you have a problem with. I have resolved the CWM issue and the errors I was getting in recovery.
you should youtube a tutorial on how to do this... it will take 10 minutes to explain how to do it all and it would be easier than going back and forth through forum messages. google can be your friend also if you just use it. if you eff it up too bad you can always put your phone back into dl mode and odin it back to stock.
True, Google can be you're best friend but at the same time, I was able to find a detailed fix right on the forum. After another hour or so of searches. Just installed my second ROM yesterday and running great. Chose the Dragon ROM for the Captivate. It's Great!! and I happen to be a fan of Dragons!
http://forum.xda-developers.com/showthread.php?t=884364
And for phone specific questions post them in the phones forum, though not in developers forum
i found that rom manager does not work for certain phones, period. i use odin and flash cwm 2.5.1 to my phone while in download mode. then i can use the 3 button combo to get into cwm,oh yeah and dont forget to back up your rom version once in cwm! i then wipe cache (user data) and delvic cache and batt stats. then i go into a folder i created on "root" (which i made on the sd card) i store my roms/kernels themes ect...in this folder i pick which rom to install "please do your homework" make sure u know which rom ect, is right for your phone, or u will have a nice shinny paperweight!!!
ok so, now your in your folder with the rom of choice, flash install from .zip let it install.......takes awhile just be patient. thats about all i can say. took me awhile but its well worth it, i have a way better understanding about everything now. hope it helps, i own the mesmerise and found rom manager is useless for this type of application so ditch it!
What happened: Samsung Galaxy S2 tmobile SGH-T989 (more info at the bottom)
Ok so I installed the usb drivers through kies and got the latest firmware from kies. Installed Odin 3.07. Backed up my stuff. Flashed recovery-cmw-hercules using Odin. Then I rooted my phone using tmobilegalaxys2rootICS (flashing with CWM recovery) and installed CWM-SuperSU v0.87. Updated root and CWM on the next boot using SuperSU app and Rom Manager to the current version (non touch for CWM). I then got cyanogenmod9.1.0-hercules (stable) and gapps-ics-20120317-signed. I wiped the internal SD card and external SD card. Went into recovery manager. Did a factory reset, cache wipe, dalvik wipe, battery stat wipe. Flashed cyanogen9, flashed gapps, fixed permissions and rebooted. Now i'm stuck in a bootloop just looking at the start up screen of cyanogenmod. I have access to the recovery menu and the odin screen so i'm not bricked as far as i know, just bootloop'd. I read somewhere of a super wipe by JDT or someone along those lines but i can't find those scrips to flash them. Any help would be great. Thanks!
Info:
Computer OS: Windows 7 Ultimate (64-bit)
Firmware Version: PDA:LH1 /PHONE:LH1 / CSC:LH1 (TMB) - (Ver. 12.07.20.02) (current)
Binary: Samsung Offical (Kernal 3.08 ICS)
Build Number: IMM76D.UVLH1
ROM: Stock T-mobile Android 4.0.4 (before i flashed cyanogenmod9)
Baseband Version: T989UVLH1
Brand: Samsung
Model: SGH-T989 (hercules)
Type: Galaxy S2 X
Carrier: T-Mobile, USA
Country Code: 1 (USA)
Access Point: epc.tmobile.com
Odin3: v3.07
Clockwork Recovery: v5.0.2.7
Root: tmobilegalaxys2rootICS -> CWM-SuperSU-v0.87 (updated can't view newer version right now)
Cyanogenmod9: cm-9.1.0-hercules
Google Apps: gapps-ics-20120317-signed
spikeguy4 said:
What happened: Samsung Galaxy S2 tmobile SGH-T989 (more info at the bottom)
Ok so I installed the usb drivers through kies and got the latest firmware from kies. Installed Odin 3.07. Backed up my stuff. Flashed recovery-cmw-hercules using Odin. Then I rooted my phone using tmobilegalaxys2rootICS (flashing with CWM recovery) and installed CWM-SuperSU v0.87. Updated root and CWM on the next boot using SuperSU app and Rom Manager to the current version (non touch for CWM). I then got cyanogenmod9.1.0-hercules (stable) and gapps-ics-20120317-signed. I wiped the internal SD card and external SD card. Went into recovery manager. Did a factory reset, cache wipe, dalvik wipe, battery stat wipe. Flashed cyanogen9, flashed gapps, fixed permissions and rebooted. Now i'm stuck in a bootloop just looking at the start up screen of cyanogenmod. I have access to the recovery menu and the odin screen so i'm not bricked as far as i know, just bootloop'd. I read somewhere of a super wipe by JDT or someone along those lines but i can't find those scrips to flash them. Any help would be great. Thanks!
Click to expand...
Click to collapse
Hey! As of I know, you are not using a TOUCH recovery. Sad to say but a lot of ROMs will only work on TOUCH recovery, because they changed something in the Cache wiping that ain't screwing up with device or something (as I understood digging up a little bit).
Here is my advice, go with this for now:
MIRROR
It's v13.1 of Sk8er's recovery. Though I want to tell you, if you try to hardboot into it (what I mean is: hold +/- volume and plug in USB) it probably won't work since it doesn't work for me for a weird reason (I'm on v13.0 so I couldn't say for v13.1).
In EXTRAS you got the cache.wipe and the super.wipe of TDJ.
And another thing I think you should know about this device is HOW TO FLASH CORRECTLY.
Here is the way:
Make a backup (optional)
SUPER WIPE (using TDJ tools)
Factory Reset (wipes data/cache/.....)
Install your rom (without GApps)
Reboot phone.
Wait for let's say 10 minutes (optional as well I don't do it but it's recommended... Just reboot, and when you see no bootloop, go back to recovery for next)
Wipe cache/dalvik (without using TDJ but only from recovery touch)
Install gapps.
Reboot.
if you just update your rom, like going from a nightly to another nightly, no need to follow this. Just wipe cache and dalvik using recovery touch, and you are good going.
Cheers!
I'll try it!
Thanks switchfoot! I'll try this today. I'll grab the cache wipe and super wipe as well as upgrade to touch-cwm however i'm a little worried when you say skaters mod made you unable to hard boot, seems risky as that's your last resort if you brick the device (as far as i know). Thank you so much for the steps on flashing, I read so many different ways I was very confused on the proper procedure. I have class today so I probably won't report back till later today but i'll let you know what happens!
spikeguy4 said:
Thanks switchfoot! I'll try this today. I'll grab the cache wipe and super wipe as well as upgrade to touch-cwm however i'm a little worried when you say skaters mod made you unable to hard boot, seems risky as that's your last resort if you brick the device (as far as i know). Thank you so much for the steps on flashing, I read so many different ways I was very confused on the proper procedure. I have class today so I probably won't report back till later today but i'll let you know what happens!
Click to expand...
Click to collapse
My friend here is a flawless recovery with 0 issues if you are worried about the one above TWRP 2.2. Also stay on one site for everything and may I suggest xda only. Do not venture off not that the other sites are issues just that you will confuse yourself although rootzwiki is just as good.
There is plenty of How To's here in xda that you do not need to be confused, confusion comes when you start asking others there opinions and take bits and pieces from all of them... Good luck and feel free to pm me if you need any further help... Just please read up before you do anything
These are the exact instructions from CM on how to install their rom: did you follow these instructions
Installing
How to INSTALL from another ROM (DO NOT SKIP ANY STEPS!):
Be sure to back up your current ROM!
Update your radio to the above recommended version if you have not already done so. (See the list below)
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON NON-TOUCH CWM RECOVERY: Install darkside-wipe-cache-only.zip (which fixes bootloop due to bad /cache format)
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
Awesome!
Wow that's exactly what i was looking for! Thank you! I just flashed a stock rom to go back to the start. I'll begin the process over again following these steps. The only issue is that the radio update section in the guild no longer exists. Is it ok to go on without the radio update? Or will this cause issues? If so is there a mirror for them?
SOLVED!
OK! I'm all set now. I had to use the full wipe as well as the cache wipe after install and the bootloop was resolved. The bigger headache was when kies failed at updating the firmware so i had to do an emergency firmware flash. Any way i have clockwork, root with SuperSU, cyanogenmod9.1.0, and the latest google apps! Plus its backed up now! YAY! Now i just have to configure it to how i like and we'll be in business! Thanks for all your help guys! I really appericate it!
Last thing
I still need the radio update since the file no longer exists in your link. Everything is good but I don't have any wifi calling or features of that order. Which are important in keeping my usages down and getting coverage in my house and otherwise bad areas. Where do I get this and would I just install it via CWM? Thanks again!
Hey guys, I was playing around on my phone, and I downloaded something off of 4shared (just a game) and it crashed and made my phone freeze. I then held my power button and waited for it to boot but now im stuck in a bootloop with the stock telus rom... is there anything I can do that wont wipe everything on my phone? Oh and I can get into both CWM recovery and download mode.
I gave it some more time to startup and it pretty much factory reseted my phone. I get that thing to setup my phone after startup. Everytime I turn my phone off it goes back to this screen and my phone restarts. If I surf through the files of my phone, it shows I still have everything but It doesnt show any of my apps or anything.
Hey -
First of all, thanks in advance for any help. I never thought I'd be one of the folks posting a "help, I killed my phone" thread, but I don't have a choice!
I was running AOKP JB Milestone 1 and CWM, and decided to flash TWRP 2.3.something and the new AOKP JB MR-1 build. I did a backup in TWRP, ran Ti Backup, and installed the new build and gapps that I dl'ed from GooManager. I wiped dalvik and cache. When I booted, every app crashed and the phone was unusuable, so I went back to TWRP recovery and did a factory reset (after googling to confirm that it would not delete my GNex's sdcard, so I should still have my backup images).
Now, I get past the AOKP boot animation, but the Setup Wizard appears, then stops. Clicking "ok" leads only to another "Unfortunately Setup Wizard Has Stopped" box. Infinite loop. Bad news.
What is scaring me is that I can't find any recovery images to flash in TWRP, and don't see them even in the /0 folder on the SD card. Now I'm thinking I somehow erased my backups, and have a version mismatch. I thought I had TWRP 2.3.3.0, but the recovery says 2.3.1, so I'm wondering if I have an ICS/JB issue.
Anyway, I'm clearly stumped. Do I need to start from scratch and load CWM and a stock image via my PC? I don't think I can load anything any other way, but can't try that until later today.
Thanks again for any advice...
Ok, not sure what is going on, but after multiple reboots I could at least access my roms via TWRP and was able to reflash and get past where I was stuck. I'm hoping a new flash of the current gapps package will at least clear this up enough to see if my data is gone...
What gapps version were you using?
Sent from my i9250
Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.
jrodcamaro said:
Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.
Click to expand...
Click to collapse
I'm going to assume you're able to boot into a custom recovery (CWM). I persoanlly use TWRP, but either will work well for this. If you can't go through the root process again, based on qbking77's thread. Check out the videos and learn how to use Odin to gain root and a custom recovery. (always good to take a refresher course).
Here are directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Make sure the zip of the Rom you downloaded is on your externalSD Card or the root directory of your internal memory.
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's a certainty that at least one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though, as you never know exactly what might be left over from your old Rom (especially when going from 4.1.X to 4.2.X or vice-versa).
Also while in the Wipe menu, wipe Cache and Dalvik Cache (can't hurt).
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
MOAR rom already installed. If, in the future, you flash an AOSP Rom, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms (such as the MOAR Rom) have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
I could tell you but from what you're asking, honestly I think it's better not to and to force you to read a lot more. I am pretty new to this stuff too, joined this site in like march but I did about 3 weeks worth of reading before I rooted and flashed my first ROM. I'm not trying to be mean here but the question you're asking will be the least of your worries once you read a little more. I recommend you read this Q&A thread, it's also at the top of the Q&A forum.
Edit: It seems good guy topherk here gave you the info, I stand by what I said though, from a fellow newbie to another
jrodcamaro said:
Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.
Click to expand...
Click to collapse
Download the rom on your pc and transfer it to your sd card or internal sd card on your phone. Don't put the rom zip file in any folders as it's easier to find, commonly referred to as the root of your sd card. Power off your phone if your still on stock, after it shuts down hold the volume up button+the home button and then hold power button, this will take you to your custom recovery. First thing to do once in your recovery is make backup of your current rom, make sure you have at least 3GB free space on either your sd or internal sd, some backups can be even bigger, if you don't have space it should tell you. After your backup is done, wipe cache, dalvik cache, factory reset and then flash your rom, after it's done and you see it was successful, fix permissions and reboot...you should be good to go at that point. If all is running well you can boot back into cwm, select restore and only restore /data, to get all your apps and their data back, fix permissions again and reboot. You can use titanium backup or my backup root /pro to restore apps and data but personally I don't prefer those methods. If you have any issues, restore your backup and try again.
I see I was slow again as topherk said everything and then some lol...still posting this just in case it helps at all.
Edit; just to throw it out there I'll tell you how I do things, once your more experienced this could make flashing roms, kernels, tweaks ect, easier. I always make a backup first before I switch roms. Then I simply wipe cache, dalvik cache, flash new rom and fix permissions....reboot and enjoy, this is known as a dirty flash, some roms don't dirty flash well, some work great.
Also I always 100% of the time download roms, kernels ect straight from my phone, never had a bad download that I'm aware of, I don't check md5 sums, I just verify the size of the dl matches what I dl'd. My dl's go to my download folder on my ext sd card so when I go into recovery, I know to look in my download folder on the ext sd card.
Other things to note about dirty flashing if you choose to do it, figure out your rom issues quietly and it can't hurt to try dirty flashing if you always remember rule#1.....make a backup first. If you get stuck in a boot loop, just pull the battery, put it back in and 3 button boot to recovery and restore your backup.
Yeah, the main reason I prefer a clean flash is that when people dirty flash, any and all problems will not be supported by the developer. And since the person is asking how to flash a Rom, I doubt that they'd know what to do with a FC. I'd prefer if they would do a clean flash until they get used to it. I do all my app backups in Titanium Backup, and even then I have to be careful not to restore something that might mess up the new Rom.
Anyways, I really liked your advice with the backups: if you're ever stuck in a bootloop, you can just restore your backup. I recently tried out a new Rom that I wasn't too fond of, and in a few minutes was back to my LiquidSmooth. No sweat.
Sent from my SPH-L710 using xda app-developers app