yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] lvgdgts:
That's a great point that I would not have thought of. I use Hyperdrive, which names the device as an SCH-i605, but I rename it to a Galaxy Nexus so that Wallet will work. Either of those might affect the recovery files.
[Verizon Samsung Galaxy S III] Blaiser47:
So I have been using twrp for quite some time and love it! After the 2.5.0.0 update looks like the UI switched a bit which I mostly love, but i am having a little trouble understanding a few things. 1.) with the new factory wipe or advanced wipe/format set up, where has the wipe internal SD gone? From what I can tell factory wipe doesn't wipe internal, advanced, with everything selected might, but just says micro SD card (i assume external?) so presumably internal is also wiped? 2.4.0.0 used to have external and internal options? 2.) does the file manager allow us to browse anything? I just has a blank screen for me and I cant actually browse to anything?

Thanks for any help!
[Verizon Samsung Galaxy S III] Badger50:
Internal storage is now Micro SD card. I was confused at first as well so don't feel too bad, but it will wipe your internal storage clean as a whistle :)

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] kenbrownstone:
Anyone having problems with it changing to stuff on its own?
[Verizon Samsung Galaxy S III] Badger50:
Changing to what stuff? I see you've come over from the Razr side of life Kenny :)

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] iclickjohn:
Here is my list of errors when trying to do a Backup in 2.5

[backup started]

backup folder/ external_sd/twrp/backups/4916

backing up system...

generating md5

md5 created

backingup data

breaking backup file into multiple archives

E: Error tarring split files

updating partition details

E: error opening'/data/lost+found/#12#12/#12/#1

E:error: too many open files

E:error opening /data/lost+found~0/#12/#12/#12/

E: error: too many open files

E: error opening /data/ lost+found~1/#12/#12/#12/

E: error: too many open files

RED FAILED

END

Then I switched to internal card for storage

[BACCKUP STARTED]

*Backup folder: /data/media/TWRP/BACKUPS/49160

BAckung ups System/ / /

Genreating md5

MD5 Created/

Backing up Data

Breaking backup file into multiple archives///

E:Error tarring split files

END
[Verizon Samsung Galaxy S III] kenbrownstone:
When in twrp it will change screens by itself...I will be bought to install then it goes back to main page. It also will do it if I'm in file manager.Also in advanced wipe. Thought maybe it was a bug cause its never done that....And yes loving the S3. But will always remember the Razr that I lost my cherry to...:)
[Verizon Samsung Galaxy S III] jpmcnown:
Against my better judgement, When wiping my phone for a clean flash, I also selected to wipe "micro sd", and POOF there went both my internal AND EXTERNAL memory, clean as a whistle. So thanks.
[Verizon Samsung Galaxy S III] Badger50:
Oh man I'm sorry my friend. I certainly was not trying to give anyone bad advice :( Hopefully you made a back up of your external SD card before you started. When I wiped my internal storage using the micro SD card selection, I forgot to mention that I removed my external SD card before I wiped. A good lesson for all of us I guess. Sorry if I caused you any undue grief my friend :(

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] jpmcnown:
Lol, no worries. I actually reverted to 2.4.4.0, before I read your comment, and thought, sweet, I can wipe the internal after all. lol. I make sure to backup important stuff online(in 4 locations, lol) My RomToolbox App backups went bye bye though. Agreed that it's a good lesson. I'm totally taking my automatic backups to another level now.....well, after I set it all up again. Seriously though, no biggie.
[Verizon Samsung Galaxy S III] Badger50:
Thanks for understanding my fellow Kansan :)

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] LaserEyeballs:
Having a problem with the factory reset where even though it states it won't wipe internal memory it definitely is. Never happened before today. Crazy thing is I flashed a rom earlier in the day wiping before and my internal wasn't wiped. I went back in this thread far enough to cover the latest version and didn't see anything regarding this.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, did you flash an AOSP rom? If so, look in data/media for your internal storage. I'm still on 2.4.4.0 or something like that so I haven't updated yet. Normally I would say your issue sounds weird but the previous ten posts are confusing but seem related to your issue. I should probably test the two settings this weekend when I have enough time.
[Verizon Samsung Galaxy S III] LaserEyeballs:
I did flash an Aosp rom earlier. Switching from a TW rom. After I tested that Aosp rom I restored my previous TW rom. I was trying to flash another TW rom. I would dislike it very much to have to go back to CWM. I thank you for your input
[Verizon Samsung Galaxy S III] kenbrownstone:
Anyway to back to 2.4.4.0 ? The newest one is very buggy for me
[Verizon Samsung Galaxy S III] Badger50:
If you look under the theme and app section, look for "Custom Recoveries". You will find all the TWRP and CWR recoveries that you can flash with EZ-recovery app :)

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] jpmcnown:
I went back to 2.4.4.0 I think I've had success using the "custom" option in EZ-Recovery to flash a .img maybe twice, in the 50 or so times I've tried it. Of course it "says" that if flashed, but you reboot to find nothing has changed. It used to be the ONLY reason I had EZ-Recovery installed on my phone. Though requiring a pc, I still think the best bet is to download the .tar of TWRP, and flash it in download mode, via Odin.
[Verizon Samsung Galaxy S III] kenbrownstone:
Y'all think I should just try to flash the newest one in odian again? Maybe just a bad down load?
[Verizon Samsung Galaxy S III] Will32:
I rooted and unlocked my son's gs3 last night but I got an error when trying to backup his stock rom with twrp. The error said that it failed when trying to make the twrp directory on my external sd.

