yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] lair12:
I'm not sure why the reference to the Sprint based recovery has been removed from the steps to root your phone.

My solution is here:

SGS3 Install Sprint Based Recovery

What does this get me?

1.	I can make full backups directly from Rom Manager by selecting Backup Current Rom.

2.	The dates for these backups are CORRECT!!!

3.	Backup goes to the External SD Card, and can be restored through recovery. Note: you cannot restore through Rom Manager, as it seems to look for backups on the Internal SD Card. But Rom Manager can take your directly into recovery mode, then restore from there.

4. I do not have or want touch recovery. Sorry, but I am old school and like scrolling to what I want and having a chance to change my mind before I press "go".

Installation Steps

To get Sprint based ClockworkMod (CWM) on your phone, you'll need adb installed and working for this. Your phone must be rooted.

1.	Download ADB.zip from: www.advancedcary.com/apps/ADB.zip .

2.	Unzip and copy to your C: drive. The Sprint recovery image is in the folder already.

3.	Connect your phone via USB cable. USB debugging needs to be ON.

4.	Open a command window as administrator.

5.	Type cd: c:\ADB

6.	Then carefully type or cut and paste the following series of commands.

adb push recovery.img /sdcard/

adb shell

su

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18

reboot recovery

7.	Download ROM Manager from Google Play

8.	Open Rom Manager and Flash ClockworkMod Recovery.

Recovery Mode

•	Key Combos: Volume Up+ Home

•	While holding both of them simultaneously press the Power button

Any problems or errors??? Please let me know.

Did this help? Then

GIVE A THANKS!
[Verizon Samsung Galaxy S III] glitho:
In what mode I have to be to run the commands? In hboot? in cmw recovery? or when my phone is in use? Because I have an error: device offline
[Verizon Samsung Galaxy S III] AtLemacks:
Rebuilding the image now. Sorry guys, with the weather I have been non-stop between the ER and the Fire Department. People don't understand burn ban.

Still no luck. Talking with Koush in G+ right now.
[Verizon Samsung Galaxy S III] AtLemacks:
Koush still isn't supporting our device yet. Tried talking to him on G+ and Twitter, no response. I would suggest everyone just continue to use TWRP until then. My build currently just bypasses recovery and boots the phone as normal. He doesn't have our Kernel Source or anything supported yet. -_-
[Verizon Samsung Galaxy S III] sincerity:
thanks for working on this...any way you can see to get internal sd to mount in either recovery? You know more about this than me....lol
[Verizon Samsung Galaxy S III] M4gicM@:
My internal sdcard was able to mount using the image found here http://xdaforums.com/showthread.php?t=1756885 here is the link if you did not wish to click http://goo.im/devs/invisiblek/i535/recovery.img
[Verizon Samsung Galaxy S III] sincerity:
^using which recovery?
[Verizon Samsung Galaxy S III] AtLemacks:
I believe that is the one invisiblek directly ported.

BTW, I got a BETA up guys. Let me know if it does or doesn't boot for you.
[Verizon Samsung Galaxy S III] AtLemacks:
Still no luck, I have posted all the recoveries to the OP though.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Is the Sprint one you say to use, the same one that I posted from Koush's files and ROM Manager? That one has confirmed to work?
[Verizon Samsung Galaxy S III] Marcismo55:
I just flashed the Sprint one you posted and I successfully flashed and made a backup. Restoring that backup now and seems to be working.

Edit: I have access to both internal storage and SDcard. Flashing invisibleK's stock stripped rom now with no issues.
[Verizon Samsung Galaxy S III] AtLemacks:
Yes, it is. I am trying to build based off of it, and their touch version now as their touch won't boot on our phone either.

Awesome.
[Verizon Samsung Galaxy S III] AtLemacks:
Touch build now working! Check OP!
[Verizon Samsung Galaxy S III] jlokos:
Great work. I'll "flash" it as soon as I receive my S3. Thanks.
[Verizon Samsung Galaxy S III] AtLemacks:
Push, Flash, Kick, Punch, Cartwheel, whatever you please, lol.
[Verizon Samsung Galaxy S III] raisins:
If I already have CWM do I need to remove it or anything? Can I just push this over it?
[Verizon Samsung Galaxy S III] AtLemacks:
Yep, it will install right over it just as if it was the stock recovery.
[Verizon Samsung Galaxy S III] frifox:
flashed the touch recovery. did a nandroid backup (to /sdcard). everything went down as expected. one small issue, backup folder date is wrong, 1970 != 2012. personally that's not a problem since i rename my backups anyways :good:
[Verizon Samsung Galaxy S III] AtLemacks:
I'm looking into it because it worked fine before this version I uploaded. I have 2 versions on my computer so I'll see if I can find the flaw.
[Verizon Samsung Galaxy S III] kthung:
How is this different from the recovery in invisiblek's thread?
[Verizon Samsung Galaxy S III] eastwood1:
Wooot finally got touch recovery installed and its working great. I had to fiddle around with adb but i finally got it installed.

