yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Droidriven:
No, the Verizon S3 with 4.4 has a locked bootloader and it can not be unlocked by any means, you can't flash TWRP on devices that have a locked bootloader.

This is available for the Verizon S3 devices that still have 4.3 but didn't take the last 4.3 incremental update or the 4.4 update. Devices that have the updated firmwares all have locked bootloaders.

The only thing the Verizon S3 with locked bootloader can use is SafeStrap recovery and the modified stock Touchwiz(TW) ROMs.
[Verizon Samsung Galaxy S III] Ibuprophen:
Just an FYI in case you weren't aware.

TWRP v3.3.0-0 was just released.

Some notable changes were made too... :eek:

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
[Verizon Samsung Galaxy S III] Ibuprophen:
Just providing some additional information about the recent TWRP release.

The following are 2 locations reflecting any form of recently released Changelogs...

1) TWRP does provides an (uncomfortably brief) Changelog/bullet list here:

https://twrp.me/site/update/2019/04/15/twrp-3.3.0-0-released.html

2) The following is an excellent article with an outline of the new changes by the XDA News Editor in Chief:

https://www.xda-developers.com/twrp-3-3-0-release/

Enjoy and Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
[Verizon Samsung Galaxy S III] Ibuprophen:
I just wanted to let everyone know that TWRP v3.3.1-0 was just released a few days ago for this device.

The following link is to their brief Changelog /Announcement regarding this release.

https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html

Enjoy and Good Luck! :)

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] ShapesBlue:
I'm shocked they are still supporting this phone. It's been years since I've even touched my S3. At this point I don't even know where it is.
[Verizon Samsung Galaxy S III] Droidriven:
Even the S2 still has a very active development community, I would say it has become the Sammy that wouldn't quit, I even have one that was found 6 years ago after being ran over in a parking lot with a busted screen that still works like a charm other than the screen, lol.
[Verizon Samsung Galaxy S III] ShapesBlue:
I miss my S3 but I wouldn't trade it for what I currently have. It was my 2nd smartphone after the HTC thunderbolt. Someone walked me through rooting the TB. It was relatively easy to root the S3. I'm just surprised there's a demand for this device as it's coming up on a long time since this came out
[Verizon Samsung Galaxy S III] Ibuprophen:
I've actually got 2 d2vzw devices still with 1 of them that has an Unlocked Bootloader and the other has a Locked Bootloader.

I also have 1 jfltevzw (Verizon GS4) with a Locked Bootloader and 2 GS5 devices with 1 being a kltetmo and the other being a kltevzw (Both with an Unlocked Bootloader).

I'm actually considering another GS5 variant (maybe a G900F) and/or one of the GS9/GS9+ variants (hopefully an international one that I can unlock its Bootloader as well).

The d2vzw device is still a very reliable device I keep with the others only for testing purposes and such.

It doesn't look very promising (personally) that anyone will be able to either create or obtain a Kernel to allow for any Custom Firmware above the LineageOS 14.1.

I can only keep my fingers crossed for this... LMAO! :eek:

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] ShapesBlue:
I've always had my S3 unlocked bootloader. I only buy phones now with unlockable bootloaders. Don't buy carrier branded garbage either
[Verizon Samsung Galaxy S III] ST Dog:
There wasn't a non carrier GS3 in the US, it was a few years before the good non carrier phones started appearing. And only the Verizon version would work on Verizon.

But once unlocked/rooted all the bloat could be removed.
[Verizon Samsung Galaxy S III] Ibuprophen:
Both of the GS3 devices still work with the Net10 BYOP program.

Net10 leases the usage of the various Towers for the major brands in the US.

I've never had a contract with Verizon Wireless directly. I've always used Net10 where the device used the Verizon Towers via the Net10 Service.

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] ST Dog:
Not for long, at least not on Verizon side as they are going VoLTE only at the end of the year.

Guess AT&T/TMO side for 3G for a while longer, but I don't think it supports LTE that way. The stock ROMs didn't.
[Verizon Samsung Galaxy S III] Ibuprophen:
This only affects new services for device as of the affected date. Devices that had service already won't be affected.

