yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] PACMAN456:
I'm getting an error when installing this rom on twrp. it says "error executing updater binary in zip". Do you know what the problem is ? thanks

---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------

I'm getting an error when installing this rom on twrp. it says "error executing updater binary in zip". Do you know what the problem is ? thanks
[Galaxy S III Original Android Development] NZedPred:
Either a bad download or you need to update twrp would be my best bets.
[Galaxy S III Original Android Development] underdoq:
Thanks

Is this rom more safer to use than those other available one's that i've found also to be most popular(oreo beta and pie alpha). I guess 500+ replies on this thread say something. Pls share you opinion. Thanks
[Galaxy S III Original Android Development] PACMAN456:
Can you tell me how to update twrp? i can't find a decent tutorial on how to do it.
[Galaxy S III Original Android Development] curiousrom:
How To Update TWRP - Official LineageOS 14.1 Safer?

You can use Odin on a Windows PC or TWRP itself on the phone to update TWRP.

See S3 LineageOS Super Clean Install & Samsung Firmware step #3 & 4.

***

Official LineageOS 14.1 Safer?

There are 2 major differences between the Official LineageOS 14.1 for S3 i9300 & [ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [BETA] or [ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 [ALPHA]:

No dirty hacks in Official 14.1 to make it work.

Official 14.1 has the major Android & Linux SELinux Enforcing (Wikipedia) security feature as seen in > Settings > About phone.

For those who want to know more check Security-Enhanced Linux (SELinux) on the Android Open Source Project site:

For some more nerdy explanations: How dangerous is the fact that SELinux is in “Permissive” mode?

This is especially important if you use your personal accounts, shopping, banking, etc. because root + SELinux permissive or disabled + apps from shady sources = zero security. :eek:

SELinux Enforcing is important or not depending on your S3 usage & setup and this is the user's choice.

***

I successfully ran Official LineageOS 14.1 on my S3 i9300 as a daily driver for over 10 months without any problems except for minor stuff described in LineageOS S3 i9300 Known Issues - Workarounds & Bugs and applying those tips for better battery life & more fluid UI: S3 LineageOS 14.1 Battery Optimization.

If the Official LineageOS 14.1 S3 i9300 builds are not available anymore here (they will be removed eventually as no new Official 14.1 builds will be made) https://download.lineageos.org/i9300 you can find copies in this archive: https://files.moskvich.xyz/LineageOS/14.1/i9300/

I did not try [MENTION=7346927]NZedPred[/MENTION] security patch updated unofficial 14.1 linked in his post here but if he is using the official LineageOS source it should show as SELinux Enforcing also.

***
[Galaxy S III Original Android Development] kurtn:
I don't have the impression [MENTION=7346927]NZedPred[/MENTION] or anyone else does significant work on S3 kernel since [MENTION=2959051]forkbomb[/MENTION] left community like half a year ago. So security patch level only tells half of the truth. User space bugs get patched. But we are missing some important kernel patches.
[Galaxy S III Original Android Development] curiousrom:
AFAIK you are right & that's why SELinux Enforcing is important as quoted in the post above: "SELinux operates on the principle of default denial: Anything not explicitly allowed is denied.".

This is a search in the LineageOS Gerrit with the kernel used in S3 i9300 and nothing new since Aug 01, 2018 and the last merged commit was in Jan 19, 2018: project:LineageOS/android_kernel_samsung_smdk4412 branch:cm-14.1.

"...since @ forkbomb left community like half a year ago" - If you want to ping Simon you have to use his full XDA username: [MENTION=5405215]forkbomb444[/MENTION]. I was worried about him because if you check all the links related to him that I posted in Bunch of Links: S3 i9300 LineageOS, Developer & Oreo Project there was no activity since Oct 2018 but I see a January 7, 2019 commit in https://github.com/fourkbomb

Who knows, maybe he's busy studying & working, or sick, depressed, moved to Windows programming or met a sexy girlfriend or boyfriend and stays in bed all the time. :)

***
[Galaxy S III Original Android Development] kurtn:
Oh he still works on mainline kernel!
[Galaxy S III Original Android Development] ChronoMonochrome:
There are none hacks are involved in my unofficial builds of LOS 15.1 and LOS 16.0 anymore (except for the kernel) ;P

If you check the repo for LOS 16.0 there's just one patch left for the vold which was just cherry-picked from [MENTION=2222292]rINanDO[/MENTION]'s LOS 16.0 and is probably not needed for S3.

Yet it's going to be even more mainline-ish in the future builds as I just will get rid of some custom kernel stuff and hopefully get it working more stable than it currently is.
[Galaxy S III Original Android Development] ArdaCsknn:
Even who cares about security on a 7 years old device. You have to sacrifce some things in order to make it work better. I don't know why he keeps bringing that SELinux thing.
[Galaxy S III Original Android Development] ChronoMonochrome:
That can be still needed if we ever care of trying to make this official, though :)

Yet it can be pretty difficult to get it working properly on a such an old device, but still should be doable (at least I hope so).
[Galaxy S III Original Android Development] ArdaCsknn:
Yeah definitely but it is going to take some time, it is in beta and as you guys progress the things will going to improve and like you said will be complete we hope. There is no need to keep asking the same thing over and over while it's developing.
[Galaxy S III Original Android Development] underdoq:
Thank you for your detailed reply.
[Galaxy S III Original Android Development] curiousrom:
Re: SELinux Enforcing

Maybe you could follow the links I posted in the How To Update TWRP - Official LineageOS 14.1 Safer? to get more info about what SELinux Enforcing is.

It's even more important for security on older devices with older kernels & vendor's security patches that are not up to date because it's a last line of defense. I quoted the Android Open Source Project in that post: "SELinux operates on the principle of default denial: Anything not explicitly allowed is denied.".

"Even who cares about security on a 8 years old device..." - For several users the S3 is their daily driver. As I wrote in that post: This is especially important if you use your personal accounts, shopping, banking, etc. because root + SELinux permissive or disabled + apps from shady sources = zero security. :eek:

If you are playing with a spare device without personal accounts then anything goes. If you link to the cloud where you upload personal stuff like photos, etc & if you don't care about security then it's your choice.

Edit: According to this Wikipedia page Samsung Galaxy S III: "Samsung unveiled the S III on 3 May 2012. The device was released in 28 European and Middle Eastern countries on 29 May 2012" so technically it's 6 years old & will turn 7 soon.

Also from that page: "...it had sold about 70 million units by 2015...". Impressive. According to the LineageOS stats page the i9300 is the #5 most popular LineageOS device with 40,000+ "Active installs" which means devices pinging almost everyday to the LineageOS servers. You can click on i9300 to see the breakdown by firmware builds.

"I don't know why he keeps bringing that SELinux thing.":

underdoq asked "Is this rom more safer to use than those other available one's that i've found..." so I replied to his question with facts & authoritative reference links.

If you search this thread with SELinux you will see that my last post on the subject was 3 months ago so I don't know what you mean. It was on 6th December 2018 here.

Nobody is "asking the same thing over and over" in this thread.

As I posted here in an other thread: "Developers often use SELinux Permissive in the early stage of app or firmware development & track the "avc: denied" entries in logcat to spot bugs or coding errors. There is nothing wrong with that.". {Bold added by me.}

What I asked in that thread is to include the info that SELinux Enforcing is not working @ the present in the post #1. Then users can chose to use that firmware or not depending on their usage & personal security choices.

***

Yes the LineageOS Device Support Requirements Charter is pretty strict and a bunch of stuff must work including SELinux Enforcing before a firmware is accepted in the official LineageOS roster.

That's a lot of hard work. Good luck and thanks for supporting the S3 i9300 community. :good::cool:

***
[Galaxy S III Original Android Development] ArdaCsknn:
They both said they are working on it to get the OFFICIAL tag so that means it is going to happen sometime. But you bring that thing if I'm not wrong 3 times in total. I also know it was a 7 years old device it was a miss typo. SeLinux is must needed for an old device but it is also hard to maintain an old device, patience is what we need at this time. It is really hard to get in to shady things to get hacked or get your personal stuff stolen even if you use a Permissive or Enforced SeLinux.

I'm also happy that ChronoMonochrome always reading our comments and try to make this device work after Forkbomb's silence.
[Galaxy S III Original Android Development] curiousrom:
Re: SELinux Enforcing

Yes it's hard to develop custom firmware & users should be grateful for the work done by unpaid volunteers on their free time & be patient. Nobody is denying this in this thread.

"...It is really hard to get in to shady things to get hacked or get your personal stuff stolen even if you use a Permissive... SeLinux…" - No it's not if as I wrote above you also have root & apps from shady sites.

Recently I installed a cracked app & looking in SD Maid > AppControl > Sort mode > Install date I could see the app + a spy app it also installed.

Other dangers include open Wifi attacks, phishing, attachments, etc, etc. The subject is too vast for this thread.

Edit: From the How dangerous is the fact that SELinux is in “Permissive” mode? link I included in the post above:

"SELinux is a mitigation technique. It does not prevent attackers from entering into your phone, but it ensures that once there they can do as few things as possible, ideally nothing useful thus removing any interest of attacking the phone in the first place..."

***
[Galaxy S III Original Android Development] NZedPred:
Build with 01 March 2019 security patches available

The sources have been updated with the 01 March 2019 security patches (note 01 March, not 05 March - not sure if this is a reflection of the official builds not being built anymore or something along those lines). Seems they're updating a bit faster now that there is no longer any official builds... :silly:

Android File Host - lineage-14.1-20190313-UNOFFICIAL-i9300.zip

Dropbox - lineage-14.1-20190313-UNOFFICIAL-i9300.zip

These have been built from the official Lineage repos, no alterations have been made.
[Galaxy S III Original Android Development] curiousrom:
Re: Unofficial LineageOS 14.1 Build 2019-03-13 for S3 i9300

Thanks! :good::cool:

The LineageOS devs are still updating the repos for 14.1 so all the Merged patches older than 2019-03-13 are included in your unofficial build as you can see in this LineageOS Gerrit search. I excluded all the automatic translations patches to simplify the results: branch:cm-14.1 status:merged -translation.

Note that some of these patches are not included in the i9300 tree as they are for other devices.

I can see Bump Security Patch Level to 2019-03-01 which applies to all 14.1 devices for example.

Here you can see all the patches that applies to the i9300 @ the present: https://download.lineageos.org/i9300/changes/

I did not try it yet but if installing that unofficial build over Official LineageOS 14.1 you need to do this because the signature is different:

In TWRP do a full backup so you can go back easily by restoring it in case something goes wrong including the important EFS partition.

TWRP > Wipe > Advanced Wipe > wipe System & the Dalvik / Art cache & Cache only & flash the new unofficial + Open GApps if you had it (or want to add it) in one go without rebooting in between to set the proper hooks + LineageOS addonsu if you wish.

The LineageOS addonsu can be added at a later time but not Open GApps which must be installed right after the LineageOS firmware to work properly.

If you have the time because you would need to re-install all your apps or restore a Google backup, the best would be a clean install: wipe both Data & System or a S3 i9300 LineageOS Super Clean Install which includes Format Data instead of just wipe. Note that Format Data destroys all the content of the internal sdcard as it rebuilds the entire Data file system as explained in that post.
[Galaxy S III Original Android Development] dana.marivani:
Hi everyone

In 19 december 2018 page 523 I said that good news will come soon,My good friend who became curious [MENTION=8031265]kurtn[/MENTION] [MENTION=5102787]Hesham Sleem[/MENTION]

Surprised news by Simon Shields Four hours ago linux 4.17 Updated
[Galaxy S III Original Android Development] Sobhan Mazaheri:
Linux 4.17

Wooooooooow

thanks for good news:fingers-crossed:
[Galaxy S III Original Android Development] Hesham Sleem:
Thanks ... waiting to see this on land soon
[Galaxy S III Original Android Development] curiousrom:
Re: Speculating on Simon's Work - Kernel?

Err... in https://github.com/fourkbomb/linux ("mainline(-ish) linux for smdk4412") it says @ the present: Latest commit 04b9c1d on Feb 2 and what that did is just to "Revert" a previous commit. It's like deleting a previous commit so nothing new: "fourkbomb Revert "ARM: dts: add infrastructure for building dt overlays" - This reverts commit 17e8963."

OTOH there are some recent commits to u-boot which is an alternative bootloader: https://github.com/fourkbomb/u-boot

Scroll down to Contribution activity in this page to see his activities: https://github.com/fourkbomb

@ the present for March 2019: Created 4 commits in 1 repository fourkbomb/u-boot 4 commits.

So nothing related to a kernel.

Check in his blog here to learn more about it: U-Boot on Galaxy S3

Edit: this is the kernel used by S3 i9300 LOS 14.1 @ the present https://github.com/fourkbomb/android_kernel_samsung_smdk4412 "Latest commit d735a7e on Jan 4 2017".

This is a search for that kernel in the LineageOS Gerrit: project:LineageOS/android_kernel_samsung_smdk4412 status:merged

***
[Galaxy S III Original Android Development] dark-ryuk:
Speaker volume and handset volume not enough

Hello again. I made a clean install on my S3 phone yesterday. a little faster than before. but again the speaker volume and handset tone is not loud enough. Is there a solution to this?
[Galaxy S III Original Android Development] Noobkid77:
Can't wait for theme support ??? then this ROM will b complete
[Galaxy S III Original Android Development] baltics:
I was reading up on the issue of the introduction of a theme engine for Lineage 14.1.

Unusually Cm never created one. All its earlier series had them, but not CM14.1.

I read that is why the theme developers created Substratum. I have never tried it. Officially it does not support this ROM, but from one or two posts, I think some do.

When the hard working Lineage developers will look at this remains to be seen.

In a few months we will see Google release the replacement of N with O. And so it goes on ?
[Galaxy S III Original Android Development] Noobkid77:
True by the time theme arrives there might be Android orange lol
[Galaxy S III Original Android Development] baltics:
This forum was created to discuss the question you raised

https://xdaforums.com/lineage/help/theme-support-lineage-os-t3531658
[Galaxy S III Original Android Development] i9000usersa:
I understand this may be off-topic, but does anyone know where I might find the latest modem for Argentina, Panama, Chile, or Uruguay? That Russian site doesn't say which countries those modems are for. I need one for one of the above countries, or any other where the 3g works on 850mhz and 1900mhz.
[Galaxy S III Original Android Development] zarere:
Check here

http://kernel.boeffla.de/sgs3/modems/

https://xdaforums.com/galaxy-s3/general/ref-galaxy-s3-modem-radio-collection-t1740061

http://www.android-hilfe.de/thema/efsv2-modem-thread.508822/

https://xdaforums.com/galaxy-s3/general/ref-galaxy-s3-ril-modem-cwm-flashable-t2076857
[Galaxy S III Original Android Development] Frenzi2012:
hi guys, someone try F2FS partitions in this rom?
[Galaxy S III Original Android Development] baltics:
[MENTION=6625965]Frenzi2012[/MENTION], You need to read this long post from [MENTION=4898097]arter97[/MENTION] on f2fs
[Galaxy S III Original Android Development] dzincha:
Tried to update from 31.01 to 06.02 with integrated updater. It rebooted and went in recovery - cwm. And that's it. And i couldn't find update file manually under \data\data\org.linegeos.updater

Same happened with s5 and twrp. But with twrp i managed to get downloaded zip and flash it manually.

Is it same for other users?
[Galaxy S III Original Android Development] Simon_29:
Cwm isnt supported.... Read first post.

Its under /data/data/org.lineageos.updater/app_updates .
[Galaxy S III Original Android Development] pix106:
Same for me using Twrp 3.0.2-2.

But I could manually flash the zip from /data/data/...
[Galaxy S III Original Android Development] andrescm:
The only recovery that will allow an automated update at the moment is TWRP 3.0.2-2. Follow the instructions in the OP and then you'll be able to update again without problems.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Sorry but the latest update is the BAD version ever!

From Good To Bad!

unbelievable Things happening with me

1. battery drain more than past. ?

2.frezze sometimes and rebooting. ?

new feature of flashlight with power button not working sometimes.

3.LED light when charging the phone too much "noisy"

the most important issue for all of us is BATTERY DRAIN

Please Mr. [MENTION=5405215]forkbomb444[/MENTION] fix it.

Thanks in advance
[Galaxy S III Original Android Development] baltics:
.

If you expect anyone to take note of your post, you should follow the instructions in OP1.

Reporting bugs

DO NOT report bugs if you're running a custom kernel

DO NOT report bugs if you've modifies system files

DO NOT report bugs if you've installed xposed and/or other mods

Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)

