yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] gatebil:
have installed the non touch cwm. my backup to external sd was fine but the size of the backup is 3.65 gb. with cf cwm it was 1.5gb. ist that ok?
[Galaxy S III Original Android Development] andip71:
Can confirm this...

Hi,

I can confirm this. Data partition does not seem to get compressed somehow. With Chainfires CWM it is around 700 MB in my case, with this touch recovery it grows up to almost 3 GB.

But I have another issue: The touch CWM still cannot access my external SD card it seems. I have a 64 GB card, formatted with exFAT. Working fine in my phone, but seems CWM has an issue with it? Anyone can help or give ideas?

Thanks

Andi
[Galaxy S III Original Android Development] olavopb:
The same for me...
[Galaxy S III Original Android Development] Sepp0rl:
Neither does it work for me .it keeps counting and counting exsdcard.went back to normal cmw und everything is fine.
[Galaxy S III Original Android Development] slonn:
Touch CWM did a backup to the external sd card but the backup file is only 200mb. Usually backups are around 1.2GB so I definitely think something is wrong. Don't want to try and restore the small backup in case something goes wrong, so until this gets fixed I'll just keep backing up to the internal memory and then manually move the backup file to the external sd.
[Galaxy S III Original Android Development] mskip:
THREAD UPDATE

I tested 5.8.4.5 this morning and the data backup bug is present for both internal storage and external sdcard. The data backup size is over 3GB probably because its backing up more than it should.

Until this bug has been fixed I have reverted this thread back to 5.8.4.3 which works perfectly apart from the lack of ext sdcard support. If it is fixed then I will update it again.

Mark.
[Galaxy S III Original Android Development] fenstre:
Realistically, software changes without any visible or complete features/fixes. Somebody's committing to the CWM codebase, but we can't reasonably say it has new features until the devs have finished them, tested them, and released a build they believe is stable. A lot of bugfixes fix bugs nobody has even noticed (the developer just notices some bad behavior will occur in certain circumstances). Other code changes only make future changes easier. I looked at the changes and it looks like some thread-handling was a bit incorrect (I've never actually used linux threads, though). I especially liked this bit that got removed:

// wtf is this here for?
// don't fix threading problems with sleep.
usleep(1);
[Galaxy S III Original Android Development] kulica:
I'm getting device mismatch when I try to install MIUI v4 ROM, as it wants the device to identify itself as m0, but this recovery identifies it as galaxys3... It works fine on the CF- SGS3-CWM v1.5 recovery.

Any workarounds, solutions?
[Galaxy S III Original Android Development] fenstre:
Is your phone the i9300 or not? If your phone is the i9300 and some other script (miui installer?) wants your device to be something different, that's not CWM's problem, is it? Can you elaborate if you think there's a CWM issue?
[Galaxy S III Original Android Development] kulica:
My phone is GT-I9300, so I guess yes.

It's the issue of identifying the device... originally it identifies itself as 'm0', but with this CWM it's 'galaxys3' and I don't know why they really changed it. Of course the ROM has a pre-install script so idiots don't try to install it on other devices and that's where the issue occurs, "device mismatch".
[Galaxy S III Original Android Development] fenstre:
A post half way down this page makes me think a newer version of MIUI will work. Beyond that, you know as much as I do.
[Galaxy S III Original Android Development] kulica:
Yes, that's the issue, accept I didn't write it down.

Exact issue:

assert failed: getprop("ro.product.device") == "m0" || getprop("ro.build.device") == "m0" || getprop("ro.product.device") == "galaxys3" || getprop("ro.build.device") == "galaxys3" ||

E:error in /sdcard/miui.us_I9300_v4_2.8.3_eng_deo_zipa_signed.zip

(status 7)

installation aborted.
[Galaxy S III Original Android Development] gavin-phelan:
Is there no download for the latest

Sent from the third Galaxy
[Galaxy S III Original Android Development] mskip:
The latest version on the clockworkmod website is 6.0.1.2 which is where I get the files from.

Mark.
[Galaxy S III Original Android Development] fenstre:
I think you mean 6.0.1.2. But your point remains: there is no new version yet.
[Galaxy S III Original Android Development] gavin-phelan:
I have it on my gnex
[Galaxy S III Original Android Development] mskip:
Ohh yeah lol all fixed I dont think anyone will notice ;)