I had looked this up when I had heard about it.

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] ST Dog:
No, Verizon is supposed to be shutting down the CDMA towers at the end of December.

The no new activations was last year in July for Verizon customers, but MVNOs got a few months longer.
[Verizon Samsung Galaxy S III] Ibuprophen:
I was referring to those who had their device activated before that date.

According to the following link...

https://www.verizonwireless.com/support/knowledge-base-218813/

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] ST Dog:
Right and they are retiring the network at the end of Dec 2019. It will be gone come 2020. So nothing w/o VoLTE will work.

(Unclear if they will shut down LTE data only phones, or just no voice/text)

The end of 2019 has been out there for several years.

From that page (the first sentence)

"Verizon Wireless is retiring its CDMA (3G) network at the end of 2019."

Also AT&T has said the end of 2022 for their 3G shutdown (including so called 4G that's not LTE). They will be LTE only then

https://techblog.comsoc.org/2019/02/22/att-to-shut-down-3g-network-in-2022-verizon-at-end-of-2019/
[Verizon Samsung Galaxy S III] invisiblek:
enjoy!

consider it unofficial (2.2.2.1)

img ez recovery: http://truelinux.net/sch-i535/recoveries/TWRP-UNOFFICIAL-2.2.2.1-d2vzw.img

tar.md5 for odin: http://truelinux.net/sch-i535/recoveries/TWRP-UNOFFICIAL-2.2.2.1-d2vzw.tar.md5

zip for cwm/twrp: http://truelinux.net/sch-i535/recoveries/TWRP-UNOFFICIAL-2.2.2.1-d2vzw.zip
[Verizon Samsung Galaxy S III] wera750:
Well this version with with goo manager? And does it see sdcard? Or do we still use /data/media?

Thanks!
[Verizon Samsung Galaxy S III] invisiblek:
it should see both

should work with goo manager as well
[Verizon Samsung Galaxy S III] wera750:
Thanks for the quick reply!
[Verizon Samsung Galaxy S III] silver04v:
I assume that previous backups can be restored on the newest version without issues?

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] invisiblek:
that is entirely untested but i dont see why not
[Verizon Samsung Galaxy S III] Haro912:
Working great over here. Used it to flashed the new xoomdev aokp build. Didn't try to backup or restore thougho_O
[Verizon Samsung Galaxy S III] Dees_Troy:
Updated to 2.2.2.0 on 8/24. I just forgot to update the OP for this thread at the time it was released. There really aren't any code updates in 2.2.2.1 that would affect the SGS3 because the only code changes that I made are for devices with hardware keyboards. GooManager has been installing 2.2.2.0 since last Friday. Enjoy!
[Verizon Samsung Galaxy S III] mike86325:
Has anyone had problems restoring backups with the newest version? Just wondering since someone mentioned that they went into bootloop trying to restore using the last version, which made them change back to CWM. I don't think I've ever had to restore, but I just want to make sure it's a 100% working option in a worst case scenario.
[Verizon Samsung Galaxy S III] awmobjects:
That has 2.2 not 2.2.2...can we update EZ Recovery with 2.2.2?

---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------

I figured it out...put the IMG file in the expected Dir
[Verizon Samsung Galaxy S III] Cye3s:
so wipe /data with TWRP will keep internal sdcard or not?:confused:
[Verizon Samsung Galaxy S III] Haro912:
To wipe data and not the internal sd use factory reset. To wipe data and internal sd wipe data

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] awmobjects:
What labeled option in twrp is that?

Thx
[Verizon Samsung Galaxy S III] Haro912:
Let me reboot Into it and check.

EDIT: It's the format data option. If you just use factory reset it wipes data without wiping /data/media which is the sd card according to twrp.

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] goldsmitht:
I'm feeling really nooby here; can't find expected dir and when I copy and paste to file with rest of recoveries, ex recovery doesn't see it. Any help would be appreciated

---------- Post added at 09:53 AM ---------- Previous post was at 09:22 AM ----------

worked great; however, when my wife get's pissed, can i just rename UI.zip to ui.zip.bak and go back to old version? she gets a little miffed sometimes when i have pictures on the phone that aren't her...

