yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] lowg:
Work around now is to browse to /data/media

Future version will support the /sdcard symlink per latest post by Dees_Troy.
[Verizon Samsung Galaxy S III] Karl:
Inando84 hooked me up with this thought someone else might want it
[Verizon Samsung Galaxy S III] t0adman:
I'm rooted. Can I simply install TWRP (have it on my Kindle Fire...love it!) and flash or is there some other app required prior or in addition? Sorry for the noobiness folks. Got my S3 yesterday and it's my first Samsung phone.
[Verizon Samsung Galaxy S III] lowg:
Yes, make sure you get the VZW GS3 version though. Easiest way is using goo manager per original post or you could download the image from the teamw.in web Site and follow the instructions to use dd.

Sent from my Galaxy S3
[Verizon Samsung Galaxy S III] t0adman:
Hmm. Downloaded/Installed GooManager from Play Store, downloaded and (thought I) installed TWRP 2.2. Phone rebooted. When I go back into GooManager to confirm it says I need the RecoveryScript. When I hit volume up and home key I boot into Android Recovery. Okay, back to step one...repeat!

Gave GooManager superuser, rebooted but into Android Recovery again. What am I missing?

EDIT: Third time was a charm. Leave me along long enough and I'm bound to find a solution or brick my phone.
[Verizon Samsung Galaxy S III] pyrostic:
What did you change to get it to work the third time? (I'm going to give you your thanks in advance)
[Verizon Samsung Galaxy S III] wera750:
Wish this worked with kexec
[Verizon Samsung Galaxy S III] WhatMeWorry:
Friggin' GREAT job

Amazing work guys. Thank you.
[Verizon Samsung Galaxy S III] mike86325:
Pretty sure I saw a link in this thread (might be wrong I've looked at so many threads today lol) that was to an xda thread of recoveries that had been modded to support kexec and they had TWRP

Edit: here it is:

http://xdaforums.com/showthread.php?t=1773514
[Verizon Samsung Galaxy S III] wera750:
Says twrp won't work with kexec
[Verizon Samsung Galaxy S III] mike86325:
ahh, I stand corrected. I should have kept reading before posting that lol. That's a bummer since so far TWRP has been nothing but awesome. I'm sure that they will figure it out soon enough.
[Verizon Samsung Galaxy S III] wera750:
Anyone know if Deez Troy plans to make this kexec compatible? Twrp is by far my favorite recovery.

sent from locked bootloadrer SGS3 running a custom kernel :)
[Verizon Samsung Galaxy S III] t0adman:
I wish I could tell you I discovered something wrong or found a fix. I simply attempted the steps in the correct order several more times and finally it worked. Still a bit of a mystery really.
[Verizon Samsung Galaxy S III] Wisiwyg:
Solution posted several pages back...

http://xdaforums.com/showpost.php?p=28782645&postcount=43
[Verizon Samsung Galaxy S III] wera750:
CWM touch ?

sent from locked bootloadrer SGS3 running a custom kernel :)
[Verizon Samsung Galaxy S III] sbattosai:
How can you make a user error with one file to flash ? And with a correct MD5 for the file? the recovery flashed, I was then on 2.6.3.1 but everytime I flashed a rom, I was stuck at the bootanimation until I flashed the official tar version with ODIN.

And the other user also had this problem and who knows how many others. Maybe my phone doesn't like your file but don't throw "user error" to my face, I don't appreciate it.
[Verizon Samsung Galaxy S III] Karl:
if you cant reproduce it then dont make such claims
[Verizon Samsung Galaxy S III] sbattosai:
Because I flashed PA 4.0 beta, then I flashed Gummy 2.1 then I flashed Ose rom, then I flashed CM11. Thought it was a kitkat thing so I flashed carbon rom from 11/17 and I finished with Beans 20 a TW rom that I was on before the flashing madness. Funny thing, I did flash again all those roms after installing my official recovery and they all worked. Ended up installing PAC because the kitkat roms are not exfat compatible yet.

I am not going to brick my phone to prove a phone, I wasted enough time because of that yesterday.

I just wanted to warn that some phones may not like this file and people should use the ODIN version, not start a fight with you.
[Verizon Samsung Galaxy S III] StrumerJohn:
My word, if it helps anyone feel less afraid to update:

