yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] gadgetguy08:
You might find this thread helpful:

https://xdaforums.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
[Verizon Samsung Galaxy S III] mjb32803:
Thanks for the thread link... the first post looks like a cut/paste from the lineageos wiki guide I've been using from < https://wiki.lineageos.org/devices/d2vzw/build > so I guess I've at least started in the right direction. Will dig through the rest of the thread tonight. If I can get the process working reliably, I'd like to make periodic builds available here.
[Verizon Samsung Galaxy S III] J-Lindo:
Dude. You are super cool for making updated builds. For everything you intend to do, thank you!

I noticed in your photos, though, that your baseband is the MF1 and not NE1. I remember for a long time I had strange internet connection issues that no one else here seemed to have, until I finally realized the OP has a link to a flashable .zip with the updated baseband, which magically fixed the issues I'd been having. I don't have nearly enough experience to say whether that's affecting anything on your build progress, but perhaps you might try flashing it and see how it goes?
[Verizon Samsung Galaxy S III] mjb32803:
Thanks for pointing out that my baseband is older. I haven't thought to update it because I use it on WiFi only. My daily driver is a Nexus 6. Generally I just use the s3 media streaming through bluetooth to my stereo, hangouts dialer, Roku remote, and Western Digital TV Live remote.

Regarding the build. I did flash it successfully and ran it all day.

Unfortunately, the only way I could get it to flash, was to wipe everything on the phone.

After using it on and off all day, it has been very stable.

I will probably stick the SIM card from my Nexus 6 in it later tonight to verify that LTE/CDMA work, so will report back on that.

Reason I was motivated to tackle this project was to keep the phone updated with security patches. As you will notice, this build is updated to February 2018. The last LOS14.1 build (I think) only had the November 2017 updates.

After googling, the "Error: 7" issue while flashing may be caused by using an OLD version TWRP.

There was a TWRP update (ver 3.2.0) in December 2017, which I just flashed.

I restored my previous LOS setup that has the Dec 5th (FINAL OFFICIAL) build.

Am going to try flashing my build using the newer TWRP, and see if that solves the "ERROR: 7" snag.

Should know in about 15 minutes.
[Verizon Samsung Galaxy S III] mjb32803:
Another update.

I have so far been unable to flash my "unofficial" LOS14.1 on top of the last "official" build, UNLESS I wipe data.

If I do a clean install (factory reset), it flashes fine.

Tried making a TWRP backup, flashing my build, and then restoring just Data. After rebooting, I got all kinds of Apps failing/crashing/ etc.

So the warning I got during flash (Error: 7) must really mean something significant ( Will have to do more investigating on that).

I created a 2nd build, and was able to "dirty flash" it on top of my 1st build.

So I shouldn't have to deal with reinstalling all my apps again.

As far as testing my builds, I took my SIM card out of my Nexus 6 and stuck it in the d2vzw.

LTE works fine. Also tested GPS, Camera, WiFi. Installed Open Gapps NANO.

Phone seems to work the same as the last Official LOS 14.1 from Dec 5th.

If anyone is interested in giving this build a whirl, message me. I will probably stick it on dropbox and then send individuals the link? (Unless someone can make a better suggestions).

Given the age of the d2vzw, I don't expect a huge number of people to suddenly have great interest in my builds, so maybe using dropbox will be ok.
[Verizon Samsung Galaxy S III] Stealth111:
This is GREAT news! PM Sent!
[Verizon Samsung Galaxy S III] Ibuprophen:
I remember when CyanogenMod had Unified the d2vzw with one or more other d2 variants for the d2lte builds.

I wonder why it had stopped with LineageOS?

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

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] Droidriven:
Because it got to be more difficult as more of the MVNO networks came on board with their own versions of their host networks devices, each with their own differences that were minor but turned into a mess modifying unified builds that supported so many variants. Plus, some of the variants weren't really supported but could flash builds from a similar variant, this led to issues from users needing help with devices that weren't specifically meant to use this or that build. Such as my Straight Talk S3(d2tfnvzw) that could flash the d2vzw and d2lte even though the developers didn't specifically build for the Straight Talk S3. Or the Straight Talk S3 variant that ran on Sprints network and could flash the d2spr ROMs.
[Verizon Samsung Galaxy S III] mjb32803:
After doing some more reading.... i "think" the reason I cannot flash my "unofficial" build over the "official" LOS build, is that my builds are UNSIGNED... I assume it is a security feature that is designed to protect the data on your phone?
[Verizon Samsung Galaxy S III] Ibuprophen:
AHHH!!!

