yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Quami:
Hello guys, if any could help me on this

Recently (4 days ago), I've flashed LineageOS 14.1 on my i747. I've used the stock room over for 4 months but I wanted to use Custom ROMs. I was in love with the LineageOS, everything was perfect, until I plugged my headphones (which worked on stock rom 4.4.2). The music was playing but no sound was coming through the headphones. When I take out the headphone from no sound comes from the speaker till restart the device.

I tried flashing the RRemix 5.8.3 and the Octos and the same problem occurred. I made a clean install (wiped everything via TWRP), installed the Micro GApps (tried with the Full GApps) but the problem still persists. The bluetooth works fine too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Juleast:
No root

Please make a version without root because for me root is really not a necessary need and I can't a play certain games because of root (e.g. Brawl Stars)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Page three or four of this thread has a possible solution i have not personally ran into this problem after I flashed the file everything works well for me but I didn't get feedback on the issue i did a little research and found the file and it worked for me

QUOTE=DerPuGNa;76306930]earphone/headset don't have sounds when plugged in, after removing it everything has no sound. Alarm, Music, Ringtone, Locking sound Etc... :confused:[/QUOTE]

I just recently ran into this issue flash this no need to wipe anything

https://www.androidfilehost.com/?fid=746010030569971886
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Most of the updates don't have root maybe the last one did because I updated my Ubuntu and needed to test compiling a full build with root but unless it says it has root then it does not have root magisk manager will squash the root restrictions on games issue pretty easy to install but the updates are not rooted unless it states that it is rooted my apologies for the inconvienience
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Juleast:
Thx!

Thanks for releasing so many updates for this device this device is a still a nice one to this day.:good:;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moo113:
Agreed, we really appreciate it. Even with whenyoucanlies irregular security updates beat most vendor software schedules.

[MENTION=6044923]Joker1716[/MENTION] Any possibility of getting the October ASB included in the next build? I'm unaware of the difficulties of such.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodflood:
[MENTION=6044923]Joker1716[/MENTION]

I just updated to the lastest ROM (10-07-18)... the patch level shows as July 2018; just wondering if you forgot to update the field OR we are actually at July patch level?

Appreciate you putting these out! Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I compiled again today. I did not forget to update The field. The security patch level is updated to September 5th that is the most current as of yet. I am glad that it is being enjoyed by other people i do not use this phone but I did at one point and wanted to keep it going. The only compensation i get are thanks and knowing that the device lives on. I hope that it can continue to bring enjoyment to the many people who have this device i build four different versions that's why they were whenicanlies but enjoy link will be up in a minute or two
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlotTech:
[MENTION=6044923]Joker1716[/MENTION] I have been running this update since yesterday and everything is running as expected. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moo113:
Does any other users have the issue where the device boots from a cold state when plugged into a power source? Looks like offline charging might have an issue. I had this on an old OnePlus One at one point, but I think it was a kernel specific problem. Searching for a solution!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlotTech:
[MENTION=1172632]moo113[/MENTION] Yeah mine does it too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] argonax:
How can I get 4G or LTE signal using lineage 14? I am always getting H+ signal only but my other smartphone has 4G signal..

Thanks for the help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Dialer *#*#4636#*#*/Phone information/Set preferred network type.

Settings/More/Cellular Networks.

Idk I don't have service on that phone but you can try those.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
QUOTE=moo113;77868971]Does any other users have the issue where the device boots from a cold state when plugged into a power source? Looks like offline charging might have an issue. I had this on an old OnePlus One at one point, but I think it was a kernel specific problem. Searching for a solution![/QUOTE]

Mine does not have that issue the Samsung logo appears but it starts charging and does not boot up

I'm gonna go out on a limb here and say it's prolly your recovery. I'm running twrp 3.2.3-0 try updating your recovery and see if the issue persists
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] argonax:
My i747m cannot connect to wifi even if in the settings>wiFi i can see the wifi name but it has status "saved". i reboot the phone and still my s3 wiFi will just show opbtaining IP address and i will go back to saved. and I cannot connect anymore to the wifi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moo113:
Also 3.2.3-0, but my devices aren't true AT&T as they are the Canadian models. Strange. Of all bugs, this is by far the least impactful so who am I to be concerned anyhow :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Juleast:
Btw, what are updated on these new releases?

:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoshkapundrick:
To me the important part of these updates is the update to the Android Security Patch Level.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
This rom is awesome but I still have the speaker phone problem during calls. If I put a call on speaker phone, the other person can't hear me. Does anyone have any insight to this? A fix? Maybe it's just my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Juleast:
I see so I assume that the security patches gets updated here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] argonax:
need help sometimes my s3 i747m is hanging or lagging even if i close all recent apps and it is from clean install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
Unable to get any of Joker's ROMs to boot.

Tried clean and dirty flash with the 20180412 ROM and each update, but no dice.

Tried clearing data, cache, etc in TWRP 3.2.3-0 before flashing, but after flash phone still hangs on Lineage loading animation. Have let it sit for upwards of 60 minutes. Sometimes I get "process system not responding", which I ignore.

Tried this too.

I have an unofficial 14.1 from javelinanddart for d2att dated 20170127 that boots fine when flashed. Why does this one work while Joker's won't boot on my device?

Is Joker still working on his builds? Does anyone know of other updated unofficial builds for the S3?

Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I am still working on the builds. I have been attempting to compile 15.1 which I have but will not boot. Neways what bootloader and modem are you on. It needs to be nj2. Are you just flashing the rom? I need more info to help. Previously in this thread I posted a video of a dirty flash but all that shows you is that it will boot. Something is different with your device than others so that needs to be identified b4 you can continue. What's the model of your device, the baseband and modem, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
That's great to hear! Running Oreo on the S3 would be very impressive.

I was on LK3 earlier, so I've updated to NJ2 today (followed this post https://xdaforums.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654) Getting the same result for your 20180412 and 20181007 build with a clean flash using TWRP 3.2.3. Wiping Dalvik, System, Data, Internal, Cache every time. I'm only flashing the ROM. No GApps or root for now. Just trying to get the ROMs to boot. I did watch your video and read all the other thread posts hoping for a solution thinking I missed something.

I have a d2att (I747UCUFNJ2) now on bootloader and modem NJ2 (verified with getprop in TWRP terminal)

Thanks for the help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
use Odin to flash this full NE4 firmware update. Once you're up on stock NE4, you can take OTA updates. You'll go from NE4 -> NJ1 -> NJ2.

enewman17 has posted everything you need to update manually linked to this thread. If you go this route, read that thread carefully, then read it again and make certain you understand it. You have to update sequentially MJB -> NE4 -> NJ1 -> NJ2, and you have to reboot into system between every firmware update. Be super careful if you go this route. This phone is easy to hard brick when messing with bootloader and modem.

Did you update incrementally and reboot each flash b4 flashing the next? I personally used odin to flash updates to the stock firmware up to nj2 then I used odin to flash TWRP. The problems you are experiencing sound like the warnings given for not updating incrementally it is a tedious process but that is how it has to be done to avoid those issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
Before my previous post, I used TWRP to update incrementally following enewman17's thread. From LK3 -> MG2 -> MJ2 -> MJB -> NE4 -> NJ1 -> NJ2. I would flash in TWRP 3.2.3, then hit system reboot, watch for the SAMSUNG boot logo, then wait for the ROM to start to load, then pull the battery and reboot into TWRP for the next flash. I did this for each of the 6 firmware updates.

I way trying to reboot into the OS, but after the first firmware flash, the ROM that was working before wouldn't fully boot.

I'm currently on NJ2. Are you suggesting that I "backflash" from NJ2 to NE4 and re-flash each incremental firmware back up to NJ2?

What do you mean "reboot into system" each update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I spent from about 6pm today till midnight putting together an all in one zip file and guide as well as a video. I will be posting the links as soon as they upload. The all in one zip contains EVERYTHING one needs to restore STOCK, update bootloader and modems and flash lineage 14.1 (see picture). That being said, it is a large zip file (1.6-1.8gigs). The zip file will be called "Odin3_v3.13.1.zip". The guide is in the zip file on README.

Odin3_3.13.1.zip(all in one zip)

https://www.androidfilehost.com/?fid=11410963190603866416

YouTube Video

[youtube]gNDzh6iB0Gc[/youtube]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
Awesome! I'll give this a run tonight and report back tomorrow. Thanks for your hard work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
No Worries. Have fun.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
Now I'm really stumped. I followed your directions exactly as outlined and everything worked flawlessly right up until the final reboot. Verified that I'm on NJ2 bootloader and baseband.

My S3 has been trying to boot into Lineage for about 2.5 hours now. In your video it looks like it took about 10-13 minutes, which is normal. That's how long it took to boot after flashing stock ROM via Odin and that's how long it takes when booting javelinanddart's 20170127 LOS build.

