yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jhvoorhies:
That means that I must've been lucky then. I had cm10 then decided to go back to my nandroid of stock. I still have my imei after flashing from that stock nandroid to aokp then back to a deodexed stock rom. I used cwm every time.

via my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
I really dont think CM10/9/AOKP are the culprits for lost IMEI, in fact CWM alone may not even be to blame, I think its a combination of factors that can cause IMEI loss, one thing I think is how CWM is flashed to the phone, I've personally only used ADB to flash CWM to the phone, and havent (thank god) experienced the IMEI loss issue, however there have been reports that flashing CWM via odin and then flashing CM9/10/AOKP from stock causes IMEI loss...I'm pretty sure its quite a random occurrence though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Narcistic:
Losing imei is very very very rare or you would see rom threads full of crying... Cm and aokp are probably not the culprits but it's so far the only thing other than cwm that seems to be reoccurring in the occurrences that imei does disappear. Usually it seems by people using nandroid backup somewhere before or after flashing cm9/10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
My 64GB UHS-1 class10 SanDisk IS recognized by TWRP. Did you reformat it FAT32 yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
Nope, I figured I didn't need to since it functions properly with all my apps, but I guess i'll try that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tyshemi:
That's what I had to do as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
What program did you use? Were there any repercussions?

Edit: Posts: 969... hehe *troll face*.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tyshemi:
It's all good I'm being slow tonight lol trollin :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d0cx:
Recovery's working good with my phone, with both internal storage and external.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
I have not been able to figure out how I can push files to my phone while I am in recovery - I used to be able to do this with CWM but I wasn't sure if TWRP offered this optoin?

What steps do I take to make it happen (assuming it is possible)

Everyhting I have tried so far my computer doesn't recognize my phone when I am in recovery -

Is there something special I need to do to make this work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rfb813:
I got a new 64gb sd card for my S3 and inserted it into the phone, The phone recognized the card. However CWM and TWRP did not. I reformatted the card from ExFat to Fat 32 and all has been well. As far as I can see the only loss of capability is the ability to store files greater then 4gb. I formatted the card with my S2; inserted the card and formatted it. By the way once it was formatted to Fat 32 all of the space on the card was available to the S2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duffman14:
Does TWRP see the 64gb card after re-formatting? Mine does not. Not a huge deal, just have to keep flashable zips on the internal instead.

*edit--derp...read up a few posts and see that it is for folks. Not sure if it is worth the effort for me to re-format and copy everything back....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rfb813:
Mine did!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastfed:
I installed this Recovery for a friend of mine, but many roms when going to flash give him an error.

Can someone confirm which recovery from the goo manager it should be?

THANKS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roughneckboren:
I've never had a problem with flashing any ROM. What error specifically?

And you can use the flash able zip I posted a few pages back to install.

jellybeans on the 10.1 tab! my god the sweetness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoonari:
im getting "error 7" while flashing latest miui

update: flashed 2.2.0 from previous page over 2.2.0 i've got from sgs toolkit 2.3 - now its ok
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] V@no:
What's up with all new recoveries and messed up date on backup folders? The first time I've experienced this was when last december LG Nitro finally got CWM ported to, since then every phone I've tried had the same issue. It's like epidemic virus going on here...

Is this so hard to fix or what?

Other then that and no exFAT support (well, and not able turn off screen) this recovery is perfect.

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duffman14:
Speaking of, any word on support for exFAT support?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
exFAT == never (but ext2/3/4 would be nice, since it's free to implement)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duffman14:
Meh, semantics. As long as it recognizes my 64gb memory card and I am not limited to fat32 file system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
TWRP will recognize ext2/3/4 on a sdcard but Android / vold may not handle it. NTFS usually mounts as read only.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Oh? Cool - good to know! The last time I tested ext4 was a few months ago while still on CWM-touch, and both it and CM10 didn't support it, but now that I know that at least TWRP does, I can finally reformat from FAT32 to EXT4 once CM10 adds support. I run linux on my desktop anyway, so in the rare case I need to pop my extsdcard out and into a card reader, I'm good to go, as are MacOSX users, unlike Windoze users who can't handle it without installing a 3rd-party extfs driver.

You should list extfs support as a feature; it's not mentioned in the OP or on your website (though it is mentioned in the changelog of the old version's changelog) :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] finnmacool:
OK, followed the basic goo instructions, menu, installed and am now frozen completely on the teamwin screen. Any reboot or battery pull brings me directly to the frozen screen. what the heck did I do and how can I fix it?