Mark.
[Galaxy S III Original Android Development] mskip:
This isnt a thread for the Galaxy Nexus though and the official GNex Touch version is only 6.0.1.0..

What versions are your Gnex and S3 Touch Recovery?

Mark.
[Galaxy S III Original Android Development] gavin-phelan:
Dont think you are reading the right stuff over on the gnex thread the latest is 6.0.1.2 its even on rom manager and have it on my gnex.. its ok i got it now
[Galaxy S III Original Android Development] Ostatni:
When i want backup my rom on sdcard the i see:

SD Card space free:.....

backing up boot image

backing uprecovery image

backing up system

backing up data

backing up .android_secure

Unable to find mounted volume: /sdcard

Error finding an appropriate backup handler

Then i go to mounts and stronage and i want mount sdcard I click on it and nothing happens. I got CWM touch 6.0.1.2 and i use OMEGA ROM v11.1+ siyah kernel 1.4. So it should be? What should I do? Some information is still needed?
[Galaxy S III Original Android Development] fenstre:
This recovery doesn't work if /sdcard/.android_secure exists. Don't know why. You could look inside that folder and if it contains no app data that looks important, delete it. Or you could temporarily rename it. (Make sure your file manager shows hidden files.)
[Galaxy S III Original Android Development] marioh:
I've changed my Samsung 32 gb Sd card for a Sandisk 64 gb sdxc extreme. This recovery is FANTASTIC, but can't mount my new sdxc.

For now, i reverted back to standard recovery.

Is there a way to fix?
[Galaxy S III Original Android Development] 9Lukas5:
format it to fat32 as filesystem ;)

L
[Galaxy S III Original Android Development] marioh:
Tryed, but in fat32 my phone says that sd is damaged and needs to be formatted. So it formats it in exFat.

Maybe that Jelly Bean works only in exFat?
[Galaxy S III Original Android Development] gsw5700:
Just found the nerve to use cwm touch as I was worried about wearing out buttons due to high level of flashing. So glad standard full tar backups are now available. Well, performed a backup to external sd, did full wipe, full restore, all working great. What a joy, no more button pressing, this is wicked

Sent via TCP/IP
[Galaxy S III Original Android Development] DirkStorck:
Hi. I have flashed the recovery but if I enter the recovery and want to access the external sdcard it tries to access "/mn/external_sd/"

Thanks!
[Galaxy S III Original Android Development] gboydroid:
love it. thanks!
[Galaxy S III Original Android Development] 9Lukas5:
where's the problem?

L
[Galaxy S III Original Android Development] DirkStorck:
The problem is, that there isn't a /mn/external_sd/ and I can't access it. If the phone is booted up the external sdcard is mounted as /mnt/extSdCard...
[Galaxy S III Original Android Development] alojo:
I think here is happening something like that. I can access the backups of the external card but there's some error when trying to restore system.
[Galaxy S III Original Android Development] Raghav_K:
works fine, thanks :)
[Galaxy S III Original Android Development] 9Lukas5:
How often it has to be said yet, until the question doesn't appear anymore?! -.-

The android os mounts the card under /mnt/extSdCard and shown under /extSdCard

if you're using cm10 it's mounted under /storage/sdcard1 and shown under /extSdCard

the recovery mounts the external sd under /mnt/external_sd, that has nothing to do with the functionality of the card.

If it gives you an error on mounting the sd, you haven't inserted one or the recovery can't read the card. The second option happens if the card isn't formatted to fat32 on the first partition, it won't accept ext, exfat or anything else than fat32.

L
[Galaxy S III Original Android Development] DirkStorck:
The ext sdcard can't be accesed...the first patition on my scard is extFat and the second is swap!
[Galaxy S III Original Android Development] Mopral:
Has been said many times in this thread: touch recovery does not support exFAT partitions!
[Galaxy S III Original Android Development] DirkStorck:
Maybe that should be highlighted on first post or in titel of the thread....that way nowone would have to ask and noeone would be confused why it doenst "work"...

I have seen that post http://xdaforums.com/showpost.php?p=30795815&postcount=565 and thought it works!

Any plans to support extFat in future?

Thanks!
[Galaxy S III Original Android Development] alojo:
Some backups that I did can't be restored.

It has problems when restoring SYSTEM.

It shows often this message:

E: unknown volume for path [/sd-ext]

