yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] singingandroid:
I've always used old phones, and like old phones. A few days ago, I was fortunate enough to buy 3 SCH-I535 S3 phones on ebay for about $40 each, all in excellent condition and with unlockable "MF1" or lower firmware. Although the S3 is "old", it is the most advanced phone I have owned, and being able to run Android 7.1.2 is supurb. IMO Android 4.4.x is good, Android 5 and 6 are a regression, but Android 7 is excellent.

I've flashed some custom ROMs in the past, but still consider myself a novice. I initially had difficulty installing TWRP, not realizing that even though the bootloader can be unlocked on MF1 firmware, it does not come unlocked. Once I discovered CASUAL, my life was bliss.

I wrote my own guide on the steps to install LineageOS 14.1 UNOFFICIAL. This guide fits my technological ecosystem, and your mileage may vary depending on your setup. I used this process to flawlessly root, unlock bootloader, and install the latest UNOFFICIAL LineageOS 14.1 on all 3 of my I535s that were originally running Android 4.1.2. Feel free to copy or modify the guide in any way you find useful.

HUGE thanks to [MENTION=4013543]mjb32803[/MENTION] for reviving the S3 legend, and for support I've received from [MENTION=4828250]Ibuprophen[/MENTION]. This thread in a large way helped me to buy the S3 rather than the HTC One (M8), which was my other consideration. I plan to use my Galaxy S3 I535 (d2vzw) for years.

[IMG="Galaxy S3 I535 (d2vzw) LineageOS 14.1"]https://justpaste.it/img/fbb5060a10e44b5a5d20935d079c804c.jpg[/IMG]
[Verizon Samsung Galaxy S III] mamarcac:
S3 is a classic

Great looking phones you found! I have 2 Verizon S3's at home unlocked with custom ROMs; switched to a Pixel 2 on a Black Friday sale last year after 5 years of the S3. But there's something about that S3, headphone jack, removable battery, microSD, beautiful OLED, great ROMs, it's just a joy of a phone. It really feels like the perfectly designed phone. Glad you got yours working :highfive:
[Verizon Samsung Galaxy S III] lonelyastronaught:
E:unknown Command [log]

I'm trying to flash this on a Rooted Galaxy S3 (Verizon) but i get unknown command

It bootloops after this, so I have tried the flash again but same thing happens.

Maybe I'm flashing incorrectly? I do factory reset, wipe cache, dalvik cache, and data then I flash the ROM.
[Verizon Samsung Galaxy S III] Ibuprophen:
This is because Custom Firmwares requires a Custom Recovery and SafeStrap is not a Custom Recovery.

Custom Recoveries requires an Unlocked Bootloader and it looks like you don't have it unlocked.

Sorry for the bad news...

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

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] mjb32803:
New Build is live

Android security patch level bumped to July 5th.

An unusually large number of changes made this past month (>30).

Some Bluetooth fixes.

Read Post #1 for download and install instructions.
[Verizon Samsung Galaxy S III] mrdally204:
I have not installed this yet but I wanted to give the op a pointer for tracking downloads with Dropbox. You can use a 3rd party site called orangedox to track downloads through Dropbox. You link the 2 accounts and share the link from orangedox. Their free account will let you share 10 links concurrently and see activity on them. I will be installing this rom as soon as I can figure out if/how to unlock bootloader. Hope my tip helps :)
[Verizon Samsung Galaxy S III] Nmoz21:
Thank you, my S3 feels modern again. I did have issues the first boot, stuck at Lineage OS loading logo. Killed power then rebooted. Loaded up but things were buggy, crashing apps and buttons not working. Ended up reflashing over it and seems that it missed the out of box setup. Once I set that up correctly, everything is great now!
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm happy to see that your up and running but, I've got a question out of curiosity only.

When you first ran into that issue, did you perform a fresh install or a dirty flash (dirty flash = updating the firmware over a previously installed LineageOS 14.1)?

