I've been running CM 10, 4.1.2, on Verizon gn. Works fine.
But I can't leave well enough alone, and want to try 4.2.2.
That should be easy right, just flash the recent CM 10.1. No cache wiping. Right?
But if I do that and I don't like it. how do I go back? Is it as simple as just flashing CM 10?
Also, I have Ti backup. The backup folder is sdcard/TitaniumBackup. I've read that 4.2.2 creates /sdcard/0/ for data. Does this mean that my present backup will be deleted?
Any help appreciated.
Since you are migrating Android versions, I would recommend that you do a full wipe, so system, data, and cache (and restore apps from TiBu if you must). You can do a nandroid backup from recovery; if you don't like 4.2 just restore it. When restoring a nandroid backup everything will be exactly the same.
seandarcy said:
Also, I have Ti backup. The backup folder is sdcard/TitaniumBackup. I've read that 4.2.2 creates /sdcard/0/ for data. Does this mean that my present backup will be deleted?
Click to expand...
Click to collapse
I just upgraded from 4.1.2 to 4.2.2 and had the same concern about being able to go back if I had problems and knowing that the partitioning of internal storage would be changed.
I recently got my GN back from Samsung after getting the screen replaced. Before sending it off, I totally wiped and reset the phone to stock. I made sure I did a full Ti backup first, then a Nandroid backup, and finally copied the entire contents of internal storage via "adb pull" to my desktop computer. When I got the phone back, I reversed the process and was able to restore the phone entirely to where it was before the wipe.
I did the same operation before upgrading to 4.2.2, without wiping the phone. So if I'd have wanted to go back to 4.1.2, I'd have wiped the phone, including internal storage, and restored as described above. I'm pretty confident that this would have removed the new partitioning from 4.2.2 and reset it to where it was before the 4.2.2 upgrade.
Sorry to be dense, but...
So I do a nandroid backup from TWRP 2.4.4.0, system, data and cache
From TWRP flash the CM 4.2.2.
Do nandroid restore from TWRP?
Flash gapps, restore apps from TiBu.
Now if want to go back to 4.1.2:
Flash 4.1.2, wipe system data cache.
Flash gapps, restore apps from TiBu
Do I have this correct?
Nandroid the entire thing from TWRP, wipe system, data and cache from TWRP, flash CM10.1 and gapps from TWRP, restore apps from TiBu in ROM. If you don't like it just restore the nandroid from TWRP. TiBu only restores apps, nandroid restores everything: ROM, account, system settings, apps, etc.
The only extra thing I referred to was making a full copy of your phone's internal storage to your computer using "adb pull". This would allow you to wipe the internal storage and restore it, in case the partitioning change from "/storage/sdcard0" to "/storage/emulated/0" needed to be removed. But if TWRP's nandroid backup and restore takes care of this, this step isn't necessary.
How easy? Dead easy.
Sent from my Nexus
Related
Can someone explain a few things about backups and ROM flashes, please?
I've got a custom ROM on my Desire, and I'm using an Ext partition to hold my apps using App2SD.
I've run a full backup with Titanium Backup.
If I want to wipe and flash a new ROM, how does it work?
I do a factory reset, wipe cache, wipe dalvic.
I then flash a new ROM. New ROM will presumably be faced with the apps I've already got on my SD card ext partition.
Do they just install back, or do they cause problems?
If I reinstall Titanium Backup on the new ROM and restore everything, do I end up with new ROM and all my old apps back as they were before?
Or do I need to wipe the ext partition too, before doing a restore?
Any pointers would be great.
Ric
Doing a factory reset wipes all apps so if you do that before flashing the ROM all the apps will be gone from your ext partition.
You can then restore your apps using titanium backup. Be careful though, your market apps are fine to restore but you should be very selective about restoring system apps. I only restore data on the green coloured system apps to get back things like SMS, my custom sense layout, that sort of thing.
If you go from sense to non-sense ROMs then you may not even want to do this much.
I rooted, did a CWM backup and also did a titanium backup. I downloaded a jelly bean ROM and dragged it into my phone. My question is this. After I do a wipe and then install the ROM won't titanium backup be deleted? How will I restore from titanium after I install the ROM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jackryan57 said:
I rooted, did a CWM backup and also did a titanium backup. I downloaded a jelly bean ROM and dragged it into my phone. My question is this. After I do a wipe and then install the ROM won't titanium backup be deleted? How will I restore from titanium after I install the ROM?
Click to expand...
Click to collapse
TiBu backs up to your internal (or external) sdcard, which doesn't get wiped when you do a wipe & factory reset (cache, dalvikcache, system, and data partitions), so you're good to go as long as you remember not to format your sdcards. Just re-install TiBu + TiBu key (paid) after flashing the ROM, then restore. If you're worried, tell TiBu to backup to DropBox or GoogleDrive instead.
zmore said:
TiBu backs up to your internal (or external) sdcard, which doesn't get wiped when you do a wipe & factory reset (cache, dalvikcache, system, and data partitions), so you're good to go as long as you remember not to format your sdcards. Just re-install TiBu + TiBu key (paid) after flashing the ROM, then restore. If you're worried, tell TiBu to backup to DropBox or GoogleDrive instead.
Click to expand...
Click to collapse
Thank you for the reply! I just assumed a wipe would wipe everything. Thanks again.:good:
I noticed in TWRP 2.5 that there is the option to backup/restore 'Preload'. I have also read that the ROMs based on TMo 4.1.2 need preload working properly to boot, unlike previous ROMs. Should that option to include it be checked when backing up and restoring the stock 4.1.2-based ROMs?
I've also noticed that the the Preload size is 0 when backing up other roms in TWRP, so I haven't concerned myself with it. Before TWRP 2.5, I knew nothing of preload (I guess I still don't really know anything). Any thoughts?
Well, I guess I'll find out what to do by trial (and error?). I backed up JMT JB3 (including preload) to flash the Koodo update and run it for a while. I'll restore it later on and see how it boots.
I'm not sure how it works. I'm on JMT3 myself right now. I used ODIN to update to the official release when it came out, and it was doing fine, but I wanted to try some of the custom ROMs out there that are based on it. I was rooted with CWM, and did the usual backup that has worked since I can remember. I don't remember what ROM I tried next, but I didn't like it much, so I restored my back up. It restored correctly, or so I thought. After some use I started getting FC here and there. I couldn't fix it, so I did a factory reset from within the phones settings, not through recovery. As soon as it tried to reboot I kept getting a boot loop. I never was able to get it booted. I was able to boot to recovery, flash cache and wipe scripts that were recommended, and flashed JMT3. All is good now. I know trying a cache wipe or factory reset through CWM won't work since I tried it before, so I didn't even try it for this one.
So long story short I don't know how CWM (or any recovery) handles the preload. All I know is the scripts work to flash clean, or wipe cache/dalvik/fix perms, but I haven't gotten them to work after restoring a back up. My thinking is to be careful until someone figures it out because I don't think backing up will help if I ever need to. I'll have to start fresh each time I want to flash anything.
Here are the scripts I'm talking about: http://forum.xda-developers.com/showthread.php?t=2235141
Thanks for sharing your experience. I have those same scripts handy - had to use them when I flashed JMT3.
If or when I restore, I figure I'll wipe my current preload and restore the preload in my JMT backup, then flash the Infamous cache wipe script (or equivalent function in recovery if TWRP develops something similar). I'll post again to share my results when the time comes.
I ended up wanting to restore old stock 4.0.4 in TWRP 2.5.0.0 recovery. Part of me wanted to do it just so I could test the backup/restore of the preload.
I first backed up my current rom (stock Koodo/Telus 4.1.2) with the cache and preload included. I then wiped data, system, caches and preload, and ran the restore of my old backup. The 4.0.4 booted just fine. Once I was done checking for the info that I wanted, I went back to recovery and wiped all the same stuff (everything except internal and external SD) under advanced wipe options. I then restored my stock Koodo/Telus 4.1.2 backup. It seems to be running fine now although I haven't experimented much to test for any FCs. It didn't seem to have any issues booting at least.
I may have been doing some excessive wiping - I assume restoring a partition also formats it before overwriting it. I'm not even sure I needed to wipe anything to restore 4.0.4, but I didn't want a preload (110 mb) causing issues in a rom that doesn't need it at all. In any case, I know what can be done to avoid issues restoring stock 4.1.2, although I'm still not sure what needs to be done to avoid issues.
You did it exactly right. When using a 4.1.2 Samsung rom, be it custom or stock, and backing up or restoring; the preload folder is just as important as data or system. Basically the point of the preload patition is to get the system partition to fit. By symlinking the apps from preload to system Samsung has saved room and allowed a bigger rom to work on our hardware.
As an example, I am on TWRP 2.4.? and cannot backup preload. When I tried a different rom, then went back to my backup I had FCs like crazy. Because I had used the Infamous wipe script it had wiped the preload folder but there was nothing to restore to it from my backup. I had to reflash the rom I was using (really I just wanted the preload folder installed) and then restore my backup to get it working.
I hope all this makes sense. I'm going to Twrp 2.5 so I can backup my preload folder (when I stop being lazy).
Thanks guys.
I took a Nandroid backup of my stock phone (all partitions) before I flashed a new ROM (DN3). Then I decided to return to stock ROM, so I wiped phone and restored Nandroid backup (all partitions except bootloader and recovery).
Now the phone will not boot, it just shows a logo and then a black screen. I can connect to it via ADB however.
I thought Nandroid backup was a safe way of preserving phone, but it seems it cannot actually be trusted?
number_thirty_two said:
I took a Nandroid backup of my stock phone (all partitions) before I flashed a new ROM (DN3). Then I decided to return to stock ROM, so I wiped phone and restored Nandroid backup (all partitions except bootloader and recovery).
Now the phone will not boot, it just shows a logo and then a black screen. I can connect to it via ADB however.
I thought Nandroid backup was a safe way of preserving phone, but it seems it cannot actually be trusted?
Click to expand...
Click to collapse
depends on bootloader i guess, but maybe try wipe data and preload / cache and dalvik and reflash, make sure ROM to flash is on external sdcard as may lose all data on phone
Having the same issue after re-partitioning my phone. My nandroid backup is about 2.3gb and it took about 200 seconds to restore. Nothing was actually restored when I booted up. (This nandroid was made to my SD-Card, wonder if that makes any difference.
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!
I made a backup of my 5x when it was running rooted/xposed 6.0.1 but then decided to update to 7.1.1 to try out the new features. But now I really miss a lot of xposed modules so I decided that I want to restore my 6.0.1 backup that I made a couple of weeks ago. So I flashed the 6.0.1 factory image from Google's developer website and was able to successfully boot into Marshmallow again. However after installing TWRP I tried restoring the backup (through USB OTG) after wiping system and cache and a doing factory reset but it pauses on "restoring system image" for a brief moment then proceeds to reboot by itself despite that it's only 27% complete. The reboot however does not go to completion and so the phone is stuck in a bootloop. I'm really not sure where the problem is here. Is it TWRP? Or the backup file? What can I do?
Which version of TWRP have you used? By any chance the backup also contained EFS?
marioemp2k7 said:
Which version of TWRP have you used? By any chance the backup also contained EFS?
Click to expand...
Click to collapse
I used version 3.0.2-2.
And isn't EFS supposed to be backed up anyway? I just checked the backup folder and it contains 4 files that begin with "efs". Should I delete those and try again?
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
marioemp2k7 said:
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
Click to expand...
Click to collapse
I made the backup while I was running 6.0.1 and I flashed the 6.0.1 factory image so they both should have the same vendor image.
I also tried wiping everything except for internal storage and I unchecked "EFS" when restoring the backup but the same problem still persists, the phone automatically reboots itself before the restoring is complete and gets stuck in a bootloop. I'm not sure where the problem is at this point. I guess I'll just have to start from scratch again