yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] sd_N:
Hmmm...I'm on 4.1.2 and I have the same issues as u. Gonna try CWM... Thanks for helping me think I'm not crazy...haha
[Verizon Samsung Galaxy S III] mav3rick478:
Can I ask why you would still be one 4.1.2 because the only reason I can see to still be that far back but is no longer valid would be for Google Wallet?
[Verizon Samsung Galaxy S III] justinnotjason:
Got a refurb S3 when I cracked my screen. I was using a 4.3 ROM from here on my old phone, but it was slow and random rebooted alot. So I was holding out for a good 4.4 ROM and by the time they started working the kinks out we'd moved on to LP, and now I'm readying to flash an LP rom.

I can't do OTA updates for obvious reasons.
[Verizon Samsung Galaxy S III] codezzie:
I've got an S3 with an unlocked bootloader.

When I flash TWRP it can't seem to find any partitions.

E: unable to find partition size for '/boot'

E: primary block device '/dev/block/mmcblk0p15' for mount point '/data' is not present!

E: unable to mount '/data'

Any ideas?
[Verizon Samsung Galaxy S III] mav3rick478:
Ahh makes sense, I don't know if I'm going to jump to LP, Omni Rom seems to be working fine for now. Is the camera working on LP?
[Verizon Samsung Galaxy S III] sd_N:
Unlocked boot loader.
[Verizon Samsung Galaxy S III] mav3rick478:
You can still have an unlocked boot loader on 4.3 and 4.4.
[Verizon Samsung Galaxy S III] ShapesBlue:
Not if you took either OTA you can't

Sent from my N5
[Verizon Samsung Galaxy S III] mav3rick478:
I know and by now everyone should know that especially if you are reading about custom recoveries. I understand wanting to unlock the boot loader but other than that there is no real reason to stay at 4.1.2, that's why I asked way back then to the original poster that I quoted and he explained.
[Verizon Samsung Galaxy S III] ShapesBlue:
Sadly no not everyone knows that. Tons of people have locked there bootloader due to not reading and just taking it, then wondering how they can go back and the reply is you can't. Well on a technicality you can but it's only available via a jtag service

Sent from my N5
[Verizon Samsung Galaxy S III] sd_N:
Yep...that's y I enjoy my 4.1.2 jellybean. Lol... I bought this phone brand new a long time ago. Never opened it... I did finally the other day... Memories... Ha-ha... The S3 is a keeper.
[Verizon Samsung Galaxy S III] t-mobile_mda:
hi..

this recovery is not for 4.4.2.? isnt it..?
[Verizon Samsung Galaxy S III] ShapesBlue:
No its not. This is for unlocked bootloaders only

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] skyss07:
Hi guys, I just successfully installed the latest version. I own SCH-I535 MF1 4.1.2 and I need suggestion to what OS version should I install or should I stay in this version
[Verizon Samsung Galaxy S III] ShapesBlue:
Its truly up to you. There are a bunch of solid roms out there. However I wouldn't post anything regarding which rom is better. Moderators frown upon that.

As far as roms go slimkat is a stable and solid rom. You do however have a few choices if you want a lollipop rom. Check in the development forums for those

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] Apache0c:
Sorry. Wrong forum.
[Verizon Samsung Galaxy S III] lepa71:
You understand that you are in S3 forum :confused:
[Verizon Samsung Galaxy S III] ShapesBlue:
I was going to chime in but I figured I would let someone else for once

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] justinnotjason:
Can anyone confirm whether the latest update addresses the issue with TWRP not reading the partitions on later S3's?
[Verizon Samsung Galaxy S III] ScottDB:
Yes, 2.8.7.0 DOES recognize the S3 partitions. I've been using it for a couple of months now.
[Verizon Samsung Galaxy S III] Syfer198754354:
Were the download link?
[Verizon Samsung Galaxy S III] ScottDB:
Look at the original post - the links are near the end of the post...
[Verizon Samsung Galaxy S III] ShapesBlue:
There is also a twrp manager app in the play store which will work as long as your not on a locked bootloader