Sent from my SM-G900V using The ClaRetoX Forum App
[Verizon Samsung Galaxy S III] Nmoz21:
I ran into that issue installing over the VZW official firmware. I think it was one of the last before the locked bootloaders. So I had factory reset it prior, then installed TWRP, then LineageOS, then GAAPS.

The second time, I flashed LineageOS and GAAPS at the same time through TWRP.

P.S. Right now I'm having issues detecting the SIM.

Scratch that. It detects Verizon sim. But not straightalk. I have a freedompop sim on the way.
[Verizon Samsung Galaxy S III] mjb32803:
When installing this ROM for the first time, you MUST factory reset (Wipe Data).

You MUST also flash the ROM and GApps @ the same time.

The issues you describe are because you did not perform these steps.
[Verizon Samsung Galaxy S III] Nmoz21:
I don't believe I did anything except a factory reset before flashing the first time. As for the rom, I flashed the rom, rebooted straight back into TWRP to flash GAAPS, then rebooted into the system for the first time.

Perhaps this is a bit misleading as I think they're two different processes. Factory reset != wipe data. ??
[Verizon Samsung Galaxy S III] mjb32803:
Per multiple google searches, "Android Factory Reset is a feature that erases all device settings, user data, third-party applications, and associated application data from an Android device's internal flash storage to return the device to the condition it was in when shipped from the factory."

When you perform a Factory Reset, your Data partition will get reformatted.

Yes, you can reformat JUST the Data partition in TWRP so technically, as long as you choose the Factory Reset option, you're good. I just put Wiping Data in there to remind everyone that by doing the Factory Reset, you will also Wipe Data, which means having to reinstall all apps from scratch. You can also do a Factory Reset & Wipe Data, which would double format Data (which is OK).
[Verizon Samsung Galaxy S III] mjb32803:
General flashing rules to follow:

Whenever moving from one ROM to another, you will need to perform a Factory Reset. Otherwise you will have issues. This includes moving between Cyangoen to anything else, Official to Unofficial LineageOS, and Touchwiz to LineageOS.

The first time you flash a ROM, you MUST flash GApps at the same time. Otherwise, GApps will not install correctly and you will have issues. I would even be hesitant to flash a newer GApps on top of a previously working ROM / GApps install.
[Verizon Samsung Galaxy S III] J-Lindo:
The idea of Oreo Go does sound appealing. Someone correct me if I'm wrong, but isn't our kernel too old for it?
[Verizon Samsung Galaxy S III] mjb32803:
The main reason maintaining 14.1 for the Verizon S3 (d2vzw) has been fairly simple, is because it HAD Official 14.1, and the International S3 (i9300) is still getting OFFICIAL LineageOS 14.1 builds. When I sync to the Git Repo to do a new build, it includes the global Samsung S3 i9300, Android Security Patches, and the LineageOS 14.1 changes. Lucky for us, we get to leverage off their updates. If/when the i9300 looses their OFFICIAL builds, I'm not sure what will happen. Maintaining 14.1 would then become a much more manually intensive process.

Regarding 15.1.... I'm not sure what would be involved with that task. Since none of the S3 variants ever had 15.1, there is no baseline to start with. I'd imagine the 14.1 kernel drivers would not play well. There is some info here https://blog.forkwhiletrue.me/pages/midas-mainline/ regarding kernel development, but it's for the International Galaxy phones (that use the Exynos SoC).

Also, since my S3 is not my daily-driver (Nexus 6 still going strong), I don't have much motivation for the task.
[Verizon Samsung Galaxy S III] mjb32803:
Yes. After doing some googling, the Kernel is too old.
[Verizon Samsung Galaxy S III] mjb32803:
I though Oreo Go got it's speed and smaller storage footprint by utilizing web based / "lite" versions of common Android apps? Underneath though, is still the basic Oreo infrastructure? Can anyone that's researched this comment?
[Verizon Samsung Galaxy S III] J-Lindo:
I believe there are system-level optimizations made and a few features left out of O-Go. I'd bet [MENTION=4828250]Ibuprophen[/MENTION] would have a more specific answer :silly:
[Verizon Samsung Galaxy S III] Ibuprophen:
Thank you for the vote of confidence! :eek:

