yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jonhern:
lol yeah. I then copied to my computer and put it back on my new phone. how do i get it to see the back up? I also made a second backup and it did not show it either at first. Now it is. and the old backup was on my phone when i found it and copied before i factory reset my old phone, this new backup is on my ext card. and its in the same folder as the old restore point too as i put the folder on my sd card too, but only the new restore shows up in the menu. I am coping the files from the other folder to the new one that was created to see if that works. but yeah, just wont see my back up.

---------- Post added at 09:39 PM ---------- Previous post was at 08:49 PM ----------

So that last thing worked, I made a new backup and that showed up in the restore menu after i mounted sdcard. When i made one without mounting the sd card the backup did not show up. Anyway, even though it was in the same folder that i had placed the backup from the original phone, that backup file would not show up. So i tricked it, i deleted everything in the new backup folder, and copied the files from the other folder into that. then went back into recovery, mounted sd card, and there it was, i restored and it worked. So looks like that is the work around. I never had this issue with clockwork so i am going to flash that now instead. TWRP is nice, but it was a pain to get it to see my files.
[Verizon Samsung Galaxy S III] lynseyw:
Works great for me. I didn't have a problem with the external SD card once I reformatted it to Fat32 (64GB class 10) otherwise none of my stuff would recognize it. Still getting the 1970 date, but not a big deal.
[Verizon Samsung Galaxy S III] mikejr83:
So I tried flashing a zip to add Jelly Bean sounds. TWRP says it flashes fine but I open RootExplorer and /system/media files haven't been changed. Not getting any errors when installing.

Anyone else have problem flashing zips?
[Verizon Samsung Galaxy S III] x_SCOS_x_ELITE:
Is there any chance at all this would hit sprint version of s3, we can give just as much love
[Verizon Samsung Galaxy S III] mikejr83:
Quick update on the flashing issue. It turns out that the method of the two zips I was testing out that were mounting /system was incorrect (maybe?). They were loading by partition and then flashing. I suppose I lucked out that none of them destroyed anything. I have busybox installed and changed the mounting method to use a method from another script to mount /system. Worked like a charm.

That was hella noobish on my part (the whole flashing anything). I DID checked the script before hand just to make sure it didn't have anything super device specific and I thought the mount point for /system would be pretty much the same across devices. I came to that assumption as I got the flashable zips from two different locations for what I thought were different devices and they both mounted the same partition for system.

Overall I'm really digging this recovery!
[Verizon Samsung Galaxy S III] jnehama:
So far this recovery has been working beautifully. I was able to install the alternative boot animation and completed a back up. I have not restored it yet. The file manager is a bit tricky as it does not mirror the non recovery one. As per instructions I placed the boot.ani zip on the root of my sd card (aka internal sd card) using root explorer. In recovery I looked for data/media and eventually found it. It installed in no time and reboot was uneventful. By the way you can get to the external sd card with the buttons in the file manager but I'm not exactly sure what I then pressed to see all the files. It would be nice if someone with a better understanding could do a video tutorial. This recovery is more complex and a visual media would be great. But kudos to Team Win, they made adding a custom recovery to our phones a seamless process. I was getting ready to use the adb push interface for the first time when I came across this thread. Thank you!
[Verizon Samsung Galaxy S III] burpootus:
So is there an option to uninstall TWRP and reinstall the stock recovery?
[Verizon Samsung Galaxy S III] jhanford:
So I just want to be clear on this as this was an issue with the first recoveries on the ASUS Transformer last year: Using the options to "wipe" and "format data" will or will not remove the contents of /data/media (this is /sdcard when booted)?

Anyone able to verify either way?
[Verizon Samsung Galaxy S III] Funkybooyea:
To get to the External_SD_Card in the file explorer, just press (Up a Level) until you get to the root of the phone and then you can see both internal (Sd Card) and external. Is that what you were asking?
[Verizon Samsung Galaxy S III] nicholaaaas:
are there two dots near the top of the screen? click them to go up a level

