yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] fenstre:
I found the (a) problem: bug in handling .android_secure

I was only able to make one successful backup with 6.0.1.0 before it stopped working. Today, determined to get to the root of the problem, I renamed everything on my internal storage. Lo and behold, whenever the folder /sdcard/.android_secure/ existed, the backup failed. When the folder is deleted, the backup works fine.

I'm a little uncomfortable with this because I thought .android_secure was important for the operation of many programs. However, I rebooted and opened several programs but nothing recreated that directory.

For the record, the error I had been experiencing was something about being unable to mount sdcard and unable to find appropriate backup handler when the backup should have been finished.

Edit: I see freebordjunky has discovered the same thing as me. This recovery chokes on .android_secure every time!
[Galaxy S III Original Android Development] jutley:
I am having problems stock latest jellybean trying to install this recovery when i flash it it just loads up android system recovery 3a stock recovery am i doing something wrong i am not rooted or unlocked any bootloaders pure stock international galaxy s3 latest jellybean.
[Galaxy S III Original Android Development] Cristiano Matos:
Did you try to backup via Rom manager app or recovery?

This happens with me when I try to backup using rom manager app.

Backup in recovery (external SD) works great for me.
[Galaxy S III Original Android Development] Pyr0x64:
I was troubleshooting this with koush the other day...

CWM is looking on the internal SD for the .salted_hash file, but ROM manager is putting the file on the external.

he did give me a new build of RM to try, which semi worked but was putting the backup on the internal instead of the external.

hopefully we should see a new build soon as he told me he had an idea what was wrong now.
[Galaxy S III Original Android Development] TecQuality:
Yes i got issues using rom manager apk :)

Glad to hear this mate, i sent my logs to koush today, i got a very similar issue with an older cwm, but it was fixed with the standard 6.0.1.0, now i've the issue again with the touch recovery. :p
[Galaxy S III Original Android Development] Htc_One_X:
Does this include rot or will i have to root separately?
[Galaxy S III Original Android Development] mskip:
You will have to rot seperately ;)

Mark.
[Galaxy S III Original Android Development] Htc_One_X:
Ha ha ha i only just noticed my mispelt "root", I'm off to root now :0) ( Don't buy ACER laptops keyboards are rubbish )
[Galaxy S III Original Android Development] TecQuality:
Koush just released 5.0.1.1 rom manager, everything's working now :)
[Galaxy S III Original Android Development] baste07:
i checked sd card, where can i find it?
[Galaxy S III Original Android Development] temasek:
Extract from tweet.

May have fixed the issues with ROM Manager on SGS3/CM10. Please test: http://t.co/s0ZznuvR -- ClockworkMod (@clockworkmod)
[Galaxy S III Original Android Development] sgs9:
it is in the folder named "clockworkmod" in your internal or external sdcard.

maybe /mnt/extSdCard/clockworkmod

otherwise it was write error and file is to small.
[Galaxy S III Original Android Development] baste07:
thanks! saw it,

will backups from cwm work with this?
[Galaxy S III Original Android Development] Pyr0x64:
anybody else loose the option in ROM manager settings to use the external SD?
[Galaxy S III Original Android Development] Cristiano Matos:
Yes.
[Galaxy S III Original Android Development] temasek:
It is always greyed off for me, no matter what RM including latest.
[Galaxy S III Original Android Development] sgs9:
sure :)
[Galaxy S III Original Android Development] Cristiano Matos:
Two or tree days ago this option was available for me. Now isn't more.
[Galaxy S III Original Android Development] Pyr0x64:
For me the external sd option is selectable when running 5.0.0.9 or the 5.0.1.0 build i was given for testing, but greyed out in build 5.0.1.1

if i downgrade then the option is available again
[Galaxy S III Original Android Development] hectorcore:
Noob question, ClockworkMod Touch 6.0.1.0 is compatible with Rom Manager 5.0.1.1 ?
[Galaxy S III Original Android Development] TecQuality:
yes :)

10chars

---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------

yes, know that option is gray :mad:
[Galaxy S III Original Android Development] crawrj:
Has the default backup date issue been resolved? Where it would show 1970.
[Galaxy S III Original Android Development] :
I got my recovery working again that got stuck on android_secure I flashed the recovery from the CF root thread that's the only recovery that works for me right now

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] 78cortina:
I want to rename backups but rom manager always asks me to install recovery the last time I did it buggered up recovery, I am running touch ver 6.