Thanks for putting the recovery together for us.
[Verizon Samsung Galaxy S III] silasrye:
Koush just updated his cwr's and now a verizon gs3 is included, can be easily flashed via rom manager.
[Verizon Samsung Galaxy S III] AtLemacks:
His was a direct port from an unofficial version the Sprint devs built, and want touch. Mine is touch, built in cwm recovery builder.

As someone stated above, Koush released his official build. I'll update OP later.
[Verizon Samsung Galaxy S III] AtLemacks:
Here's a direct link. https://docs.google.com/file/d/0B5YKMprNcHHJZlBaam9OLTNyRnc/edit
[Verizon Samsung Galaxy S III] AtLemacks:
Whoever that was that tried downloading try again. I didn't have it shared yet, sorry :beer:
[Verizon Samsung Galaxy S III] preusstang:
just copied over the cwm touch verision with terminal emulator. works great. the soft "back" key works as well :)
[Verizon Samsung Galaxy S III] TheBiles:
Personally, I'm sticking with TWRP, but it's nice to see us supported in ROM Manager.
[Verizon Samsung Galaxy S III] AtLemacks:
I need to work on the OP later. This means we have a wide variety now though!
[Verizon Samsung Galaxy S III] suzook:
while i like twrp the best, its not great on the s3...it has isssues with sd/ext sd
[Verizon Samsung Galaxy S III] largeselection:
Weird...flashed via rom manager and it seems ok. I was able to boot into it no problem. Tried to backup and immediately got "error while backing up boot image!" any ideas how to fix?
[Verizon Samsung Galaxy S III] HolyGrail:
Did the same thing...and got the same results....confused on how to flash and overwrite with twrp. :confused:
[Verizon Samsung Galaxy S III] jmacko:
Saw that earlier today, and after updating it, I'm getting an error when I try to backup. Tries to backup /boot and then stops. I'm also unable to choose /ext-sd or pick "Use External Storage" from the ROM manager GUI when booted normally.

CWM version 5.8.4.6.
[Verizon Samsung Galaxy S III] mds96:
It seems like all the Recoveries are having problems with backups. I tried three times in invisibleks recovery.img and got "1970" instead of 2012 on all of them. Had a guy on Twitter who installed the official CWR Touch try a backup and he got the same result. From my experiences on CWR on my ol DX, when I got "1970" it was a bad backup! I already went back to stock unrooted till the backup issues get ironed out!
[Verizon Samsung Galaxy S III] s197:
If you look at the date on the mount points here:

http://vzwgs3.wikia.com/wiki/Dev:_Mount_Points

You'll see that it's 12/31/1969. So you probably did a nandroid a day later, hence, 1970. My assumption is while the date is wrong, the backup may still be good.
[Verizon Samsung Galaxy S III] HolyGrail:
Update: Using terminal emulator and the OP commands.....flashed touch.img and overwrote CW. :o

That worked but still cannot do backups......says No /sdcard/.android_secure found.

I get the same error, also running the internal backup option.

Has anyone been able to do a successful backup? If so...what did you do differently?
[Verizon Samsung Galaxy S III] mds96:
Damn, now thats interesting and you've got me wondering! Over on invisibleks thread a guy posted that he made a backup, flashed it, and I believe it looped him or failed, can't remember. He didnt say whether it had 1970 though...
[Verizon Samsung Galaxy S III] AtLemacks:
Hey guys, for the time being my "touch.img" and the "sprintrecovery.img" work fine. It DOES make backups. I have yet to try to restore one, but it does at least make the backups. I will look into the official version tomorrow.
[Verizon Samsung Galaxy S III] Marcismo55:
^This.