---------- Post added at 10:56 AM ---------- Previous post was at 10:52 AM ----------

I'm about to flash it. I see no reason it shouldn't work.
[Verizon Samsung Galaxy S III] teh roxxorz:
You can using mobile odin or odin.
[Verizon Samsung Galaxy S III] burpootus:
First Samsung phone, still learning about odin. I got into trouble and my phone would only boot to the splash screen, so I figured I would have to start from scratch. I used odin to flash the stock image, phone still would not boot. Then used odin to flash the rooted stock image, still no go. Booted into recover and did a data wipe, phone booted. Probably could've done this to begin with and been okay. So I'm assuming odin doesn't do anything to /data, only system and recovery?
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Check out the Download section in the OP. The Goo Manager method works well and is simple.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Open GooManager: tap Menu/Install Open Recovery Script

Do the GooManager route or use EZ Recovery to install the 2.4.0.0 img. TWRP website even tells you how to dd command the img.
[Verizon Samsung Galaxy S III] DAMAGEvINC:
i have done the goo mgr route. I downloaded from market link. opened the program and in the search option i typed d2vzw twrp and the only options to dl were the .img or .tar files So that leaves me to ask for help from you guys. The goo mgr wont just auto update what i have for some reason. I ask it to but say my rom is up to date. And that is fine but it wont auto update my backup..... thanks for helping :)
[Verizon Samsung Galaxy S III] raypino:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

go to goo hit the menu button and select update recovery script and your done. just did it a few minutes ago and it worked.

sent via carrier pigeon
[Verizon Samsung Galaxy S III] DAMAGEvINC:
Thanks for the help guys, up and running!
[Verizon Samsung Galaxy S III] Sycobob:
Thanks for the update. Still wishing TWRP allowed ADB from the get-go. I did manage to get it working by messing with the Samsung drivers. It looks like all you would need to do is make the phone show the same Hardware ID(s) in recovery as it normally does when booted. http://xdaforums.com/showthread.php?t=2110854
[Verizon Samsung Galaxy S III] alquimista:
ExFAT support in v2.4?!?! OMGasm!

Downloading now.

Ta,

ALQI
[Verizon Samsung Galaxy S III] Mike3.14159:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Just download goo manager from the play store. Open up the app, in the top right there will be a drop down that says something like 'install open recovery', hit that and it will download and auto install. Thats the easiest way!

Or you can push it through using a computer and adb.
[Verizon Samsung Galaxy S III] Nonek:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Yeah.. Unfortunately the Auto update isn't working for me.. But I might have a strange case. I got this at Best Buy last month and after it updated it gave me "no digital certificate to insert" Or something very similar to that in the upper left hand corner on every boot.. So I did what any warm blooded professional returner would do and I exchanged it. And the next one from the same store did the exact same thing....

One thing that I heard about over the internet was that OTA updates didn't work anymore and I didn't really want to mess with trying to RMA it as I saw online that some people that did that had to do it twice because they gave it back the first time with the same issue.. One thing that was also said is that the unlock took didn't work, but I gave that a shot.. that worked and then I was able to root and now I'm on Cleanrom.. I just get the "this device is unlocked" message where the cert error was..

Anyway.. I told you all that to tell you that.. The auto update install script doesn't work for me. ;) I must have some device signature that is missing.. So does anyone here think it would make sense to try and nvflash this guy? I'm afraid that I have some sort of corruption in the device sig area of the device which wouldn't be touched even by an nvflash in that case.. I think I saw something about someone coming out with an image..

Anyway.. Sucks to be me and although everything is working just fine for a few weeks now I just hate running into these stupid things that nobody else has a problem with..
[Verizon Samsung Galaxy S III] ylexot:
When you say "auto update", do you mean the "Check for updates" option or the "Install OpenRecoveryScript" option. They are two completely different things. To install TWRP, you want the "Install OpenRecoveryScript" option in the menu.