My sdcard is used without problems by the recovery to create backups, but some of them cant be restored.
[Galaxy S III Original Android Development] freyria182:
I'm also having the same problem
[Galaxy S III Original Android Development] 9Lukas5:
There won't be exFat support as long as it isn't opensourced. Has been said many times yet.

L
[Galaxy S III Original Android Development] Schrotty35:
Whene come a update to Recovery 6.0.1.3 or 6.0.1.4?
[Galaxy S III Original Android Development] alchopop:
Why do you need it?
[Galaxy S III Original Android Development] gavin-phelan:
Version 2.0.1.3 has usb storage support

Sent from the third Galaxy
[Galaxy S III Original Android Development] tarekkkkk:
Is it possible to make the recovery password protected like when u boot to recovery a startup page asks for a pin/password or reboot system ?

Sent from my GT-I9300
[Galaxy S III Original Android Development] sgs9:
I like the .tar, in cwm I must change everytime again to tar or how i can Set to Standart?
[Galaxy S III Original Android Development] PhuocTri:
How to port this CWM to galaxy S III E210L ???

Or translate it into another language?
[Galaxy S III Original Android Development] khanguyen519:
thanks for the info on the new CWM. I've just nandroid and move the recovery to my extSD card and delete the original blobs folder(didnt expect it to have all my app data). so i've lost 1 month of good tweaking..
[Galaxy S III Original Android Development] TheWeasl:
any chance of getting a zip flashable trough recovery?! or can i flash it via mobile odin, too?

I am Weasel

- - - - - - - - - - -

and you've been SPANK'd by a S3
[Galaxy S III Original Android Development] andip71:
You can flash it via mobile odin. I always do it.

Select Recovery partition in mobile odin and choose the tar.

Thats it :)

Cheers

Andi
[Galaxy S III Original Android Development] TheWeasl:
just did it. and i gotta say: i like :thumbup:

and thanks andi

I am Weasel

- - - - - - - - - - -

and you've been SPANK'd by a S3
[Galaxy S III Original Android Development] bammert:
Is this working on XXDLIB?
[Galaxy S III Original Android Development] gboydroid:
Y not....hahaha yes it will work in any rom.
[Galaxy S III Original Android Development] gavin-phelan:
Its got nothing to do with roms so yes it will work
[Galaxy S III Original Android Development] Kremata:
error finding an appropriate backup handler

I'm trying to make a backup on external card, I get the error "Unable to find mounted volume" / "error finding an appropriate backup handler" . . but the card is mounted. it can go in the card and look at the files. I have a 64G FAT32 sandisk card.
[Galaxy S III Original Android Development] TheWeasl:
is there any chance to change the background of the recovery?! would like a picture of mine i have on the phone...
[Galaxy S III Original Android Development] iBuzman:
+1 Me too - 64gb fat32 SanDisk.
[Galaxy S III Original Android Development] Kremata:
Now it's doing the same thing with my 32G. Any idea?
[Galaxy S III Original Android Development] fenstre:
re: error finding an appropriate backup handler

This is a bug--I e-mailed koush a while ago, but he didn't respond. I don't know whether any of the devs are interested in fixing it.

This happens when the volume has a .android_secure directory present (it's hidden, btw). I deleted mine without any harm, but if you're nervous you can rename it to something else and test your phone before actually deleting it.
[Galaxy S III Original Android Development] Kremata:
ok I renamed the .Android_secure folder but now the backup doesn't backup the data. It's better than nothing but I flash a lot of ROM to test and restoring data is very important to me.

I don't think it is a Koush recovery problem because I tried to flash back Chainfire's 5.5 recovery and it does the same thing.

It start doing this after I flashed JB.

---------- Post added at 08:40 PM ---------- Previous post was at 08:27 PM ----------

I apologize to Koush, this should have been in the Q&A section. But I didn't know at the time
[Galaxy S III Original Android Development] fenstre:
Sounds like you have two separate problems. Tell us more about the new problem, maybe we can help.

Edit: I sound like a shrink.
[Galaxy S III Original Android Development] Kremata:
After doing like you said (I renamed .Android_secure) Now the backup complete with no error but it skip making a backup of the DATA. It backups system, boot, recovery then It says "sdcard/.Android_secure" not found, skipping data backup (or something like that).

Again: I used both 32 and 64G

I used Koush and Chainfire recovery(latest version)

Like I said it started doing this after I flashed Checkrom JB. But recovery have nothing to do with the ROM.

CheckRom v5.5

Siyah kernel 1.6 RC-1
[Galaxy S III Original Android Development] fenstre:
It says that for mine, too. I think it just means .android_secure isn't being backed up because it doesn't exist. If you want to verify that data is being backed up, do an easy test: make a backup. Create a note or make some other sort of data on your phone (not online). Then restore the backup and verify that the new data is gone: you've just proved your backups are working.
[Galaxy S III Original Android Development] Kremata:
Yep it restored data backup. Thanks
[Galaxy S III Original Android Development] DirkStorck:
So finally I have done the jump from CWM-v5.5-v1.5 to 6.0.1.2! :D

I have formated my ext sd card with fat32...

First the recovery couldn't mount the sd card but after I have formated again unsing the phones option everything is working fine now.

I can create my backups to ext sd card...:)

