I've noticed that whenever i restore a clockworkmod backup, it actually reverts my whole phone back to when i made the backup (even games) whereas amonra didnt revert my games. How do i stop this from happening (i know in cwm recovery it gives you the option to restore certain imgs. which one do i leave out?)
I haven't tried it, but games/apps should be in 'android_secure' and sd-ext.
Sent from my LG-P500 using XDA App
so out of these imgs:
.android_secure.img
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
i can just manually flash everything one at a time except .android_secure.img (which i leave out)? this will leave my android_secure as it is? and the most important question, is this safe?
sweetnsour said:
so out of these imgs:
.android_secure.img
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
i can just manually flash everything one at a time except .android_secure.img (which i leave out)? this will leave my android_secure as it is? and the most important question, is this safe?
Click to expand...
Click to collapse
Its safe. But you will have some dead icons on your home screen.
Sent from my LG-P500 using Tapatalk
will the dead icons mean that its a broken shortcut or broken application?
if its a broken application, can i just restore a titanium backup? or i can just flash android_secure.img to fix it right?
Related
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..
I know it's possible do restore apps and such using Titanium backup but I'm wondering if it's possible to restore using the TWRP backup?
I'm not sure what the different things do that TWRP backs up. System, cache, recovery, boot, data, (and something else). If it's possible to restore apps and such restoring from some of those, which ones?
Thanks
ItsTommyGun said:
I know it's possible do restore apps and such using Titanium backup but I'm wondering if it's possible to restore using the TWRP backup?
I'm not sure what the different things do that TWRP backs up. System, cache, recovery, boot, data, (and something else). If it's possible to restore apps and such restoring from some of those, which ones?
Thanks
Click to expand...
Click to collapse
Make sure you do a nand backup then after you flash a rom go to your nand backup and restore only the data,
This has worked for me
Sent from my EVO using xda premium
ItsTommyGun said:
I know it's possible do restore apps and such using Titanium backup but I'm wondering if it's possible to restore using the TWRP backup?
I'm not sure what the different things do that TWRP backs up. System, cache, recovery, boot, data, (and something else). If it's possible to restore apps and such restoring from some of those, which ones?
Thanks
Click to expand...
Click to collapse
josh030181 said:
Make sure you do a nand backup then after you flash a rom go to your nand backup and restore only the data,
This has worked for me
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yes, restoring only the data partition will restore both the application .apk files themselves as well as the application's data files (settings, etc). The issue is when restoring data from a different ROM, the uid/gid could mismatch and cause a boot loop. This is one of the main reasons people suggest to wipe the data before loading a new ROM. Sometimes this issue can be fixed using the script, fix_permissions, in the custom recovery.
I think using Titanium Backup might work around this permissions uid/gid issue and might be one of the reasons people chose this over a nandroid restore of just the data partition.
In regards to your other question of what the different partitions "do" which TWRP backs up, here is a rough list off the top of my head:
system (holds all the Android OS files and stock apps)
data (holds all settings and 3rd party apps)
cache (temp partition usually used to store downloaded OTAs before they are loaded)
recovery (stores the custom recovery)
boot (stores the kernel)
Hope that helps fill in some of the missing details!
joeykrim said:
In regards to your other question of what the different partitions "do" which TWRP backs up, here is a rough list off the top of my head:
system (holds all the Android OS files and stock apps)
data (holds all settings and 3rd party apps)
cache (temp partition usually used to store downloaded OTAs before they are loaded)
recovery (stores the custom recovery)
boot (stores the kernel)
Hope that helps fill in some of the missing details!
Click to expand...
Click to collapse
That does help. Thanks!
I'll root my S3 and then will install a custom ROM, do I need to backup my existing ROM or I can flash it back by downloading it via the forums?
you can either:
-back it up with cwm recovery(making a nandroid backup) so that when you restore it,it restores to the way it was when you made a backup
or
-just flash a custom rom without making a backup.(Note:you can restore it to stock using the stock roms flashable available but you would have to set it up again like you do when you factory reset.)
Lither said:
I'll root my S3 and then will install a custom ROM, do I need to backup my existing ROM or I can flash it back by downloading it via the forums?
Click to expand...
Click to collapse
Always make a full nandriod (use the toolkit) backup of your own ROM, a stock ROM won't restore your the efs folder and, if it gets corrupted during ROM installation can't be recovered.
backup your efs
in cwm, a nandroid backup is simply labelled as back up. it'll be in a zip file in the location of your choosing when it's done or in the cwm folder labelled by the date and time it is backed up.
Sent from my GT-I9300 using xda app-developers app
mputtr said:
in cwm, a nandroid backup is simply labelled as back up. it'll be in a zip file in the location of your choosing when it's done or in the cwm folder labelled by the date and time it is backed up.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your quick reply !
It should work like that and even more hoped it would work like that !
Instead of a .ZIP file, I get 3 directories under /sdcard0/ClockWorkMod : these are BACKUP, BLOB and DOWNLOAD.
On every backup, there is indeed a directory created in the directory BACKUP with the current date as name (like "2012-11-04.23.27.05").
The data in there can never be a full nandroid back, as it's only 18 MB (yes megabytes).
Here is a listing for example : (size filename)
> ..
8.388.608 boot.img
811 cache.ext4.dup
1.479.801 data.ext4.dup
237 nandroid.md5
8.388.608 recovery.img
289.833 system.ext4.dup
18.547.898 bytes
Notice the file extentions .DUP and their size for cache.ext4, system.ext4 and data.ext4.
I guess the real data must be distributed in the BLOG directory with it's > 2500 sub-directories and taking up 2.7 GB space.
The directory download contains some strange named files :
> ..
6.182.912 -1032133489
157 -1046604230
6.180.864 -1582411299
60.826 -2110140792
907 -750693690
4.846 102398884
2.263 1306009840
73.462 1487533053
630 386293678
9.153 426056750
747 488289109
12.516.767 bytes
Filenames are "random" numbers and all together only about 12 MB
I suspect it has to do with ROM manager, do you have ROM manager installed ?
The problem is that the only backup I have are these, so I can't just trash ROM-manager because I'm unaware of any other tool that is able to handle these backups.
What version from CWM recovery is displayed when a backup is started ?
weird... this is what it looks like in my nandroid back up folder....
it should look like this.
EDIT: i used CWM app to run the backup from the OS, but recovery should be the same
Sent from my GT-I9300 using xda app-developers app
So if I didn't make a backup and wanted to restore back to JB, I will have to setup everything again?
a backup is only there to "restore" you to the point that you made a backup. think of it as a failsafe.
EDIT: yes, if you did not make a backup, you'll just have to flash a stock rom of choice (assuming you're going to stock) and set up everything again (contacts, apps, messages, etc)
the current CWM has 2 options when backing up the files.you can either choose TAR or DUP.default setting is dup.DUP saves more space when you make multiple backups as it stores the core files in the blob folder and only updates the different file when you make a different backup.if you want independent backups,set it to TAR in CWM recovery>backup and restore>choose backup format.
LaZyDood said:
the current CWM has 2 options when backing up the files.you can either choose TAR or DUP.default setting is dup.DUP saves more space when you make multiple backups as it stores the core files in the blob folder and only updates the different file when you make a different backup.if you want independent backups,set it to TAR in CWM recovery>backup and restore>choose backup format.
Click to expand...
Click to collapse
Thank you !
That must be why I could never make a single "stand-alone" NANDROID backup from my SG3 !
To eliminate any interaction from my ROM Manager, I uninstalled it using Titanuim Backup, as I've seen some posts saying that ROM manager doesn't work well with Sammy's, but I don't know for sure.
After rebooting, I went manually in to CWM recovery (the 3 button trick) and created a backup on my external SD card. (not on phone memory).
This is what I got :
An extra directory with current date as name was created under /mnt/extSdCard/ClockWorkMod with the files :
boot.img
cache.ext4.tar
cache.ext4.tar.a
cache.ext4.tar.b
data.ext4.tar
data.ext4.tar.a
nandroid,md5
recovery.img
system.ext4.tar
system.ext4.tar.a
system.ext4.tar.b
Total space occupied : 1.8 GB
Is this the "expected" output from a "backup" (I wanted a nandroid backup) from CWM ?
It seems that some .TAR files are 0 bytes and 2 files are then generated : one with a .TAR.A and one with a .TAR.B.
The file system.ext4.tar.a for example is is exactly 1.000.000.000 bytes, de rest is in system.ext4.tar.b
Note that I'm using the "Touch version 6.0.1.2" from CWM recovery (see method here by mskip (author from "The Toolkit v6.0 for SG3)"
Is this a so called "standard" NANDROID backup ?
Can this completely restore my SG3 to it's current state including all apps, settings,.... ? Obviously I can do a restore using CWM recovery (t least I hope so, but also using "The Toolkit" via it's ADB commands ?
Further, I'm also asking myself about keeping on to use ROM-manager or not, any experiences on SG3 with it (good and bad please) ?
Guys i have a karbonn A21 running ICS 4.0.4
I recently flashed its newly compiled CWM recovery 5.0.xx version ( 5.0.2.8 is full name i guess)
When i try to backup my rom.. it backs up my system image... everything but when it comes to backing up of data .. it gets stuck at the last on a file tombstonenocrash01 .. and after some time the phone reboots itself.
When i check my backup folder in clockworkmod there's about 435 MB of backup data in there including recovery.img , boot.img , data.ext4.tar and system.ext4.tar .
I just wanna ask that is the backup of my rom Complete and is it safe to restore that backup without any errors ?
Because it didnt show " backup complete" and rebooted itself automatically while backing up data in the end .
Help me please !!!
I would not recommend to restore this backup. I don't think it is consistent.
Try the following:
Open your file manager and go to /data/tombstones. Delete tombstonenocrash01 and try backup again.
blu2lz said:
I would not recommend to restore this backup. I don't think it is consistent.
Try the following:
Open your file manager and go to /data/tombstones. Delete tombstonenocrash01 and try backup again.
Click to expand...
Click to collapse
Dont you think it might cause a system crash by deleting that file ? Cause its in the android data folder( not on the sdcard) . There are three of those tombstone files. When i extracted my backed up data.ext4.tar i saw those three files are present . And moreover the size of data folder in android directory is same as that of backed up data.ext4.tar .
What should i do ? Restore or not ?
I am scared cause at the moment we dont have any stock rom for the device and if i restore the device and problem crops up then my device is gone. Suggestions please
I wouldn't use that backup ....it will tell you when backup is complete .......and it doesn't look like yours is
Your phone is still working ??? I would download a stock rom or another rom for your phone and copy it to sd card at least you can
use cwm to install it
Hope this helps
Nishchay1 said:
Dont you think it might cause a system crash by deleting that file ? Cause its in the android data folder( not on the sdcard) . There are three of those tombstone files. When i extracted my backed up data.ext4.tar i saw those three files are present . And moreover the size of data folder in android directory is same as that of backed up data.ext4.tar .
What should i do ? Restore or not ?
Click to expand...
Click to collapse
As I wrote, don't restore.
For deciding to delete the tombstone files you might want to know what they are for:
If one of your apps crash (forced close) such a tombstone file is created. It is kind of a system dump to search for the error. Maybe some apps crashed in the past on your phone.
Always remember:
Files in /data are configuration files. If you format/wipe data in CWM recovery and reboot, your system is still okay. Wiping data only leaves you without configuration of the apps you have installed.
So don't panic, deleting tombstone files does no damage to your system.
blu2lz said:
As I wrote, don't restore.
For deciding to delete the tombstone files you might want to know what they are for:
If one of your apps crash (forced close) such a tombstone file is created. It is kind of a system dump to search for the error. Maybe some apps crashed in the past on your phone.
Always remember:
Files in /data are configuration files. If you format/wipe data in CWM recovery and reboot, your system is still okay. Wiping data only leaves you without configuration of the apps you have installed.
So don't panic, deleting tombstone files does no damage to your system.
Click to expand...
Click to collapse
Deleting tombstone files doesnt help. It's still getting stuck at backing up data . Recovery's fault i guess
fredworxz said:
I wouldn't use that backup ....it will tell you when backup is complete .......and it doesn't look like yours is
Your phone is still working ??? I would download a stock rom or another rom for your phone and copy it to sd card at least you can
use cwm to install it
Hope this helps
Click to expand...
Click to collapse
The phone is kinda new so no roms (even stock) are availible right now
Can anybody help in building a new recovery ?
Nishchay1 said:
The phone is kinda new so no roms (even stock) are availible right now
Can anybody help in building a new recovery ?
Click to expand...
Click to collapse
Yeah.. Please Anyone...
I hope if backup is successful i can create a ROM
Please Anyone!! X)
Hi! I have a Leeco Le Max 2 X829, and as there aren´t any official stock ROM I wanna save a 100% stock Backup of my X829 with 16S USA ROM. I mean ROM + Recovery, just as it is unpacked(without downloaded Apps and my data).
Could I make it booting in temporaly TWRP with fastboot and doing NAND backup choosing:
- Boot
- Recovery
- System
- Data...
Any other option? All options that TWRP show? thanks!
Yes. EFS too
Turn on phone with power+volume keys.
Fastboot boot TWRP.img
unrafa said:
Yes. EFS too
Turn on phone with power+volume keys.
Fastboot boot TWRP.img
Click to expand...
Click to collapse
Then must I choose all options in TWRP backup?
One more thing... I Will be in a booted Recovery, so original Recovery is going to be still, then the one saved in the backup Will be the booted one ore the stock one? Thanks!
If you just want a factory setup without your apps and data I would say just backup the system image in twrp, backing up data definitely uncheck .
Only system is bit to less...
I would keep the us version.
eUI is not that bad and until we all get the update to android 7 ... it s probably the best and most stable rom running.
Why change it, when the other opportunities are leading to an less smooth running phone ?
To me all the cooked roms have disadvantages.
I need to have a fully working phone/ camera /fingerprint sensor...
without option to go back to the US rom I wouldn't change a thing!
castuis said:
If you just want a factory setup without your apps and data I would say just backup the system image in twrp, backing up data definitely uncheck .
Click to expand...
Click to collapse
Mmm, then all options least Data? Thanks!
Don't listen to them. Back up everything. Who cares about a few space? Besides data is probably empty or with a few stock tools. Just backup all for your complete image. EFS contains IMEI and other stuff. It is important to have it. You can Back up everything, and then move it to a computer or somewhere else
It will have stock recovery backed up to TWRP and it's better if you backup as image, that way it saves the partition structures too.
Only first backup as image,to have perfect copy, the next backups you do is better do them as normal backups compressed (not image).
unrafa said:
Don't listen to them. Back up everything. Who cares about a few space? Besides data is probably empty or with a few stock tools. Just backup all for your complete image. EFS contains IMEI and other stuff. It is important to have it. You can Back up everything, and then move it to a computer or somewhere else
It will have stock recovery backed up to TWRP and it's better if you backup as image, that way it saves the partition structures too.
Only first backup as image,to have perfect copy, the next backups you do is better do them as normal backups compressed (not image).
Click to expand...
Click to collapse
Hi, I have done and it made a lot of .win archives, is that right? thanks
Yes those are md5 or Sha sums, drag the whole TWRP folder to computer and you are good to go, don't change any name of any folder inside TWRP folder or TWRP will never detect that backup.
I don't know why but once I copied all except 73shf38 folder, and it turned out that folder with those numbers matter, and I couldn't restore without the exact name