Also, what device? Is your bootloader unlocked?
[Verizon Samsung Galaxy S III] obeygiant:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Word to the wise, (or stupid in my case) make sure your build.prop is correct first. I modified the build.prop file to install Google Wallet and didn't restore my original when I was done. When I went to update TWRP it downloaded the file for Galaxy Nexus Maguro and flashed that! Borked! All is well now but just keep it in mind, automation is only as accurate as the operator!
[Verizon Samsung Galaxy S III] Dees_Troy:
That's part of the reason that GooManager displays the filename of the file that it's going to flash. Near the end it said "maguro.img" instead of "d2vzw.img" which should have tipped you off that something was wrong. Eventually we'll probably improve the app to display the proper name (Verizon Galaxy S3) instead of d2vzw.
[Verizon Samsung Galaxy S III] obeygiant:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Thanks Dees. But come on, that's like actually reading the terms of agreement before checking ”I agree"! Following all the rules would be so boring, and I would never learn anything that way!

Vengeance is mine, thus saith the Galaxy S3!
[Verizon Samsung Galaxy S III] andybones:
anyone having issues getting this installed I suggest getting the EZ recovery.apk from play store, and download the .IMG from my thread here and install that way.

http://xdaforums.com/showthread.php?t=2096735
[Verizon Samsung Galaxy S III] Nonek:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

I'm going to call mental retardation as I thought I was in the TF300 section.. I have been jumping back and forth.. I'm just having WAY too much fun..

I'm sure this update will work just fine.. ;) I think the auto update for the TF300T just doesn't work and that might be why it's.. well not working but I'll get all crazy in the right forum.. My apologies ;)
[Verizon Samsung Galaxy S III] lowg:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Yep, killer feature props to teamwin

Sent from my Galaxy S3
[Verizon Samsung Galaxy S III] bluezr1:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

+1
[Verizon Samsung Galaxy S III] RCITNet:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

2.4.0.0 borked my SD card. It wouldn't recognize my SD card after completing the back up of my ROM so that I could install cm10.1. I had to Odin back to stock and let the phone settle for a while before it started recognizing my card again. It was an odd issue to have.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] WhiteReign:
If I change from Rom manager to TWRP what should I do. I am a bit scared to do this. Also will this fix my 0 Folder that drives me nuts? Thanks!
[Verizon Samsung Galaxy S III] suchavibrantthang:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

I think I f'd it up. Downloaded goomanager, then the zip file in the app, went into recovery and flashed the zip. Rebooted recovery and its bricked. Wont start, boot into recovery or download. Anyideas? Please help.
[Verizon Samsung Galaxy S III] WhiteReign:
Same Here DAMN!
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

The OP states:

1) Install GooManager from the Play Store

2) Open GooManager and provide root permissions

3) Hit Menu and then Install OpenRecovery

That's it. What exactly did you download and flash in Recovery?

