yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Is anyone trying to build lineage 15.1 for this device? I have been trying unsuccessfully for two months. I have gotten as far as like 30%. I changed a few lines here and there and got it to build a kernel but, after it builds the kernel it runs into sepolicy errors. I'm making progress but I was wondering if anyone else was trying and had knowledge we might could swap? I'm not a full fledged developer but I have made progress.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
You could ask for help from previous mainteiners of this device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
https://xdaforums.com/galaxy-s3-att/development/rom-octos-t3532529/post75186090#post75186090 the reply on this post said he will maintain the device he was on octos team .you can ask him for help, hope he can

https://xdaforums.com/member.php?u=6264948 his page
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
I don't think we will ever get 15.1. Last time I checked the kernel change, it's huge. Almost you need to rewrite everything... Can't use the old stuff. To be honest, it's not hard to port a rom. You can learn it to do it yourself in probably a day. But to build a kernel, it will take a team plus many months. It's not a one man's job. Most of the kernel developers here are taking a similar device as a base and port new functions or changes. Unless we can get a similar base, I don't think we will get a kernel works for 15.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
It's not easy but I think it's possible I keep trying in my free time that I don't seem to have alot of
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I have gotten it to compile to 52%. I ran into a failed parsing overlays error and I am trying to work through this error. Alot of work and time has been invested in this I'm hoping it pays off soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
you can do it bro :good::victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Still encountering errors but I've gotten it to 75% or better. Still trying
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
Awesome, bro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
Good luck to you. What's your base?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I've gotten all the way through the build basically. But I keep getting a recovery partition size too large error. I am trying to work it out. Not very successfully but I am still trying. I have devoted all of my free time into trying to get this done. Hopefully it's worth it. Even if it builds the Ota zip, it may still not even boot. But I am dedicated to attempting to make this happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I finished still gotta try to flash it. About to pass out no sleep in a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Wouldn't flash. Changed updater script to kinda force it to flash. It flashed but will not boot and messes up the system mounting. I guess I will go back over my device files try to work on the partitions and other stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
Awesome! Glad someone is doing this for us!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
Don't give up bro! And try to ask for some help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I managed to compile the recovery it's still a little iffy but it does flash and factory reset. dirty flashing works but if you factory reset first it deletes everything and does not mount to the usb to the computer. It also does not match the assert right. what i did was unzip the d2att rom.zip , delete the assert line on the META-INF/com/google/updater-script, and re-zip to get it to flash. It did flash. haven't tried with a SD card yet. So it's not where it needs to be just yet. If you plan on messing with this recovery it will flash in TWRP under install/install image the lineage recovery will not flash an image so make sure you know how to flash one in odin, and have everything ready if you plan on going back to a different recovery. The rom i built with it flashes tries to boot up led light pulses like 7 times and then goes into download mode . Making progress but I'm going to be taking a break for a few days. AYOR I assume no responsibilty for whatever you may do to your device with this file. if you dont know what you are doing dont mess with it if you do its At Your Own Risk . Enjoy.

if anyone wants to check it out here is the download link

#Recovery