- Rerooted phone today tired a few different things to make sure it's worth archiving older methods still:

CASUAL: Worked (ICS&JB, Not detected under SysScope or Download mode)

Debug "1-click": Worked (ICS; JB, but ended up with CUSTOM boot)

Original: Worked (ICS; Not JB)

- Unlocking:

EZUnlock (1.0): Worked [*I have not tested newer versions as I do not remember which one does not work. Only archiving first to be safe*]

CASUAL: Worked

USBRootFlash: Worked

- Recoveries:

TWRP 2.6.3.0: Worked (tested backup, compressed backup, compressed restore, restore, theming, wiping, charging, formatting and encryption!)

TWRP 2.6.3.1: Worked (tested backup, compressed backup, compressed restore, restore, theming, wiping, charging, formatting and encryption!)

TWRP 2.6.0.0: Worked (tested backup, compressed backup, compressed restore, restore, theming, wiping, charging, formatting) [Did not test encryption; may or may not work]

TWRP 2.4.2.0: Semi (tested backup, compressed backup, compressed restore, restore, theming, wiping, charging, formatting* [softbricked when I formatted system])

TWRP 2.4.1.0: Semi (tested backup, compressed backup, compressed restore, restore, theming, wiping, charging, formatting* [softbricked when I formatted system])

CWM 6.0.2.3: Worked (backups, restores, wipes, formatting; charged very slowly)

CWM Touch 6.0.2.3: Worked (backups, restores, wipes, formatting) [charging not tested]
[Verizon Samsung Galaxy S III] countryfolk07:
[MENTION=4160641]StrumerJohn[/MENTION], so you're saying you used the above methods on the new 4.3 update? That is what it sounds like per you're title.
[Verizon Samsung Galaxy S III] StrumerJohn:
What? You confused me. If you mean ML1 (4.3), here's some facts for you:

- ML1 includes a new "aboot," or bootloader, which is locked.

- A locked bootloader means NO custom recovery or unlocking (obviously, unless cracked).\

- A locked bootloader means NO AOSP, MIUI, Modified TouchWiz, or other ROMs.

- I535 Firmware update includes a new firmware signature key that requires all partitions to have matching keys or a "Qualcomm Fuse" will break, causing your device to brick (No modified RECOV, SYS, Aboot, etc.)

- Once updated these fuses are like rivets and only go in, not out (you can not downgrade firmware from this point on either).

- This OTA Sadly marks the end of TouchWiz development.... unless we happen to figure out a way to RE-crack the new bootloader OR reverse engineer a kernel that works with the 4.3 TW System.

So if you thought I was doing all of this on 4.3... Well then you should have donated to me because that would mean I'm a genious who saved everyone's modding life (for TW) . ^^.

Oh and incase you didn't get the point:

DO NOT DOWNLOAD THAT OTA. THERE IS NO GOING BACK!

Say goodbye to AOSP, Custom Themes, Custom ROMs, Recoveries, and Kernels if you do.

Invisiblek has a great read here:

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

and Drbliss (also linked in above) explains the fuses:

http://t.co/myb0LIrN6e
[Verizon Samsung Galaxy S III] Wisiwyg:
Version 1.2 is the best. In the past, Play would try to update to 1.4, but you just uncheck auto update to prevent it. I keep a copy just in case.

Very nice work!
[Verizon Samsung Galaxy S III] jackdubl:
Looks like we may all find ourselves in the Motorola thread by this time next year.
[Verizon Samsung Galaxy S III] BadUsername:
This isn't necessarily true.

TW 4.3 is still something to build off of, but the apps and bootloader have to be de-knoxed and removed. If the bootloader is removed from the rom, then there's no reason touchwiz development can't continue.

cnexus did it for the sprint s3. I'm confident beans or rerick will eventually be able to do it also. There's still plenty of life for TW development.

However, I don't think people who took the ota will ever be able to unlock their phones, and they're going to be completely stuck to a rooted stock rom.
[Verizon Samsung Galaxy S III] StrumerJohn:
I never said we'd not get passed it; I'm just saying until we do there will be NO 4.3 ROMs.
[Verizon Samsung Galaxy S III] lowg:
This is wrong. All you need for a custom recovery is root.

I'm running stock bootloader/kernel and have TWRP flashed.
[Verizon Samsung Galaxy S III] landshark68:
Then you are the only person on these or any of the forums I follow who is on 4.3 and has successfully flashed a custom recovery.

Sent from the Shark Tank using XDA Premium 4 mobile app
[Verizon Samsung Galaxy S III] jackdubl:
Can you flash anything with it?
[Verizon Samsung Galaxy S III] malo1m:
sd card error after goo

Please help, I'm on the road and cannot go through the pages fast enough to find the fix. I did the simple goo install method. Now my Sandisk 32gb SD card is giving errors. I have all of my pics and most importantly music for the drive. Anyone have a quick fix.
[Verizon Samsung Galaxy S III] lowg:
Yeah of course, you can flash a ROM/backup only limitation is that you need a stock kernel. There is a workaround using kexec to load a custom kernel that was used before the gs3 was unlocked that should still work.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
So, how did you get TWRP installed on 4.3 VRUCML1?

Edit: to be clear, I am referring to the 4.3 OTA. How did you root and then install TWRP on this OTA?
[Verizon Samsung Galaxy S III] lowg:
landshark68/slimsnoop:

Never said that sorry for the confusion... I just said is that if you had root you can flash a custom recovery with a locked bootloader. Old locked bootloader only checked kernel partition if you guys are saying all partitions are now signed then yeah people in 4.3 are f'ed.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
The reason he stated that is because of your post. Being that you quoted part of StrumerJohn's post which included "ML1 (4.3)", you wrote:

and when one reads this it is logically inferred, based on your wording, that you had TWRP installed on VRUCML1 4.3. I see what you mean now, but you initially wrote an ambiguous post. You're on stock rooted 4.1.2 and you have TWRP. Cool, glad that's all cleared up cuz I asked something similar as you can tell.
[Verizon Samsung Galaxy S III] malo1m:
Anyone know how to fix this?
[Verizon Samsung Galaxy S III] cstone1991:
This probably isn't the best place to post this question since this thread is related to TWRP specifically, but to answer your question (somewhat anyways) I had an issue with my SD a while ago. Through Google searches I found a number of windows programs meant to recover lost data on a corrupted SD card. I had no luck with any of these and ended up having to do a low level format with a different windows program I found. Windows 7 Pro was incapable of reformatting it on it's own. In all honesty, you may have lost your personal data and this may be a valuable lesson on backing up your data (I hope not). I let Google Photos backup my pics so that I know that I can at least recover from there and I recommend copying them to a computer at least once per month too. Any other important files could be backed up to Google Docs or Dropbox and then backed up to your computer in a similar fashion, but I only really care about my pics personally.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] ashisharia:
i am using s3 and have cwm 6.0.1.2 . i want to install twrp and installed app and downloaded the script but still cwm is being shown
[Verizon Samsung Galaxy S III] Macrodroid:
Ok, I just installed this recovery and it wants a password? I never set one, so how do I get past this? Googled and it seems this is a common issue, but no set answer to fix it. Would think the developer would address it in the op ...
[Verizon Samsung Galaxy S III] bamaredwingsfan:
There is a recall on certain SanDisk cards. I had a 64 gb card that was brand new and went bad. Go to their website and hit up customer service an see if they will replace it
[Verizon Samsung Galaxy S III] david_hume:
If goomanager doesn't work, then try using flashify (download from play store) and then download the image from TWRP's website.

After that, just open the flashify app and then select the TWRP image and them you should get TWRP flashed onto your phone.
[Verizon Samsung Galaxy S III] Chevelle1768:
Anyone else having recovery reboot/crash during a "factory reset"?
[Verizon Samsung Galaxy S III] lepa71:
I want to be able to switch between rooted TW 4.3 and KK roms. I know that 2.6.3.0 does not support KK. Do I need swap recoveries from 2.6.3.0 to and back 2.6.3.1 or i'm ok to stay full time with 2.6.3.1? Will 2.6.3.1 handle restores and backups of both versions Android OS? Thanks
[Verizon Samsung Galaxy S III] KevinGee:
I've been switching from 4.4 to 4.1.2 to 4.3 and back to 4.1.2 now I'm on 4.3 and I'm not having any problems whatsoever. I'm using 2.6.3.1
[Verizon Samsung Galaxy S III] chocolate8175:
Is there a way to have twrp make backups store to the external sd card?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Sure, tap the part of the menu where it says "internal storage" on the backup screen. You still have to manually move over your pre-existing backups.
[Verizon Samsung Galaxy S III] Nomad1600:
Took me three tries with Goo Manager to update my TWRP from 2.5.0.0 to 2.6.3.0 but success! Now on to 4.3. :victory:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Cool! If you want to use KitKat 4.4+, you'll need 2.6.3.1 btw
[Verizon Samsung Galaxy S III] J 3 M:
Posted in wrong thread.
[Verizon Samsung Galaxy S III] jimwick:
.......... when I started with Wickedness 4.3 some mods I would try to flash, example KillJoy Red_Skeleton_Warrior_Pulldown.zip, would not install and I thought it was because of the new file system with 4.3, I had a snow day today so I was tinkering with my phone and thought the last this happened to me it was because I upgraded to TWRP 2.6.3.1 and that was the reason my installers weren't working and when I went back down to TWRP 2.6.3.0 everything worked again, this was on the Wicked 4.1.2 ROM.......... So I gave TWRP 2.6.3.1 a try again and this time everything started to flash fine and solved my install problems........... For my phone TWRP 2.6.3.0 dies with the 4.1.2 ROMz. ......
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Hey guys, I have been running this version of TWRP since back in September 2013 when I got my Verizon GS3. Never EVER had any issues or hiccups until tonight. Not a big deal, since my phone is fine, but still I want to know if this is ok or I need to re-install or tweak my TWRP 2.6.3.0.

Okay, I was stupid and tried to install a apk in my system folder and messed everything up. I just got boot loop after boot loop, so I just wiped everything when I booted to TWRP and re-installed my ROM zip and a few other zips. When the phone was done and I hit reboot to system it said "it doesn't appear that you are rooted. Install SuperSU? This will root your phone." I hit install zip and the phone rebooted and is fine now. I figured the phone is rooted, has been since day one, so installing SuperSU again can't hurt. Like I said, my phone is fine and dandy. Now, is this a normal glitch in the matrix or should I do something about this, re-install TWRP, etc?

Thanks so much and TWRP is sent from UP ABOVE :angel::angel::angel::angel::angel::angel:

P.S. I just checked as my phone was setting up and it says "SuperSU Installer: Hit here to install SuperSU and root your device." I just declined that because SuperSU is on the phone already but should I have installed this???
[Verizon Samsung Galaxy S III] appl3mac:
You need to update the binarys thats all its asking try normal if they don't update choose ziip hope this helps.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Never actually updated TWRP binarys before. Do I go through TWRP itself or do I use Goo manager or? Thanks again.
[Verizon Samsung Galaxy S III] chossen:
hello. i downloaded goomanager and i tapped the install openrecoveryscript and it downloads it, installs it, and when i reboot to twrp it is still on 2.5 why? i tried it 5 times by now. please help (i have a nexus 4)
[Verizon Samsung Galaxy S III] lepa71:
Are you unlocked and rooted?
[Verizon Samsung Galaxy S III] unhappybirthday:
This is the TWRP forum for the Verizon Galaxy S3. You should probably post your question in the one for the Nexus 4:

http://xdaforums.com/showthread.php?p=34363480
[Verizon Samsung Galaxy S III] android-incredible:
I installed goo manager on my friend gs3 and tried to make a nan droid backup, but when the phone reboot in recovery the only thing I can see is the green Android and i don't see the backup option.he is on 4.1.2 and the bootloader is unlock, the goo manager version is v2.1.3 I'm trying to update the goo manager but don't let me do it.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
A backup using TWRP isn't good? That's what I always do. Good luck.
[Verizon Samsung Galaxy S III] JRJ442:
Did you install TWRP first? Didn't see any mention of that. Just installing the Goo App doesn't install the recovery.

---------- Post added at 09:11 PM ---------- Previous post was at 08:59 PM ----------