Download mode (and ODIN) is the usual way to recover from bad ROM and Recovery. What happens when you try to go into Download mode?
[Verizon Samsung Galaxy S III] WhiteReign:
If its a BLACK Screen you cant do any thing. NO buttons work Nothing. I get qhsusb_dload. So ya. :(
[Verizon Samsung Galaxy S III] suchavibrantthang:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Anyway to recover with pc at this point?

---------- Post added at 05:59 PM ---------- Previous post was at 05:52 PM ----------

I know, I f'd up I said. I downloaded the .zip file from a search, moved to sd, then flashed in twrp. That was it. Now its black, wont boot into anything.
[Verizon Samsung Galaxy S III] dan_joegibbsfan:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Pull battery, hold down home button, down volume button, power button, after first vibrate let off power but continue to hold down home + volume down. That will get you into download mode so you can Odin back to stock. Also don't forget to unlock bootloader when you get back going.

EDIT: I forgot putting the battery back in but that is how you get into download mode.
[Verizon Samsung Galaxy S III] WhiteReign:
JUST FOUND THIS POST

"Sorry to say I did this to my first s3 by accident. Nothing u can do unless u can get it into download mode. Which the only way you can do that with a hard brick is by using a jig. Google galaxy s3 jig. U can buy one cheap or watch a YouTube video on how to make one for around $2. But other than that ur only option is to turn it into the phone insurance or maybe Verizon will jtag it for u. U can Google jtag as well. That's all the help I have for u. Good luck!!!!!"
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

I am truly sorry, but if you cannot get into Download mode, the solution is beyond me. You may want to post this in the q&a part of the forum in case anyone else has dealt with this. Good luck.
[Verizon Samsung Galaxy S III] Wisiwyg:
Make your own jig to force download mode.... link below - not too hard. Or buy jig off ebay for about $2.50 plus $2.50 shipping.

http://xdaforums.com/showthread.php?t=1604707

Good luck!
[Verizon Samsung Galaxy S III] trook:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Sometimes you have to leave the battery out for a couple minutes....no idea why but worth a shot.
[Verizon Samsung Galaxy S III] aypeeootrek:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Hey guys, quick question. I just updated my recovery through the goo app. Install and boot into recovery went fine. Having a problem locating files though. I used the older version to flash a 4.2 aosp Rom and ended up creating that 0 folder plus duplicating all the other folders like downloads and stuff. Pretty much all my downloads after the 4.2 flash went to the new download folder.

Now after flashing the new recovery, it doesn't allow me to view those folders. The list where the 0 folder(pretty much the folders created by the 4.2 flash) is in accessible. I can view them in a file explorer and was able to move files that I wanted but just curious why twrp doesn't recognize those folders it created with the 4.2 flash
[Verizon Samsung Galaxy S III] unhappybirthday:
Are you talking about accessing your nandroid backups for a restore? Did you move your TWRP folder out from under '0'? When a '0' folder is present, TWRP will assume its files are under it. If you moved them to the root of the internal SDcard, you will need to move them back.
[Verizon Samsung Galaxy S III] aypeeootrek:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Not just nanos, regular internet downloads too. I had to move a nano back to the 0 folder to restore a backup but the folders that were created while the 0 one was(if that makes sense lol)
[Verizon Samsung Galaxy S III] valorian13:
I recently started using this recovery. One problem I'm having is the time. This recovery is showing the wrong time at the top even though I have the write time zone selected. It also has the wrong date and time in the backup file when I use the time stamp as the file name.

Is there a way to change the date and time in TWRP?
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

No. Known issue. Low priority.
[Verizon Samsung Galaxy S III] harosxcomp170:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

I have a problem with TWRP 2.4.1.0 recovery, whenever I go to wipe cache or factory reset or system or dalvke cache it does it but it always reboots recovery after every wipe?? Anyone else having this issue? Is this normal? I'm getting sick of it so I've been staying on 2.3.0.0 recovery instead cause it doesn't do this?
[Verizon Samsung Galaxy S III] corbn89:
Cannot mount ext SD after nandroid

So I've been using this 16GB ext SD from Amazon with my d2vzw since I got my phone last summer. Been working fine until this morning.

I made a nandroid to ext this morning for Synergy r326 (TWRP 2.4.1) and, after rebooting, I could no longer see my ext SD card.

Ext storage does not show up in "My Files", I could not mount it in TWRP, could not see the files when plugged into a comp. via USB, could not see files in root explorer.

Does anyone know the underlying cause of such a problem? I seached but the only similar instances were fried cards.

I won't be able to take out the SD and plug it into a comp. until this evening (no adapter on me).
[Verizon Samsung Galaxy S III] smelkus:
The adapter on a PC will tell you for sure. If you're booted into your ROM, you should be able to go into Settings > Storage and unmount the SD. Peel off your battery cover, remove and reinsert your SD card. If it doesn't mount, it is probably a bad card. There are some definite cheap-o cards on Amazon and it seems to me some are counterfeit cards of SanDisk, Samsung, etc. Nothing TWRP would have done to it though.
[Verizon Samsung Galaxy S III] Gibscreen:
Not sure about a fix for the date. But r time go to Settings - Time Zone. You can switch to your time zone. It may still be of by some so you can use the offsets to change the time by 15, 30 or 45 minutes. I'm in California and I set it to pacific time and use a 45 offset.
[Verizon Samsung Galaxy S III] Dees_Troy:
[RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]
[Verizon Samsung Galaxy S III] corbn89:
An update: Was able to borrow an adapter from a co-worker. All my data is still on my Fat32 microsd. It just wont mount on my phone. I copied my data out to the PC then formatted the sdcard. Problem solved.

Something to note: While transferring files there was an immovable/undeleteable item in my TWRP folder (which i keep in my ext. card). It had file extension .win but could not be displayed because the title/name was "too long". I think this was the cause of the problem. I just moved everything else off the card and formatted that file away. Seems like something went wrong with my backup. I do not recall any errors flashing during the nandroid but who knows.
[Verizon Samsung Galaxy S III] KevinGee:
idk if anyone else is having this issue, although not really as important but the time is off by like 5-6 hours and some minutes. I know that you can change the time zone, i have already changed it to Pacific (Thats where im at) and its not correct. For example right now as of this moment its 11:25 P.M and in recovery it says its 5:53 P.M any ideas?
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]