https://www.androidfilehost.com/?fid=11410932744536990805
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chuckles5150:
Truly appreciate the amount of time, effort, and sleeplessness you have put into and endured for this development! :angel:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
Can you not use twrp?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Not really sure if I understand the question. I'm using the d2att device tree. Msm8960 board, krait architecture. I built for the klte (krait, Msm8974) which is very similar so I could see how everything goes down then compare, make changes, and wait an extremely long time for the build to compile. My computer is old. I run into .jackserver problems like there's no tomorrow. I am a landscaper I cut grass. build walls, lay sod, plans flowers,trees, dig up flowers,trees, etc. That being said I am a tad out of my element but I started doing android developmental things on my s2 and have not stopped sometimes I think smoking crack would be easier but I kinda enjoy this type of stuff. Just basically saying I have no clue what I'm doing in technical terms but I can read compare and research and maybe get something accomplished
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Yeah I can use TWRP.?? I can use what I have build a new one etc. But I'm trying to build 15.1 for the d2att and lineage recovery is included in the build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
Ok, thanks for explaining! I thought roms usually didn't have the recovery come with
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
It doesn't flash, but it's stored in the system folder if I'm not mistaken. I think it may say recovery.from.boot or something like that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godkingofcanada:
hmm. you caught my attention. I have some thoughts. do you have your device tree? that should tell you in one of the mk files what sizes the partitions should be so you can set them. and at some point between android lollipop and nougat im pretty sure they changed the file system structure. something about board files. it might be very difficult to boot a rom above MM on this device. but that being said if MM works nougat should work... most nougat roms are based off of a MM bootloader. same with oreo that ive seen so far. you may have an easier time building or finding a device tree and just syncing the lineage 15 repo then adding your tree to the vendor folder and using lunch to compile a rom. i know my s3 is only on MM. i hadnt touched it in years. and i was cleaning an old desk and found an s3 and galaxy ace 2. so i charged them up and came on xda looking to see what i could do with them. sadly nothing for s3 above MM in the form of a stable rom can be found yet. i was about to start poking around seeing what the difference is between building for the s3 and the s6. ive used droids for years but only got into development in the last couple years when i started college because they go hand in hand. you can find my work over in the s6e+ forums. i've got builds of 9.0 and 8.1 for the s6e+ and note 5 going. my device now which is the s6e+ is running 9.0 unofficial lineage 16 which i ported from s6. i would like to get my s3 to oreo or pie. but for some reason in my experience PIE is easier to work with then Oreo, when i built oreo for my phone it was a nightmare, kernel mods, flashing zips to fix things. with pie it was just build n boot and look at bugs, i never had an issue getting it to boot. you can also try the google 8.1 GSI build, and see if it will boot on your device. but there is no list of what works and what does not on GSI builds, its guaranteed to work on google devices, but others are a shot in the dark, it doesnt use your phones real hardware drives, more just generic stuff that may or may not work. but it might.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
You should build Treble for the s3. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godkingofcanada:
I would like to do something for the s3, however being unsupported by lineage means I have to find a device tree. My s3 has no USB port
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
How do you charge then?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
you are right i saw that developpers had built los 16 easier than los 15.1, it maybe better to try build tree for los 16 hope it works better than los15.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godkingofcanada:
I have an external battery charger
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
Could you replace the port? Or is it too expensive?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
Which s3 you are talking about ?

Because both the international version (1gb ram) and us variants (2gb ram) are on stable nougat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godkingofcanada:
Mine is 1gb. And it's not stable. I went back to cyanogen 13

---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------

I tried to downgrade the phone back to 4.1 to unlock it free and bricked it. Fried the Mobo. Another xda member sent me an old broken s3 they had to swap the boards. So I have a t mobile board that just resets randomly but works and I have a Telus board that doesn't have any issues but the USB port is weird. It does work but you have to play with the cord then not touch the phone. It took me a couple hours just to root it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
Maybe the intl version can't handle recent android versions anymore but it's still maintained on lineage tho. On d2 nougat is pretty stable even though the cpu cries sometimes and the battery can't take it anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godkingofcanada:
My biggest issue is getting device trees. It's a cryptic riddle. You can get all or most of a tree from GitHub, but you need a kernel vendor and device tree to build. Sometimes you can find one n sometimes you have to build it. Vendor... Lol. And then when tutorials tell you how to use lunch they all don't explain what to do with all these files. Infact they don't tell you to get the device tree, they rely on lineage and lunch to have it. So... If it doesn't you gotta fly blind n learn

---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------

Quite possibly. When I went past mm the phone got buggy fast
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arubamon:
Lineage 15.1 Builds on Android File Host?

Maybe I'm slow, but I see three Lineage 15.1 builds on Android File Host when searching for 'd2att', all posted by the same uploader that posted the 14.1 builds: https://androidfilehost.com/?w=search&s=d2att&type=files. I tried clean flashing all three, however none booted on my SGH-i747. Am I missing something? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
is there any news about this rom ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
Still working on it. I did an Unofficial DirtyUnicorns Nougat build for learning purposes, it's posted in the Forums.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I can't get a build to boot but I am trying. I am sure it's a kernel issue considering I flash it and am able to navigate through adb and twrp file manager. The kernel I believe is not looking in the right spot or isn't able to idk but I am continuing to try. I need to take a break so that I can update the 14.1 builds and that will be done by this weekend. If anyone knows anything about kernel building build one. I am learning but I can't build one that will boot 15.1. I can build ones for 14.1 that will boot though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
thanks for your efforts, i hope you skip building los 15.1 and try 16 ,it maybe easier to build like other old devices that get los 16
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javedgh:
any oreo rom for this devise
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
UPDATE:

I am figuring this out. I was wondering why I could get my initlogo to show up on booting one of my builds but not anything else, so I'm messing with the proprietary file placement into the correct vendor folder. I can file manage in twrp and see the files are there and when comparing to other device I see that the vendor files are being placed in the wrong vendor folders so hopefully I can get this worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Interesting, I know many devs who have tried to build Oreo for d2 but failed. Seems like you're getting closer! Good luck man. I think it's awesome that you're still updating N for this old beast. Makes me wanna pull my old d2 out & flash it lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joker1716:
I am failing, but I keep trying. Its because I'm insane. But I have learned alot so it's not a completely wasted endeavor
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 92millmac:
I just wanted to say thanks Joker1716 for the hard work on this phone! My favorite phone period, I was honestly getting worried that everyone had given up on this device. Can't wait to see what you come up with!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eosirl:
A new April 11th version of lineage-15.1-20190411-UNOFFICIAL-d2att.zip was posted here:

h t t p s : / / androidfilehost . com/ ? fid = 1395089523397938962

I downloaded and attempted install it over the working version 14.1 Lineage. But got the following error:

Installing zip file '/sdcard/lineage-15.1-20190411-UNOFFICIAL-d2att.zip'

Checking for MD5 file ....

Skipping MD5 check: no MD5 file found

Warning: No file_contects

e3004: This package is for device: d2att, d2lte, d2can, d2tmo; This device is .

<RED>Updater process ended wth ERROR 7

Error installing zip file '/sdcard/lineage-15.1-20190411-UNOFFICIAL-d2att.zip' </RED>

Updating partition details....

....done
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
does it work on d2tmo ? i can flash it if it is Compatible with this device to check this problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eosirl:
I don't believe so. I don't have d2tmo only the d2att version of the Galaxy S III or S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SnowFuhrer:
Are you getting anywhere or is it a failed endeavor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cnt:
I hope you get there...

I really hope you get there. I have an old i747m I would love to use as a travel phone - given the crap that border services sometimes wants to look at your device contents, I would like to keep a basic phone that I can I can connect to my email servers during my trip and disconnect & flush as I cross the border.

The i747m was a workhorse phone. Slow by today's standards, but this would be a great use for it if someone could keep the security updates coming.

Thanks and keep up your efforts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
My time is short these days, but I'll support the effort in any way I can. Send me a PM, let's get a chat room set up so we can get everyone together.

(former pac-rom / team octos maintainer)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
we hope you can help him to build this rom for this device after waiting two years to get an update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Well, it's a lot of work since they google changed the API, most phones that didn't ship with O didn't make it to O. And at some point, the S3 just won't have the power to run the current OS. I'm actually pretty amazed we kept it going as long as we did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
get

thanks for every thing you have done for this device ,we are sad because older devices like s2 i9100 had got los16 and i9300 and some devices with msm8960t got it but this device hadn't
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Which ones with msm8960 have made the jump? I was unaware that any made it. The i9300 is exynos, completely different phone even though it's an "s3".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
xperia v has msm8960 and get oreo 8.1.0

https://xdaforums.com/xperia-t-v/v-development/8-1-0-carbonrom-t3840284

https://xdaforums.com/xperia-t-v/v-development/rom-8-1-0r43-aospextended-rom-v5-8-t3845646

is there any way to port the roms to d2tmo ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I don't think we can really port it without a base rom.

We might be able probably by changing the kernel a bit.

I want to do it and I will try to make some research about porting to other devices.

(Btw I built my first rom a week ago so I have a bit of experience)

---------- Post added at 10:55 PM ---------- Previous post was at 10:45 PM ----------