not sure why... LOL!!! :angel: edit: little less nooby; renamed ui.zip to ui.zip.bak and it is now wife safe. whew... :D now if i can just figure out how to put 2.2.2.1 in so that ez recovery recognizes it, all will be well

any help?
[Verizon Samsung Galaxy S III] Haro912:
I just did custom and navigated to where I saved the img file.

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] goldsmitht:
tried that, and it rebooted into just recovery, not TWRP
[Verizon Samsung Galaxy S III] preusstang:
Damn this is nice. Thought I'd flash to see what the fuss about and wow is all I got to say. A recovery with a file manager? That is a huge time saver. This recovery rocks my socks.
[Verizon Samsung Galaxy S III] Haro912:
You have to hit flash recovery before you reboot into recovery. :silly:

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] awmobjects:
/sdcard/gs3ezrecovery/
[Verizon Samsung Galaxy S III] wera750:
So first time I tried to flash with goo it worked perfectly. Now I get E: unknown path sdcard0 error?
[Verizon Samsung Galaxy S III] th3taman:
In GooManager, you hit Menu, and then Install OpenRecoveryScript to flash the latest TWRP recovery? Is that when you get the error?
[Verizon Samsung Galaxy S III] wera750:
No when I select zips to flash and hit flash. It reboots to recovery, starts the script, then I get an error.
[Verizon Samsung Galaxy S III] th3taman:
If you want the latest TWRP recovery, follow the steps I just said in my last post (first sentence). It will flash latest version within the app. When it's done you can flash to recovery from within the app to check you have the most recent version. It's displayed on the main screen.

You should need to flash anything else in any other way.
[Verizon Samsung Galaxy S III] wera750:
Sigh, I have 2.2.2.1. It works fine when manually flashing. But when using goo to select zips to flash, it reboots to recovery and fails. Then I have to flash them manually.

Have you ever used goo to flash a Rom, gapps, and kernel ?
[Verizon Samsung Galaxy S III] th3taman:
Nope, just go straight to recovery and flash. See no point in using GooManager honestly. The problem you are highlighting is exactly why. Just flash in recovery, less hassle to me.
[Verizon Samsung Galaxy S III] wera750:
I'm not asking if you like it.I'm asking if it is working for anyone else. That's the whole point in the goo manager app.
[Verizon Samsung Galaxy S III] th3taman:
I understand and can't answer your question, sorry. But I have had problems with the app in the past. That's why I don't use it hardly any more.
[Verizon Samsung Galaxy S III] wera750:
It worked flawless on my gnex as long as the zips were in the goo folder on my sdcard. My initial flash worked, but subsequent flashes have failed. Maybe it's on goo's side?
[Verizon Samsung Galaxy S III] Haro912:
It's the way Samsung setup the external sd from what I've heard about it.

Sent from a strange blue box hurling through time and space.
[Verizon Samsung Galaxy S III] MFD00M:
You have to change the download path. For some reason Jellybean points goomanager to /sdcard0. I had the same issue on Jellybean roms on the GNex.

I changed mine to /sdcard/goomanager/ and it works fine now (from within goo manager go to Menu > Settings > download path). You can probably point it to the external sdcard as well but i haven't tried it so I'm not sure if that will work. Worth a shot, shouldn't hurt anything. Oh and the files you want flashed dont have to reside in the /goomanager/ file. I flash straight from the download folder usually.