Nexus 6 via VRToxin
[Verizon Samsung Galaxy S III] mzfr.shh:
Hey [MENTION=4635005]ShapesBlue[/MENTION] I have Samsung i535 running 4.4.2 which has a locked bootloader. How can I unlock the bootloader to install TWRP?
[Verizon Samsung Galaxy S III] ShapesBlue:
You can't. Your only option for a custom recovery is safestrap. Do not believe anyone who tells you that you can unlock the bootloader because it's false

Nexus 6 via VRToxin
[Verizon Samsung Galaxy S III] Dudash:
[MENTION=912474]Dees_Troy[/MENTION]

Any idea when 3.0.0-0 will actually be available on the site?

The newest one on the site and via the app is still 2.8.7.0.

---------- Post added at 04:28 PM ---------- Previous post was at 04:25 PM ----------

Or was the edit to the OP a "preparation" type deal?
[Verizon Samsung Galaxy S III] ShapesBlue:
Just double checked and it's not available for the S3. I think its being worked on but that's it. Here's what it looks like for version 3

Nexus 6 via Pure Nexus
[Verizon Samsung Galaxy S III] ST Dog:
Looks like all the official threads were updated for 3.0 even though not all devices have a 3.0 build yet.
[Verizon Samsung Galaxy S III] ShapesBlue:
Seems like it to me as well. The VZW S3 has no maintainer

Nexus 6 via Pure Nexus
[Verizon Samsung Galaxy S III] Dudash:
Then it seems to me like we need to get one :P

If Dees_Troy or someone else doesn't make one within the next few days, I may know a few people that could do it. I just really don't want to bother them as they always seem to have their hands full with other devices/projects.
[Verizon Samsung Galaxy S III] ShapesBlue:
I'm truly unsure why 2.8.7.0 isn't good enough, the new version may have some updates such as the interface but I'm thinking not much else has changed

Nexus 6 via Pure Nexus
[Verizon Samsung Galaxy S III] ScottDB:
It's because some people want the latest and greatest recovery and/or ROM the day Google releases a new version of Android.
[Verizon Samsung Galaxy S III] ShapesBlue:
To be honest if you want the latest and greatest then it might be time to update to a newer phone. The S3 is now approaching 4 years old. There may be no maintainer because there is little interest in the device

While I will always keep and enjoyed my S3 in its prime it is time to move on

Nexus 6 via Pure Nexus
[Verizon Samsung Galaxy S III] ST Dog:
I'm sure it's fine. The point was the thread was updated to reflect 3.0.0 w/o regard to the device support.

Same as if a ROM thread was updated for a new version w/o actually updating the download, people are going to ask about the update mentioned.

If this thread had not been changed, no one would have mentioned it, certainly not so soon. Same happened with other devices too.
[Verizon Samsung Galaxy S III] Dudash:
The recovery has been updated to 3.0.0-0 now.

And yes, people always want the latest and greatest.

Also [MENTION=4635005]ShapesBlue[/MENTION] my S3 is only used for CM13 and the newest features of android.

My daily phone is an S5, which will change to a nexus in the fall. Damned 2 year contracts.
[Verizon Samsung Galaxy S III] ST Dog:
A few items that are worth upgrading for:

-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)

-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)

-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow

-Update exfat, exfat fuse, dosfstools (by mdmower)

The terminal is a big one to me. And if you use large SD cards the exfat updates worthy.

Not sure if the GS3 uses sparse images or not but one of my other devices does, so it's a plus to me.
[Verizon Samsung Galaxy S III] ShapesBlue:
Not too worried about sd cards as neither of my Nexus devices have that but it seems like some positive updates/changes none the less

Nexus 6 via Pure Nexus
[Verizon Samsung Galaxy S III] phonetool:
I see 3.0 in TWRP Manager now.
[Verizon Samsung Galaxy S III] Droidriven:
I need a good working link to download and manually flash the TWRP.img.

Inked from my KrAkEn'd S3
[Verizon Samsung Galaxy S III] ShapesBlue:
Not at all hard to find my friend...

https://dl.twrp.me/d2vzw/

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] Droidriven:
Yeah, I tried that, its not working for me, hence the good "working" link, something like Android file host or something.