https://github.com/LineageOS/android_kernel_samsung_d2/tree/lineage-15.0

Someone made a oreo kernel!

I will definetely try it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
https://xdaforums.com/xperia-t-v/orig-development/lineageos-15-1-xperia-t-tx-t3758219

i dont know if this can help ,there is los 16 for this devise too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Well, that's much more feasible. I just nuked my octos-o dist yesterday too. Probably best to start with lineage anyway.

It's true there's a lineage-15 kernel branch, last update was 2017 though, who knows if it works.

I checked with twrp, and amazingly, they have kept it up to date, pretty sure an update is required to go to O and P.

https://eu.dl.twrp.me/d2tmo/

I'm slammed right now, and my daughter lost the phone (still in the house, somewhere), but I could take a look at some point. It would be a huge triumph to bring this phone even to O.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I am really suprised no one did it yet. I am currently compiling Oreo (Lineage 15.0) for this device and I will see how it goes :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I ran into the same sepolicy errors that Joker1716 ran into. :(

We need help!

on the s3 i9300, the only maintainers are TeamInFusion. They have made spectacular progress.

Without them the i9300 would be as dead as all of the d2 devices
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
los15.0 will not work even it has branch i think it hadn't completed and still has errors

building los 15.1&16 with some help from xperia v roms will be more effective , I hope this works and keeps the device alive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
Actually, This device (Sony Xperia V) uses a more common kernel for more modern custom roms android_kernel_sony_msm8x60 which can be found here https://github.com/LineageOS/android_kernel_sony_msm8x60.

We need a bit of help and I am not willing to give up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I have started porting the sony msm8x60 kernel. There are 88 changes that were made between the branch cm-14.1 and lineage-15.1. Let's hope it will work!

My base kernel is kernel_samsung_d2

The kernel that I will port is kernel_sony_msm8x60

I will let you guys know how it goes!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
It's much better than before. I get fewer errors and I can get up to 6% for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
if anyone knows how to extract rom on windows to do port ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
https://github.com/zawzaww/androido...4kMNV2qm5hHpcBkvP67o1Tb7tyFHwz1iqteEUteXC6pYU

i found this guide igt may helps to create a new kernel and branch
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
https://xdaforums.com/htc-one/development/rom-lineageos-16-0-t3960329

another los16 rom works on msm8960 device , that is a good thing and it means it is not impossible to do it ,sorry for my frequent comments but i dont have enough requirement to build roms or buy a new device ,i only have hope to get new los version on my device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
I have been busy theese days ? and I haven't made much improvements scince last time. Making los 16 for this device is not impossible, but the problem remains the same, there are not any devs currently supporting or updating this device. I tried, and I will still try my best when I will have time. Also, I am not a dev, I am just a person that learned how to compile using the internet... I am not saying that I am giving up, but I am not too active. Also, porting a kernel or rom does not require software, it's better to copy&paste the files and edit them. With that being said, there are 3 options: I figure out how to compile it properly, or there might be someone that shows up with a miracle, or you will have to ask the devs that make roms for msm8960 devices. I will try to ask some people if they want to help such as AdrianDC maybe he wants to help... Also thanks for helping me with finding other similar devices so now I can compare the sony and the htc m7 and find out which changes I should add ?. If someone wants to help please do so!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasan.sy:
i asked a developer who tell me i have to edit files in source so i am afraid to make something wrong, may AdrianDC can help you to do the changes and port this rom without errors, there is a xiaomi device with msm8960 which get 9.0 and adriandc helped them
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexenferman:
There is new hope!

There is someone still working on the Htc m7 (MSM8960) and has branches up to Los 17.1 (Mentioned by hasan.sy)

here it is: https://github.com/htc-msm8960-dev/android_kernel_htc_msm8960

Now, what I can do is compare both the Sony Xperia V and Htc m7 kernels and have more hope of finally bringing at least Oreo for this device!

The only problem, (at least for me) is how can I compare the changes made between the cm-14.1 and 15.1 branches.

The Htc m7 was officially supported until cm-14 and the guy still working on it put it on his own repo therefore I cannot compare those 2 branches.

Edit: I used winmerge and there are 300+ changes...

I think I will be skipping oreo...