I ran in to an issue today.... I used CWM (Touch recovery 5.8.0.2) to backup my system then flashed the latest CM9 nightly. I was getting some force close issues so I tried to revert back to my backup. I got an "error restoring /data" and the restore stopped.
After looking in to it I think the issue may be the /data backup is over 2 gigs. CWM (or busybox?) has an issue with this and cannot restore (or maybe the way the tar archive is created gives the problem). I've read some people trying things like:
Split the data.ext4.tar file into half so they are less than 2GB.
Push both to the device using adb.
Execute "tar xvf data.ext4.tar -C /" for each part.
Click to expand...
Click to collapse
I tried this but got the error:
Code:
/data/media # tar xvf data.ext4.tar.001 -C /
tar xvf data.ext4.tar.001 -C /
tar: invalid tar magic
Help! How can I restore my backup?
I even tried some earlier backups but they all had the same error with /data.
Thanks!
I have heard bad things about touch recovery. have you tried restoring your backups with regular CWM?
WiredPirate said:
I have heard bad things about touch recovery. have you tried restoring your backups with regular CWM?
Click to expand...
Click to collapse
Yeah, I gave that a try and no luck... I think the tar used in both touch and non-touch have the same 2gig limit.
Would it be possible in adb to delete the /data then push the untared /data from my computer to the phone? The file untars fine on my desktop system.
And this is why I switched to TWRP recovery.
Compression allows the backup to be less than 2 gigs...and it works.
Personally, I'd skip all that...
Just wipe all data.
Install the rom you're trying to restore data for...
And use titanium to restore app data from the nandroid.
Jubakuba said:
And this is why I switched to TWRP recovery.
Compression allows the backup to be less than 2 gigs...and it works.
Personally, I'd skip all that...
Just wipe all data.
Install the rom you're trying to restore data for...
And use titanium to restore app data from the nandroid.
Click to expand...
Click to collapse
Yeah, I'm leaning that direction. I'm just really annoyed that they nandroids are sitting there but I'm being confounded by the tar functionality. I'll be switching to TWRP myself.
When you want to install or send some data to your new rom, you can use "nandroid browser" from the store
https://play.google.com/store/apps/...dvZGRjaGVuLmFuZHJvaWQubmFuZHJvaWRicm93c2VyIl0.
Jubakuba said:
And this is why I switched to TWRP recovery.
Compression allows the backup to be less than 2 gigs...and it works.
Personally, I'd skip all that...
Just wipe all data.
Install the rom you're trying to restore data for...
And use titanium to restore app data from the nandroid.
Click to expand...
Click to collapse
With TWRP can you restore backups that were made in CWMR?
I'm almost thinking this is not something to blame on CWM. If CWM makes a call to tar (in busybox) then it's the busybox version of tar that has the issue.
I was able to get my CWM /data backup back on my phone. I made two copies of /data. I opened them up in 7zip and split them in to two archives (deleting the first half of one and second half of the other). I then restored by doing:
tar xvf data.ext4-1.tar -C /
tar xvf data.ext4-2.tar -C /
(I had tried this earlier but I think I corrupted my tar archive which is why it was giving me the error).
Using the busybox (from CM9) and trying the same thing on the full 2.6GB tar archive I'd get an error stating "Value too large for defined data type". From what I've read this may be a result of how tar (in busybox) was compiled.
The funny thing is I'm getting the exact same problem in TWRP if I don't use the compression option and the /data backup is greater than 2GB! Using compression I'm at 1.6GB and everything is fine.
Related
Do we have nandroid with full backup/restore of all partitions working yet?
If so, some instructions would be greatly appreciated
we wont have nandroid until we have a custom recovery image and possibly full /system access
So... are we seeing any progress in the nandroid department yet?
I distinctly remember seeing a twitpic (from Paul?) of a Desire running custom recovery image so that shouldn't be a problem.
What's holding it back?
You can make nandroid backups from the recovery....
abats said:
You can make nandroid backups from the recovery....
Click to expand...
Click to collapse
That's precisely what I thought.
Golgo said:
So... are we seeing any progress in the nandroid department yet?
I distinctly remember seeing a twitpic (from Paul?) of a Desire running custom recovery image so that shouldn't be a problem.
What's holding it back?
Click to expand...
Click to collapse
I'm sure he said it wasn't a recovery image, but just an app/script. In any case, if we run the recovery script we have the NAND backup/restore options amongst the others (wipe/partition/etc).
alex101uk said:
we wont have nandroid until we have a custom recovery image and possibly full /system access
Click to expand...
Click to collapse
Can you elaborate on this please? You can write /system (and probably any other partition) from within the recovery.
Run the step2.sh from Paul's given files, and you'll see a quick adb shell and mount /system gives full rw to /system.
Really? And it's fully working?
I've been reluctant to try other roms until I knew nandroid was a go.
So just to be crystal clear - I can take a nandroid backup of EVERYTHING, the full stock-rom incl. every partition and restore it later just as easily?
Golgo said:
nandroid backup of EVERYTHING, the full stock-rom
Click to expand...
Click to collapse
Nope (unless you invent/modify the method yourself using the RUU and recovery shell - not 100% sure it's possible). You can only nandroid what's on there past Pauls rootedupdate.zip if you use his instructions.
jayshah said:
Nope (unless you invent/modify the method yourself using the RUU and recovery shell - not 100% sure it's possible). You can only nandroid what's on there past Pauls rootedupdate.zip if you use his instructions.
Click to expand...
Click to collapse
Ok, so you cant make a full backup of /system, /data etc?
Too bad. nandroid is damn handy when you'r messing around with custom roms!
Nandroid make full back as usual. I used it many times without any issues when playing with different desire roms.
Golgo said:
Ok, so you cant make a full backup of /system, /data etc?
Too bad. nandroid is damn handy when you'r messing around with custom roms!
Click to expand...
Click to collapse
Of course you can. I said you can nandoid past Pauls update, and not the stock ROM as you said.
jayshah said:
Of course you can. I said you can nandoid past Pauls update, and not the stock ROM as you said.
Click to expand...
Click to collapse
Ah, alright. Shame
Im new to this so let me get this right, I currently have a rooted stock ROM by Paul using the original linux rooting method. Can I use nandroid to back up this up and then flash a cooked ROM and if I do not like it then I can use the back up to reflash back to where I was?
Nekromantik said:
Im new to this so let me get this right, I currently have a rooted stock ROM by Paul using the original linux rooting method. Can I use nandroid to back up this up and then flash a cooked ROM and if I do not like it then I can use the back up to reflash back to where I was?
Click to expand...
Click to collapse
Yes. If you nandroid restore, it will be as if absolutely nothing has changed (excluding any SD card data changes).
jayshah said:
Yes. If you nandroid restore, it will be as if absolutely nothing has changed (excluding any SD card data changes).
Click to expand...
Click to collapse
thanks
I still need to push the recovery files in order to get into the recovery menu in order to flash etc. Will that mean I cant nandroid my current ROM?
That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
I don't THINK you can, but I skipped it entirely, so it might be worth trying. Worst thing that happens is it fails, right? Can you get into recovery without rooting?
The Professor said:
That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
I don't THINK you can, but I skipped it entirely, so it might be worth trying. Worst thing that happens is it fails, right? Can you get into recovery without rooting?
Click to expand...
Click to collapse
I cant get into the custom recovery menu without pushing the recovery files so I think we need a custom ROM to be able to get into the recovery menu directly from the phone.
The Professor said:
That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
Click to expand...
Click to collapse
Yes, this is exactly what I did. I have a recovery.sh file which is just step2.sh without the push of rootedupdate.zip each time.
Code:
# pwd
/sbin
# ./nandroid-mobile.sh -b
cp: './nandroid-mobile.sh' and '/sbin/nandroid-mobile.sh' are the same file
nandroid-mobile v2.2.1
Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept default:
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
Dumping boot to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/boot.img...done
Dumping recovery to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/recovery.img...done
Dumping misc to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/misc.img...done
Dumping system to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/system.img...done
Dumping data to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/data.img...done
Dumping cache to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/cache.img...done
generating md5sum file...done
unmounting system, data and sdcard
Backup successful.
#
Edit: Running a nandroid using the GUI method worked too, the 2nd time. 1st time failed, hence I did it manually above.
-edit- hm, got this
Code:
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
mtd: MEMGETBADBLOCK returned 1 at 0x00240000 (errno=0)
Dumping boot to /sdcard/nandroid/HT03WPL08829/BCDMRS-20100511-1419/boot.img...mt
d: MEMGETBADBLOCK returned 1 at 0x00240000 (errno=0)
done
.
.
.
.
Backup successful.
#
what does this mean?
So heres the situation. I made a backup of my phone using rom manager because I wanted to try out the new cyanogen. I got done playing with it and I went to revert back to my restore I had just created. During the restore I got an md5 mismatch error.
I used the instructions here to repair the restore
http://www.droidforums.net/forum/droid-hacks/40428-checking-md5-sum.html#post430944
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
The procedure worked in the sense that I was able to restore the image. The problem is after the restore I am stuck at the white "HTC Incredible" screen. I tried wiping caches and running the restore again but I am unable to get the phone to reboot.
I was able to restore to a much older restore that I had previously created but it lacks alot of updates and changes that I have made since then. Not to mention my Angry Birds saved game.
Looking at the restore files it looks like the folder for the restore contains a hand full IMG files. What i'm wondering is since it appears that the boot process is damaged I'm wondering if I could make a backup of the phone as it is now then take lets say the data.img file (or whatever file i need to recover installed apps and saved games) and overwrite the img files for the restore i just created. I could then use the same procedure I just performed to recreate the md5 hash and run the restore. My home is that will allow me to get my data back and still allow the phone to boot.
What do you guys think? Is it doable or am I going to be in a world of hurt if I start messing with this?
Something else you might try is to restore the latest backup, then do an advanced restore of just the boot partition from your older backup. It's worth a shot I'd think.
Did you put spaces or special characters when you named your backup? This can cause MD5 mismatch errors.
s197 said:
Did you put spaces or special characters when you named your backup? This can cause MD5 mismatch errors.
Click to expand...
Click to collapse
NO, I didn't. I used the default setting. I think it was 2010-12-29.01.34.10 or something like that.
setexascustoms said:
Something else you might try is to restore the latest backup, then do an advanced restore of just the boot partition from your older backup. It's worth a shot I'd think.
Click to expand...
Click to collapse
Thanks man, This worked perfectly. Restoring the boot.img didn't fix the problem but restoring the system.img did. I have all my data back and my phone is fully functional again. Thanks again.
At this point there's no way to have full recovery backups through CWM. adb allows us to do almost the same.
Here's how:
Code:
$ adb shell
$ su
# stop
# busybox tar cf /mnt/external_sd/data.ext4.tar --exclude media --exclude dalvik-cache /data
# reboot
To restore:
Code:
$ adb shell
$ su
# stop
# busybox tar xf /mnt/external_sd/data.ext4.tar -C /
# reboot
This will not backup the internal sdcard "/data/media" it's likely too large, so it should be backed up manually.
tar is the same format CWM uses, so it should restore from Titanium Backup.
thanks for this! Every little bit helps.
eww245 said:
At this point there's no way to have full recovery backups through CWM. adb allows us to do almost the same.
Here's how:
Code:
$ adb shell
$ su
# stop
# busybox tar cf /mnt/external_sd/data.ext4.tar --exclude media --exclude dalvik-cache /data
# reboot
To restore:
Code:
$ adb shell
$ su
# stop
# busybox tar xf /mnt/external_sd/data.ext4.tar -C /
# reboot
This will not backup the internal sdcard "/data/media" it's likely too large, so it should be backed up manually.
tar is the same format CWM uses, so it should restore from Titanium Backup.
Click to expand...
Click to collapse
I've not tried this yet, but am wondering what and where the output file would be located. Would you be able to use this as a recovery method from one ROM to the saved ROM similarly to what is done with CWM?
tomlogan1 said:
I've not tried this yet, but am wondering what and where the output file would be located. Would you be able to use this as a recovery method from one ROM to the saved ROM similarly to what is done with CWM?
Click to expand...
Click to collapse
For the instructions posted an external sdcard is needed it would be in the root of the card. You can substitute external_sd with sdcard to save in to the internal memory.
And yes this can work just as CWM when switching ROMs. For example before upgrading to ICS. Then, if possible, flash back to Honeycomb and restore the backup.
eww245 said:
For the instructions posted an external sdcard is needed it would be in the root of the card. You can substitute external_sd with sdcard to save in to the internal memory.
And yes this can work just as CWM when switching ROMs. For example before upgrading to ICS. Then, if possible, flash back to Honeycomb and restore the backup.
Click to expand...
Click to collapse
Just to make sure I have done this, correctly, I have a file on my external sd called data.ext4. Should I wish to try another ROM, I would load the new ROM via the normal recovery method, and then if I wanted to restore from the data.ext4 file, I would use ADB to restore this file. Would this overwrite the existing ROM so I could , for instance, use ICS and then move back to HC? Looking at the data.ext4 file, it appears that all the applications have been backed up as well. Am I correct? Thanks.
tomlogan1 said:
Just to make sure I have done this, correctly, I have a file on my external sd called data.ext4. Should I wish to try another ROM, I would load the new ROM via the normal recovery method, and then if I wanted to restore from the data.ext4 file, I would use Titanium backup to restore this file and then use Titanium to also restore applications and data that I has backed up previously. Am I correct? Thanks.
Click to expand...
Click to collapse
Currently no one has made any roms, I guess because of no CWM which isn't needed, Theres only stock HC and stock ICS. Unfortunately ICS CAN'T be downgraded back to HC, previously I saw no mention of it being possible or not. Titanium backup is capable of restoring apps and data from a nandroid / tar. Which I don't own so I can't test it. Lets say you start getting a bunch of Force Closing apps and you have already made a tar backup. Then just fire up adb and restore it. Or you want to factory reset and start fresh, then install individual apps/data through Titanium from the tar, if even possible.
AppExtractor can also restore app data from a nandroid. Well, it doesn't work with my adb backup on the a100 but if I copy it to my phone AppExtractor has no problem reading the archive. I don't know about Titanium.
[edit]Just want to add to this post because it is actually possible to downgrage to HC. crossix has instructions here forum.xda-developers.com/showpost.php?p=22970185&postcount=147.
Also peporras opened a thread about it forum.xda-developers.com/showthread.php?t=1517286
eww245 said:
Currently no one has made any roms, I guess because of no CWM which isn't needed, Theres only stock HC and stock ICS. Unfortunately ICS CAN'T be downgraded back to HC, previously I saw no mention of it being possible or not. Titanium backup is capable of restoring apps and data from a nandroid / tar. Which I don't own so I can't test it. Lets say you start getting a bunch of Force Closing apps and you have already made a tar backup. Then just fire up adb and restore it. Or you want to factory reset and start fresh, then install individual apps/data through Titanium from the tar, if even possible.
AppExtractor can also restore app data from a nandroid. Well, it doesn't work with my adb backup on the a100 but if I copy it to my phone AppExtractor has no problem reading the archive. I don't know about Titanium.
Click to expand...
Click to collapse
I know there are no custom ROMS. If I wanted to try ICS, there there is no way to flash one of the stock ROMS back? Just wanted to be sure before I do something I would regret.
Thanks.
I am new here so sorry for this newbie question, I have tried the method in post 1 but I get the message tar: empty archive have I missed something? any help will be greatly appreciated. Many thanks in advance.
I have re-typed the commands and all seems ok.
Your not specifying any files to be tarred. The command should end with /data
eww245 said:
Your not specifying any files to be tarred. The command should end with /data
Click to expand...
Click to collapse
many thanks
eww245 said:
At this point there's no way to have full recovery backups through CWM. adb allows us to do almost the same.
Here's how:
Code:
$ adb shell
$ su
# stop
# busybox tar cf /mnt/external_sd/data.ext4.tar --exclude media --exclude dalvik-cache /data
# reboot
To restore:
Code:
$ adb shell
$ su
# stop
# busybox tar xf /mnt/external_sd/data.ext4.tar -C /
# reboot
This will not backup the internal sdcard "/data/media" it's likely too large, so it should be backed up manually.
tar is the same format CWM uses, so it should restore from Titanium Backup.
Click to expand...
Click to collapse
If you changed "data.ext4.tar" to "nameilike.ext4.tar" you would then be able to have a catalog of different setups you made, assuming some other ROMS in the future. The reason for this is the previous generation of CWM on the A500 used the date for the file name and if you had 5 or 6 you didn't know which was which.
Ever since i installed Android 4.2, this whole emulated storage thing is a mess. I have some backups, and i am trying to restore from them in CWM touch. When i go to restore, it always says "cant open directory/cant find files" or something of the sort. I have verfieid that the files are in the 0 storage.
Its frustrating. Does anyone know of a way to restore from a cwm backup ? It would be much appreciated ! I have the latest CWM touch by the way.
Thanks !
Did you update your cwm recovery to one that supports the new 4.2 sdcard layout?
Sent from my Galaxy Nexus using Tapatalk 2
Search is your friend
saadkhan07 said:
Ever since i installed Android 4.2, this whole emulated storage thing is a mess. I have some backups, and i am trying to restore from them in CWM touch. When i go to restore, it always says "cant open directory/cant find files" or something of the sort. I have verfieid that the files are in the 0 storage.
Its frustrating. Does anyone know of a way to restore from a cwm backup ? It would be much appreciated ! I have the latest CWM touch by the way.
Thanks !
Click to expand...
Click to collapse
This is a problem with flashing 4.2. TWRP has a fix for the issue you are talking about, but right now the fix for you can be found in this post, or others like it. This is how I fixed my problem!
http://forum.xda-developers.com/showthread.php?t=1762846&page=256
ual4720 said:
I flashed this build and later tried to go back and do a restore on my CWM backup. When I attempted the restore it couldn't find any backups! I found the problem to be that it moves the sdcard contents to /data/media/0 then mounts /sdcard/ to /data/media/0. Clockwork mounts the folder /data/media and is searching for the backups in that directory. It fails to find it because it is not there. To fix this I made a backup of my sdcard by doing an adb pull then moved the clockwork folder in the /data/media/0 to /data/media/. so the commands that I executed are as follows:
adb shell <enter>
su <enter>
cp /data/media/0/clockworkmod /data/media/clockworkmod <enter> (you could also replace the cp command with mv. This will keep from creating a duplicate of your backups - suggested by tiny4579)
reboot recovery <enter>
go through the process of restoring a clockworkmod recovery and when it is finished reboot into your restored backup. If you explore the sdcard with root explorer or adb you will notice the 0 folder inside your sdcard.
I suggest you dont try this if you are unfamiliar with the command line. Has anyone else experienced this issue and have a better fix?
Click to expand...
Click to collapse
ual4720 said:
This is a problem with flashing 4.2. TWRP has a fix for the issue you are talking about, but right now the fix for you can be found in this post, or others like it. This is how I fixed my problem!
http://forum.xda-developers.com/showthread.php?t=1762846&page=256
Click to expand...
Click to collapse
BUT if TWRP is installed....can i restore from a CWM backup ???
saadkhan07 said:
BUT if TWRP is installed....can i restore from a CWM backup ???
Click to expand...
Click to collapse
No
Sent from my Galaxy Nexus using Tapatalk 2
If there is way to point CWM to the proper directory, is there a way ? Can i restore via ADB ?
I have all the CWM files to restore from, just cant due to the location of the files i guess. Does CWM default to the 0 ?
re
saadkhan07 said:
If there is way to point CWM to the proper directory, is there a way ? Can i restore via ADB ?
I have all the CWM files to restore from, just cant due to the location of the files i guess. Does CWM default to the 0 ?
Click to expand...
Click to collapse
I actually ended up resetting the whole device, and actually was able to restore by using the MD5 mismatch fix. I have reinstalled CWM and everything.
i am currently running cm10.0.0 and completely satisfied with it. just for curiosity reasons i would love to flash 4.2 to see how it feels. my problem now is, can i simply return to cm (4.1) by reflashing my cwm backup?
as with 4.2 the file-system was changed (sdcard0), is that pretty easy with cwm recovery, or do i have to invest an hour of work with adb pulls and pushes?
thanks for your experiences!
saadkhan07 said:
I actually ended up resetting the whole device, and actually was able to restore by using the MD5 mismatch fix. I have reinstalled CWM and everything.
Click to expand...
Click to collapse
Same with me... :/ it was annoying... Just because of that new sdcard layout on 4.2
Hi-
If i want to not only wipe system, data, cache but the /data/media partition as well before installing a new ROM, what's the least onerous method for restoring all my data after flashing the new ROM? currently all i know to do is backup my data, wipe everything, then restore factory image via adb, then copy zips to the device, flash desired ROM, then copy back data via adb or from dropbox after installing app
Is there an easier way?
titanium backup is the easiest way.
just dont restore system apps.
1. Run a backup in titanium backup
2. Copy the contents of your /data/media partition to your PC via adb or MTP (this should include your TiBu backup)
3. Wipe System, Data, Userdata, and the caches via method of your choice
4. Copy the contents of your /data/media backup back to /data/media via adb
5. Use adb to push a ROM of your choosing to /data/media (assuming you didn't have one in your /data/media backup, and assuming you're not using fastboot to flash a stock image)
6. Flash away (Recovery, if needed, and System via either fastboot or CWM/TWRP)
7. Download TiBu from the Play Store
8. Restore non-system apps/data in TiBu
However, if you're going to make a backup of /data/media and then restore it immediately after wiping it, I have to ask why? It's a time consuming process (transferring gigs via adb is very slow) and would provide no benefit to your device.
Also, if you're going from Android 4.1.x to 4.2.x, make sure your /data/media backup goes back in /data/media/0, or the OS will not see the files as being on your "external" storage.
Zepius said:
titanium backup is the easiest way.
just dont restore system apps.
Click to expand...
Click to collapse
Oh im definitely using titaniumbackup to restore apps, but i was mostly referring to restoring the contents of the sdcard
Thanks!
jackbane said:
Oh im definitely using titaniumbackup to restore apps, but i was mostly referring to restoring the contents of the sdcard
Thanks!
Click to expand...
Click to collapse
Using twrp I wipe cache, davlik, factory reset, and system and my sdcard is untouched. I was told by a dev to also delete the android folder in my sdcard using the twrp file manager.
No need to flash stock image when wiping everything just fast boot flash the rom you want and adb is the best way to restore your sdcard
Cilraaz said:
However, if you're going to make a backup of /data/media and then restore it immediately after wiping it, I have to ask why? It's a time consuming process (transferring gigs via adb is very slow) and would provide no benefit to your device.
Click to expand...
Click to collapse
I know, I know...I have this idea of after flashing many different ROMs and finding my keeper, that I would totally wipe the device and then install a super clean ROM, and start with a virgin /data/media partition, bringing back only what I want. I recognize that this is probably unnecessary and says more about my desire for neatnes than anything else.
But thanks for the detailed instructions. Until now, I have been using the GNex Toolkit downloaded from the sticky in the dev forum to handle all pushes and pulls and adb duties. I thought that to push a file to the device, it had to be in Android mode. This is why I found myself having to flash the stock rom just to copy back the contents of /data/media. It sounds like, from the posts in this thread, that I don't need to, that I should be able to copy the files from fastboot mode? Or do I temporarilty boot into an image to push files, then flash the ROM from TWRP. (I'm using TWRP 2.4.1.0, btw).
If I could avoid installing the factory ROM, just to copy back /data/media/, that's what I'm looking for. Do you know if this is possible using the GNex toolkit?
Thanks again!
you have full ADB access within any custom recovery. toolkits not required.
Zepius said:
titanium backup is the easiest way.
just dont restore system apps.
Click to expand...
Click to collapse
I always wondered about this. Does the stock browser qualify as a system app? Should i not use titanium to restore any of the gapps?
jackbane said:
I always wondered about this. Does the stock browser qualify as a system app? Should i not use titanium to restore any of the gapps?
Click to expand...
Click to collapse
The best option for titanium, is to select BATCH, RESTORE MISSING APPS+DATA
Go down the list and deselect anything you DONT want restored. everything else should be OK on that screen.
Also, make sure you have the pro license, otherwise batch jobs are a PITA
There is also an option in the MENU button - BACKUP TO XML
This option allows you to backup call logs, wifi networks, mms/sms, bookmarks separately from the other backups and works 100% going rom to rom.
Everybody is recommending TiBU, and I concur, but OP is talking about all the other contents of the sdcard..
I actually just did this today. I had been on cm10.1 but went back to cm10 for a while, getting the extra /0/ folder and all. I was going to just copy EVERYTHING over to my comp, but ended up just copying a few music folders and a few backup folders. After flashing cm10.1 and gapps, I formatted the sdcard. Now I'm transferring those few folders back. I had a FULL sdcard before, so it feels good to have some space, that is until I think of something I wanted that I didn't copy lol..