Has anyone had an error like that?

When I tried to backup to my internal sd everything went fine. It made the twrp folder and made the backup. One thing that was weird was that the stock backup was almost 3gb.
[Verizon Samsung Galaxy S III] unhappybirthday:
In TWRP, go into Advanced --> File Manager (or something like this). Can you browse into your external SD? If not, are you on the latest version 2.5.0.0?

Stock ROMs are pretty big but you might not have the compression option enabled (in the Backup dialog).
[Verizon Samsung Galaxy S III] Will32:
I figured out the problem with twrp not creating a folder. I used es file explorer and tried to make the twrp folder manually and it said there wasn't enough memory to make a folder. We deleted some stuff and I was able to make a folder, so I assume twrp will make a folder now although I haven't tried it yet.

Also, you're right, compression wasn't enabled. Does enabling compression cause any issues? Is there a downside to enabling compression?
[Verizon Samsung Galaxy S III] APeaceofStrange:
Ya

Did you ever solve this? I'm having a similar issue

Edit: Nevermind, think I got it fixed
[Verizon Samsung Galaxy S III] unhappybirthday:
Compression likely adds a bit of time. If you use a utility app that pulls apps or SMS messages directly out of backups, it will have to decompress it first, which will require extra space.

I always ride the edge of my available space, so it's compression for me. Never had a problem over many backups and restores.
[Verizon Samsung Galaxy S III] x Jumpman23 x:
How? Please let me know, having this problem too
[Verizon Samsung Galaxy S III] APeaceofStrange:
I flashed cwm touch recovery, then flashed back to twrp. Problem was gone after that.
[Verizon Samsung Galaxy S III] ShhImSleeping:
Has anyone had issues with 2.5.0.0 when trying to do make a backup, and TWRP saying your data partition is insanely huge?

Example - what twrp is currently telling me:

- boot: 10mb

- system: 883mb

- data: 1273148mb

Has anyone else experienced this? It only does this for the data partition, I haven't found any other issues with its size reporting. Although it takes, what feels like hours, clockwork backs things up just fine... but I can't stand clockwork's slowness.

EDIT: Well, it only seems to do this with synergy's rom.
[Verizon Samsung Galaxy S III] buffal0b1ll:
I can't remember the last time goo manager scripted flash ordered zips worked.

It'll backup, but it never installs anymore.

2.5.0.0 d2vzw
[Verizon Samsung Galaxy S III] jackdubl:
Are you referring to installing/updating recovery thru goo manager, or are you talking about something else?
[Verizon Samsung Galaxy S III] buffal0b1ll:
When I try to use GooManager to Order and Flash zips with checkboxes to Wipe Caches and Make a Backup. The backup works everytime. The ordered zip flashing part fails more often than not.

d2vzw CarbonRom 5/15
[Verizon Samsung Galaxy S III] Bright09:
How do i change the time and date on my twrp im using the last build before this one i keep seeing my time and date wrong from 1979 lol when i back up my rom but ive been naming them time and date thought
[Verizon Samsung Galaxy S III] what be up:
Wrong date and time is a known issue for the gsiii. It's something that apparently can't be fixed, I'm not sure of the specifics.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Personally, I name my TWRP backups with the date before doing the actual backup. Being able to name backups is the main reason I switched to TWRP.
[Verizon Samsung Galaxy S III] ddggttff3:
If you run CM10.1 nightlies, this has been fixed. It is a issue with the stock samsung kernel, and the phones RTC (real time clock).
[Verizon Samsung Galaxy S III] what be up:
Hm, I did not know that, good to know
[Verizon Samsung Galaxy S III] Bright09:
thanks for the reply i thought it had to be with something with it glad that i name and date them :) and is it worth updating twrp from last build jw
[Verizon Samsung Galaxy S III] CaliLove310:
I'm having this problem with paranoid android. Did you get it fixed?
[Verizon Samsung Galaxy S III] buffal0b1ll:
No. I just flash in recovery when the scripts fail.
[Verizon Samsung Galaxy S III] gtdtm:
Hey Dees,