Edit: Managed to get into download mode.

Edit: Flashed using Odin...never had a successful flash but it seems to be working now. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
Yeah i'm also wondering whats up with the date stamps? There isn't any info on why it happens or if a fix is in the works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roughneckboren:
I remember reading about why it was messed up but can't remember where. Just rename the backup and there should be no confusion

jellybeans on the 10.1 tab! my god the sweetness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
Trouble Flashing Themes on Jellybean

I am using the Paid version of TWRP - I know it is free here but I wanted to support the team - anyway - I have never been successful flashing themes on any of the Jellybean TW ROMS I have been on - even though the flash said it was Successful, the ROM was not themed after booting. I tried mounting system and that didn't work either.

Today - I tried flashing a theme after I had installed the most recent Touch version of CWM - and this time the theme worked. I would much rather use TWRP - I like the User interface better and it just seems a more complete recovery to use - except for this issue with themes on JB TW Roms -

any sugestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] V@no:
Unable wipe data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
http://xdaforums.com/showpost.php?p=30950470&postcount=140
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
I appreciate the tip - I downloaded the file (Zip ALlned) but then I realized I don't know how to install it - it said to rreplace the file on my phone with the one they provided the zip for - but they didn't say what folder that file was located in?

This is the instruction they offered: Most of the time if a vrtheme doesn't install it's because of the dynamically linked zipalign binary that's being used. If you simply replace the dynamically linked zipalign binary with the static binary linked below, it will work just fine.

and they provided a ilnk to download the file you need to install -

Any idea what folder I need to replace that file with the one they offered?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
I believe he means to replace the update binary in the zip you want to flash located in the zip file here: meta-inf/com/google/android/update-binary with the one provided. Give it a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
Look in the vrtheme folder.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] turilo:
This twrp has been ported to the I9300 variant and so far loving it :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
Updated to 2.3.0.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d.cortez:
since i'm not a member of GitHub, i wanted to report an issue i encountered using 2.3.0 in this thread. just installed the new 2.3.0 version on my ATT S3, rebooted to recovery and restored a backup from yesterday. unfortunately, my data partition was not restored at all. when the phone rebooted, i was prompted with the setup screen. i rebooted to recovery again and selected the data partition for restore and that didn't work either. so, i reinstalled 2.2.2.0 and restored the same backup and everything restored as i had expected. again just reporting in case there's an issue or a misstep on my part. thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jawonder:
Thanks for your work bro really appreciate it .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Nice, just updated. Awesome to see fix permissions will now only take a few seconds :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
Try the restore again in TWRP 2.3 and copy the log (under advanced) or adb pull /tmp/recovery.log after the restore and before rebooting. I restored data 2 or 3 times successfully last night on my Sprint SGS3 so I can't reproduce.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmacdonald19:
Love TWRP, but I've noticed something. I upgraded to a 64 GB SDXC in my phone and TWRP can't access it. Any ideas why?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d.cortez:
thanks for the suggestion; i will test later today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shoonari:
can you please share with .zip file which i can flash in recovery?

thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
backups made on version 2.2.2 are NOT compatible with new version.. at least for me. i tried ALL my backups.

edit: got one backup made previously to restore..apologies for innaccurate info
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
That's two who are having this issue. I think I am going to hold off upgrading until this is resolved, which I am sure the team will do quickly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d.cortez:
attached are two recovery logs. here are my steps:

install TWRP 2.3.0 recovery via GooManager

use GooManager to boot to recovery and then restore nandroid backup via TWRP 2.3.0. result: restore process completed, copied log file to SD card and then rebooted device. phone rebooted to setup process. the data partition was not restored, e.g., none of my apps, settings, etc., were restored.. see log file titled recovery 2.3.0.log.txt

reinstalled TWRP 2.2.2.0 using adb (e.g., adb shell, then su then, dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18)

use GooManager to boot to recovery and then restore the same nandroid backup via TWRP 2.2.2.0. result: restore process completed, copied log file to SD card and then rebooted devuce. phone rebooted and all data and settings were present. see log file titled recovery 2.2.2.0.log.txt

i hope this is helpful. thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jawonder:
Yep there's a problem with restoring backup using 2.3, even Titanium backup doesn't show apps that were backed up before and when i check Titanium Backup on my SD the are there . Went back to 2.2.2.0. and everything is fine .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
It was very very helpful, especially having logs from both versions. The problem exists only when multiple archives are present. If you can, give this build a try and see if it restores properly. You can find instructions for the manual install on our website. Thanks in advance.

http://techerrata.com/dees_troy/d2att.img
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
made a quick cwm flashable out the new image, flashed it. now gon backup then try it out. ill post results in a few.

EDIT: the new image appears to have restored a previous backup correctly, although i only tried one rt now..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Will we experience similar problems on the d2can version or is this problem isolated to AT&T?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goojman:
Just installed twrp. I'm on AOKP 10/11 build. I copied the rom to internal & external cards. When I go to flash it keeps saying failed.. I keep having to restore from that point. Can someone please help??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwiing:
Not sure why this works, but when I unmount all my partitions, it lets me flash any rom I want. Strange I know, but it's worked 3-4 times in a row now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goojman:
Thanks. Will give it a try. Hope this works cause twrp seems better than traditional cwm..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I honestly had no idea that so many people restored old nandroid backups for this bug to be an issue. I mainly use the backups as "snapshot" insurance against my next major flash going wrong and having something immediate to restore in a hurry, and then I manually go and delete all the older "useless" backups

(... and posting this made me think of another feature I'd like to see in TWRP :) a "Keep Only N Backups" option to delete my old backups automatically after the Nth newest successful new backup, just like how most Linux distributions only keep the 3 newest kernels around as backup.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goojman:
Not sure why this works, but when I unmount all my partitions, it lets me flash any rom I want. Strange I know, but it's worked 3-4 times in a row now.

Just so we're on the same page, you mean unmount system, data, etc... Right?? Can you briefly explain? Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RUNNERX:
I have not been able to flash any rom with this. I have been able to restore fine but that's it. I tried to flash CM and it will tell me it failed (status 7). When I tried Black jelly it runs maybe ten seconds and says it is finished, but when I try to reboot it says there is no system installed.

Tried the unmount method, CM still fails though I was able to flash Black Jelly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwiing:
Yes, unmount system, data, etc. All of them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goojman:
Hey Shwing, YOUR THE MAN!!! Worked like a charm bro!! Thanks again.. Greatly appreciated.. You made my night.. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] V@no:
Please rename button "Format Data" in "Wipe" menu. It's confusing, it not only wipes data partition, but also internal storage! It just wiped all my backups (hopefully I did adb pull on them before try that option).

And yes, it did warned me that it will wipe internal storage (that's why I pull my backups), but since there is no other buttons to wipe just data, it's not very common sense.

BTW, in v2.2.2 this button didn't work, it would give error message about incorrect data size or something similar, v2.3.0.2 works fine, thanks.

P.S.

After flashing the .img the phone stuck at the TWRP splash screen. However after touching the screen it showed the menu. Next reboots showed splash screen only for a second or two.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmbrown81:
Are there steps to go back to the previous twrp? I tried all the unmount steps but I still can't flash a rom. Every time I go back the settings still shows that they are mounted. Also I tried the update binary in the op but I'm not sure if I'm doing it correctly. Does that update replace the one in the rom or does it get added into
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
This will be fixed in the next release slated for Monday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] V@no:
@Dees_Troy:

You seems to visit this topic often lately, would you explain why is the date format in the backup filenames is messed up for so long and nobody seems to care about it?

The clock on top of the screen show correct date, so it can't be that it can't get proper date from the system...

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bori1030:
I restored my back up with the new 2.3.0.0 and after rebooting it looked like a fresh flashed rom it was at the setup wizard with no personal data apps contacts nothing.... anyone else?

restored twice with same results.. thinking about going back to 2.2.2.0 it was flawless for me....

---------- Post added at 05:41 AM ---------- Previous post was at 05:36 AM ----------

just name your back ups its probably why no one really cares about that...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brorex:
Do you have a copy of 2.2.2.0 that you could share? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
If you updated to 2.2 using the goo app, the img file is also in the goo folder on your sdcard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
The stock kernel never saves time to the real time clock (RTC) which is what holds the time between reboots on other devices. The CM team tried fixing it in their kernel but they lost Internet within 24 hours. I will take Internet over a correct date in recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
I think the warnings are sufficient. If someone "accidentally" formats data at this point I won't feel bad about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AngelsNecropolis:
GooManager was able to download the recovery img file but when it tried to install it gives an error stating "Invalid MD5 Sum." I rebooted into recovery and it wasn't installed. I'm using Serenity v1.1 ROM. I noticed this wasn't on the compatible list of ROMs in GooManager. Would this be the reason? Or do I need to follow the manual install method outlined in this thread to make this recovery work?

