I've seen older threads saying that, if you're updating a custom ROM with a new version, usually you will need to clear the caches and re-flash or possibly do a clean wipe.
I have RaymanFX 0.5.0 (which will be updated soon), so I'm wondering if, for an update, I need to do a data wipe or if just clearing the caches and re-flashing is sufficient.
Thanks.
The rule of thumb for upgrading is this:
If you're upgrading within a rom (say RaymanFX 0.5.0 to RaymanFX 0.6.0) then wiping cache/dalvik cache is generally enough. I'd also suggest wiping/formatting the /system folder too, but that's up to you.
If you're upgrading to another rom (say RaymanFX to EOS4) then you should fully wipe/factory reset your device.
The exception to the rule would be upgrading within a rom that changes from android 4.1.x to 4.2.x. In that case you should also fully wipe/factory reset.
Your mileage may vary but this is what's always worked for me. A full wipe each time for every upgrade is the best thing you can do, but it's not needed and means you spend a lot more time re-installing stuff (which I'm guessing is why you are asking).
Thanks, grgmre. That's what I expected. And, yes, I was asking precisely because of reinstalling apps. After I flashed 0.5.0 and played with it for a few hours, I reinstalled most of my apps. I'll install them a bit more slowly after I flash the upgrade or a different ROM.
As easy as it is, it's actually tempting to flash and try out more ROMs.
Related
I am relatively new to flashing ROMs & kernels for Android. Currently I'm using MIUI 1.5.6 and would like to upgrade to the newest version of 1.5.13.
My question is, do I have to wipe data if I'm just upgrading to the same ROM or would wiping cahce & Dalvik cache be sufficient?
Before anyone flaming me I have searched the forum prior to posting and surprisingly didn't find anything useful as I thought this would be a frequently asked question.
Thanks in advance!
I never clear if i'm gonna do the same rom and it seems to work perfect. So I'd say dont it takes less time but if your worried do it. clearing that stuff wont really loose anything so its your choice really
I think you ALWAYS should do a backup, just in case something goes wrong.
You have the device at the Computer, you have the cable hooked up.
What would it take... about 5 minutes to do the backup up ??
oddball69 is right. You should always do a wipe.
Just to avoid problems
Most of the Devs will specify for each version if a full wipe is not required. If you can't find anything about it then do a full wipe.
If they directly say a wipe is not required then it's probably just some small fixes.
Thanks for all the responses.
I was going to do a backup for sure I just wanted to avoid having to wipe everything and then reinstalling and re-setting up all my apps which could be quite a pain
Depends on the ROMs used, usually the developers state if this is necessary.
It wont hurt if you try without wiping, if it makes problem just wipe and do it again.
What is there to loose?
Hey all, long term lurker here posting, obviously, for the first time. I'm not sure whether this would be better placed in the general or q&a section, as it seems like a good portion of the general section consists of questions.
Anyways, on to the problem. I recently attempted to flash the mr1 version of CM7 and was greeted by a force close loop, with com.android.phone closing. This was after wiping the dalvik cache and all data before flashing the rom. I was actually getting into a bootloop before that, even thought the md5 of the rom matched up with the one posted. I had redownloaded the rom to try again, and managed to actually boot before running into this fc problem. I have no idea what could be causing this, and it would be great if anyone could offer up some ideas on potential fixes, or at least some insight into what might be going wrong.
What radio are you using?
As far as I know, the stock radio. I don't remember ever flashing anything other than some of the early thunderbolt cm7 builds. Radio version is 1.16.00.0223r.
You have the correct radio (you can use 223r or 402w for MR1 version). Did you wipe /data, /system, /cache, /dalvik-cache?
I believe I wiped all of those. I know for a fact that the dalvik cache got wiped, and I'm pretty sure I wiped /system and /cache
Dark_Rak3r said:
I believe I wiped all of those. I know for a fact that the dalvik cache got wiped, and I'm pretty sure I wiped /system and /cache
Click to expand...
Click to collapse
I'd recommend wiping and flashing back to a Froyo ROM (BAMF is always a good choice, just make sure its not one of the new Froyo mr2 ones), and then attempting to wipe and re-flash CM7. Sometimes these things just happen. If its just a little bug, this will fix it. If theres a deeper issue, we can do more to expose what exactly it is, but lets go in baby steps
MattBeyers said:
I'd recommend wiping and flashing back to a Froyo ROM (BAMF is always a good choice, just make sure its not one of the new Froyo mr2 ones), and then attempting to wipe and re-flash CM7. Sometimes these things just happen. If its just a little bug, this will fix it. If theres a deeper issue, we can do more to expose what exactly it is, but lets go in baby steps
Click to expand...
Click to collapse
I'd agree but me personally I'd just do a wipe of /system, /data, /cache, /dalvik-cache and reload the ROM fresh over a clean system. Once you do that and load up gapps see if you have any issues before reloading apps. It wouldn't hurt to return to a FroYo ROM just to make sure things are good though as well.
Try clearing data on contacts storage, phone, and media storage, for some reason one of those worked for me
Thanks, I'll try your suggestions and see if they get anywhere. @MattBeyers, I'm currently on the stock sense rom (or whatever you end up on after rooting), so would you suggest I flash another froyo rom or should I just go ahead and try a wipe and then reflash cm7?
EDIT: Well something worked. Seems like I'm good to go, although I'm not really sure if anything changed in what I did to try and get cm7 running this time. Thanks for your help guys, and hopefully I won't run into any more problems here.
I am currently running Jellytime R28. Since R31 have been released, do I need to do a clean wipe or can I install over R28?
If it's same rom different build, you can probably get away with just wiping cache and dalvik instead of wiping data
but better check the dev thread
BnD always asks for fresh install if you intend to report any bugs, or posting logcats etc
I took a speed reading course and read ‘War and Peace’ in twenty minutes. It involves Russia.
—Woody Allen
As the title states, I can't get my camera to run on any AOSP ROMs. Camera works fine as soon as I switch to something TW based, but breaks as soon as I load anything AOSP.
I've searched everywhere I can think for this issue and have tried solutions that have worked for others but with no success. I've tried flashing back to stock unrooted, then rooting and starting all over again. I've tried copying cameradata files from TW based to AOSP (in several variations). I've tried reflashing (and I've done nothing but clean flashes each time I'm flashing anything). If it matters, my normal method is to wipe data/factory reset, then clear cache and dalvik, then install ROM + gapps, and then reboot.
I'm using CWM touch recovery v6.0.2.3, firmware VRBMF1 (and one or two others), and have tried leankernel in addition to stock kernels.
It may be worth mentioning that this is a refurbished device and I used Casual's One Click Root, whereas previously (Jan 2013) I rooted the long way and had no issues with anything really.
I had this problem for months. I did a clean install and it fix the problem. Try doing that and it might work for you too.
What do you mean by clean install?
Gigatrig said:
What do you mean by clean install?
Click to expand...
Click to collapse
He's probably meaning to wipe everything in CWM. Data, system, sdcard, etc. Pretty much everything and you'll probably fix your problem. Maybe even flashing latest firmware again wouldn't hurt.
Sent from my SCH-I535 using xda app-developers app
kude87 said:
He's probably meaning to wipe everything in CWM. Data, system, sdcard, etc. Pretty much everything and you'll probably fix your problem. Maybe even flashing latest firmware again wouldn't hurt
Click to expand...
Click to collapse
Do you mean in the "mounts and storage" menu? Use format /system... /data... /sdcard? I think that's what you mean, but I've not had to use those before, so I wanna make sure.
Thanks
:laugh:
Gigatrig said:
As the title states, I can't get my camera to run on any AOSP ROMs. Camera works fine as soon as I switch to something TW based, but breaks as soon as I load anything AOSP.
I've searched everywhere I can think for this issue and have tried solutions that have worked for others but with no success. I've tried flashing back to stock unrooted, then rooting and starting all over again. I've tried copying cameradata files from TW based to AOSP (in several variations). I've tried reflashing (and I've done nothing but clean flashes each time I'm flashing anything). If it matters, my normal method is to wipe data/factory reset, then clear cache and dalvik, then install ROM + gapps, and then reboot.
I'm using CWM touch recovery v6.0.2.3, firmware VRBMF1 (and one or two others), and have tried leankernel in addition to stock kernels.
It may be worth mentioning that this is a refurbished device and I used Casual's One Click Root, whereas previously (Jan 2013) I rooted the long way and had no issues with anything really.
Click to expand...
Click to collapse
I had the same problem with my phone, I made a thread a little while ago with what I did. http://forum.xda-developers.com/showthread.php?t=2492304 ask any questions you have on there I want to improve it as this was a very frustrating and time consuming fix for me.
I was tinkering with my TF101 and sort of accidentally (lol) overwrote my installation of Timduru's KatKiss-4.3.1_029.zip with his KatKiss-4.4.2_016.zip without wiping anything before doing so. (Actually didn't have any data to speak of - as I formatted and wiped in proper fashion on the install of KatKiss-4.3.1_029), and it hadn't been run for more than a couple of days.
I've developed a severe addition to ROM experimentation, and so may install and backup every few days it seems. Don't have a nickname for that habit yet, but I sense that they are many similar addicts around this site.
What I would like to know, since all seems, at least to this n00b, to be just fine - what "might" happen w/ my TF101 since the overwrite of a newer ROM?
Staying put, until I hear from a forum guru, or at least anyone with more experience than me (and that will include most all members).
Thanks,
Cal
If you overwrite a ROM with a different one (different android version, or by a different developer) you may run into issues where it will not boot, or it may run poorly, random reboots, sleep o death.
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
I have not tried this with the 4.4 version of his ROM (I am still on 4.3 for now.)
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. If you want to go back to 4.3, make a backup and then use Titanium Backup Pro version to extract any apps and data from the 4.4 version and restore to 4.3. Do not restore any system settings or apps.
frederuco said:
<snipped a bit>
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. <some stuff snipped>
Click to expand...
Click to collapse
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Cal-123 said:
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Click to expand...
Click to collapse
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
schwigi said:
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
Click to expand...
Click to collapse
Read the original post again -- I've been on the 4.4.2_16 forever now it seems!! The urge to try something new is over-bearing! :silly: :victory:
Ah-Ha! I see that Tim's put up a new 'stable' one. KK 4.4.2_17! Yeah!! This should be a super easy fix for the 'crack-itis' I have developed...as I will overwrite this one also.