I was wondering if you guys had considered whether it would be possible to put a pin to log into recovery? I'm not overly paranoid, but if by chance a member of law enforcement had my phone and was familiar with custom recoveries, they would have some limited access to my files through the file manager. I don't know if that's really an issue or not, but I was just thinking about it.
[Verizon Samsung Galaxy S III] gorgarath:
I've yet to encrypt my card, but I'd assume that you would need to enter your credentials when accessing an encrypted card for your backups wouldn't you?
[Verizon Samsung Galaxy S III] jakereeves31:
You must me a secret agent with important stuff on there, huh?:eek:

Signature:

Please read this:https://plus.google.com/app/basic/stream/z12bhtd4nwvmihxsi232wldpfo3mfj3pl04
[Verizon Samsung Galaxy S III] gtdtm:
As I said, I'm not overly paranoid. I guess I could have framed it as: If my phone were stolen by somebody familiar with rooting and such. I use a "secure" lockscreen, but have just wondered about who could access what through access to my custom recovery.
[Verizon Samsung Galaxy S III] gdavis2570:
I downloaded goomanager from the play store. When I open it it says find compatible ROMs can I download and flash from there. I have a Verizon S3
[Verizon Samsung Galaxy S III] unhappybirthday:
Someone can jump in if I'm wrong, but I think if you are working with an encrypted device in recovery, you are prompted for the password there as well.
[Verizon Samsung Galaxy S III] KevinGee:
Why when I boot into recovery, I get

Updating partition detail

E: opening '/data/lost+found

E: Error not a directory

E: opening '/data/lost+found

E: Error not a directory.

Is that a problem? Because I also get something like that when I do a factory reset or a nandroid backup.
[Verizon Samsung Galaxy S III] gdolla3:
This also happens to me whenever I am clearing cache and dalvik.

In addition to this, my nandroid restore always crashes on the data restore. Is there a fix for this?
[Verizon Samsung Galaxy S III] KevinGee:
Yeah same here, But the thing is that I could restore my backups previous before the most recent backup

Sent from my phone
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Will there be any more updates to galaxy s3 twrp or is this which it is it's final stable release 2.5.0
[Verizon Samsung Galaxy S III] kenbrownstone:
I love twrp...but I hope its not the last it has a lot of bugs.. My twrp on the razor was flawless. This twrp has caused me to erase my extsd 6 times. It pushes things on its own. Also it will change pages on its own and the screen will lock up without wanting it to
[Verizon Samsung Galaxy S III] HypostaticOnion:
Bad flash maybe? Haven't had any issues with mine and that's all I've used on this phone.
[Verizon Samsung Galaxy S III] jmorton10:
Can somebody please repost the boot animation zip??

I have been trying to DL it for two days with no luck...........
[Verizon Samsung Galaxy S III] s197:
Any chance we get a kexec version of this recovery? Right now there's only one version, and it's clockwork.
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
http://xdaforums.com/showthread.php?t=1773514

Sent from my Commodore 64..

READY.

load"*", 8,1
[Verizon Samsung Galaxy S III] dmrnhs:
why is my recovery flickering the display? everything works but the screen flickers/blinks while I'm in recovery
[Verizon Samsung Galaxy S III] JMink:
What needs done if I already have clockwork installed? Do I need to flash back to the stock recovery first or can I just install this from goo over clockwork?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] s197:
You should be able to just flash right over clockwork. If it doesn't take for whatever reason, flash TWRP, reboot, flash TWRP again and you should be good.
[Verizon Samsung Galaxy S III] guyd:
Same here. I finally realized that the VZW SGS3 formats the 64GB sdxc Card as exFAT, and no recovery could use it for my backups. Windows 7 would not allow me to reformat it to FAT32 either, so I pulled out my old trusty HTC Sensation and formatted it in that (which made it FAT32). TWRP 2.2.0 works fine on the extSdCard :)
[Verizon Samsung Galaxy S III] seth.i.simmons:
Anyone else having issues seeing zips in TWRP? I cant seem to see anything, either on 2.1.8, 2.2.0, or Kexec 2.2.0. Not sure what the heck is up. No zip files will show at all, either in the file manager, or when trying to install. Any ideas?
[Verizon Samsung Galaxy S III] NxtGenCowboy:
I can see my backups just fine, Internal and External.

