yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Your issue kinda worries me now, all I do is make biweekly backups although I haven't attempted to restore them yet. I may try fiddling with a restore and seeing if I have the same issue after work tonight.
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Yeah, I hope you don't have the same issue, but then that would mean I only have the problem-_- haha
[Verizon Samsung Galaxy S III] goldsmitht:
did you make the backups through TWRP? Reason i ask, is that i never click on anything to chose this or that when making a backup, i just click on backup. Makes a nandroid of my rom at that moment in time, and when i want to go back, then i can reflash.

HOWEVER: sometimes i have made a backup, then when i restore that nandroid, realize that my backup was made before i added more data. could be why yours didn't restore all the data you think it should have.

but just my 2 cents worth

:cyclops:
[Verizon Samsung Galaxy S III] jackdubl:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Has anyone else made and restored a backup on 2.4.3.0?
[Verizon Samsung Galaxy S III] unhappybirthday:
You guys got me worried, so I just restored 2 different backups that I had made under v2.4.3.0. Both seemed to restore properly after spot checking each. Both auto-connected to a WPA2-PSK network, so system settings look good.

I am running all my wipes/backups/restores directly within recovery.
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Lucky-_-
[Verizon Samsung Galaxy S III] jackdubl:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

With a new build out this seems like the perfect time to test.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Aight folks, I made two backups using TWRP 2.4.3.0: one on March 4th and another an hour ago. Both restores worked as expected and that's even with me doing my normal pre-restore process of factory reset and system wipe. Opening random apps loaded up fine with data, sms all matched the backup data, Super Hexagon still kicked my butt, etc. I'm using a fat32 32Gb sdcard and I'm not sure if anything else is relevant.
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Well, idk what the hell happened to my backups then. I have some numbers on one of those ROMs that I kinda need too-_- haha
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

I'm really not sure either dude, I typically just stay on the same version of TWRP unless there's a huge addition I know I'll need like the support for 4.2 multi-user (/0 files). V2.3.1 worked great which is what I was on before upgrading to v2.4.3.
[Verizon Samsung Galaxy S III] :
today I wanted to flash CleanROM 6 over Synergy R373. As usual, I did a factory reset, wipe cache, and wipe dalvik cache, as well as wipe system, then I flashed CleanROM. I was surprised to find my apps with their data, as well as the call log, messages, wifi, and accounts are still there. The ROM is working perfectly fine. Although I'm happy with that, but I feel something is wrong. Can anyone explain please.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

The factory reset must have failed to wipe your data. Now you love the dirty flash too.
[Verizon Samsung Galaxy S III] :
Weird... Because I did that twice, and I made sure it said successful on the second try.
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