I was just knocking out some items on Github and afterwards I took a quick look at one of the repositories that some of the Official Lineage Team Contributors uses and located the following there from a LineageOS 15.1 channel...

https://github.com/TheMuppets/proprietary_vendor_samsung/tree/lineage-15.1/d2vzw

... I can't state for certain that it's what [MENTION=4013543]mjb32803[/MENTION] is looking for or has what he needs but, it's something that I hope can be used to help out.

I was just thinking that, since the d2vzw was dropped from the LineageOS development only because the maintainer no longer owned the device, on top of the I9300 still being maintained, i just felt that there may be something regarding the upkeep for the d2 device in general.

Don't let "TheMuppets" on the Github link throw you off since they may have just found a name that nobody else had already taken. LOL!

I'm keeping my fingers crossed! :)

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Verizon Samsung Galaxy S III] wanb1i:
Downloading the current build now, will update the status when done. Thanks for the work & the ROM! :good::fingers-crossed:

I thought this device was dead, it's been a desktop clock for about 3 years!
[Verizon Samsung Galaxy S III] Ibuprophen:
Just an FYI [MENTION=4013543]mjb32803[/MENTION]...

The following thread does have an Unofficial LineageOS 15.1 for another Galaxy S3 Variant (S3 Neo).

https://xdaforums.com/showthread.php?t=3795428

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Verizon Samsung Galaxy S III] J-Lindo:
Do you think the S3 Neo is closely related enough to pull from it to develop for the S3?
[Verizon Samsung Galaxy S III] Ibuprophen:
This all depends upon if [MENTION=4013543]mjb32803[/MENTION] can use the Kernel from the S3 Neo.

I wasn't sure what he can do with it and wanted to point it out in hopes of it helping in some way.

The biggest thing for creating/developing any newer Custom Android Firmware is primarily based upon the ability to update the d2vzw Kernel.

I've never actually messed with (Developed) a Kernel before and I wish that I had the time to do this but, I really don't have the time and expertise to do this (I'd have to learn, read, etc...). :eek:

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Verizon Samsung Galaxy S III] J-Lindo:
Definitely fair enough. At least the S3 Neo has a Snapdragon SoC unlike the I9300. That alone might be worth a smidgen of hope.
[Verizon Samsung Galaxy S III] mjb32803:
Just wanted to let everyone know I am back, and working on another build. I will look into the S3 Neo.
[Verizon Samsung Galaxy S III] mjb32803:
I pull the proprietary blobs (d2-common and d2vzw) from TheMuppets. You do that once, and there isn't a need to repeat as those files haven't changed in years (doubt they ever will).
[Verizon Samsung Galaxy S III] mjb32803:
New build available for download

Download information in Post #1

This build has the September 5th Android Security Updates.

The file size is slightly larger than prior builds 298.5 MB vs 298.1 MB

I have already flashed this to my d2vzw and seems to work ok for me.
[Verizon Samsung Galaxy S III] mjb32803:
I took a quick scan through the 7 pages of posts on the S3 Neo. They have a lot of issues, probably due to kernel and drivers. Take a look at the open bugs, and it's pretty much a no-go from my perspective. I'd much rather have a fully functioning S3 on 14.1, than a buggy, missing functionality 15.1.

14.1 continues to be relatively easy to maintain. Since July, I've noticed the S3 Android Security patches show up about 4 - 6 weeks after they do for the newer phones, but that's still better than not getting them at all. I am pretty much at the mercy of whomever maintains the other S3 variants. Some portions of the repo don't always sync, and I have to go back and manually force them. But in the big picture, last night's build only took me about 40 minutes to generate. So let's keep our fingers crossed.
[Verizon Samsung Galaxy S III] Ibuprophen:
I just knew that they were working on it and made the suggestion.

I knew that they were having some problems but, one in a while I take a peek there to see how it was progressing in it's stability.

I believe that there's one or two other variants that were in talks regarding a team development as well.