If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)

If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
[Galaxy S III Original Android Development] Ashraf Iraqian:
You right

thanks for notice
[Galaxy S III Original Android Development] sirpsychosexy86:
i cant update from Beardymarrow version... saying error 7.... any ideas ?
[Galaxy S III Original Android Development] abelenki:
yes, read official site:

http://lineageos.org/Update-and-Build-Prep/
[Galaxy S III Original Android Development] sirpsychosexy86:
ok so first update with that experimental build and then that normal?
[Galaxy S III Original Android Development] abelenki:
yes.
[Galaxy S III Original Android Development] andrescm:
If by "noisy" you mean the green light keeps blinking at random intervals when fully charged but still connected to the charger, I'm experiencing this too since unofficial 01-06 as far as I can remember.
[Galaxy S III Original Android Development] Willy89:
sorry for real dumb question but is this

lineage-14.1-20190217-nightly-i9300-signed.zip

The most recent Lieange Rom Version?
[Galaxy S III Original Android Development] kurtn:
Yes, but there are newer unofficials and forks like microG or /e/.
[Galaxy S III Original Android Development] Willy89:
Could you please link them to me?

Thanks!
[Galaxy S III Original Android Development] ArdaCsknn:
It is literally on the one page behind. Just read the thread a bit please.
[Galaxy S III Original Android Development] Andresine:
Do i have to uninstall magik everytime that there is an update of the rom? Sorry for my inglish.
[Galaxy S III Original Android Development] kurtn:
No. But S3 doesnt get regular update.
[Galaxy S III Original Android Development] Mo3az_fathi11:
Can someone tell me what is microG?
[Galaxy S III Original Android Development] kurtn:
https://microg.org/
[Galaxy S III Original Android Development] Willy89:
Good day.