I really love flashing my roms/kernels etc via goo manager. I can pick all the things i want flashed, tell it to make a backup (and i can name it ahead of time), and tell it to do a full wipe or just cache/dalvik. Total time saver. I can load up what i want, tell it to make a back up and wipe and it reboots on its own when its done. I can leave my phone and play some xbox or whatever while it does its thing.
[Verizon Samsung Galaxy S III] Nnyan:
Weird I have been on TWRP 2.2.2.0 for awhile now (just love being able to rename backups) and after trying a bunch of ROMs I'm getting a Teamwin banner whenever I reboot into recovery (was not able to find any threads about this), before this I wasn't getting anything (just a very brief flash of a black screen with blue text(?) before the recovery would load.
[Verizon Samsung Galaxy S III] MFD00M:
I've had that happen before but usually started up fine. Seems like it lagged a bit on start up but eventually started and worked ok. How long did you wait?
[Verizon Samsung Galaxy S III] Dees_Troy:
There's an update for GooManager that should help fix some of the flashing issues.
[Verizon Samsung Galaxy S III] cadams122593:
Hey Dees, i noticed theres a format data in the wiping options. what does that actually do? it says it will delete all backups. app data?
[Verizon Samsung Galaxy S III] pimpmaneaton:
Dees_troy long time man. Glad to see twrp here on the gs3 but was wondering if there is a possibility of seeing why vrtheme and twrp don't play well with each other. If that could be ironed out then I would say TWRP would take lead on recovery for this device. But at least half the themes here use vrtheme including mine. Thanks for your hard work with twrp.

EDIT: Nevermind man, I just installed 2.2.2.1 and ran my installer and all is well. Guess I should test before I speak. May be because I have vrtheme going to /sdcard now instead of /cache. Thanks again Dees. TWRP is numero uno.

Launched from Hot Rod running Synergy!!
[Verizon Samsung Galaxy S III] Haro912:
Try searching. Start at post 111 and read.

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] wera750:
Confirmed, this fixed it! Thanks for the work!
[Verizon Samsung Galaxy S III] th3taman:
Cool, was going to come here and say there was an update to the app. Glad it works for you now. :)
[Verizon Samsung Galaxy S III] Dees_Troy:
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.

http://techerrata.com/file/twrp2/utilities/zipalign
[Verizon Samsung Galaxy S III] silver04v:
Is there an image file of the official newest twrp we can flash in ez recovery?

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] Haro912:
Not sure if its in OP or not
[Verizon Samsung Galaxy S III] th3taman:
Should be here. http://www.teamw.in/project/twrp2/102
[Verizon Samsung Galaxy S III] Haro912:
Ook wow meant to post a link with this. Sorry about that. Post 101 I think it is

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] th3taman:
I did just above you. :laugh:
[Verizon Samsung Galaxy S III] Haro912:
Yeah I saw that but felt like an idiot so I just said where the link was going to :silly:

I still can't believe I forgot the stupid link...

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] neyenlives:
awesome work guys, thanks
[Verizon Samsung Galaxy S III] 1900mcm:
Encryption wipe failed - reboot loop

After playing around today and performing an encrypt of data, i returned to the phone an hour after starting the process to see a screen stating the encryption failed and to 'press to reboot'.

So I pressed and it booted into recovery (2.2.2.0) - the splash came up and a term window displayed 10+ lines about mount failed for /data/this and /data/that. The phone rebooted and went back to the 'encryption flailed'. I was effectively in a boot loop as recovery would never get to a menu allowing interaction. The normal boot would just get to the failed screen and send me back to recovery. I pulled the battery to try to get a recovery boot not driven by the encryption reboot screen, but never was able to get to a TWRP menu screen

I had to Odin the thing to stock (recovery) -

The 1st reboot after applying stock recovery had the same encryption popup.

The reboot happened, stock recovery appeared and was able to perform the wipe of data needed to have a working device.

(I then reflashed TWRP, restored a backup i made before beginning the playing) and was back to normal. )

I am/was using stock VRALG1 and Kernel KT747 8/31. Dont know if the encryption issue was caused by the kernel but I wanted to report the recovery error issue. Sorrry I dont have any screen related to the 10+ lines ( they seemed to be mount failure msgs )

This may be related to issue #35 - failure to perform a wipe of /data/data
[Verizon Samsung Galaxy S III] Dees_Troy:
There's a cancel button on the password page in TWRP that lets you use TWRP without decrypting the device. After hitting cancel, you would go to the wipe page and use the "Format Data" button to reformat the data partition so that data can be mounted again.
[Verizon Samsung Galaxy S III] 1900mcm:
Thanks for the tip, BUT, I never get to a TWRP UI. How would I have access this feature if the UI is never reached? ... Or more correctly, what should I have done to get to the UI?