Of course there's a difference between talking and doing... LOL! :)

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Verizon Samsung Galaxy S III] mjb32803:
I just checked the LineageOS 14.1 changelog for the International S3 https://www.lineageoslog.com/14.1/i9300

No changes as of today. Will check back in another week.

Obviously no point in doing a new build until there are some changes, so stay tuned.
[Verizon Samsung Galaxy S III] mjb32803:
I just read some more interwebs chatter regarding 4.4.x kernel development for the International S3. Unfortunately for us d2vzw users, we have completely different SoC. Regardless, I continue to be impressed by the present day performance of this "old" device.
[Verizon Samsung Galaxy S III] biship:
What are the mobile network settings for Verizon? I can't get any combination of them to work.

I am on MF1 Firmware with NE1 modem, and the latest build from this thread.

EDIT: I am on latest TWRP and did a complete factory reset and TWRP format.

Then I installed this custom rom and latest micro gapps in TWRP, and ran through the lineage setup.
[Verizon Samsung Galaxy S III] J-Lindo:
Just a stab in the dark, but you might see if you just need a new SIM card. Back when I first installed CM 13 on my S3, I discovered I wasn't getting any network signal, despite no signs of anything being out of order. I went to a Verizon store to see if it was something on their end, and the employee told me I was using an older SIM card and needed a new one. Sure enough, the new SIM looked a little different than the old one, and my S3 was up and going happily.
[Verizon Samsung Galaxy S III] mjb32803:
It sounds like you are using a SIM from another phone and transferring it to a d2vzw?

Personally, I've never had to "set" anything... just pop in the SIM and the phone auto configures.

Only other thing I could think of is set the preferred network type to LTE? Although the default Global setting should work just fine.
[Verizon Samsung Galaxy S III] biship:
I was trying to use the original VZW S3 sim from 2012 and after 2hrs trying to get VZW support to understand the problem, they check the ICCID and tell me the SIM has been 'retired' and can no longer be used.

I'll get a new SIM & reset the network settings and see if it works. Thanks for the help.

EDIT: Yup, that's all it was. I needed a new SIM. VZW Online let me place an order with the old sim, but didn't check if it was valid, or tell me the it'll never work. 'Global' setting working fine.

Thanks for updating 14.1 for the S3!
[Verizon Samsung Galaxy S III] iPG1101:
lOS 15/16?

Can you try doing Android 8.0 or 9.0? lineageOS 15/16 don't support a few old devices, including mine (d2vzw). If not I fully understand but would be nice to be able to have an up-to-date ROM
[Verizon Samsung Galaxy S III] MASHAFF:
TWRP and bootloader unlocker no longer supported?

Someone attempting to upgrade my SCH-I535 phone for me says the cwm or twrp (custom recovery) and the bootloader unlocker files are not supported anymore, that he's only getting dead links. Any direction?
[Verizon Samsung Galaxy S III] J-Lindo:
This thread has a cool java-based toolkit that'll do the trick for unlocking the bootloader and installing older TWRP (don't bother with CWM) https://xdaforums.com/showthread.php?t=2332825

You'll need the .zip containing the updated NE1 modem (not the NE1 bootloader) to ensure proper network connection, but I can't find a good link. I may still have a copy on my laptop (I'll look when I get a chance), but I'd bet [MENTION=4828250]Ibuprophen[/MENTION] has it too. Check out Ibuprophen's linked thread a couple posts down.

Once bootloader unlocked and TWRP installed with the above toolkit, you want updated TWRP (not hard to find, it's still on the official TWRP website—look for d2vzw).

Then flash the Unofficial Lineage from this thread and whatever add-ons your heart so desires :)
[Verizon Samsung Galaxy S III] J-Lindo:
Looks like I don't have it after all. Do you have a copy, [MENTION=4828250]Ibuprophen[/MENTION]? I'd like to have a saved copy myself should I get a chance to redeem an old S3. If not, we'll just have to figure out how to recreate it ourselves :eek:
[Verizon Samsung Galaxy S III] Ibuprophen:
The following thread has all the Firmware Modem Updates (Only) that's specific to the d2vzw device.

https://xdaforums.com/showthread.php?t=3735628

All the download links should still be working on that thread too.

Good Luck! :)

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
[Verizon Samsung Galaxy S III] mjb32803:
This topic was discussed in prior posts. Short answer is No. Too much effort. Likely would not result in a stable phone. d2vzw would need an updated kernel, with updated drivers. Never going to get updated drivers for a phone this old. Sorry. Take comfort in knowing that only 20% of phones are running Oreo or Pi.
[Verizon Samsung Galaxy S III] mjb32803:
New Build for November