One question about ROM Manager...Is there a way to tell the app to make the backups to external sd card and not to the internal?

Thank you!
[Galaxy S III Original Android Development] donalgodon:
I'm a bit confused by how this recovery makes backups. I have two "clockwork mod" folders on my device now (one internal and one external) and each contains a "backup" and "blobs" folder. Inside the backup folders, there are dated folders containing about 16MB of data and the blobs contain (ostensibly) backup data in the range of about 1.5GB each.

If I revert to CWM 5.x will these backups be incompatible?
[Galaxy S III Original Android Development] Striatum_bdr:
No. This version uses incremental backup. When doing another backup of the same Rom only changes will be saved. It uses the blob format for that.

So incompatible with 5.x versions. You can set the backup format to use old system if you want retro-compatibility. See in backup menu.
[Galaxy S III Original Android Development] donalgodon:
I thought so, but the strange thing is that when I've reverted to 5.x in the past for compatibility reasons with some mods, etc. I was not able to delete the blobs folder, even using Root Explorer.

Any idea about that?
[Galaxy S III Original Android Development] Striatum_bdr:
I don't know I'm not used to this strange relationship between recovery/kernel/system. On my previous phone recovery was more separated and you didn't need to downgrade except for bug concerns.

And I can't see why you can't erase files that are not in system partition. Perhaps try another file explorer like solid beta or es file explorer.
[Galaxy S III Original Android Development] vatvedt:
I'm using 6.0.1.2 and it seems it's working as it should. Just wondering. The text "No sd-ext found... etc" is the old apps2sd? Since we're not using this (usually) on phones with a lot of space, this shouldn't be an issue. I'm wondering more about the "No /sdcard/.android_secure found.." error. When I went looking for the folder, I can't find it myself. Running CM10. The restore seems to work as it should, but shouldn't I have this folder somewhere? :)

Can't find it on internal or external SD. Is this folder only created when I move an app to SD? Don't think I've moved anything to SD on my SGS3.

Edit: I think I had this right.

sd-ext is the old Apps2SD/A2SD that I used on my old HTC Hero, and such phone with low internal space.

.android_secure is only created when an app is "moved to SD". And since SGS3 has alot of storage, I haven't had the need to move any apps to SD. Hence the directory has never been created. Correct me if I'm wrong. :)
[Galaxy S III Original Android Development] fenstre:
I don't think that's the only thing it's for, because on my old phone I never moved apps to SD but still had this directory. It contained data from the same 3-4 apps, even after I deleted the contents. (It was recreated.)

On the SGS3, I haven't experienced this--I deleted the old .android_secure folder, and it hasn't been created again, even though I have the same apps. In fact, you don't want this folder, because the 6.x series CWMs will fail to perform a backup if /sdcard/.android_secure exists.
[Galaxy S III Original Android Development] vatvedt:
Thanks. I'll give 6.0.1.2 a go and hope it works as it should. :)
[Galaxy S III Original Android Development] iBuzman:
Reformatted my sd in mini tool (used paragon partition magic last time) and now all works perfectly - thx, love being able to back up to sdcard :)
[Galaxy S III Original Android Development] kevinarjun:
I am also not able to delete it from phone..i guess as there is huge chunk of small files it is unable to calculate...I always delete the backup from pc...it taks around 30secs to delete via MTP..
[Galaxy S III Original Android Development] JJEgan:
No problem for me to delete blobs with Super Manager file explorer .

jje
[Galaxy S III Original Android Development] TheWeasl:
Selfquote FTW :D
[Galaxy S III Original Android Development] mskip:
You can't change the background image or colour in recovery mode.

Mark.
[Galaxy S III Original Android Development] donalgodon:
Why can't I delete the blobs folder on my external SD? I was able to delete the internal blobs folder via Root Explorer after mounting r/w, but I can't do the same on the external.

Any help would be appreciated, because I have a 1.5 GB blob folder there that won't die now.
[Galaxy S III Original Android Development] Jonnyredcorn:
I have just recently ran into a problem trying to restore nandroids. I was running omega v27 JB and since its not quite as polished I was gonna nandroid back to v13, however when I went to restore the backup which is stored on my 32gb card it would not give me my list of nandroids to restore from. Instead it just went to the page that says restore, even though I didn't pick a file to restore. I have not done anything different except run omega v27 for a bit. Any clue what's causing it?

Sent from my Tablet
[Galaxy S III Original Android Development] Northern-Loop:
Great tried to restore a backup from external SD card and all I get its can't restore /system /data
[Galaxy S III Original Android Development] 9Lukas5:
Why do people delete the blobs folder?
[Galaxy S III Original Android Development] donalgodon:
Because I reverted to 5.x

Have an answer?
[Galaxy S III Original Android Development] Northern-Loop:
So I have never deleted anything to do with my blobs folder.

Only do the delete through recovery but I have found if you you have 2 backups on your phone, delete the oldest one through recovery then the newest one will fail to restore.

GUTTED!
[Galaxy S III Original Android Development] donalgodon:
Exactly. One of the reasons I've reverted. There's just too many issues for me yet. I'd love to reclaim the space that is now allocated to the useless blobs folder on my external SD.
[Galaxy S III Original Android Development] Northern-Loop:
Yeah pointless having a V6 recovery if it doesnt do the RECOVERY bit! :cyclops:
[Galaxy S III Original Android Development] EViollet:
Hi.

I don't understand your problems with the blobs. They allow for much faster backups using far less space.

Using it old way is rather counter productive in my opinion especially when you've got LOTS of data to backup.

Why exactly do you think the blobs are useless?

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] Northern-Loop:
No issue with the blob folder but if you backup your rom then click free unused space it will fail to restore that rom again.

Also leaves the device in a non booting state.
[Galaxy S III Original Android Development] EViollet:
Strange.

Never had this issue. I clean up the blog folder quite regularly.

Then again maybe I've never done it in that order. I find it more natural to clean up unused backups before making a new backup, so everything is automatically cleaned.

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] donalgodon:
I don't mean this to sound disrespectful to the author. I'd just would like to have known that the external SD blobs folder could not be deleted before I tested it.
[Galaxy S III Original Android Development] EViollet:
Well, you're not supposed to delete it manually but just let the recovery manager it.

Regards

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] Northern-Loop:
If it does it automatically then why is the option in the list? I was seeing my Blob folder just getting bigger and bigger even though I would only keep 2 backups?
[Galaxy S III Original Android Development] donalgodon:
So, is there a way to delete it manually at all? I realize who it was SUPPOSED to work, but for me, it didn't, which is why I reverted to 5.x, so I'm sorta' stuck with a couple of GB of wasted space on my external SD.
[Galaxy S III Original Android Development] mikep99:
You should be able to delete it by flashing a script in recovery. PM me if needed so as not to go OT on this thread :)
[Galaxy S III Original Android Development] donalgodon:
PM sent.

Thanks.
[Galaxy S III Original Android Development] EViollet:
Did you select "restore from external sd card"?

You have 2 choices here which I find quite confusing. To me it should be configurable once and for all which drive we want to use for backups b restores/etc.

Be sure to choose the right option.

Regards

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] kandem:
I'm trying to make a nandroid backup but it's says an error. Anyone have link to normal no touch recovery? Thanks a lot

Enviado desde mi GT-I9300
[Galaxy S III Original Android Development] JJEgan:
In Android Development section or via the INDEX .

jje
[Galaxy S III Original Android Development] donalgodon:
Tried everything I can think of and nothing can kill the external SD blob folder. Is the ONLY option to either give up the GBs of data or reformat the SD?

Surely there must be a way to delete it. One user was kind enough to several iterations of a flashable script, but none of these worked.

I cannot be the only person here who's reverted back to 5.x and faced this problem. Maybe others haven't noticed that blobs won't die.
[Galaxy S III Original Android Development] EViollet:
Have you tried an adb shell?

cd /mnt/extSdCard/ClockworkMod
rm -rf blobs