Make sure your SD is not formatted to exFAT
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
Anyone know how to get rid of the Samsung Custom boot screen with the white unlocked padlock?
[Verizon Samsung Galaxy S III] landstander:
For several months now, I've been looking for a recovery which could play nicely with the encrypted data partition on my Galaxy Nexus. AWESOME!!! ::)
[Verizon Samsung Galaxy S III] 4FatSno:
I thought CWM was cool...but TWRP is....awesome!

Thank you!

sent from outerspace
[Verizon Samsung Galaxy S III] jnehama:
Try putting the zip files on the root of your internal sd card(/mnt/sdcard) then in recovery click internal sd card and look for data/media all the way at the bottom. That's where I found them. Worth a shot.
[Verizon Samsung Galaxy S III] seth.i.simmons:
Yep, that worked! Really odd way of mounting it, but it works. Question though. Anyone been able tovuse the kexec version to boot into a kexec kernel?

Sent from my SGS3
[Verizon Samsung Galaxy S III] Stam2000:
Been wondering the same thing
[Verizon Samsung Galaxy S III] timothydonohue:
Busted. At least for me. :( every time I try to get goo to work, I get a "server is broken"type of message

Edit: worked !!! Love it! Nice work, tw
[Verizon Samsung Galaxy S III] silver04v:
Can anyone help me out please. I'm on twrp installed from vzw ez recovery.

I was able to boot into recovery fine and make a backup.

My issue is like the users above, I cannot see my internal SD card if I go into install to install a zip. If I click on sd card I get nothing.

I go back to the root of the phone, then go to data then media and that is were the contents of the sd card is?? Thats very odd.

So this is normal and I can just install the zips from there?

also

when i factory reset/clear data, this isnt going to erase my zip file on my internal right?
[Verizon Samsung Galaxy S III] Dees_Troy:
The SGS3 devices don't have a separate partition for storage (just like the Galaxy Nexus and most Android tablets). The "/sdcard" folder in Android is a symlink to /data/media. At some point I plan to modify TWRP's handling of dual storage devices so that it creates the same symlink, but until last week I didn't have a dual storage device that used /data/media to test with.
[Verizon Samsung Galaxy S III] silver04v:
Ok, so that is normal and fine to go that route to flash with. How bout wiping? Wiping won't affect that data/media area right?
[Verizon Samsung Galaxy S III] GRBlitz:
How do I do a "full wipe" using twrp? The kind of wipe I would need for a new ROM? What do all the wipe functions do?

Just trying to be careful :)
[Verizon Samsung Galaxy S III] kenbrownstone:
I've redone It several times. .it could just be my phone...I've even went back to the one before this edition.
[Verizon Samsung Galaxy S III] sbenson1226:
I came to the GSIII from the Gnex and I think I'm seeing some strange behavior with TWRP. I could be crazy, but I'm just looking for some validation...

On my Gnex, when I made a recovery backup I could use a file explorer to view my backups. The location was /storage/sdcard0/TWRP/Backups/XXXXXXXX/ then all of my backups would be displayed. I would usually keep 1-3 backups at all time.

Now what's different? On my GSIII, when I navigate to that folder, all I see is the original stock rooted rom backup that I made right before I moved on to CM10.1 from stock Touchwiz. I don't see the other two backups I've made.

When I reboot recovery and tap restore, I see the other two missing backups, however the original backup is not listed...

If I go advanced > File Explorer and then navigate to /sdcard/TWRP/Backups/XXXXXXXX/ I then see my original stock recovery image. I'm not really sure what's going on here? Why can't I view my backups with a file explorer like I could on my Gnex? Are they being backed up and saved somewhere else that I'm not aware of?

Is this possibly a permissions issue?

Thanks in advance for any and all input.
[Verizon Samsung Galaxy S III] kenbrownstone:
The same thing is happening to me ... Files are disappearing ..Then a reappear when I close and then go back into twrp.
[Verizon Samsung Galaxy S III] funnyperson1:
I haven't had any issues with extsd being erased, but the random freezes and random jumping back to home screen are definitely a problem.
[Verizon Samsung Galaxy S III] sbenson1226:
I did some digging and found my ***New*** backups here: /data/media/TWRP/BACKUPS/xxxxxxxx/