Happy Thanksgiving!

This build brings the security patch level to Nov 5th.

Download link updated in Post #1

Just to give everyone an idea of the changes over the past 3 weeks.... most likely d2vzw inherits almost all of these from the SGS3 i9300:

PartsActivity: Prevent actionbar NPE

apns: update RJIO APNs

RJIO: Change Roaming protocal to IPV4V6.

Release the wakelock before worker thread termination

Allow intent shared subject or title to be mms subject

Security string to 2018-11-05

MediaExtractor: stop rendering when an error occurs

Verify number of Map entries written to Parcel

RESTRICT AUTOMERGE: Hide overlay windows when requesting media projection permission.

Fix OOB access in Tremolo

Check data length when parsing AVRCP vendor specific command responses

AVRCP: unify Get{Element,Item}Attributes response.

Check AVRCP data length when parsing inside avrc_ctrl_pars_vendor_rsp()

sonivox: prevent rejection of good but large MIDI files

sonivox: prevent infinite loop in OTA ringtones

ZoneInfo: Exclude boundary tz transitions

BACKPORT: Disable changing lock when device is not provisioned.

Fix information disclosure in mediadrmserver

Fix crash during cursor moving on BiDi text

Checks the SMP length to fix OOB read

Add packet length check in smp_proc_master_id

DO NOT MERGE Fix OOB read before buffer length check

Check packet length in bta_av_proc_meta_cmd

Add missing AVRCP message length checks inside avrc_msg_cback

Add packet length checks in mca_ccb_hdl_req

DO NOT MERGE. Persistable Uri grants still require permissions.

Always create grant structures when persistable.

Optimise the hit test algorithm

Fix a wrong check in rfc_parse_data

Add support for search in DownloadManager.

DO NOT MERGE. Extend SQLiteQueryBuilder for update and delete.

Add bound check for rfc_parse_data

Check remaining frame length in rfc_process_mx_message

DO NOT MERGE. All untrusted selections must go through builder.

Fix copy length calculation in sdp_copy_raw_data

Test for error in handling getters changing element kind.

2018-10-30 11:32 UTC (android_external_chromium-libpac)

20 days ago

DO NOT MERGE. Execute "strict" queries with extra parentheses.

manifest: Track our own chromium-libpac

Enable search for Downloads.

manifest: Track our own external/v8

Backport: Fix Object.entries/values with changing elements

BACKPORT: Cherry-pick "begin cleanup of malloc porting layer"
[Verizon Samsung Galaxy S III] Ibuprophen:
I just wanted to express my Thanksgiving Greetings to Everyone Here!

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
[Verizon Samsung Galaxy S III] Ibuprophen:
First of all... It's a real bummer when I noticed one of the Galaxy S2 devices having LineageOS 15 AND 16 (Unofficial) releases. :eek:

No complaints... Just a real bummer of a deal... LMAO!

Anyways, Happy/Merry Christmahanakwanzika Everyone!!!

LMAO! :eek:

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Tandy TRS-80
[Verizon Samsung Galaxy S III] mjb32803:
Happy Holidays everyone.

The Galaxy S2 in question is the i9100, which is the International GSM version. The i9100 and i9300 are both GSM phones using completely different silicon inside (Exynos 4210 dual core, and Exynos 4412 quad core respectively) . Keep in mind the Verizon S3, being CDMA compatible, was only sold in the USA, while the GSM S2 and S3 were sold throughout the entire WORLD... hence they have a much larger user base. Consequently, those phone continue to get support.

,