I've just made a full backup of CM7.2 RC2 and its size is... 900MB! Usually my backups didn't exceed 400MB. There's one file which size is 540MB itself. Can someone explain what is it and why it's so big?
Nevermind I found the explanation. Please delete this thread
Related
So, if I have a ROM (CMYLXGO's Stock Desire) w/ 425 MB system partition and I back it up with CWM , then install another ROM with 150MB system partition (installing the 150MB partition prior to install of course), do I need to repartition back to the 425MB prior to restoring the 425MB partitioned backup?
Common sense would tell me yes, BUT, I figured I would ask just in case I am wrong!
JWhipple said:
So, if I have a ROM (CMYLXGO's Stock Desire) w/ 425 MB system partition and I back it up with CWM , then install another ROM with 150MB system partition (installing the 150MB partition prior to install of course), do I need to repartition back to the 425MB prior to restoring the 425MB partitioned backup?
Common sense would tell me yes, BUT, I figured I would ask just in case I am wrong!
Click to expand...
Click to collapse
Yes, you definitely need to re-partition.
Thank you - thats just what I needed to know!
JWhipple said:
Thank you - thats just what I needed to know!
Click to expand...
Click to collapse
glad I could help....
What will be the problem if i dont perform repartition?
I had been wondering if a nandroid backup would restore old partition sizes, since it backs up everything, but yeah i guess it makes sense that it can't change the size of the recovery partition, since that's what cwm is running from at the time of backup/restore. But does nandroid restore system and cache partition sizes?
Sent from my HTC HD2 using XDA App
huggs said:
I had been wondering if a nandroid backup would restore old partition sizes, since it backs up everything, but yeah i guess it makes sense that it can't change the size of the recovery partition, since that's what cwm is running from at the time of backup/restore. But does nandroid restore system and cache partition sizes?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
No, the restore just loads the partition contents into the partition, it doesn't adjust the sizes, or recreate them,, just loads the backed up contents into it.
Hello HD2 users,
This may seem like very basic information but got me confused so i want to share it with you. Its about restoring nandroid backups.
The Experiece:
I had the typhoon rom working very well. Its fast and smooth and i like it alot. Anyways, being a flash junkie and wanting to try out different roms all the time i wanted to try a sense 3.5 rom. It required a greater internal memory partition 200 or 245mb. I currently had 150mb.
So anyways, i made a nandroid backup in CWM and then flashed a new partition size, flashed the new sense rom and it was working. I didnt like it. I wanted the typhoon rom back. I booted into CWM and restored the backup. BUT it didnt work. The backup restored successfully but due to low internal memory, it didnt even go to the boot animation. Just stayed on the boot image.
The lesson:
To restore your nandroid backups and run them u need to restore them on the SAME partition size that you made them on.
If u made a backup with 200mb partition, the restored backup will ONLY WORK if your partition is still 200mb.
Just some basic info. Hope it helps people out
Peace
Sent from my HTC HD2 using xda app-developers app
adil1508 said:
The lesson:
To restore your nandroid backups and run them u need to restore them on the SAME partition size that you made them on.
If u made a backup with 200mb partition, the restored backup will ONLY WORK if your partition is still 200mb.
Click to expand...
Click to collapse
I would dispute that, and say that it is more likely that your increased system partition size resulted in the data partition being too small to restore fully.
Did you make sure you did a 'wipe data factory reset' before restoring? since leftovers on the sd card could be causing problems too.
did you try 'fix permissions'?
(Always happy to be proven wrong, of course, i'm no great mind when it comes to android, but i'm ((fairly) sure ive restored to larger partitions before)
samsamuel said:
I would dispute that, and say that it is more likely that your increased system partition size resulted in the data partition being too small to restore fully.
Did you make sure you did a 'wipe data factory reset' before restoring? since leftovers on the sd card could be causing problems too.
did you try 'fix permissions'?
(Always happy to be proven wrong, of course, i'm no great mind when it comes to android, but i'm ((fairly) sure ive restored to larger partitions before)
Click to expand...
Click to collapse
Yes i did fix permissions and wipe data/cache and dalvik cache too.
When i was using the typhoon rom i had like 200something used internal memory. And some 37 left. Not exact figures. So roughly 240mb is available after the partition. When i increase the partition, less than 240 is available. Maybe thats the reason?. Im not too sure too. Lets wait for some expert guy
Sent from my HTC HD2 using xda app-developers app
adil1508 said:
Yes i did fix permissions and wipe data/cache and dalvik cache too.
When i was using the typhoon rom i had like 200something used internal memory. And some 37 left. Not exact figures. So roughly 240mb is available after the partition. When i increase the partition, less than 240 is available. Maybe thats the reason?. Im not too sure too. Lets wait for some expert guy
Sent from my HTC HD2 using xda app-developers app
Click to expand...
Click to collapse
I am no "expert guy" but I have proved your theory wrong because I had a jelly bean Rom installed with a 150 mb partition and backed it up. Then this afternoon I remembered I needed a number from a text I received on that rom. I had since already repartitioned my phone to 250 mb and flashed a sense 3.5 Rom. I just restores my back up of jb made in a smaller partition and worked like a charm. Don't know the logistics behind it, just know it works
rawdaddymagraden said:
I am no "expert guy" but I have proved your theory wrong because I had a jelly bean Rom installed with a 150 mb partition and backed it up. Then this afternoon I remembered I needed a number from a text I received on that rom. I had since already repartitioned my phone to 250 mb and flashed a sense 3.5 Rom. I just restores my back up of jb made in a smaller partition and worked like a charm. Don't know the logistics behind it, just know it works
Click to expand...
Click to collapse
Ok thanks for the clarification. Ill look into it again.
Meanwhile, i urge other members to share their experiences too. To confirm.
Sent from my HTC HD2 using xda app-developers app
If I check compression and skip md5 sum, will it make the total size of my backups smaller? Is there any disadvantages to this? Also, do I need to backup the cache?
Armyrj127 said:
If I check compression and skip md5 sum, will it make the total size of my backups smaller? Is there any disadvantages to this? Also, do I need to backup the cache?
Click to expand...
Click to collapse
Can anybody help me out with this?
I have never tried it. But they are already zip files so I'm thinking they aren't going to get smaller. Also you can backup the cache if you want but it's not required. I don't ever backup cache.
Armyrj127 said:
If I check compression and skip md5 sum, will it make the total size of my backups smaller? Is there any disadvantages to this? Also, do I need to backup the cache?
Click to expand...
Click to collapse
Compression will definitely shrink the size of your backups but will make it take much longer. I have not done a comparison of size lately to give you a good estimate.
MD5 sums are good for verifying the integrity of the backed up file and don't use a significant amount of space, because it's just a short string of text.
Sent from my SM-N900V using xda app-developers app
Armyrj127 said:
If I check compression and skip md5 sum, will it make the total size of my backups smaller? Is there any disadvantages to this? Also, do I need to backup the cache?
Click to expand...
Click to collapse
Running Beans 5 a typical nandroid with no compression 3.1 GB, and 2 GB with compression. Compression also doubles backup time to 11 minutes. I do not use MD5 , but it is used to verify integrity of nandroid file at time of restoration (makes sure file is not corrupted). MD5 will add 1-2 minutes to backup time. Times are using 64GB sandisk extreme microsd card.
Thanks for all your input. From all the info you gave me, I will not backup cache, I will compress and I will use md5 to be safe.
Edit:
Fixed my issue.
I have a small affair since CM resized the partitions, and some questions haunt me.
The system partition of my phone is in the initial format 600MB and 1.3 GB for data. As everyone will know CM changed partitions to 400MB and 1.5GB of data.
Approach: I would like to have a ROM of Ginger for sporadic use of the camera and any other issues with Nandroid saved. I understand that this requires the old system partitions that i have, and kk for regular use with current system partition, copied also with Nandroid.
The issue is if when move from one to another from the corresponding copies saved from the recovery also restores the size of the partitions or not.
If not, is it absolutely necessary to have the partitions on the current format of CM for KK?, What problems can be if left to the native format 600MB, 1.3GB?
Regards
Note: Edited to better understanding, sorry for my poor english.
Hi everyone,
I have a situation here with my Nexus 4. I am running CWM Recovery 6.0.4.3 and AOKP nightly builds. I was using Stock ROM before AOKP. That time, before I upgraded I was trying to make a nandroid backup. I had around 7GB free space before performing the backup. Eventually the backup went wrong, it said "Error while backing up /data". I don't know what to do so I just reboot and re-run the backup process, but it still gave me the same error. I then boot into my phone and realized something... my free memory space has lessened to around 2GB only! I then decided not to make the backup and just flash my ROM to AOKP. I thought this will clear the problem, but it's not.
So, my question is, how to clear this used space? I checked in the nandroid backup folder and found absolutely nothing there, so it must be somewhere else... Any help would be appreciated! Thanks in advance
james.abcde said:
Hi everyone,
I have a situation here with my Nexus 4. I am running CWM Recovery 6.0.4.3 and AOKP nightly builds. I was using Stock ROM before AOKP. That time, before I upgraded I was trying to make a nandroid backup. I had around 7GB free space before performing the backup. Eventually the backup went wrong, it said "Error while backing up /data". I don't know what to do so I just reboot and re-run the backup process, but it still gave me the same error. I then boot into my phone and realized something... my free memory space has lessened to around 2GB only! I then decided not to make the backup and just flash my ROM to AOKP. I thought this will clear the problem, but it's not.
So, my question is, how to clear this used space? I checked in the nandroid backup folder and found absolutely nothing there, so it must be somewhere else... Any help would be appreciated! Thanks in advance
Click to expand...
Click to collapse
Just as you said, it must be somewhere. Check other folders or even the rood of the virtual SD card. If you still don't find anything you may have to factory reset the device and wipe the SD card partition. Before you jump the gun though, make sure (assuming you're using windows as your PC OS, show hidden folders.
Did you check of have a Clockworkmod folder? Each time you create a backup, it creates a new folder with a new time stamp.
Use a file manager to delete the unnecessary or aborted backups. The backup folder should be visible with having to use an app such as Root Explorer.