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?
I am having a problem with switching ROMs on my sensation which just started a few days ago. I am currently running ARHD 3.1.1 and it is very stable and I have had no problems whatsoever, but like many here, I like trying out different and new ROMs. Anyways, I did a backup and installed ARHD 3.6.2, and it was forcing close on several apps, and kept getting soft reboots, so I tried RCMix's, and it would load and automatically install some apps and settings that I had on my previous ROM, and it was working fine, but then I started getting soft reboots when I would open any app, so I tried about 2 other ROMs (S3n5eay/Pyramid3D) and same thing, so being fed up I restored my backup and then I began to have superuser problems, so I unistalled updates, cleared data, and still was unable to gain root access. I kept clearing data, installed superuser 2.3.6 then 3.02 and finally got root again, but everytime I reboot I lose root. I then again tried different ROMs, and same thing is happening. I have used superwipe script, ARHD's wipe script, P3D wipe script, formated from CWM, and no matter what, I am still unable to keep a new ROM and keep losing root with my backup. I'm sorry for a long post, but can anyone please help me figure this out. I have upgraded ROMs many a times in the past on this phone and others, and have never experienced these problems, so can someone please help me.
I kinda had the same problem with you, with that being root was the problem. But the ROM's are pre-rooted so that shouldn't be a problem. Try to flash the root file again, until it is succesfull flashed.
Thanks. I'll go ahead and try that.
Sent from Sensational toy running ARHD 3.1.1
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
West0000 said:
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
Click to expand...
Click to collapse
Well for the most part everyone downloads different software. For that just one of the factors that make us all somewhat "different" this is why everyone has some sort of problems here and there.
Most times a fix can be a reboot or reinstall of the app. Even clearing of caches helps because of data conflicts on the phone. Especially when someone like me that flashes different ROMS, that's why nandroids and backups are key so that if you fudge up your phone, you can always revert back to your nandroid.
And for all the people who are trying to revert back to their nandroid after flashing a different rom, you need to use the wipe data scripts in ARHD or Coredroid to reformat the ext4 before reverting your nandroid. Just a FYI.
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
cbrvnm said:
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
Click to expand...
Click to collapse
Keep trying different ROMs and different strategies of when you wipe/restore stuff. It's quite interesting that theoretically identical phones can have different responses to the exact same actions. 2 people can install a ROM in the exact same way and for 1 it will work, the other it won't. You just gotta work it out until you figure out how to manage your particular issues.
Yeah, I hear you. It's just very frustrating when in the past I have switched ROMs on all the phones that I have ever owned without any problems until now. But I'll try different methods and see what happens. I appreciate everyones input. Thanks. Oh, and if anybody has any other suggestions, please, share.
Ok, I was able to get Pyramid3D v0.8.0 working so far. I flashed with superwipe about 3 times then installed the ROM. I did not sign into my account, and installed my apps from titanium first, and then signed in. I got several reboots with setcpu so I unistalled it. I also get a few market fcs. Now the problem that I have is that I installed the 4EXT recovery and my phone is unable to play my music files through any of the music players. I am able to open them with astro, but not music player. But I guess I'll try to figure this one out now. Thanks for the advice.
The Janitor Mop said:
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Click to expand...
Click to collapse
Good post. I didn't realize I should be doing so much wiping even before restoring a backup.
Incidentally, I'm kicking myself now, but in the excitement of flashing my first custom ROM, I forgot to backup my original system. Doh. It's the only time I haven't backed up before changing ROMs, but that's arguably the most important backup to make.
i have CM10 and android 4.1.2 on my one x (att), i want to upgrade to 4.2.2.
if i install the new rom and gapps do i need to flash a new boot.img or will the one i have still work?
also what is the best way to restore my settings to the new version? i spent lots of time setting this phone up with and and i'd prefer to migrate as much as possible. I would appreciate if if you treated me as a newbie with the migration and are descriptive in your response as i have never done this before.
TIA
You can probably find out more about upgrading from CM10 to 10.1 by looking through the 10.1 thread. I'm almost entirely a Sense person, so I can't speak specifically to this situation (moving from CM10 to 10.1). But seeing as you are moving from one Android build to another, I'd assume you need to treat it as moving to a "new" ROM. I would also bet that you need to flash boot.img again. It only takes a minute to do, so why bother even trying to skip that step?
In general, if moving from one ROM to another, you should wipe user data, and not migrate system data, and migrate as few settings as possible. Migrating system data is almost sure to cause serious bugs, and migrating settings can be problematic also.
Recommend using Titanium Backup to migrate apps and data (but not system data), and if you get the paid version, its well worth the couple dollars to get the batch function (can backup and restore all your user apps with just a couple taps).
Do any other backing up you want to do (I like to backup my text messages by using the app SMS Backup+). And if you like, use TWRP to make a nandroid backup, in case you want to revert to your current ROM.
Then before flashing CM10.1 factory reset only within TWRP (factory reset in hboot will corrupt your SD card). Factory reset will wipe any user data (but should leave the internal SD untouched). So be sure to backup anything you want to keep, beforehand. Then wipe Dalvik and cache, also within TWRP. Then flash the ROM, boot.img and gapps. Then startup the ROM, restore your apps with Titanium. Then setup your homescreen and settings to your liking. Some people also like to migrate WiFi and Bluetooth pairings (I think Titanium will do it). Especially handy if you have a lot of pairings. But I don't have many pairings, and migrating them never seemed to work right for me, so I just do it manually.
Really, setting up from scratch is not that hard. With the help of Titanium, I can be back up and running in about 20 minutes.
You shouldn't have to flash a new boot just flash the new Rom over the old one. As long ast there there both cm something your good. But make a backup in recovery just on case
Sent from my HTC One X using xda premium
Arrow44 said:
As long ast there there both cm something your good. But make a backup in recovery just on case
Click to expand...
Click to collapse
I don't think you mean that literally. If you were to go from CM9 to CM10, and not flash the kernel, I don't think that would work.
Even going from CM10 to CM10.1, it would require the kernels being the same, or at least similar enough to not cause any problems. Have you tried this yourself, or read others tried it on the CM thread?
Are you sure you aren't thinking of just going from one nightly to another?
Also assume the OP is hboot 1.14 or higher, and S-on. Otherwise flashing boot.img separately is not an issue at all.
redpoint73 said:
I don't think you mean that literally. If you were to go from CM9 to CM10, and not flash the kernel, I don't think that would work.
Even going from CM10 to CM10.1, it would require the kernels being the same, or at least similar enough to not cause any problems. Have you tried this yourself, or read others tried it on the CM thread?
Are you sure you aren't thinking of just going from one nightly to another?
Also assume the OP is boot 1.14 or higher, and S-on. Otherwise flashing boot.img separately is not an issue at all.
Click to expand...
Click to collapse
thanks for the relies, i backed it all up this morning and tried to flash the latest nightly and the htc screen just hung, so im guessing i need to flash the boot.img, i need to do that home where i have the android sdk tools installed.
as far as migrating the data, im guessing that's not practical with what appears to be two separate builds... sigh, the 10.1 night came out a week after installed cm 10. oh well at least im not still waiting for slow ass ATT to get me the update.
mike_311 said:
thanks for the relies, i backed it all up this morning and tried to flash the latest nightly and the htc screen just hung, so im guessing i need to flash the boot.img, i need to do that home where i have the android sdk tools installed.
as far as migrating the data, im guessing that's not practical with what appears to be two separate builds... sigh, the 10.1 night came out a week after installed cm 10. oh well at least im not still waiting for slow ass ATT to get me the update.
Click to expand...
Click to collapse
Sorry I come from sense based roms but I have a feeling you haven't heard of flash gui. http://forum.xda-developers.com/showthread.php?t=1453617
Sent from my HTC One X using xda premium
Hi!
I installed the latest SlimBean on my i9000, I came from CM10.0. It all went smooth, but when the OS started, I was quite surprised: all my old apps from CM10.0 were still installed!
I'm not sure whether this is a bad thing or that a complete clean install is more preferable? I think it was kind of handy, but maybe other things remain as well and make the system go slower?
I followed the official steps exactly:
From another JB or ICS Rom to SlimBean
Download device_x.x.zip, slim_gapps.zip.
Enter CWM, wipe data, format system ( in mounts and storage)
Flash Device_x.x.zip***, then MUST flash slim_gapps.zip (other files optional)
*** - If the flash is too quick ( < 5 seconds or so), reflash device before flashing common or other zip files.
Click to expand...
Click to collapse
Furthermore: do you guys think there is a lot of battery life gain with this SlimBean OS?
Thanks.
You should always wipe data when switching ROMs
Sent from my SCH-I500 using Tapatalk 2
Wizzie86 said:
Hi!
I installed the latest SlimBean on my i9000, I came from CM10.0. It all went smooth, but when the OS started, I was quite surprised: all my old apps from CM10.0 were still installed!
I'm not sure whether this is a bad thing or that a complete clean install is more preferable? I think it was kind of handy, but maybe other things remain as well and make the system go slower?
I followed the official steps exactly:
Furthermore: do you guys think there is a lot of battery life gain with this SlimBean OS?
Thanks.
Click to expand...
Click to collapse
I think you forgot to wipe data which is a "dirty install" and sometimes everything will work with no problems and sometimes you can end up with countless little problems. The more closely related the two ROMs are, the more likely a dirty install will be head ache free. Just remember if you do a dirty install and end up with problems, that you shouldn't report them as bugs until you have tried a clean install (wipe data, wipe cache, wipe dalvik cache).
Changes in battery life will depend a lot on how you use your device, so it is best for you to test it yourself. I noticed that you mentioned that you have a i9000, the best place to get questions answered about that device is here: http://forum.xda-developers.com/forumdisplay.php?f=748
I am quite ashamed of myself, sorry guys. The "problem" was that Google Market automatically downloaded the apps that I had installed on a previous installation because they were "my apps" and somehow Market thought I wanted them in my fresh install :S Thanks...
Problem solved - Thread Closed!
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.