I See says the Blind Man! LOL :)

I wasn't aware of the back story behind this decision.

Thank you very much My Friend. :thumbup:

I apologize for my absence when this was previously mentioned.

I knew that Unofficial builds either won't flash over an Official one though, I have seen it work in some cases but, the Firmware would not work very well with some to a ton of issues (depending on what was addressed within the Unofficial build).

A majority of the time that it failed to flash was in fact either a Signature Mismatch or Unsigned.

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

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] Droidriven:
Yes....and no......sorta......depending.

A mismatched updater script vs. build.prop could possibly cause the same results.

Do you have TWRP installed? You can't flash via stock recovery.
[Verizon Samsung Galaxy S III] Droidriven:
I've never flashed anything unsigned.
[Verizon Samsung Galaxy S III] Ibuprophen:
It looks like there's a handful of failed signature checks that are mismatched.

I'm just throwing out ideas based on what I see.

Have you asked this question within a thread like the following?

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

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

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:
Haven't posted anything outside this thread.

Building LOS for my standby d2vzw was a spur-of-the-moment whim... simply because I noticed there hadn't been any updates since last year. I came to this threat and discovered it wasn't being maintained anymore... so I did some reading and figured out how to do it myself.

Now that I have my own build running, I've already verified I can flashed another of my builds without issue....

so for my own purposes, I'm good to go....

I'm trying to solve the ERROR: 7 to make it easier for anyone that might want to use my builds, so they can easily flash over an existing "Official" build, and not have to wipe data.

---------- Post added at 06:14 AM ---------- Previous post was at 05:18 AM ----------

I just finished reading through 31 pages of posts in that thread.

In all that, only one post where someone asked about a Signing Guide, and the response was to "use search".

No other info provided.

Will try to spend some time this weekend investigating.
[Verizon Samsung Galaxy S III] Ibuprophen:
[MENTION=4013543]mjb32803[/MENTION], Maybe the following information might be helpful to you regarding the Error 7.

https://wiki.lineageos.org/faq.html

https://xdaforums.com/showpost.php?p=47357982&postcount=1

http://www.teamandroid.com/2017/04/30/fix-lineageos-status7-error-installation-twrp-cwm/

Just throwing out some information you may not know because they cover this Error better than what I can provide.

Also, they're not a ton of pages to go through... LMAO! :)

I do hope their helpful.

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

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:
Thursday, I learned a real-life lesson in WHY you NEVER want to USE an UNSIGNED build.

It's kind of funny in a way.... but short story is I spent over half an hour on the phone with my bank's fraud department.

My online bank access was disabled because their "system" detected the use of a "fraudulent device" accessing my account.

You guessed it.... it was me testing out my UNSIGNED build, using my bank's android app. Funny right?

From this experience, I can deduce that while building lineage "technically" works (it builds error free, installs, and runs on the phone), you cannot effectively use that build unless it is SIGNED . The guides I've been following (IMHO) seem to imply that once you build, you are home free and that "signing" is just something else you could do (not the case at all). As I found out, "signing" the build is critical.

For reference, I've been using the guides here:

https://wiki.lineageos.org/devices/d2vzw/build

https://xdaforums.com/chef-central/android/how-to-build-lineageos-14-1-t3551484

Now I'm busy trying to get the signing process to work, which so far, has been as complicated at the build process.

Just in case others come looking for guides, I've been reading through here:

https://xdaforums.com/chef-central/android/signing-cyanogenmod-rom-building-t3385756

https://wiki.lineageos.org/signing_builds.html

---------- Post added at 04:10 PM ---------- Previous post was at 03:28 PM ----------

Google is your friend.... but today, Reddit was my BEST friend.