About Magisk (for rooting), have you tried it with Lineage Unofficial?

Does it work good?

I've tried on my S3 (still my daily phone) but it was causing the phone to go on sleep modeand never woke up.

Maybe was just mine, or there are some issues?
[Galaxy S III Original Android Development] kurtn:
I prefer lineageOS official rooting solution from downloads/extras.
[Galaxy S III Original Android Development] Willy89:
This one here, right?

https://download.lineageos.org/extras

Little bit of memory black out in this moment: 14.1 ARM or ARM 64?
[Galaxy S III Original Android Development] eriol1:
ARM
[Galaxy S III Original Android Development] Willy89:
I've flashed (trough TWRP) this

"addonsu-14.1-arm-signed.zip"

But my S3 still appears not to be rooted..quite weird.

Any suggestion?
[Galaxy S III Original Android Development] kurtn:
Enable developer settings. There enable root.
[Galaxy S III Original Android Development] Willy89:
Right...i've done it many times but i've forgotten completely..

Feeling such an idiot :P

Thanks a lot!
[Galaxy S III Original Android Development] kurtn:
Haha! And don't forget to hit thanks button.
[Galaxy S III Original Android Development] NZedPred:
05 April security patch update now available

Hi all

I've completed a new build, and it's up now at the following places:

Android File Host - lineage-14.1-20190407-UNOFFICIAL-i9300.zip

