Hi,
I'm running CyanogenMod 7 Nightly on an Incredible S. I was on Nightly #68 and today I updated to #89. For the update, I backuped my rom, wiped the Data and Dalvik cashes as is recommended. When the update was done, I had to re-setup my phone from the Android's first boot screens as well reinstall all of my apps and set the options like they were beforehand manually.
I'd like to know if there is a way to make updating roms a little quicker by not having to go through this whole process every time? ie: update rom and still have the phone as it was. I could understand that it may not be possible when going from CM to Virtuous Unity for example. But I'm wondering if I'm missing a step when it comes to simply updating the version of a single rom?
Thanks for any help!
You need a partition with the stable ROM and one to experiment with Nightlies.
lifehacker.com/5826050/how-to-dual-boot-multiple-roms-on-your-android-phone
There is no need to do any wipe going from one nightly to the next.
If you do wipe don't wipe data and you don't have to do set up again.
I do recommend titanium backup for times that you have to do full wipe.
Alright, thanks guys! I should be good to go now!
Sent from my Incredible S using xda premium
Related
As you all know, before installing new rom we we have to wipe data and cache in recovery...
But do we have also to wipe dalvik's cache?
As you read on every ROM thread, it is advisable to do a CLEAN wipe meaning all of it before installing a different rom. I personally don't find any difference between wiping and not wiping.
When upgrading CyanogenMOD nightlies wiping is pointless, and a waste of time. When switching between Sense-based ROMs and CM etc. then a full wipe is recommended, but not always needed. Wiping dalvik cache will never hurt
Just a thought here, but isn't DC in /data ? So if you wipe data you wipe DC as well, no?
I've been flashing Mdj Droid L2.1.110210 rom but the only thing I am seeing is the HTC screen for over 10 minutes. Is there anybody helps me to solve this issue? I am newbie so I cannot post in Mdj Droid L2.1.110210 topic.
Thank
I always wipe because it cleans the dust. As GrammarFreak said, when switching between CM nightlies, it is pointless as of the minor changes that come with them. But switching to an entirely new ROM (like stock -> CM) I thin it is better to wipe everything. The cause: Android DO collect junk, and a clean system is always nice.
Regarding contact, sms and other app data: backup to phone and cloud, simple as hell.
thanks for the advice. so if you flash anew rom, do u lose all ur apps every time? i'm flashing ics on my g2 alpha 8 right now. so i will find out soon enough
shinobi3432 said:
thanks for the advice. so if you flash anew rom, do u lose all ur apps every time? i'm flashing ics on my g2 alpha 8 right now. so i will find out soon enough
Click to expand...
Click to collapse
In my experience (using a HTC Desire HD) you only lose your apps and settings when you perform a full-wipe before flashing a new rom. When you update your rom without wiping, your settings and apps are not removed. However, I personally like to do a full-wipe before flashing a rom, because it clears out al the dust and gives you a fresh new phone.
If you don't want to lose your apps and data, but you do want to wipe, you can offcourse always use Titanium Backup to make a backup of the apps and data.
Just do it! It's free (costs only a slightly longer startup the first time after you wipe dalvik)!
aiuvoanh said:
I've been flashing Mdj Droid L2.1.110210 rom but the only thing I am seeing is the HTC screen for over 10 minutes. Is there anybody helps me to solve this issue? I am newbie so I cannot post in Mdj Droid L2.1.110210 topic.
Thank
Click to expand...
Click to collapse
in my experience, this happens when you dont clear the cache prior to updating the rom. in my case, I had to re-apx mine, since I didnt figure this out until I had tried the factory rom. good thing I had the SBK and CPUid, or it would have been even a more painful experience!
My friend and I flashed MUIU onto his Vibrant we were coming from trigger 3.2. Everything was going great it work for about a few hours then a force close kept appearing.
android.process.acore
It will not let him use his keyboard or even get to his messaging app.
We have wipe data cache and davilk and even went to ROM manager and fix permissions.Still didn't work. Should I just ODIN back to stock re-root and find a different ROM or can this be fix's.
Need more information, like what version of MIUI you installed, did you make sure it was the one made for the Vibrant and not a different Galaxy S variant, did you follow all the instructions, did you wait the full 10 mins after first flashing it, did you try restoring all your apps + data with a non-MIUI backup program like Titanium Backup, did you try to restore system apps...
Anyway, try a complete re-install of MIUI. Follow the instructions posted in the MIUI thread to a "T".
I installed the latest build off of the thread in the vibrant forums. And yes I used titanium to do a restore
Sent from my ADR6400L using xda premium
I didn't wait ten minutes. What does that do. There weren't any instructions just wipe and flash.
Sent from my ADR6400L using xda premium
http://forum.xda-developers.com/showthread.php?t=1123922
that is the Rom we flashed
I think you might want to start from scratch and follow this link:
http://forums.miui.us/showthread.php?1189-Installing-MIUI-from-any-Non-MIUI-rom
As a rule you generally can not jump immediately from a non-MIUI rom to MIUI without resetting some parameters. In addition, you also need to be on FROYO bootloader instead of Gingerbread.
Anytime I run into issues with any ROM the first thing to try is a simple re-flash of the ROM. This fixes problems 97% of the time. If all else fails ODIN will take care of any other problems for the other 2% of the time. The other 1% is left open as nothing in life is perfect
I flash all MIUI/CM7 ROMs from a clean stock setup to ensure a good flash.
I am currently running the CM9 4/8/12 nightly. It was the first ROM that I have installed so far since getting my TP less than a week ago. I wanted to try the 4/12 nightly and just had a quick question before I do so.
I am using cell phone ROM flashing logic here, so please correct me if I'm wrong. Do I just need to download the latest CM9 nightly zip, put it on the root of my TP and just flash the zip through CWM? Of course I would clear cache and dalvik first. That's how I would do it with my phone but I just want to make sure that it's the same with the TP before I bork something.
Thanks!
I went from CM9 to AOKP. It was my first ROM switch. All I did was clear cache/dalvik and did a factory reset. I wanted to do a factory reset just to be safe. I dont know how it acts yet when you just clear cache. But the way I did it worked just fine.
WizeGuyDezignz said:
I am currently running the CM9 4/8/12 nightly. It was the first ROM that I have installed so far since getting my TP less than a week ago. I wanted to try the 4/12 nightly and just had a quick question before I do so.
I am using cell phone ROM flashing logic here, so please correct me if I'm wrong. Do I just need to download the latest CM9 nightly zip, put it on the root of my TP and just flash the zip through CWM? Of course I would clear cache and dalvik first. That's how I would do it with my phone but I just want to make sure that it's the same with the TP before I bork something.
Thanks!
Click to expand...
Click to collapse
You are right... just download the latest nightly zip to your internal sdcard and flash away... wiping Cache and Dalvik in the process... nothing really different here as compared to the methods you used on your phones.
Thanks fellas!
Hi,
My i9100 runs CM 10.2 Nightlies and I install these in this sequence:
Reboot recovery'
Format /system
Wipe Dalvik
Wipe /cache
Install new CM nightly .zip
This works every-time, except if I try and install the CM 10.1.3 Release Candidate. In this case my phone boots and displays the CM rotating boot animation until the battery runs out of juice. If I boot into recovery and flash CM 10.2 then my phone boots correctly.
Does anyone know how one should downgrade from 10.2 to 10.1.3?
( If you suggest a factory reset ( format /data) then please explain your logical behind your suggestion, if you could).
Thanks!
forgetmyname said:
My i9100 runs CM 10.2 Nightlies
if I try and install the CM 10.1.3 Release Candidate. In this case my phone boots and displays the CM rotating boot animation until the battery runs out of juice. If I boot into recovery and flash CM 10.2 then my phone boots correctly.
Does anyone know how one should downgrade from 10.2 to 10.1.3?
( If you suggest a factory reset ( format /data) then please explain your logical behind your suggestion, if you could).
Click to expand...
Click to collapse
Check these threads out first:
http://forum.cyanogenmod.com/topic/77376-cm-1013-rc-for-i9100-int/#entry406963
http://forum.cyanogenmod.com/topic/77807-how-to-downgrade-to-101-rc1/
:good:
Yes I do suggest a factory reset. It's recommended whenever you change android version to do a factory reset. Flashing a new nightly of the same android version it's ok not to (I still do) but when you upgrade /downgrade android versions unless you reset you'll get trouble, as you've already found out.
Edit: just read those links that immortalneo posted, there you go.
Sent from a galaxy far, far away
Hopper8 said:
Yes I do suggest a factory reset. It's recommended whenever you change android version to do a factory reset. Flashing a new nightly of the same android version it's ok not to (I still do) but when you upgrade /downgrade android versions unless you reset you'll get trouble, as you've already found out.
Edit: just read those links that immortalneo posted, there you go.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Hi, Thank-you for your links.
Funnily if I upgrade on Android versions I don't reset. I just format /system, wipe cache & Dalvik, and then install the right gapps. I have never downgraded before.
However, perhaps I could roll back to a 10.1 nightly backup I took with CWM, and then upgrade with this and avoid a Factory Reset
forgetmyname said:
Hi, Thank-you for your links.
Funnily if I upgrade on Android versions I don't reset. I just format /system, wipe cache & Dalvik, and then install the right gapps. I have never downgraded before.
However, perhaps I could roll back to a 10.1 nightly backup I took with CWM, and then upgrade with this and avoid a Factory Reset
Click to expand...
Click to collapse
I don't understand why you're shying away from a factory reset? If you're flashing ROMs it should be a regular part of your routine. Use an app such as Titanium backup to restore user apps & data afterwards. Doing a factory reset will erase everything which isn't compatible with the new ROM. Titanium, used correctly, only restores things which are compatible.
As for restoring your nandroid, if it's a downgrade, you should also factory reset before restoring it. Like I said, I don't know why you're trying so hard to avoid it.
Hopper8 said:
I don't understand why you're shying away from a factory reset? If you're flashing ROMs it should be a regular part of your routine. Use an app such as Titanium backup to restore user apps & data afterwards. Doing a factory reset will erase everything which isn't compatible with the new ROM. Titanium, used correctly, only restores things which are compatible.
As for restoring your nandroid, if it's a downgrade, you should also factory reset before restoring it. Like I said, I don't know why you're trying so hard to avoid it.
Click to expand...
Click to collapse
Hi,
Because restoring from TB all my apps took me 5 hours last time.
More importantly I have to add back all of my accounts (FB, Dropbox etc) and k don't always recall my passwords, so they all have yo have password resets. Factory resets mean several days of extra work. I have 1.5 hours each evening to myself and I'd rather watch TV (18 month old child is source of time consumption)) ).
Cheers.
forgetmyname said:
Hi,
Because restoring from TB all my apps took me 5 hours last time.
More importantly I have to add back all of my accounts (FB, Dropbox etc) and k don't always recall my passwords, so they all have yo have password resets. Factory resets mean several days of extra work. I have 1.5 hours each evening to myself and I'd rather watch TV (18 month old child is source of time consumption)) ).
Cheers.
Click to expand...
Click to collapse
:0 :0 how many apps do you have installed? It takes me about 10 min absolute tops. But sure, definitely spend time with your child
Hopper8 said:
:0 :0 how many apps do you have installed? It takes me about 10 min absolute tops. But sure, definitely spend time with your child
Click to expand...
Click to collapse
I have 51 apps and a few like Touchdown (for Lotus Notes) won't play well with downgrades or even upgrades sometimes. This is the bane of 'enterprise' applications...
Hi everyone! I was wondering if you guys had any thoughts how I could restore settings like the desktop configuration of all the shortcuts/widgets/folders setup to my liking whenever I do an update to this ROM's nightly releases? If there is an easy way to do this, I would be more apt to updating to each of the new nightly updates for CM 10.2, versus updating and then having to reconfigure everything to my liking all over again knowing I'll be doing this over and over till there is a stable release.
I saw another post when searching, but as it was from Feb 2011, I figured there would be some updated programs on the market. [Q] Restore settings after custom ROM/wipe as well as this was for a different phone.
Thanks in advance for the help!
If you only wipe cache and dalvik cache between flashing cm nightlies there should be no need to restore any kind of settings as they stay the same. The only time you would need to restore settings is if you do a full wipe ( most of the time a full wipe isn't needed when flashing between nightlies of the same Rom unless you start to experience glitches or fc's )
Sent from my HTC6435LVW using XDA Premium HD app
You can also do a nandroid backup, clean flash and make sure everything works okay, then restore just the data partition of your backup.
Sent from my Droid DNA using Tapatalk 4
Thanks guys! I tried .torrented's method yesterday afternoon and it worked. So I'll try that till I have issues and then after that I'll try jamiethemorris's method.