I am running NexusHD2-ICS-CM9_V1.3 which is working great, is there any advantage in upgrading to a later version and if so do I just flash the new ROM from recovery.
1. Title with [Q] then your username? Really? :')
2. v1.3? You're a good few months behind there mate, obviously there's going to be a huge advantage to updating. There have been so many fixes and improvements since then, I don't see how you can even use that as your daily ROM tbh.
3. On occasion there have been major updates which require a wipe and fresh install. Check the changelog to see if this is the case for any of the versions after v1.3 I think the required partition size also increased at some point. Since you're so far behind I'd recommend backing up your data with Titanium backup and CWM, fresh installing v2.7 (just wipe in CWM, no Task29 BS) then restoring your data.
Related
Hi all,
This is probably a pretty basic question for you, so please bear with me, and if it is basic, hopefully there is a straightforward answer .
Having settled on the awesome CM-6.1.0-RC1, I haven't looked to change ROM.
However, with CM-7.0.0-RC1 being released, its time to upgrade .
Can anyone please explain the steps needed to follow in order to go from CM-6.1.0-RC1 to CM-7.0.0-RC1 please?
I appreciate there is a lot of info in ali ba's dev thread [ [ROM] CyanogenMod experimental builds] however, there is approx 235 pages there, and the OP is a little lite.
Would it be possible to have guide here, as I presume many people will be wanting to follow the same upgrade path.
I am wondering how we can 'save' apps, [i.e. Angry Birds status, web browser installation, general settings/config,] during the upgrade... because I am guessing a full wipe is required and therefore a Nandroid backup won't really help...or will it?
Anyone that can help?
I'm also running CM6.1 rooted and I've tried upgrading by downloading Rom manager and then booting into recovery, doing a factory reset/wipe data/wipe cache/wipe dalvik cache - and then flashing the CM7 RC1 zip but I get a boot loop every time.
I've tried removing the SD card and Sim card but same error appears.
Actually it's weird because I've been getting a boot loop with every firmware I've tried to flash except for CM6.1.
Luckily I did a Nandroid backup...
c_man said:
Can anyone please explain the steps needed to follow in order to go from CM-6.1.0-RC1 to CM-7.0.0-RC1 please?
Click to expand...
Click to collapse
First question should be:
Do we need to wipe when upgrading from CM6.1?
If we need wipe, I suggest you to:
- do a nandroid backup
- backup all apps with titanium backup
- wipe + flash 7.0 RC1
- download and install gapps
- restore apps with titanium backup
If no wipe required:
- do a nandroid backup
- flash 7.0 RC1
Question: does UOT kitchen (for circle mod battery) works with 7.0?
gilliu00_ said:
I'm also running CM6.1 rooted and I've tried upgrading by downloading Rom manager and then booting into recovery, doing a factory reset/wipe data/wipe cache/wipe dalvik cache - and then flashing the CM7 RC1 zip but I get a boot loop every time.
I've tried removing the SD card and Sim card but same error appears.
Actually it's weird because I've been getting a boot loop with every firmware I've tried to flash except for CM6.1.
Luckily I did a Nandroid backup...
Click to expand...
Click to collapse
http://forum.cyanogenmod.com/topic/15838-cyanogenmod-7-for-legend-v700-rc1-2152011/
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full ourput.
Please use Pastebin when possible
Skardy said:
First question should be:
Do we need to wipe when upgrading from CM6.1?
Click to expand...
Click to collapse
Yep, true.
Anyone?
Upgrading from earlier version of CyanogenMod 7?
* Perform a NANDroid backup of your current ROM.
* Flash CyanogenMod (your Google Apps will be backed up & restored automatically)
Click to expand...
Click to collapse
So no, you do not need to wipe before upgrading,
The backup is just for security reasons. You never know what could go wrong, so it's good to have a backup in place.
Just flash the new CM 7 and you should be good to go.
^ Mastacheata - thats if you're upgrading from earlier version of CyanogenMod 7
That question we are asking here is what if you're upgrading from CM6.1.
Oh I'm sorry, I misread that the whole time.
Gonna try it now and report back in a few minutes.
I've not gone 6.1 -> 7rc directly, but I did go from 6.1 to a 7 nightly build a couple weeks ago without wiping and I don't seem to have any problems (except GPS not working).
I'm thinking I may just do a full on Titanium backup, full wipe, then go for CM7.0RC1.
easyonthev said:
I've not gone 6.1 -> 7rc directly, but I did go from 6.1 to a 7 nightly build a couple weeks ago without wiping and I don't seem to have any problems (except GPS not working).
Click to expand...
Click to collapse
GPS not working in CM7.0 RC1 ??
Do we even have a list of things not working in CM7.0RC1? Again, the OP in the dev thread is a little lite with respect to 'known issue' and similar.
My test was unsuccessful.
I was neither able to install directly over 6.1 nor with prior wipe.
My phone would always end up in a boot loop.
Logcat did tell some Exceptions for unknown permissions.
Detailed explanation will follow in the developer thread.
i accidentally flashed cm7 build 0 over cm6.1 stable before. was able to boot but my phone was laggy & some features were broken, as far as i can remember. so i guess the best path is:
TI backup
complete wipe
flash cm7
TI restore
cliche by now, i know. but it never fails...
As we start the RC phase of CM7, many of you are now taking the leap from CM6 stable to the new RC's.
Some of you may be able to get away with doing this without a wipe; however, most of you will not be that lucky.
Differences in the rom, files system, and even Google Addons will likely throw most of you into boot loops.
Therefore, here is my recommended upgrade path:
1) Nandroid backup your current rom
2) Update your recovery to the latest available (CWR is my choice)
3) Format system via recovery
4) Wipe/Factory reset
5) Flash CM7 then Google addon 1/20
If any of you have data that you must absolutely save, then and only then should you use Titanium backup (or other backup apps) to restore your data. Please be sure not to restore any data to /system using these apps, as this will mostly likely corrupt your ROM and/or Market.
Click to expand...
Click to collapse
Here is what CM Team recommends
Skardy said:
Here is what CM Team recommends
Click to expand...
Click to collapse
Perfect, I shoud've found that myself .
Now its just a question as to whether to go to CM7.0RC2 - lots of people still reporting bugs...
I have a T-Mo G2 and want to keep my Froyo image to reinstall later if I cannot get theGingerbread to work right. I want to make an image file that will restore the phone to exactly how it is now. I have tried all kinds of stuff, but am not able to make the "img" file so that I ca do a restore when booting...
Can someone point me to what I need to install to do this, and if possible some directions on what/how to create the "img" or restore file ?
I would be most appreciative, as I had to reverse everything from the OTA of Gingerbread, since too many apps didn't work, ESPECIALLY the GPS!
My current Froyo is a temp-root system.
Thank you all!
Aloha. .
I would do full root via the wiki, and then install 4EXT (the full one that's like $2) - it will keep your old stuff straight
Ditto on previous reply
Root your G2
Backup all your apps with using Titanium backup
Get Clockwork mod ROM manger or 4ext ( I prefer 4ext) and backup your stock rom. You can download new ROM CM7 for first ROM.
If you don't like the ROM you can restore your stock ROM with CWM or 4ext at anytime.
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
WTF? said:
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
Click to expand...
Click to collapse
1. I have had zero problems with TB personally.
2. Without it your app data is gone.
3. Triple wipe, takes a few extra minutes and makes a world of a difference.
4. Do not restore system data!
5. Check md5 sums BEFORE doing anything!!!!
6. Make sure you have a recent nandroid backup and you'll be fine either way.
7. triple wipe before flashing anything including nandroids. Preferably with different wipes aka factory reset, superwipe+ ext4, then recovery wipe!
Just my 2 cents, it's saved my a$$ more then a few times...
Have flashed and rooted - can someone confirm
a) OTA updates no longer work - what will happen if I accidently OK the install prompts - is there any way to suppress these?
B) best app to made backups - clockwork recovery with titanium backup - if I make full nandroid - will titatium restore all apps fully?
c) I plan to test out paranoid android first then probably the modoco ROM - any other suggestions
Thanks in advance
A)No, OTA updates will not work if you're rooted. I don't know what would happen, but it wouldn't be pretty. Don't sweat it, just don't accept the update
B)I back up my apps with titanium backup, so j can restore them onto new ROMs that I flash and still have the same in app data and whatnot, but if you do a nandroid, it will backup everything into a (somewhat large) file, apps included. I use ROM manager to create my nandroids, but you can do it in clockwork mod recovery without the app too.
C)As for what ROM, its a good idea to try a few out, then settle with the one that you like and enjoy using the most. I would suggest at least try out the glazed jellybean ROM, super smooth and stable
Hi Guys,
Im looking to update my dads phone today and just have a quick question (it been a while since i did it and am a bit rusty)
Basically he currently has MIUI-STABLE V5 by langthang android 2.37 installed (i know i used Magldr for this but arnt sure of the exact process)
I basically just want to update to the last gingerbread Miui Rom (so i can just keep all his data as it is, not fussed about JB or ICS) i beleive this is 2.4.20
If i were to just drop this into the root of the sd card could i just use CWM to install this ROM without the need to do a system wipe? and just do Dalvik and Cache? Im hoping this will then put the phone on a stable build (it was having bluetooth issues)
Also once that is done can i add a EXT3 partition on the sd card(something i forgot last time!! and it now says no storage)
Thank for any help,just to sum up haha, i just want to update the rom to solve the BT issue, and add a EXT 3 (i found some instructions fo this) so it has more 'system memory' thanks for any help guys.
If it's the same ROM and uses the same /system partition (on occasion they change even if the ROM is the same) then that should be fine. I'd strongly recommend backing up in Titanium backup first at the very least (CWM backups can take a long time) just in case something goes wrong.
Nigeldg said:
If it's the same ROM and uses the same /system partition (on occasion they change even if the ROM is the same) then that should be fine. I'd strongly recommend backing up in Titanium backup first at the very least (CWM backups can take a long time) just in case something goes wrong.
Click to expand...
Click to collapse
Thanks for your repl, im not 100% sure if its technically the same ROM, as the one installed (stil MIUI and GB) was a modded one from here. and the one im looking to install is the 'official' MIUI one (Still GB)n
Lidds123 said:
Thanks for your repl, im not 100% sure if its technically the same ROM, as the one installed (stil MIUI and GB) was a modded one from here. and the one im looking to install is the 'official' MIUI one (Still GB)n
Click to expand...
Click to collapse
In that case backup and fresh install, it won't work if it's not the same ROM. If the system partition is the same, wipe in CWM then flash the new ROM. Download and install Titanium Backup on your new ROM and restore your apps.
Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Any information you guys can offer would be great. Thank you so much for your time !
Downloaded7 said:
Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
A backup in CWM is the same as a nandroid backup. It basically take a "snapshot" of your ROM and restore it exactly as it was when backing up.
Titanium Backup is an app that backup your apps and app's data. It's recommend you only restore user's apps and data. Let Google restore any system app's data.
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
Wiping data/factory reset only wipe the data. Wiping system will wipe your ROM (system partition) Of course you don't want to wipe all the files such as the ROM you're going to flash.
There's an option to format internal sd, that will wipe EVERYTHING so unless you know how to ADB push files or sideload a ROM, DO NOT touch that.
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
No, just flash kernel. Some recommend wipe cache and dalvik cache after kernel flash before reboot.
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Different app that does the same thing. Usually go with what is recommend by the ROM's dev. I ususally just leave what's included with the ROM.
Any information you guys can offer would be great. Thank you so much for your time !
Click to expand...
Click to collapse
Hope that answer some of your questions. I'm sure I left out some stuffs so hopefully someone else can add to it.:good: