yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
I have tried once "TWRP" but did not know how to flash ROM the right way since I came from "CWM" and was used to that, even up to this moment I always wanted to go back to "TWRP" but is there a tutorial something like Step-by-step

that will show how to backup/flash and restore ROM's please help needed.

thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
To backup a ROM (also called "nandroid" or "making a nandroid"):

- Tap "Backup."

- Typically, the default partitions selected are enough. "Boot," "System," and "Data."

- By default, your backup will be named <Date>-<Time>; by that I mean the date and time at which the backup occurs. You can change the name of the backup by tapping "Set Backup Name". The date and time will NOT be saved if you change the name yourself.

- By default, the storage mechanism is the phone storage. If you wish to switch to an external SD card, tap "Storage: Internal Storage (XXXX MB)". A selection will appear allowing to choose "Internal Storage," "Micro SDcard," or "USB-OTG." (USB-OTG is an external storage hooked into your micro USB charging/data port at the bottom. Most likely you will not have this type of storage, as it requires a special connector.)

- Swipe at the bottom to begin the backup.

To restore a ROM:

- Tap "Restore."

- By default, the storage mechanism is the phone storage. If you wish to switch to an external SD card, tap "Storage: Internal Storage (XXXX MB)". A selection will appear allowing to choose "Internal Storage," "Micro SDcard," or "USB-OTG." (USB-OTG is an external storage hooked into your micro USB charging/data port at the bottom. Most likely you will not have this type of storage, as it requires a special connector.)

- The backups stored at the location selected will be displayed. Tap one of these backups.

- Swipe at the bottom to begin the restoration.

To flash a ROM or kernel:

- Depending on the instructions of the OP / developer of the ROM in question, you may need to wipe partitions. Tap "Wipe."

- By default, swiping without choosing "Advanced Wipe" will mimic a ROM's factory reset, i.e. as if you freshly installed the ROM. However, this is not usually what is needed when flashing a new ROM. You should tap "Advanced Wipe." Here's a guide that may help (but others may have differing opinions):

- - For dirty flashing, sometimes used for incremental updates (i.e. updating a ROM without removing your data), or for flashing a kernel: Dalvik Cache, Cache

- - For clean flashing, typically for new ROMs or major updates: Dalvik Cache, System, Data, Cache

- Swipe at the bottom to begin the wipe.

- Tap the back arrow until you are at the home page (or simply tap the home button).

- Tap "Install."

- A storage selection is available at the top.

- A file explorer will appear. Tap on the zip you downloaded, i.e. the ROM zip file.

- If you have additional files to flash, you may tap "Add More Zips." You can see that recovery will allow up to 10 files, as evident by the counter indicating "File 1 of max of 10."

- Once all files have been selected, swipe at the bottom to begin flashing.

To fix permissions:

- Sometimes it may be necessary to do so if apps are not acting correctly. Tap "Advanced."

- Tap "Fix Permissions."

- Swipe at the bottom to fix permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] force70:
Im having md5 issues trying to restore compressed backups with 2.6, normal back ups are no problem?

Anyone else in the same boat?

sent from my i337m, i317m or i747m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
No issues for me ever with TWRP. When you enable compression are you also checking the skip md5 box, too?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] force70:
Nope thats what i was going to try next,i just started using compression. Im assuming i ought to opt out.of md5 checks lol?

sent from my i337m, i317m or i747m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
I always make it check the md5, but honestly I don't even know what it is. And I always use compression, too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] force70:
I can restore compressed without md5 but not with.Strange...

sent from my i337m,i747m or note2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I never use the md5 option enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheDickster:
MD5 is a type of hash. In this case it is being used for file verification.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
Which just makes sure it's a legit file?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
It makes sure the file isn't corrupted in the dl process.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
Ah, okay. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dizzle91:
For the first time i am having a issue with TWRP. I have used it since i got my I747 and it has always worked perfectly..until yesterday..i flashed to stock 4.1.1, ota updated to 4.1.2, rooted, installed Twrp 2.6.0.0 through goo manager, and made a nandroid. Everything was peachy, until i tried to copy the nandroid to my pc. It wouldnt copy, saying a unspecified error had occured and the file could not be moved. I then tried to move it to my ext. Sd though MTP, and then root explorer. Nada. Same error. Any thoughts?

Edit: forgot to mention i have tried with compression and md5 sum checked and unchecked. Same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
If I try and use the "Recovery Install" option in Superuser to update su, it fails once it gets into TWRP and then my phone boot loops. I'm running cm 10.2 nightlies. Anyone else have any luck?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sguerra923:
Just want to make sure if I'm switching from CWM to TWRP and using goo manager to update all I have to do it just download and install correct? Will I have to back anything up or will it be a smooth update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eddalysse:
I too wanted to change from CWM to TWRP I flashed the recovery, followed those steps, when the phone boots, it shows the TWRP blue logo and then reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atrix4nag:
I am trying to change from CWM to TWRP, but everytime i go to recovery, still it opens CWM. I tried morethan 10 times using goomanager, but no luck..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacemanr:
Is there any chance that this backup issue will be solved in the near future? I know nobody like eta asking and it's not like that but just curious if there is an easy solution except changing the permission to 775 (if I remember it correctly) through twrp file explorer coz it didn't work for me :confused:.

Sent from Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Did you wait long enough for Goo to download then install? Goo can be really slow sometimes. Did you see the confirmation message that it installed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
Updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
And installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
What version is showing for you in recovery? I flashed via Goo 3 times now and it still says v2.6, not 2.6.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Excellent, thank you. I switched to this from philz's enhanced CWM, and aside from the ability to delete backups from within the recovery, I don't miss it. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radtech777:
I believe you can do that in twrp as well. I think of you go to Restore and click on one of your back ups it gives you the choice to restore or delete the back up. It's been a while but I'm pretty sure it's there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Shows how new to TWRP I am. :) I'll check it out!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Me too normal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Galaen:
Goo wouldn't install it for me either. Had to install using the image file from their website and terminal emulator.

http://teamw.in/project/twrp2/104

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the_mentor:
What is the Changelog from 6.0 - 6.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rokonacdc:
It's in the OP. It's the second 2.6 post. Typo I guess.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I just looked. It's still 2.6. False alarm. All previous installs via goo were fine so I only assumed it was good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
I installed via Goo and 2.6.1.0 showed up for me. This is odd
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] integraGSR:
+1 I'm showing 2.6.1.0 as well. This update fixed a lot of my hanging up on boot on a lot of 4.3 ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oldbbman:
2.6.1.0 shows up on mine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I even tried again this morning after your post and it was no good. Had to manually install via terminal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
That's odd. Even weirder that it works for some people and not others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Build.prop edits perhaps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
First time it hasn't installed via goo for me.

Stock slim build.prop here so I haven't a clue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacemanr:
In my case no upgrade even goo says that it will upgrade to 2.6.0.1?

Over Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
Ditto
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdagreek:
I tried on both my Galaxy S3 and also on my Nexus 7 2013 ... both on 4.3

ROM downloads but when I reboot into recovery it has not updated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Goo said installed but still said 2.6.0.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
Or if you go into files and find your way to the backups you can move or delete that way as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ovni007:
No issues with me. Just installed and says 2.6.1.0.

Currently using venom 7.1.0

and UCDMG2 firmware
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacemanr:
I had to flash it through twrp and now it's updated, the only thing that makes me feel sad is that my old backups still can't be moved to pc but not a big problem I'm over it.

Over Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iCyanideS3:
Quick question, if I'm on version 2.5.0 and I want to update can I just go onto goo and select install open script recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacemanr:
Yes.

Over Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Similar to others, this is the first time in the year+ I've been using GooManager that it failed to update recovery. I've tried a half dozen times on LTE and WiFi, and though the .img downloaded and Goo reported success, the actual version reported in recovery was still 2.6.0.0.

Perhaps it's a CM10.2 issue? Doubt it, but in any case, I'll give it another go in a bit, and if still fail, I'll just manually dd the image to... (hah - forgot the partition number already :)... mmcblk9?... gotta google it (or maybe look for a recovery-installable version instead). Spoiled by GooManager)

edit: ah... it's mmcblk0p18
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
EDIT: Forget everything I said below. :) Go to this message and download a flashable zip file to upgrade to 2.6.1.0.

I might have discovered what's wrong. I manually installed the 2.6.1.0 that I downloaded from the TWRP site by creating an update.zip file (I took an old update.zip that someone else had created to flash TWRP, and just added the new recovery.img file), and when I rebooted recovery, the version number still said 2.6.0.0. I'm starting to think that the version number in the image wasn't updated (an oversight, I'm sure), so that even though it's really 2.6.1.0, it's actually going to show as 2.6.0.0. This leads me to believe that those who updated via GooManager did, in fact, receive the updated recovery; it's just showing the wrong version number.

Of course, I might be completely wrong. It's happened before. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Not a bad theory, but how does that explain those who report having the updated version number?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacemanr:
That was my thought too, to check it and prove it maybe someone who did it that way should try to make a new nand backup and try to copy it to pc. If it works than it's newer version with wrong name :).

Over Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
That's why I added the caveat. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Theory invalidated :) -- as I can confirm that a successful flash should in fact show the 2.6.1.0 version number, and this is also born out by looking at the string in the img file itself:

$ dd if=openrecovery-twrp-2.6.1.0-d2att.img skip=1814 bs=2048 | gunzip -d|cpio -i --to-stdout sbin/recovery | strings| grep -A1 "Starting TWRP"
Starting TWRP %s on %s
2.6.1.0
1340+0 records in
1340+0 records out
2744320 bytes (2.7 MB) copied, 0.0436367 s, 62.9 MB/s
9512 blocks

Discovered how to suss the twrp version out without actually booting recovery by getting curious myself after somebody asked about it a few months ago. The only "hard" part is finding out where the gzip magic header has shifted to (0x1f8b magic on 2k boundaries))
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Subsequent to my theory being proven totally wrong :), I went ahead and redid the update ZIP file and flashed it, and 2.6.1.0 appeared. (I must have copied the wrong .img file; my bad.) I've attached a flashable update to 2.6.1.0 for those who can't seem to update it via GooManager. I flashed it on my SGS3 and verified that it's working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Yeah, I had to use mobile Odin. I was too lazy to go into the other room to use my computer lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
I did this and A+ never fan of goo, twrp should change and make zip files that we can flash to update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
is it me or the OP doesn't have a changelog for 2.6.1.0? it has TWO 2.6.0.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wash23:
To get Goomanager to install the update, changed the download path in settings to /sdcard/goomanager and then used the menu setting to install the update. Rebooting into recovery then displayed the updated version number.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackmoor2000:
Set my download path to storage/extSdCard/goomanager

Then went to install custom recovery... downloaded & rebooted.

Shows 2.6.1.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
E:/error opening '/data/lost+found'

I found this error to be a real son of a *****, took me about 2 hours to finally figure it out. If I tried to restore it would throw the above referenced error, try to run data restore, then fail. I tried everything to figure it out, I even reverted all the way to 2.4.x.x.x. to see if that would help. The only thing that finally worked was to go into data, find all the lost+found folders and change them to something different. Then the error did not happen during my next attempt to restore and everything was back to normal.

I found this problem in some other device forums/threads, but no one had a definite fix. I also didn't see one reference to it in this thread.

Hopefully this helps someone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Twrp 2.5.0.0 is still better/has less issues than any other version. Went to 2.6.1.0 backed up my ROM flashed a ROM then decided to restore my other ROM and during the restoring of data it failed to restore even after a recovery reboot. Happened on 2 occasions. I'll stick with 2.5.0.0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
2.5 can cause bootloops on certain ROMs I heard

Dab
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Bump 2.6.3.0!! New update, flashing it right away
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Pfft. Late to the party junior. I flashed it successfully through goo manager last night around 6pm EST.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
Unfortunately goo manager is still being screwy. Seems to download fine, says recovery is updated. When I check it, I'm still on the old version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
It worked for me this time. With 2.6.1, not at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Working for me without any issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
I'm hoping that someone with more knowledge than me could upload a flashable zip. :confused:;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
You can download it from the website and use Odin. Goo hasn't worked for me the past few updates. Not sure if it's a 4.3 issue, but the timing seems right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Here y'go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
GooManager FAIL

For the second time in a row (on CM10.2) GooManager failed to update TWRP. GooManager downloads the img and says it was successfully installed, but the version actually shown in recovery proves otherwise.

Last time, I manually dd'd the image to the right partition (forgot the # again) to upgrade, but this time I decided to try some earlier GooManager advice on changing the Download Path settings, and it worked.

So, if you have an external SD card -- and what self-respecting rooted ROM user doesn't? :) -- change the "Download Path" setting in GooManager from the default ('/storage/emulated/0/goomanager/') to '/storage/sdcard1/goomanager/', then Install OpenRecoveryScript again, and reboot to verify that it worked. HTH.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vitanet:
i cant install in my s4!! dunno why i want it! if some can help me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Probably because this version of TWRP is for the S3, not the S4. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cerobles1:
I really wanna try this recovery out. Will this recovery fix the 0\sdcard\ that occurs when flashing AOSP/AOKP roms? Does anyone know of a way to stop that from happening. I would like to run AOSP/AOKP roms but the whole emulated sd card seems like a pain in the butt. Thanks everyone in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
That was happening several versions ago. Maybe you should have a look at the changelog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Agent5150:
How do I fix the date.. twrp thinks its 1970 and expects me to boogie on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pre4speed:
I'm not even on the current version and mine does the same. Drives me crazy. I'm on 2.5.0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cerobles1:
I did look at the changelogs but it seems it's not written in English cuase I didnt understand a word. Anyways, i also looled under settings and advance settings and couldn't find anything that says about \media\ or anything like that. Does it force it to stay regular and not emulate the sd card automatically? How does it work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] highlander07422:
Goo installed it, but when I boot into recovery, nothing happens. The blue text on the top left is there, but screen stays black.

Any help appreciated.

Stock rom rooted with CF autoroot through ODIN. I noticed that after root, the only way to get back to the OS is through download mode- re-boot. Seemed to have lost recovery at that point.

Any fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
I would try goo again but this time don't leave the app. After you hit the download and install recovery script, just wait and watch it download. Then it will say successfully installed. Then reboot into recovery. This has happened to me before. I think it could be when the screen goes off or some small interruption can cause it to fail
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] highlander07422:
Thank you for the reply. I tried this and goo said trying to boot recovery. Goo did not boot to recovery. When I boot manually, just get the booting recovery blue text for like 2 seconds and blank screen.

as of now, There is no recovery.

Help please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] playya:
why dont you just us odin or mobile odin to flash recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] highlander07422:
Is there a .tar file for TWRP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nishchhal:
Yup, bottom of the page.

http://techerrata.com/browse/twrp2/d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdnckreaper:
Weird Situation

I have been using TWRP since it came out for my Cappy. Had it on my Skyrocket and now my S3. I have been flashing the Carbon AOKP Nightlies using TWRP. I know TWRP isn't the culprit for this but (after all of my research) I can't figure out what is.

What has happened is when I updated to the Carbon Nightly that upgraded to 4.3.1 I lost my imei and my nv files in my EFS folder. I was able to get my imei reinjected but can't find anything on getting my nv files restored or reinstalled.

Can anyone here help me get my ATT phone back on 4g instead of it being stuck on EDGE?

Might there be someone that could copy their nv files to a folder on dropbox and send me a link to download or something like that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ill Named:
For some reason on 2.6.3 it fails to create a folder for backups on my ext sd card. Internal works fine. Never had this problem on previous versions. Do I have to delete all previous backups? I only have one in there. Should I just try renaming the existing backup? Any advise would be great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Roseysdaddy:
when i click on the installscript option in the goo app it asks me for permissions, downloads the img file, then does nothing. Goo definitely has superuser rights. What am I missing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
The answer is here in this thread - read back a bit. It has to do with the paths. Something about legacy or emulated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] finneginsfast:
I hope someone can point me in the right direction here. I flash pretty much on a daily basis and for some reason today when I attempt a backup to external sd, I immediately get the dreaded "failed".

E:unable to create folder: /external_sd/TWRP/BAC

E:Failed to make backup folder

Last rom I flashed was one I'd never used before, could it be a problem with the rom or ...?

Any ideas appreciated...

edit:well, I just flashed slimbean and immediately tried a backup with no issues so I suppose it's not a twrp issue. Just never came across this before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Magaboo:
I had the same issue (only seems to be happening on the latest AOKP-Task360 and Cyanogen ROMs). When I re-name the android save before saving it, it will store on the ex- sd. Just deleting the last few numbers (7 or 8) from the default name, will also let you save to the ex- sd. At least that is how it worked for me.

Hope this helps.

Btw. Restore works ok from either SD card
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
When I try to install the TWRP via Goo Manager, I get a 500 Internal Server Error.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] finneginsfast:
Goo just built new servers and have been transitioning for the past week. Still lots of missing files...

Flashable zip file: http://xdaforums.com/showpost.php?p=45677246&postcount=686