https://www.reddit.com/r/LineageOS/...am_i_building_it_the_efficient_way_are_there/
[Verizon Samsung Galaxy S III] Droidriven:
In my time here, I've never even heard of or seen anyone flashing unsigned ROMs, I wasn't even aware that you could even build a flashable ROM without signing it because, for me, signing is a required default part of the process.

How you overlooked the fact that is a key part of the process is beyond me. Everything I've ever read made it a standard, not an optional thing.
[Verizon Samsung Galaxy S III] mjb32803:
Apparently quite easily.... /s

I went back and re-read through this link <https://xdaforums.com/chef-central/android/how-to-build-lineageos-14-1-t3551484>, then just to be sure, did a search on "sign"... found nothing pertinent

Then I went to this link other link I was using <https://wiki.lineageos.org/devices/d2vzw/build>

The only reference I saw was this text.. " Tip: Want to learn how to sign your own builds? Take a look at Signing builds."

"Tip" doesn't exactly scream that this is something critical and/or mandatory.... but hey, maybe it's just me?

To provide context, the "Tip" it is located AFTER the section that builds, and right BEFORE the section to install.

"Start the build

Time to start building! Now, type:

croot

brunch d2vzw

The build should begin.

Tip: Want to learn how to sign your own builds? Take a look at Signing builds.

Install the build

Assuming the build completed without errors (it will be obvious when it finishes), type the following in the terminal window the build ran in:

cd $OUT"
[Verizon Samsung Galaxy S III] Droidriven:
I'm not criticising, I just didn't understand how you came to your interpretation. Forgive me for saying, but, it seemed as if you didn't fully dig in to understand what you were doing, it seemed that you dug only deep enough to "throw" a build together.

Software development in android can be a risky thing as it can easily destroy a device just testing your work. Android devices aren't as flash friendly as PC, there isn't much you can do with PC to render it completely dead unless you flash an incorrect BIOS. Android is much more hardware/software specific than even the most complex PC system.

When developing android, it's best to research it from all angles and at all depths because there are a lot of specifics involved with most devices, specifics that can easily be overlooked even by those with experience and can cause major issues.

When attempting a process that you've never done, research the "don't do's" involved along with the "How to do's" involved in the process. Look for things discussing the mistakes that others made when attempting the process and their solutions. This gives you the advantage of being aware of the various mistakes to avoid and how to correct any issues if anything does go wrong.

In other words, don't just learn how to get to the door and open the door, also research what is on the other side of the door and what to expect, BEFORE opening that door. Waiting until after you've opened the door and stepped through to do more research is a disadvantage because you may have stepped into a pit that there is no escape from or any solution to.
[Verizon Samsung Galaxy S III] Ibuprophen:
Just a suggestion/recommendation [MENTION=4013543]mjb32803[/MENTION]...

You may want to create a separate thread for your Progress on your Unofficial LineageOS 14.1 for the d2vzw.

I only mentioned this to help prevent any, potential, backfire from XDA or one of the Official LineageOS Developers thinking that you may be, inadvertently, Hijacking this thread.

Maybe you can title it similar to the following...

[DISCUSSION][UNOFFICIAL]LineageOS 14.1 for the Samsung Galaxy S3[d2vzw]

I would hate to see you, possibly, receive any negative responses for your great work that is progressing very well.

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

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:
Thanks for the heads-up, and apologies if I've stepped on toes... I don't spend much time on XDA and I'm an old guy who doesn't know much about the protocols. I mistakenly assumed since I was trying to pick up where the OP stopped, it would be ok to post here. Obviously that is not acceptable. I will hold back on the posting for now and do some more reading on the "thread starting" process. With my luck, I'll start it under the wrong category and end up offending someone.
[Verizon Samsung Galaxy S III] Ibuprophen:
The following thread is from an XDA Administrator with a little guidance for New Threads.

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

This type of Discussion Thread can be posted within one of the following areas of the forum.

https://xdaforums.com/galaxy-s3-verizon/general

https://xdaforums.com/galaxy-s3-verizon/help

Just a little Helper for you... :)

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

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] Ibuprophen:
I just wanted to spread the word regarding the following thread for those who may be interested in a continued development for an Unofficial release.

[ROM] [Unofficial] [LineageOS 14.1] [Verizon] [d2vzw] [SCH-I535] by mjb32803