@android-incredible if you haven't, open the goo app, tap the menu button in the top right corner. Then select Install Open Recovery Script. It'll find the recovery for your device and install it.
[Verizon Samsung Galaxy S III] android-incredible:
Ok I downloaded the TWRP now and it's working now, thanks..
[Verizon Samsung Galaxy S III] JRJ442:
Glad you got it!
[Verizon Samsung Galaxy S III] appl3mac:
I apoligise for the late response I don't get update notifications, But what from I have read as far as superSu I have not ever moved to system app. It will probably ask to reinstall superSu and might need it to update the binarys. To flash some of the new roms you need to update TWRP threw Goo Manager to 2.6.3.1 so everything goes smooth for you.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I realized what you meant after I replied to your post. You meant update SuperSU binaries, not TWRP. That I did and all is well. Haven't seen that issue again. Thanks.
[Verizon Samsung Galaxy S III] appl3mac:
Glad it worked.:good:
[Verizon Samsung Galaxy S III] planetf1:
Happily using TWRP on my Samsung i9505 and N8010.

One thing I noticed -- not a TWRP error per se, but surprising was the sheer difference in backup performance between internal storage on the S4. and a fast (supposedly) 64GB sandisk ultra card (should be up to 30 MBps read I think)

Internal - 13 MBps for files, 20 Mbps for image

External - 1 Mbps for files, 6 Mbps for image

... not sure if this is a driver issue in TWRP, S4 hw or a poor performing card -- but it was a retail, boxed, UK, respected retailer purchase so no reason to suspect a counterfeit card.

Backup worked though!
[Verizon Samsung Galaxy S III] bearklaws:
Is there a new recovery 2.7.0.0? Just went to goo manager and hit (install OpenRecovery) and 2.7.0.0 pops up but does not load when I boot in to recovery...not sure I want to try t again...I know I have had to load it a couple times before it would work before...

could not wait ...reloaded2.7.0.0 is up and running...cool...even has right time.
[Verizon Samsung Galaxy S III] Wisiwyg:
Yes... Went here http://techerrata.com/browse/twrp2/d2vzw

New 2.7.0.0 is listed.
[Verizon Samsung Galaxy S III] lepa71:
Can I use goo manager to update it? Thanks
[Verizon Samsung Galaxy S III] Wisiwyg:
I suspect yes...

The home page for TWRP has a full listing of changes for 2.7.0.0 (http://www.teamw.in/project/twrp2)

The prior version that allowed 4.3/4.4 installation support was 2.6.3.1, but it didn't have an entry - minor version. This being more of a major version, it most likely shows up in Goo Mgr. If not, you can download the .img file and flash it with a utility like Flashify out of the market.
[Verizon Samsung Galaxy S III] bearklaws:
good read..Thanks
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Cool! Seems to be running fine for me. I've done three Nandroids, temp flashed a new rom, and renamed backups as well. Because of this update, I now know that we can change the brightness in TWRP lol I always thought it was too bright but didn't know it was customizable.
[Verizon Samsung Galaxy S III] bearklaws:
Can I flash back to 6.3.1...just tried to back up rom and it fails about half way?

installed 2.7 few days ago..seemed to be running fine...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yup, first download the Verizon S3 2.6.3.1 IMG file from the official TWRP website. Then, download "Flashify" from the Play Store and choose to install the recovery IMG within the app. Simple and clean.

Edit: just realized the Techerrata.com link is posted a few posts back. Just download the IMG from there and follow my steps. You'll get the same file from both posts.
[Verizon Samsung Galaxy S III] bearklaws:
right on...thanks

Thank You.....that was very easy...Peace
[Verizon Samsung Galaxy S III] phillipmckinnish:
Did y'all know you can just install Rom installer and flash either one in just one step...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Never heard of it
[Verizon Samsung Galaxy S III] Hobart!:
Couldn't make a nandroid on mine or wife's phone with new update. ..had to flash philz recovery....any ideas why it's happening to some of us???
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Just tried to make a backup after reading your post which oddly I had no problems doing but after a reboot my gmail is force closing upon start up I did not even click on it it unfortunately stopped on it's own. I then launched gmail with zero success and cleared cache as well no dice. I will reboot and try again and report back. Is it still possible to down grade back to 2.6.3.1 if I have the file via the ez recovery app since I have both the app and the recovery file readily available to me. Thanks for any help in advance

---------- Post added at 05:39 PM ---------- Previous post was at 05:17 PM ----------

Ok so I took the gentleman's advice and used flashify and downgraded back to 2.6.3.1 and that was a breeze and thanks for the advice and just in case I forget to mention I am still 4.1.2 and intended to flash a 4.3 rom right now but gmail is still force closing so I am going to restore this same 4.1.2 back up and report back as I never even had a force close until updating to twrp 2.7