I haven't figured out why it won't finish booting these builds. Is there a log file that we can look at?

Could Knox be causing an issue?

My volume down button hasn't worked in years, but that doesn't prevent me booting into download mode as I built a usb jig for this project a few days ago. I've been using adb reboot command when I can also.

Phone isn't cracked or damaged in any other way. 16GB device with a SanDisk 16GB microSD. No SIM inserted.

I've tried booting with USB cable plugged in (to keep battery from dying) and also have let it sit without cable attached. Doesn't seem to make a difference to anything but battery.

The two cameras have been physically removed from this device as I'm intending to use it in a sensitive environment that doesn't permit cameras. I can reinstall them as a test. Hasn't prevented the older builds (pre-2018) or stock ROM from booting though.

Trying to think of anything else that might be relevant...

EDIT: Booted right up once I put the cameras/proximity sensor back in. It looks like I can't use the later LOS builds without the cameras installed. Kinda weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Try flashing a new build and flashing the old boot image on top of it then reboot. so wipe factory reset. Install newer build install boot image (youll have to extract it from older build first) then reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
With the cameras installed, the phone is working with your most recent build.

Which boot.img are you referring to? Also, how do I flash just the boot.img ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Do you have a 14.1 rom that will boot on the device? (javelinanddarts) if so, flash the rom that will not boot with the cameras installed but before you reboot go back to install click install image and navigate to the javelinanddarts boot image( that you will need to have extracted before this process) select it select boot then reboot system. This will only possibly work if it's a 14.1 rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
I flashed your latest full build (doesn't work without cameras) using TWRP, and before rebooting flashed the boot.img from the javelinanddart build (works without cameras) using the TWRP flash image option but it wouldn't boot. Same issue as before.

I clean flashed the javelinanddart build just to check the version and make sure it still works with NJ2. It's Lineage 14.1, Android 7.1.1, Security patch level Jan 5, 2017.

I was able to boot after several reboots and deleting the Setup Wizard (didn't have these issues before).

Edit: I did the above with cameras removed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Did you try removing them after you booted up successfully? I really don't know how to help any farther than that. My experience with trying to run a device with missing hardware is non existant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
Yep. Tried both ways (1-whole process with cameras installed, remove cameras after, 2-whole process without cameras installed). Never got a full boot.

I'm also out of ideas, but I do appreciate your help along the way. I learned quite a bit.

I'll just run the Jan 2017 build on this device for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
I found that when I couldn't get this rom to boot, I would power down right after flashing, then boot into twrp, and select reboot. Then it worked. Could have been a fluke tho..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skeebum:
Thanks for the idea. No luck though. Something in the later builds prevents the OS from booting while the cameras and proximity sensor are disconnected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
Flashed the latest, no camera app, and flashlight doesn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoshkapundrick:
I have same problem(s). Open Camera doesn't work either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Did you guys clean or dirty flash? I am sure it's because I got rid of my vendor/samsung folder. I am also pretty sure that if you dirty flashed you wouldn't be having this problem. So if you flash the build previous to the newest then reboot the device then dirty flash the newest build you should be good to go. I will re add the vendor/samsung files next build. I cannot use them to try to build 15.1, I mean I can but they aren't from a 15.1 rom so I thought it would hinder the build so I trashed them but forgot to add them when I updated 14.1. They are not open source files so they don't come with the repo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
I clean flashed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoshkapundrick:
I dirty flashed 12/7/18 over 10/10/18.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodflood:
Hello,

With this,

ROM: Joker's d2att 10-10-18 version

Bootloader: NJ2

Radio: NJ2

TRWP: 3.2.3

I dirty flashed 12-7-18 build over 10-10-18. I removed Lineage superuser and added Magisk. All three together. Wiped Dalvik and Cache. Rebooted. Camera is not working. Would dirty flashing the 10-10-18 version fix the problem for now, until a new build comes out?

Thanks!

Edit: I am back on 10-10-18 build and camera is working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
It will take about 16 hrs for the roms (d2att, d2tmo, d2spr, d2refreshspr) to build. I will have them by tomorrow. I apologize for the inconvenience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
No apology necessary, thanks for your effort.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Update Posted. Camera is accessible from lock screen, and gallery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Screenpics
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
Finally! The speakerphone calling works. I'll be putting my galaxy note aside to test this. Thanks

Update: All apps, and functions working perfect, runs smooth, fast and battery drain is not bad at all, not the best, but definitely above average. This is so good, I'm very thankful. I wish it had some of the interface, functions, and toggles from carbon rom, but that's being picky, this rom is awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoshkapundrick:
Dirty flashed over 12/10/18. Working beautifully now. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlotTech:
Thanks [MENTION=6044923]Joker1716[/MENTION] the 12/15 image is working great so far.

I did a clean install and prevented a bunch of gapps from installing and my phone is significantly faster.

I was having problems with the system not responding and having to reboot the phone about once a week before so hopefully ditching Google Now Launcher will remedy that, as I didn't know it's been eol'd.

Thanks again for your work Joker1716
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] argonax:
Can i dirty flash the 12/15 version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlotTech:
Can't see why not, someone else has. As long as it's an earlier build you are coming from that is. If it doesn't work out you'll have to wipe and start from fresh.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VTMongoose:
Hey, I downloaded and installed the 12-15-18 build and everything seems to be working, except that the phone won't recognize my SIM. I see there's a fix posted in the 2018-04-12 build in the OP but I would think that would be irrelevant by now... do I need to follow any special instructions? Or do I need to do that build.prop extraction thing but with the 12-15-18 ROM?

edit: I copied build.prop from the zip into the folder as instructed in the OP using the one from both the 12-15 build and the 04-12 build. No dice with either. I am on firmware version I747UCDLK3. Is this too old? Do I need to upgrade?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Try nj2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monstermonkey:
I noticed on afh a los 15.1 d2att build got posted. Has anyone been able to get it to boot?

I just get kicked into the Samsung downloading screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidk21770:
It's working great here. Backed-up, installed, rebooted. No issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] teestreetx:
I am trying to flash the Lineage Os 14.1 zip posted here on page 1 but it doesn't seem to recognize my sim card and when i flash the bootloader/modem zip i get error: 7. Please any help

My Baseband version is I747UCDMG2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
I can't find 15.1 anywhere, can you share a link?

---------- Post added at 09:05 PM ---------- Previous post was at 08:52 PM ----------

I can't find 15.1 anywhere, can you share a link?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I'm wondering if anyone reads these forums or do they just smash the download button and hope for the best? [MENTION=9783512]teestreetx[/MENTION] = 6 posts below the first post on this thread there was a discussion on needing to have nj2 installed and that it has to be done incrementally. [MENTION=3701903]Bugly Astard[/MENTION] & [MENTION=9506663]monstermonkey[/MENTION]= there is no 15.1 yet. ( [MENTION=4235848]davidk21770[/MENTION] is prolly talking about these 14.1 builds.) I've been working on 15.1 for a while. I have compiled it multiple times and have not had any luck getting it to boot. I upload them to AFH so that I can test them on my device. I've made progress now it only bootloops instead of bailing to download mode but a bootable build has not happened yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
I read them but my S3 still isn't working yet. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoshkapundrick:
I read. But since I have 4 s3's running your 14.1 (flawlessly) I have no problems. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Update Posted built fresh, clean flashed, everything looks to be working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidk21770:
Sorry, been away for a while. You are correct, I'm running your nougat on my wife's s3. Sorry if I misspoke about oreo. I do read and update. But since it's my wife's phone and she is more about keeping things the same, I'm an infrequent visitor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
What exactly do you mean? What's changed? The only problem I've had with this rom is that Google maps is very laggy, almost unusable.. Other than that, works awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Replaced vendor blobs with newer ones from TheMuppets repository . the ones I had been using were from a year ago and were pulled from one of the last official builds. Along with various other things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
Latest release is working great, except for randomly the screen goes black. Apparently other ports on other phones have this problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davidk21770:
We're having problems that MMS messages take a really long time to come down (5 minutes or more some times). Doesn't appear to be a slow data issue. Anyone else seeing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I have spent the morning and afternoon setting up the automatic updater app called ''OTA Updater-2.0.5.apk'' to work with the four different variants of this rom. I will either write a tutorial on how to use it, or post a link to a video tutorial i may make. The app will check for the updates when you ask it to manually or on a set schedule it will download the update and flash the update through prompts in the app. If you do use it consider heading on over to the OTA Updater page, like and possibly donate. The developers work hard to bring roms ,kernels, apps, etc to users to simplify the experience and make the experience easier as well as better. Show some love. I have been updating these apps for over a year now and have recieved three donations within the last 30 days

"Thank you William K Wilcox".

"Thank you Aaron Donnely".

"Thank you Kelwyn Friesman".