I have my two most current backups located here.

My original backup is still here: /sdcard/TWRP/BACKUPS/xxxxxxxx/

Why are they split up like this? Can I merge one into the other?

Is this related to the whole sdcard0 issues when going from 4.1x to 4.2?
[Verizon Samsung Galaxy S III] muiriddin:
Recovery not successfully factory resetting and no error message!

Just as a heads up, I have seen some very strange behavior that I originally thought was 2.5.0.0 behaving incorrectly and later it appears as if it was a permissions issue.

When I factory reset the phone, it would not reset. I typically do this in the recovery before flashing a rom. In this case the new rom didn't come up clean (asking me for my google account) it came up with the upgrading message...

So I initially thought it was rom specific and ran with the obviously dirty flashed device for a while. Had a problem and then tried factory reset from TWRP again, this did not reset the device. Then I tried a different recovery which did not reset the device. Then I tried to reset from within the phone and the same result (no reset occurred).

Further strange testing resulted in a device that would not reset.

Finally, I reset permissions.... Once I had done this and then rebooted to recovery the phone successfully factory reset...

The questions I have that I need to take a look around to answer are.

Does the factory reset in TWRP validate that permissions are such that the command can succeed before it wipes? If they are set wrong does it not report an error? or am I chasing smoke which is unrelated here. I now have a device which has been reset, I just want to make sure that someone else does not spend as much time as I did chasing this issue if possible
[Verizon Samsung Galaxy S III] HypostaticOnion:
Yes it has to do with the SD card 0 folder thing
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Just making sure this got quoted correctly...
[Verizon Samsung Galaxy S III] manatti:
I cannot believe after so many versions this wiped my sd card. So garbage. I remember donating when this started, tried going back to it, and lost everything. Nice
[Verizon Samsung Galaxy S III] ylexot:
It shouldn't have wiped your SD card. You must have done something wrong.
[Verizon Samsung Galaxy S III] sbenson1226:
Care to expand on your random rant?

Your own ignorance is most likely to blame...

Sent from my Galaxy SIII
[Verizon Samsung Galaxy S III] silver04v:
I've had my sd card become corrupt after installing my last rom and then again when I installed a kernel. This is one version 2.4.4. Happened shortly after rebooting. First one immediately after install and second was a little while after. Not sure if it was related or my sd card is calling it quits?
[Verizon Samsung Galaxy S III] unhappybirthday:
SanDisk ultra?
[Verizon Samsung Galaxy S III] silver04v:
No it's a pny 32gb
[Verizon Samsung Galaxy S III] RoxRedEye:
Is there anything specific I should be doing with TWRP if I'm coming from TouchWiz MB1 to an AOKP 4.2.2? My recovery is acting weird and giving me messages I never seen. A mesaage I'm getting is "E: error opening 'data/lost+found' E: error: Not a directory. I seen a post on the T-Mobile S3 where the developer told someone with the same issue to back up internal storage and format data. Is it possible to flash back and forth between TouchWiz and AOKP?

EDIT: I backed up my internal storage and formatted data like Dees_Troy recommended from a T-MOBILE S3 thread. Working fine again. Again, is it possible to flash between Touchwiz and AOSP without having this issue happen again?
[Verizon Samsung Galaxy S III] KevinGee:
I can't restore backups anymore, it keeps telling me "failed" right after it restores system and it restoring backup. It says "cannot open /data/lost+found" and it just fails
[Verizon Samsung Galaxy S III] Hybridnoob:
Are you restoring from an external SD? I had that issue on my S3 when I attempted to restore from my external SD, but once I moved my backup to my internal SD, it worked.
[Verizon Samsung Galaxy S III] KevinGee:
Yeah I am, you think that's the problem?
[Verizon Samsung Galaxy S III] Hybridnoob:
That was the problem for me. Try copying your backup to your internal SD. I bet it will restore.
[Verizon Samsung Galaxy S III] KevinGee:
Okay I did that just now but it still says

"E: Error opening ' data/lost+found"

EDIT: Well it actually restored it this time without fail.
[Verizon Samsung Galaxy S III] Hybridnoob:
That's great! I have that same message too, but can't get rid of it. Regardless, everything but the external SD restore works for me. I'm glad it's working now.
[Verizon Samsung Galaxy S III] KevinGee:
Thanks bud, idk but that never came to mind, since I have a 32gb SD card with 12gb free and only about 3-4 GB of internal storage and TouchWiz roms being +1gb in size. I would only backup to sdcard

But I'm glad it works now. :thumbup::D