Develop Bugs

CLOCKWORK recovery backup blob folder info!

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

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Reserved!

Dees_Troy is one of the best and nicest developers here, he did it all in like 5 minutes
Kudos brother, this is a great addiction for the Wonder!

sorry , is the image size 7.984MB ?

hadidjapri said:
sorry , is the image size 7.984MB ?
Click to expand...
Click to collapse
4.37MB, MD5 is 4c689ba24c1657540d8094124bf1e155

Dees_Troy said:
Direct Download
Turn the device off. Press and hold volume down, volume up, and power until the device boots, then on your computer:
fastboot flash recovery openrecovery-twrp-2.3.2.3-mako.img
Click to expand...
Click to collapse
this link refers me to the file with 7.984MB

hadidjapri said:
this link refers me to the file with 7.984MB
Click to expand...
Click to collapse
Ahhh, that is what I get for copying and pasting >_<

Dees_Troy said:
Ahhh, that is what I get for copying and pasting >_<
Click to expand...
Click to collapse
you get me bricked my phone :crying:
i hope nobody do the same mistake as i am by flashing "extreme huge" recovery.img
i didn't notice that ancora's recovery partition only capped to 7.5MB :crying:
well, it's not a problem. ssc is near my house
thanks for porting TWRP to ancora :good:

post no weighted ANCORA WAE LAH ....!:good:

hadidjapri said:
you get me bricked my phone :crying:
i hope nobody do the same mistake as i am by flashing "extreme huge" recovery.img
i didn't notice that ancora's recovery partition only capped to 7.5MB :crying:
well, it's not a problem. ssc is near my house
thanks for porting TWRP to ancora :good:
Click to expand...
Click to collapse
Odin should be able to fix it.

Dees_Troy said:
Odin should be able to fix it.
Click to expand...
Click to collapse
well, ancora's download mode sucks. it wastes me almost 1,5hours only stucked in "press up to continue"
gonna try the twrp after ssc fix my phone :good:

Testing it..
Sent from my GT-P5100 using xda premium

Thanks for porting it!

Can I flash this with adb and this command? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
-sent from my awesome phone-

hotheabilly said:
Can I flash this with adb and this command? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
-sent from my awesome phone-
Click to expand...
Click to collapse
Tested it, yes it works. But I reverted to CWM for a reason.
Sent from my GT-I8150 using xda app-developers app

Kreaz said:
Tested it, yes it works. But I reverted to CWM for a reason.
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Yes it works for me too, and yes I'm back to cwm for some reason too
-sent from my awesome phone-

comment removed.

hotheabilly said:
Yes it works for me too, and yes I'm back to cwm for some reason too
-sent from my awesome phone-
Click to expand...
Click to collapse
I screwed up ma phone. I flashed TWRP via ADB. When i reboot to recovery it goes to CWM. When i switch on normally it goes to TWRP!!! Now im havin 2 recoveries and i cant boot to SlimBean!!!!!! Any fix?!?!?
Edit: I did a full wipe and Restored my system. Thanks to CWM!!

jassim007 said:
I screwed up ma phone. I flashed TWRP via ADB. When i reboot to recovery it goes to CWM. When i switch on normally it goes to TWRP!!! Now im havin 2 recoveries and i cant boot to SlimBean!!!!!! Any fix?!?!?
Edit: I did a full wipe and Restored my system. Thanks to CWM!!
Click to expand...
Click to collapse
lololol you probably format your ROM partition by your command line and replacing the whole rom to TWRP, but this is the first case I've ever seen!

hotheabilly said:
lololol you probably format your ROM partition by your command line and replacing the whole rom to TWRP, but this is the first case I've ever seen!
Click to expand...
Click to collapse
Is there .tar format for flashing TWRP via Odin?

[Q] How big is your Nandroid /blobs folder?