How do I rename without rom manager?
[Galaxy S III Original Android Development] jb_alphamale:
Same here.
[Galaxy S III Original Android Development] :
HERE: http://download.chainfire.eu/195/CF-Root/SGS3/CF-SGS3-CWM-v5.5-v1.5.zip

this is the only working recovery that i found at the moment after havein these problems!

extract it and flash the .tar with odin or mobile odin!
[Galaxy S III Original Android Development] oyam:
How do I make this compatible with ROM Manager application

I have flashed this using mobile odin, now when i try to use ROM Manager its not recognizing the recovery, event tried to flash the non-touch through ROM Manager and flashed the touch recovery again using mobile odin.

Anybody successful in making this touch recovery compatible with ROM Manager?
[Galaxy S III Original Android Development] fenstre:
Based on the responses in this thread, it works for almost everybody without needing to jump through any hoops. If ROM Manager isn't recognizing the recovery, I would try clearing ROM Manager's data, and deleting the hidden files in your recovery folder:

adb shell 'rm /sdcard/clockworkmod/.*'

Then try again. And as I've experienced, if the folder /sdcard/.android_secure exists, the backup won't work.
[Galaxy S III Original Android Development] andreasy:
Is this modified version from official 6.0.1.0?

I rooted my SGS3 with Toolkit v4 which installed CWM recovery 6.0.1.0. Then I installed ROM manager to manage newer recoveries but when I clicked on install recovery it froze. After 2-3 attempts and after 1-2 times asking SU permissions it finished and I still have the same recovery.

They say that ROM manager may harm SGS3 but later I read that both ROM manager and newest recovery are now safe. Is it true? Should I use it or uninstall it and is this recovery compatible with this phone? Maybe when I installed from ROM manager it replaced the one that the toolkit installed or are they the same?
[Galaxy S III Original Android Development] Stevemann:
Backup error to exFAT 64GB SD card with v6010

Just tried v6.0.1.0 Touch CWM to backup my S3. I can boot to CWM Recovery touch screen and can select backup to external sd_card ok. But the opeartion fails:

failed to mount /dev/block/mmcblk1p1 (Invalid argument)

Can't mount backup path.

W:failed to mount /dev/block/mmcblk1p1 (Invalid argument)

Error mounting /external_sd!

W:failed to mount /dev/block/mmcblk1p1 (Invalid argument)

Error mounting /external_sd!

So still not supporting exFAT then.

But it does work fine to the Int_SDcard mount point. And the Blobs folders total 1.36GB with the Backup folder as 16.9MB. Copied to laptop for safekeeping.
[Galaxy S III Original Android Development] Mopral:
And it will probably never support it!

Do not forget that exFAT is a proprietary filesystem
[Galaxy S III Original Android Development] andreasy:
/dev/block/mmcblk1p1 is the external sd card and as you said, it can't mount because is exFAT. But it works fine with FAT32.

Why do you use exFAT for your sdcard? I think you will encounter incompatibilities in other areas as well.

CF CWM supports your exFAT without issues?
[Galaxy S III Original Android Development] krazykat:
Speedmod might be your solution. =)
[Galaxy S III Original Android Development] nicesoni_ash:
Can you work on latest touch version... v6.0.1.1 is already released by the developer.. Can you make a zip or tar to be flashed, it's only available in .img format.. or tell me how to flash it using adb scripts or some way to flash it.

Thanks.
[Galaxy S III Original Android Development] MadMatt89:
I'm missing the create .zip funktion. Isnt it already implemented?

cheers
[Galaxy S III Original Android Development] Mopral:
I use Siyah so no need for an exFAT solution!

But even with a kernel that support exFAT, CWM still does not work with exFAT partitions...

It was like that when I tried about a week ago and I don't think an update occured on this point but I may be wrong
[Galaxy S III Original Android Development] alojo:
I'm using Fat32 and can't use neither external SD for my backups!!

With this one: recovery-cf-cwm-i9300-1.5-gsm.tar I use external SD without problem
[Galaxy S III Original Android Development] Mopral:
I also use FAT32 on my external SD and backup works with CWM Touch 6.0.1.0 from this thread
[Galaxy S III Original Android Development] mskip:
Have you tried formatting the sd card via cwm recovery?

Mark.
[Galaxy S III Original Android Development] nicesoni_ash:
I think latest v6.0.1.1 supports that..
[Galaxy S III Original Android Development] LightSwitchTTM:
RECOVERY BOOTING... then black screen