Known issue. The post made 3 before yours has a workaround suggestion...
[Verizon Samsung Galaxy S III] smelkus:
It's also listed on TeamWin's site as a known issue that cannot be fixed.
[Verizon Samsung Galaxy S III] andybones:
yea I do the same thing, it's off by like 6 mins in the end for me, not a big dealio :)
[Verizon Samsung Galaxy S III] Daciple:
Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]

Great Recovery Option

Sent from Galaxy S3
[Verizon Samsung Galaxy S III] Dees_Troy:
[RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
[Verizon Samsung Galaxy S III] FrostyOrDie:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

On it like hot sauce in a taco

Make it so number one!
[Verizon Samsung Galaxy S III] keymaster911:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

+1

Sent from my SCH-I605 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] HHF2:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Does this recovery display the 1970 date the way CWM does? Also, if all of my backups are from CWM, can this restore them?

I am happy with what I have except for the date issue, it is tough to figure out which backup is which. I can say that it has never let me down across multiple devices.
[Verizon Samsung Galaxy S III] corbn89:
Yes, it has the incorrect timestamp date (tl;dr explanation is that its unfixable)

No, you cannot restore CWM recoveries with TWRP, or vice versa.

However, you can name/title your backups to whatever you want so you could just manually date the recovery
[Verizon Samsung Galaxy S III] buffal0b1ll:
Something wrong with ordering and flashing zips/sending wipe cache dalvik commands to recovery from GooManager app,

Updated to 2.4.3 from 2.4.1 yesterday.

In 2.4.1 and prior versions I never had a problem ordering and flashing 6 or 7 zips, wiping cache/dalvik, naming and requesting backup job from GooManager. It would reboot into recovery and I'd come back in 15 minutes and everything would be done waiting for me to reboot.

Yesterday I tried twice to flash 7 zips and wipe cache/dalvik in goomanager with TWRP 2.4.3.

The device reboots into recovery but it never processes the jobs I entered in GooMangler;-(

Anybody else having this problem?

EDIT : last night I successfully flashed 5 zips and wiped by setting up the jobs in goomanager. 6 and 7 both failed the day before.
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

So, on the latest version, I made backups of three different ROMs cause I was jumping around and when I went back to flash one of my backups, it said the data was restored and everything, but only part of it was there. Some apps, but none of my system settings or anything. It happened to all three backups and it freaking pissed me off-_- Idk what's up with that
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Anyone?
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Did you make sure that data, system, and boot were all selected when you made the backup? How about on the restore?
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Yes yes yes. I'm not a noob:P
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Sorry, I had to ask the obvious question. Hopefully someone else can chime in with other ideas. :(
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Yeah. Thanks though!