So I tried to backup another ROM and then tried to restore it...and no dice. Three or four perfectly set up ROMs and now I gotta start from scratch. I gotta go to CWM:(
[Verizon Samsung Galaxy S III] Chris Hansen:
I'm in the same boat. It was happening to me on 2.2.2.0, and now it's happening to me on 2.4.3.0.

It's not restoring data, if you look at the log when it does the restore, it says that it takes 0 seconds to do so.

I had found this thread the other day, but their solution didn't work for me. You can try it yourself and see if you recover those numbers. Best of luck!

Sorry to say goodbye as well, but I have to go over to CWM until I can confirm that it's fixed.
[Verizon Samsung Galaxy S III] jackdubl:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Maybe reflash recovery. Mine restored just fine.
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Eh, it's too late. I already deleted the backups. Haha
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

What kind of sd card is it? Format? Do you have another sd card to try testing with?
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

I'm too lazy right now to take this damn case off my phone to look. I don't have any other SD card on hand. Thanks though
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Well until you can try with another sd card, there's not much else to suggest besides using an older TWRP version.
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

FWIW, my successful restores were made from my internal SD card.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

That's definitely a good sign. Both of my restores were through my external sd. I don't really have the space on my internal to keep them there.
[Verizon Samsung Galaxy S III] jackdubl:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

Yes, mine as well.
[Verizon Samsung Galaxy S III] Lt. Barclay:
FWIW I recently restored a backup only to find data was missing. I had previously installed the ubuntu touch preview and someone mentioned deleting the data/ubuntu folder helped. And it did. Restored fine after that.
[Verizon Samsung Galaxy S III] Dees_Troy:
[RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]
[Verizon Samsung Galaxy S III] jackdubl:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Typo in the OP change log. Says 2.4.3.0.
[Verizon Samsung Galaxy S III] barrackOBAMA:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Did a backup on 2.4.4.0

Clean installed ROM.

With gapps

Twrp can't find my backup now. Not in file manager (twrp folder is there but it is empty)

also I lost all my titanium backup data to the same style.

Sent from that young galaxy.

God bless the American people.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Look under /data/media
[Verizon Samsung Galaxy S III] barrackOBAMA:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

No luck.

Sent from that young galaxy.

God bless the American people.
[Verizon Samsung Galaxy S III] andybones:
That's weird, I just tested and made a backup, and rebooted to recovery and was able to find it.
[Verizon Samsung Galaxy S III] jackdubl:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Sure you're looking in the right card(internal/external)?
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Don't forget that if you ever flashed a 4.2 rom that it might have change your internal memory file structure get handy with a file manager and search your internal memory for a folder marked 0 and if that's the case just change the path your stuff is checking for and it should be there no problem (titanium) also just make sure your recovery is current.?
[Verizon Samsung Galaxy S III] keymaster911:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

This is yhe worst recovery ever. Jk. Thanks for your work.

Sent from my SCH-I605 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] bbshopper:
Date says 1970

TWRP is dating all of my files as 1970 and thinks that EST (Eastern time zone) is the same as GMT. Is it not reading the date/time correctly?
[Verizon Samsung Galaxy S III] unhappybirthday:
Yup - known issue. I just put the date into the names of my backups to keep track.
[Verizon Samsung Galaxy S III] jackdubl:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

I had to set my time to some country I never heard of to get it close. And, as stated, name your own backups while in in TWRP.
[Verizon Samsung Galaxy S III] bbshopper:
Thanks for the reply...

Thanks for your help... I really appreciate TWRP, since I have an exFAT SD card and CWM won't even recognize it. The least I can do is name my own backups! Thanks again for all your efforts!
[Verizon Samsung Galaxy S III] ITR218:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Is Goo down? When I run goo and check updates or browse compatible ROMs it won't load?? Thanks in advance.

-> Never mind it's working...
[Verizon Samsung Galaxy S III] Jdelta9889:
Battery Drain

I backed up my system and left my phone at my desk for a couple of hours. I came back and the battery had dropped from 79% to 12%!! The backup only took like 5 min so the rest of the battery drain was from the phone sitting idle.. is this normal?? Any reason why sitting idle in recovery with screen off would drain so much battery?
[Verizon Samsung Galaxy S III] what be up:
is anyone able to mount internal/external sd card to their computer? i can't with mine unfortunately.. it might be something that i did but idk
[Verizon Samsung Galaxy S III] Dees_Troy:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

There's no power management in recovery besides the recent screen timeout. Idle power usage will still be pretty significant.
[Verizon Samsung Galaxy S III] KoolKidd_23:
TWRP keeps failing to restore my backup, I don't know what's wrong
[Verizon Samsung Galaxy S III] capt730:
compression

Has anyone used compression when making a backup? If so, does it take longer to make a backup/restore a compressed backup? I didn't really see anywhere if anyone used it.

Thanks,

Mike
[Verizon Samsung Galaxy S III] neyenlives:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

I have, but I stopped using it. Just takes longer, not sure how much space is saved.

---------- Post added at 04:39 PM ---------- Previous post was at 04:38 PM ----------

Wondering how far we are from having incremental nandroid backups. You know, so it can only backup the files and directories that have changed and appending to a current backup, so we don't have to make a full device image every time.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