This specific conversation will need to take place there to prevent any misunderstandings regarding this Official and the above threads Unofficial releases.

Thank you very much for your time and understanding with this! :)

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

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] abd ulfatah:
Who can help me

I didn't find twrp recovery for sch i535
[Verizon Samsung Galaxy S III] J-Lindo:
Try this https://www.google.com/search?q=sch...j0l3.5867j0j4&sourceid=chrome-mobile&ie=UTF-8
[Verizon Samsung Galaxy S III] Ibuprophen:
It's located on the following link...

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

Good Luck! :)

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

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The XDA Labs Forum App on my Sanyo Juno device.
[Verizon Samsung Galaxy S III] Ibuprophen:
I think I'm going MAD, i tell you, MAD!

I know that I'll eventually figure it out...

Yesterday, i had tried a few different ways trying to install CM14.1 and they all resulted in the same outcome.

My thinking cap may be on a little too tight.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well they got those old ones through opengapp.org

---------- Post added at 02:21 PM ---------- Previous post was at 02:19 PM ----------

That's obvious by your avatar! XD
[Verizon Samsung Galaxy S III] Ibuprophen:
I love that avatar. LMFAO!

The movie it came from is a classic and one of my all time favorites!
[Verizon Samsung Galaxy S III] Master Cylinder:
EYE-gore! Helluva funny guy.

Dr. F.: "Damn your eyes!"

Eye-gore: "Too late."
[Verizon Samsung Galaxy S III] Ibuprophen:
Hump? What Hump?
[Verizon Samsung Galaxy S III] unitypunk:
whats the trick to getting this to boot, i have safestrap installed, when i install cm nightly and gapps and boot all i get is a black screen :-/ is safestrap to blame?

im running rooted 4.4.2
[Verizon Samsung Galaxy S III] Deliquified:
This ROM is not for safestrap.. You MUST have your bootloader unlocked and be freely able to flash roms.
[Verizon Samsung Galaxy S III] unitypunk:
How can I tell which roms will work with safestrap :(
[Verizon Samsung Galaxy S III] Deliquified:
They should be clearly labeled [Safestrap].. If they aren't labeled as such, assume they won't work for you.
[Verizon Samsung Galaxy S III] unitypunk:
Hmm musr not be looking hard enough. Haven't seen any haha thanks man!
[Verizon Samsung Galaxy S III] Master Cylinder:
Go to the (not Original) dev forum and you'll find what you're looking for there. Don't know how much dev is going on for that because I think you'll be limited to a TW ROM, but there are some.
[Verizon Samsung Galaxy S III] phonetool:
You have a phone with a blown Q-fuse and a locked bootloader. Your only option is to run a cleaned up version of 442 like SuperLiteROM. Sorry, no custom roms for you.
[Verizon Samsung Galaxy S III] J-Lindo:
I had this issue too, which is unfortunate because I really like [MENTION=5968361]IvsomEmidio[/MENTION]'s HEBF battery optimizer, which requires BusyBox to run.

However... I've managed to find a workaround, all thanks, funnily enough, to HEBF! First, go to the Play Store and install Stericson's BusyBox, as one normally would. Then, install and open HEBF (I can't post links, but it's not hard to find the XDA thread). It may be slightly different on a first install, rather than already installed like mine, but one way or another, you should get this error message saying that "It seems BusyBox was not found anywhere." Naturally, hit "Install Now", and it'll present you with two options: either go to the Play Store and download Stericson's app, or, if the app is already installed, hit "Install Now". And you, my friend (and anyone else trying to get BB to install on official nightlies), shall have BusyBox!

Edit: Also, the screenshots I posted are of my phone running the latest 12/12 nightly, in case anyone wondered if that issue had been fixed yet (it hasn't).
[Verizon Samsung Galaxy S III] Ibuprophen:
So BusyBox is installed but, you are unable to install /Symlink the Binaries?
[Verizon Samsung Galaxy S III] J-Lindo:
Erm... Could you rephrase that in more n00b-friendly terms? XD

If you're more or less asking whether BusyBox is installed but I can't install it directly from the app, then yes, that's what I'm saying. After installing it with HEBF, however, Stericson's app shows BB as installed. Here's another screenshot.
[Verizon Samsung Galaxy S III] Ibuprophen:
Okay... I'll try to explain it the best i can (i also uploaded 2 images to reflect what I'm stating below/what you should be seeing)...

First of all, look at the image you provided, at the top, you will see "BusyBox v1.24.2-Stericson is installed" and now look at where your green check mark is and notice the top drop down box where it states "BusyBox 1.25.1"... That is telling you that the 1.24.2 Binaries are currently installed in the "/system/xbin/busybox" but the 1.25.1 Binaries are awaiting to be installed but, have not. Keep in mind that installing and updating the BusyBox app doesn't install and update the Binaries. When BusyBox is installed and updated, you have to enter the app and execute the install (notice the bottom left button labeled "Install").

And Second, move to the left side (Applet Manager) and see if you can find/confirm the following (i also uploaded an image with an example of what the bottom 3 are referring to):

1) Installed in "/system/xbin/busybox".

