How to update CM9 Nightly when newer versions are available without having to flash the new ROM, So that i can keep my settings and apps as it was before.
Any better ways than backing up and restore.
I think flashing between CM9 nightlies doesn't require wipe data. You can flash normally but if you change between ROMs or different android version (2.3 going to 4.0) you need to wipe.
Also, if you want to backup, I suggest Go Backup or Titanium Backup
Hi guys,
strange question: I was on an old MIUI GB ROM and decided to upgrade to the official MIUI JB ROM. Saved everything using MIUI backup. I then installed the ROM (NativeSD) and everything went wrong. When I finally got it working ok, it was way laaaaaaaaaagy, so I decided to try tytung's CM10 JB ROM.
Stupid me - didn't take a Titanium or image backup in recovery. I do however have the MIUI backup file. Anyone know of a way that I can either automatically or manually use the data in the MIUI backup to restore at least my game saves, SMS's etc in CM?
Any help appreciated!
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4
Just as title states, I always spend a lot of time after restoring apps and data from flashing a new ROM getting my screen and layout and folders and widgets as they were prior to flashing a new ROM.
Is there a way to restore all this quickly?
NO
The problem you're having is when you install a different ROM you usually "Wipe" everything. If you don't wipe /data then everything you have is still there. However you will have problems going from one custom ROM to another, as each developer has made some tweaks to the system packages.
Generally speaking, if you are running a "Stock Odexed" ROM you could possibly dirty flash a "Custom Odexed" ROM.
Same goes for Deodexed to Deodexed. You will have problems if you try to cross dirty flash a ROM.
So the simple answer to your question is NO there is no easy way, even if you backed up your Applications using a tool like Titanium Back Up.
If you are just updating the same ROM, the developer will say to either Clean Flash (wipe everything) or Dirty Flash (IMO still wipe cache and dalvik). If you can dirty flash everything will still be just as you set it up.
Got everything restored already, I'll have to just suck it up then I guess.
Just makes me wonder how flashaholics do it.
On my G900P, I made a CWM NANDroid backup of 4.4.4 stock rooted ROM. Then I did a full wipe and installed Cyanogenmod 5.0 ROM. Then to revert back I wiped everything (including dalvik cache) and tried to recover the NANDroid backup, which seems to complete without errors, but every user application will force close when launched. Also, SMS or Calls cannot connect.
So is the NANDroid backup corrupt? Did it not flash properly when I recovered it? (tried multiple times)
My suggestion would be to flash the stock rom which is the same version as your NANDroid, 4.4.4, first. Then restore your NANDroid backup.
You shouldn't have to, but it might work.
That doesn't seem to work. The apps still force close / stop working over and over. Here's a lengthy logcat. Anyone have any ideas?