yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] mskip:
Its not overly important as we have the microsd card to load files onto if needed and now extsdcard is supported in 6.0.1.0 the Recovery can actually be used as a recovery method if Android won't boot. Saying that, being able to mount storage and transfer files would be the icing on the cake lol :)

Mark.
[Galaxy S III Original Android Development] engas:
Hello,

It looks still have problem on 64GB SDXC. Mine still shows can't mount external_sd message.

Anybody have same problem?

Thank you!
[Galaxy S III Original Android Development] freyria182:
I'm using 32gb sd, so far no problem yet
[Galaxy S III Original Android Development] gaeng4665:
What does "Free Nand" exactly do?

Last time i pressed it with version 6.0.0.9. it deleted everything on my internal sd and wiped my rom...

I can imagine what it means, but please if someone can report who's tried it withe the new version.

Thanks
[Galaxy S III Original Android Development] temasek:
If u read a few posts before u.......

Its good. Both mskip & myself have tested and posted that its good - cwm 6.0.1.0 touch.
[Galaxy S III Original Android Development] earthworm1102:
Works great! Thanks! mskip i'm your no.69 on "Thanks".
[Galaxy S III Original Android Development] gaeng4665:
Thanks i read it. But i still don't know what it does?

Does it delete the fragments not needed anymore from old backups?

Thanks
[Galaxy S III Original Android Development] temasek:
Cwm 6.0.1.0 touch fixes the unintentional wiping of external sdcard. As for your question, see below post by koush.
[Galaxy S III Original Android Development] fenstre:
Koush, I'm concerned about one particular aspect of this whole thing. After the system was fouled, I flashed recoveries 5.8.4.3 and 6.0.0.8, both mostly stable versions. However, the system would not boot into recovery (I think it worked the first time using 'adb reboot recovery' but it was not happening with the volume+home+power buttons.) Nothing worked until I reflashed cf-root, which includes a cache image and a recovery image. At that point, I could boot into recovery. This happened to other people, as well. Wiping /sdcard and /system at least falls into the class of "ordinary bugs", but why would we also be unable to boot recovery after re-flashing it?

Do you understand what caused this, and is it fixed in 6.0.1.0? We may be at risk by making these new incremental backups if there could be a situation where borking the phone will result in a boot loop, with only a much earlier version of recovery (or a stock ROM installed with samsung software) being bootable.

A workaround that I didn't test but I think would work is flashing cf-root (which contains a cache and a recovery image), then immediately flashing recovery 6.0.1.0 on top of it. Seems like ClockworkMod just depends on a valid cache partition? Can you add anything to this situation?
[Galaxy S III Original Android Development] ::indie:::
Yes I have the same problem with 64GB SDXC.
[Galaxy S III Original Android Development] mehrzad1363:
mount external sdcard not working . (sdcard 4gb)
[Galaxy S III Original Android Development] schack:
Is the non touch 6.0.1.0 also safe to use?
[Galaxy S III Original Android Development] easycure1974:
Probably no support for exfat as it works fine with my fat32 formated 64 GB card

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Original Android Development] inffy:
6.0.1.0 working nicely.

One thing I noticed. I did a backup to the internal storage, and it went fine. Then I deleted the backup from recovery, was ok. But I noticed that the blobs folder on the internal storage (/sdcard/clockworkmod/blobs) didn't get erased...so should it get erased?

I did also backup to the external sdcard, worked fine. But now i indeed have two blob folders, one in internal storage and one on the external sdcard.
[Galaxy S III Original Android Development] Smiffyboots:
Can't mount or format external SD in recovery.

I have a 16GB class 10 by Transcend.

Do I need to format it in ntfs or something else before I put it into my phone?

Thanks
[Galaxy S III Original Android Development] mattiadj:
Extfat is not supported yet?

Inviato dal mio Transformer TF101 con Tapatalk 2
[Galaxy S III Original Android Development] 9Lukas5:
You have to go to backup and restore and select "free nandroid space" then cwm checks which blobs are needed to kept and which are deleted from you ;)

L
[Galaxy S III Original Android Development] ashok:
My San disk 64gb SD card formatted in exfat is not being recognized
[Galaxy S III Original Android Development] 9Lukas5:
format it to fat32.

exFAT is a Microsoft proprietary driver and so isn't recognized in cwm, cm9, cm10, ...

If you want to use exFAT formatted you have to use stock rom/stock based rom.

L
[Galaxy S III Original Android Development] gaeng4665:
I did a nanddroid bachup of cm9 yest night and tried cm10 . Today i tried to restore it and it gave me an error... used the latest touch recovery and backedup to infernal sd. Of course i backed up my cm10 rom.

In beetween i formated system.

Anyone else encountered similar issues?

Anyone tried backing up two different roms and then restored without any problem?
[Galaxy S III Original Android Development] 9Lukas5:
Yes, I had three different backups yet made with cwm 6 touch. Hadn't any problems so far with anything (also restore all three multiple times) I also tested the freeing nand space option and all was working fine, the blobs folder got smaller but all backups I left were completely intact. So, all is working fine with cwm 6.0.1.0 touch here ;)

L
[Galaxy S III Original Android Development] bedtime_with_the_bear:
Heads up guys, Titanium Backup has been updated and includes support for CWM 6 backups.
[Galaxy S III Original Android Development] Cristiano Matos:
External or internal memory?

I restore a cf-cwm cm9 with 6 touch. But when I try to do a new backup I receive a error in middle of the process.

Apparently the blobs are fine but the other folder have missing things such as md5 and ext4. I try to restore but "md5 miss match" won't let me.

I still with my cm10 made successfully in 6 touch.

Any idea?
[Galaxy S III Original Android Development] 9Lukas5:
Internal storage. And I haven't tried old backups. Only those made with cwm6. Maybe you go back to cwm5, restore the backup, flash cwm6 again and then make a new backup of the rom with cwm6?

L
[Galaxy S III Original Android Development] jonsmith709:
Thanks from a noob, all your instructions are easy to follow, I don't post a lot just read and take in bits, the last couple of days I have learned a lot and even recovered from a boot loop. So thanks again to you and all on XDA......

Cheers:good::o
[Galaxy S III Original Android Development] freyria182:
Weird thing happened.. I flashed to latest touch recovery this morning.. In the evening just now, i recalled I've flashed to nimphetamin kernel.. Just realized my cwm have changed to non touch.. How come this happened?
[Galaxy S III Original Android Development] ctrlaltdel:
can we use mobile odin to flash this?
[Galaxy S III Original Android Development] IamIrene:
yes can

just choose open file or recovery in the mobile odin
[Galaxy S III Original Android Development] fenstre:
If you use Mobile Odin to flash this, ROM Manager won't realize you've updated your recovery and it will nag you. I may end up using ROM Manager to re-flash just so it stops nagging me.
[Galaxy S III Original Android Development] 9Lukas5:
flash nontouch with rommanger and then touch one with mobileOdin :D

L
[Galaxy S III Original Android Development] Neophite31:
work perfect!!thanks!!
[Galaxy S III Original Android Development] mariotme:
Guys please ignore my ignorance but i would like to ask of its safe to rename the backups folders with names instead of date/time?
[Galaxy S III Original Android Development] unfnknblvbl:
No. Touch nothing in the /clockworkmod/ folder. At all ever.

Unless you're deleting backups, but only then. Never. Ever. Rename anything.
[Galaxy S III Original Android Development] seriouser:
I've installed at least 3 different recoveries with Odin and Heimdall and none of them have stuck, I still have the 3e one when I boot to recovery. The counter in Download-mode has increased though.

Does anybody have any idea why this is happening? I've never had this kind of problem on my previous phones.
[Galaxy S III Original Android Development] mariotme:
Thanks bro :good:

happened to me once. I flashed CF Root first then rebooted and managed to re-flash CWM touch
[Galaxy S III Original Android Development] 9Lukas5:
Yes, you can rename the backup folders to names, but make sure that you don't put any spaces in the name, use "-" or "_" for that instead.

Why shouldn't we change the names from the backups? How should we know then what's in which backup??

L
[Galaxy S III Original Android Development] Smiffyboots:
Well... After a lot of playing around, my solution was simple! Everything is working fine and I can see and install from my external SD card in recovery :)

For the people getting the error can't mount external SD in their recovery, try formatting your external SD card in the phone by going to Settings / Storage / Format SD card, it's right at the bottom of the list. Just make sure you backup your SD card first.

I'm new to Samsung, I could always format cards for my HTC in windows. Oh well noob school boy error, glad this brilliant recovery is now seeing my external memory =)
[Galaxy S III Original Android Development] schack:
How do you make ROM Manager prefer external CD card for backups ?

My option is greyed out

/Henrik Schack
[Galaxy S III Original Android Development] aelael:
how to install via fastboot

it is possible to install the 6.0.1.0 without Odin? fastboot?
[Galaxy S III Original Android Development] inffy:
I think Rom Manager doesn't support backing up to a external sdcard...atleast not yet.
[Galaxy S III Original Android Development] brian6685:
I always change the names in my backups, never a problem
[Galaxy S III Original Android Development] ATN24:
u will get md5 error mismatch during the restore.

The easiest solution is to rename during the process of the backup before you validate it :)
[Galaxy S III Original Android Development] mariotme:
I just renamed 2 of my backups and i managed to restore them both with zero issues :P
[Galaxy S III Original Android Development] fenstre:
Huh? I rename my backups every time and have never had that problem (unless there was an error during the backup). And what do you mean about validating? How would you rename your backup before finishing the backup process? In other words, what are you talking about?
[Galaxy S III Original Android Development] 9Lukas5:
hahahahahahahahahahahahahahahahaha

sooooryyy man, I had that also once, but the fix was as easy as stupid my fault was. If anywhere in the name of the backup folder is a space, it will give you a md5 mismatch. I also have once lost the md5 file in the backup folder and used a md5 hash generator to get the md5 hashes of the backed up files and used the md5 from another backup with the just read hashes and it worked fine.

So, simply don't do any spaces into your folder name and all is well :D

L
[Galaxy S III Original Android Development] ATN24:
That's what I was always doing first but when u'll get this error, it pisses u off lol and if its working for u, lucky u then :)

So when u're in CWM app, u click on create a new backup, and now u rename ur backup and validate :)

---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------

lol yeah but my backups never had a space or etc ;)

anyway, from now on, i do not rename my backups and problem solved ;)
[Galaxy S III Original Android Development] 9Lukas5:
Ok, surely everone can make like he/she wants ;)

L
[Galaxy S III Original Android Development] freyria182:
Same thing happened again. Suddenly my touch recovery changed back to non touch.
[Galaxy S III Original Android Development] kamaliqwan:
is it working with cf-cwm?
[Galaxy S III Original Android Development] 9Lukas5:
If it is always flashing a specific file, maybe you should check that zip, if it installs a recovery.img? It happend a few days ago to me too, installed a rom and after that, had cf cwm v1.5 again, checked the zip file and found a recovery.img that is being flashed. ;)

L
[Galaxy S III Original Android Development] brian6685:
So restore is ridiculously fast, when it works. Some of the time it can't restore system... also, the backup is fast, when it starts to backup. It takes like 15 minutes to free space when I back anything up, anyone else have this happen?
[Galaxy S III Original Android Development] 9Lukas5:
no, for me backup didn't last over 5min anytime with cwm6. I would say it's even less than 5min. Also restore is that fast. And with freeing space I, also, hadn't any problems yet. CWM 6.0.1.0 touch.

L
[Galaxy S III Original Android Development] mariotme:
9Lukas5 i would like to ask when i delete a backup would the blobs be deleted automaticly?
[Galaxy S III Original Android Development] brian6685:
Are you restoring to internal or external? Maybe its because I'm using external?
[Galaxy S III Original Android Development] inffy:
You have to use thr free nandroid space option in recovery.
[Galaxy S III Original Android Development] fenstre:
He could make "Delete backup" and "Delete backup (fast)" operations, which would and would not do the garbage collection. Because logically, garbage collection is part of backup deletion (so I bet he'll eventually add this).
[Galaxy S III Original Android Development] 9Lukas5:
ah, not quite right, as I have seen, if I delete a backup it simply deletes the backup folder, but deleting the corresponding blob files get's done if you make a backup, then it says freeing space before starting to backup.

As infra said, if you want the memory to be cleaned directly, you have to go to backup and restore/freeing nandroid. If you don't care at that moment because you have enought free space, it will be done automaticially before the next backup operation starts. If you take a look at it, you'll see that it says freeing space before starting to backup anything ;)

I'm backup up and restoring to internal sdcard, because I haven't a external one yet. I should get a 64GB sdxc class 10 one on thursday coming week. But I'll furhter on using the internal one for backups, roms, etc. and the external one will be used for pictures (maybe, not sure abt this yet), media files like music, videos, etc.

L
[Galaxy S III Original Android Development] fenstre:
Sigh. It's no longer working:

Unable to find mounted volume: /sdcard
Error finding an appropriate backup handler.

6.0.1.0 touch here. Was working until I used ROM Manager to flash 6.0.1.0 non-touch then flashed 6.0.1.0-touch again.
[Galaxy S III Original Android Development] earthworm1102:
I made a backup using latest 6.0.1.0 on my internal SD card. When i checked the file on CWM , the file was only 16.6 MB. Is that normal? When i used the older version (5.8.4.3) to backup it consumed 1.2 GB of space. Does anybody had the same result as i did?
[Galaxy S III Original Android Development] mskip:
I will clarify this in more detail tonight but im not at my pc now so will have to keep it short. Basically on the new cwm all the data is stored in a blob folder in the clockworkmod folder. The backups folder now doesnt hold the actual data and instead the system and data files contain links to the files in the blob folder. When you perform another backup only the changes have to be added so it performs incremental backups instead of full backups everytime. You can still flash different roms and back them up as any new data is stored in the blobs folder with the links in the backup folder. When you delete a backup via cwm you can then free space of the blob files that are no longer needed to keep everything tidy and make sure that no files are stored that arent referenced to any backup.

Ok I guess that wasnt a short answer lol.

Mark.
[Galaxy S III Original Android Development] earthworm1102:
Gotcha mskip, i mean Mark!!! Thanks!
[Galaxy S III Original Android Development] edwardob:
i cant get ClockworkMod Touch Recovery 6.0.1.0 to install

getting stuck on endless boot
[Galaxy S III Original Android Development] Kurai Kitsune:
That sounds amazing. Gonna give it a try :)
[Galaxy S III Original Android Development] Yusei:
Backup and restore working great here... really cool this cwm.
[Galaxy S III Original Android Development] GabrielSousa:
mount sdcard or ext dont work for me :(
[Galaxy S III Original Android Development] Smiffyboots:
Try formatting your SD card in your phone. Settings / Storage / Format SD card.

Make sure you backup your SD card first though.
[Galaxy S III Original Android Development] GabrielSousa:
with any rom mounts good...

it will work ???
[Galaxy S III Original Android Development] morg01:
Tried this and had an error whilst trying to back up to external sd card, basically got part way through and recovery stopped saying could not back up data, gonna post a log via rom manager.

Sent via courier pigeon
[Galaxy S III Original Android Development] baste07:
Seemd not stable enough to replace the non touch cwm
[Galaxy S III Original Android Development] kimycai:
can u tell me how to pack the img file into a tar file that can be flashed over CWM in Windows 7 ?
[Galaxy S III Original Android Development] TheSmokingAndroid:
Me too!In fact, i haven't been able to get my sdcard or ext card to mount since i flashed cwm...thats why i came here, lol.

Gonna try this and see if it fixes the problem right now. I'll report back if it fixed it.:o
[Galaxy S III Original Android Development] freyria182:
Hi, can I know how to check on this?
[Galaxy S III Original Android Development] 9Lukas5:
Very simple, open the zip and have a look if there is a recovery.img in it ;)

L
[Galaxy S III Original Android Development] 9Lukas5:
As I know the mount option under mounts and storage isn't doing anything for now, but flashing, restoring, backup etc. is working well

L
[Galaxy S III Original Android Development] TheSmokingAndroid:
Quote:

Originally Posted by vladnosferatu

mount sdcard or ext dont work for me

Me too!In fact, i haven't been able to get my sdcard or ext card to mount since i flashed cwm...thats why i came here, lol.

Quote:

Originally Posted by Smiffyboots

Try formatting your SD card in your phone. Settings / Storage / Format SD card.

Make sure you backup your SD card first though.

Gonna try this and see if it fixes the problem right now. I'll report back if it fixed it.

Tried, didn't work. Recovery still wont allow me to mount either internal or external storage when selected in mounts and storage.:eek:
[Galaxy S III Original Android Development] Smiffyboots:
I can only say that it fix it for me. Perhaps it would be a good idea to state card size and makes. Maybe there's a certain type of card that's incompatible with cwm.
[Galaxy S III Original Android Development] BritSwedeGuy:
Mirror?

Could someone please set up another download site - I just get errors from Mediafire.
[Galaxy S III Original Android Development] mskip:
Mirror to dev-host in first post.

Mark.
[Galaxy S III Original Android Development] ketan_naik:
Can U upload CWM base zip file?
[Galaxy S III Original Android Development] mskip:
What zip file?