I've flashed CWM twice on my SGSIII and I'm getting the same result. I boot my phone into Recovery mode, I see "RECOVERY BOOTING" very quickly, then the screen goes black, until I reboot it. I'm on ATT and it's the 16GB model, stock ICS. I've checked this thread and the one other post with a similar or identical issue wasn't answered. Any help is appreciated, thanks.
[Galaxy S III Original Android Development] fenstre:
This thread is for the international I9300--I don't think this version of recovery is supposed to work on the US variants of the phone.
[Galaxy S III Original Android Development] mskip:
As stated above this version is for the i9300 International version ONLY. You need the ATT version which you can flash via the S3 Snapdragon ToolKit.

Mark.
[Galaxy S III Original Android Development] Mone181:
Hi,

flashing it via MobileOdin Pro will not increase my counter, is it right?
[Galaxy S III Original Android Development] alojo:
Yes, that's what I did. Via "no touch" recovery, because "touch recovery" doesn't mount it. No results.

The toolkit can't use neither external SD, but using internal I can backup.

Thanks for your time

Edit: today it works fine (till now didn't). Still have to try The Toolkit.
[Galaxy S III Original Android Development] mskip:
Wierd.. but glad it started working lol.

Mark.
[Galaxy S III Original Android Development] andreasy:
Your counter already increased by flashing a custom rom. You can reset it using the triangle app if you need to claim waranty.
[Galaxy S III Original Android Development] toqpuk:
Who knows when we will able use 64GB exFat in Recovery?
[Galaxy S III Original Android Development] mskip:
As far as I know exFat is licensed to Microsoft so I dont know if that will ever be available but you would have to ask koush.

Mark.
[Galaxy S III Original Android Development] Mone181:
no My counter is 0 thanks to triangle app, But if i flash this with mobile odin My counter Will add 1 more or remain at 0?
[Galaxy S III Original Android Development] redcore2k:
regarding to chainfire it will remain at 0.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] micmaccc:
guys, just to inform that touch recovery not working with exfat, but cf recovery does work with exfat :thumbup:

Sent from my GT-I9300
[Galaxy S III Original Android Development] mskip:
Flashing via custom recovery or Mobile Odin will not increase your flash counter.

Mark.
[Galaxy S III Original Android Development] LightSwitchTTM:
Well this is embarrassing.

Thanks for the help regardless.
[Galaxy S III Original Android Development] 9Lukas5:
Has anyone a problem with the latest rommanger 5.0.1.3? I think it happened since I updated rommanger, that on my sdcard root a .nomedia file appeared and also after deleting it and rebooting no musicplayer was able to find any files.

L
[Galaxy S III Original Android Development] Pyr0x64:
First thing I checked was that the new Rom Manager 5.0.1.3 has the external storage option available again :)

[edit] but it doesn't work :(

I enabled the option in RM and ran a backup, phone rebooted and proceeded to create a backup on the internal sd. :rolleyes:

If the option is left disabled, the backup fails as Rom Manager is trying to use /emmc while CWM is using /sdcard

.nomedia files are used to stop the media scanner from scanning whatever folders they are placed in.

useful to prevent music players from having sound effect files from games etc. listed.

after installing the new rom manager 5.0.1.3 i can see a .nomedia file in the root of my internal sdcard as well.

i keep all my music on my extsdcard though, so it has not affected my music player.

[edit2]

The new Rom Manager is failing to install zip files as well as it still tries to tell CWM to install from /emmc

[edit3] looks like Rom Manager 5.0.1.4 is still broken for the GS3

[edit4] Rom Manager 5.0.1.5 can backup to internal sdcard, but the RM option to use external is greyed out again
[Galaxy S III Original Android Development] toqpuk:
But license for exFat does not affect operations in OS, problem only in Recovery/ :confused:
[Galaxy S III Original Android Development] bedtime_with_the_bear:
That's because those kernels and ROMs based on Samsung ROMs are using the drivers already licensed for exFAT, but the recovery isn't which is why they don't usually support exFAT.
[Galaxy S III Original Android Development] GREGHARKINS:
Nandroid errors

I use EZRecovery which has 6.0.1.0 built into it on my Galaxy s3

when i run the nandroid back up i get this

Backing up boot image...

Backing up recovery image...

Backing up system...

Backung up data...

No /sdcard/.android_secure found. Skipping backup of applications on external storage.

Backing up cache...

No sd-ext found. Skipping backup of sd-ext.

Generating md5 sum...

Backup complete!

it makes a directory and puts what i would assume is a back up but it dates everything

dec 31 1979

the clockworkmod folder and the files inside

then when i run restore it says no files are found

so.. i know its not working and i have no idea how to fix it