Thanks for your response! (great tool/product)
[Verizon Samsung Galaxy S III] Cynema:
I backed up my CM10 rom to test out AOKP, when I restored the cm10 backup, I had the launcher app and superuser from AOKP and they were really glitchy. Why is that?
[Verizon Samsung Galaxy S III] awmobjects:
I've flashed 2.2.2.1 and have issue when naming my backups. It doesn't take much to hit a key and it takes you out of the screen and you have to start all over...sometimes 3 or 4 attempts for me. How does that happen?
[Verizon Samsung Galaxy S III] wera750:
Anyone have themes?
[Verizon Samsung Galaxy S III] Karl:
this one, i have not tested on new version yet

http://xdaforums.com/showpost.php?p=29613827&postcount=67
[Verizon Samsung Galaxy S III] joshw0000:
Hey guys, love this recovery. Running it on my TF201 as well as every other unlocked device I've owned.

My question: Is it possible to wipe battery stats with this recovery? I know that's not a widely used command but I actually need to do it. My phone has been running down to about 21% battery and then powering itself off without any warning. I'm hoping a recalibration will set things straight.
[Verizon Samsung Galaxy S III] Dees_Troy:
Battery stats doesn't have anything to do with that problem. There's a wide gap between what most people believe battery stats is and what battery stats actually are. Besides, anytime you plug your device into the charger and let it charge for a while, Android automatically wipes the battery stats.
[Verizon Samsung Galaxy S III] Haro912:
This but if you still want to try download battery calibration app from the market.

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] joshw0000:
Thanks for the info. So what exactly is battery stats for?
[Verizon Samsung Galaxy S III] 1ManWolfePack:
You missed the point.

Battery calibration/wiping is completely useless and was debunked by a lead Google Android engineer. You're just wasting a few seconds of your life by doing it. NOTHING happens....
[Verizon Samsung Galaxy S III] joshw0000:
Just seems odd that it always was and still is an active option in CWM. I've had similar problems on older devices that was seemingly fixed by fully charging my phone (powered off) and wiping battery stats. Maybe it was just the full charge cycle that actually fixed the problem (which I did last night while powered off). I guess I'll see tonight when my battery creeps down to the low 20's. Hopefully my extra batteries will come in soon and I'll no longer even charge my battery in the phone itself.
[Verizon Samsung Galaxy S III] Haro912:
I didn't miss the point. I said "this" agreeing with him. But if they still wanted to do it I personally always did it with an app from the market called Battery Calibration. This was before it was debunked.
[Verizon Samsung Galaxy S III] joshw0000:
Even though it's debunked, I will still try that app. My battery died again today at 20%. Some process might somehow be keeping the OS from deleting batterystats.bin. It's a long shot but doesn't hurt to try. Thanks for the link and I'll stop derailing this thread now.
[Verizon Samsung Galaxy S III] djd338:
FYI: older devices had Ni-Cad batteries which had a "memory", thus required you to fully discharge before charging etc. Today it's all Li-ion which is a whole different way to maintain. As stated previous, wiping stats does absolutely zilch & is a complete waste of time. Why does CWM still include the wipe function? Only Koush can answer & this is not his thread.
[Verizon Samsung Galaxy S III] jmaeishi:
I am pretty much a noob so please forgive.

I wanted TWRP because I had problems with CWM on past device, and because you guys did the HD for the Evo.

Anyways, I successfully installed TWRP 2.2.2.0. I just have a few questions.

1) Before that, I had CWM. However, I seem to have lost or misplaced the nands I did using it. Can someone direct me to them, or are they gone?

2) If I use/update ROM manager, will it auto throw me back to CWM? This is a fear I have, based on past experiences, where I lost all my nands.

3) I wipe in the order factory reset, cache, dalvik cache, system. Is this correct? Is this the safest, surest, for just about all cases?

4) Why doesn't the "format data" work? I get an error

5) Since going with TWRP I have, now, two sets of media. I'm very confused. I have a set of music files, all named incorrectly (though the music links to other songs I have) in "SD 1". Apparently, there is an SD 0 and and SD 1, which I do not understand. Anyways, my correct music files are listed and play from external SD. What does this mean?

I know it's a lot of questions but I hope the answers can be pieced together. Thank you for your hard work and providing a great recovery!