Dropbox - lineage-14.1-20190407-UNOFFICIAL-i9300.zip

This has a security patch level of 05 April 2019.
[Galaxy S III Original Android Development] CupangTerbang:
Bug april update

Hi it's have bug.

When shutdown or restart (using power button) phone didn't respond.

Kernel also have problem. I can't turn on 1 core CPU (CPU2) it always offline > pegasusrq). Solution only change to ondemand
[Galaxy S III Original Android Development] curiousrom:
S3 Fix Power & Volume Buttons

See S3 Fix Power & Volume Buttons - Screenshot, Screen Mirroring & Dead Screen.

***
[Galaxy S III Original Android Development] rfmalta:
Will we get an update tomorrow? make your bets!
[Galaxy S III Original Android Development] kurtn:
Official? No way!
[Galaxy S III Original Android Development] CupangTerbang:
Fixed by changing to custom kernel

Thanks. But it already fixed by changing to custom kernel.

I want ask for phone status, is this normal for this phone ? :

1. Normal CPU temp for this phone ? (53°c at gaming mode & 44°c for normal operation mode. Cpu max clock set to 1.5Ghz)

2. Battery normal temp ? (Got 40° gaming, 30° do nothing and normal mode) duration : 12H sleep state, with cellular network. 2H gaming.

3. Phone Voltage : 4.19 v = battery 100% and 3.4v = battery 35%. But phone regulator out are normal 1.1v when no battery with charger plugged.
[Galaxy S III Original Android Development] Pirate83:
Hi,

Does it mean that there will not be official release anymore ? :crying: