Related
I tried a ROM update today (Magnolia) and my phone is now seriously slow (including SpeedTest which shows about 50Kbps download speed). I attempted to reinstall the same ROM and to restore a Nandroid (neither of which has helped). I did every wipe present in CWM v2.5.1.2 (I know v3.x.x.x is not a good wiper) and in HBOOT, also all to no avail.
It is possible that the ROM is focused on carefully updating itself rather than completely overwriting.
Does anyone have a recommendation as to the best way to really ensure that no old runaway processes are surviving the flashes (ROM or Nandroid)? I am wondering if flashing another ROM would do it (it wouldn't try to update), but am very open to suggestions.
Thanks!
I had the same problem when I would install a rom with the CW 3.0.0.8 and it will just update the current rom, and not do a full wipe like I just to get before with the CW 2.x.x.x what I have done to get a clean install is this...
- I dont use the Rom Manager no more to update...
- Boot into Recovery and do the Following before you install a new Rom..
1-) Wipe Data/ Factory Reset
2-) Wipe Cache Partition
3-) Install the Rom .Zip with CW
Thats how I have done it before hope it helps...
Dont use rom manager to install go into recovery. Do a factory reset twice, then goto mounts and storage and format manually, data, cache, system, boot. Do that twice or more and youre super wiped as you put it. But as far as magnolia goes...did you make sure that you dl'd the flashover and not the whole rom?
Sent from my ADR6300 using XDA App
Thanks
Pete - Thanks. I never use RomManager to do ANYTHING (and remain surprised that people do). I do factory reset and wipe in CWM but never formatted system; which I just posted in the Magnolia forum as being what I thought is causing all the trouble. At least this lets me know how to manually do it. Thanks
1107963 said:
I had the same problem when I would install a rom with the CW 3.0.0.8 and it will just update the current rom, and not do a full wipe like I just to get before with the CW 2.x.x.x what I have done to get a clean install is this...
- I dont use the Rom Manager no more to update...
- Boot into Recovery and do the Following before you install a new Rom..
1-) Wipe Data/ Factory Reset
2-) Wipe Cache Partition
3-) Install the Rom .Zip with CW
Thats how I have done it before hope it helps...
Click to expand...
Click to collapse
Building on this- I do EVERYTHING from recovery. In addition to the steps listed I also go to "mounts and storage" and wipe /system, /data, /cache, and /boot. Eradicate!
Sent from my ADR6300 using XDA Premium App
I gave out a loud guffah when reading this thread title. Maybe stuff's just funnier before having coffee.
johnchad14 said:
I gave out a loud guffah when reading this thread title. Maybe stuff's just funnier before having coffee.
Click to expand...
Click to collapse
Right? Super Charmin came to mind right away.
Sent from my ADR6300 using XDA App
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.
eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?
teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!
I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.
Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.
SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu
Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk
please help me
I try about 3 roms and when I try to install new app the device reboot..
what should I do ??? please help me X_x
Which roms did you use?
Model: Wildfire S A510e
Recovery: unofficial CWM
Rom: JxMatteo_ROM_V1. 1 with Link2sd - OC - Rooted
apparently freezes and reboots can be a problem if you forget to clear everything before installing custom roms....so you need to do factory reset, clear all cache, clear dalvik cache or whatever it's called, then install rom.
this didn't actually work for me when i tried to put CM7 on my phone, i've ended up clearing it all, formatting evrything and just going back to stock because CM7 was so unstable on my phone.
but if you forgot to clear everything when you first installed, try that first?
Hope you get it going. If not, you can also install stock, but you can still partition the sd card and use link2sd to give you basically a gig of "internal" storage (it lets you install pretty much all apps to the 2nd partition on the sd card. running very well now on mine.
I was just about to create a thread about this problem. I flashed m1ndh4x8r's ROM onto my device after a bad experience with the CM7 nightly, fully wiped, permissions fixed. I was on that exact same ROM the day before flashing CM7 and it was working perfectly, did everything it said it would, apps installed just fine. And the first time I installed that ROM, I didn't wipe a single thing.
So, now I'm thinking we should revert to the stock ROM, then flash this one back over it with no wipes, then if that doesn't work, revert to stock again and try flashing the ROM the proper way, wipes and all.
I'll try fixing this every way I can. I'll tell you if I find a fix for myself that you could use as well
matt5eo said:
Which roms did you use?
Model: Wildfire S A510e
Recovery: unofficial CWM
Rom: JxMatteo_ROM_V1. 1 with Link2sd - OC - Rooted
Click to expand...
Click to collapse
1- JkantaruROM XE
2- alquez cyanogenmod 7
3- m1ndh4x8r
Gloris said:
apparently freezes and reboots can be a problem if you forget to clear everything before installing custom roms....so you need to do factory reset, clear all cache, clear dalvik cache or whatever it's called, then install rom.
this didn't actually work for me when i tried to put CM7 on my phone, i've ended up clearing it all, formatting evrything and just going back to stock because CM7 was so unstable on my phone.
but if you forgot to clear everything when you first installed, try that first?
Hope you get it going. If not, you can also install stock, but you can still partition the sd card and use link2sd to give you basically a gig of "internal" storage (it lets you install pretty much all apps to the 2nd partition on the sd card. running very well now on mine.
Click to expand...
Click to collapse
how can I go back to stock ?? and what is CM7 meaning???
johnnyspritz said:
I was just about to create a thread about this problem. I flashed m1ndh4x8r's ROM onto my device after a bad experience with the CM7 nightly, fully wiped, permissions fixed. I was on that exact same ROM the day before flashing CM7 and it was working perfectly, did everything it said it would, apps installed just fine. And the first time I installed that ROM, I didn't wipe a single thing.
So, now I'm thinking we should revert to the stock ROM, then flash this one back over it with no wipes, then if that doesn't work, revert to stock again and try flashing the ROM the proper way, wipes and all.
I'll try fixing this every way I can. I'll tell you if I find a fix for myself that you could use as well
Click to expand...
Click to collapse
Ok thank you , I'm waiting you
but can you tell me what is the CM7 ???
*_^AL_Ha$aN^_* said:
Ok thank you , I'm waiting you
but can you tell me what is the CM7 ???
Click to expand...
Click to collapse
is a type of rom... currently cm7.2 stable build... CM stands for cyanogenmod
check this site: cyanogenmod.com
Pretty much every ROM ever made says be sure to wipe EVERYTHING. They put that there for a reason. The only time time you MIGHT get away with not wiping is if your flashing the exact same ROM you just had. Then and only then, you might get away without wiping your dalvik.
Sent from my HTC_A510c using Tapatalk
Idk, the ROM worked fine for me, even though I think I didn't wipe anything. When I did wipe the phone before flashing, there was a problem. Though it could just be my device and my bad luck
God hates me, I don't know why I even bother living anymore -.-
EDIT: My faith in God is restored. Just flash this ROM instead. You'll be happy with it and it works just fine for me. Also, wipe EVERYTHING I can't agree that you always have to wipe everything, since not wiping actually solved a problem I had with CM7, but I think that was just an isolated case.
hey guys. im very new here and new to the world of andriod. took the plunge with the Supernova rom, loved it till it gave issues with freezing
found the above mentioned rom and tried it out
LOVING IT. its super fast and stable without a joke, but here are my problems:
1: unable to download and install ANYTHING from the android market. when i try it, the phone flashes to the mildwild screen as if it rebooted and then nothing, no app installed
2: unable to set the free space on my memory card to be read as phone memory (as in supernova, it allowed u to set ur ext4 partition) i have a 8gb card and it was partitioned using Gpart for the supernova installation. i just cleared the partitions and tried the same thing with this rom. it only reads 140~mb free space as phone memory.
another point to note, i tried flashing the data2sd that was used with supernova. the phone didnt boot at all and i had to reflash with the mildwild rom to get it up again
so am a bit lost. any help is greatly appreciated
no one can help at all?
kevearc said:
1: unable to download and install ANYTHING from the android market. when i try it, the phone flashes to the mildwild screen as if it rebooted and then nothing, no app installed
2: unable to set the free space on my memory card to be read as phone memory (as in supernova, it allowed u to set ur ext4 partition) i have a 8gb card and it was partitioned using Gpart for the supernova installation. i just cleared the partitions and tried the same thing with this rom. it only reads 140~mb free space as phone memory.
another point to note, i tried flashing the data2sd that was used with supernova. the phone didnt boot at all and i had to reflash with the mildwild rom to get it up again
Click to expand...
Click to collapse
1 Try a clean install.
2 MildWild does not have a built in d2sd script. use s2e from market. Do not flash the supernova d2sd.
cronus101 said:
1 Try a clean install.
2 MildWild does not have a built in d2sd script. use s2e from market. Do not flash the supernova d2sd.
Click to expand...
Click to collapse
thanx, will try this
however, can you highlight the steps to perform a clean install? i have the installation steps down pat, just need to know what do i clear to do the install
kevearc said:
thanx, will try this
however, can you highlight the steps to perform a clean install? i have the installation steps down pat, just need to know what do i clear to do the install
Click to expand...
Click to collapse
Wipe cache, dalvik cache, factory reset in recovery then install rom.
Hope this helps
Sent from my HTC Desire using XDA App
charlescaz said:
Wipe cache, dalvik cache, factory reset in recovery then install rom.
Hope this helps
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
thanx and much respect for this. will get back to you guys and let you know how it goes
Thanks to Hobby31 (http://forum.xda-developers.com/member.php?u=2360932) for figuring this out. I have taken his post, and rewritten for ease of reading. Tested and working on (at least) 2 phones so far.
How to restore a Nandroid or flash new ROM with CWM Touch
In CWM Touch Recovery
1. Go to mounts and storage and unmount cache.
2. Make a nandroid. (Going back to mounts and storage, you will see data is mounted and will not unmount.)
3. Go to "advanced" and select reboot recovery.
4. Once phone reboots into recovery, go back to mounts and storage and see that data is unmounted. You may now wipe data, system, and cache.
5. You may now restore a nandroid or flash a new rom.
Recommendation : As noted below, proper wiping matters when switching between roms, particularly from ICS to JB. Use superwipe from Mike (android revolution HD) when moving between roms. http://api.viglink.com/api/click?fo...="0" alt="">&jsonp=vglnk_jsonp_13416929577832
If this helped you, hit thanks. Also, thank hobby 31. Thread here. http://forum.xda-developers.com/showthread.php?t=1748049
EDIT 7-19-12 If you say "I've had no issues doing backups and restores with CWM," please ask yourself the following questions:
1. Are you using CWM Touch or non-touch? This is a Touch issue. If you are using the non-touch... you need not read further or report "I have no problems" because this is specifically related to Touch. (Please note I have not flashed the new 6.0 CWR Touch as some people are reporting problems with it also.)
2. Did you do multiple operations in the same recovery session? Meaning did you wipe data/factory reset, wipe cache, wipe delvik? Then did you try to flash a new ROM or restore a backup without restarting recovery? The reason this matters is because this issue of data not unmounting seems to happen in Touch CWM after a wipe is performed. You might be able to do one action per recovery session, but doing multiple actions that require data to be unmounted are what borks the operation and leaves some people hanging at the glowing X of "Oh crap I need to boot back into recovery."
Let me know if there are any problems, need for further clarification.
I flashed an older version of CWM (5.5.0.4) Non Touch version so I could flash JB but my SD card would not mount after I did a full wipe. Had to use the Toolkit to flash stock image. Do you know what would cause that to happen? People are saying to use the older version to flash JB and I want to try VanirBEAN ROM but don't want to run into the same SD mount issues.
I have not had any difficulty restoring cwm nandroid backups of other ROMs, or flashing other ROMs coming from V3. Have not had to resort to any of these steps. But I have seen a lot of threads about others having a lot of problems. Just curious if anyone has any theories about why this is?
Gallery69 said:
I flashed an older version of CWM (5.5.0.4) Non Touch version so I could flash JB but my SD card would not mount after I did a full wipe. Had to use the Toolkit to flash stock image. Do you know what would cause that to happen? People are saying to use the older version to flash JB and I want to try VanirBEAN ROM but don't want to run into the same SD mount issues.
Click to expand...
Click to collapse
I flashed the BAMF You Jelly Huh? ROM using the clockwork touch recovery and it worked flawlessly (I did wipe data though)
cam30era said:
I have not had any difficulty restoring cwm nandroid backups of other ROMs, or flashing other ROMs coming from V3. Have not had to resort to any of these steps. But I have seen a lot of threads about others having a lot of problems. Just curious if anyone has any theories about why this is?
Click to expand...
Click to collapse
After talking with others, I think my issue was after flashing the older CWM I did not reboot before moving forward with the wipe. Too chicken to try it again
I think it has to do with the coding in vicious and some of the initial releases of JB roms. Coupled with the data not unmounting at the proper time. A couple people also have mentioned that they didn't do as full of a wipe as is done with the super wipe script, hence why a lot of devs suggest using it to clean out old ics code.
Has nothing to do with Viscious. Same on JellyBelly 3.x Even when moving between JB roms, Data won't unmount when performing multiple operations.
I have flashed all three versions of Vicious' JB with CWM Touch and have not had a single problem. My process is as follows:
-Backup
-format /cache
-format /data
-format /system
-Wipe Dalvik cache
-Flash ROM
-Wipe Dalvik cache
-Reboot
-????????
-Profit
Team win recovery aka twrp. Everyone done says "use non touch recovery" it doesn't matter. Haven't had a single issue using twrp on this phone or any of my previous phones. It works great. Especially with super wipe scripts.
Sent from my Galaxy Nexus using Tapatalk 2
Omen87 said:
I have flashed all three versions of Vicious' JB with CWM Touch and have not had a single problem. My process is as follows:
-Backup
-format /cache
-format /data
-format /system
-Wipe Dalvik cache
-Flash ROM
-Wipe Dalvik cache
-Reboot
-????????
-Profit
Click to expand...
Click to collapse
Bingo. That's what superwipe does.
Added link to Mike's superwipe.
Sorry for the dumb question, but ive done a search and found conflicting answers. When you wipe data and cache do you want them to be mounted or unmounted?
Sent from my Transformer TF101 using Tapatalk 2
I have Touch CWM and I have no problems flashing back and forth between JB and ICS roms and nandroids.
You just have to flash a Super Wipe in between.
I just did this yesterday to test out my MHL adapter. Backed up my JB rom, super wiped, restored my ICS Liquid Rom, tested, super wiped, restored my JB rom.
I think super wipe is key in going between different rom builds. But I've had absolutely no problem using CWM at all. If Super wipe is the answer, then perhaps CWM's Factory Reset option isn't wiping as well as it should.
Flashing a SuperWipe is much easier then having to restart the phone a few times.
I think it may be related to Viscious old versions. Not Sure. Using Jelly Belly now. If you are not having problems, that's great. I used superwipe script. No problems. But, if people want the manual solution without getting errors, then at least we know the above method works. It might not be neccesary now with the newer releases, maybe data will unmount ok.
If anyone wants to test and see if they can restore old backups from ICS w/out doing the above steps (IE the rebooting) and report back, it'd be appreciated. I will be uber busy the next couple days or I'd take the time to backup to my computer before trying.
Would you mind sending me the super wipe script to flash? Or point me to the thread?
Sent from my Galaxy Nexus using xda premium
mikeacela said:
Would you mind sending me the super wipe script to flash? Or point me to the thread?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Link on Page 1... Sorry, I'm on my phone or I'd paste it for you.
player911 said:
I have Touch CWM and I have no problems flashing back and forth between JB and ICS roms and nandroids.
You just have to flash a Super Wipe in between.
I just did this yesterday to test out my MHL adapter. Backed up my JB rom, super wiped, restored my ICS Liquid Rom, tested, super wiped, restored my JB rom.
I think super wipe is key in going between different rom builds. But I've had absolutely no problem using CWM at all. If Super wipe is the answer, then perhaps CWM's Factory Reset option isn't wiping as well as it should.
Flashing a SuperWipe is much easier then having to restart the phone a few times.
Click to expand...
Click to collapse
I'm running CWMR 5.8.0.2 and I've restored my ICS roms over several JB roms without issue and no use of any sort of superwipe script.
nhizzat said:
I'm running CWMR 5.8.0.2 and I've restored my ICS roms over several JB roms without issue and no use of any sort of superwipe script.
Click to expand...
Click to collapse
This. ^^^^^^
Sent from my Galaxy Nexus using xda app-developers app
nickles96 said:
This. ^^^^^^
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Are you using Touch Based CWMR? Or Standard.
I can confirm even with Jelly 3.6, that after I wipe data, cache, and delvik that the data will then remain mounted and not unmount unless I restart recovery.
This can/does cause problems and messes up operations when people are doing multiple actions in recovery at the same time. You might be able to do one action, such as making a backup just fine. But if you are using CWMR Touch, you might have issues with doing multiple operations in the same recovery session, like, backup, wiping, then restoring if the action you are doing requires data to unmount.
So, if you say "I have no problems..." please confirm that you are using touch recovery... not just standard.
CWM Touch was updated to 6.0.0.5 this week, is this issue still present? I haven't experienced any problems yet using CWM Touch, I'm just curious.
My steps are 1. Backup 2. Wipe data/factory reset 3. Wipe cache partition 4. Wipe Dalvik cache 5. Flash ROM 6. Flash GApps if needed 7. Reboot