Inked from my KrAkEn'd S3
[Verizon Samsung Galaxy S III] ShapesBlue:
Alright. Will download and upload to my android file host account in that case

Sent from my Nexus 6
[Verizon Samsung Galaxy S III] Droidriven:
Thanks

Inked from my KrAkEn'd S3
[Verizon Samsung Galaxy S III] ShapesBlue:
Not a problem at all, here you go!

https://www.androidfilehost.com/?fid=24459283995309231
[Verizon Samsung Galaxy S III] Droidriven:
Much appreciated, thanks.

Uploaded to my Android File Host now.

Inked from my KrAkEn'd S3
[Verizon Samsung Galaxy S III] MuhammadBilal:
Will this work on stock 4.3? (Sorry for noob question)
[Verizon Samsung Galaxy S III] newbe1droidx:
You need the correct recovery for your phone. Hope this helps
[Verizon Samsung Galaxy S III] Droidriven:
That depends on which 4.3 firmware build number you have. There is a Verizon 4.3 stock firmware that had an unlockable bootloader that could flash TWRP if the bootloader was unlocked.

Then there are the 4.3 updates that had locked bootloader that is permanently locked and can't be unlocked. These devices can't flash TWRP no matter what you do.
[Verizon Samsung Galaxy S III] Ibuprophen:
Out of Curiosity....

Is there a way to Simulate, within the Recovery, Flashing a file?
[Verizon Samsung Galaxy S III] Droidriven:
Yes, if you go into TWRP settings, you'll see an option to "simulate actions for theme testing" as shown in this screenshot.

http://cloud.tapatalk.com/s/587924c492614/TWRP-Recovery-Settings.jpg?
[Verizon Samsung Galaxy S III] lepa71:
He is asking about simulating flashing ROM.
[Verizon Samsung Galaxy S III] Droidriven:
Yes, I know, I didn't misunderstand, what I told him is what he is looking for, the option I mentioned simulates all of your recovery actions without actually performing them, including simulating flashing a ROM. That option was designed to test TWRP themes to make sure the theme didn't break any of the other features in TWRP, to make sure they still work properly with the new theme being tested. The option can be used even if you aren't testing a TWRP theme.

Here's a link to explain it in the "settings" section.

www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide
[Verizon Samsung Galaxy S III] Ibuprophen:
Really?

I've always seen that option but, have never used it.

To me, the Verbiage to that title option came across as an option for theme testing only. I rarely select nor select an option/perform an action if i either didn’t need it or am not positive as to what it exactly does.

So, bottom line, by selecting that option will allow me to perform flash testing (ROM's, Firmware, etc...) that will provide results as to it being successful or not without actually flashing it permanently?

I just wanted to be clear on that.

Thanks!
[Verizon Samsung Galaxy S III] Droidriven:
It will test whether the recovery options are working correctly, it won't tell you if the ROM would successfully flash or if the ROM would actually work correctly, but it will tell you of the recovery is working correctly. Nothing can tell you if a ROM works or not, all you can do is actually flash it and test the ROM itself.

The feature was intended to be used for testing the recovery actions, it just happens to be the most useful tool to test TWRP themes. It can be used to simulate all of your recovery options without actually doing them, just to see if the feature are working as they were intended.
[Verizon Samsung Galaxy S III] Ibuprophen:
To add, though I can pretty much figure out the information located on the link you provided, it's really out of date.

Even the screenshots reflects TWRP v2.5.0.0 but, I have v3.0.2-0 with a really different User Interface/layout.

There really should be a guide that reflects the current TWRP Recovery and updated periodically.
[Verizon Samsung Galaxy S III] Ibuprophen:
Github Issue #1 Submitted " Reboot to Recovery Issues in TWRP v3.1.0-0 D2VZW"

[MENTION=912474]Dees_Troy[/MENTION], I just wanted to post #1 of 2 issues reported in Github.

Date of Submission in Github: 01-May-2017

Location in Github: https://github.com/TeamWin/android_device_samsung_d2vzw/issues/1

Verbiage of Github Issue:

The feature for Reboot to Recovery in TWRP now only Reboots the Device and not back into Recovery.

I confirmed twice that this issue was not present in the v3.0.2-0.

In order for me to Reboot back into Recovery, i have to immediately hold the button combinations to re-enter Recovery.

The issue is pretty self explanatory.

Thank You!

**********************************

I wanted to post the information for others to be aware of for posterity and awareness.

Thank you Very Much!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Verizon Samsung Galaxy S III] Ibuprophen:
Github Issue #2 Submitted " Action Simulation Issues in TWRP v3.1.0-0 D2VZW"