Hi! I am new to making Nadroid backups. Yesterday, I could've swore my /blobs folder was about 3GB. Today, when I made another Nandroid and it was at 6GB.
I'm on the dedup method, so my /blobs folder shouldn't be increasing. I also tried "free unused backup data" and still at 6GB.
Here's my storage usage, attached. Am I in the right ballpark or is something odd here?
P.S. If anyone has a Nandroid backup management system, let me know! I keep jumping between CWM Recovery to make them and then to Android to fix all the things CWM Recovery does wrong (like the date-for-the-file-name; it's not 1970 and the month/day/time are all incorrect) and can't do (like viewing the backups, renaming the backups, uploading the backups to cloud storage).

My blobs folder at one point was at 4gig. I deleted all my backups except for two. Went into cwm and selected free space under backup/restore and brought it down to 1.01gig.
Mind you the only backup I care about (rooted, stock with TW) is 1.8gig but I have that on external and on my computer just in case.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KorGuy123 said:
My blobs folder at one point was at 4gig. I deleted all my backups except for two. Went into cwm and selected free space under backup/restore and brought it down to 1.01gig.
Mind you the only backup I care about (rooted, stock with TW) is 1.8gig but I have that on external and on my computer just in case.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hmmm...that may be it: this new backup required new blobs for whatever reason. Let me figure out a way to restore SystemUI and SecSettings to stock and then maybe delete those early backups...
How much space have you used,by chance, on the internal SD card?
~Ibrahim~

the blobs folder continues to grow with each backup. the only time it would decrease is you delete a backup then clear unused data after booting to recovery.
this blobs folder will drive your media scanner CRAZY.
my suggestion is to boot into recovery, set the backup type to .tar rather than the default .dup. This unfortunately will cause each backup to take up approx 1.5g, but that is an incredible reduction in indvidual files for the media scanner to scan. but, thats what ext sd cards are for
after making this change, if you have .dup backups you want to convert to .tar, you will have to restore each then backup again.

ikjadoon said:
Hmmm...that may be it: this new backup required new blobs for whatever reason. Let me figure out a way to restore SystemUI and SecSettings to stock and then maybe delete those early backups...
How much space have you used,by chance, on the internal SD card?
~Ibrahim~
Click to expand...
Click to collapse
I formatted internal when I went to PAC-Man I've done one back since so my internal is fairly empty. (I switched to TWRP recovery and the backups are around 750mbps)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Russ77 said:
the blobs folder continues to grow with each backup. the only time it would decrease is you delete a backup then clear unused data after booting to recovery.
this blobs folder will drive your media scanner CRAZY.
my suggestion is to boot into recovery, set the backup type to .tar rather than the default .dup. This unfortunately will cause each backup to take up approx 1.5g, but that is an incredible reduction in indvidual files for the media scanner to scan. but, thats what ext sd cards are for
after making this change, if you have .dup backups you want to convert to .tar, you will have to restore each then backup again.
Click to expand...
Click to collapse
YES. YES. THAT'S THE OTHER ISSUE! These things are all related! My Media scanner, out of *nowhere*, exploded to 50% battery usage.
Going to *.tar, then. Thank you hugely.
@KorGuy
I may transition to TWRP. CWM is a fine recovery, but it's backup solution isn't up to par. Appreciate the help!

0... I don't make nandroids... use the external sd...

Quasimodem said:
0... I don't make nandroids... use the external sd...
Click to expand...
Click to collapse
Wait, so how do you backup? I make Nandroids onto the external SD.

ikjadoon said:
Wait, so how do you backup? I make Nandroids onto the external SD.
Click to expand...
Click to collapse
I don't make backups or use tibu...
Not sent from your phone...

Quasimodem said:
I don't make backups or use tibu...
Not sent from your phone...
Click to expand...
Click to collapse
You're brave. But probably more experienced. I bootloop'd my GS3 after just trying to modify the framework-res.apk and my Nandroid saved me! But, I'm on TWRP now and it looks much better.

ikjadoon said:
You're brave. But probably more experienced. I bootloop'd my GS3 after just trying to modify the framework-res.apk and my Nandroid saved me! But, I'm on TWRP now and it looks much better.
Click to expand...
Click to collapse
I've got everything I need on the SD to fix whatever... not really worried about it...
Not sent from your phone...

To be honest the huge blobs folder you are stuck with using cwm is exactly why I switched to twrp recovery and I was a long time user and big fan of cwm for a long time. But the blobs really screwed that up for me anyway. Twrp works great and is better in my opinion ...
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

I'm using cwm 6.0.2.2 touch recovery and it doesn't have none of that blob folder crap
sent from the dark side of the universe....

thatsupnow said:
I'm using cwm 6.0.2.2 touch recovery and it doesn't have none of that blob folder crap
sent from the dark side of the universe....
Click to expand...
Click to collapse
I just updated cwm and noticed that the default is now .tar

Good call from Koush, then. They're a good idea, but executed poorly.
But, CWM has problems for me beyond blobs: it mislabels backups without a way to rename in CWM, somehow mismatched the MD5 of my backups (until I renamed them to "backup" ), and doesn't seem to compress backups = all fixed in TWRP.
Battery life is fixed!

Interesting Experience with CWM Recover 6.0.2.3

I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?

solidhound said:
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
Click to expand...
Click to collapse
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.

milky1112 said:
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
Click to expand...
Click to collapse
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!

solidhound said:
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
Click to expand...
Click to collapse
That is very possible, still odd that it will not let you delete even with R/W permissions set. But as long as everything is working.. Then i wouldn't fuss too much

The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2

edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks for clarification Ed. I've been on TPR for a while so haven't flashed any 4.2 roms.

edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
hey edfunkycold,
thanks a ton for the response and clarification! i was thinking about swapping recoveries but i already reverted back to the original nandroid image i had at that point.
and you are correct. i was on 4.1 and not 4.2. i didn't know such changes were made but its great to see dual boot is coming up.
i will make sure to THANK both responses once i reach 10 posts. i'm trying hard to participate in these forums but haven't had time until recently.

CWM blobs ?? Where have they gone ?

Maybe a stupid question .....
With the latest CWM Im aware that Nandroids go to Blobs .... Im trying to then copy a backup to my PC (as its 3.5GB) but I cant find it !? Nothing in the clockworkmod folder. The backup definitely worked as im now 3.5gb lower on space but I cant find the blobs anywhere ???

Which CWM and which version of android? If youre above CWM 6.0.1.9, and android 4.2, the backups should be in data/media/clockworkmod, rather than data/media/0, which is your sdcard.

bodh said:
Which CWM and which version of android? If youre above CWM 6.0.1.9, and android 4.2, the backups should be in data/media/clockworkmod, rather than data/media/0, which is your sdcard.
Click to expand...
Click to collapse
Im on 6.0.2.3 (touch) and 4.2.1 ROM. Ive got a clockworkmod folder - just no blobs in it ??

The latest version has reverted to the .tar method, which means you do a full back up without the blobs folder.
However if you prefer the blobs folder method, you can change it in the settings in recovery. The new default method is .tar (non blob)

gpfnzl said:
The latest version has reverted to the .tar method, which means you do a full back up without the blobs folder.
However if you prefer the blobs folder method, you can change it in the settings in recovery. The new default method is .tar (non blob)
Click to expand...
Click to collapse
thanks .... im still confused though as my clockworkmod folder is 5mb in size combined so the .tar must be somewhere ????

If you have made a backup using the latest version of CWM using a 4.2 rom you are unable to acess that backup with other apps. To save the backup you have made, open rom manager, in the backup restore section there is an option to down load to your computer over a server. Just connect your phone to your wifi, type the address it give you into your internet browser on your computer and select download

Very very interesting. In fact, I like the sound of this better than the blobs. Plus it sounds like koush addressed an issue i've been trying to solve: How to backup the backup to mac if you cannot see it in the sd.

bodh said:
Very very interesting. In fact, I like the sound of this better than the blobs. Plus it sounds like koush addressed an issue i've been trying to solve: How to backup the backup to mac if you cannot see it in the sd.
Click to expand...
Click to collapse
its interesting to know that to copy a nandroid to your PC you now have to fork out for ROM Manager Premium ....
I stopped using ROM Manager a while back when it really started screwing up my phone when flashing ROMs.

bodh said:
Very very interesting. In fact, I like the sound of this better than the blobs. Plus it sounds like koush addressed an issue i've been trying to solve: How to backup the backup to mac if you cannot see it in the sd.
Click to expand...
Click to collapse
The .tar full backup was the original method. The blobs folder was introduced to speed up the backup process, but users would delete the blobs folder which made the backups useless.

I mean that you can choose which method, either / or, from within clockworkmod. Good to know its a rom manager premium feature. I've never truly made use of rom manager. But i do still have the issue of how to backup the backup if i cannot see it from sdcard, so i'm exploring some possibilites.