Say I want to flash a new version of the rom i'm using do I need to wipe everthing again?
After multiple updates it's usually a good idea for a full wipe. However just one update you'll be fine wiping cache and dalvik only. If you've flashed a custom kernel then you'll need to reflash that, along with any other mods you've made to the system.
Read the thread for the rom and double check that it isn't recommended to do a full wipe for this particular update. Also make a nandroid backup just in case you encounter any problems.
I only flash updates of the same rom, usually only wiping dalvik and cache. I do make sure to do a full wipe about once a month though. It keeps the phone running smoothly and helps weed out apps that I don't really use when I go to restore.
Supersonic Evo 4G | MIUI | Tapatalk
It's always recomended to do a full wipe unless the op says otherwise. Some ops will make patches that do not require full wipe. If you don't full wipe, don't complain about problems. It's the first thing you will be asked. Use Titanium Backup for your apps and wipe away. Always nandroid first just in case you make a mistake.
thanks for the great answers guys appreciate it
You're welcome, just trying to be helpful.
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.
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn
I want to flash to Magnolia Rom from the stock HTC rom. Im rooted with Unrevoked, HeyItsLou v8 Kernel, and I have my 16Gb SD card. Now what Im concerned about is the apps. I assume since Magnolia is based on the same framework I dont have to do any wiping. I just want to verify before I go ahead and flash first.
Make a backup and try it. I had the stock rom and installed it with out wiping and it worked fine for me. But every phone is different. As long as you have a backup you can always go back to what you had before and try it again with wiping.
Just to clarify as well when they say "wiping" they are referring to what? I assume more than the dalvik cache.
Data/cache. A.k.a. factory reset.
Sent from my ADR6300 using XDA App
Ok so just clear the data cache and the dalvik cache and I should be good to go?
Also when wiping, you should wipe data and cache at least 3 times to make sure you clear every thing so you don't leave anything that might be "corrupt" behind.
Sent from my ADR6300 using XDA App
Yeah, first do a Titanium backup, then a nandroid backup just in case. Then wipe the cache and dalvic; don't wipe/master reset if you don't want to. Flash Magnolia and see if you have any issues. If not, you're good.
If you do have problems you have a choice of going back to where you were (via nandroid restore), or simply doing a master reset and keeping Magnolia (then restoring your apps - but don't do a blanket "restore all").
I've been using Magnolia off and on for weeks. It's a great ROM. Good luck!
whitedragon551 said:
I want to flash to Magnolia Rom from the stock HTC rom. Im rooted with Unrevoked, HeyItsLou v8 Kernel, and I have my 16Gb SD card. Now what Im concerned about is the apps. I assume since Magnolia is based on the same framework I dont have to do any wiping. I just want to verify before I go ahead and flash first.
Click to expand...
Click to collapse
It's always smart to wipe the phone first, Magnolia runs off the same framework, but things can go awry if you don't wipe first. Wiping includes Data/Cache/Dalvik. As the others have said always make a Nandroid backup and a Ti backup also. Just don't reinstall your account settings via Ti, it tends to cause issues.
Suggest you wait until tomorrow when Magnolia 1.3.2 is set to drop. Check the Magnolia thread for that.
Hello,
I have an Amazon Kindle Fire with gedeROM v1.7. I love the updates because it makes my device better and better.
But can i update my device without data wipe so i don't have to reinstall and reconfigure the entire device every time. And if I can can someone please tell me how.
My usual procedure is download file, data wipe, clear davlik and cache, flash, wipe cache restart and wonderfull a better device. But all the data and apps go with the wipe so any help would be awesome!
Thnx for all the help!!
Moaely said:
My usual procedure is download file, data wipe, clear davlik and cache, flash, wipe cache restart and wonderfull a better device.
Click to expand...
Click to collapse
If you're not switching to a different ROM (ie, from CM7 to CM9, or from hashcode to energy...) then you can optionally skip the data wipe (factory reset), which will retain your data and applications...
Alternatively, you may want to take a look at Titanium Backup.
Thnx for the info.
I have been hearing a lot about Titanium Backup, can you give more info about the program.
With TB you can back up any apps on your device. Then when you update a rom just download TB again and then you can restore your apps that you backed up. I love TB and use it on every device that I have rooted. It is a lifesaver!! Ok maybe a time saver anyway!! LOL!!!!
I had a REALLY bad experience from not wiping everything completely. I'd definitely do a backup, like Titanium or MyBackupPro, and wipe it all just to be safe. To many goofy things can happen if you don't.
It really depends on what ROM your flashing. There are rare occasions you can cross flash without issue. Not recommended. Just updating the same ROM so wipe is necessary, unless mentioned by the dev.
If you do wipe than BUYING titanium backup is the way to go. The free version doesn't auto install apps, each needs confirmation.
I can get any ROM on the kf or my gnex but up and running in less than 15 minutes.
this is what I have been doing and I am not sure if it's bad to do or not. I make a backup of just my data using twrp, then I wipe the caches and do a factory reset. Then I install the rom, and then restore my data using twrp
chris_m128 said:
this is what I have been doing and I am not sure if it's bad to do or not. I make a backup of just my data using twrp, then I wipe the caches and do a factory reset. Then I install the rom, and then restore my data using twrp
Click to expand...
Click to collapse
Restoring your backed up data is akin to not having done "factory reset" in the first place.
You shouldn't encounter any major issues so long as you're flashing newer versions of the same ROM and there hasn't been a large change (for example, switching to linaro).
Hello, all,
Apologies if this is a noob-ish question, but I could really use some assistance here. After installing kennyglass123's People's ROM v3.1 without incident, upon reboot, I get stuck in the boot screen (in this case, the black and white spiral). Only solution--that I know of--is to restore from nandroid backup to get back to previous ROM.
Is there some sort of app conflict that I'm coming up against? I ask because I had previously, successfully installed it back in early Feb, and it worked great, and then after a reboot after some app updates, it got stuck.
Love the ROM...want to get it to work again!
Appreciate it,
For faster help, you should post this queation in the peoples rom thread.. For now if you want to try and fix it do this.. I wipe cache, delvik cache, factory reset, and system. Flash rom agin, wipe cache again, reboot.. Remember it can take a while for the system to fully boot..
Yes, as said above, make sure you are wiping EVERYTHING. The system can take long to boot as well depending on how large the OS you flashed is. Additionally, multiple wipes dont hurt either, especially if you are flashing a different android version (ICS to JB)
Make sure to always format system, clear data (might say factory restore), clear cache, and clear dalvik cache (rinse and repeat to be safer), then flash your rom of choice
Sent from my PG06100
As everyone above stated, make sure your doing a complete clean install. TPR uses Aroma Installer and make sure you make all the right selections, and choose a kernel during the whole process.
Transmitted with a portable device using Xparent Blue Tapatalk 2
peajul said:
Hello, all,
Apologies if this is a noob-ish question, but I could really use some assistance here. After installing kennyglass123's People's ROM v3.1 without incident, upon reboot, I get stuck in the boot screen (in this case, the black and white spiral). Only solution--that I know of--is to restore from nandroid backup to get back to previous ROM.
Is there some sort of app conflict that I'm coming up against? I ask because I had previously, successfully installed it back in early Feb, and it worked great, and then after a reboot after some app updates, it got stuck.
Love the ROM...want to get it to work again!
Appreciate it,
Click to expand...
Click to collapse
Been running TPR since the OG days.. As with flashing ANY rom, Do a Full data wipe, cache clear, dalvik clear (couple times if you prefer) make sure you select a kernel in the Aroma process. Should be back in business. Always can post in the TPR thread for most help available tho, The People are always ready and willing to help out where we can! Let us know if there is anything else that happens.