2) States that the Binaries are" Symlinked".

3) If you scroll down a bit, you should be finding a handful of entries reflecting a handful of Binaries located in the "system/bin/toybox" are "Symlinked".

I hope you can understand what I explained above.

Good Luck and, hopefully, let me know that all is well...
[Verizon Samsung Galaxy S III] J-Lindo:
Ah! The version number difference totally sneaked past me. Whoops. And yes, I know updating the app doesn't update BB, only the bottom-left Install button.

As far as those binaries, it would seem that some are, and some aren't. The ratio of ones that are to aren't seem about 50/50 to me, though I may be off (gotta head off to work). Here's another couple screenshots.

Also, just for kicks, I went and tried hitting Install again to see if it'd update from 1.24.2 to 1.25.1, but no dice.

Also, just curious, are you color-blind? The checkmark in my previous screenshot was red, not green :P
[Verizon Samsung Galaxy S III] Ibuprophen:
This is a note to all the noob/uninformed members only...

When it comes to the BusyBox App:

Keep in mind that when you initially install the BusyBox App, it does not automatically install and Symlink the Binaries.

Also, if you already have BusyBox installed with the Binaries installed and Symlinked, updating the BusyBox App will not automatically update and Symlink the Binaries unless the box located on the extreme top right side of the first Main Screen of the BusyBox App, you will notice a box labeled labeled "Auto Update Busybox" has been checked BEFORE updating the BusyBox App.

If the Auto Update box has not been checked before updating the BusyBox App, you will have to enter the app and execute the update to the new Binaries and Symlinks by pressing the install button located at the bottom left (notice the button labeled "Install").

If installing/updating the BusyBox App and/or the Binaries, then that is a different issue in itself and help is out there with assistance. All you have to do is ask.

*** Please Note: this posting was prompted by me finding noob/unaware individuals having this type of issue.

***If anyone has located/noticed any issues, errors, mistakes,etc... Please let me know as i am not perfect myself :eek:

Happy Holidays!!!

---------- Post added at 11:17 PM ---------- Previous post was at 10:56 PM ----------

My bad on the color LOL!!!

Okay... Try this small thing not too many individuals know about...

1) Open the BusyBox app, be sure the bottom dropdown menu for the installation location is on

"/system/xbin", then select install. After it's done installing, exit the app.

2) Re-enter the BusyBox app, Go to the last tab to the right (the settings tab), check the top box and select the the button labeled "Clear Database", then exit the BusyBox app again.

3) Re-enter the BusyBox app and wait till the top of the page is at 100% loaded. Once it's done and disappears then move to the left tab labeled "Applet Manager" and see if all is well.

Many times this is needed to reflect that the Binaries are installed and Symlinked.

Let me know how it went...

Sent from the Bridge of the U.S.S. Enterprise using XDA Labs
[Verizon Samsung Galaxy S III] alado221:
So 95% of the things I do are buttery smooth. The other 5 percent of my use is YouTube. And it sometimes hangs up after a minute or so. I always change the source to 480 instead of 720/60 and it fixes this issue. Any suggestions?
[Verizon Samsung Galaxy S III] Ibuprophen:
Can you please explain what your question is specifically in reference to?