I have been using your touch CWM making backups, fixing permissions, etc. with no issues. The date thing is easily dealt with by renaming the files which i do anyway.
[Verizon Samsung Galaxy S III] AtLemacks:
I'm still trying to get a hold of Koush, he sure has hell can get a hold of you when he wants to. But, then again that man is a busy dude! We talked about Crossfit gym's in some PM's a while back and can't get a hold of him since.
[Verizon Samsung Galaxy S III] HolyGrail:
Himmmmmm...must be on my end then....going to do a factory reset and start all over again.
[Verizon Samsung Galaxy S III] AtLemacks:
Factory reset won't reset your recovery image. Try pushing my touch version again.
[Verizon Samsung Galaxy S III] jackdubl:
I don't care about the date, as long as the backup can be restored. Can anyone confirm if the original invisiblek recovery.img can restore a backup? I, of course, am too scared to try.
[Verizon Samsung Galaxy S III] mds96:
Well I had to prove myself wrong! I would like to thank the OP for giving us a great working touch recovery! The touch.img worked perfect making a backup! I flashed it even though it said 1970 and I'm back up and running with no problems!!
[Verizon Samsung Galaxy S III] jackdubl:
So restore worked? Confirmed? And you used the fourth link in the list of recoveries, correct?

I'm having a problem. I flashed Koush's recovery for Verizon S3 when it came out, and it didn't work. Now my recovery seem permanently screwed. I have since reflashed invisiblek's initial recovery, which was making backups just fine, and now flashed this working touch.img recovery. Everything just hangs on the "backing up system" but nothing ever even starts backing up. I end up having to do a battery pull. All I can do is reboot but I can't seem to back up anything now, no matter what I do.
[Verizon Samsung Galaxy S III] mds96:
Yes to everything! I'm running the "fixed" stock rooted rom, not invisiblek's. Not sure if it makes a difference, but thought I'd throw it in there also
[Verizon Samsung Galaxy S III] Syndacate:
AtLemacks, your sig says SGS III unlocked and rooted.

How did you unlock the boot-loader?
[Verizon Samsung Galaxy S III] jackdubl:
I'm running that rom as well.

I'm having a problem. I flashed Koush's recovery for Verizon S3 when it came out, and it didn't work. Now my recovery seem permanently screwed. I have since reflashed invisiblek's initial recovery, which was making backups just fine, and now flashed this working touch.img recovery. Everything just hangs on the "backing up system" but nothing ever even starts backing up. I end up having to do a battery pull. All I can do is reboot but I can't seem to back up anything now, no matter what I do.
[Verizon Samsung Galaxy S III] mds96:
I would just start fresh, which is what I did, and everything is working so far
[Verizon Samsung Galaxy S III] jackdubl:
start fresh, as in reflash the rom and then recovery, i.e. start all over again? I guess it'll only take about ten or fifteen minutes.:rolleyes:
[Verizon Samsung Galaxy S III] mds96:
Yeah seems like the best option. Well I guess you could try a full wipe, then try flashing the touch.img again. Might be aquicker first try
[Verizon Samsung Galaxy S III] jackdubl:
Reflashed the rom, set everything back up...same problem. Recovery just doesn't do anything for me. This is getting bad. Only option now is to try to go all the way back to stock and see if it somehow starts working. But I factory reset, reflashed the working rooted stock rom, and reflashed touch recovery...and it still does nothing. So now I'm even wondering if going all the way back to stock will do anything. Can't figure out what happened for the life of me. Recovery seems completely bricked for me.

If going back to stock doesn't work, what, do I need to do a 14-day exchange? It's mindboggling to me.
[Verizon Samsung Galaxy S III] Serinety:
If you are blaming koush for your phone problems, you might want to find another hobby.....