i am running senergy rom with no special kernals.
[Galaxy S III Original Android Development] gavin-phelan:
Were did you get ez recovery
[Galaxy S III Original Android Development] MadMatt89:
ah okay but this version isn't release for i9300 yet, right?
[Galaxy S III Original Android Development] earthworm1102:
Actually i ahve the same problem. It says it is backed up but when i restore, it says"no files found". but if you check it has backup and blobs folder. But when you tick on it(Backup folder), it doesn't read it therefore no restore is made. Can anybody tell us noobs using touch recovey how to do this?? Thanks!!
[Galaxy S III Original Android Development] PC400:
I have problem...

I installed JB by Nandroid backup, after, i installed CF-Root by Odin 3.4, now, i don't can access recovery mode, only, i see "manual mode" and i don't can flash recovery 6.0 touch, don't install here... i want go back to Cwm 5.5, but i don't can. "manual mode" i don't have acess to "restore/backup " nandroid, help-me!

Thanks a lot!
[Galaxy S III Original Android Development] fenstre:
You can force the phone to boot into recovery by holding the Volume Up key + Home button + Power button simultaneously for a several seconds. This should reboot your phone into recovery mode. Or you use ROM Manager or CWM Manager, which would probably work if you used them to reboot the phone to recovery mode.
[Galaxy S III Original Android Development] GREGHARKINS:
I got ez recovery from the play store

It is recommended in about all the forums here
[Galaxy S III Original Android Development] aydc:
6.0.1.2 seems to be out:

https://github.com/CyanogenMod/andr...mmit/c01469cd4ebbb9eef2e88f55c9d5510ade4a78f2
[Galaxy S III Original Android Development] gavin-phelan:
Its not for the international gs3 omly verizon and other American s3's
[Galaxy S III Original Android Development] 9Lukas5:
We have cwm6, and the 6.0.1.0 as version comes only as we had a few releases until it was fully working. I don't think there is a new version until there is anything new or anything to be fixed. Please, if you want to tell us about a new version out in tbe future, go to clockworkmod.com/rommanager, scrl down to gt-i9300 and check if there is a newer version listed than the 6.0.1.0. Anything else is only confusing the noobs here. Thanks

L
[Galaxy S III Original Android Development] Theshawty:
Cwm 6 doesn't even work for me. Cannot install stuff from my sdcard. Kinda sucks a bit that the Cwm in cf-root isn't touch.
[Galaxy S III Original Android Development] Manar Aleryani:
Guys, can someone help me? I need an answer to my questions.

I have an older version of CWM recovery (5.5.0.4) using CF method.

It's working fine but I can't mount or install anything from External SD card.

Does anyone have an idea if I can still flash this recovery? Or will I have to revert to the stock recovery before being able to flash this recovery?

Will older backups I made with the old CWM be restored using the new CWM?
[Galaxy S III Original Android Development] 9Lukas5:
You can directly upgrade to cwm6 via rommanager and then flash the touch recovery with mobile Odin (that rommanager knows that you have installed it).

Old backups are working fine as reported a few times yet.

If the external sd has fat32 as filesystem it should work with both, internal and external.

L
[Galaxy S III Original Android Development] asphaltkiller:
I have installed the TAR provided in OP, i m now on recovery 6.0.1.0 but there s no touch at all i have to use vol up down and menu button!!!!!!

why?
[Galaxy S III Original Android Development] JohnCorleone:
I just got 6.0.1.2 when updating through ROM Manager

