After playing around with several ROM / kernel combinations I am looking to return to the latest stock Rom. I have the PC36IMG file on my SDcard and will be installing via ClockworkMod recovery. What is the proper procedure to ensure the cleanest possible installation? Im a bit scared of all the options in recovery such as all the format options in the partitions menu. Do I need to format everything? Will any files be carried over? I know I will need to re install Clockwork and SU app just want to make sure everything is as clean as possible. Thanks in advance.
cleanest possible? Flash this in recover. It wipes 100% of every every time.
Courtesy of Calk.
If you are just changing kernels, choose wipe catch and delv catch.
Changing to a different rom you need to wipe everything.
Thanks for the tip. I am running a custom kernel so I'd be looking to wipe all of those files as well as the ROM. The ROM I am using is just a re packaged RUU, does the RUU completely wipe all data or will I still need to manually wipe?
You should always manually wipe. I never count on something else to do it for me. When I am changing roms I always wipe data/factory reset, cache and davlick, plus I use calkulin's format all tool that the other responder to your question attached to his post. That way you know nothing will be left over. Before you do all that, remember to make a backup of your current configuration just in case something goes wrong. I have been bailed out by nandroid backup a few times.
Also one more thing, there is a Rom on here that is the latest stock already rooted which would make it much easier on you. You could just wipe and flash and still have SU and all other benefits of having root. Just a suggestion.
I found the stock rom thread. It has both odexed and deodexed version. Odexed will probably boot faster, but deodexed can be themed and/or modded. Heres the link: Stock 3.70 EVO Rooted
I reccommend clearing the cache, and then wiping the dalvik to ensure a clean rom. After that, just flash your rom. As always if you are unsure, you can backup your SD card.
Related
I was looking to flash to Bakedsnack 1.8 with ROM manager, has anyone done this successfully? Or would you recommend doing it a different way. I ran the backup current ROM for the standard one that came with phone just rooted... but does that save EVERYTHING??
Yes, a nand backup saves EVERYTHING. Think of it like having a clone of your hard drive on your computer. If something goes wrong with your new ROM you restore a nand backup and everything is there.
Backing up through ROM Manager is fine. Make sure you do a complete data wipe and cache clear before flashing your new ROM of choice. If you don't do the data wipe and cache clearing you will likely end up going into a boot loop after flashing the new ROM. If that happens it isn't a big deal. You'll simply have to reflash the ROM, this time remembering to do the data wipe and cache clear.
I've got a general question that I haven't really found an answer for - although I know the information is there, I'm just not 100% sure how to piece it together. I'm hoping all you experts out there can help provide some guidance.
Using my EVO as an example, I currently have Fresh 3.5.0.1 flashed and have been very happy with it. But, I've been dinkin' around with Titanium Backup and uninstalled a few things (i.e. LiveWallpaper) and generally (probably) made a mess of things.
Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
I have ROM Manager installed... is it as simple as creating a NANDROID backup, downloading the ROM again and flashing? Or, should I boot into recovery and clear caches, wipe data/factory reset? I'm not sure if a "wipe data/factory reset" from the CM recovery (3.0.0.5) is the right thing to do.
Guidance would be very helpful and much appreciated. Hopefully, others could use any information provided to do the same with their device if they're unsure how to do the same thing with other ROM's.
i usually like using amon ra recovery instead of clockwork recovery which is the one use by rom manager, if you want to try it rom manager has an option at the bottom that says flash different recovery and says amon ra, if you click it your recovery will become amon ra which i like better for wiping. but to answer your question, yes for a fresh start on a new rom you need to boot into recovery, then NANDROID BACKUP, then wipe 1.cache 2. dalvik cache 3. data and then flash your new rom and you are good to go
If you want to start fresh on the current 'Fresh' ROM then, yes, wipe fully and reflash.
sent from my
Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
Click to expand...
Click to collapse
Just do exactly what you did when you flashed it for the first time. Place zip on sd card, nandroid backup, wipe everything, flash rom.
Alright so i installed my first ROM on my evo last night. seems like it worked fine everything still works and the ROM is awesome.
http://forum.xda-developers.com/showthread.php?t=1012918
One questions i did have is, if i want to install another one how would i go about that?
Do i just install it like i did the first or do i need to remove the current one and install the new one?
Im sure this is posted somewhere but i wasent able to find the answer im looking for.
Thanks for any input
The tried-and-true and overall preferred method, as I've observed, of XDA forum members is to do the following when changing to a new ROM, or for the first time:
Place the ROM in the root of your SD card.
Boot into Recovery by holding vol+down and Power (most custom ROMs will let you reboot into Recovery specifically instead of having to turn off the phone and back on).
Make a nandroid backup.
Wipe data/factory reset.
Wipe cache.
Go into Advanced, wipe Dalvik cache.
"Go Back."
Install zip from SD card.
Choose applicable .zip.
Wait for installation.
Reboot.
Enjoy.
Furthermore, if going to an AOSP ROM, be sure to flash GApps right after you flash your ROM.
As far as kernels go, some people say to do it after you flash your ROM, some day to reboot and then go back into Recovery and do it, some say either way.
Load the new rom zip on your sd card from your pc. Boot to Recovery, make a nandroid backup of your current rom. Then factory reset the phone in Recovery and wipe data, cache and dalvik cache. Wiping them each 2-3x for optimal results.
Then flash the zip for your new rom. Reboot and there it is. If your gonna change kernels or task bars etc, I recommend booting between each zip flashed. Just seems I have less problems this way.
Also get a sms backup app if they are important to you. I use sms backup+. It's free and works great, backs up msgs to gmail. Then u can restore with the app when the new rom is loaded.
Sent from my Warm Z EVO
totalanonymity said:
The tried-and-true and overall preferred method, as I've observed, of XDA forum members is to do the following when changing to a new ROM, or for the first time:
Place the ROM in the root of your SD card.
Boot into Recovery by holding vol+down and Power (most custom ROMs will let you reboot into Recovery specifically instead of having to turn off the phone and back on).
Make a nandroid backup.
Wipe data/factory reset.
Wipe cache.
Go into Advanced, wipe Dalvik cache.
"Go Back."
Install zip from SD card.
Choose applicable .zip.
Wait for installation.
Reboot.
Enjoy.
Click to expand...
Click to collapse
Awesome thank you very much. Sounds pretty much just like how you install one.
Thanks again
yes do that ^^ nandroid and you can leave the rom on your card if you have enough space and in case you want to reinstall it clean again.
one more question
im thinking about installing another rom and it has multiple downloads some are themes and some widgets and the main ROM. Do I install them 1 at a time or can i do them one after another.
Honestly, preference, with those, I think. As stated before, some people's phones are fine with flashing tons of things at once and some people's phones like to take it nice and slow and have a reboot in between.
Also, make sure the themes you are installing are in flashable zips. There are some out there that aren't and require manually placing them in the SD card or using adb.
http://forum.xda-developers.com/showthread.php?t=841311
this is the one i was thinking about
dahlinc said:
http://forum.xda-developers.com/showthread.php?t=841311
this is the one i was thinking about
Click to expand...
Click to collapse
ROMs are flashed in recovery just the same as any other ROM.
All add-ons in his first post are flashable via Recovery, as well.
Get into a habit of wiping cache and Dalvik cache before every flash of anything. (Data/factory when flashing between ROMs, though.)
Also, a nandroid backup before you flash anything would be wise. I stopped doing them as often because they take up quite a bit of memory when you start flashing things left and right! But, it is wise to do so before flashing anything. If anything goes wrong flashing a particular item, you can always restore a backup and start again from a very recent point (i.e. not losing much of what you did) from when there were no issues.
I personally also copy my files to my computer for safekeeping, should something occur with the SD card.
Thats all i need know thank you again!!!!
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
Is it only necessary when coming from ICS to JB or is it necessary to do when coming from a JB ROM to another JB ROM? In my SGS2 days it was factory data wipe, wipe cache, wipe delvik cache, and maybe a kernel cleaning script for good measure, but never touched my SD user content( PDFs, music, etc.).
Super wipe will erase everything( as indicated by the warning in CWM), if you don't think it did cuz you still see the files, try and open them, its a shell only, no content (still lists correct file sizes though???)
I found this out by trying to flash some alternate ROM firmware or kernels I had but couldn't get them to work.
Don't use those stupid superwipe .zip's.
They're running the same scripts as your recovery runs...potentially multiple times for the "LULZOMGCLEAN" factor. [Uh...not needed]
Even installing a rom wipes /system...but %90 of people say "lul wipe /system/ /data/ /cache/ /dalvik/ and then flash superwipe..."
(Yes, I realize a script has to be run for the .zip to wipe system...and the Rom dev MAY leave it out. Personally, if the developer of my rom doesn't even make a "wipe system" script in the .zip I would not use that rom.)
NOT necessary.
If you don't trust your recovery to do it's job...wipe everything with one wipe...
Maybe you should get a new one.
Jubakuba is right but rather than assume the ROM zip wipes /system I find it easier to just wipe it. I never have the problems that others do when they flash ROMs and I always do a factory reset from recovery and wipe system. And if a ROM requires Gapps I always reflash the Gapps after a new ROM update. May not be needed but has saved me from problems before and only takes a couple seconds. Wipe zips are for chimps.
jesusice said:
Jubakuba is right but rather than assume the ROM zip wipes /system I find it easier to just wipe it. I never have the problems that others do when they flash ROMs and I always do a factory reset from recovery and wipe system. And if a ROM requires Gapps I always reflash the Gapps after a new ROM update. May not be needed but has saved me from problems before and only takes a couple seconds. Wipe zips are for chimps.
Click to expand...
Click to collapse
You have to flash Gapps after flashing a rom as they reside in /system/
FYI!
Jubakuba said:
You have to flash Gapps after flashing a rom as they reside in /system/
FYI!
Click to expand...
Click to collapse
Right. Many ROMs like CM are supposed to have a script to preserve Gapps and they say that you don't need to flash Gapps after, say, updating to a new nightly but I've learned the hard way not to depend on it.