I dont have cwm 6.0.1.0 in a flashable zip format just flash it via Odin. If you can't then I may make one later.

Mark.
[Galaxy S III Original Android Development] fenstre:
what could be the matter with this version?

I posted this a couple pages back, but got no response. Does this error look familiar to anyone? It looks like it's trying to mount /sdcard at the end of the backup and failing (it should fail, because /sdcard is a symlink to /data/media). It's an internal backup.

Pastebin recovery log: http://pastebin.com/33yeNusu
[Galaxy S III Original Android Development] Mcign:
The only bug i find is when i try to flash domination theme

With touch dont work , and work perfect with normal cwm
[Galaxy S III Original Android Development] Sirklip:
Morning

Many Thanks for all the work that have been put into this up to date recovery

I have encountered an issue an was hoping someone can help

I have successfully loaded V6.0.1.0 using mobile odin but when ever i boot into recovery touch control does not work

The hardware buttons still work and allow me to browse around but no touch control

Any help would be greatly appreciated.

I am currently running CM9 RC2 with Siyah Kernel 1.38
[Galaxy S III Original Android Development] FadeFx:
Try flashing with mobile odin

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S III Original Android Development] Vap0ur:
I flashed the 6.0.1.0 via Odin and it works fine. I then flashed it again from ROM Manager as it was bugging me that it couldn't detect the recovery.

However, I now can't use Mobile Odin as i get a message saying "Could not locate Mobile ODIN package."

I did search and I'm not sure what the solution is. Based on that post above, I might try flashing the non touch version, but does anyone have a link for that?

Thanks.
[Galaxy S III Original Android Development] inffy:
Mobile Odin doesn't work here either...runnin cm10 preview
[Galaxy S III Original Android Development] Vap0ur:
Infra... Is it a vanilla 6.0.1.0 install via Odin, or did you reinstall the recovery from ROM Manager at all?
[Galaxy S III Original Android Development] 9Lukas5:
Only a question, but have you also installed the correct odin flashkernel.apk? You know you need the app and the flashkernel addon to use MobileOdin.

L
[Galaxy S III Original Android Development] Vap0ur:
Yeah. In theory the Pro version grabs the right flash kernel itself. I downloaded it anyway and installed it, with the same result.

I might try swapping to the light version to see if the same thing happens.
[Galaxy S III Original Android Development] Vap0ur:
Oddly, I've just installed the Lite version from the forum thread (as mentioned above I already installed the flash kernel for the S3), and now Mobile Odinn works fine (it did request SU permissions again). I installed pro on top and that also works. (the lite link now launches the Pro version).

If I then remove the lite one, the Pro one breaks again!
[Galaxy S III Original Android Development] Mopral:
No issue here: I flashed Touch 6.0.1.0 from this thread and Mobile Odin Pro still works
[Galaxy S III Original Android Development] inffy:
I flashed the recovery from rom manager.
[Galaxy S III Original Android Development] Vap0ur:
Have you tried now flashing the recovery again from ROM Manager?

EDIT: Sorry, that was @Mopral. Thanks for feedback Infra. It looks like the flash from ROM Manager might be a common 'theme'.
[Galaxy S III Original Android Development] fenstre:
Well for me, flashing within ROM Manager was certainly the first thing that broke it. I wonder how I could possibly get my recovery back to the state it was a few days ago? I really want to use the new space-saving features, but every time I try installing a new version of clockworkmod I have to go back to CF-root to be able to make any backups at all :(
[Galaxy S III Original Android Development] RMXO:
Great work, OP! I noticed doing a nandroid is much faster.
[Galaxy S III Original Android Development] Vap0ur:
Ok. I think the best bet is just doing a flash from desktop Odin then leaving ROM Manager alone. Of course that means that ROM Manager is unlikely to work as it won't detect recovery... But I'll try it anyway.
[Galaxy S III Original Android Development] morg01:
Update :

Wanted to flash new rom so decided to give touch recovery another go before reverting back to cf recovery, anyway I success!

Backed up to external sd card with no errors, took bloody ages, although looking at the card on the pc its not surprising it took that long, 8.5 GB is that normal?

Sent via courier pigeon
[Galaxy S III Original Android Development] fenstre:
No, it's not. My backups were 2.7G with the stock system and a bunch of programs and 1.5G with cyanogenmod9 and a bunch of programs. Do you have sixteen 3D games installed?