[MENTION=912474]Dees_Troy[/MENTION], I just wanted to post #2 of 2 issues reported in Github.

Date of Submission in Github: 01-May-2017

Location in Github: https://github.com/TeamWin/android_device_samsung_d2vzw/issues/2

Verbiage of Github Issue:

After updating to the v3.1.0-0, upon selecting the "Sinulate Actions for Theme Testing", and select a file to test, all the Terminal reflects is that the action was performed but, doesn't reflect the detailed information that v3.0.2-0 reflected.

I had confirmed this twice with v3.0.2-0.

This is also pretty self explanatory since when simulating actions really requires more information as actually performing the action itself so if there was any errors or similar then it could be seen.

Thank You!

**********************************

I wanted to post the information for others to be aware of for posterity and awareness.

Thank you Very Much!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm not sure if you had realized this [MENTION=912474]Dees_Troy[/MENTION] regarding the title of the thread reflecting the version of TWRP as being "3.1.1-0" and dated for "2017-05-19".

According to the following link:

https://dl.twrp.me/d2vzw

It states the last version of TWRP as being "3.1.0-0" dated for "2017-03-10".

I was mentioning this because I was wondering if the discrepancy of the title was made by design or by accident.

Thank You for your time and understanding... :)

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] JimmySmalls:
I'm not sure what I did wrong but I am rooted and have an open bootloader and I installed the latest TWRP but when I try to boot into it I get the "System software not authorized". Otherwise the phone boots fine and everything but I was planning on installing a custom rom. Any ideas?
[Verizon Samsung Galaxy S III] Ibuprophen:
I'd advise you to install it via ODIN. That's what I do and always worked.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] JimmySmalls:
Hey thanks for the quick reply, I'll give that a shot.

---------- Post added at 01:17 AM ---------- Previous post was at 12:32 AM ----------

I tried that and odin fails:

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> recovery.img

<ID:0/005> NAND Write Start!!

<ID:0/005> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)
[Verizon Samsung Galaxy S III] Ibuprophen:
While in Download Mode, did you put the "twrp-3.1.0-0-d2vzw.img.tar" in the PDA spot in ODIN and then press Start?

I have a feeling you may have used the "twrp-3.1.0-0-d2vzw.img" download from the TWRP site but, when using ODIN, you need to download the "twrp-3.1.0-0-d2vzw.img.tar" file.

Also, just to clarify, you don't use the PIT file when installing TWRP either.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] JimmySmalls:
I doubted myself after you said I probably had the .img file but mine is "twrp-3.1.0-0-d2vzw.img.tar" and it is in the PDA slot. Not sure about the PIT, it just does that after I load up the file and click start. Am I messing up a setting or something?
[Verizon Samsung Galaxy S III] Ibuprophen:
On your PC, try a different USB cable and/or a different USB Port. To be honest, the both of these had worked for me when it comes to the connection between ODIN and the device. This connection is a touchy one and ODIN can be a challenge.

Also, try a different ODIN version like v3.07. I've had better luck with that one because that was the version that came out around the time the GS3 came out.

You can also look again at the instructions on the following TWRP link.

https://twrp.me/devices/samsunggalaxys3verizon.html

If you scroll down a bit, you'll locate the instructions when using ODIN.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] Ibuprophen:
I just noticed something that REALLY doesn't make sense and forces me wonder what and why...

[MENTION=912474]Dees_Troy[/MENTION] (one of the Official TWRP Developers for the d2vzw) provides a link to Github for reporting any TWRP issues for the d2vzw at the following link.

https://github.com/TeamWin/android_device_samsung_d2vzw

What doesn't make sense is, yesterday, i had noticed that the d2vzw device page for TWRP provides a Github link to this page.