Also, does this recovery have an install queue option or will I need to install each file/zip individually as was the case for cwm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] V@no:
Thank you for explaining this. My lack of knowledge doesn't allow me understand all that, it seems easy to fix at first, since the time shows correctly on top of TWRP...anyway hope you guys figure it out soon.

True, yet it's confusing, because "factory data reset" with stock recovery deletes both data and internal storage.

In TWRP "factory reset" deletes only cache and data, but "format data" will do as "factory data reset" does. Unnecessary confusing? - yes.

IMO "factory reset" and "format data" should be swapped...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
Newest Update 2.3.1 just came out

What's new in 2.3.1.0:

Unmount system after boot to prevent some status 7 symlink failed errors on zip install

USB Mass Storage code improvements

Better handling of mounting storage during boot for some devices

Fixed a problem with sizes of images (boot & recovery) after resetting defaults

Fixed size errors during backup for some devices on recovery, etc.

Fixed a problem with restoring backups when multiple archives were present
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
TWRP 2.3.1.0 WorkedForMe (without having to manually unmount anything first).

Successfully made a new named nandroid backup ("CM.10.20121010.twrp.v2.3.1.0"), but noticed that "filesystem write rate" stats was a little buggy by showing a huge 4.2billion uint maxval, whereas the "image write rate" below it was correct @ 10MB/s.

Then deleted some old backups, and flashed cm1014 + new 1011 gapps, wiped cache, and rebooted. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] V@no:
I guess USB Mass Storage is not for SGS3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JibbsIsMe:
http://www.mediafire.com/?3oeyftsb52h1f1d - This is a flashable zip of the new 2.3.1.0 TWRP recovery.

There you go! I just took a file from earlier in the thread and updated it. Enjoy!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the_mentor:
I wonder if the latest version 2.3.1.0 fixes the date/time not working properly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jawonder:
The OP explains the date/time situation at #242 above your post .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monk33y:
Awesome, thanks Mate!! Worked like a charm!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Does fix permission actually work on 2.3.1.0? Every time I try it it finishes in 1/2 a second showing on the screen

Updating partition details.....

Fixing permissions....

Loading packages.....

Fixing /system/app permissions....

Fixing /data/app permissions....

Fixing /data/data permissions....

Done fixing permissions.

Done.

With the header at the top saying successful. Now either this is a miracle or it's not really working imo as this takes half a second from start to done. Anyone with any ideas on this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmacdonald19:
Thanks for the quick update to the "not restoring data" problem... working like a champ now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adolchristin:
Does 2.3.1.0 support external sdhc now? Everytime I've selected it previously there have been errors in the log trying to mount sd-ext.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RiPpeR_dUdE:
Per the change log:

-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deoxlar:
This with goo manager is a lot better than cwm. I'm surprised so few use it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] renehd2:
Hello can someone help me please? My twrp doesn't recognize my internal memory. It happens since I rooted the phone, so I dunno what could be the problem..

Any help? I'm using TWRP 2.2 I guess
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roughneckboren:
What version for sure are you using? It says at the top of your recovery screen. If your using an older version update to the newest. See if that fixes your problem. If not you can always go back to an older version. And is it just your internal memory? Because you may have stuff in folders that you may not be seeing. Can you see any internal files or folders. Please give more info so we may be able to help.

jellybeans on the 10.1 tab! my god the sweetness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dees_Troy:
Internal storage is located at /data/media and we usually mount that point to /sdcard. You might try settings -> reset defaults and/or make sure that you're browsing to the correct folder / path.

More info on your "internal memory" here: http://teamw.in/DataMedia
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] graffixnyc:
Having a strange issue. I was using twrp fine with my external sdcard for months (64gb formatted to fat32) I then converted it to exfat but realized that twrp didn't see the card(also the rom I'm working on exfat isn't supported in the kernel I'm using yet). So I reformatted the card back to fat32 but I still cant access the external sd card in recovery. It gives me an unable to mount /external_sdcard error.

When I put the card in a sdcard reader it shows the fs as fat32 when I have it in the phone and mount it, it shows "Generic Hierarchical"

Any ideas on how to get recovery to see the card again?

Here is my recovery.log https://dl.dropbox.com/u/21064708/recovery.log