I use it every time, saves space. Idk about which method is quicker since I usually perform a nandroid while watching TV.
[Verizon Samsung Galaxy S III] buhohitr:
Compression backup will be slower, specially you have a big rom (a lot of installed apps), I would keep the regular backup, but limit the backup to maximum of 5. So you always have the latest 5 backups and that's plenty. Incremental/differential backup are nice but they are a pain to keep track and restore.
[Verizon Samsung Galaxy S III] neyenlives:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

I did it both ways last night and there was a several hundred megabyte savings in size, but restoring from a compressed backup takes a bit longer.
[Verizon Samsung Galaxy S III] capt730:
Thanks for the input guys. I started using TWRP on my Asus TF300 once it was available and since I went custom, the ROM's were so much smaller the backups weren't really an issue. I use my phone a lot for work, so I am staying with a stock based rom, but they are huge compared to the tiny 150 MB my tab uses lol.
[Verizon Samsung Galaxy S III] Bright09:
Can i swap this if i have clockwork mod recovery?
[Verizon Samsung Galaxy S III] capt730:
You can download the goo manager app to install it, that is the easiest way. I don't believe you can restore a CWM backup with TWRP though.
[Verizon Samsung Galaxy S III] Bright09:
reason why im asking i trying to backup my rom up to my sd but clockwork doesnt support exflat and i need to change cwm

---------- Post added at 09:15 PM ---------- Previous post was at 08:51 PM ----------

i need to change clockwork mod recovery i ment*
[Verizon Samsung Galaxy S III] schneid:
Can one rename the backups anything they want? TWRP, as CWMR, is clueless as to what date it really is. I want to relabel with ROMname and date. Okay?
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Yes, you can rename the folder holding the backup files. Just don't move them elsewhere and expect TWRP to find them.
[Verizon Samsung Galaxy S III] KevinGee:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Is it possible for the recovery to see the files not stored in the /0 folder but stored in the SD card?

When I'm on an 4.2 ROM and I boot into recovery, if I had downloaded a rom and it was on the SD card and not in the /0/ directory, the recovery wouldn't be able to find it until I booted back up and moved it from SD card to the sdcard/0/ folder.

I noticed that on CWM recovery it always stays on the sdcard when I boot into recovery and not inside the sdcard/0/ folder, even while I'm running a 4.2 AOSP rom
[Verizon Samsung Galaxy S III] smelkus:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Yes, you just click the radio button that says "use external storage" when you are on the install menu (among other places).
[Verizon Samsung Galaxy S III] KevinGee:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Omg, I'm so stupid I meant the phone's internal storage not the SdCard.
[Verizon Samsung Galaxy S III] unhappybirthday:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

The recent versions of TWRP look for its path to backups (/TWRP/BACKUPS/1234abcd/) in both the root of the internal storage partition or under a /0 subdirectory. You cannot move them to any other location (except external SD) and expect restore to find them. It is not like ZIP flashing where you can go looking for them.
[Verizon Samsung Galaxy S III] KevinGee:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

(When I say SDcard, im talking about my internal storage and not my external SD card)I wasn't asking about twrp backups. I was asking about when I flash a 4.2 rom, my directory when i open root file explorer is now in the SDcard/0/ folder. But if I were to download a rom to my internal storage, it would be placed in the SDcard and not in the SDcard/0/ folder

So when I boot into recovery and go to install, the directory is also in the SDcard/0/ so the rom that I downloaded can't be accessed because its in the SDcard and not in the SDcard/0/ folder.

I don't know if you understand what I'm saying.