https://github.com/TeamWin/device_samsung_d2vzw

Notice that one is "android_device_samsung_d2vzw" and the other is "device_samsung_d2vzw".

Also, i had noticed that, with both links, I am the only one who submitted any issues and none of the developers had even taken a look at them. Where are all the closed, open, etc... issues that other individuals had submitted and keep in mind that Github keeps historical issues too for the record.

So i found where individuals go and, some, developers go to see them.... they're all found in the following link.

https://github.com/TeamWin/Team-Win-Recovery-Project

I know that there's other members who'll respond to this post with excuses (masked as reasons) but, can an official TWRP developer provide an answer as to conflicting and confusing information for the users as to how, when and where to go to submit issues that is monitored by an official TWRP developer.

I'm now ranting or hating anyone... I'm just a dedicated TWRP user who still loves the work that the TWRP team puts into the project and the product that's released AND a bit annoyed as to how are they going to know any of the feedback from a user to help improve on the TWRP experience if they don't know where to look or even take note to the issues.

I apologize for this but, it really needs to be said (and known by those who doesn't know).

Thank you all very much for your time and understanding with this.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm EXTREMELY happy to see that the new TWRP v3.1.1-0 released is working GREAT!!!

THANK YOU!!!

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] phonetool:
Working great for me, too!

The TWRP app not so much, though. It downloads the file but then wouldn't select it for install without crashing.

3.1.1.0 wasn't showing up in TWRP Manager (still isn't), so that was no help either. Finally I installed Flashify to install the file that the TWRP app downloaded.
[Verizon Samsung Galaxy S III] Ibuprophen:
I've had some minor issues with the app and stopped using it completely.

The updates are small in size and it's easier to just download them and reboot into TWRP then update it from there.

The app pretty much (when it works LOL!) does the same thing but, it's such a simple task where i prefer to do it myself that just elevates any issues that may/might happen via the app itself.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] phonetool:
I wasn't sure if I could flash the new file from within TWRP itself.
[Verizon Samsung Galaxy S III] Ibuprophen:
Go to the downloads here:

https://dl.twrp.me/d2vzw/

Be sure to grab the latest ".img" file and save it to a location where you can find it while in the TWRP Recovery.

*** Be sure you don't confuse it with the ".img.tar" file. That's for flashing via Odin on the PC.

Reboot into the TWRP Recovery and select "Install" then select the bottom right button for "Image" then navigate to where you just downloaded the TWRP update file and select it then proceed.

Once Successful, you can now Reboot (You don't need to, though it won't hurt, to wipe the Dalvik Cache).

Presto!!!

It looks like allot of steps/work but, it's really not and very easy and quick too.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] eh1san1:
its not working on my device 4.4.2 (sch-i535)

---------- Post added at 10:00 PM ---------- Previous post was at 09:40 PM ----------

i am facing the same issue. but i manage to have Safestrap recovery unofficial 3.73 and able to boot into recovery mode but i dont know can we flash this rom with this safestrap or not..!
[Verizon Samsung Galaxy S III] phonetool:
442 is a locked bootloader. You can only run safestrap and 442 roms. SuperliteROM is a good one. Good luck!
[Verizon Samsung Galaxy S III] eh1san1:
hmmm yeah i tested SuperliteROM work fine...

All we have just three roms for this device

1. I535VRUDNE1 stock 442

2. SuperliteROM

3. PualPiZZ ROM

can you give me a list of rom which we can flash this device ???
[Verizon Samsung Galaxy S III] BadUsername:
You got it, that's all you can use.
[Verizon Samsung Galaxy S III] SeewolfPK:
I have a wrong (backupfile)date in twrp. Date:2015-05-05)

How can I fix?

I use TWRP 3.1.1.-1 for LG G4
[Verizon Samsung Galaxy S III] Droidriven:
Ask in the G4 forum, this is the Verizon s3 forum.
[Verizon Samsung Galaxy S III] Ibuprophen:
Just an FYI for those who may not be aware...

There's an update available on the Official TWRP website to "v3.2.2-0"...

Enjoy!

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Verizon Samsung Galaxy S III] saberlv:
this works on verizon s3 4.4 ?,