I'd just return it, do it over the phone and just give a BS reason . Then.. never flash your phone again plz ...
[Verizon Samsung Galaxy S III] xliderider:
This is why Verizon locks and encrypts bootloaders. :(

Because ppl bork their phones, then take it back for another one.
[Verizon Samsung Galaxy S III] jackdubl:
Thanks for the constructive assistance. Of course I don't blame Koush. Flashed his recovery on every phone I have owned. Just can't figure out what the problem is. I'm wondering if the bootloader in conjunction with the non-working Koush recovery bricked it.
[Verizon Samsung Galaxy S III] eastwood1:
Koush updated CWM again to 5.8.4.8 , hope this helps those that are having probs.
[Verizon Samsung Galaxy S III] jackdubl:
Phone works fine, only recovery is bricked. I'm actually thinking it's BECAUSE of the locked bootloader.
[Verizon Samsung Galaxy S III] jackdubl:
Well, I flashed the stockrecovery.img and then flashed TWRP.img and it's backing up now fine. Can anyone confirm if you can restore a backup with the TWRP recovery in the OP? If not, I'll try to flash the touch.img back on it.
[Verizon Samsung Galaxy S III] AtLemacks:
SIM unlocked, not bootloader.

I'll check this afternoon.

How are you pushing recovery?
[Verizon Samsung Galaxy S III] jackdubl:
Through adb. The instructions are here in the OP: http://xdaforums.com/showthread.php?t=1756885 Make sure to substitute "recovery.img" for whatever the name of the img file you're using.
[Verizon Samsung Galaxy S III] AtLemacks:
Maybe try terminal then. I have always had success in terminal and I've used all the recoveries.
[Verizon Samsung Galaxy S III] AtLemacks:
I'm extremely busy today so forgive me if I don't answer prompt.
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
Only one recovery works for me...but restore not tested.

Rooted SGS3, but had backup recovery problems from the beginning. Date was showing 1970, etc, and should have just stuck with that and renamed.

But wanted resolution, so I have pushed a number of recovery.img to find something that works. Results are:

1. Neither the ClockWorkMod site 5.8.4.6 or the 5.8.4.8 images (7002 kb) work for me. Regular and touch made no difference. No backups from ROM Manager or from recovery mode. BUT, installing these did allow my ROM Manager to update to regular and to touch in the app, as the SGS3 phone became an option.

2. Stock recovery image (6257 kb) as it was known on this thread also did not work and caused total backup capability loss.

3. TWRP8 (7116 kb) originally worked and gave me backups with the 1970 date, but I never tested restore capabilities.

4. I've now re-pushed the Sprint based recovery image: http://goo.im/devs/invisiblek/i535/recovery.img and seem to have working CWM backup. When I backup from ROM Manager, I even have the correct date and time. So for me, this is what works. The recovery reboot screen does show an unlocked picture of a lock and says CUSTOM. I don't see any problem with this.

NOTE: I've not tested a full recovery of these backups, as I have spent too much time setting up my phone and do not want to risk losing all this!! If you are not as set up as I am and find that you get valid full recoveries, please let us know if this Sprint version fully works.

Thanks.
[Verizon Samsung Galaxy S III] jackdubl:
So can anyone confirm that TWRP can restore one of it's 1970 backups?
[Verizon Samsung Galaxy S III] rothnic:
I've tested the sprint TWRP8 restore capabilities and they worked fine.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Has anyone been able to get backups to external SD card rather than internal memory on any of the CWM versions? No matter which one I try it isn't able to detect the external SD card at all. Only the sprint and touch-based in OP work but only to internal memory.
[Verizon Samsung Galaxy S III] sincerity:
finally got cwm to detect internal SD card but I still can't get twrp to detect any internal sd at all....said can't mount...anybody else?
[Verizon Samsung Galaxy S III] Budwise:
I installed the touch one straight from ROM Manager. Booted into recovery and tried to backup and it would just error out immediately saying it cant backup the system.img. Do i need an external SD card to do this?
[Verizon Samsung Galaxy S III] jackdubl:
Is that the one in the OP? 2.1.8?
[Verizon Samsung Galaxy S III] AtLemacks:
I won't be by my computer until 3-4. I'll look into it then guys. I know for a fact mine works. If it doesn't work the first time repush it a second time and try before pushing another recovery. I noticed the recoveries break pushing them over recovery. So push, reboot, push, then try to backup.
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
YES. My backup through ROM Manager is saved in the clockworkmod/backup/... folder just as it did when I had my Inc2 without internal storage.
[Verizon Samsung Galaxy S III] AtLemacks:
OP updated.
[Verizon Samsung Galaxy S III] Marcismo55:
I am still running the touch recovery posted yesterday and my backups are saved to external storage.
[Verizon Samsung Galaxy S III] sincerity:
fyi, the path for twrp is data/media to get to the internal sd card....dees_troy from team win sorted that out in chat....might as well use 2.2 tho he has just made a thread as it has a keyboard and its awesome.
[Verizon Samsung Galaxy S III] pdinphx:
Where do we get the most recent version of TWRP for our phone?

Pj

Phoenix, AZ

p.s. Nevermind ... saw your recent post just below this one. Thanks!
[Verizon Samsung Galaxy S III] luke1333:
I'm running the new cwr from Rom manager and can't backup or restore. Error on boot img any ideas??
[Verizon Samsung Galaxy S III] Budwise:
Same here.
[Verizon Samsung Galaxy S III] luke1333:
Same as me above?
[Verizon Samsung Galaxy S III] Budwise:
Yep, flashed via ROM Manager to latest version, backup doesnt work.
[Verizon Samsung Galaxy S III] luke1333:
Crap I wanted to try new Rom and now I ain't happy lol
[Verizon Samsung Galaxy S III] Marcismo55:
Very easy...don't use those versions yet. The touch.img in the OP works perfectly except for the backup date issues (which is not a big deal).
[Verizon Samsung Galaxy S III] luke1333:
Tried that too same issue. I'm going to flash first cwr back via adb when I get home from work tonight
[Verizon Samsung Galaxy S III] open1your1eyes0:
For anyone that is having problems backing up to EXTERNAL SD Card please take a look at this: Link

Took me a while to figure out why my 64GB MicroSD wasn't being detected by any recovery and several apps couldn't detect it.
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
ROM Manager stores on external, looks for restore on internal!?

I decided to try to see if my ROM Manager backup would successfully restore. I was please to see that it did the backup on the external hard drive as I wanted.

But when I go into the ROM Manager app and tell it to restore backups, it only sees looks on the internal memory...weird. So to do the backup through the app, I had to copy the entire backup from the external SD to the internal memory for it to find it.

The GREAT NEWS is that the backup installed fine. If I go to recovery mode, I do have the choice of restoring from the external or the internal memory.

For me, the backup problem is well solved. Thanks to all you brains that got this working.
[Verizon Samsung Galaxy S III] AtLemacks:
Which recovery version did you use?
[Verizon Samsung Galaxy S III] mikejr83:
Quick notes on my experiences:

Birdman's TWRP recovery - Was able to successfully make a nandroid. Didn't test restore functionality. Decided to move off because I couldn't figure out how to flash zips (as in I wanted to flash a zip with a manifest to reset the sounds to stock Jelly Bean).

CWM Recovery Touch relased by Koush from his website - Was able to successfully flash the zip I wanted (yea Jelly Bean sound scheme!), but wasn't able to make a nandroid. The same issue where it errors when trying to create. Decided that was a deal breaker.

Latest 2.2.0 TWRP recovery - This is where I currently am. The earlier poster that pointed out the /dev/media is the location of the internal SD card made it so I could flash the zips with a manifest. Tested that and it works!

Here's the deal though. I took my earlier backup from Birdman's TWRP and renamed the folder to "Original Backup". Just the folder name. I didn't realize that you could rename in TWRP. I later screwed something up in settings.db. I thought, "well damn, at least I made a nandroid." I tried restoring it in 2.2.0 TWRP and it failed on me. I'm really leaning towards the fact that I renamed it AND it was from an earlier version. I'm going to make another nandroid when I get out of the office, rename it in TWRP (because of the date issue), and then see if it restores fine.

At this point I'm inclined to say that the latest version of TWRP installed via GooManager is the best working option. I have not had the chance to put in an external sdcard so I cannot vouch for how well it works in that scenario.

I'll report back after I attempt the backup and restore, but I'm low on battery. I'm going to get some juice on the phone before I attempt this. BTW, does the phone charge in recovery? I didn't think my DX would do that so I always made sure to have it above 70% before flashes and backups.
[Verizon Samsung Galaxy S III] AtLemacks:
What relevance does this have to MY recovery? It doesn't.
[Verizon Samsung Galaxy S III] WhammyDroid:
Why don't you get your changes merged with Koush's CWM changes and it an official release made!
[Verizon Samsung Galaxy S III] AtLemacks:
Koush build is a newer version. I don't even know what changes if any were made. I stripped parts out of multiple builds. What I did for my port may not work on the official build.
[Verizon Samsung Galaxy S III] lair@nc.rr.com:
I used the sprint one. It's the only one that worked for me.
[Verizon Samsung Galaxy S III] ftmaniac948:
My stock rom is coming in at around 2gb of memory. Is this normal? Backups in the past for me were much smaller
[Verizon Samsung Galaxy S III] AtLemacks:
ROM Manager does not recognize anything other than official builds by Koush.

Did you try what I said in the OP about pushing twice before trying to make a backup?

The backup of your stock ROM? It should be backing up your apps/data/etc too.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Opened rom manager, hit backup rom. Was told to install a recovery. I had installed cwr when I rooted my phone the other day. So i clicked install recovery, scrolled down the list an seen a recovery for the Verizon version. Installed it an still can't make a backup, what gives?

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] mikejr83:
Well... no relevance to your recovery! Just that others were posting on what their issues with recoveries coming out. I've been testing them since I've had a chance to root. I honestly didn't flash yours because I saw Kosh had released one. Figured he took what you did and brought it into an official release.

That said I've finished up testing with TWRP and I've found it is not flashing zips for me. Since I haven't tested yours I'll give it a go.

Sorry if my post was a bit off topic.
[Verizon Samsung Galaxy S III] AtLemacks:
-_- Read above....

The point of this thread is to use mine, and if it DOESN'T work for you I have listed the resources to try the others. Would have been ok if you had tried mine and it didn't work.
[Verizon Samsung Galaxy S III] AtLemacks:
There's a new version of official CWM Recovery. If anyone wants to push it and let me know if it works I'll update the OP when I leave the ER later. Should be v5.8.4.9.