I saw this "thing" in recovery,any one know a way that help me get rid of it or somehow reduce the file size?
Trung Gs said:
I saw this "thing" in recovery,any one know a way that help me get rid of it or somehow reduce the file size?
Click to expand...
Click to collapse
Get rid of it, why in the world would you want to?
You don't need to use it, it's to create a raw backup of the system partition, that means a bit for bit exact copy. It also allows factory images to be flashed.
If you'd rather stick with a file based backup then just use the normal system backup.
how to format that partition??
Related
Well, I have made a few NAND backups here and there whilst using different ROMs for my Evo. I only have one issue: how do I tell which setup was which ROM? Is there a way I can tell, without NAND restoring each individual one, which NAND backup is which ROM? Like maybe previewing it?
Also, I once read that you can take them off of your Evo and put them on a desktop so it doesn't take up space. Well I was wondering can I rename the folders and files to the setup they are or even to anything? Will it mess up if I try to restore to it after changing the name?
Thanks you
DRatJr said:
Well, I have made a few NAND backups here and there whilst using different ROMs for my Evo. I only have one issue: how do I tell which setup was which ROM? Is there a way I can tell, without NAND restoring each individual one, which NAND backup is which ROM? Like maybe previewing it?
Also, I once read that you can take them off of your Evo and put them on a desktop so it doesn't take up space. Well I was wondering can I rename the folders and files to the setup they are or even to anything? Will it mess up if I try to restore to it after changing the name?
Thanks you
Click to expand...
Click to collapse
You can remove them to your desktop to free up some space on your SD card and YES you can rename your Nandroid folders not the files.
So for example if your Nandroid folder is setup like this...../Nandroid/HT0CMHL08312/BCDEARS-20110622-0404......THEN you can rename the BCDEARS-20110622-0404 into whatever you want as long as you don't have any spaces and if you do have spaces then replace them with either _ or - to avoid any errors during restore
Oh and this is all assuming you're running amon ra recovery not clockworkmod which the folders will be setup differently which in that case you would just rename the last folder before you see all the files such as recovery.img and things like that.......
Okay thanks. Do you know how I could identify them without restoring to each individual one?
DRatJr said:
Okay thanks. Do you know how I could identify them without restoring to each individual one?
Click to expand...
Click to collapse
The only way I know aside from restoring them and to be honest, this way is kind of long but not longer then restoring the files one by one IS......
download an app from the market called unyaffs2
Make a folder on the SD card "whatever you want to call it"
once you download that app, copy over the system.img to that folder you just created from whatever restore folder you're trying to ID
Run unyaffs2
Hit Browse for input (find the system.img)
Hit Start Unyaffs
Once is finish doing it's thing, navigate to the folder you created and you should find a file called build.prop, go ahead and open it up with a text editor.....if you're using Root Explorer then is one of the options in that app
Once you're inside that app, navigate to the very bottom until you see "ro.modversion" and that should tell you what the ROM is whether is Cyanogenmod 7 or Sprint Lovers or whatever......
Kinda lengthy haha. I wish they would just have an emulator for PC or something to where you could just have it "virtually restore" from the NAND and see what it was.
DRatJr said:
Kinda lengthy haha. I wish they would just have an emulator for PC or something to where you could just have it "virtually restore" from the NAND and see what it was.
Click to expand...
Click to collapse
Yeah is long but not as long as rebooting into recovery, wiping caches and factory settings, restoring......getting an ID on the rom and doing it all over again time after time after time...hahahaha
Hey guy's just figured id copy and paste this article I read about recovery backups and blob folder within..
If your like me you probaly wondering what this new blob folder is and why is it consuming alit of space...so I was gonna delete it but decided not too and read first this is what I found:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
https://plus.google.com/103583939320326217147/posts/L5aVZe7C9vg
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was*c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Thank you for the info! I was just looking for this today as my blobs was about 4gb large
Question:
If I wanted to free up space and backup my backups to my PC, could I just move the backup folders with the entire Blobs folder and be good to go?
Thanks.
msherman123 said:
Thank you for the info! I was just looking for this today as my blobs was about 4gb large
Question:
If I wanted to free up space and backup my backups to my PC, could I just move the backup folders with the entire Blobs folder and be good to go?
Thanks.
Click to expand...
Click to collapse
Yeah personally that's what I did to save my backups i needed in case of anything...since the new system deletes your old one when making a new backup..it cleans or so called "unused space" now....what I did is save the whole clockwork folder and placed it on my computer and save them as according to what ROM now...this new setup I don't like....I had 4 GB in my blob folder too...what a waste of space. for a new idea..I understand there method of a full proof backup system..but why change something that wasn't broke in the first place right?...
wish777 said:
Yeah personally that's what I did to save my backups i needed in case of anything...since the new system deletes your old one when making a new backup..it cleans or so called "unused space" now....what I did is save the whole clockwork folder and placed it on my computer and save them as according to what ROM now...this new setup I don't like....I had 4 GB in my blob folder too...what a waste of space. for a new idea..I understand there method of a full proof backup system..but why change something that wasn't broke in the first place right?...
Click to expand...
Click to collapse
I am not sure, but doesn't cwm have an option to backup to single file like it used to?
Sent from my SGH-I317M using Tapatalk 2
I'm not sure man..if you see it let me know..I'd love the old setup. This new way is horrible... Lol
wish777 said:
I'm not sure man..if you see it let me know..I'd love the old setup. This new way is horrible... Lol
Click to expand...
Click to collapse
In theory this should be a much more efficient use of space. Im sure each backup contains a lot of files/data that is already backed up in a previous backup basically wasting space on redundant data. This is kinda like backup cubing sorta...at least the way Im thinking of it. This method saves nothing ONLY if every single backup is absolutely unique which would make your blob huge. I like the idea....but I use twrp so it doesnt affect me.
wish777 said:
I'm not sure man..if you see it let me know..I'd love the old setup. This new way is horrible... Lol
Click to expand...
Click to collapse
I don't have cwm installed, but check settings, I am confident you'll find an option for tar or whatever format it was before.
Have you tried twrp? I heard great things about it.
Sent from my SGH-I317M using Tapatalk 2
sonny21 said:
I don't have cwm installed, but check settings, I am confident you'll find an option for tar or whatever format it was before.
Have you tried twrp? I heard great things about it.
Sent from my SGH-I317M using Tapatalk 2
Click to expand...
Click to collapse
You know I been flashing roms for so many years that I guess im old school. .lol I never tried twrp..I guess I should try it from alot of people giving it such postive reviews..I guess im just stuck in my ways ibshould be more openmined about recovery....lol....thank you
wish777 said:
You know I been flashing roms for so many years that I guess im old school. .lol I never tried twrp..I guess I should try it from alot of people giving it such postive reviews..I guess im just stuck in my ways ibshould be more openmined about recovery....lol....thank you
Click to expand...
Click to collapse
Yeah no problem, usually I like to stick to what works for me as well.
Sent from my SGH-I317M using Tapatalk 2
wish777 said:
You know I been flashing roms for so many years that I guess im old school. .lol I never tried twrp..I guess I should try it from alot of people giving it such postive reviews..I guess im just stuck in my ways ibshould be more openmined about recovery....lol....thank you
Click to expand...
Click to collapse
Have found that TWRP and CWM have there specific needs and functions. I usually try both when settleing on a dailu driver. Kinda odd but they handle data slightly different and bugs turn up on a install depending on one or the other. (Under controlled conditions and data that you can reference) . I have just had to accept that some things work well with TWRP and others with CWM.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Thank you guys for the info ..
wish777 said:
Hey guy's just figured id copy and paste this article I read about recovery backups and blob folder within..
If your like me you probaly wondering what this new blob folder is and why is it consuming alit of space...so I was gonna delete it but decided not too and read first this is what I found:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
https://plus.google.com/103583939320326217147/posts/L5aVZe7C9vg
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was*c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Click to expand...
Click to collapse
what if you just want to backup your nandroids to an external hard drive. I just copied most of my nandroids from the phone to my hard drive. and deleted them from the phone.
i didn't touch the blobs folder.
So now my backups I copied to my hard drive are useless without the blobs? And on top of that, if I understand correctly, the blobs needed to make those backups functional will be automatically deleted the next time i do a backup?
this sounds horribly horribly wrong. how do i copy functional nandroids from my phone to my hard drive?
mistermojorizin said:
what if you just want to backup your nandroids to an external hard drive. I just copied most of my nandroids from the phone to my hard drive. and deleted them from the phone.
i didn't touch the blobs folder.
So now my backups I copied to my hard drive are useless without the blobs? And on top of that, if I understand correctly, the blobs needed to make those backups functional will be automatically deleted the next time i do a backup?
this sounds horribly horribly wrong. how do i copy functional nandroids from my phone to my hard drive?
Click to expand...
Click to collapse
Good question, I made 3 backups one of the stock rom, which I stored to my mac.
The most recent back up the blobs are still on my phone, does that mash my mac backups are defunct now?
Cheers.
Great post wish777. I wondered about deleting a CWM backup when I read about the blob system, so it's great to have the garbage collection clarified.
Still, I agree with the other posts, the blob system makes moving a backup off the phone and back again unreliable. I am also old school - I ghost everything. That's why I'm using TWRP instead. I'm happier just dealing with image files that stand on their own.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Okay I'm really in need of a response from who knows the mechanic of backing up
I've two questions
1. I've noticed that u can actually flash apps with a zip file. So if I put my personal apps into the rom folder after extracting them and recompress, is it possible that my apps will also get flashed along w the rom?
2. I've also noticed when u do a factory reset in the recovery, it only deletes cache and data. If I copy the data folder to my sdcard and paste to the orig directory after factory reset, is it possible that the data will get restored?
I'm not just curious. I think if this is possible, it'll be much dependable
Thnx
Sent from my Galaxy Nexus using xda app-developers app
christianyu said:
Okay I'm really in need of a response from who knows the mechanic of backing up
I've two questions
1. I've noticed that u can actually flash apps with a zip file. So if I put my personal apps into the rom folder after extracting them and recompress, is it possible that my apps will also get flashed along w the rom?
2. I've also noticed when u do a factory reset in the recovery, it only deletes cache and data. If I copy the data folder to my sdcard and paste to the orig directory after factory reset, is it possible that the data will get restored?
I'm not just curious. I think if this is possible, it'll be much dependable
Thnx
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
1. Yes, put the app's APK under /data/app in your zip package (although I do think that you need to modify the updater-script a bit to make it actually flash the apps).
2. Depending on how you do it - you MUST keep ALL the files' and folders' permissions untouched (which is nearly impossible since there are just WAY too many of them), or when you simply copy back, the permissions will be messed up and you'll face continuous FCs. Better use apps like Titanium Backup or, if you're brave enough, try restoring only the /data partition from an existing nandroid backup.
Sent from Samsung Galaxy Nexus @ CM11
1. How do I modify the updater script?
2. Is it possible to restore only part of the nandroid backup?
Sent from my Galaxy Nexus using xda app-developers app
Titanium Backup is the best way. The way you are doing it sounds like a lot of unnecessary work.
look for an app called zipme from author jrummy on the play store
I wrote some code a long while back that allows you to pack/encrypt and unpack/unencrypt your own android backups so that you can do your own partial backups and restores.
See http://forum.xda-developers.com/showthread.php?t=1730309
However, for the past 18 months, I have just used BackupPC to back up my android devices. BackupPC is a linux-based backup that allowd for automated backups with all types of options for incrementals & fulls. The backup files are pooled so that you can backup every day while requiring minimal extra space since only new files add to the poo size. It can use several different transport systems for the backup ranging from rsync to rsyncd to tar to ftp etc.
I use rsync (over ssh) since it is fast -- only the deltas need to be transported across the network when files change.
Basically, all you need to do is install ssh + rsync, modify the server side config file and then you get automatic backups at your own pre-determined frequency over wifi whenever your device is connected to the wifi network.
Now BackupPC is probably overkill for just backing up a droid -- since it is typically used to backup whole networks of linux, Mac, Windows, etc. pc's. But since I already use it to backup all my home computers, it was a cinch to modify the config file to also backup my droid devices.
I verified that it worked when my Gnexus broke and I was able to flash the replacement device which restored not just my apps and data but also all my settings.
jsgraphicart said:
Titanium Backup is the best way. The way you are doing it sounds like a lot of unnecessary work.
Click to expand...
Click to collapse
I agree. The play store has a bunch of other ones too but I would go with Titanium.
hsypsufan said:
I agree. The play store has a bunch of other ones too but I would go with Titanium.
Click to expand...
Click to collapse
I am using EaseBackup and I find it very good. Helium is another option but I found it buggy.
I ran into a weird problem when trying to get a backup onto my device.
I created that backup today, copied it to my pc for storage, wiped the system and tried to install a custom ROM. That failed so i decieded to just move my backup back to the phone and restore it.
Now the real problem comes in: One of the files is bigger than 4GB and I can't find any way to get that thing back onto the device. ADB just fails miserably and doesn't do anything and direct copying via windows explorer tells me it exceeds the file size limitation which seems pretty dumb to me because this file comes from the phone.
Is there some workaround for a file transfer like this?
Hope you guys can help
DarkMathis said:
I ran into a weird problem when trying to get a backup onto my device.
I created that backup today, copied it to my pc for storage, wiped the system and tried to install a custom ROM. That failed so i decieded to just move my backup back to the phone and restore it.
Now the real problem comes in: One of the files is bigger than 4GB and I can't find any way to get that thing back onto the device. ADB just fails miserably and doesn't do anything and direct copying via windows explorer tells me it exceeds the file size limitation which seems pretty dumb to me because this file comes from the phone.
Is there some workaround for a file transfer like this?
Hope you guys can help
Click to expand...
Click to collapse
if your device supports otg, you could flash it from there. it would also be easier in the future to backup to otg, then you dont have to move it and worry about possible corruption.
The Problem is resolved. Luckily the file was only needed for a system image backup so i coulld just ignore it and still restore the phone. Now for that stock recovery
Im on OOS and made a nandroid backup via TWRP (official)/ Backup size was 5 GB... So i thought this is regard to OOS. Then yesterday i flashed CM ROM and made a nandroid backup.Back up size was 5 GB.. What the hell. Then i looked in to both of OOS and CM TWRP backup folders. I've notice that those commom files on both backups are massive.."system_image_emmc" is 2.4 GB and "system.ext4" is 1GB .. What is this?Why this much of capacity? Is this normal for OP3 or am i doing something wrong?
In twrp, when in the backup section you can go to settings I believe and enable compression.
crazykas said:
Im on OOS and made a nandroid backup via TWRP (official)/ Backup size was 5 GB... So i thought this is regard to OOS. Then yesterday i flashed CM ROM and made a nandroid backup.Back up size was 5 GB.. What the hell. Then i looked in to both of OOS and CM TWRP backup folders. I've notice that those commom files on both backups are massive.."system_image_emmc" is 2.4 GB and "system.ext4" is 1GB .. What is this?Why this much of capacity? Is this normal for OP3 or am i doing something wrong?
Click to expand...
Click to collapse
untick the system image option in twrp when making a backup of anything that doesn't need OTA compatibility. A system image backup will always be the same size because it's taking a backup of the entire /system so it basically makes the empty space take up space in the backup.
Mine is 7.08GB even without system image ?
StykerB said:
untick the system image option in twrp when making a backup of anything that doesn't need OTA compatibility. A system image backup will always be the same size because it's taking a backup of the entire /system so it basically makes the empty space take up space in the backup.
Click to expand...
Click to collapse
Should be system images of OOS vs CM be different capacities? Anyway, if i untick system image emmc, would be a problem when i restoring that backup?
crazykas said:
Should be system images of OOS vs CM be different capacities? Anyway, if i untick system image emmc, would be a problem when i restoring that backup?
Click to expand...
Click to collapse
a system image takes a copy of the entire /system so even the empty space in /system will take up space in the image because the image needs to represent bit for bit the entire /system. A regular system backup intelligently stores the files from /system so it takes up less space but you lose compatibility with anything that requires bit for bit exact /system (basically only OTA's right now) but for any sorta custom rom use it's 100% fine.
You basically only cannot use an incremental OTA from Oneplus if you use a regular system backup.