I have the rw SDE-based root on my A43.
I tried backing up with Titanium Backup Root, but the restore didn't work after an android reset--I got a non-working system as a result, and had to reset again and manually reinstall apps.
I think that instead of trusting a backup app, I'd like to just tar the data, and then if I have a problem, I can reset android and untar. Is it enough if I just tar cvp /data, or is there stuff to backup outside /data, too? (I haven't modified any prop files, but I guess if I do, I'll need to add them.)
(I already cross-compiled tar, and it works fine.)
arpruss said:
I have the rw SDE-based root on my A43.
I tried backing up with Titanium Backup Root, but the restore didn't work after an android reset--I got a non-working system as a result, and had to reset again and manually reinstall apps.
I think that instead of trusting a backup app, I'd like to just tar the data, and then if I have a problem, I can reset android and untar. Is it enough if I just tar cvp /data, or is there stuff to backup outside /data, too? (I haven't modified any prop files, but I guess if I do, I'll need to add them.)
(I already cross-compiled tar, and it works fine.)
Click to expand...
Click to collapse
Hit the Problems button in titanium backup. The stock busybox is flawed and titanium will install a good one.
Thanks for the suggestion. But I also don't like the idea of trusting my backups to a closed source app. I much prefer to have full control over what's backed up, in what format, etc.
arpruss said:
Thanks for the suggestion. But I also don't like the idea of trusting my backups to a closed source app. I much prefer to have full control over what's backed up, in what format, etc.
Click to expand...
Click to collapse
The backup format used by titanium is tar.gz
I suggest you do a full backup with titanium and then see what is backed up. From there you can decide what to tar up. tar exist on the system with busybox you don't need to build it. The problem with the tar of the busybox is the compression does not seems to work correctly. When you hit the problems button in titanium it downloads a copy of busybox that works correctly if you copy that you can use to to scipt your own backups.
I'v been using titanium for a long time and even if it's closed source it does it job perfectly.
wdl1908 said:
The backup format used by titanium is tar.gz
I suggest you do a full backup with titanium and then see what is backed up. From there you can decide what to tar up. tar exist on the system with busybox you don't need to build it. The problem with the tar of the busybox is the compression does not seems to work correctly. When you hit the problems button in titanium it downloads a copy of busybox that works correctly if you copy that you can use to to scipt your own backups.
I'v been using titanium for a long time and even if it's closed source it does it job perfectly.
Click to expand...
Click to collapse
There is no tar in the busybox on my A43 as far as I can tell.
I am using MyBackUp Pro
So, I've been experimenting some more. I tar all of /data, reset android, and restore. That works sometimes, but not always. The problem is that tar is pushing data to the mmcblk0p4 device too fast, and it's timing out with "error -110 transferring data", which is apparently timeout.
Looks like the Maemo community has noticed this and has a fix by patching the mmc driver.
In principle, this could happen with a backup utility, but those may work too slowly for the problem to come up.
I've done more experimenting. The restore seems to work fine if I run the backup file through a throttle utility that feeds it to tar at 200Kbytes/sec, and then reboot after restoring. (It takes a minute or two for the icons for the apps moved to internal storage to reappear.)
I am tarring up everything in /data except for /data/cache and /data/dalvik-cache .
Related
I wanna start by saying that I have been searching and I can't find a similar post...forgive me if I was simply unsuccessful :/
So here's what happened.
Me - "Hey! I've got a rooted phone, but no custom ROM? I think I'll download one!"
I performed a Nandroid backup.
Flashed Macnut 14.
"Awesome, it works. Now I'm gonna restore my data."
I tried doing an advanced Nandroid restore, but it hung at "dalvik-cache".
I then tried doing a full Nandroid retore, but it still hung at "dalvik-cahe".
I then flashed Stock JK6 and repeated steps 5 and 6 with the same results.
I then downloaded and compiled unyaffs in order to get files out of the Nandroid .img files.
I tried "adb install" for apps and "adb push" for both data and apps. I've been getting error messages for both approaches (not syntax errors, but things like "permission denied," "not enough space," etc.), both while the phone is booted and when it's in recovery.
I've also tried moving the files to my SD card and then using "adb shell" to move them to their appropriate folders, but that didn't work either.
Besides these errors, I also had a very hard time figuring out where to put certain things.
So that's what happened...you guys are my final hope. I'm trying to figure out a foolproof way to restore (in order of priority):
Application data (settings, high scores in games, etc.).
Applications themselves (.apk files, preferably not overwriting newer versions of things like GMail, Youtube, etc. included in Stock JK6).
Text messages.
Phone settings.
I've learned my lesson...next time, I should use Titanium Backup.
Thanks,
Gerard
Personally I would:
1. ODIN to JK6
2. Root and use the modified 3e recovery
3. Install ROM Manager from the market and flash CWM Recovery
4. Then attempt to Nandroid restore
If you're not comfortable with the above Step 2 you can:
1. ODIN to JFD and root
2. Install ROM Manager from the market and flash CWM Recovery
3. CWM Flash JK6
4. Attempt to Nandroid restore
You went from eclair to froyo and when you restored your backup, CWR does not restore the kernel.
Try flashing the stock 2.1 kernel and then restoring your backup.
And yes, titanium backup & SMS Backup+ are your friends.
hmm... re-read... it's odd that a restore started and didnt finish. Most people get hung at the vibrant screen when they do not restore the kernel.
Sounds like you nandroid is corrupt, and if that is the case I'm afraid that I do not know the answer you seek.
Yeah, I don't think that a Nandroid backup is gonna do the job...I just tried again after ODIN.
Any other ideas?
EDIT: I was finally able to push all my applications back...However, I'm having trouble pushing the contents of "data/data/" and "datadata/". I keep getting errors like:
failed to copy 'data/com.android.browser/app_appcache/ApplicationCache.db' to 'datadata/com.android.browser/app_appcache/ApplicationCache.db': No such file or directory
Click to expand...
Click to collapse
How can I evade this error? :/
You have to flash a kernel as well cause nandroid won't replace that
Sent from my GT-I9000 using XDA App
Are you trying to adb from linux or windows? If you are on linux try this:
1) sudo adb kill-server
2) sudo adb devices
3) now push your apps
Also I found out the hard way, do not restore apps or system data from nandroid backup, I always had a corrupted system with a lot of force closes. Always use Titanium Backup and SMS Backup.
Hope this helps
brnbock said:
Are you trying to adb from linux or windows? If you are on linux try this:
1) sudo adb kill-server
2) sudo adb devices
3) now push your apps
Also I found out the hard way, do not restore apps or system data from nandroid backup, I always had a corrupted system with a lot of force closes. Always use Titanium Backup and SMS Backup.
Hope this helps
Click to expand...
Click to collapse
I'm actually on a Mac. I tried your method but I still got the same results...is Mac close enough to Linux (since it's Unix), or do you think I should attempt it on Linux as well?
DEFINITIONOFREAL said:
You have to flash a kernel as well cause nandroid won't replace that
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I don't mean to sound like a douche...but isn't that what s15274n was saying?
ya try it on linux, Mac is BSD based but I'm not sure how permissions are set. BSD is close to linux but there are some major diff and some commands are diff.
So far, for me Nandroid on the Vibrant has been completely useless. I don't even bother any more.
I use Titanium to back up my apps and my SMS messages, and it only takes a couple minutes to re-do the settings once I install a new ROM.
This is way different than my experience with the G1, where I could easily restore a Nandroid backup if I didn't like a new ROM install. On the Vibrant it's easier to just Odin back to a stock ROM and redo all my settings using TB.
brnbock said:
ya try it on linux, Mac is BSD based but I'm not sure how permissions are set. BSD is close to linux but there are some major diff and some commands are diff.
Click to expand...
Click to collapse
Yeah...tried this too after downloading and setting up everything on my Linux box (java, Android SDK, etc.). Same error as I got on my Mac
I think I'll take like one more suggestion from the community before I finally give up and start my phone from scratch...It's been like 3 days since I lost all my data, ugh.
I'm curious about this. Maybe someone can enlighten me.
Lets say that I'm on stock 2.2, rooted. I do a nandroid backup. Then I allow the upgrade for 2.2.2. Of course I lose root.
Will a nandroid restore, restore root, or will I have to root again?
A full nandroid restore will restore everything - the system and data - and you will be right back where you were, on 2.2 and rooted.
maltloaf said:
A full nandroid restore will restore everything - the system and data - and you will be right back where you were, on 2.2 and rooted.
Click to expand...
Click to collapse
Ahh, okay.
So to confirm that I understand you correctly...
...the 2.2.2 update won't hold after the nandroid restore? I'll be back to 2.2, as it was before the (2.2.2) update?
If you just wanna backup and restore your apps, use Titanium Backup (it's free on the Market).
Nandroid backs up your entire phone. When you restore a nandroid backup your phone will be exactly like it was when you made the backup. Restoring a nandroid backup is used to recover from a crash or to revert to a previous ROM.
After a ROM change I will set up my accounts, root if needed and do any other basic setup stuff and then, before installing any apps, do a nandroid backup. I can then go back to a "fresh install" if I want to. I also do a nandroid each weekly to capture the state of my phone.
Backing up apps and restoring them across different ROMs may or may not work for you. When I have tried this with Titanium Backup I had many force closes and ended up reinstalling everything from the market. Others have had success. I have read the MyBackup pro does better, but most suggest that you just backup and restore data not the app itself.
I have not tried backing up my apps to Google, which you can do in later versions of Android. Go to Privacy in the setting menu and then to Backup and restore. There are boxes for data backup and automatic restore you can check. maybe someone who has used this can comment on how well it works.
If your nandroid backups hang up at "backing up firstboot" get the latest version of StreakMod Recovery.
marvin02 said:
Backing up apps and restoring them across different ROMs may or may not work for you. When I have tried this with Titanium Backup I had many force closes and ended up reinstalling everything from the market. Others have had success. I have read the MyBackup pro does better, but most suggest that you just backup and restore data not the app itself.
Click to expand...
Click to collapse
After installing a fresh ROM and rooting my device, the first thing I do is install Busybox. Then, with Titanium Backup I do Restore Apps Only, then reboot my device. I never get any FC's with this restore process.
Thanks!
Thank you everyone. I appreciate the info.
I've used Titanium BU, and have busybox installed too.
It was just a matter of if after an update (OTA), and restore with Nandroid, would root still be in place.
I totally understand what you guys are saying now.
I've also been using MyBackup to see how it compares to Titanium. So far so good.
~X
I prefer mybackup root to titanium. It's far more user friendly and more automated (in the free version). As for nandroids, I always take a backup before doing any system changes (hacks or rom updates) so I can roll back to a known good system if needs be.
BTW - it is a good idea to copy your ROM backups to another device, just in case your SD card dies. I copy mine to one of my desktop computers and to a USB drive. I usually back up my entire SD card, except my music folders, every couple of weeks.
Where does Nandroid put the backups so I can rename them and save off phone?
mine (from Streakmod recovery) are in /sdcard/rom_backup
StreakMod recovery puts the backups on the SD Card in a folder named rom_backup.
Each backup is in a sub-folder of it's own and uses a date-time format for the folder name. I rename the folders with a meaningful name by just pre-pending to the name. So my last backup is named BB351-2011-06-18-02.41.04. The following files are created:
.android_secure.img
boot.img
cache.img
data.img
firstboot.img
recovery.img
system.img
nandroid.md5
the md5 file is a text file that contains the md5 sums for the other files. This file is used to verify the other files when they are restored.
Hi guys!
I just backed up my system because I wanted to load another system/ROM. So I wanted to restore the system is just backed up, but when I restore the ROM/system is different. For example the design is changed, and the home button does not work, I have to press back to exit apps. All my contacts and messages are gone. But my applications is there.
So I looked at the size of the backup files, and it this is how big the files are:
cache.img - Size: 0
data.img - Size: 252772352
nandroid.md5 - Size: 0
system.img - Size: 129997824
So it looks like the cache file and nandroid file is damage/broken. But it will take loong time to fix all this up to how it was.....
Is there something I can do? What can I restore? system, cache, data or what to get my design and contacts back and those things.
I hope you guys understand me.
Thanks for all answers.
Wait... are you saying that you actually back up /system and then restore it when you get a new rom? No no no no no...
/system is where your rom is actually stored, replacing it with the /system of another rom would have all kind of bad consequences.
What you need is to get Titanium Backup and MyBackup Root from the market; Titanium Backup for apps and app data, and MyBackup Root for contacts, sms', etc.
Messing with /system is not advised unless you know exactly what your doing.
Sent from my X10i using XDA Premium App
..JusT Try 2 Help..
Uuupz..missing here..
Hope you mean Xrecovery BackUp..
1. Yuuup..the BackUp Files is BiiiiiG..coz it BackUp All of Your Phone (inc. ROM, KerneL, Apk, SmS & Phonebook)..coz the BackUp mean "Duplicate Your Phone"..soo when it Restored (Full Restore).."Your Now Phone" JusT Back to "Your Phone" when the last you Back It Up..
2. Never Go to "Advance Restore" To "IndividuaL Restore" anything when you have "Change" your RoM/KerneL..coz it can brick your phone. Just Do It when you still in the same RoM/KerneL..it safer..
3. If It Already Happen but you still can access XRec. then just make a Fresh Flash RoM..
4. If It Already Happen and you can't access XRec. just Flash It through Flash TooL..
I backed up everything with xRecovery. And when I'm now restoring I get the problems as I wrote in the first post.
The problem is that the files looks corrupted or something, because I have the problems above.
Something to try:
Do a fresh install of the rom you backed up(don't restore the backup again, just flash the rom zip from the thread). Then in xrec choose advanced restore> restore data using the 'damaged' backup. Since data.img seems to be intact and it's the same rom, hopefully that will restore apps & contacts, etc.
It is always good practice to back up apps & contacts w/apps like Titanium Backup and MyBackup Root before flashing like Frosty said just in case something like this happens.
Uupz..corrupt backup files..try to Re-Install xRec...
Or
Just do a Fresh Flash through FlasH TooL..and StarT from Begin again..
Hello, while I was using my phone it rebooted and aparrently someting from my /data got corupted disabling my Rom from booting ever again.
So I created a nandroid via CWM6, installed a new rom and I'm now scratching my head on how to extract certain apps from that backup. Using CWM5 I could do this via the use of Titanium Backup, but now it's more complex than that CWM6 nandroids are unreadable from anything that exists out there. The only app which could analyze the backup correctly was the latest beta of "app extractor" but even that could not extract the apks *with* their data.
Basically my apps' data is precious and I wish to restore it at all costs, I have a nandroid of them, but the format is so unspeakably complex that it is basically useless. So the other "solution" was restore the nandroid and pull the whole /data partition in my PC via ADB, but I'm not sure what I can do with it.
So as it stands I now have two copies of my apps, one in a nandroid format another as it was pulled from the phone but I'm not sure how I can go on and restore them in a new rom. As I have found out CWM6 was quite a downgrade for/to those who backup/recover frequently, it's sad that I have found about it in such a disastrous way
How to recover data from "adb backup --twrp" archive? Been through hell and back
I have two backups I made using "adb backup --twrp" while my OnePlus one phone was in TWRP recovery 3.2.1-0 running LineageOS with a recent build (don't know exactly which one, but it was from Feb/March 2018). Each of the backups are about 6.0GB so they appear to be complete backups. I am trying to recover one app and its data (Signal/Textsecure) but the rest would be nice too. The backup files have .ab extensions. I am fairly android savvy and have been working on this for days, your help is VERY MUCH APPRECIATED! I have access to Windows and Linux.
I have tried the following:
-"adb restore filename.ab" while in TWRP recovery. It appears to restore (progress bar goes, it reports success, etc), but no apps are restored. I have tried this both with totally wiped partitions/system/data and with a fresh install of LineageOS. As far as I can tell, nothing happens. When doing a restore after a full wipe and trying to restart, TWRP warns that no OS is installed.
-Restoring using the restore menu in TWRP. Immediately upon clicking on the backup, the phone restarts and TWRP opens again. Not sure what's going on there.
-Opening the backups in Titanium Backup, Nandroid manager, and a few other apps. None of them worked. Titanium backup crashes instantly in recover from ADB, doesn't recognize the backups in nandroid recovery mode.
-Opening the .ab files in an archive manager, all of which report it isn't a valid tar archive. One time I was able to get a list of directories, and things looked pretty right, so I know at least some of the data should be there. Running variants of this command with different skip values, none of which produces a valid tar file dd if=file.ab bs=512 skip=1 of=test.tar
Questions:
- Is there a way to extract data from these backups in Linux or Windows outside of Android? From what I read, TWRP adds some stuff in the headers which makes them invalid tar files, and that doing "adb backup --twrp" is different from a regular TWRP backup.
- Why is TWRP crashing? Is there a log I can look at for this and how? Maybe i can find a way to diagnose it that way.
- Where does Signal store message data? I have a flat-file backup that may have this information depending on where it's stored.
- Can I somehow convert these backups to a different format that might be better-tolerated by TWRP or other apps?
- Any good utilities for reading a corrupted tar file? I think all this utility would need to do is skip through the junk at the start.