Sent from my GT-I9300 using Xparent SkyBlue Tapatalk 2
[Galaxy S III Original Android Development] schack:
Hmm still no use external storage option :(
[Galaxy S III Original Android Development] Northern-Loop:
Only reason I updated as well, wanted to see the EXTERNAL STORAGE option in ROM Manager :(

Shame I can't tick it!
[Galaxy S III Original Android Development] mskip:
UPDATED CWM TOUCH RECOVERY IN OP TO 6.0.1.2

NOTE: VERY NICE addition to 6.0.1.2 is the ability to 'choose backup format' to either the new .dup method with the blobs folder or the original .tar method where everything is in the date/time stamped folder. You can now ALSO 'create image zip' file from a NAND backup. Be patient with the zip backup option as it does take a while to create the zip (to be expected from a 1GB+ backup). Thank you for this addition koush it makes recovery alot more complete :)

All credit to koush and the clockworkmod team for the recovery. I just created the tar to flash via Odin or Mobile Odin.

Mark.
[Galaxy S III Original Android Development] asphaltkiller:
Many thanks I have just installed it.

Could you explained me why it's not touch controlled at all?

thanks
[Galaxy S III Original Android Development] baste07:
great! this is fully compatible with backup from cf recovery 5.5.0.4 right?
[Galaxy S III Original Android Development] sarbe:
Touch control works fine here.
[Galaxy S III Original Android Development] asphaltkiller:
for me the layout is different from normal recovery aka larger lines etc but moving my fingers on the screen have no effect...
[Galaxy S III Original Android Development] mskip:
It definitely says 6.0.1.2 at the top of the recovery menu?

Mark.
[Galaxy S III Original Android Development] mskip:
I have tried restoring backups made on the 'old' backup format and they restore fine.

Mark.
[Galaxy S III Original Android Development] baste07:
Thanks mate

Just flashed touch recovery
[Galaxy S III Original Android Development] micmaccc:
just to inform this version still not support exFat :o

Sent from my GT-I9300
[Galaxy S III Original Android Development] rotorsk8r:
Just to confirm that I also have no touch control with v6.0.1.2 and am still having the same issue with back ups. Unable to find mounted volume : \sdcard error finding an appropriate backup handler (Is there some other fix for this other than going back to v1.5 ? )
[Galaxy S III Original Android Development] nicesoni_ash:
Thanks for the tar version mate.. +1..
[Galaxy S III Original Android Development] 9Lukas5:
Could you now please explain also why should it support exfat? Is exfat opensourced now ? NO! So it won't be applied to cwm.

And now please stop asking for that!!

I'd like it to see cwm support ext4 as extsdcard filesystem on /dev/block/mmcblk1p1

L
[Galaxy S III Original Android Development] andip71:
Just wanted to confirm: Working like a charm!

Was already using the 6.0.1.0 version without issues (reformatted my 64 GB sd-card to FAT32 as the 2 GB file limit is not an issue for me... - so no exFat required). All working perfectly.

Many thanks for this piece of work!

Andi
[Galaxy S III Original Android Development] aydc:
This is not like other recoveries where you control with gestures. On this one, you should directly press your finger on the line that you want to select.

Having said that, I think the lines must be even broader. It's hard to press on the right line even on a large screen like SGS3. This must be very difficult to use on a smaller screen.
[Galaxy S III Original Android Development] DroidRevenge:
Try to press not to move...
[Galaxy S III Original Android Development] mskip:
If you use the recovery to reformat your card to fat32 then it will work fine apart from not supporting large file sizes. exFat will not be supported in recovery as it is not open source so if you are holding out for that day then unfortunately you will have a long wait.

Mark.
[Galaxy S III Original Android Development] Theshawty:
This recovery is awesome! About the FAT32 format thing: besides not being able to handle files over 4GB at once, this filesystem seems much slower than exFAT were.
[Galaxy S III Original Android Development] micmaccc:
thx for explaining...

currently using cf recovery due to support exFat ;)

Sent from my GT-I9300
[Galaxy S III Original Android Development] kai84m:
Just flashed it via ODIN and Phone wasnt booting anymore.

Had to reflash 6.0.1.0.

I dont know why maybe the .tar integrity.

Cant anyone provide a MD5-checksum for the recovery?
[Galaxy S III Original Android Development] MauricioAedo:
Flashed without problems!
[Galaxy S III Original Android Development] wind0zer:
Dear users who find exFAT support missing,

You will want to use this recovery [RECOVERY][18.06.2012] ClockWorkMod Recovery 5.5.0.4 - "v1.5"

This thread is a pointer/link to the official opensource clockworkmod. On the other hand user/dev Chainfire (above link) has done some work & added some more value to CWM by adding exFAT support - opensource is cool like that...instead sometimes it's used as an excuse to slap people in the the face by saying "not in another 100 years". It kind of leaves a bad taste in the mouth for those who ask.
[Galaxy S III Original Android Development] aydc:
6a5622ff0f06e535b3b2ebc7f669ee7c *recovery-cwm-touch-6.0.1.2-i9300.tar
[Galaxy S III Original Android Development] Musko:
External SD Card mount

A cannot mount my sdcard.

My sdcard is called extSdCard and in ClockworkMod recovery called external_sd.

How can I correct this?
[Galaxy S III Original Android Development] yuriza:
Same problem!!!

My CWM now is: CWM-Based Recovery V. 5.5.0.4 CF-V 1.5

It 'compatible?

Can I install it over what I have now?

Sorry for my bad english. :(
[Galaxy S III Original Android Development] mattiadj:
If i flash some themes built with vrtheme system it doesen't work!!

It's a know bug??