(Just to be clear, I'm talking about internal storage and not external SDcard)
[Verizon Samsung Galaxy S III] smelkus:
This might be the 50th time this link has been posted in this thread, but here we go again http://teamw.in/DataMedia.

If you went from a 4.1.x ROM to a 4.2.x ROM for good, you'd probably never notice much trouble. The confusion comes from people bouncing between 4.1.x ROMs and 4.2.x ROMs. If you're on a 4.1 ROM originally and your TWRP backups are in /data/media/TWRP/xxx, when you flash a 4.2 ROM they moved to /data/media/0/TWRP/xxx. Same is true of Downloads. They were in /data/media/Downloads and now they are in /data/media/0/Downloads. Basically, you would need to move files around and change your default download folder or just move to a 4.2 ROM permanently and delete all the old stuff at the "sdcard"/ internal storage root into the /0 folder. Read and re-read that link and it should clear things up.
[Verizon Samsung Galaxy S III] schneid:
On my S3 FileExpert shows internal sdcard = sdcard0. The physical removable one is extsdcard. Internal storage to me is the ROM where the system stuff is. In RootExplorer under /mht it lists /extSdcard and /sdcard. In GhostCommander it has the same under /mht and /storage but relists the sdcard0 contents again in /sdcard. To each its own naming scheme.

Confusing myself now, but on my S3, I have 2gb RAM, a 32gb internal SD card that I cannot physically access and a 32gb removable "external" MicroSDHC (64gb coming tomorrow). Both are used to store "user" files.

I always put my flash-able stuff on the external one as some ROM installs want you wipe the "internal" one. To me, it is just safer there.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thank you for all of your hard work. This recovery is awesome!

Confirmation: 7JP93758S34115006
[Verizon Samsung Galaxy S III] Dees_Troy:
[RECOVERY] TWRP 2.5.0.0 touch recovery [2013-04-09]
[Verizon Samsung Galaxy S III] schneid:
Is this the expected result? Had previous version. Used GooManager to download this. Did a ten second countdown and then went back to settings screen. I thought it would flash and reboot but nothing happened. Rebooted into recovery and 2.5.0.0 was the version # so I guess it worked.

One worry. The GooManager downloads to sdcard0. Won't a data wipe nuke that. Should I change it to extsdcard? Or, is sdcard0 where it has to be? Or, does it make know difference as TWRP resides somewhere I can't see.

Thanks.
[Verizon Samsung Galaxy S III] Eyalkn:
The new 2.5.0.0 still aborts back to the main screen while picking files to flash in the install screen. It happens intermittently.
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Only the download goes there I thought once it's on the phone it's flashed and installed makes no difference with regards to the path I thought
[Verizon Samsung Galaxy S III] Dees_Troy:
The file gets flashed to the recovery partition. After the install is complete the file on sdcard0 or wherever it went is not needed or used.
[Verizon Samsung Galaxy S III] sob372:
To answer your question only a full wipe will delete your internal memory but wiping data and system to flash will not. But like the guy above.me said you dont need the recovery image once.its flashed u n less you switch to another recovery and need to switch back
[Verizon Samsung Galaxy S III] schneid:
Thanks all. Glad to know it works as expected.
[Verizon Samsung Galaxy S III] andybones:
I haven't had this problem and I've flashed about 10 things..
[Verizon Samsung Galaxy S III] Eyalkn:
I flash a wipe caches zip 3 times before and after each rom or kernel flash and it happens then so maybe the trigger is choosing the same file couple of times.

Do you flash multiple files at once (queue)?
[Verizon Samsung Galaxy S III] Dees_Troy:
Excessive wipe much?
[Verizon Samsung Galaxy S III] Eyalkn:
Lol, I know. Doing anything to get a stable flash.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
This happens to me but only when I am attempting to name a nandroid or after I press reboot system after performing a nandroid. It's not really reproducible but it's kind of a weird quirk. For me, it hasn't been worthy of mentioning since it's random.
[Verizon Samsung Galaxy S III] Danno131313:
It installs very quickly. Also, you can data wipe, the recovery is installed elsewhere, but downloaded to /data
[Verizon Samsung Galaxy S III] zamball:
Anyone having issues wiping cache and dalvik cache? I get a too many programs open error. Any solutions?
[Verizon Samsung Galaxy S III] dreDrennon1:
Everyone i have used does that sometimes
[Verizon Samsung Galaxy S III] KevinGee:
Deal with it :cool:
[Verizon Samsung Galaxy S III] Eyalkn:
I am :) still loving it over cwm.
[Verizon Samsung Galaxy S III] andybones:
No, Never.

I will flash ONLY one .zip at a time, reboot to ROM, then back into Recovery to flash again..

and when you wipe, once it wipes once it did it's job it didn't miss anything, multiple wipes is so unnecessary I find it odd people even do it :confused:
[Verizon Samsung Galaxy S III] jcyoun33:
Depends on the method of wipe. Just don't choose the method that wipes your sdcard. Golden.
[Verizon Samsung Galaxy S III] andybones:
I personally prefer to have a copy of the .IMG for the Recovery version and jsut keep the .apk for installing the recovery on sd card and I install that way. I add all the .IMGs to a thread I made.
[Verizon Samsung Galaxy S III] Feche:
Data and Cache wipe is FULL? deletes everything? like this http://xdaforums.com/showthread.php?t=1818520
[Verizon Samsung Galaxy S III] SpyroDazee:
I read somewhere that the newest version of twrp also does efs backup. Is this true? That'd be great, so I can have an extra line of defense incase the efs backups I have fail to install :D
[Verizon Samsung Galaxy S III] lvgdgts:
This may have been answered, but I have scanned the bulk of this thread and didn't see the answer.

I have TWRP 2.4.3 on my S3. I have used GooManager to download both 2.4.4 and 2.5.0, but it doesn't show that they were installed. When I boot into recovery, TWRP always states it is version 2.4.3. Can someone help me through this? TIA.
[Verizon Samsung Galaxy S III] Badger50:
Download EZ recovery from.the play store. Then after you open the app to initialize the file on your sd card, you can drop your recovery files into the EZ file. Then open up the app, hit custome, browse, and go to the EZ recovery file. Select which recovery file you want, and flash it. Sounds a lot harder than it really is. Good luck :)

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] Badger50:
The gs3ezrecovery file is where you will put your downloaded recovery files, which will enable you to flash them :)

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] lvgdgts:
Well, I did this and now I can't boot into recovery. I get the initial screen with the blue type at the top, then it turns off. If I pull the battery and try to turn the phone on, I get the same response. Ugh. I guess I'll have to Odin back to stock, but that won't fix the recovery issue.
[Verizon Samsung Galaxy S III] Hybridnoob:
Use GooManager and hit menu - install openrecoveryscript. That should overwrite your recovery and fix your problem. That's the only way I update my recovery.
[Verizon Samsung Galaxy S III] Badger50:
I would like to offer my sincerest apologies my friend if I caused you any unnecessary grief. I've use EZ-recovery many times without difficulty. I like the app because it allows my to switch between TWRP and CWR on the fly. The problem may have occued because your goo manager files didn't jive with the EZ app. There is a thread on XDA that has all of the recoveries in .zip format, which makes it easy to have all the recovery files in one place, and ready for flashing. Again my apologies my friend :)

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] Óðinsdagr:
Coming from a different device I grew accustomed to zipped up version of twrp, do you have a link for that thread NY chance. Tried searching not finding, don't think I'm using the correct key words
[Verizon Samsung Galaxy S III] Badger50:
Here is the link up all of the custom recoveries.

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

They actually come in .img files. After you download them, then put them into the EZ-recover file on your SD card, then select the one you want from the custom, browse file and flash away. The other guy was right as well. If your using goo-manager, just hit the menu button on your phone, and select install. Hope you get it working my friend. Sorry if I messed you up. Good luck :)

Sent fom my HyperDriven Mobile Beast Device :)
[Verizon Samsung Galaxy S III] unhappybirthday:
One other thought: Did you modify the device name in your build.prop file? You might do this manually (or with an automated tool) in order to install Google Wallet. This would cause GooManager to pull the wrong recovery files for your device.
[Verizon Samsung Galaxy S III] lvgdgts:
Thanks. I had to odin back to stock and redownload EZ recovery, but this explanation got it done. I'm back up and running.

Love this community and all the devs here!
[Verizon Samsung Galaxy S III] Badger50:
Glad to hear it my friend. Sorry for the inconvenience, and thank you for your service to our country :)

Sent fom my HyperDriven Mobile Beast Device :)